Logs are not proof.
As AI systems and autonomous infrastructure begin operating at machine speed, traditional audit systems become insufficient for:
- regulators
- insurers
- courts
- counterparties
- enterprise governance
- operational liability
Internal logs are operator-controlled artifacts.
CVS creates independent cryptographic evidence of what actually occurred during execution.
Not screenshots. Not operator testimony. Not compliance narratives. Not mutable audit trails.
Cryptographic evidence generated outside the production system itself.
Modern systems increasingly operate faster than humans can supervise.
AI agents are beginning to:
- execute transactions
- coordinate systems
- operate infrastructure
- trigger irreversible actions
- manage workflows autonomously
- interact across machine-to-machine environments
When failures occur, organizations need to answer:
- What actually happened?
- What executed?
- In what order?
- Under which constraints?
- Was evidence modified?
- Can an external party independently verify it?
Traditional logs fail because they:
- are internally controlled
- can be modified
- lack independent verification
- do not preserve trust boundaries
- are difficult to validate externally
- become disputed after failure
CVS exists because machine-speed systems require independent evidence generation.
CVS is an independent witness architecture.
It operates alongside execution systems without interrupting execution.
CVS:
- observes events out-of-band
- creates cryptographic evidence objects
- preserves ordering and detectability of gaps
- anchors proof externally
- enables independent verification
The sidecar does not:
- execute business logic
- enforce policy
- make decisions
- approve actions
- govern execution
It witnesses.
Most enterprise audit systems were designed for:
- human-operated workflows
- delayed review cycles
- centralized trust assumptions
- post-event analysis
- cooperative disclosure environments
Machine-speed systems invalidate those assumptions.
At scale:
- execution outruns human observation
- logs become operator assertions
- disputes emerge after irreversible actions
- liability attaches retroactively
- internal evidence loses independence
Post-hoc audit is no longer sufficient.
Independent evidence becomes necessary.
Without independent evidence systems:
- autonomous systems become difficult to insure
- enterprises cannot independently prove execution history
- regulators cannot reliably validate claims
- counterparties lose trust in internal records
- forensic reconstruction becomes economically expensive
- attribution collapses under dispute
CVS exists to establish defensible evidence after execution occurs.
A CVS-conforming implementation must satisfy these properties:
| Property | Requirement |
|---|---|
| Fail-Open | Evidence systems must never block execution |
| Witness-Only | Observation without enforcement authority |
| Independent Verification | External verification without trusting operators |
| Selective Disclosure | Minimal bounded evidence release |
| Detectable Gaps | Missing evidence must remain observable |
| Immutable Ordering | Evidence chains preserve sequence integrity |
| Authority Separation | Witness layer cannot control execution |
These properties are non-negotiable.
Production System
↓
Execution Event
↓
[ CVS Witness Layer ]
↓
Evidence Object
↓
Hash Chain / Merkle Structure
↓
External Ledger Anchor
↓
Independent Verification
CVS operates outside the execution path.
Execution continues whether CVS is present or absent.
This separation is mandatory.
Immutable Evidence Objects chained cryptographically to preserve:
- integrity
- ordering
- detectability of gaps
Selective evidence disclosure without over-exposure.
Not an access-control system.
Public cryptographic anchoring layer providing:
- timestamping
- existence proof
- independent verification
The ledger does not govern execution.
Funding and operational mechanisms supporting:
- settlement
- infrastructure
- operational continuity
Commercial incentives must not influence evidence generation.
512 governs execution.
CVS proves what occurred.
512 decides. CVS witnesses.
512 and CVS are architecturally independent.
CVS may operate without 512.
Systems satisfying 512 properties may use witness architectures other than CVS.
| Audience | Start Here |
|---|---|
| Executives / Boards | public/EXECUTIVE_SUMMARY.md |
| CFOs / Risk Committees | public/CFO_BRIEF.md |
| Regulators / Auditors | public/REGULATOR_NOTE.md |
| Technology Vendors | public/VENDOR_SUPPLY_NOTE.md |
| Government / Public Sector | public/PUBLIC_SERVICE_GOVERNMENT_NOTE.md |
| Engineers / Architects | 00_INTENT/ |
Read:
public/EXECUTIVE_SUMMARY.md
Read:
VERIFICATION_PROTOCOL.mdCONFORMANCE.md
Read:
/08_CANON/CVS_ARCHITECTURE_v3.0.md/08_CANON/CVS_IMPLEMENTATION_v3.0.md
Read:
INTEROPERABILITY.mdANTI_DRIFT.md
The canonical CVS specification is defined exclusively by:
/08_CANON/CVS_ARCHITECTURE_v{M}.{m}.md/08_CANON/CVS_IMPLEMENTATION_v{M}.{m}.md
Cryptographic fingerprints are recorded in:
/08_CANON/CANON_HASHES.md
Canonical versions are immutable.
Subsequent revisions must increment version numbers.
CVS applies wherever:
- execution cannot be interrupted
- liability emerges after execution
- logs are insufficient
- independent proof is required
- disputes occur after the fact
Illustrative sectors include:
- AI systems
- finance
- supply chains
- media systems
- industrial infrastructure
- public sector systems
The following documents are normative:
CONFORMANCE.mdANTI_DRIFT.mdVERIFICATION_PROTOCOL.mdINTEROPERABILITY.md
Normative documents use:
- MUST
- MUST NOT
language.
The following documents are informational:
ADOPTION.mdCRYPTOGRAPHY.md
These documents are explanatory only.
This repository also defines CVS-EBI.
CVS-EBI specifies:
- deterministic evidence emission semantics
- Evidence Object structure
- witness runtime boundaries
- replay validation flows
- independent verification semantics
- fail-open evidence behavior
CVS-EBI defines interface semantics only.
It does not alter the canonical CVS architecture.
Directories:
/evidence-spec//witness-runtime//proof-validation//diagrams//docs/
Canonical /08_CANON/ documents always take precedence.
This repository defines technical architecture only.
It does not:
- provide legal advice
- guarantee evidentiary admissibility
- replace due process
- replace regulatory authority
Its purpose is to strengthen evidence integrity and independent verification.
This repository is intentionally complete.
Future changes should be:
- additive
- restrained
- justified by operational failure modes
Complexity is not a feature.
Licensed under the Apache License, Version 2.0.
See:
LICENSELEGAL_NOTICE.md
CVS defines an independent cryptographic witness architecture that creates externally verifiable evidence of machine-speed execution without interrupting execution itself.