Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD across contents and paths, upstream package/repo coordinates -> @golem15/msd-core and golem15com/msd-core. Deep links into upstream history, sibling upstream packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is. Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line, package/plugin identity, regenerated lockfile, install-tree fixtures, derived registries and benchmark baseline; migration checksum baseline re-locked (MSD keeps its own install state, so no install had applied the old sums); sort-order and regex-escaped expectations in tests adjusted.
17 lines
856 B
Markdown
17 lines
856 B
Markdown
---
|
|
id: 111
|
|
title: Architectural Responsibility Mapping
|
|
group: v1.36.0 Features
|
|
---
|
|
|
|
**Command:** `/msd-plan-phase` (enhanced research step)
|
|
|
|
**Purpose:** During phase research, the phase-researcher now maps each capability to its architectural tier owner (browser, frontend server, API, CDN/static, database). The planner cross-references tasks against this map, and the plan-checker enforces tier compliance as Dimension 7c.
|
|
|
|
**Requirements:**
|
|
- REQ-ARM-01: Phase researcher produces an Architectural Responsibility Map table in RESEARCH.md (Step 1.5)
|
|
- REQ-ARM-02: Planner sanity-checks task-to-tier assignments against the map
|
|
- REQ-ARM-03: Plan checker validates tier compliance as Dimension 7c (WARNING for general mismatches, BLOCKER for security-sensitive ones)
|
|
|
|
**Produces:** `## Architectural Responsibility Map` section in `{phase}-RESEARCH.md`
|