-
Notifications
You must be signed in to change notification settings - Fork 0
Theory Map
PIC implements finite, checkable interfaces for five source theories.
The theory names can look abstract, but each one maps to a practical engineering role.
ECPT stands for Executable Capability Percolation Theory.
Plain-language role: it asks how useful, verified capability packets can move through a fixed population and become usable paths, closures, and certificates.
In PIC, ECPT appears as:
- capability packet registries;
- packet promotion;
- closure witnesses;
- execution-available paths;
- hidden-injection checks;
- collective phase certificates.
ECPT does not prove real ASI. It provides protocol-relative finite checks about declared packets, agents, thresholds, and baselines.
BIT stands for Bottleneck Inversion Theory.
Plain-language role: it asks which missing witness, route, or finite check would unlock the most useful next step.
In PIC, BIT appears as:
- bottleneck tasks;
- finite witness records;
- unlockable-potential reports;
- route obligations;
- residual-preserving prioritization.
BIT helps identify work worth doing next. It does not make missing evidence disappear.
TRC stands for Typed Reality Compilation.
Plain-language role: it asks whether a claimed process has a typed, executable, resource-aware trace.
In PIC, TRC appears as:
- typed frontier records;
- executable trace normal forms;
- lifecycle and resource ledgers;
- external proof obligations for physical or domain-specific claims.
TRC separates checkable trace structure from unobserved physical truth.
SQOT stands for Salience-Queue Occupation Theory.
Plain-language role: it asks what should be handled next while preserving diagnostic reserve.
In PIC, SQOT appears as:
- salience schedules;
- quarantine decisions;
- stale packet handling;
- hazard-aware queueing;
- residual-reduction prioritization.
SQOT is a scheduling layer. It is not a truth layer.
ALT stands for Abstraction Liquidity Theory.
Plain-language role: it asks whether an idea, trace, pattern, or packet is reusable enough to reduce future work after costs and risks are counted.
In PIC, ALT appears as:
- abstraction-token admission;
- liquidity certificates;
- negative liquidity;
- deprecation and resurrection;
- baseline refresh;
- reproduction diagnostics;
- scoped acceleration certificates.
ALT treats raw external content as candidate material, not as capital.
candidate material
-> packet intake
-> evidence and trace checks
-> residual ledger
-> salience queue
-> verifier routing
-> packet promotion or quarantine
-> collective certificate or next bottleneck
The important discipline is scope. A packet can be useful for one profile, route, receiver, or validity domain without being globally true or generally settled.
- 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