-
Notifications
You must be signed in to change notification settings - Fork 0
Operation Gate
PIC's TRC operation gate is a non-executing preflight over a typed trace. It helps an agent decide whether a candidate operation is structured enough for review before any provider, connector, or physical-world handoff is considered.
It does not execute the operation.
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: the trace declares required planning fields for the scoped candidate. -
provider_dispatch_ready: provider dispatch preconditions are represented; this is still not dispatch. -
physical_dispatch_ready: physical dispatch fields are represented; this is still not physical outcome proof. -
executed: always false for PIC gate reports. -
settled: remains false unless scoped verifier obligations are discharged elsewhere.
Operation readiness requires authority, resource ledger, rollback or escrow obligation, witness or evidence references, causal schedule, preconditions, postconditions, and tolerance ledger.
The stricter operation gate also checks authority status, expiry, scope, trusted issuer policy, hazard envelope, lifecycle freshness, side-effect policy, verifier windows, provider-dispatch flags, physical-dispatch profile fields, MCP tool gates, and A2A agent gates.
physical_dispatch_ready=true is not physical outcome proof. It only means the record contains the declared physical-dispatch prerequisites under the selected provider profile. A separate runtime still needs explicit approval, execution policy, observation windows, rollback, emergency stop, and verifier evidence.
TRC operation gate, TraceNF, operation_ready, provider_dispatch_ready, physical_dispatch_ready, authority envelope, hazard envelope, rollback escrow, lifecycle certificate, side effect policy, MCP tool gate, A2A agent gate, executed=false, settled=false.
- 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