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, admitted lower-bound capital witnesses, and explicit verifier tasks.

It does not mean proof of real ASI.

v0.8.0 CARA Rule

v0.8.0 treats ASI-proxy/CARA acceleration as a target-valid comparison. The target set, baseline upper envelope, and runtime capital witnesses must be declared before outcome observation.

A phase acceleration report can become a certified acceleration candidate only when the target validity report passes, the baseline upper envelope is resource matched and observable, at least one runtime capital witness is admitted, admitted lower-bound capital crosses the target with positive margin, and all blockers remain empty.

PIC-TS mirrors Python PIC fail-closed behavior. Non-accepted target laws, unapproved authority, rejected hazard/capability/viability envelopes, stale or missing baselines, absent admitted capital witnesses, proxy-only capital, negative liquidity, stale lifecycle evidence, stale authority, raw-net floor failures, and MCP descriptor rug-pulls become explicit blockers. Blocked CARA reports return ok=false while preserving settled=false.

Node.js 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 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 --provider-profile examples/asi_proxy_benchmark_bundle/provider_profile.json --output operation_gate.json
npx pic-ts 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

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, physical-dispatch, MCP, and A2A gates.

operation_ready=true means the scoped candidate declares authority, resources, rollback or escrow, witnesses, schedule, preconditions, postconditions, and tolerance data. provider_dispatch_ready=true is not dispatch. physical_dispatch_ready=true is not physical outcome proof.

SDK Helpers

import {
  phaseAccelerationReport,
  targetValidityCheck,
  mcpToolDescriptorReport,
  mcpToolInvocationPreflight,
  operationGateReport,
} from "percolation-inversion-compiler-ts";

All helpers return JSON-serializable data. They do not execute tools or provider calls.

Search Terms

PIC-TS ASI-proxy acceleration, Node.js phase plan, CARA, target-validity certificate, runtime capital witness, baseline upper envelope, phase acceleration report, proxy_only_non_contributing, capital_admitted, TRC operation readiness, TRC operation gate, TraceNF, operation_ready, provider_dispatch_ready, physical_dispatch_ready, executed=false, settled=false, CCR task JSONL, MCP descriptor report, A2A handoff report.