Someone renamed a file. An AI session quietly rewrote a spec. You edited a design doc six months ago and cannot remember what changed. By the time anyone notices, the decision that mattered is gone.
Chronolith notices. It gives your documentation one hash — a one-byte edit, a rename, or two files swapping contents all move it — and refuses the push when the tree stops matching a signed baseline.
pip install chronolith-lite
chronolith-lite init
chronolith-lite checkNow change any tracked file and run check again. That is the whole idea, and
it takes a minute. Nothing here asks you to trust the author: verify is
read-only, and it reports what it did not prove.
A cryptographic integrity layer for the documents that carry a project's intent across AI-assisted sessions.
Chronolith hashes your canonical project documents into a Merkle tree, records a signed baseline, and fails closed when the current state no longer matches it — so unintended changes to a project's context are caught before they propagate, instead of being discovered later. It does not read minds or guarantee an AI "remembers"; it gives you a verifiable record of what the agreed context was, and a hard stop when it drifts.
The names in this project (DNA, sovereign, nucleotides) are deliberate narrative. What they map to technically — and why — is documented plainly in LORE.md. The engineering docs below make only claims a test or a command can back up.
Chronolith addresses semantic drift in long-term AI–human collaboration:
- Cross-agent handoffs — carry a signed, verifiable snapshot of project context between models and sessions, and detect if it was altered in transit.
- RAG source-of-truth integrity — keep retrieval pointed at documents whose state is cryptographically pinned, and notice when they change.
- Architectural provenance — an auditable, signed history (and optional Bitcoin timestamp) of how the project's canonical documents evolved.
Get the entire Ethernium Chronolith Ecosystem running in seconds:
# Install the unified metapackage
pip install chronolith
# Initialize the Guardian DNA in your current project
chronolith init
# Verify state consistency
chronolith check
# [NEW] Audit project cognitive weight (tokens)
chronolith-tokens scanA DNA state from this project is anchored in Bitcoin block 958484. You can verify it without trusting this repository or its author — the proof and the one-line command are in docs/evidence/, alongside measured guardian benchmarks and the adversarial (red-team) results.
To address the need for concrete evidence, we provide a verified Case Study and Benchmarks:
- CASE_STUDY_DRIFT.md: A real-world demonstration of how Chronolith detects and blocks unauthorized semantic changes that Git ignores.
- BENCHMARKS.md: Measured performance results (Latencies, Memory footprint, and Merkle scan speeds).
The three editions install standalone (each vendors its own core), so run the full audit per edition in isolated processes — one command:
python scripts/audit_all.py # per-edition tests + cross-edition core parity
python scripts/audit_all.py --install # also build + install each guardian in a clean venvCross-edition parity guards the deliberate vendoring: if a shared core primitive drifts between Lite/Pro/Omega, the audit fails.
- Choose Your Edition
- Technical Specifications
- 30-Second Quickstart
- Quick Installation
- Operation Modes
- Core Infrastructure
- The Quality Flow
- Guardian DNA Algorithm
- Origins: The Ethernium Heritage
- Documentation Quick Index
- Documentation Index
Minimalist local sync with DNA Synthesis for zero-loss handoffs.
Industrial-grade border guard. Features Enterprise-grade cyber-security, RFC 6962 Merkle Hardening, and Fail-Closed Hooks.
Advanced RAG and cognitive mapping over the governed corpus.
| Guide | Link |
|---|---|
| Start here | Five minutes: pick an edition, crystallize a project, watch drift get caught |
| Industrial Guide | HOW_TO_USE_IT.md |
| Editor & Agent Integration | VS Code, Cursor, MCP and agent-host boundary |
| External Tools | Seneschal extraction notes |
| Production Readiness | Supported gates, portability contract and honest limits |
| Release Manifest | RELEASE_NOTES_MANIFEST.md |
Chronolith implements high-integrity governance for the project lineage:
- Path-bound Merkle Integrity: Every markdown file is a leaf keyed by its path, so a one-byte edit — or a rename, or a content swap between two files — changes the root hash.
- Real drift detection:
checkcompares the computed root against a signed baseline and halts (fail-closed) when they diverge — not only on secrets or doc-parity. - Sovereign cryptography (Pro): Ed25519-signed baselines, an append-only DNA transparency chain, O(log n) Merkle inclusion proofs, real X25519 sealed context, and a passphrase-protected key vault. See chronolith-pro/SOVEREIGN_SECURITY.md.
- Deterministic synthesis: LF-normalized hashing gives the same root on Windows and Linux, so verification is cross-platform.
- External witness (Pro):
anchortimestamps the transparency-chain head into Bitcoin via OpenTimestamps, so a third party can verify the DNA state existed at a given time without trusting the operator. See SOVEREIGN_SECURITY.md. - Fail-closed hooks: Git hooks that block a push when DNA drift, a broken transparency chain, or an invalid signature is detected.
Chronolith provides three levels of depth in governance:
- Border Control: Strict validation of commits against the project's logical heritage.
- DNA Integrity: Automated file synchronization of documentation and source code.
- Global Awareness: Full documentation and CLI support localized in 9 languages.
- Diamond Sanitization: Deep purge of encoding errors (mojibake) and streamlined terminal-friendly directory structures.
- [NEW] Token Sentinel (v1.0): Integrated telemetry to monitor project "Cognitive Weight" and optimize LLM context consumption.
Lite and Pro answer "has this changed?". Omega answers "why did we decide this?" — semantic search over the governed corpus, entirely local.
pip install chronolith-omega
chronolith-omega init # memory core + auto-index hook
chronolith-omega index # build the local vector store
chronolith-omega query "why did we choose Ed25519 for signatures?"query ranks the corpus by meaning rather than keywords, so it finds the
decision log for that question even though the log never contains the word
"why" — and it answers across languages, because the embeddings are
multilingual, not translated.
chronolith-omega map # -> outputs/chronolith/cognitive_map.htmlmap renders the decision lineage as an interactive hierarchical graph: each
logged decision becomes a node, chained in the order it was taken.
Note
The generated map loads vis-network from a CDN, so that one HTML file needs
network access to render. Indexing and querying are fully local — nothing
about your corpus leaves the machine.
Seneschal is the external agent-operations layer for token frugality, prompt-risk scanning, scoped capabilities, MCP, and local/cloud routing. Chronolith remains the Python runtime and governance core.
CONEKTA is the optional local-first dashboard — a cockpit that renders the DNA transparency chain and Seneschal's state read-only, through the governed FRUGAL verifier boundary (see docs/external/CONEKTA.md). It visualizes the ecosystem; it does not govern it.
Tip
READ MORE: docs/external/README.md
Each edition is optimized for specific resource footprints:
| Edition | RAM (Min) | Storage | Dependencies | Best For |
|---|---|---|---|---|
| Lite | < 100 MB | < 5 MB | Zero | Local Dev / CI-CD |
| Pro | 4 GB | 50 MB | Standard | Industrial Handoffs |
| Omega | 16 GB+ | 500 MB+ | RAG/Graph | Enterprise Strategy |
examples/example-project/is a pre-configured sandbox included in this repository. It simulates a real project already managed by Chronolith.
- Navigate to the example environment:
cd examples/example-project - Verify the DNA Parity:
python ../../chronolith-lite/run_chronolith_lite.py check
- Expected Outcome: You will see a green
[OK] Parity Confirmed.
# 1. Clone the repository
git clone https://github.com/SteveBlackbeard/CHRONOLITH-by-Ethernium.git
cd CHRONOLITH-by-Ethernium
# 2. Install from PyPI (when published)
pip install chronolith-lite
# Or install locally in editable mode
pip install -e chronolith-lite
# 3. Activate the Sentinel Guardian (auto Git-Hooks + DNA init)
chronolith-lite init
# 4. Verify your DNA parity
chronolith-lite checkChronolith uses a Total Decoupling design. Editions are not a monolithic block, but independent tools operating on a single source of truth:
- Absolute Independence: Using
Litedoes not consumeProorOmegaresources. Engines only consume RAM/CPU on demand. - Common Substrate: All editions share the
.chronolith/STATE.jsonandPROJECT_CONTEXT.md. - Passive Interoperability: A change registered by one edition is immediately visible to others, ensuring the logical lineage flows without friction.
sequenceDiagram
participant D as Developer (Architect)
participant SDK as SDK Identity (ED25519)
participant HG as Hub Guardian (GHOST_MODE)
participant TC as THE_CHOSEN_ONES (Registry)
participant DNA as DNA Ledger (STATE.json)
D->>SDK: Sign Context Seed
SDK->>HG: Verify Cryptographic Identity
HG->>TC: Audit Collaborator Key
alt Identity Verified
TC->>HG: Grant Access (Open Nucleotides)
HG->>DNA: Update Merkle Root
HG->>D: Green Badge (v3.0.3)
else Identity Missing
HG->>D: REJECT (SDK_ERROR)
Note over HG: Context stays LOCKED
end
Chronolith can be integrated into your workflow in three main ways:
- Autonomous Mode (CLI): Run
chronolith-lite checkmanually. - Sentinel Mode (Automatic Guardian): Use
chronolith-lite initto install Git-Hooks automatically. - Auditor Mode (Manual DNA): Use the parity script to generate drift reports.
- Metabolism Optimization: Typ-Rich engine with <100ms startup and lazy-loading of cores.
- DNA Synthesis: Merkle Tree cryptographic protection (SHA-256).
- Cryptographic Identity: Digital signing of Project DNA using ED25519 (v2.6.0+).
- Dual Bridge Portals: Symmetric Identity for ZIP files (
Ethernium_Portal_Inside/Outside). - Token Sentinel: Context telemetry and x10 optimization via ENE.
- Governance: Sentinel Guardian with automatic Git-Hooks and session logging.
- Global Symmetry: Industrial-grade documentation and CLI support in 9 languages.
- Industrial Sanitization: Full purge of UTF-16 files and tactical debris.
Chronolith organizes project intelligence into structured nodes:
- .chronolith/: The memory core with
TIMELINE.mdandDECISIONS_LOG.md. STATE.json: State snapshot protected by SHA-256 signature.PROJECT_CONTEXT.md: Defines the rules and the strategic soul of the system.
Tokenator is the cognitive engine that manages context density and security. It operates on the principles of Information Theory to minimize token cost while maximizing logical purity.
Chronolith acts as a "Socratic Firewall". It protects your design intent through a deterministic validation loop.
graph LR
subgraph "Input Layer"
RAW[Raw Context/Code]
end
subgraph "Processing Layer (Chronolith Runtime)"
RAW --> H[Shannon Entropy Audit]
H -- "H < 5.0 (Pure)" --> ENE[ENE v3.0 Mapping]
H -- "H > 5.0 (Noisy)" --> REF[Suggest Refactor]
ENE --> SYMB[Symbolic Equations]
end
subgraph "Security Layer (THE_CHOSEN_ONES)"
SYMB --> SDK[SDK Sealing]
SDK -- "GHOST MODE" --> LOCK[Encrypted Nucleotide .locked]
end
graph TD
A[Context Gravity] -- "Raw Fragments" --> B((Entropy Reduction))
B -- "Minimizing H(X)" --> C[Logic Density Maximized]
C -- "Chronolith Core" --> D{Cryptographic Persistence}
D -- "Authorized" --> E[Instant Context Restoration]
D -- "Unauthorized" --> F[Semantic Silence]
Chronolith uses a deterministic "Nucleotide" hashing algorithm to generate the unique identity of a project.
- Nucleotide Hashing: Each canonical artifact (
.md,.json) is processed using SHA-256. - DNA Synthesis: The system aggregates these segments into a hierarchical Merkle Tree.
- The Merkle Root: El hash final que representa el Estado Absoluto.
The governed runtime phase is protected by explicit contracts, health checks, and baseline verification. Open source contributions are welcomed, while critical logic and symbolic DNA remain protected by review gates.
- How to Collaborate: See CONTRIBUTING.md for keys and access.
- Support: Reach out via X (@ethernium) or Email
Chronolith was born from the systemic need within the Ethernium Ecosystem, an evolving frontier of cognitive computing and autonomous systems. Where session resets occur millions of times, the risk of "Semantic Entropy" was critical. We needed to ensure that the soul of a project transitioned from one cognitive instance to the next without loss or drift.
Chronolith: Protecting the logical lineage of your software.
| Section | What You Will Find |
|---|---|
| Root Documents | Core project docs: changelog, governance, usage, security, and DNA. |
| Process Documents | Release checklists, staging plans, session logs, and token reports. |
| Archive Documents | Historical portal/demo artifacts kept out of the root view. |
| Root Translations | Localized root README and release-note variants. |
| External Tool Documents | Seneschal extraction notes and adapter boundary. |
| Lite Edition Documents | Lightweight package docs and handoff references. |
| Pro Edition Documents | Full operational package docs, roadmap, troubleshooting, and examples. |
| Omega Edition Documents | Omega package overview and context docs. |
| Example and Demo Documents | Demo and sample-project walkthrough material. |
| Internal Chronolith Core Documents | Internal chronolith ledgers, templates, boot protocols, and registry docs. |
| Document | Purpose |
|---|---|
README.md |
Main overview of Chronolith, its philosophy, architecture, and core capabilities. |
CHANGELOG.md |
Historical record of major releases, hardening milestones, and ecosystem evolution. |
PROJECT_CONTEXT.md |
Strategic and conceptual framing of the project, including its operating intent. |
PROJECT_DNA.md |
Canonical description of project identity and continuity lineage. |
CONTRIBUTING.md |
Collaboration rules, contribution entry points, and protected-logic contribution policy. |
CONTRIBUTORS.md |
Contributor-facing collaboration principles and engineering expectations. |
SECURITY.md |
Security posture, protected logic expectations, and handling of sensitive system areas. |
GOVERNANCE.md |
Governance model, stewardship expectations, and system authority boundaries. |
HOW_TO_USE_IT.md |
Practical guide for installing, running, and using Chronolith. |
BENCHMARKS.md |
Performance and measurement notes for the system and its workflows. |
CASE_STUDY_DRIFT.md |
Analysis of drift, chronolith failure modes, and why the system exists. |
ETHERNIUM_UNIVERSAL_DNA.md |
Ethernium-wide lineage and identity framing for the broader ecosystem. |
RELEASE_NOTES_MANIFEST.md |
Release-note manifest and documentation map for published versions. |
| Document | Purpose |
|---|---|
docs/process/SESSION_LOG.md |
Working-session trace and continuity record for recent development cycles. |
docs/process/SESSION_TOKEN_REPORT.md |
Token telemetry and session-level reporting artifacts. |
docs/process/REPO_AND_PYPI_RELEASE_CHECKLIST.md |
Release checklist for GitHub publication and PyPI packaging. |
docs/process/RELEASE_STAGING_PLAN.md |
Commit/staging strategy for safe release preparation. |
| Document | Purpose |
|---|---|
docs/archive/Ethernium_Portal_Outside.json |
Legacy portal metadata retained for traceability. |
docs/archive/demo_portal.zip |
Legacy demo portal artifact retained outside the root view. |
| Document Set | Purpose |
|---|---|
OTHER_LANGUAGES/README_*.md |
Translated editions of the main root README. |
OTHER_LANGUAGES/RELEASE_v2.1.0_*.md |
Translated release notes for the v2.1.0 release line. |
OTHER_LANGUAGES/RELEASE_v2.1.0-NEXUS_*.md |
Translated release notes for the NEXUS-specific release line. |
| Document | Purpose |
|---|---|
docs/external/README.md |
Index of external tools related to Chronolith. |
docs/external/AGENTOPS.md |
Seneschal product boundary, token-frugality role, usage, and MCP notes. |
| Document | Purpose |
|---|---|
chronolith-lite/README.md |
User-facing guide for the Lite edition. |
chronolith-lite/PROJECT_CONTEXT.md |
Lite edition context, scope, and intended usage model. |
chronolith-lite/LIVE_HANDOFF.md |
Handoff guidance for continuity across active sessions. |
chronolith-lite/OTHER_LANGUAGES/README_*.md |
Translated Lite README set. |
| Document | Purpose |
|---|---|
chronolith-pro/README.md |
Main guide for the Pro edition and its richer operational tooling. |
chronolith-pro/CHANGELOG.md |
Version history specific to the Pro edition. |
chronolith-pro/CONTRIBUTING.md |
Contribution rules specific to the Pro package and workflow. |
chronolith-pro/PROJECT_CONTEXT.md |
Pro edition mission, boundaries, and operating assumptions. |
chronolith-pro/ROADMAP.md |
Planned feature trajectory and future development priorities. |
chronolith-pro/MAINTAINERS.md |
Maintainer responsibilities and project stewardship notes. |
chronolith-pro/SECURITY.md |
Security expectations and safeguards for the Pro edition. |
chronolith-pro/TROUBLESHOOTING.md |
Problem-solving guide for common runtime and workflow issues. |
chronolith-pro/USE_CASES.md |
Representative workflows and intended real-world usage scenarios. |
chronolith-pro/AGENT_START.md |
Agent/session bootstrap guidance for Pro operators. |
chronolith-pro/examples/README.md |
Example pack overview for Pro usage patterns. |
chronolith-pro/examples/sample_project/README.md |
Walkthrough for the sample Pro project. |
chronolith-pro/OTHER_LANGUAGES/README_*.md |
Translated Pro README set. |
chronolith-pro/OTHER_LANGUAGES/*/README.md |
Language-scoped translated Pro overviews. |
chronolith-pro/OTHER_LANGUAGES/*/TROUBLESHOOTING.md |
Language-scoped translated troubleshooting guides. |
chronolith-pro/OTHER_LANGUAGES/*/USE_CASES.md |
Language-scoped translated use-case guides. |
chronolith-pro/chronolith_pro/chronolith/README.md |
Packaged README embedded in the Pro Python distribution. |
| Document | Purpose |
|---|---|
chronolith-omega/README.md |
Main guide for the Omega edition. |
chronolith-omega/PROJECT_CONTEXT.md |
Omega edition context and high-level operating frame. |
chronolith-omega/OTHER_LANGUAGES/README_*.md |
Translated Omega README set. |
chronolith-omega/chronolith_omega/chronolith/README.md |
Packaged README embedded in the Omega Python distribution. |
| Document | Purpose |
|---|---|
examples/example-project/README.md |
Example project showing how Chronolith is applied in practice. |
examples/example-project/DAILY_HANDOFF_SCENARIO.md |
Example of session-to-session chronolith handoff. |
examples/demo-folder/README.md |
Demo folder notes for lightweight demonstration material. |
| Document | Purpose |
|---|---|
.chronolith/DECISIONS_LOG.md |
Local architectural decision ledger for this repo. |
.chronolith/PROJECT_DNA.md |
Local DNA record for project identity. |
chronolith-pro/.chronolith/README.md |
Overview of the Pro chronolith core internals. |
chronolith-pro/.chronolith/AGENT_ACTIVATION_PROTOCOL.md |
Pro agent activation contract. |
chronolith-pro/.chronolith/BOOT_SEQUENCE.md |
Boot process for Chronolith initialization. |
chronolith-pro/.chronolith/BYPASS_LOG.md |
Record of bypasses, exceptions, or chronolith-critical deviations. |
chronolith-pro/.chronolith/CONTEXT_CHRONOLITH.md |
Chronolith-memory protocol for Pro. |
chronolith-pro/.chronolith/DECISIONS_LOG.md |
Pro-specific decision ledger. |
chronolith-pro/.chronolith/LIVE_HANDOFF.md |
Pro live handoff instructions. |
chronolith-pro/.chronolith/TIMELINE.md |
Pro chronolith timeline. |
chronolith-pro/.chronolith/templates/README.md |
Template overview for Chronolith scaffolds. |
chronolith-pro/.chronolith/templates/external_docs/README.md |
External-document template usage notes. |
chronolith-pro/.chronolith/registry/README.md |
Registry notes for internal chronolith bookkeeping. |
Current release: 3.2.2, live on PyPI for all four packages.
- https://pypi.org/project/chronolith/
- https://pypi.org/project/chronolith-lite/
- https://pypi.org/project/chronolith-pro/
- https://pypi.org/project/chronolith-omega/
Licensed under either of MIT or Apache License 2.0 at your option. Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this work shall be dual licensed as above, without any additional terms or conditions.
