Procedural memory

Runbooks

A runbook is promoted only after the procedure has run and been verified. Reuse is what makes the second run cheaper than the first.

Acme Insurance

Lead-router production deploy

12 validated runsVerified Today, 11:14rb_1
Procedure
  1. 1Confirm acceptance suite green on staging
  2. 2Capture rollback snapshot
  3. 3Request Class C approval
  4. 4Promote deployment to production alias
  5. 5Observe logs for 10 minutes
  6. 6Submit synthetic lead and verify
  7. 7Record deployment artifact
Known failure modes
  • HubSpot 429 during burst — retry with idempotency key
  • Slack channel archived — escalate, do not create channels
Northstar Financial

Salesforce token expiry recovery

7 validated runsVerified Yesterday, 09:05rb_2
Procedure
  1. 1Detect 401 pattern on connected app
  2. 2Re-issue refresh token from vault
  3. 3Replay dead-letter queue
  4. 4Verify record counts match source
  5. 5File incident report
Known failure modes
  • Replay duplicates records if idempotency key missing
  • Sandbox token used against production org — hard stop
Lumen Medical Spa

Consent-safe patient messaging

3 validated runsVerified 3 d agorb_3
Procedure
  1. 1Verify consent field coverage above 95%
  2. 2Draft messages, never send directly
  3. 3Request human approval for first 50 sends
  4. 4Record opt-out handling evidence
Known failure modes
  • Missing consent proof — never autonomous
  • PHI in log output — hard stop
Harbor CPA Group

Document intake classification

5 validated runsVerified 4 d agorb_4
Procedure
  1. 1Pull new intake items from all three channels
  2. 2Classify by document type with deterministic rules first
  3. 3Route unclassified items to human queue
  4. 4Send acknowledgement from approved template
Known failure modes
  • Scanned images below 200 dpi — route to human queue