-
Notifications
You must be signed in to change notification settings - Fork 0
Acceleration Measurement
Compare a baseline and candidate under the same observation protocol, constraint frame, receiver family, resource envelope, fixed horizon, stopping rule, and evidence policy.
Higher is better for verification yield, receiver reuse, and certified capital gain. Lower is better for time-to-verified, residual half-life, resource cost, and absolute error correlation.
Use an accelerator claim only when accepted=true and
acceleration_metrics_certified=true. This is a finite protocol result, not
proof of real ASI.
From a source checkout:
pic runtime compare --baseline examples/runtime_acceleration/baseline.json --candidate examples/runtime_acceleration/candidate.json
pic runtime certify-acceleration --baseline examples/runtime_acceleration/baseline.json --candidate examples/runtime_acceleration/candidate.jsonThe example folder also contains rejection fixtures for resource mismatch,
missing evidence, post-selected horizons, and metric regression. Input-side
accepted fields are ignored. Every metric must be finite and evidence-backed;
there must be no worsening beyond its declared tolerance and at least one
improvement beyond tolerance.
- 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