Use Cases

Use Cases

Use percolation-inversion-compiler-ts when AI agent output should be checked before it is reused, routed, merged, sent to another agent, or treated as complete.

LLM Output Checking

Run a compact check before reusing a generated answer:

npx pic-ts agent check --compact --text "Candidate packet: preserve residuals." --profile development

This gives a JSON report that shows whether the output is accepted and what remains unresolved.

Node.js Agent Runtime

Use the SDK inside an agent loop:

import { runAgentCheck } from "percolation-inversion-compiler-ts";

const report = runAgentCheck({ agent_output: draftText }, true);

CI Report Artifact

Save a JSON report from a build job:

npx pic-ts agent check --compact --text "Candidate packet: preserve residuals." --output agent-check.json

Upload agent-check.json as an artifact.

Packet Exchange

Export runtime output as a packet file and inspect it without executing content.

npx pic-ts packet export --report runtime-report.json --output packet.json
npx pic-ts packet inspect --packet packet.json

Phase Planning

Ask for the next finite workflow plan:

npx pic-ts phase plan --compact --text "Candidate packet: preserve residuals." --profile development

Phase planning is recommendation-only. It does not execute commands.

CCR Runtime Handoff

Emit JSONL records for CCR or another scheduler:

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

These files are candidate task and residual records. The downstream runtime must still apply leases, authority checks, provider policy, and settlement rules.

Phase Ecology Lab

Observe several local reports together:

npx pic-ts phase lab init --output-dir .pic-lab
npx pic-ts phase lab ingest --store .pic-lab --report runtime-report.json
npx pic-ts phase lab graph --store .pic-lab
npx pic-ts phase lab observe --store .pic-lab

This helps find accepted packets, candidate-only packets, missing evidence, and blocked execution paths.

Diagnostic Review

Use BIT, SQOT, ALT, TRC, and ecology commands to inspect bottlenecks, queue pressure, abstraction reuse, typed traces, and execution-available paths.

These commands are useful for review and routing. They do not grant execution authority.

TRC Operation Candidate Review

Check whether a trace is structured enough for scoped operation review:

npx pic-ts trc trace-normalize --input trace.json --output trace_nf.json
npx pic-ts trc trace-check --trace trace_nf.json --output trace_check.json

This can report operation_ready=true when authority, resources, rollback, witnesses, schedule, and tolerance data are present. It still does not execute the operation.

Search-Friendly Summary

Common uses include AI agent output checking, LLM output validation, JSON schema validation, workflow report generation, residual ledger preservation, missing obligation tracking, packet inspection, Phase Ecology Lab observation, effective packet graph generation, Node.js agent runtime integration, Python-compatible PIC reports, CCR task JSONL, CCR residual JSONL, TRC operation readiness, TraceNF, operation_ready, ASI-proxy acceleration, and npm workflow diagnostics.