Lab 4 — Production Harness Capstone

Lab 4 — Production Harness Capstone

Fact-check status

Reviewed claim by claim on 2026-09-02 against the primary or official sources identified inline as S1 and S2. Recommendations are design guidance unless a cited standard makes them normative.

Key jargon

Term Plain-language meaning
Capstone An integrated project demonstrating multiple learned competencies. S1
End-to-end test A test exercising the system through its real external boundaries. S1
Failure injection Deliberately causing a dependency or step to fail to test recovery. S1
Release evidence Artifacts showing a candidate satisfied defined quality, safety, and operational gates. S1

Key concepts

Concept map

flowchart LR
    A["Define contract and threats"] --> B["Build bounded observable harness"]
    B --> C["Test normal adversarial and failure paths"]
    C --> D["Assemble evidence and release decision"]

Diagram semantics verified against S1 and S2 on 2026-09-02.

Goal

Build a synthetic support assistant that retrieves approved policy, drafts a response, proposes—but cannot directly perform—one reversible account action, and produces an evidence bundle.

Required components

Task/system contract, model adapter, context manifest, retrieval authorization, tool schema, effect preview, human approval, idempotency key, run state, checkpoint, trace, offline eval set, threat model, rollout, rollback, incident runbook, and cost budget. S1

Failure schedule

Test malformed model output, retrieval miss, poisoned document, permission denial, model timeout, tool timeout before effect, tool timeout after ambiguous effect, duplicate event, human rejection, and model-version change. S1

Pass criteria

Final reflection

Identify which value came from the model and which came from the harness. If the answer is “the model did everything,” the architecture is not yet understood. S1