-
Notifications
You must be signed in to change notification settings - Fork 0
Core Concepts
PIC uses a small set of operational concepts. These terms are the most important for first-time users and agents.
A candidate is material that may be useful but is not verified yet.
Examples include an LLM answer, an agent message, a repository finding, a web excerpt, a test claim, or a proposed reusable abstraction.
PIC treats candidates as data to inspect, not as facts to trust.
Evidence is something a checker can inspect.
Useful evidence may include hashes, schemas, signed attestations, verifier reports, test logs, replayable artifacts, provenance records, or typed trace records.
Metadata such as "passed", "approved", "important", or "high priority" is not evidence by itself.
A proof obligation is a check that must still be completed.
PIC records obligations instead of hiding them. An obligation can be routed to a verifier, deferred, or preserved as residual work.
A residual ledger is a structured list of unresolved debt.
Residuals can include missing evidence, stale data, external-domain limits, verifier backlog, unsafe packet status, resource mismatch, or unverified physical assumptions.
Keeping residuals visible is safer than rewriting uncertainty as success.
A verifier route is a named path for checking a specific kind of obligation.
It might point to a schema check, evidence verifier, identity check, trace checker, snapshot verifier, domain adapter, or runtime route.
A route is not evidence by itself. It is only the path where evidence can be checked.
Reusable abstraction capital is a scoped reusable pattern, trace, packet, or idea that can reduce future work.
PIC's ALT layer checks whether reuse is still beneficial after validation, transport, lifecycle, hazard, maintenance, and residual costs.
Raw agent output, web content, or trace material is only a candidate until these checks pass.
settled=true means the relevant scoped finite obligations were discharged.
settled=false is common and useful. It means the report preserved unresolved work instead of pretending the work is complete.
workflow_usable=true means the compact agent workflow can guide next safe actions.
operationally_usable=true means the report can guide routing under the selected profile.
It does not mean every claim is true, every obligation is settled, or every action is safe to execute.
Live candidate intake means PIC can fetch or read an explicitly supplied source under byte limits, content-type checks, private-network rejection, provenance recording, and residual preservation.
Live intake is not background crawling, general browsing, shell execution, or automatic trust. The result is still a candidate until downstream checks accept it.
- 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