Run Ref-gate checks, recoverability scoring, Governance Routing Workbench route selection, autonomy-budget accounting, and ledger evidence for each action.
Work / Result / Impact
Cloud reviewers can see the operational value quickly.
The pack answers whether recoverability changes judgment before an autonomous agent changes infrastructure state.
The current report returns `DENY`, `THROTTLE`, and `ESCALATE` outcomes across 24 cloud-admin scenarios.
Actions can be blocked, narrowed, checkpointed, reviewed, or routed through constrained execution before infrastructure changes occur.
SMERC does not replace IAM, OPA, Terraform policy, Kubernetes RBAC, CI approvals, SIEM, or human accountability.
Company Intake Bridge
From proof pack to safe customer test
The Cloud Metadata Connector turns read-only exported summaries from IAM, Terraform, CloudTrail-style event summaries, Kubernetes rollouts, DNS change requests, and backup-policy changes into strict SMERC customer-evaluation metadata. It gives a company a way to test familiar cloud evidence before granting live access or building an enforcement integration.
Reason Codes
Cloud-specific reasons make the proof easier to review.
IAM scope expansion
Permission changes may increase who or what can act later.
Rollback uncertain
Rollback, reversibility, or checkpoint support is weak for the proposed action.
Production blast radius
Production impact scope is wide enough to create meaningful operational exposure.
Evidence incomplete
The action lacks enough trusted evidence to support confident execution.
Network boundary widening
Network access changes can expand exposure faster than reviewers can respond.
Backup recovery risk
Retention or recovery-policy changes can weaken the future recovery path.
Best next test
Replace the sample actions with 10 to 25 metadata-only actions from one cloud workflow family: production IAM changes, infrastructure-as-code applies, Kubernetes rollouts, DNS routing, database administration, network policy, service-auth rotation, or backup policy.