Release list

Chronolith 3.2.2 — What An Agent Found Using It Latest

Latest

SteveBlackbeard released this 21 Jul 14:13

v3.2.2

e3da09d

Chronolith 3.2.2 — What An Agent Found Using It

An agent used Chronolith from end to end while shipping another project, and
filed a reproduction for every defect it hit. This release is those fixes. The
theme is uncomfortable and worth stating plainly: the tool did not enforce the
doctrine it printed.

pip install --upgrade chronolith-pro

The one that mattered

check exited 0 on detected drift, by default.

With stock defaults — not permissive, no --strict — the old logic printed
[!] DNA DRIFT DETECTED and then fell through to exit 0. A CI job running plain
chronolith-pro check passed on a drifting repository. That is the exact
failure a fail-closed governance tool exists to prevent, and the opposite of the
module's own Law 3.

It was nearly invisible to a human — who sees the red text and reacts — and
catastrophic to an agent, who reads the exit code and proceeds. That distinction
is the lesson of the whole release.

check now fails closed by default. CHRONOLITH_MODE=permissive is the only way
past an inconsistency, and it says so.

The rest, all with reproductions

Severity is respected. Any finding was collapsed into a security failure,
so check halted on the very sovereign keys sovereign-init creates — it told
you to make a key, then failed you for having one. Only a tracked key in the
index (a real leak) is a failure now; an untracked local key is a warning.
The pre-push hook is portable. It wrote a bare python and a hardcoded
absolute site-packages path; under git-bash on Windows python is often not on
PATH, so the hook died with "command not found" and blocked every push. It now
invokes sys.executable -m the module.
The status panel cannot lie. It printed Status: Status: OK above the
fail-closed check, announcing OK on a run about to halt. The verdict is
computed first; the panel says OK or INCONSISTENT to match the exit code.
.chronolithignore. A repo that vendors backup trees had them hashed as
governed content, so an edit inside a dead copy triggered drift on the live
project. One fnmatch glob per line, the .gitignore syntax you already know.
--quiet on check, for clean CI and agent output. The banner and spinner
go; the status panel and exit code stay, because those are the contract.
init is honest on re-run. A second init created nothing and printed
nothing, reading as a successful re-crystallization. It now says the core is
already present and points at check --accept.
Docs reference real commands. HOW_TO_USE_IT.md told you to run
chronolith status --fix. There is no status command and no --fix. Doc
drift in a drift-detection tool is the one it can least afford.
Descriptions say what each package does — not "industrial-grade" or
"Enterprise Oracle" or "Shannon Entropy physics" (it computes an entropy
metric). A tool whose verify reports what it did not prove should not
overclaim in its own summary.

Every fix ships with a regression test that reproduces the original defect,
including the exit-0 reproduction.

First release published through Trusted Publishing across all four packages

chronolith, chronolith-lite, chronolith-pro and chronolith-omega are
built and published by this repository's workflow. PyPI holds an attestation
naming the repo and workflow for each file — you can confirm where the wheel came
from without trusting the author, which is the claim the tool makes about
everything else.

Full detail: CHANGELOG.md

Assets 2

3.2.1

SteveBlackbeard released this 19 Jul 07:09

v3.2.1

50aa7f8

Publish release v3.2.1

Assets 2

v3.0.3 - Governed Release Candidate

SteveBlackbeard released this 18 Jun 22:38

v3.0.3

dc0e006

v3.0.3 - Governed Release Candidate

Continuity Legacy v3.0.3 turns the Python framework into a governed continuity platform: explicit rulebook, feature registry, live handoff, golden baseline verification, health guard, clean package metadata, and clean separation from Continuity Conekta.

Highlights

