AIOS playbooks for work that needs proof.

Playbooks are scoped operating recipes: what Atlas checks, what it builds, what proof is required, and what stays gated until the right policy exists.

Website meaning

AI SEO Visibility Playbook

Audit one public page, clarify the buyer path, tighten CTA/contact flow, and document what changed.

Crawl, score, repair, retest, teach.View Playbook
Lead response

Follow-Up Starter Playbook

Turn one inbound path into a clean first-response and handoff workflow without sending until policy is green.

Intake, draft, review, gate, watch.View Playbook
Build and package

Project Factory Launch Playbook

Move a scoped idea through ProjectSpec, build, QA, proof, and locked delivery.

Spec, build, verify, package, handoff.View Playbook
Repo assistance

Code Intelligence Playbook

Create a safe code-reading and BuildSpec workflow for local agent teams without broad apply.

Scope, inspect, propose, test, review.View Playbook
Payments and delivery

Revenue Guardrail Playbook

Map checkout, proof, delivery lock, and customer handoff rules before changing live payment flows.

Map, protect, verify, unlock only with proof.View Playbook
Agent build

Custom Agent Workflow Playbook

Define an AgentSpec, tool boundaries, proof contract, memory policy, evals, and rollback before production use.

Scope, AgentSpec, eval, package, monitor.View Playbook

What every playbook includes

Each playbook is built to keep the work inspectable: scope, inputs, agents, deliverables, proof, approval gates, rollback, and handoff.