website: regenerate reference pages for it.39–it.41 concerns

Run scripts/generate-reference.py to surface the +25 cross-cutting
concerns, the artifact-impact contract, the verification exit gate, and
the converge-loop additions on the site. 31 new pages, 42 updated.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: easel

website/content/artifact-types/build/implementation-plan.md

@@ -16,7 +16,7 @@ test-plan context into bounded implementation slices with dependencies,
 validation gates, and closeout evidence.
 
 It is not the tracker. The runtime owns issue state and execution. This artifact
-defines the intended build shape so DDx beads or another runtime can execute
+defines the intended build shape so the runtime's work items can execute
 without inventing scope, ordering, or validation rules.
 
 ## Example
@@ -32,11 +32,11 @@ ddx:
     - example.technical-design.depositmatch.upload-csv
     - example.story-test-plan.depositmatch.upload-csv
   review:
-    self_hash: 8f48b07ab604fe52786de7648f7ab37da251cfade0ea38bb4e802082d4f977de
+    self_hash: c470ce1b656f474335d2b2ec376a3e41e3389d5b83c7fcc1b350890b50a42d7c
     deps:
-      example.story-test-plan.depositmatch.upload-csv: ea5f25266c2652513d7c3623b18bb3b8f9ac0058379e1edcfe305107bdf6a11e
+      example.story-test-plan.depositmatch.upload-csv: 20aed2c4e248a67b448b0528b49ae9b2724d5045879ddcda655ad220d1c276ed
       example.technical-design.depositmatch.upload-csv: 064c51468da1d444da9c6f65d6c2502487724ac315fa3e6c50f9bbeffd3d69b9
-    reviewed_at: "2026-05-15T04:11:24Z"
+    reviewed_at: "2026-05-26T02:56:15Z"
 ---
 
 # Build Plan
@@ -76,7 +76,7 @@ or match generation.
 
 ## Issue Decomposition
 
-Story-level work is tracked via `ddx bead` in `.ddx/beads.jsonl`.
+Story-level work is tracked as work items in the runtime's work-item store.
 
 **Per-issue requirements**:
 
@@ -155,7 +155,7 @@ test-plan context into bounded implementation slices with dependencies,
 validation gates, and closeout evidence.
 
 It is not the tracker. The runtime owns issue state and execution. This artifact
-defines the intended build shape so DDx beads or another runtime can execute
+defines the intended build shape so the runtime's work items can execute
 without inventing scope, ordering, or validation rules.
 
 ## Reference Anchors
@@ -165,6 +165,13 @@ Use this local resource summary as grounding:
 - `docs/resources/google-small-cls.md` grounds small, reviewable,
   rollback-friendly implementation slices with related tests.
 
+## Active Concerns
+
+For each concern selected in `docs/helix/01-frame/concerns.md`, apply its declared
+`## Artifact Impact` (from `workflows/concerns/<name>/concern.md`) to THIS build plan — realize the
+IMPLEMENTATION_PLAN-level obligations it names (relational-data-modeling -> migration steps; resilience -> guard wiring; usage-metering -> metering wired on the real path). A selected concern whose Artifact Impact names IMPLEMENTATION_PLAN
+but leaves no trace here is drift (reconcile-alignment Concern->Artifact Realization check).
+
 ## Storage Location
 
 `docs/helix/04-build/implementation-plan.md`
@@ -191,12 +198,13 @@ Use this local resource summary as grounding:
 | Design or interface decisions | Solution Design / Technical Design / Contract / ADR |
 | Exact story tests and fixtures | Story Test Plan |
 | Build slice order, dependencies, and validation gates | Implementation Plan |
-| Assignee, live status, claim, execution logs | DDx bead or runtime issue |
+| Assignee, live status, claim, execution logs | runtime work item or issue |
 
 ## Template
 
-`.ddx/plugins/helix/workflows/activities/04-build/artifacts/implementation-plan/template.md`
-For tracker conventions see `ddx bead --help`.</code></pre></details></td></tr>
+`workflows/activities/04-build/artifacts/implementation-plan/template.md`
+For tracker conventions see the runtime&#x27;s install guide (DDx:
+`docs/install/ddx.md`).</code></pre></details></td></tr>
 <tr><th>Template</th><td><details><summary>Show the template structure</summary><pre><code>---
 ddx:
   id: implementation-plan
@@ -224,7 +232,7 @@ ddx:
 
 ## Issue Decomposition
 
-Story-level work is tracked via `ddx bead` in `.ddx/beads.jsonl`.
+Story-level work is tracked as work items in the runtime&#x27;s work-item store.
 
 **Per-issue requirements**:
 - Labels: `helix`, `activity:build`, `kind:build`, `story:US-{story-id}`

website/content/artifact-types/deploy/release-notes.md

@@ -213,7 +213,7 @@ and `runbook`), not inside release notes.
 - [ ] Breaking changes, migration guidance, and known issues are clear when relevant
 - [ ] References point readers to deeper docs or support paths when needed
 
-Use the template at `.ddx/plugins/helix/workflows/activities/05-deploy/artifacts/release-notes/template.md`.</code></pre></details></td></tr>
+Use the template at `workflows/activities/05-deploy/artifacts/release-notes/template.md`.</code></pre></details></td></tr>
 <tr><th>Template</th><td><details><summary>Show the template structure</summary><pre><code>---
 ddx:
   id: release-notes

