Executable constitutional governance for AI-assisted software development.Designed for environments where AI action traceability is not optional.
Versioning: SemVer with 2.x denoting an API approaching stability (Beta on PyPI); see the versioning policy.
AI coding tools generate code fast. Too fast to stay sane.
Without enforcement, AI-assisted codebases accumulate invisible debt — layer violations, broken architectural contracts, files that grow unbounded. And agents, left unconstrained, will eventually do something like this:
Agent: "I'll delete the production database to fix this bug"
System: Executes.
You: 😱
CORE makes that class of violation impossible — structurally blocked before execution, not detected after the fact. (Which surfaces hard-block versus advisory-report is mapped under Current proof status below.)
Agent: "I'll delete the production database to fix this bug"
Constitution: BLOCKED — Violates data.ssot.database_primacy
System: Execution halted. Violation logged.
You: 😌
CORE is a governance runtime that constrains AI agents with machine-enforced constitutional law — enforcing architectural invariants, blocking invalid mutations automatically, and making autonomous workflows auditable and deterministic.
LLMs operate inside CORE. Never above it.
You don't have to take this on faith. On a clean machine with Docker:
git clone https://github.com/DariuszNewecki/CORE.git
cd CORE && ./install-core.sh
install-core.sh
stands up CORE and finishes by running the consequence-chain demo live — no LLM key required. It:
- commits a function that violates
linkage.assign_ids
(a blocking rule) - watches CORE's audit block it - has CORE propose a fix, the governor approve it, and CORE execute it and commit the repair
- re-audits to confirm clean - prints the full causal chain it recorded: finding → proposal → approval → execution → file change
Re-run it any time with scripts/demo.sh
.
Governance is executable.
Every enforced action records its lineage. Two consequence chains, pulled live from the CORE database — same schema, two different authorities:
Autonomous path — risk-classified as safe, system self-approved
FINDING → workflow.ruff_format_check src/api/cli/client.py 2026-05-18 05:15:15 UTC
PROPOSAL → 8845dacc… fix.format 2026-05-18 05:16:15 UTC
APPROVAL → risk_classification.safe_auto_approval 2026-05-18 05:16:15 UTC
EXECUTION → completed (1.29s) 2026-05-18 05:17:18 UTC
FILE CHANGE → +105 / -0 98da9038 → fca9a971 src/api/cli/client.py 2026-05-18 05:17:19 UTC
Human-approval path — governor in the loop
FINDING → purity.docstrings.required src/cli/commands/audit_reporter.py 2026-05-15 08:28:29 UTC
PROPOSAL → a4363a81… fix.docstrings 2026-05-16 13:39:34 UTC
APPROVAL → principal.governor (cli_admin) 2026-05-16 13:53:32 UTC
EXECUTION → completed (24.5s) 2026-05-16 13:55:48 UTC
FILE CHANGE → +26 / -0 5a123426 → 71fde489 src/cli/commands/audit_reporter.py 2026-05-16 13:55:49 UTC
Both chains are queryable end-to-end from proposal_consequences
and blackboard_entries
. The constitution decides which authority applies; the schema is identical. Reproduce them yourself with the Consequence-chain query in the Proof Index.
CORE separates responsibility across four repository layers — three enforced as constitutional law, and Specs (human intent). This separation is enforced as law — not convention.
Where humans define what the system is for and why decisions were made. Contains architectural papers, northstar documents, user requirements, architectural decision records, and planning documents. This is the entry point for anyone trying to understand CORE before reading its implementation.
.specs/
is read by humans and searchable by CORE's semantic layer. It is never written by CORE itself.
Defines what is allowed, required, or forbidden. Contains machine-readable constitutional rules, enforcement mappings, phase-aware governance models, and the authority hierarchy (Meta → Constitution → Policy → Code
).
Mind never executes. Mind never mutates. Mind defines law.
Reads constitutional constraints, orchestrates autonomous reasoning, and records every decision with a traceable audit trail. Every operation follows a structured phase pipeline:
INTERPRET → PLAN → GENERATE → VALIDATE → STYLE CHECK → EXECUTE
Will never bypasses Body. Will never rewrites Mind.
Deterministic, atomic components: analyzers, evaluators, file operations, git services, test runners, CLI commands.
Body performs mutations. Body does not judge. Body does not govern.
Every autonomous operation is governed by the same constitutional loop:
flowchart TD
A["🟢 GOAL\nHUMAN INTENT"] --> B["📂 CONTEXT\nRepo state • knowledge • history"]
B --> C["🔒 CONSTRAINTS\nImmutable rules\n215 rules • 15 engines"]
C --> D["🗺️ PLAN\nStep-by-step reasoning\nRule-aware plan"]
D --> E["✨ GENERATE\nCode • changes • tool calls"]
E --> F["✅ VALIDATE\nDeterministic checks\nAST • semantic • intent • style"]
F -->|Pass| G["▶️ EXECUTE\nApply compliant changes"]
F -->|Fail| H["🔄 REMEDIATE\nRepair violation\nAutonomy Ladder"]
H --> E
G --> I["✓ SUCCESS\nChanges committed"]
subgraph "SAFETY HALT"
direction TB
J["🚨 CONSTITUTIONAL VIOLATION\n→ HARD HALT\n+ FULL AUDIT LOG"]
end
E -.->|Any violation| J
F -.->|Any violation| J
classDef phase fill:#f8f9fa,stroke:#495057,stroke-width:2px
classDef constraint fill:#d1e7ff,stroke:#0d6efd,stroke-width:2.5px
classDef validate fill:#fff3cd,stroke:#ffc107,stroke-width:2.5px
classDef halt fill:#ffebee,stroke:#dc3545,stroke-width:3px
class A,B,D,E,G,I phase
class C constraint
class F validate
class J halt
Within CORE:
- No file outside an autonomy lane can be modified
- No structural rule can be bypassed silently
- No atomic action can execute outside the governed executor (inline authorization is deferred to the audit→consequence loop)
- Decisions are phase-aware and logged with decision traces (audit persistence is best-effort — see Current proof status) - No agent can amend constitutional law
If a blocking rule fails, execution halts with no partial state. Reporting and advisory rules surface findings and continue — what blocks versus what reports depends on the mode.
CORE's guarantee semantics are split across modes by design. This is the honest map of what each surface does, so a single binary claim ("CORE blocks violations") is not mistaken for the whole picture:
| Surface | Mode | Behaviour |
|---|---|---|
.intent/ writes |
||
| hard invariant | blocked — the governance directory is immutable to all components | |
| Constitutional rules | always-blocking | block a commit regardless of strict mode |
| Policy rules | strict vs. default | block only when strict_mode=True ; otherwise report |
| Capability tier | advisory today | reports a "would-deny" signal; does not yet block (ADR-079) |
| Stateless CI (GitHub Action) | rule subset | skips knowledge_gate + llm_gate (they need DB / LLM state) and reports the skip |
| Action audit trail | best-effort | recorded when the DB write succeeds; a write-action failure is surfaced (AUDIT_GAP ), not silent |
The hard invariants and constitutional rules block unconditionally; the policy, capability, and stateless tiers are weaker by design and labelled here so the boundary is legible rather than implied.
| Primitive | Purpose |
|---|---|
| Document | Persisted, validated artifact |
| Rule | Atomic normative statement |
| Phase | When the rule is evaluated |
| Authority | Who may define or amend it |
Enforcement strengths: Blocking · Reporting · Advisory
| Engine | Method |
|---|---|
ast_gate |
|
| Deterministic structural analysis (AST) | |
regex_gate |
|
| Pattern-based text enforcement | |
glob_gate |
|
| Path and boundary enforcement | |
cli_gate |
|
| CLI surface and command-shape enforcement | |
artifact_gate |
|
| Declared-vs-discovered artifact completeness | |
workflow_gate |
|
| Phase-sequencing and coverage checks | |
knowledge_gate |
|
| Responsibility and ownership validation | |
action_gate |
|
| Atomic-action invariants | |
passive_gate |
|
| Substrate-enforced rules (DB/runtime marker) | |
taxonomy_gate |
|
| Capability-id ↔ atomic-action coherence (ADR-079 D9) | |
contracts_gate |
|
| Cross-cutting data-contract coherence (context-level; ADR-102) | |
llm_gate |
|
| LLM-assisted semantic checks | |
IntentGuard * |
|
| Runtime write authorization (not audit) |
*Runtime Gate per .specs/papers/CORE-Gate.md
, kept here for visibility.
Deterministic when possible. LLM only when necessary.
215 rules across 51 rule documents. 209 are mapped to enforcement engines; 6 test-quality rules are still pending mappings. "Mapped" means engine-bound — not enforced in every mode: stateless CI skips knowledge_gate
and llm_gate
, which need the knowledge graph and an LLM provider.
CORE progresses through defined levels. Each adds capability while remaining constitutionally bounded.
A0 — Self-Awareness ✅ Knows what it is and where it lives
A1 — Self-Healing ✅ Fixes known structural issues automatically
A2 — Governed Generation ✅ Natural language → constitutionally aligned code
A3 — Governed Autonomy ✅ Daemon finds, proposes, and fixes violations unattended ← current
A4 — Self-Replication 🔮 Writes CORE.NG from its own understanding of itself
| Dependency | Version |
|---|---|
| Python | 3.12+ |
| PostgreSQL | ≥ 14 |
| Qdrant | latest |
| Docker | for services |
| Poetry | for deps |
Honest status — what works today.CORE governsitselfend to end (the demo above), and audits any repo thathas a— in CI via the.intent/
constitution[GitHub Action], or locally withcore-admin code audit --offline
inside that repo.pip install core-runtime
gives you thecore-admin
CLI.
Govern your own repo (BYOR):from the CORE source tree, two commands bootstrap a fitted constitution. (1)core-admin project onboard <path> --write
delivers the machinery floor (no LLM, no database). (2)core-admin project scout <path> --write
reads your source, proposes candidate rules via LLM, and requires you to ratify each before delivery — no LLM means a curated four-rule menu instead.core-admin code audit --offline
inside that repo enforces the ratified rules immediately. Source-tree only for now — the machinery floor andproject scout
are not yet bundled in the wheel ([#674]).
Fastest way to see CORE today: run it on itself, below.
Full local runtime — one command. Clone, then run the installer:
git clone https://github.com/DariuszNewecki/CORE.git
cd CORE
./install-core.sh
install-core.sh
checks prerequisites, installs dependencies, starts Postgres + Qdrant, applies the schema, and finishes by showing CORE govern itself — a violation found, proposed, approved, fixed, and verified, with the consequence chain recorded. No LLM API key needed for the demo.
Prefer to run the steps yourself? #
poetry install
cp .env.example .env
docker compose up -d
docker compose exec -T postgres psql -U postgres -d core < infra/sql/db_schema_live.sql
poetry run core-admin code audit --offline # offline mode needs no running services
Full setup — services, schema, vector sync, first audit — is in Getting Started.
Full documentation, architecture deep-dive, and governance reference: dariusznewecki.github.io/CORE
To understand what CORE is for before reading its implementation, start here:
.specs/northstar/CORE-What-It-Does.md
Current Release: v2.7.0 — Bounded Autonomy
Active work: A3 Governed Autonomy — the daemon runs continuously, finds constitutional violations in its own codebase, proposes fixes, executes approved fixes, and verifies the result. The governor's role is to define intent, review proposals that require architectural judgment, and approve constitutional changes.
All four A3 integrity gates are now closed. No enforcement logic or operational threshold lives in src/
— governance is declared in .intent/
and enforced from there. The autonomous loop is circuit-breaker protected; systematic errors surface as signals rather than unbounded churn.
| Gate | Meaning | Status |
|---|---|---|
| G1 — Loop closure | Round-trip autonomous fix demonstrated | ✅ |
| G2 — Convergence | Circuit-breaker; resolution rate > creation rate | ✅ |
| G3 — Consequence chain | Causality queryable end-to-end | ✅ |
G4 — Governance in .intent/ |
||
No enforcement logic or thresholds in src/ |
||
| ✅ |
Build fast with AI. Stay constitutionally aligned.