Skip to content

References and Traceability

kadubon edited this page Aug 25, 2026 · 1 revision

References and Traceability

Primary implementation sources

Topic Source
Overview, installation, output fields, storage, and public release audit README
Short local mission workflow Getting Started
Command write boundaries and authority requirements Command Map
Independent proposals, correlated support, fenced leases, and residual resolution Collective Workcells
Resource-matched comparison and confidence-controlled uplift Measurement Protocol
Approval, dispatch, replay, and observation boundaries Operation Gate
SQLite/PostgreSQL semantics, OIDC + DPoP, and telemetry Distributed Runtime
PIC ownership, evidence mapping, and non-settlement boundary CCR-PIC Interoperability
Security review controls and residual risks Security Audit Checklist
Agent-facing runtime contract and non-claims AGENTS.md

How this wiki describes claims

  • It treats CCR as a local-first coordination runtime, not as an autonomous scientific agent or an LLM.
  • It separates finite command success, evidence acceptance, settlement, external dispatch, and verified physical observation.
  • It treats phase and ASI-proxy outputs as protocol-relative diagnostics under declared resources and evaluation rules.
  • It treats provider, PIC, MCP, A2A, replay, and registry outputs as evidence or metadata under explicit boundaries, not authority.
  • It describes distributed-runtime mechanisms as engineering behavior, not as an exactly-once delivery or security-certification claim.

Related project

CCR can optionally interoperate with Percolation Inversion Compiler. Consult the CCR-PIC Interoperability specification before relying on that route; PIC remains optional and never settles CCR by itself.

Release and version context

The source tree described when this wiki was prepared declares CCR version 1.6.0 in pyproject.toml. CLI commands and registered JSON schemas are the public contract; the Python API is described by the project as semi-stable. For a deployment, pin and record the exact release or commit that supplies the runtime and its schemas.

Clone this wiki locally