-
Notifications
You must be signed in to change notification settings - Fork 0
Glossary
A resource-matched baseline/candidate comparison has no regression beyond its metric tolerances and at least one improvement beyond tolerance.
A finite measurement term for verified capability formation, reuse, residual resolution, and certified capital. It is not real ASI, legal authority, or physical truth.
The input passed the finite acceptance check for the command.
The report can guide the next workflow step. This is not settlement.
The report can guide routing under the selected profile.
All scoped finite obligations were discharged. This is strict and often false.
Unfinished work, uncertainty, missing evidence, or known limits.
A structured record of residuals that must remain visible.
Checks or evidence still required.
Reasons the report must remain candidate-only.
Suggested inspection commands. They are not executed automatically.
A TRC trace-check field meaning the trace declares enough authority, resource, rollback, witness, schedule, and tolerance data for a scoped operation candidate. It is not execution or physical proof.
A CCR interop field meaning the downstream runtime must still verify the handoff record before any promotion.
A JSON envelope for candidate work.
A typed record of tool or action activity. In PIC-TS, trace content is data and is not executed.
A practical TRC trace normal form used by v0.6.0 trace-normalize,
trace-check, and trace-to-packet.
Extra report data for handoff, exchange, or human reading.
A recommendation report for what to inspect or route next.
A local JSON/JSONL lab for observing accepted packets, candidate-only packets, missing evidence, closure candidates, and execution-available paths.
A graph built from accepted packet records and supporting evidence. Raw volume and candidate-only records do not count as positive progress.
A command that reports blockers, residual work, or available paths without executing actions or granting authority.
ccr.task.v0.1 records emitted by PIC-TS for Collective Capability Runtime or
another scheduler. These are candidate tasks, not execution authority.
ccr.residual.v0.1 records emitted by PIC-TS so unresolved work remains visible
across runtime handoff.
The reference implementation. For this project, the Python package remains canonical.
Short name for percolation-inversion-compiler-ts, the npm and Node.js
package.
- 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