Home

Percolation Inversion Compiler Wiki

Percolation Inversion Compiler, or PIC, is a local checker/compiler for AI agent output, evidence, unfinished work, safe reuse decisions, and protocol-relative ASI-proxy phase diagnostics.

The current public release is v0.8.0 ASI-proxy/CARA interop and safety gates.

PIC helps a person or an agent answer:

• What is being claimed?
• What evidence is attached?
• What residual work remains?
• Which verifier, CCR task, or next check should handle the missing work?
• Can this result be reused under a limited scope?
• Is an operation candidate structured enough for review before any provider or real-world handoff?
• Why is a result useful but still not settled?

PIC treats agent output as candidate work. It does not treat confident text, raw packet volume, MCP descriptors, A2A handoffs, provider evidence, command-like strings, or high priority as proof or permission to act.

Current Release

v0.8.0 adds a target-valid ASI-proxy/CARA acceleration layer:

• declared target sets and target-validity checks;
• baseline upper envelopes;
• runtime capital witness reports;
• fail-closed phase acceleration reports;
• stricter TRC operation and physical-dispatch gates;
• MCP descriptor reports and invocation preflight;
• A2A agent-card and task-handoff reports;
• SQOT protocol/resource/probe diagnostics;
• BIT MEC frontier, certificate compiler, CEGAR, and dynamic-regime reports;
• CCR roundtrip fixtures under examples/asi_proxy_acceleration_bundle/.

certified_acceleration_candidate=true is not real ASI proof. It means the declared target, baseline, and admitted lower-bound capital witnesses satisfy the v0.8 protocol-relative comparison with positive margin.

Reports fail closed. Unaccepted target laws, unapproved authority, stale or missing baselines, absent admitted capital witnesses, proxy-only capital, raw-net floor failures, and MCP descriptor rug-pulls become explicit blockers instead of silent promotion.

Fastest Start

python -m pip install -U percolation-inversion-compiler
pic agent check --compact --text "Candidate packet: route evidence and preserve residuals." --profile development
pic phase plan --compact --text "Candidate packet: route evidence and preserve residuals." --profile development
pic demo installed-smoke --profile development

A useful first report can have workflow_usable=true and settled=false. That is normal. It means PIC kept unresolved work visible instead of hiding it.

v0.8.0 Safety Checks

pic phase acceleration-report --target examples/asi_proxy_acceleration_bundle/target.json --baseline examples/asi_proxy_acceleration_bundle/baseline_upper_envelope.json --capital examples/asi_proxy_acceleration_bundle/capital_witnesses.jsonl
pic ecpt target-validity-check --target examples/asi_proxy_acceleration_bundle/target.json
pic mcp descriptor-check --descriptor examples/asi_proxy_acceleration_bundle/mcp_descriptor.good.json --profile development
pic mcp invocation-preflight --descriptor examples/asi_proxy_acceleration_bundle/mcp_descriptor.good.json --call examples/asi_proxy_acceleration_bundle/mcp_call.good.json --profile development
pic a2a handoff-check --handoff examples/asi_proxy_acceleration_bundle/a2a_handoff.good.json --profile development

Commands that use examples/... assume a source checkout. The outputs are inert JSON. They do not execute tools, mutate repositories, call providers, or prove physical outcomes.

PIC And CCR

Collective Capability Runtime, or CCR, is the companion runtime for coordinating many agents around tasks, leases, blackboard events, packet distillation, residual tracking, foundry allocation, operation preflight, and release audits.

Use PIC when you need packet-level checks, verifier routing, schemas, Phase Ecology Lab diagnostics, TRC trace checks, MCP/A2A preflight, CARA reports, or CCR interop JSONL. Use CCR when you need an auditable runtime that schedules multi-agent work and imports PIC-compatible reports without treating them as automatic settlement or execution authority.

Where To Go Next

• Getting Started: choose pip install or source checkout.
• Quickstart: shortest practical command paths.
• ASI Proxy Acceleration: CARA, target validity, baseline, and capital witnesses.
• CCR Interop: PIC-to-CCR handoff and foundry allocation.
• MCP And A2A Safety: descriptor, invocation, card, and handoff checks.
• Operation Gate: TRC operation readiness, provider dispatch, and physical dispatch boundaries.
• Safety and Limits: what PIC never authorizes.
• Agent Guide: how AI agents should read PIC output.
• Theory Map: ECPT, BIT, TRC, SQOT, ALT, and CARA in plain language.

Safety Boundary

PIC does not prove real ASI, physical truth, simulator truth, oracle truth, legal authority, policy success, or arbitrary agent correctness.

PIC does not grant authority to run shell commands, write files, mutate repositories, install packages, send messages, use credentials, call live connectors without an explicit source, change model weights, or self-rewrite.

provider_dispatch_ready is not dispatch. physical_dispatch_ready is not physical outcome proof. accepted=true is not settlement. settled=false often means the safe result was to keep missing obligations visible.

Search Terms

AI agent output checker, LLM output validation, agent workflow verification, evidence routing, proof obligations, residual ledger, unresolved work ledger, safe reuse checks, capability packet, packet graph, Phase Ecology Lab, effective packet graph, execution-available paths, bottleneck diagnostics, Collective Capability Runtime, CCR, CCR task JSONL, CCR residual JSONL, CCR foundry allocation, ASI-proxy acceleration, CARA, runtime capital witness, baseline upper envelope, target-validity certificate, phase acceleration report, MCP descriptor report, MCP invocation preflight, A2A handoff report, TRC operation gate, TraceNF, operation_ready, provider_dispatch_ready, physical_dispatch_ready, capital_admitted, ECPT, BIT, TRC, SQOT, ALT, abstraction liquidity, salience queue, pic phase acceleration-report, pic mcp descriptor-check, pic trc operation-gate, settled=false.