CORE
Executable constitutional governance for AI-assisted software development.
Current Release: v2.16.1 — see CHANGELOG.md.
What CORE is
CORE audits a codebase against declared rules in .intent/, records every
violation, proposes fixes, and logs the chain from finding to commit. AI
assistants and CORE's own loop can propose changes; only the human governor
approves them. What it is for, in plain words: What CORE does.
The pip install below gives you the offline audit, CORE's audit on every pull
request (GitHub Action) and, for your AI assistant, the rules and a verdict on
its change before it commits. Recording findings, proposing fixes, CORE's own
loop and changes submitted for your approval need the full local runtime (last
block of this section).
Install and first run
You need Python 3.12 or later and git. On Debian and Ubuntu, python3 -m venv
also needs the python3-venv package (sudo apt install python3-venv git).
python3 -m venv .venv && . .venv/bin/activate
pip install core-runtime
Current Ubuntu and Debian refuse a bare pip install outside a virtual
environment ("externally-managed-environment"); the first line creates one
(pipx install core-runtime works too). This gives you the core-admin CLI. In a repository that already has a
.intent/ constitution, audit it with no services running:
core-admin code audit --offline
To bring CORE into an existing repository, no services are needed either:
cd your-repo
core-admin project init . --write --yes
core-admin project adopt-pack core/starter-python --write
git add .intent .github && git commit -m "Adopt CORE"
core-admin code audit --offline
project init --write asks for confirmation at a terminal; --yes skips the
question, and without a terminal (CI, scripts, AI agents) it stops at once
unless --yes is given.
The audit judges the law committed at HEAD, so commit .intent/ first;
uncommitted law reads DEGRADED, never PASS. project init also writes CORE's
GitHub Action (.github/workflows/core-audit.yml); commit it with the law. The
audit lists blocking and high findings; reporting and advisory ones are only
counted. Add --severity info to list them too.
Connect your AI assistant (Claude Code shown; any MCP client works) so it asks CORE about your project's rules and checks its change before committing; see Connect your AI assistant:
claude mcp add --scope project core -- core-admin mcp run
Claude Code starts core-admin itself, so it must be on PATH in the shell
you start claude from: activate the virtual environment first, or install
with pipx install core-runtime (then pipx ensurepath) so it is on PATH in
every shell; get pipx first with sudo apt install pipx on Debian/Ubuntu. Everyone who uses the committed .mcp.json needs the same.
A new project:
core-admin project new myproject --write
cd myproject
git init
core-admin project adopt-pack core/starter-python --write
git add -A && git commit -m "Adopt core/starter-python"
core-admin code audit --offline
To run the full local runtime (Postgres + Qdrant) from a clone (it also needs Docker with Compose v2 and Poetry; every prerequisite is in Run the full runtime):
git clone https://github.com/DariuszNewecki/CORE.git
cd CORE
./install-core.sh
More
- Decisions: .specs/DECISIONS.md
- Documentation: docs/, published at dariusznewecki.github.io/CORE
License
MIT — see LICENSE.
1 maintainer
Metadata
1 maintainer
Release files for core-runtime 2.16.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| core_runtime-2.16.1.tar.gz | 2.0 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| core_runtime-2.16.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.8 MB
Release files / core_runtime-2.16.1.tar.gz
| Download URL | core_runtime-2.16.1.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9cfa252c481343c40e5422cf0e62caf7d64047967516aa75f7764cce116b393d
|
|
BLAKE2b-256 checksum How to use checksums |
7f3a114f477e517182c8daa9278ee15bc2c9ff40f54d98ece18fa743d45fea1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / core_runtime-2.16.1-py3-none-any.whl
| Download URL | core_runtime-2.16.1-py3-none-any.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
115294814c57e49f4cdee1a0775a24a2344b4b65462a2d54957d14539bbc8a10
|
|
BLAKE2b-256 checksum How to use checksums |
a48d70d11bf5337b8ff2ec156c4ed05fd7d489e513e4a4615f08cab438af0632
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for core-runtime 2.16.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for core_runtime-2.16.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
