Enterprise AI narrative Spec-Driven Context Engineering

Part 06 · Demo

A guided replay of a governed pipeline run.

Watch the supervisor walk a precomputed onboarding pipeline through six governed steps — retrieving evidence by lane, assembling scoped bundles, dispatching to domain agents, validating output contracts, and either advancing or halting at each gate. This is a replay, but it is built from actual runs I conducted with the system. Four recorded runs are available.

Click between the four full-pipeline replays here

Scenario 1 · ESCALATED

Legal blockers · ESCALATED

OptiChain submits a complete questionnaire indicating EU personal data exposure, but the GDPR Art. 28 DPA is missing and NDA execution is unconfirmed. The pipeline halts at STEP-03 and routes an escalation package to General Counsel.

  • Run statusESCALATED
  • Halted atSTEP-03 · Legal
  • Fast-trackINELIGIBLE
  • Blockers2
  • Escalation ownerGeneral Counsel

Summary

Below is a replay of a scenario in which intake is complete, but authoritative evidence reveals unresolved legal blockers. The pipeline reaches STEP-03, the legal agent emits an escalated status, and halts rather than continuing through conflicting or incomplete conditions.

Keyboard

Space play/pause · / step · R reset

Speed
STEP-01 · SupervisorComplete

Nothing begins without the questionnaire

Intake validation

Stage 1Source-aware retrieval
Waiting
direct_structured
1 source
indexed_hybrid

No sources used in this step.

non_retrieval

No sources used in this step.

Stage 2Gate decision
Waiting

Technical inspection · optional for tech-savvy audiencesClick any of the steps to see the full agent inputs/outputs

Final outputs · stakeholder-ready

What the escalation package contains

When the supervisor halts at STEP-03, this is the artifact that lands on the right desks. Determined items remain visible alongside named blockers and owners.

EscalatedEscalation package

Halted at

STEP-03

Fast-track

INELIGIBLE

Blockers

2

Final artifact emitted by

Supervisor (escalation package)

Routes to the named legal owners listed below.

Checklist · 4 items

  • Intake artifacts validated

    Owner

    Procurement Operations

  • ERP integration tier · UNCLASSIFIED_PENDING_REVIEW

    Architecture diagram + data-flow docs requested as follow-up.

    Owner

    IT Security · D. Nguyen

  • GDPR Art. 28 DPA execution

    DPA required by DPA-TM-001 row A-01; not on file.

    Owner

    Legal (General Counsel)

  • NDA execution

    No signed NDA on file; required by ISP-001 §12.1.4.

    Owner

    Procurement

Open blockers · human-owned action required

  • BLK-LEG-001

    Execute GDPR Art. 28 DPA

    Negotiate, draft, and execute a DPA covering EU personal data exposure before any data exchange occurs.

    Owner: Legal (General Counsel)Citation: DPA-TM-001 row A-01
  • BLK-LEG-002

    Confirm NDA execution

    Execute the master NDA and update questionnaire NDA status before sensitive information exchange.

    Owner: ProcurementCitation: ISP-001 §12.1.4

Stakeholder guidance · routed next steps

  • General Counsel

    Owns DPA blocker. Engage vendor counsel; target execution before next pipeline retry.

  • Procurement

    Owns NDA blocker. Drive vendor signature; update questionnaire `existing_nda_status` field once executed.

  • IT Security

    Owns the unresolved integration tier. Request architecture diagram from vendor; rerun classification when available.

  • Procurement / Business Owner

    Pause kickoff scheduling. Once Legal blockers clear, the pipeline can be restarted from STEP-03.