Workshop-to-Design Audit
A 15-tier pipeline that transforms workshop transcripts into verified requirements, solution design, and traceable work decomposition.
Discovery workshops produce transcripts. The Workshop-to-Design Audit turns transcripts into auditable, traceable deliverables — and then adversarially verifies every claim before a single work item is raised.
What it is
The Workshop-to-Design Audit is a 15-tier pipeline (T0 through T12) that transforms raw workshop transcripts into a complete consulting and delivery handoff: As-Is baseline, maturity assessment, business requirements document, solution design, and a traceable work decomposition register with Epic, Feature, and Story traceability to source evidence.
The pipeline runs in four suites. Suite 1 (As-Is Baseline) produces verified per-workshop analyses, consolidated synthesis across six document types, and slides. Suite 2 (Maturity Assessment) produces target-state overlays and future-state architecture. Suite 3 (Requirements and Design) produces an R-numbered business requirements document, a DD-nn solution design document, and — at Tier 10b — the Karpathy-6 adversarial verification gate that must be passed before work decomposition begins. Suite 4 (Work Decomposition) produces a three-tier SAFe feature register and a traceability register chaining every story back through design decision, requirement, gap finding, and source workshop section.
135 quality-gate checks govern the pipeline: 32 across Suite 1, 20 across Suite 2, 46 across Suite 3 (including 7 from the Karpathy-6 gate), 37 across Suite 4.
When you reach for it
The Workshop-to-Design Audit applies on any enterprise transformation engagement that starts with discovery workshops. It is the right methodology when the gap between what was said in workshops and what appears in requirements documents needs to be provably small (not assumed small), when a regulator or governance body requires traceability from business requirement to source evidence, or when the distance between discovery and delivery is long enough that drift and misattribution are plausible risks.
It is also the right methodology when the client’s own workshop outputs are the artefacts under review — the pipeline can enter at any tier, not only from raw transcripts.
What you ship
- A verified As-Is baseline — per-workshop analyses that have passed a faithfulness gate against the source transcripts, with every claim classified as GROUNDED, REASONABLY_INFERRED, UNGROUNDED, MISATTRIBUTED, or CONTRADICTED. Zero CONTRADICTED claims proceed to synthesis.
- A requirements and design package — a business requirements document with R-numbered requirements and a solution design document with DD-nn design decisions, both verified at Tier 10b against source gap analyses and workshop evidence using Karpathy-6 adversarial verification.
- A traceable work decomposition register — a three-tier feature register with stories classified as out-of-box, configurable, custom, or process, plus a full traceability chain: Workshop → Gap Finding → R-number → DD-nn → Feature → Story → Artefact.
Linked methodologies
The Tier 10b gate is a direct application of the Karpathy-6 Adversarial Verification methodology. It is the canonical worked example of how Karpathy-6 is consumed by a multi-tier pipeline. Any requirements document or solution design produced by this pipeline has been adversarially verified before it is handed to an implementation team.
Service Awareness feeds into the As-Is architecture layer of the pipeline — CSDM service models produced during or after workshops integrate directly into the Type A (Enterprise Architecture As-Is) synthesis document.
Start here
The Workshop-to-Design Audit is available as a standalone engagement for clients who have completed discovery but have not yet produced verified requirements. Bring your transcripts and any existing analysis. We enter the pipeline at the appropriate tier. Book a discovery conversation.