ProjectSpec
Defines the problem, owner, deliverables, proof, rollback, and next action.
- What you get: Scope, deliverable list, proof checklist, and next decision.
- What Atlas needs: A target outcome and enough public context to avoid guessing.
Outcome-ready projects, not loose AI experiments.
Project Factory converts an idea, blocker, website, or client opportunity into a ProjectSpec with deliverables, allowed actions, blocked actions, proof, QA, and delivery status.
Build and review
Agents can draft copy, pages, checklists, packs, and workflows. Apex and Proof review before handoff.
- What you get: Drafts, QA notes, and review-ready artifacts.
- What is gated: Deploys, sends, posts, and code apply need separate proof.
Locked delivery
Delivery packages can be prepared, but unlocks require payment and delivery proof.
- What you get: A package that can be reviewed before release.
- What is gated: Checkout redirects are not delivery proof.
Custom Agent Build lane
Atlas can evaluate a public workflow or client-provided system context, create an AgentSpec, define tools and boundaries, run fixture tests, and package the result with docs, SKILL.md or AGENTS.md guidance, a runbook, and a proof contract where applicable.
- Evaluate the client website or workflow.
- Identify the task the agent should handle.
- Create an AgentSpec and allowed/blocked tool list.
- Define memory, proof, approval, handoff, and rollback rules.
- Build the workflow pack or agent scaffold.
- Test with fixtures and package privately after proof.