-
Notifications
You must be signed in to change notification settings - Fork 0
Glossary
The finite envelope passed acceptance checks. This is not permission to execute.
The beginner-facing and agent-facing command path. pic agent check --compact returns a compact JSON report with practical fields such as accepted, workflow_usable, settled, unresolved obligations, residual summary, next safe actions, and schema references.
A recommended finite next task. It should be reviewed before execution.
A v0.4.4 report that checks whether the core agent workflow is blocked by adoption state, approval state, shell execution, or missing compact mode. It is diagnostic only.
The optional pip extra for connector, identity, and service-layer dependencies: percolation-inversion-compiler[agent-full].
Abstraction Liquidity Theory. In PIC, this checks whether a candidate abstraction can become scoped reusable capital after costs, transport, evidence, lifecycle, and hazards are counted.
A protocol-relative proxy target for collective capability progress. It is not a claim of real ASI.
Bottleneck Inversion Theory. In PIC, this helps identify missing witnesses or finite checks that would unlock useful next work.
A structured candidate with provenance, evidence references, receiver context, route requirements, and residual charges. Plain-language equivalent: a checked reusable work item candidate.
A pip-safe v0.4.4 audit of whether the installed package exposes the expected canonical implementation surface. It is not proof of real-world truth and not settlement.
A finite, protocol-relative report over a fixed population, packet registry, queue state, hazards, thresholds, and baseline.
Executable Capability Percolation Theory. In PIC, this models how verified capability packets can move through a declared agent population and become useful paths or closures.
A concrete artifact or reference that a verifier can inspect. Metadata alone is not evidence.
A requirement that depends on a domain verifier, physical evidence, simulator result, oracle, policy judgment, or other external check.
Bounded intake from an explicitly supplied HTTP, feed, repository, or connector source. In v0.4.4 it is live-capable by default for explicit sources, but output remains candidate material.
A check that can be performed on bounded records, schemas, hashes, routes, traces, signatures, ledgers, or supplied evidence.
The report can guide routing under the selected profile.
The compact agent workflow can guide next safe actions even when deeper runtime settlement is still incomplete.
Moving a packet from candidate status to verified packet capital for a declared scope.
A check that must still be discharged before a claim can be considered settled in its declared scope.
Information about where a candidate came from, often including hashes, source records, or route context.
A structured list of unresolved evidence, assumptions, limits, debt, hazards, or external obligations. Plain-language equivalent: an unresolved-work ledger.
A request to run a verifier route. It is not permission to execute arbitrary shell, network, or repository actions.
Command-shaped recommendations or hints emitted for inspection. PIC does not execute them.
The JSON Schema definition that other languages and runtimes should use when implementing compatible PIC reports.
An optional extra report for handoff, packet exchange, dashboards, benchmark diagnostics, or observation. A sidecar is not a gate and does not make settled=true.
A checked relation between records, such as theorem-to-code, code-to-test, execution-path, rollback-support, or liquidity-transfer.
All scoped finite obligations are discharged. Many useful reports remain settled=false.
Salience-Queue Occupation Theory. In PIC, this is a finite task scheduler that preserves diagnostic reserve and residual visibility.
Protocol-relative checks that reject duplicate identities, duplicate keys, revoked credentials, overrepresentation, or clone fanout according to the selected profile.
Typed Reality Compilation. In PIC, this checks typed trace records, resource ledgers, lifecycle constraints, and external proof boundaries for process claims.
- Home
- Getting Started
- Acceleration Measurement
- Operation Guide
- AFST Satisfaction Flux
- Python TypeScript Compatibility
- Security
- Quickstart
- ASI Proxy Loop v0.9
- Token Reports and Agent Loop
- ASI Proxy Acceleration
- CCR Interop
- MCP And A2A Safety
- Operation Gate
- Phase Ecology Lab
- Related OSS
- Use Cases
- Live Intake and Agent Messages
- Core Concepts
- Concepts in Plain Language
- Agent Guide
- Diagnostics and Agent Autonomy
- What PIC Does Not Do
- Safety and Limits
- Theory Map
- CLI Recipes
- 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