AI Operator Readiness Checklist
Before a business asks Rocky to do work, decide what should be watched, what should be remembered, what can be drafted, and what must wait for a human.
When this matters
This page is for operators who want Rocky to produce usable work without turning the system into a mystery box. Use it when you need a practical path, a clear verification step, and a boundary between suggestion and action.
The operating pattern
- Name the workflow. Describe the recurring job in one sentence.
- List the signals. Identify the inboxes, forms, files, calendars, feeds, or dashboards that matter.
- Define the memory. Separate durable facts from temporary task state.
- Choose approval gates. Mark customer, payment, legal, and account actions as review-only.
- Measure success. Decide what a good day-one output looks like.
Pre-flight checklist
- One named owner for approvals
- At least one live example request
- A list of systems Rocky may read
- A list of systems Rocky must not touch
- A way to verify the result
Common failure modes
- Too broad: “Automate my business” is not a workflow.
- No source of truth: Rocky cannot verify a task if nobody can identify the canonical record.
- Unsafe autonomy: High-risk actions should start as drafts or alerts, not automatic writes.
Verification
A page is not done because it was drafted. Verify the source, run the workflow, inspect the output, and record what changed. If a step touches money, customers, accounts, permissions, or private data, keep it behind an explicit human approval gate.