01 / The operating case
What changes in a real workflow?
A guarded Kubernetes tool denies delete, while shell execution can still call the cluster API.
- 01Authority origin
- 02Task and grant
- 03Current decision
- 04Observed outcome
02 / Decision contract
What the executor must check
Inventory credentials, network routes, SDKs, jobs and human consoles to the executor; compare downstream write logs with decision IDs and block unmatched paths.
InputPrincipal · task · action · target
DecisionGrant ancestry · policy · current state
ResultEnforce · record · verify outcome
03 / Failure and evidence
What goes wrong, and what can be proven?
Failure mode
A clean wrapper log conceals an unmediated deletion.
Evidence to retain
Preserve path inventory, unpaired operation, credential and cluster outcome.
04 / Canonical scope
Why this reference stands alone
Tool-wrapper placement implements one route; this page owns coverage discovery across routes.
Illustrative implementation artifact
Path inventory
for protectedEffect in inventory:
list tool wrappers, SDKs, shell, jobs, private APIs
list credentials and network reachability
compare executor writes with decision IDs
block or equivalently guard unmatched routePrimary references