Skip to content

CCR v1.6.0 - Distributed Collective Runtime

Latest
Latest

Choose a tag to compare

View all tags
@kadubon kadubon released this 10 Jul 01:26
v1.6.0
22f855b
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

CCR v1.6.0 helps several agents turn separate proposals, evidence, reviews, and unfinished work into reusable checked results. It supports the project vision of faster protocol-relative ASI-proxy formation by measuring verified progress under equal resource limits. It does not claim real ASI.

Start here

python -m pip install --upgrade collective-capability-runtime==1.6.0
ccr --root ccr-runtime asi quickstart --profile development --json
ccr --root ccr-runtime mission next --mission mission:quickstart --compact --json
ccr --root ccr-runtime workbench report --mission mission:quickstart --format markdown --out CCR_WORKBENCH.md

What is new

  • Independent agent workcells: proposals remain separate until reveal, then move through critique, revision, verification, and integration. Repeated answers from the same model, tool, or source do not count as independent agreement.
  • Recoverable task work: SQLite leases now use transactions, heartbeats, fencing tokens, idempotent completion, and an outbox. A stopped or stale worker cannot overwrite a newer lease.
  • Verified residual resolution: unresolved work stays visible until a repair artifact and an independent verifier agree on the same digest.
  • Distributed runtime: the optional distributed extra adds PostgreSQL 16+ workers, a versioned API, OIDC + DPoP authentication, and at-least-once delivery with idempotent commits.
  • Fairer measurement: experiments require a declared task, evaluator, resource envelope, seed, tool/model version, outcome schema, and preregistered fixed horizon or confidence sequence.
  • Safer external operations: approvals bind the plan, provider, arguments, scope, resources, expiry, nonce, and use count. HTTPS dispatch blocks redirects and private-address targets. Signed scoped observations are required for physical_outcome_verified.
  • Clearer onboarding: the README, documentation index, agent manifest, command map, security checklist, and executable collective-runtime fixture now follow task-oriented paths.
  • PIC 1.0 interoperability: strict booleans, report digests, residual parity, and safe-command hints are checked without executing imported commands.

Safety boundaries

accepted is finite checker acceptance, not settlement. Unknown measurements remain unknown. physical_outcome_proven is a deprecated compatibility field and remains false. CCR does not grant legal authority, update model weights, prove consciousness, or prove real ASI.

Compatibility

The v1 CLI and registered JSON interfaces remain compatible; new fields are additive. Side-effecting provider execution must use the operation approval and dispatch path. PostgreSQL, API/authentication, and telemetry dependencies remain optional.

Validation

The release passed full tests, 90% safety-critical coverage, PIC 1.0 checks, PostgreSQL 100-worker leasing, Python 3.10-3.14, Linux/Windows/macOS smoke, schema registry integrity, repository/release audits, Bandit, dependency audit, Twine, and clean-wheel installation.

Assets 2
Loading