Skip to content
kadubon edited this page Jun 22, 2026 · 12 revisions

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.5.0 Phase Ecology Lab.

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?
  • 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, or raw packet volume as proof.

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.

What v0.5.0 Adds

v0.5.0 adds the Phase Ecology Lab, a local workbench for looking at groups of reports over time.

It can build:

  • phase windows: small time windows of report and packet data;
  • effective packet graphs: what supports what, and where evidence is weak;
  • closure diagnostics: whether useful packet loops appear to exist;
  • execution-available path diagnostics: paths that look available but are not executed;
  • BIT bottleneck reports: missing checks that would unlock useful next work;
  • SQOT queue reports: attention, backlog, obstruction, and reserve checks;
  • ALT lift reports: whether reusable abstraction value helps the packet graph;
  • TRC typed trace reports: structured action traces and action-boundary checks;
  • threshold and certificate candidates: protocol-relative reports that keep residuals visible.

These outputs are diagnostic-only. They do not execute commands, mutate repositories, crawl the web, approve agent action, or prove real ASI.

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

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. Those recommendations are data for review, 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, BIT, SQOT, ALT, TRC, ECPT, abstraction liquidity, typed trace adapter, salience queue, collective phase certificate, pic agent check --compact, pic phase lab, settled=false.

Clone this wiki locally