MetrAIyux 0S business automation Runbook

Operator Runbook

How to run the site as a lightweight autonomous business.

Use the Site Operator Brain as the front-door conductor. It routes requests to cabinet brains, queues action receipts, and forces human escalation where authority is required.

Daily operating rhythm

  1. Check new buyer/client/candidate/vendor messages.
  2. Paste each message into the Autonomous Command console.
  3. Export the event/task JSON at the end of the session.
  4. Review tasks requiring human approval.
  5. Move validated items into AE, Client OS, Recruiting, Proof, or Governance pages.
  6. Create proof receipts before publishing claims or saying work is complete.

Escalation rules

The system must escalate before legal advice, incorporation filings, contract signature, hiring or firing, payroll, banking, payment movement, regulated compliance decisions, or irreversible client promises.

Cloudflare phase path

Phase 1: Static

Use browser-local routing and JSON export.

Phase 2: Worker API

Deploy `/api/site-operator/*` endpoints.

Phase 3: KV

Persist event/task receipts.

Phase 4: Queue

Process tasks asynchronously.

Phase 5: Durable Object

Add coordinated live rooms only when needed.

Phase 6: Workers AI

Add edge generation after routing/proof is stable.