Skip to content

Add delivery plan: slice the build into parallel specifications#2

Merged
IanMayo merged 1 commit into
mainfrom
claude/root-docs-architecture-noy83e
Jul 11, 2026
Merged

Add delivery plan: slice the build into parallel specifications#2
IanMayo merged 1 commit into
mainfrom
claude/root-docs-architecture-noy83e

Conversation

@IanMayo

@IanMayo IanMayo commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

What this adds

A new candidate canonical document, assay-delivery-plan.md, that reads the existing root-level documents (assay-scaffold.md, assay-build-plan.md, assay-ui-design.md) and answers the question: how do we deliver this, and where can work run in parallel?

It does not re-sequence the build plan or introduce methodology (that stays in the register, DEC-2). It translates the seven stages into spec-kit-shaped slices and makes the implicit dependency structure explicit.

Key content

  • How we deliver (§1) — three facts that set the shape: four canonical documents are declared but unauthored and gate almost everything; the scorer is the delivery linchpin (DEC-10); the front end is a separable lane (DEC-5).
  • The specification series (§2) — five document slices (D1–D5: register, knowledge-model, seam-contract, vignette, architecture) and sixteen build specifications (SPEC-01…16), each mapped to its build-plan stage, dependencies, and DEC-11 research note. Exit criteria become the spec-kit acceptance scenarios.
  • Dependency graph & critical path (§3) — a Mermaid graph (pinned theme, per-subgraph styles, TB per scaffold §5); critical path D2 → D3 → SPEC-05 → SPEC-06 → SPEC-07 → SPEC-15 → SPEC-16, with float called out (generator SPEC-08 is sacrificial scope).
  • Parallel-working plan (§4) — six swimlanes with barriers marked; where parallelism is genuine (front-end vs services, the five-wide depth fan-out behind the scorer, the three analysis slices) and where it is false and must not be attempted (generator ahead of scorer, code ahead of its research note, surfaces before the gate). A wave structure with per-wave exit gates.
  • Open questions that gate slicing (§5) and next step (§6) — how to instantiate each slice via the installed Spec Kit toolchain.

Notes for review

  • Placed at repo root to match the existing assay-*.md convention and the task framing ("root level documents"); it is marked a candidate addition to the canonical set, not yet ratified.
  • No decisions are originated here — it cites DEC-4/5/7/10/11 and defers the four gating open questions to the register.

🤖 Generated with Claude Code


Generated by Claude Code

Translate the seven build-plan stages into spec-kit-shaped
specifications, surface the dependency graph the stage-linear
narrative leaves implicit, and identify genuine parallel-working
lanes. Names five prerequisite document slices (register,
knowledge-model, seam-contract, vignette, architecture) and sixteen
build specifications, with the scorer (SPEC-07) identified as the
critical-path linchpin and the depth theses fanning out behind it.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K11vXz8rcRbRio7N6ps1s6
@IanMayo IanMayo force-pushed the claude/root-docs-architecture-noy83e branch from b024804 to 728a39a Compare July 11, 2026 17:57
@IanMayo IanMayo merged commit cfca679 into main Jul 11, 2026
@IanMayo IanMayo deleted the claude/root-docs-architecture-noy83e branch July 13, 2026 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants