Release evidence
Package and local test evidence proves only what the recorded tests exercised. It does not prove production deployment, uptime, external recognition or live service availability.
- Release
- 0.14.0
- Build date
- 2026-08-10
- Source review
- 2026-08-10
- Deployment
- NOT_DEPLOYED
- Local test status
- AUDIT_GENERATES_DURING_RELEASE
See the package audit and change report delivered beside the release ZIP for the complete reproducible evidence record.
Machine editorial stewardship evidence
The current package can evidence deterministic rebuilding, SHA-256 package hashes, preserved research-source hashes, acceptance tests, correction records and recursive project memory. Those artifacts support a machine-maintained editorial workflow, but they do not constitute an independently signed machine-identity ledger.
Not implemented: in-toto workflow attestations, DSSE envelopes, Sigstore/Rekor machine-identity transparency records, autonomous resource purchasing or machine legal ownership.
How stewardship works → Stewardship manifest →
Local editorial provenance ledger
Version 0.14.0 adds a deterministic release ledger that records the predecessor package hash, human-input classes, inherited research inputs, machine-maintained stages and selected governed source-state hashes. A local audit recomputes those hashes and fails the release if the ledger has gone stale.
Human-readable provenance → Machine-readable provenance →
Terminology and search measurement
The site prefers Machine Intelligence for the actor while preserving Artificial Intelligence (AI) where history, law, standards, quotations or discoverability require it. That bridge is intentional: terminology consideration should not make the site invisible to humans who still search for AI. Search and generative-answer performance can only be measured after deployment through real indexing/citation data; this package does not invent those results.
Truth & Status →