Home

Percolation Inversion Compiler Wiki

Percolation Inversion Compiler, or PIC, is a local checker for AI agent output, evidence, unfinished work, and safe reuse decisions. The current public release is v0.6.0 CCR interop and TRC operation readiness.

In plain terms, PIC helps a person or an agent answer:

• What is being claimed?
• What evidence is attached?
• What is still missing?
• Which verifier or next check should handle the missing work?
• Can this result be reused under a limited scope?
• Which finite work items can be handed to a runtime such as CCR?
• Why is the result useful but still not fully settled?

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

Current Release

v0.6.0 keeps the v0.5.0 Phase Ecology Lab and adds practical handoff surfaces for multi-agent runtimes:

• CCR task JSONL and residual JSONL from phase plans and phase gaps;
• BIT registry extraction, witness checks, and CCR witness-completion tasks;
• SQOT queue diagnostics that can emit CCR repair tasks;
• TRC trace normalization, trace checking, and trace-to-packet conversion;
• an ASI-proxy benchmark bundle for dry-run routing and audit examples.

These outputs are inert JSON or JSONL. They help a runtime schedule finite checks, preserve residuals, and avoid hidden promotion. They do not run tools, mutate repositories, call providers, or prove real ASI.

Related OSS

Collective Capability Runtime, or CCR, is the companion open-source Python runtime for coordinating many agents around tasks, leases, blackboard events, packet distillation, provider imports, residual tracking, and release audits.

Use PIC when you need packet-level checks, verifier routing, schemas, Phase Ecology Lab diagnostics, TRC trace checks, CCR interop JSONL, or protocol-relative certificate candidates. Use CCR when you need an auditable local runtime that coordinates multi-agent work and can import PIC-compatible reports without treating them as automatic settlement or execution authority.

See Related OSS and CCR Interop for the plain-language boundary.

Fastest Start

Install from PyPI and run the compact checker first:

python -m pip install 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
pic demo bootstrap --output-dir pic-demo

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.

First CCR Handoff

Use this when another runtime should receive candidate work as data:

pic phase plan --compact --emit ccr-tasks --output tasks.jsonl
pic phase gap --compact --emit ccr-residuals --output residuals.jsonl

The emitted records are scheduling inputs. accepted=true, operation_ready=true, or a listed command hint is not settlement and is not execution authority.

Short Phase Lab Demo

After pic demo bootstrap, use the packaged demo files:

pic phase lab init --output-dir pic-demo/phase-lab
pic phase lab ingest --store pic-demo/phase-lab --report pic-demo/phase_lab_runtime_report.json
pic phase lab observe --store pic-demo/phase-lab --window latest
pic phase lab graph --store pic-demo/phase-lab
pic phase lab closure --store pic-demo/phase-lab
pic phase lab executable-paths --store pic-demo/phase-lab
pic phase lab certify --store pic-demo/phase-lab --threshold pic-demo/phase_lab_threshold.json

See Phase Ecology Lab for the full plain-language guide.

Where To Go Next

• Getting Started: choose pip install or source checkout.
• Quickstart: shortest practical command paths.
• CCR Interop: how PIC emits candidate CCR tasks and residuals.
• ASI Proxy Acceleration: what "ASI-proxy" means and does not mean.
• Phase Ecology Lab: windowed diagnostics from v0.5.0 and later.
• Related OSS: how PIC relates to Collective Capability Runtime.
• Agent Guide: how AI agents should read PIC output.
• Core Concepts: candidate, evidence, obligation, residual, verifier route.
• CLI Recipes: command examples grouped by task.
• Safety and Limits: what PIC never authorizes.
• Theory Map: ECPT, BIT, TRC, SQOT, and ALT in plain language.
• FAQ: common beginner questions.

Safety Boundary

PIC does not prove real ASI, physical truth, legal authority, policy success, oracle truth, 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.

PIC can recommend finite next checks and emit runtime handoff data. Those records are data for review and scheduling, not permission to act.

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, multi-agent runtime, task leasing, blackboard events, provider import, TRC operation readiness, TraceNF, trace-to-packet, BIT witness registry, SQOT queue repair, ALT ECPT lift, ECPT, BIT, TRC, SQOT, ALT, abstraction liquidity, typed trace adapter, salience queue, ASI-proxy acceleration, collective phase certificate, pic agent check --compact, pic phase plan --emit ccr-tasks, pic trc trace-check, pic phase lab, settled=false.