FAQ

FAQ

Is this the canonical implementation?

No. The Python project is canonical:

https://github.com/kadubon/percolation-inversion-compiler

PIC-TS is the npm and Node.js compatibility port.

Which Python version is the reference?

For this release line, the reference is percolation-inversion-compiler==0.6.0.

Do I need Python?

No for normal npm use. The installed npm package can run the Node-only agent loop, schema commands, packet commands, phase commands, Phase Ecology Lab commands, CCR interop commands, TRC operation-readiness commands, and SDK imports without Python.

What is new in v0.6.0?

v0.6.0 adds Node.js surfaces for:

• CCR task JSONL and residual JSONL;
• BIT witness registry extraction and CCR witness tasks;
• SQOT queue repair task emission;
• ALT-to-ECPT bridge reports;
• TRC trace normalization, trace checking, and trace-to-packet conversion;
• the percolation-inversion-compiler-ts/interop/ccr SDK subpath.

These are data and diagnostic surfaces. They do not execute commands or settle external claims.

Should I use pic or pic-ts?

Use pic-ts for the npm package.

pic is included as a compatibility alias, but it can be confused with the Python CLI.

Does accepted=true mean the output is correct?

No. It means the input was accepted for that command route.

Does workflow_usable=true mean the work is complete?

No. It means the report can guide the next workflow step.

Does settled=false mean failure?

No. It often means the tool preserved missing obligations instead of hiding them.

Does the package execute safe commands?

No. safe_commands are recommendations or display data.

Does operation_ready=true mean PIC-TS ran a real-world operation?

No. It means a TRC trace has the required declared fields for a scoped operation candidate, such as authority, resources, rollback or escrow, witnesses, schedule, preconditions, postconditions, and tolerance data.

PIC-TS still does not execute the operation and does not prove the physical result.

What is CCR interop?

CCR interop is the v0.6.0 JSONL handoff between PIC-TS and Collective Capability Runtime.

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

The output is candidate work for a runtime to import and schedule. It is not CCR settlement and not command execution.

Does packet inspection run npm, docker, kubectl, or shell commands?

No. It can detect command-like text, but it does not execute it.

What is Phase Ecology Lab?

It is a local JSON/JSONL lab for observing agent reports over a small window. It can build packet graphs, show missing evidence, inspect closure candidates, and detect available execution paths as data.

It does not execute paths or prove real-world outcomes.

Can this prove real ASI?

No. It can help route finite agent workflow checks. It does not prove real ASI, physical outcomes, simulator outcomes, or oracle truth.

Where is the npm package?

https://www.npmjs.com/package/percolation-inversion-compiler-ts