ASI Proxy Acceleration

ASI Proxy Acceleration

PIC uses ASI-proxy in a narrow, protocol-relative sense. 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 present, resource matched, and observable;
• at least one runtime capital witness is admitted;
• proxy-only evidence contributes no safe capital;
• admitted lower-bound capital crosses the declared target with positive margin;
• raw-net capital floors are satisfied;
• blockers remain empty.

pic.phase_acceleration_report.v1 is fail-closed. Missing or stale baseline envelopes, unapproved authority, non-accepted mission/generated/externality laws, rejected hazard/capability/viability envelopes, absent admitted capital witnesses, proxy-only capital, negative liquidity, stale lifecycle evidence, stale authority, and raw-net floor failures set ok=false with explicit residual blockers.

Commands

pic ecpt target-validity-check --target examples/asi_proxy_acceleration_bundle/target.json
pic 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 example paths require a source checkout. The report is JSON data. It is not execution authority.

Practical Meaning For Agents

An agent can use PIC to make an ASI-proxy workflow easier to coordinate by:

• checking candidate packets before reuse;
• ranking phase gaps and bottlenecks;
• emitting CCR tasks and residuals;
• extracting BIT witness gaps;
• diagnosing SQOT queue pressure;
• checking ALT-to-ECPT lift and capital admission;
• normalizing TRC traces before provider handoff review;
• preflighting MCP descriptors and A2A handoffs.

The result is operational routing data. It is not autonomous execution.

TRC Operation Readiness

TRC means Typed Reality Compilation. PIC can normalize a trace, check whether it has enough declared structure to be an operation candidate, and emit an operation-gate report before any provider dispatch.

pic trc trace-normalize --input examples/asi_proxy_benchmark_bundle/trc_agent_trace.json --output trace_nf.json
pic trc trace-check --trace trace_nf.json --output trace_check.json
pic trc operation-gate --trace trace_nf.json --provider-profile examples/asi_proxy_benchmark_bundle/provider_profile.json --output operation_gate.json
pic trc trace-to-packet --trace trace_nf.json --output trace_packet.json

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.

Monotone Non-Promotion

PIC follows a conservative rule: 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 did not execute it.
• certified_acceleration_candidate=false with ok=true: the report is well formed, but the positive target margin was not met.
• ok=false: safety or validity blockers prevent certification.

Benchmark Interpretation

The source repository includes examples/asi_proxy_benchmark_bundle/ and examples/asi_proxy_acceleration_bundle/. They are dry-run bundles for checking routing, audit behavior, CARA reports, MCP/A2A checks, and TRC gates. They do not measure autonomous general intelligence.

Search Terms

ASI-proxy acceleration, CARA, capital-aware response assessment, runtime capital witness, target-validity certificate, baseline upper envelope, target_validity_ok, certified_acceleration_candidate, raw_net_capital_floor, proxy_only_non_contributing, capital_admitted, TRC operation readiness, TRC operation gate, TraceNF, operation_ready, provider_dispatch_ready, physical_dispatch_ready, fixture_only_authority_non_executable, authority_scope_mismatch, executed=false, settled=false, BIT witness gap, SQOT queue repair, ALT ECPT lift, CCR foundry allocation, MCP descriptor report, A2A handoff report.