Macro 3D Playbook court with an AI agent paused at a human approval gate.
Agent Foundation One role · one job · one owned repository

Build an agent you can keep building.

For builders and operating teams with an idea, prototype, or stalled Codex project: we deliver one useful capability in your GitHub repository, establish the data, tools, policy, tests, and runbook around it, and onboard you to continue in your own environment. Production access and operation are promoted separately.

Bring your agent project See what the foundation includes
  • Unit 1 role · 1 job
  • Delivery Working foundation
  • Ownership Client repository
  • Continuation Codex-ready
What ships

Bound the job. Build the capability. Exercise the handoff.

Agent Foundation is a scoped CREATE SOMETHING Build for teams that already have a real agent project. The workflow and infrastructure stay underneath; your team receives a working, inspectable system it can continue with Codex.

01 / 03 One role and one useful capability

Start with the work the agent must perform.

Bring the repository or prototype, the role the agent serves, one representative input, and an acceptable result. We name what the agent may read, propose, change, and must stop before implementation expands.

Receipts
named ownerrepresentative caseauthority boundary
02 / 03 A working vertical slice in your repository

Deliver the capability and the system around it.

We implement the data path, required tools or MCP surface, agent instructions, policy gates, golden cases, and runbook for one end-to-end capability. Unavailable production dependencies remain visibly blocked or bound to approved development fixtures.

Receipts
working capabilitytests and stop casesknown limits
03 / 03 A handoff your team exercises

Make one bounded change before the handoff closes.

Your team uses Codex in its own environment to inspect the project, run the verifier, make one agreed change, and rerun the relevant check. The exercise proves the continuation path—not every future change or production use.

Evidence
  • documented bootstrap
  • bounded continuation change
  • verifier rerun

Ownership and authority

The foundation is working. Production is a promotion.

Your team keeps the repository, source, schemas, instructions, policies, tests, runbook, known limits, and project history. No hidden CREATE SOMETHING account or undocumented credential is required for the accepted development path.

Database

State your agent can understand.

Schemas, fixtures or approved development bindings, state ownership, and data assumptions for the bounded capability.

Automation

Tools your agent can use.

The executable path, required tools or MCP surface, deterministic checks, and explicit blocked actions.

Judgment

Policy that decides when to act or stop.

Instructions, approvals, stop conditions, evaluation cases, and uncertainty behavior stored as inspectable artifacts.

Stage 1 · Agent Foundation

Continuation-ready in the accepted development path.

  • One useful end-to-end capability
  • Client-owned repository, source, tests, and runbook
  • Codex onboarding and one bounded continuation change
  • Working, blocked, unknown, and next states recorded
Stage 2 · Production Promotion

Live authority and operation are separately scoped.

  • Production credentials, bindings, and data migration
  • Deployment, rollback, monitoring, and recovery
  • Live integration and negative-path verification
  • Named operator or real-user acceptance

Foundation pricing is quoted after fit. Deployment, hosting, live writes, monitoring, signing, distribution, ongoing managed operation, and real-user acceptance are not implied. If the accepted capability should go live, Production Promotion receives its own owner, authority, rollback plan, and verification scope. Review the full service path or, if the application already exists and only needs a governed workflow contract, inspect the Control Compiler Integration.

Foundation fit

Bring the repository and one job for the agent.

Share the project or prototype, the role the agent serves, one representative input, an acceptable result, and the intended Codex environment. We will return a fit decision and the proposed Foundation boundary before implementation is quoted.

Bring your agent project Start with Map
Owner
Builder + capability owner
Authority
Approve one role, job, and boundary
Proof
Repository + verifier + continuation exercise
State
ready
  1. 01 / Project Show what you started

    Bring the repository, prototype, or current working artifact.

  2. 02 / Job Name one useful capability

    Define the role, representative input, acceptable result, and stop boundary.

  3. 03 / Fit Choose the smallest responsible path

    Foundation fit, Map first, Harness or MCP-only, Production scope, or not a fit.