-
Notifications
You must be signed in to change notification settings - Fork 0
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, and more explicit verifier tasks.
It does not mean proof of real ASI.
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 conditions;
- normalizing TRC traces before a provider handoff is considered.
The result is operational routing data. It is not autonomous execution.
TRC means Typed Reality Compilation. In v0.6.0, PIC can normalize a trace and check whether it has enough declared structure to be an operation candidate.
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 trace-to-packet --trace trace_nf.json --output trace_packet.jsonreal_world_operation_gate.operation_ready=true means the trace declares the required fields for the scoped candidate:
- authority envelope;
- resource ledger;
- rollback or escrow obligation;
- witness or evidence references;
- causal schedule;
- preconditions and postconditions;
- tolerance ledger.
It still does not mean the operation was executed, the physical result happened, policy outside the declared scope was satisfied, or the claim is settled.
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=trueandsettled=false: the record can be routed, but work remains. -
workflow_usable=trueandsettled=false: the report can guide the next step. -
operation_ready=trueandexecuted=false: the trace is structured enough for review, but PIC did not execute it.
The source repository includes examples/asi_proxy_benchmark_bundle/. It is a dry-run bundle for checking routing and audit behavior. It does not measure autonomous general intelligence.
ASI-proxy acceleration, protocol-relative ASI, phase acceleration planner, TRC operation readiness, TraceNF, real world operation gate, operation_ready, executed=false, settled=false, BIT witness gap, SQOT queue repair, ALT ECPT lift, CCR task handoff.
- Home
- Getting Started
- Acceleration Measurement
- Operation Guide
- AFST Satisfaction Flux
- Python TypeScript Compatibility
- Security
- Quickstart
- ASI Proxy Loop v0.9
- Token Reports and Agent Loop
- ASI Proxy Acceleration
- CCR Interop
- MCP And A2A Safety
- Operation Gate
- Phase Ecology Lab
- Related OSS
- Use Cases
- Live Intake and Agent Messages
- Core Concepts
- Concepts in Plain Language
- Agent Guide
- Diagnostics and Agent Autonomy
- What PIC Does Not Do
- Safety and Limits
- Theory Map
- CLI Recipes
- Glossary
- FAQ
- v1.1 Release Notes
- v0.9.0 Release Notes
- v0.8.0 Release Notes
- v0.7.0 Release Notes
- v0.6.0 Release Notes