What PIC Does Not Do

What PIC Does Not Do

PIC is a checking, routing, and residual-ledger toolkit. It is intentionally limited.

PIC Does Not Prove Real ASI

PIC does not prove that a system is a real artificial superintelligence.

It can produce protocol-relative reports about finite declared records, packet flow, verifier routes, and phase proxy conditions. Those reports are not proof of real ASI.

PIC Does Not Prove External-World Truth

PIC does not prove unobserved physical facts, simulator outcomes, oracle answers, legal authority, policy outcomes, or real-world success.

When a claim depends on an external domain, PIC records the required verifier route or residual obligation.

PIC Does Not Grant Execution Authority

PIC output is diagnostic.

It does not authorize:

• shell commands;
• file writes;
• repository mutation;
• package installation;
• arbitrary network access;
• background crawling or autonomous polling;
• hidden live connectors without an explicit source;
• external message sending outside declared local relay workflows;
• credential use;
• model-weight changes;
• self-rewrite;
• payments or purchases.

Host runtime controls still matter: sandboxing, allowlists, permissions, and tool policy.

PIC Does Not Execute CCR Or TRC Handoffs

CCR task JSONL, CCR residual JSONL, TRC trace normal forms, and trace-to-packet reports are data records.

operation_ready=true means a scoped trace has required planning fields. It does not mean PIC called a provider, changed the world, or proved the result.

constraints.allowed_commands=[] in a PIC-emitted CCR task means the handoff record itself grants no command authority.

PIC Does Not Treat More Packets As More Progress

Raw packet volume is not progress.

A useful packet must still pass the relevant evidence, route, receiver, rollback, authority, semantic edge, liquidity, queue, identity, and residual checks for its scope.

PIC Does Not Hide Residual Work

PIC is designed to keep missing obligations visible. settled=false is often the correct result.

Do not rewrite open obligations as completed work in a summary, release note, issue, pull request, or downstream agent answer.