cordanaLLM/praetor

Enterprise Fleet Governance, Repository-as-Code & Universal AI Agent Engineering Engine
*An open governance engine for any repository fleet: your repositories, your fork, your policy.*
[![Documentation Governance][praetor-docs-badge]][praetor-docs-runs]
Praetor manages this repository's declared governance policy. This managed
block records adoption state; it is not a verification certificate.
**Verification**: make verify-all runs the repository's configured
verification cascade.
**HISS Audit**: praetorctl audit enforces policy, generated-surface
integrity, and the debt ratchet.
**Context Sync**: praetorctl compile-context --verify verifies every
generated agent context against AGENTS.md.
**Documentation**: make docs-lint enforces locked Markdown style and the
private scratch-link policy.
**Debt Baseline**: .standards-baseline.json anchors the debt ratchet at
2 recorded infractions; audit forbids growth.
[praetor-docs-badge]: https://github.com/cordanaLLM/praetor/actions/workflows/praetor-docs.yml/badge.svg
[praetor-docs-runs]: https://github.com/cordanaLLM/praetor/actions/workflows/praetor-docs.yml
---
🏛️ Executive Summary
**Praetor** is an open governance engine for any repository fleet: you run it against your own repositories or your own fork of it, and its default owner, target framework, review bot and organisation-folder list stay empty until you configure them (framework, forge and topology settings). Built in Go 1.27+, Praetor transforms repository governance into a deterministic, active platform capability by combining **Repository-as-Code** orchestration, **context transpilation** across vendor-specific AI tools, and unbypassable **HISS (High-Integrity Systems Standard)** invariant enforcement.
While traditional repositories suffer from configuration drift and agentic fragmentation, Praetor maintains a single canonical source of truth—**AGENTS.md**—and compiles it into vendor-specific harnesses (.claude, .cursor/rules/*.mdc, .windsurfrules, .gemini/GEMINI.md, .github/copilot-instructions.md, .codex/rules.md) while ensuring mathematical code quality and debt ratcheting.
---
📐 Architecture & Transpilation Flow
Praetor resolves context compilation and lattice configuration through a single-pass DAG pipeline:
Governance Lifecycle
Text description
Vendor Projections: CLAUDE.md (< 300 LOC), .cursor/rules/*.mdc, .github/copilot-instructions.md, .windsurfrules, .gemini/GEMINI.md, .codex/rules.md.
Boxes: AGENTS.md (Canonical Source), praetorctl compile-context, .standards.yaml (& .standards.lock), Effective Policy (Lattice Supremum), .devcontainer & Toolchain, praetorctl audit, praetorctl plan, praetorctl gate run, Gate stages, Ed25519 Exit-0 receipt.
AGENTS.md → praetorctl compile-context → CLAUDE.md.
praetorctl compile-context → .cursor/rules/*.mdc.
praetorctl compile-context → .github/copilot-instructions.md.
praetorctl compile-context → .windsurfrules.
praetorctl compile-context → .gemini/GEMINI.md.
praetorctl compile-context → .codex/rules.md.
.standards.yaml → Effective Policy → .devcontainer & Toolchain.
Effective Policy → praetorctl audit.
Effective Policy → praetorctl plan.
praetorctl gate run → Gate stages → Ed25519 Exit-0 receipt.
Scenario 1, compile-context: AGENTS.md is transpiled to vendor-specific files. The single source of truth is read. Target-specific files are generated.
Scenario 2, policy: The lattice resolves standard definitions into effective policy. Manifest and lockfile are merged. Policy applies to the devcontainer toolchain, audit enforcement, and plan previews.
Scenario 3, gate run: praetorctl gate run executes the gated pipeline. The gate command triggers the verification cascade. A successful run mints a signed receipt.