KokoAI Academy · Advanced enterprise architecture practice
OpenAI Architect Professional
Design, govern and operate enterprise decision-support systems built with OpenAI. Build evidence across seven domains spanning runtime choices, data and execution controls, evaluation, economics, stakeholder decisions, and platform operations.
Start the first domainIndependent KokoAI training · Practice and assessment status
Original Koko educational content and scenario questions. This is not an OpenAI-issued certification, an official exam, a claim of credential equivalence or a calibrated readiness probability. Public practice, local completion and transcript progress do not issue trusted credentials. Private forms are held-out candidates requiring separate expert review, secure server-side administration, exposure controls and pilot validation before scored use. Critical failures cannot be averaged away. Human review is required for architecture evidence.
Prerequisites, outcomes and downloads
Bring this experience
- Demonstrated implementation competence through the OpenAI Developer track or comparable reviewed work.
- Demonstrated architecture competence through Architect Foundations or comparable design and failure-analysis evidence.
- Ability to read typed interfaces, event/state tables, service metrics and basic cost calculations.
- Experience with identity, enterprise data handling and operational ownership; unknown policy questions must be escalated to accountable owners.
What you will be able to do
- Defend an enterprise architecture using measurable requirements, explicit trust/state boundaries and rejected alternatives.
- Select runtime, model and context strategies using current official capability evidence and workload-specific evaluation.
- Prove authorization, tenancy, approval and idempotency properties under negative and recovery scenarios.
- Govern release using independent quality/control gates, calibrated review, full workflow economics and known lifecycle limits.
- Operate a service with data obligations, stakeholder ownership, telemetry, incident response, rollback and controlled upgrade evidence.
- Revise the architecture and release recommendation coherently when a material requirement changes.
Domain 1 of 7 · Enterprise solution design
AP-1 · About 150 minutes suggested
Enterprise solution design
Translate an enterprise decision into owned runtime, integration and nonfunctional controls.
Your objectives
- AP-1.1: Trace measurable business requirements and constraints to architecture decisions, controls, owners and verification evidence.
- AP-1.2: Compare managed Agents API, application-owned Agents SDK and direct Responses deployment against state, integration and data constraints.
- AP-1.3: Defend nonfunctional budgets, dependency boundaries and degraded modes with explicit acceptance tests and revisit triggers.
From outcome to control contract
An enterprise architecture begins with decisions and obligations. Draw a line from the business outcome to the decision the system supports, the person accountable for that decision, the permitted data and actions, and the evidence that makes the decision reviewable. A faster answer is not automatically a better business process. Record baseline review time, rework, incorrect recommendations, reviewer effort and the protected outcomes that cannot deteriorate. Mark unknown baselines as discovery work with owners and dates. Do not manufacture a baseline to make the proposal persuasive.
For the synthetic supplier-disruption service, procurement wants a draft impact brief within ten minutes after a feed event. The model may summarize supplier evidence and suggest escalation; a deterministic ledger calculates exposure and a procurement lead authorizes any supplier communication. Requirement R1 therefore traces to a queue deadline, model budget, evidence freshness check, manual route and measured event-to-brief time. Requirement R2, no cross-tenant evidence, traces to identity-bound retrieval, server checks, negative tests and Security ownership. This is more useful than a diagram labeling everything secure. A feature-first alternative can accelerate discovery but often leaves conflicting requirements unresolved. A control-first review must still test whether its controls preserve a useful product. The failure mode is an attractive architecture with no accountable acceptance decision.
- Choose an agent runtime · Checked 2026-11-17
- Production best practices · Checked 2026-11-17
- Safety best practices · Checked 2026-11-17
Runtime ownership and deployment choice
Treat runtime selection as an allocation of work, state and risk. Current OpenAI guidance distinguishes a managed Agents API running a Codex harness, an Agents SDK running inside your application, and a direct Responses integration. These are separate resources and execution models. Managed infrastructure can reduce orchestration work, while your organization still owns business identity, authorization, data eligibility, tool contracts and release acceptance. SDK deployment gives the application control over its loop integration, storage and approval handling, with corresponding operational work. Direct integration is attractive for a bounded synthesis step whose control flow is already deterministic. More control is valuable only when a requirement needs it.
For the supplier service, compare all three against a decision matrix: where data may be processed, whether required integrations are supported, session cleanup, resumability, observability, operational staffing and migration cost. Select a deterministic application workflow with a direct model synthesis call for the first release because event handling, exposure calculation and approval are already explicit. An SDK can become appropriate when evidence gathering needs a bounded iterative loop. A managed runtime remains viable only after its precise feature and data obligations are reviewed. Rejecting a runtime today is not a claim of permanent inferiority. State a measurable revisit trigger, such as repeated retrieval failures that a tested bounded search loop resolves. Never imply that choosing a managed runtime transfers the enterprise's accountability to the provider.
- Choose an agent runtime · Checked 2026-11-17
- Data controls in the OpenAI platform · Checked 2026-11-17
- Using tools · Checked 2026-11-17
Nonfunctional budgets as executable decisions
A nonfunctional requirement needs a measurement boundary, population, time window, target, owner and failure behavior. Define event-to-reviewable-brief latency separately from model latency and reviewer queue time. A model can return quickly while a stale search index produces an unusable recommendation. Allocate an end-to-end budget across ingestion, entitlement checks, retrieval, synthesis, validation and handoff; test the combined path because percentile budgets cannot simply be added as if every component's worst case occurs independently. Keep capacity assumptions and synthetic estimates clearly labeled until measured.
The supplier design allows a bounded retrieval timeout and a manual evidence route when the authoritative feed is unavailable. It never substitutes an older supplier exposure number without marking its age and requiring the reviewer to reconcile it. Under a ten-minute scenario deadline, queue age triggers early degradation before the deadline is missed. Compare fail-closed refusal, partial evidence briefs and delayed full answers by business consequence. Read-only partial service may be acceptable when missing sections are explicit; unverified supplier communication is not. Acceptance evidence includes an unavailable-policy drill, tenant-mismatch rejection and a backlog exercise, rather than only a successful demo. A release decision records unresolved constraints and risk acceptors. Review this domain by tracing a single requirement through your lab artifacts. Watch plan: present the requirement table, animate its path through enforcement points, then show the failed-dependency view and the decision owner who responds.
- Production best practices · Checked 2026-11-17
- Latency optimization · Checked 2026-11-17
- Data controls in the OpenAI platform · Checked 2026-11-17
