-
Notifications
You must be signed in to change notification settings - Fork 0
Core Concepts
This page explains the main ideas without assuming the theory papers.
Candidate work is useful but not finished.
An agent answer, packet file, runtime report, or external note can be a candidate. Candidate work may help the next step, but it must not be silently promoted to completed work.
accepted=true means the command accepted the finite JSON envelope or input for that route.
It does not mean the claim is true. It does not grant execution authority.
workflow_usable=true means the report can guide the next step.
It is not the same as settlement.
operationally_usable=true means the report can guide routing under the selected profile.
For stricter profiles, identity, route, and verifier requirements matter more.
settled=true is strict. It should only appear when scoped finite obligations have actually been discharged.
Most useful reports are not settled.
A residual ledger records unfinished work, uncertainty, missing evidence, or known limits.
Do not erase residuals. They are the main safety signal.
Missing obligations are the specific checks still needed.
Examples:
- identity context is missing;
- verifier route is missing;
- external evidence is not checked;
- baseline safety is unresolved.
safe_commands are suggestions or examples. They are not executed automatically.
A packet is a structured data envelope for candidate work.
Packet inspection keeps content inert and visible. It does not promote a packet to settled truth.
CCR interop is the v0.6.0 data boundary between PIC-TS and Collective Capability Runtime.
PIC-TS can emit ccr.task.v0.1 and ccr.residual.v0.1 JSONL records. Those records are candidate scheduling inputs. They do not execute commands and do not settle downstream runtime work.
TRC operation readiness is a finite check over a declared trace normal form.
operation_ready=true means the trace includes scoped authority, resources, rollback or escrow, witnesses, schedule, and tolerance data. It does not mean the operation was executed or that the external result is true.
- 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