CCR Interop

CCR Interop

CCR means Collective Capability Runtime. It is a companion runtime for coordinating many agents through tasks, leases, blackboard events, packet distillation, residual tracking, foundry allocation, operation preflight, and release audits.

PIC emits CCR-facing JSON and JSONL so a scheduler can receive finite work without losing the safety boundary.

Short Version

Use PIC to check and route candidate work. Use CCR to schedule, lease, store, and audit multi-agent work. Do not treat a PIC record as automatic CCR settlement.

PIC phase plan, phase gap, TRC gate, MCP/A2A report, or CARA report
-> CCR task JSONL, residual JSONL, import report, or foundry allocation input
-> CCR import, lease, schedule, allocate, and preserve residuals
-> later PIC or CCR checks
-> no hidden promotion to settlement

Basic Handoff Commands

pic phase plan --compact --emit ccr-tasks --output tasks.jsonl
pic phase gap --compact --emit ccr-residuals --output residuals.jsonl
ccr task import --file tasks.jsonl --provider pic --json
ccr residual import --file residuals.jsonl --provider pic --json
ccr phase report --json

ccr.task.v0.1 records are candidate tasks. ccr.residual.v0.1 records are unresolved work that should stay visible.

PIC-emitted tasks keep constraints.allowed_commands=[]. Command hints under extensions.x_pic_safe_command_hints are review data, not execution grants.

v0.8.0 CARA And Foundry Roundtrip

For ASI-proxy/CARA loops, PIC can emit target checks, baseline checks, runtime capital witnesses, MCP/A2A reports, SQOT protocol diagnostics, BIT MEC frontier reports, and TRC operation-gate reports. CCR imports them as candidate evidence and residual work.

PIC can emit pic.phase_response_control_step.v1. CCR consumes that report with:

ccr foundry allocate --strategy phase-response --response-report examples/asi_proxy_acceleration_bundle/phase_response_control_step.accepted.json --json
ccr foundry simulate-allocation --cuts examples/asi_proxy_acceleration_bundle/foundry_cuts.example.json --budget examples/asi_proxy_acceleration_bundle/foundry_budget.example.json --json

The allocation is advisory. It does not promote settlement, call providers, mutate repositories, or execute physical actions.

TRC Operation Preflight

PIC reports operation_ready, provider_dispatch_ready, and physical_dispatch_ready separately. CCR still requires matching preflight, explicit operator approval, provider policy, authority, hazard, rollback, lifecycle, logging, and observation verifier checks before any provider dispatch path can be considered.

Safe Import Boundary

PIC output is provider evidence for CCR. It is not:

• permission to run a shell command;
• permission to call a provider;
• settlement of a CCR task;
• proof of physical success;
• proof of real ASI;
• permission to discard residuals.

CCR must still apply its own authority, provider, lease, witness, baseline, and settlement policies.

Search Terms

CCR interop, PIC to CCR, Collective Capability Runtime, CCR task JSONL, CCR residual JSONL, CCR foundry allocate, phase-response allocation, foundry simulate-allocation, ASI-proxy acceleration bundle, CARA report, runtime capital witness, operation preflight, task leasing, residual preservation, provider evidence, pic phase plan --emit ccr-tasks, pic phase gap --emit ccr-residuals, ccr foundry allocate --strategy phase-response, candidate-only until checked.