ASI Proxy Acceleration

ASI Proxy Acceleration

PIC-TS uses ASI-proxy in the same narrow, protocol-relative sense as the canonical Python package. It means measurable improvement in finite workflow formation: better packet routing, clearer evidence, lower residual ambiguity, healthier queues, reusable abstraction records, and explicit verifier tasks.

It does not mean proof of real ASI.

Node.js Loop

In v0.7.0, a Node.js agent can run this dry, data-only loop:

npx pic-ts phase plan --request examples/asi_proxy_benchmark_bundle/pic_phase_request.json --compact
npx pic-ts phase plan --request examples/asi_proxy_benchmark_bundle/pic_phase_request.json --compact --emit ccr-tasks --output tasks.jsonl
npx pic-ts phase gap --request examples/asi_proxy_benchmark_bundle/pic_phase_request.json --compact --emit ccr-residuals --output residuals.jsonl
npx pic-ts trc trace-normalize --input examples/asi_proxy_benchmark_bundle/trc_agent_trace.json --output trace_nf.json
npx pic-ts trc trace-check --trace trace_nf.json --output trace_check.json
npx pic-ts trc operation-gate --trace trace_nf.json --output operation_gate.json
npx pic-ts trc trace-to-packet --trace trace_nf.json --output trace_packet.json

The commands route data. They do not execute packet text, trace content, safe command hints, shell commands, or provider calls.

TRC Operation Readiness

TRC means Typed Reality Compilation. pic-ts trc trace-check checks whether a trace normal form has enough declared structure to be reviewed as an operation candidate. pic-ts trc operation-gate adds authority freshness, scope, trusted issuer, hazard, schedule, lifecycle, provider-dispatch, and physical-dispatch gates.

real_world_operation_gate.operation_ready=true means the scoped candidate declares:

• authority envelope;
• resource ledger;
• rollback or escrow obligation;
• witness or evidence references;
• causal schedule;
• preconditions and postconditions;
• tolerance ledger.

It still reports executed=false and settled=false unless a separate runtime and verifier route actually discharges those obligations. provider_dispatch_ready=true is not dispatch, and physical_dispatch_ready=true is not physical outcome proof.

Monotone Non-Promotion

PIC-TS follows the same conservative rule as Python PIC: a new candidate can add routes, tasks, evidence, and residuals, but it cannot silently become settled.

Useful states include:

• accepted=true and settled=false: the record can be routed, but work remains.
• workflow_usable=true and settled=false: the report can guide the next step.
• operation_ready=true and executed=false: the trace is structured enough for review, but PIC-TS did not execute it.

SDK Helpers

import {
  traceCheckReport,
  traceNormalFormReport,
  operationGateReport,
  tracePacketCandidate,
} from "percolation-inversion-compiler-ts/interop/ccr";

Use these helpers when a JavaScript runtime needs to keep operation candidates machine-readable before handing work to a scheduler.

Search Terms

PIC-TS ASI-proxy acceleration, Node.js phase plan, TRC operation readiness, TRC operation gate, TraceNF, real world operation gate, operation_ready, provider_dispatch_ready, physical_dispatch_ready, fixture_only_authority_non_executable, authority_scope_mismatch, executed=false, settled=false, CCR task JSONL, CCR operation preflight, BIT witness task, SQOT queue repair, ALT capital_admitted, trace-to-packet.