Implement the happy path

Implement the narrowest successful flow first: load validated config, accept one known fixture, perform one external or local operation, validate the result, and print or return the domain artifact. Avoid retries and clever abstractions until this path is observable.

Keep orchestration code boring. Dependencies are passed in, network calls are isolated in an adapter, and domain logic remains testable without credentials. The example uses a placeholder base URL because providers differ; set it to the documented endpoint of the provider you actually use.

For this project, execute will POST ${AI_BASE_URL}/chat/completions with messages and JSON-schema tool definitions. Use native fetch or the current official SDK, but isolate that choice in one file. Check HTTP status before parsing JSON, check the content type when appropriate, and parse the response into validated tool requests and grounded assistant replies. The expected terminal observation is: A request for ord_123 produces one validated lookup and a reply based only on its result.

Run the fixture from a tiny CLI and print a stable JSON summary rather than an entire provider response. A healthy run includes terminal status, elapsed milliseconds, and a safe result identifier. It must not print credentials, hidden instructions, or sensitive source content. Once this path works, commit the fixture conceptually as your regression oracle before adding retries.

export async function run(input: unknown, deps: Dependencies) {
  const started = performance.now();
  const validated = deps.parseInput(input);
  const raw = await deps.execute(validated); // POST `${AI_BASE_URL}/chat/completions` with messages and JSON-schema tool definitions
  const value = deps.parseOutput(raw);
  return { value, durationMs: Math.round(performance.now() - started) };
}

The code is intentionally provider-neutral at the adapter boundary. AI_BASE_URL and model names are environment placeholders, not invented services. If the topic uses MCP, install the current official SDK and verify its exported paths against its release documentation. If a provider offers an official SDK, it can replace fetch inside execute without changing the domain contract. Always inspect the real provider’s documented request and response fields before connecting credentials.

Debug from deterministic code outward. First print the parsed configuration with secret values replaced by [set]. Next run the parser against a local fixture. Then run the orchestration with a fake dependency. Only after those pass should you inspect the real boundary. Capture status, content type, request ID, elapsed time, and a redacted response shape. Do not “fix” malformed data with a permissive cast; save it as a failing fixture and decide whether the contract or adapter is wrong.

For this chapter, the fastest diagnostic is to assert that only an allowlisted function receives schema-validated arguments. When that assertion fails, stop before downstream work. Expected behavior is concrete: A request for ord_123 produces one validated lookup and a reply based only on its result. A different but plausible sentence is not enough if the structural and policy checks fail.

• One fixture runs end to end.
• The external response is validated before domain use.
• Expected output and terminal state are visible.
• Run npm run typecheck and npm test without provider credentials.
• Record expected terminal behavior beside the fixture so future changes remain reviewable.

A passing test is necessary but does not establish production quality. Review the fixture set for realistic distributions, stale assumptions, tenant boundaries, and expensive edge cases. When outputs are probabilistic, assert schemas, citations, chosen capabilities, stop reasons, and task rubric scores. Reserve exact string assertions for deterministic adapters and protocol framing.