CORE
Executable constitutional governance for AI-assisted software development.
Current Release: v2.15.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.
Install and first run
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
core-admin project adopt-pack core/starter-python --write
git add .intent && git commit -m "Adopt CORE"
core-admin code audit --offline
The audit judges the law committed at HEAD, so commit .intent/ first;
uncommitted law reads DEGRADED, never PASS.
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
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:
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.15.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.15.1.tar.gz | 2.0 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| core_runtime-2.15.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 4.7 MB
Release files / core_runtime-2.15.1.tar.gz
| Download URL | core_runtime-2.15.1.tar.gz |
|---|---|
| Size | 2.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ea1d07628d9cbf69b4a66ec61d98bc113577eea7a3d4b4fa6b43a5ce6ae637a
|
|
BLAKE2b-256 checksum How to use checksums |
7d9ea72017b92a42ac836d7a7c755f6c99d2491d40e80dac1bd70fd82c51b3a8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 19, 2026.
Transparency logRelease files / core_runtime-2.15.1-py3-none-any.whl
| Download URL | core_runtime-2.15.1-py3-none-any.whl |
|---|---|
| Size | 2.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a782e828bf7d9a49700fc9b06ae9c3b98cf454f7277a72c4b6ca17c0c660152f
|
|
BLAKE2b-256 checksum How to use checksums |
821958577ae280a144c1943d3e8c1af8bedcf55f020a266c221701030165fdc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 19, 2026.
Transparency logSecurity for core-runtime 2.15.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.15.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 19, 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.
