Operator Approval Loop
Approval contract for agent-drafted outbound messages: obligations, hashed drafts, epoch-keyed decisions, and a delivery ledger that proves what went out.
- What
- Approval contract for agent-drafted outbound messages: obligations, hashed drafts, epoch-keyed decisions, and a delivery ledger that proves what went out.
- Cost
- Free
- Needs
- Use "Operator Approval Loop" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a contract for agents that draft messages to external counterparties, so nothing sends on the agent's own judgment and the operator stays informed internally. Every outbound draft is filed as an obligation whose status moves from drafted to approved or rejected to sent, carrying direction, counterparty, channel and an epoch timestamp. Each obligation has one draft sidecar holding the exact text, its sha256 hash, origin coordinates and priority; decisions are recorded with the operator id, a nonce and the draft epoch they were made against, and epoch rotation means re-filing a draft invalidates any decision keyed to the old epoch, so a stale approval can never release rewritten text. A durable claim reserves dispatch with at most one active claim per obligation, preventing double sends, and a delivery ledger row proves one send or notice per obligation-decision pair. A pre-draft baseline gate can refuse filings, and internal filing notices keep the operator informed. Includes a reference SQL schema for the ledger. From the affaan-m/ECC repository (MIT). Honest caveats: a workflow contract, not turnkey software; the ledger schema must be wired into your own stack. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Operator Approval Loop" with your Muse. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/operator-approval-loop/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Design an approval loop for agent-drafted customer replies" or "Implement the obligation/draft/decision ledger from the reference schema." 3. Enforce the invariants: no send without an approved snapshot, epoch rotation on every re-file, at most one active claim per obligation. Tip: start with the baseline gate and filing rules before the SQL; the ledger only matters if drafts are filed cleanly. Safety: a skill is plain-text instructions; it runs nothing by itself. Approval records are evidence; store them where auditors can reach them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.