Skip to content

Quickstart

kadubon edited this page Jul 1, 2026 · 6 revisions

Quickstart

This page gives the shortest safe paths to useful output.

Path A: Check Agent Output

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

Read these fields first:

  • accepted: the report envelope passed finite checks.
  • workflow_usable: the output can be used for routing or review.
  • settled: all scoped obligations are discharged.
  • unresolved_obligations: checks that still need work.
  • residual_summary: unresolved work grouped by kind.
  • next_safe_actions: suggested checks or inspections, not permission to execute.

Path B: Ask For A Phase Plan

pic phase plan --compact --text "Candidate packet: route evidence and preserve residuals." --profile development
pic agent accelerate --compact --text "Candidate packet: route evidence and preserve residuals." --profile development

The planner ranks gaps, bottlenecks, residuals, and safe next inspections. It does not execute commands.

Path C: Run A CARA Acceleration Check

From a source checkout:

pic ecpt target-validity-check --target examples/asi_proxy_acceleration_bundle/target.json
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

certified_acceleration_candidate=true means the scoped v0.8 target/baseline/capital comparison passed. It is not real ASI proof and not permission to act in the world.

Path D: Check MCP And A2A Evidence

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

Descriptor and handoff reports are candidate evidence. They do not grant delegated tool authority.

Path E: Emit CCR Tasks And Residuals

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

The output is a handoff record, not a tool execution request.

Path F: Check A TRC Operation Candidate

pic trc trace-normalize --input examples/asi_proxy_benchmark_bundle/trc_agent_trace.json --output trace_nf.json
pic trc trace-check --trace trace_nf.json --output trace_check.json
pic trc operation-gate --trace trace_nf.json --provider-profile examples/asi_proxy_benchmark_bundle/provider_profile.json --output operation_gate.json
pic trc trace-to-packet --trace trace_nf.json --output trace_packet.json

operation_ready=true means the trace has explicit authority, resources, rollback or escrow data, witnesses, schedule, and tolerance fields for the scoped candidate. It still does not mean the action was executed or that the physical result is true.

Path G: Run The Packaged Demo

pic demo installed-smoke --profile development
pic demo bootstrap --output-dir pic-demo
pic runtime step --state pic-demo/runtime_state.json --input pic-demo/runtime_step_input.json --profile development

Path H: Source Checkout

git clone https://github.com/kadubon/percolation-inversion-compiler.git
cd percolation-inversion-compiler
uv sync --all-extras --dev
uv run pytest

Important Rule

Raw packet volume is not progress. A report with many candidates is not better unless the evidence, verifier routes, residuals, and safety boundary are clear.

settled=false is often the correct result. It means the remaining obligations were not hidden.

Clone this wiki locally