governed-autorun

Designs, audits, and repairs receipt-driven autonomous multi-sandbox workflow loops with cost governance.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/Noetfield-Systems/SourceA --skill governed-autorun-noetfield-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governed-autorun
Source: https://github.com/Noetfield-Systems/SourceA/tree/main/.cursor/skills/governed-autorun
Command: npx skills add https://github.com/Noetfield-Systems/SourceA --skill governed-autorun-noetfield-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Autonomous agent loops running 24/7 tend to fake PASS results, silently burn budget, drift from committed configuration, and contradict their own reports. This Skill enforces thirteen operational laws so continuously scheduled multi-workflow systems produce verifiable receipts, deterministic state transitions, and auditable cost attribution instead of unverifiable prose. ## Core Features & Use Cases - Thirteen governing laws (L1–L13): single reconciler authority, external-only verification, verifier freeze, fail-closed sinks, ROI throttling, drift detection, and deterministic replayable loops. - Receipt-driven auditing: adversarial checklist for reviewing agent reports — timestamp math, self-verification detection, count/ID validation, and cost sanity checks against defined JSON receipt schemas. - Kaizen maintenance pipeline: converts failures, drift receipts, and throttle events into an ROI-ranked improvement queue with machine-safe versus founder-gated classification and auto-rollback. - Use Case: A founder pastes an agent report claiming a deploy passed. The Skill flags that verification ran 30 seconds after publish (under the 60-second minimum), that the agent verified its own work, and that the cycle receipt lacks metered cost — rejecting the PASS and demanding external-runner evidence. ## Quick Start Ask the assistant to audit this agent worker report against the governed-autorun laws and identify any verification or cost violations.

Frequently Asked Questions about governed-autorun

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit an AI agent report for fake PASS results?

Check timestamp math first: verification under 60 seconds after deploy is auto-rejected. Then look for self-verification, prose-as-proof without command output, verifier edits in the diff, and count or ID math that does not reconcile with actual rows.

How do I make an autonomous cron loop deterministic and replayable?

Apply rules D1–D8: idempotency keys on every side effect, a single writer per state cell with compare-and-swap, IDs derived from actual committed rows, and an append-only event log as the only authored truth. Replaying the log must byte-match live state.

What counts as valid deployment verification for an autonomous agent?

Only an external runner the building agent does not control counts: raw public hostname, redirects off, content markers plus full-body hash, at least 60 seconds after deploy. Local builds, same-machine curls, and preview URLs are invalid.

How do I stop an autonomous agent loop from wasting money?

Meter cost at the call site on every cycle receipt and tag each cycle with a value class. If a loop's trailing 7-day spend is over 30 percent value_class none, it auto-enters THROTTLED_ROI with halved frequency and a founder escalation.

Why does my agent report PASS while the live site is broken?

This usually means self-verification or non-discriminating checks: identical hashes across URLs, 200-only checks on SPA fallbacks, or redirect-following on redirect tests. Demand external-runner evidence with full-body hashes and spot-check public URLs independently.

When should a new automation loop be considered verified?

A loop stays DECLARED until it completes a 24-hour zero-manual window with scheduled receipts only, passing sink invariants every cycle, plus a heartbeat containing the cost table and drift check. Manual green runs do not prove cron green.