website/content/artifact-types/deploy/runbook.md

@@ -236,7 +236,7 @@ release coordination plan.
 - [ ] Routine operational procedures are explicit or the document says none exist
 - [ ] Escalation and communication paths are explicit
 
-Use the template at `.ddx/plugins/helix/workflows/activities/05-deploy/artifacts/runbook/template.md`.</code></pre></details></td></tr>
+Use the template at `workflows/activities/05-deploy/artifacts/runbook/template.md`.</code></pre></details></td></tr>
 <tr><th>Template</th><td><details><summary>Show the template structure</summary><pre><code>---
 ddx:
   id: runbook

website/content/artifact-types/design/_index.md

@@ -25,4 +25,5 @@ Decide how to build it. Capture trade-offs, contracts, and architecture decision
   {{< card link="/artifact-types/design/security-architecture/" title="Security Architecture" subtitle="Design-level security architecture that maps trust boundaries, controls, and security decisions to implementation and testing." >}}
   {{< card link="/artifact-types/design/tech-spike/" title="Technical Spike" subtitle="Time-boxed investigation that answers one technical question with evidence before implementation." >}}
   {{< card link="/artifact-types/design/data-architecture/" title="Data Architecture" subtitle="Captures the data pipeline architecture, medallion topology, streaming vs batch semantics, processing frameworks, governance model, and quality contracts. The…" >}}
+  {{< card link="/artifact-types/design/design-system/" title="Design System" subtitle="The per-project interface-system instance: the concrete UX/design-system decisions this app commits to. It captures the navigation model and active-state conve…" >}}
 {{< /cards >}}

website/content/artifact-types/design/adr.md

@@ -118,7 +118,7 @@ search or document store in v1
 <table class="helix-reference-table">
 <tbody>
 <tr><th>Activity</th><td><a href="/reference/glossary/activities/"><strong>Design</strong></a> — Decide how to build it. Capture trade-offs, contracts, and architecture decisions.</td></tr>
-<tr><th>Default location</th><td><code>docs/helix/02-design/adrs/ADR-{id}-{name}.md</code></td></tr>
+<tr><th>Default location</th><td><code>docs/helix/02-design/adr/ADR-{number}-{decision-name}.md</code></td></tr>
 <tr><th>Requires</th><td><em>None</em></td></tr>
 <tr><th>Enables</th><td><em>None</em></td></tr>
 <tr><th>Informs</th><td><a href="/artifact-types/design/solution-design/">Solution Design</a><br><a href="/artifact-types/design/technical-design/">Technical Design</a></td></tr>
@@ -128,6 +128,15 @@ search or document store in v1
 Write a compact ADR that captures one architecture-significant decision, the
 alternatives, and the consequences.
 
+## Storage Location
+
+Store at: `docs/helix/02-design/adr/ADR-NNN-&lt;decision-name&gt;.md` — **one decision
+per file**. Naming is canonical and checkable: uppercase `ADR`, a **zero-padded
+3-digit** sequential number, then a kebab-case decision name (e.g.
+`ADR-001-modular-monolith.md`, `ADR-007-auth-tenant-isolation.md`). Do **not** use
+lowercase `adr-` or 4-digit numbers, and do **not** lump multiple decisions into
+one record. reconcile-alignment flags non-canonical names and lumped ADRs.
+
 ## Purpose
 
 An ADR is the **single-decision record** for architecture-significant choices.
@@ -156,6 +165,23 @@ Use these local resource summaries as grounding:
 - Use one ADR per decision. If the decision has independent parts, split it.
 - Treat accepted ADRs as history. New decisions supersede old records instead
   of rewriting them.
+- **Do not accept a decision whose design-defining facts are assumed.** A
+  decision&#x27;s design-defining facts (API shape, data model, pricing/cost
+  semantics, security/permissions, operational guarantees, or work decomposition)
+  must be **evidenced** — by an operator statement, a governing artifact, an
+  existing implementation, a docs/API proof, or a completed spike — not by model
+  familiarity, and not because a mechanism was picked or a provider named.
+  Choosing a provider and deferring its live integration does **not** evidence the
+  decision. If a design-defining fact is assumed, the ADR must cite **spike
+  evidence**, record a **blocked-spike rationale**, or carry an explicit
+  **provisional-risk** note (what is assumed, what could invalidate it, and that
+  the assumption is reversible/non-blocking). See the anti-reframe check in
+  `workflows/references/concern-resolution.md` (step 3a). An operator-marked
+  &quot;spike/unknown&quot; may not be accepted as a settled ADR without **spike evidence, a
+  blocked-spike rationale, or an explicit provisional-risk note**. A
+  **business/product** unknown a technical spike can&#x27;t answer (e.g. a pricing
+  model) → record **guidance-needed** or a blocked spike rather than forcing a
+  technical spike or accepting an assumed decision.
 
 ## Boundary Test
 
@@ -179,7 +205,9 @@ ddx:
   id: ADR-XXX
 ---
 
-# ADR-[NUMBER]: [Title]
+# ADR-NNN: [Title]
+&lt;!-- Filename: ADR-NNN-&lt;decision-name&gt;.md — uppercase ADR, zero-padded 3-digit, one decision per file. --&gt;
+
 
 | Date | Status | Deciders | Related | Confidence |
 |------|--------|----------|---------|------------|