Skip to content

collective-capability-runtime v1.2.0

Choose a tag to compare

View all tags
@kadubon kadubon released this 01 Jul 11:31
v1.2.0
7e68a14

What changed

CCR v1.2.0 adds a TRC operation preflight path for agents consuming PIC trace-check or operation-gate reports.

New commands:

ccr operation preflight --trace pic_report.json --provider http --config provider.json --json
ccr operation dispatch --plan trc_operation_plan.json --provider http --config provider.json --execute --json
ccr operation observe --dispatch-report dispatch.json --observation observation.json --json

Agent-readable safety model

  • CCR rechecks authority freshness and validity-domain scope before marking a plan ready.
  • Provider dispatch requires a ready PIC/CCR plan, explicit provider config, allow_execute=true, a non-dry-run side-effect policy, and an operator approval reference.
  • Fixture benchmark traces remain blocked and non-executable.
  • Preflight is not dispatch. Dispatch is not physical outcome proof. Observation evidence still requires verifier acceptance before outcome claims.

Interop

CCR now accepts pic.trc_trace_report.v1 and pic.trc_operation_gate_report.v1, and publishes schemas for ccr.trc_operation_preflight.v1 and ccr.trc_operation_observation.v1.

Validation

Local and GitHub CI passed: format, lint, mypy, compileall, pytest, schema validation, phase-form smoke, repository audit, build, release audit, twine check, Bandit, and pip-audit.

Assets 2
Loading