Learning pathsPricingChecking sign-in…
← ML curriculum

AISD-002 · DESIGN PRACTICE

Practice: Agent workflow platform

Draft the complete decision system before revealing the guidance. Use a 45-minute rehearsal budget and adapt it to the interviewer’s direction.

Preserve eligibility, available-at-decision inputs, mature labels, bounded work and compatible releases. Explain alternatives and test a normal, boundary and failure case.

Your practice draft

Design a multi-tenant agent workflow platform that can plan and execute customer operations using internal tools. Include a high-risk action requiring human approval, durable recovery, retries, cancellation and a clear policy boundary. Explain why you would or would not use multiple agents.

Saved locally on this device. The worked answer does not score your draft. Existing lesson notes and completion are separate.

Progressive hints

Hint 1

Start by separating the model's proposal from the deterministic execution authority.

Hint 2

Define typed tool contracts, tenant-scoped capabilities and side-effect classes.

Hint 3

Draw the durable task/step state machine and transactional outbox.

Hint 4

Explain idempotency and reconciliation after an ambiguous external timeout.

Hint 5

Bind approval to the exact action payload and reauthorize before execution.

Hint 6

Add tracing, trajectory evaluation, budgets and multi-agent limits.

Self-review evidence

For each criterion, record Missing, Prompted, Independent or Adaptive reasoning. No automated scoring or offer prediction is provided.

  • Model and executor have separate authority boundaries.
  • Tool contracts are typed, versioned and least-privilege.
  • Task and step state are durable and recoverable.
  • Retries are bounded; side effects are idempotent or reconciled.
  • Approval is bound to exact payload and rechecked at execution.
  • Cancellation, deadlines and backpressure are explicit.
  • Tenant isolation and memory governance are enforced server-side.
  • Evaluation covers intermediate actions, safety and task outcomes.
Reveal worked design guidance

Use an authenticated Task API to persist a task and outbox event. A planner emits a bounded structured plan. The policy service validates allowed tools, schemas, tenant/resource scope, deadlines and risk. The orchestrator persists step transitions and dispatches typed calls to leased workers. Adapters reauthorize, use scoped capabilities and stable idempotency keys. High-risk actions pause at an approval gate bound to the canonical payload hash; after approval, reauthorize and verify the resource before writing. Persist tool outcomes and audit evidence. On timeout, reconcile by operation key before retry. Cancellation stops future steps and reconciles in-flight writes. Start with one orchestrator; introduce sub-agents only for bounded parallel work, under a coordinator budget and deterministic merge.

Open the complete worked design in a new tab →

The new tab keeps this draft visible. Save it on this device before closing the page.