Operation Gate

Operation Gate

PIC-TS's TRC operation gate is a non-executing preflight over a typed trace. It helps a Node.js 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.

Commands

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 trc trace-to-packet --trace trace_nf.json --output trace_packet.json

Field Meanings

• 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: false for PIC-TS gate reports.
• settled: remains false unless scoped verifier obligations are discharged elsewhere.

Required Evidence

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.

SDK

import { operationGateReport, traceNormalFormReport } from "percolation-inversion-compiler-ts";

Search Terms

PIC-TS TRC operation gate, TraceNF, operation_ready, provider_dispatch_ready, physical_dispatch_ready, authority envelope, hazard envelope, rollback escrow, lifecycle certificate, MCP tool gate, A2A agent gate, executed=false, settled=false.