-
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 has at least one improvement beyond tolerance. This is a finite protocol result, not proof of real ASI.
A measurement term for verified capability formation, reuse, residual resolution, and certified capital under matched resources and observations. It does not mean real ASI, consciousness, legal authority, or physical truth.
The finite report envelope passed checks. This is not permission to execute.
The beginner-facing and agent-facing command path. pic agent check --compact returns a short JSON report with fields such as accepted, workflow_usable, settled, unresolved obligations, residual summary, next safe actions, and schema references.
Abstraction Liquidity Theory. In PIC, ALT checks whether a candidate abstraction can become scoped reusable capital after cost, transport, root, telemetry, lifecycle, and hazard checks are counted.
Diagnostics that ask whether ALT abstraction value can support ECPT packet paths or receiver use. ALT lift is diagnostic-only unless a narrower verifier contract settles a smaller claim.
A protocol-relative proxy target for collective capability progress. It is not a claim of real ASI.
Bottleneck Inversion Theory. In PIC, BIT helps identify missing witnesses, route checks, or finite evidence that would unlock useful next work.
Material that may be useful but is not verified yet. Examples include an agent answer, repository finding, web excerpt, message, packet, trace, or proposed abstraction.
A structured candidate with provenance, evidence references, receiver context, route requirements, and residual charges. Plain-language equivalent: a reusable work item candidate.
A pip-safe audit of whether the installed package exposes the expected implementation surface. It is not proof of real-world truth and not settlement.
A diagnostic condition where packets appear to support each other in a useful loop. Closure candidates still need evidence, route, authority, rollback, and residual checks.
Output that helps inspection or routing but does not execute actions, grant authority, or prove final truth.
Executable Capability Percolation Theory. In PIC, ECPT is the packet-flow and collective phase-control model.
ccr.task.v0.1 records emitted by PIC for Collective Capability Runtime or another scheduler. These are candidate tasks, not execution authority.
ccr.residual.v0.1 records emitted by PIC so unresolved work remains visible across runtime handoff.
A graph showing packet nodes, semantic support edges, evidence, residuals, and blockers. It is useful for diagnosing what work supports what.
Something a checker can inspect, such as a hash, schema-checked record, signed attestation, verifier report, test log, provenance record, or typed trace. Metadata such as "passed" or "important" is not evidence by itself.
A path that appears available in the packet graph but has not been executed or accepted as completed work. It is a diagnostic target, not an action grant.
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.
The local workbench for storing report windows, building effective packet graphs, observing phase metrics, checking closure and execution-available paths, and producing threshold or certificate candidates.
A practical TRC trace normal form. It is a structured record for checking an operation candidate before any runtime or provider decides whether to act.
A small stored window of Phase Lab events. It lets PIC inspect a local slice of packet ecology over time.
A required check that has not yet been discharged.
A structured list of unresolved work. Residuals can include missing evidence, stale data, external-domain limits, verifier backlog, unsafe packet status, resource mismatch, or unverified assumptions.
A named path for checking a specific kind of obligation.
The complete source for exported public record schemas. schemas/index.json and agent-manifest.json are indexes, not replacements for the registry.
All obligations for the scoped finite claim are discharged. Many useful reports correctly keep settled=false.
Salience-Queue Occupation Theory. In PIC, SQOT is the finite attention and queue discipline layer. It helps track salience, stale work, hazards, cost, reserve, and obstruction.
Typed Reality Compilation. In PIC, TRC helps turn traces and action boundaries into typed diagnostic records while preserving external-world limits.
A named checking path for a proof obligation. A verifier route may point to a schema check, evidence verifier, identity check, trace checker, snapshot verifier, domain adapter, or runtime route.
The report can support practical routing or inspection. This is weaker than settled=true and stronger than "raw text exists."
- 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