-
Notifications
You must be signed in to change notification settings - Fork 0
Safety and Limits
PIC is designed to be useful for agents while remaining fail-closed.
Fail-closed means PIC can return useful diagnostics without granting authority to execute unsafe work or claim complete settlement.
- real ASI;
- general intelligence;
- physical outcomes;
- simulator outcomes;
- oracle outcomes;
- policy outcomes;
- legal identity;
- real-world personhood;
- world-global uniqueness;
- correctness of arbitrary agent text;
- success of external actions.
- shell execution;
- repository mutation;
- package installation;
- arbitrary network access;
- background crawling or autonomous polling;
- hidden live connector use without an explicit source;
- model-weight changes;
- self-rewrite;
- credential use;
- external message sending outside declared local workflows;
- calendar edits;
- payments or purchases;
- provider dispatch;
- physical actuation.
PIC can recommend finite tasks. It does not make those tasks safe to execute.
Use fields carefully:
-
accepted: the finite envelope passed checks. -
workflow_usable: the result can support review or routing. -
ok: the report itself found no blocking residuals for its scoped check. -
settled: all scoped obligations are discharged. -
candidate_only: the item is still candidate material. -
capital_admitted: lower-bound capital evidence passed admission checks; this is not settlement. -
certified_acceleration_candidate: the v0.8 target/baseline/capital comparison passed; this is not real ASI proof. -
operation_ready: a TRC trace has required declared planning fields. -
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. -
candidate_only_until_checked: a downstream runtime must verify the handoff record.
Do not treat accepted=true as execution permission.
Do not treat operation_ready=true as proof that an external operation happened or should happen.
Do not treat settled=false as failure. It often means the safe result was to keep missing obligations visible.
PIC blocks or marks reports not certified when it sees:
- unaccepted mission, generated, or externality laws;
- unapproved authority envelopes;
- rejected hazard, capability, or viability envelopes;
- stale or missing baseline upper envelopes;
- missing resource matching or control observability;
- absent admitted runtime capital witnesses;
- proxy-only capital evidence;
- negative liquidity;
- stale lifecycle evidence;
- stale authority;
- raw-net floor failure;
- MCP descriptor rug-pull after approval;
- unsafe MCP invocation arguments or missing per-call controls.
PIC can emit CCR task JSONL, residual JSONL, TRC operation-gate reports, MCP/A2A reports, and CARA phase reports. These records are data-only handoffs.
They do not grant provider authority, shell or network authority, CCR settlement, residual removal, command-hint execution, or external outcome proof.
pic trc trace-check can report a scoped operation candidate as operation-ready when the trace declares authority, resources, rollback or escrow, witnesses, schedule, preconditions, postconditions, and tolerance data.
pic trc operation-gate adds stricter checks for authority status, expiry, scope, trusted issuer policy, hazard envelope, causal schedule, certificate lifecycle, provider-dispatch flags, MCP tool gates, A2A gates, and physical-dispatch profile fields.
That is a readiness check over a record. It is not execution, not proof of physical truth, and not permission to call a provider.
v0.8.0 adds CARA reports, MCP/A2A checks, CCR foundry interop fixtures, and stricter fail-closed TRC/physical gates while preserving the Phase Ecology Lab, CCR handoff, BIT, SQOT, ALT, and TRC boundaries from earlier releases. Paper-level and external-world obligations remain explicit residual work unless a scoped verifier route discharges them.
- 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