Skip to main content
    OpenAI learning tracks

    KokoAI Academy · Advanced

    OpenAI Architect Foundations

    An applied KokoAI Academy track for choosing and defending OpenAI system boundaries, evidence contracts, and operating tradeoffs.

    Start the first domain
    5 domainsPractice and applied labsSources reviewed 2026-11-17
    Independent KokoAI training · Practice and assessment status

    Original Koko educational practice and human-reviewed architecture work; not an OpenAI-issued credential or a calibrated certification exam. Held-out candidate forms require separate qualification and trusted scoring before use. Critical authorization failures must not be averaged away.

    Prerequisites, outcomes and downloads

    Bring this experience

    • Experience building or reviewing software systems and APIs
    • Familiarity with authentication, testing, and version control

    What you will be able to do

    • Defend a runtime and orchestration decision with evidence.
    • Design enforceable tool, context, approval, and state boundaries.
    • Evaluate and review a system using reproducible control tests and quality evidence.

    Domain 1 of 5 · Architecture and orchestration

    AF-1 · About 150 minutes suggested

    Architecture and orchestration

    Choose the smallest runtime and coordination pattern that meets a workload’s requirements.

    Your objectives

    • AF-1-O1: Compare deterministic, single-agent, and multi-agent designs against explicit requirements.
    • AF-1-O2: Select direct Responses integration, application-owned Agents SDK, or managed Agents API and specify retained ownership.
    • AF-1-O3: Specify orchestration state, handoffs, and decision records that can be inspected and challenged.

    Compare deterministic, single-agent, and multi-agent designs against explicit requirements.

    Start with the work, not the number of agents. A deterministic workflow is a sequence whose transitions are application rules; use it when inputs, checks, and branches can be enumerated. A single agent can decide among permitted tools when the next useful step depends on interpreting evidence. Multiple agents introduce independent roles, handoffs, and coordination costs; they are justified only when decomposition, isolation, or specialized context improves a measured outcome enough to pay for those costs. None of these labels determines who can authorize an external action.

    For a synthetic evidence-review service, ingestion, tenant filtering, and final approval can remain deterministic while an agent identifies missing evidence and drafts a recommendation. A competing all-agent design makes authorization harder to audit, and a rigid pipeline may fail when documents differ. Record requirements as testable constraints: permitted sources, maximum acceptable turnaround, decision owner, error severity, and how exceptions reach a person. Compare options against the same cases, including missing evidence and a hostile document. A diagram is incomplete until it shows who owns each transition and what happens on failure.

    Select direct Responses integration, application-owned Agents SDK, or managed Agents API and specify retained ownership.

    OpenAI’s runtime guide distinguishes direct Responses integration, an application-owned Agents SDK runtime, and a managed Agents API. These are architectural choices rather than interchangeable names. Direct integration offers the application explicit control over calls and tool loops; that control also means implementing and operating the required orchestration. The Agents SDK supplies an application-owned orchestration layer for agent patterns, while the managed Agents API offers a managed runtime. Confirm current capabilities and deployment constraints in the linked guide before committing, because product interfaces change.

    Use a decision record that separates a provider capability from a workload assumption. For example, compare required control over execution, existing operational expertise, deployment requirements, tool connectivity, recovery needs, and observability. A managed runtime can reduce some runtime plumbing but does not transfer business accountability, authorization policy, data classification, or acceptance testing to the provider. An SDK does not automatically make external tools safe. Direct calls do not by themselves provide a durable workflow. Prototype the hardest integration before treating a capability as proven, and include migration and rollback costs in the decision.

    Specify orchestration state, handoffs, and decision records that can be inspected and challenged.

    Draw an execution path with a durable request identifier, inputs, outputs, owner, and failure transition at every boundary. Distinguish the model’s proposed next step from the application’s decision to execute it. A handoff must carry only the task, scoped evidence references, constraints, and correlation identifiers needed by the next participant. The receiving component should validate those fields, apply its own authorization, and record what it accepted. Shared mutable scratchpads can be convenient, but create unclear provenance and accidental disclosure; a scoped handoff makes the tradeoff visible.

    For example, the intake service records request 42 and an evidence snapshot; an investigator proposes a search; the tool adapter checks the requester’s scope; the reviewer sees a recommendation with evidence and accepts or rejects it. An architecture decision record should state alternatives, assumptions, measurable acceptance tests, consequences, and a trigger for reconsideration. If specialist agents are proposed, test a single-agent baseline against the same frozen cases and include coordination latency and handoff failures. Do not claim a pattern is superior from a polished demonstration alone.

    Design review and transfer

    Architecture review is a comparison under uncertainty. Make a small decision matrix with columns for workflow complexity, control ownership, operational burden, failure isolation, and evidence required. Mark each cell as an observed result, a documented capability, or an assumption; do not mix them. In the evidence-review example, fixed intake and approval can surround either direct model calls or an agent runtime, so the runtime choice and the business workflow choice should be evaluated separately. A multi-agent candidate may help when independent specialists need different tools and contexts, but it adds authorization surfaces and handoff failure modes. Run an offline simulation of a missing evidence packet and show which component stops progress. Then change one requirement, such as a demand for independent review, and revisit the matrix. Record what new measurement would overturn the decision and the owner who will collect it. This is a design hypothesis until tested against a representative workload.