-
Notifications
You must be signed in to change notification settings - Fork 0
CCR Interop
CCR means Collective Capability Runtime. PIC-TS emits CCR-oriented JSON and JSONL from Node.js runtimes while preserving the PIC safety boundary.
These records are data-only handoff material. They do not grant shell, network, provider, repository, or physical authority.
npx pic-ts phase plan --compact --emit ccr-tasks --output tasks.jsonl
npx pic-ts phase gap --compact --emit ccr-residuals --output residuals.jsonlTask records use schema_version="ccr.task.v0.1". Residual records use schema_version="ccr.residual.v0.1". Both preserve PIC blockers and keep candidate_only_until_checked=true.
PIC-TS mirrors Python PIC's v0.8 CARA reports and phase-response control-step fixture. CCR can consume the phase-response 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 --jsonThe allocation is advisory. It does not promote settlement, call providers, mutate repositories, or execute physical actions.
npx pic-ts trc trace-normalize --input examples/asi_proxy_benchmark_bundle/trc_agent_trace.json --output trace_nf.json
npx pic-ts trc trace-check --trace trace_nf.json
npx pic-ts trc operation-gate --trace trace_nf.json --provider-profile provider_profile.json
npx pic-ts trc trace-to-packet --trace trace_nf.jsonoperation_ready=true means the trace has explicit authority, resource, rollback, witness, schedule, and tolerance data for the scoped provider handoff. It still reports executed=false and settled=false.
The stricter operation-gate report adds authority freshness, scope, provider dispatch, physical dispatch, MCP, and A2A gates.
import {
ccrResidualsFromPhasePlan,
ccrTasksFromPhasePlan,
phaseResponseControlStep,
traceCheckReport,
traceNormalFormReport,
} from "percolation-inversion-compiler-ts/interop/ccr";Use these helpers when a JavaScript runtime needs to route finite repair work to CCR while preserving residual ledgers.
PIC-TS CCR interop, Node.js CCR task JSONL, npm CCR residual JSONL, Collective Capability Runtime, JavaScript agent runtime, task leasing, residual preservation, phase-response allocation, CCR foundry allocate, provider evidence, pic-ts phase plan --emit ccr-tasks, pic-ts phase gap --emit ccr-residuals, percolation-inversion-compiler-ts/interop/ccr.
- Home
- Quickstart
- Getting Started
- Acceleration Measurement
- Operation Guide
- AFST Satisfaction Flux
- Python TypeScript Compatibility
- Security
- Node Only Agent Loop
- ASI Proxy Loop v0.9
- Token Reports and Agent Loop
- ASI Proxy Acceleration
- CCR Interop
- MCP And A2A Safety
- Operation Gate
- Phase Ecology Lab
- CLI Recipes
- JavaScript SDK
- Diagnostic Commands
- How To Read The JSON
- Agent Guide
- Agent Messages and Packets
- Schemas and Conformance
- Safety and Limits
- Compatibility With Python
- npm Package and Release Checks
- Use Cases
- Core Concepts
- Concepts in Plain Language
- What PIC Does Not Do
- Theory Map
- Glossary
- FAQ
- v1.1 Release Notes
- v0.9.0 Release Notes
- v0.8.0 Release Notes
- v0.7.0 Release Notes
- v0.6.0 Release Notes
- v0.5.0 Release Notes