Prepared all four package lines for 3.0.3: legacy, lite, pro, and omega.
Added governed release notes with the canonical Ethernium banner.
Fixed package metadata for continuity-tokens by declaring the required cryptography dependency.
Added KO and AR documentation entry points.
Hardened health_guard.py and autophagy_report.py so smoke-test virtual environments do not pollute governance checks.
Removed historical tracked dist artifacts from Git; local release artifacts are attached here instead.
Kept Continuity Conekta external and AgentOps incubated/non-blocking.

Verified

python scripts\golden_baseline.py verify
python scripts\health_guard.py --strict
python scripts\autophagy_report.py
pytest -q -> 28 passed
python -m twine check dist\* continuity-lite\dist\* continuity-pro\dist\* continuity-omega\dist\*
Wheel smoke test from a clean venv: imports and CLIs ok.

PyPI

This GitHub release does not publish to PyPI. PyPI upload should use version 3.0.3 only when explicitly approved.

Assets 10

v3.0.2 - HOTFIX

SteveBlackbeard released this 12 Apr 08:44

pypi-v3.0.2

627f5eb

Languages

"The AI doesn't just remember; it reflects."

🩹 v3.0.2: HOTFIX — CLI STABILITY & TOKENATOR REPAIR

This hotfix locks CLI stability on Windows and repairs the Tokenator entrypoint so all packages run cleanly out of the box.

Fixes (v3.0.2):

CLI Unicode Stability: Standardized console output for Windows cp1252 environments to prevent --help crashes.
Tokenator Entrypoint: Restored continuity-tokens to the real module (tokenator) so it executes correctly.
Typer Dependency Cleanup: Removed invalid typer[all] extra across packages.
Package Refresh: Rebuilt and validated all four wheels (legacy, lite, pro, omega).

🌌 v3.0.1: THE GREAT CONJUNCTION (MODULAR)

This landmark release marks the transition of Continuity Legacy into its final, modular industrial form. All core protocols have been decentralized and projected onto PyPI for global synchronization.

🧩 Key Innovations (v3.0.1):

Modular Isolation: The monolithic core has been split into 4 independent distribution nodes: ethernium-continuity-legacy, -lite, -pro, and -omega.
Functional Nexus Dashboard: The glassmorphic HUD is now active. You can command DNA Synthesis and Industrial Audits directly from the visual interface.
PyPI Synchronization: Official branding is now enforced across the global package registry under the ethernium- prefix.
Hardened Handshake: CI/CD pipelines now use a direct API-Token handshake to bypass security-identity drift during publication.

🏛️ v2.11.0: THE CINEMATIC SINGULARITY (NEXUS)

Welcome to the NEXUS Phase. This version (v2.11.0) was the foundation of the 3D aesthetic era...

Key Innovations:

The Cinematic Mirror: A professional B&W Dashboard powered by Three.js (R3F) and VFX Shaders, visualizing the Merkle Tree as a living core.
Information Physics (Shannon Entropy): Real-time auditing of "Logical Purity" (H < 5.2). If the code drifts, the entropy rises; NEXUS detects it.
SDK (Signature-Derived Key) Sealing: Cryptographic identity integration. Your private key (ED25519) is now the only way to unlock industrial secrets.
Ghost Mode: Symbolic logic is now invisible to unauthorized eyes, protecting intellectual property through cryptographic obfuscation.

Choose Your Edition

Minimalist local sync with DNA Synthesis for zero-loss handoffs.

Industrial-grade border guard with security audits and global synchronization.

The NEXUS Core: Advanced RAG, 3D mapping, and hardened encryption.

Multidisciplinary Reach

NEXUS is no longer just for software. It is a universal framework for:

Medicine: Protecting the lineage of clinical data.
Psychology: Mapping cognitive behavioral patterns.
Economics: Auditing algorithmic financial flows.
Worldbuilding: Synchronizing the "Truth" of fictional universes.

Continuity Legacy: Protecting the logical lineage of your software.

Assets 2

v3.0.1 - THE GREAT CONJUNCTION (MODULAR)

SteveBlackbeard released this 12 Apr 07:25

pypi-v3.0.1

03f7eb3