ADR: introduce docs/history/, merge 0011+0018, prune migration cruft
- CLAUDE.md: add ADR Lifecycle subsection (superseded → docs/history/, immutable numbering, no renumber) - ADR-0011: merge ADR-0018 content as "Address Model: LA" section alongside PA / VA; status notes VA model is currently implemented - ADR-0018 / 0029 / 0031: moved to docs/history/ with status updates (0018 merged into 0011, 0029 superseded by 0032, 0031 absorbed into 0001 rev 2) - ADR-0019: rewrite Context as PE-HBM connectivity decision (self-contained, no LA model framing) - ADR-0019/0020/0021/0023/0025/0027: Status Proposed → Accepted (code verified) and prune Implementation Notes / Affected files / Test strategy / "현재 상태" sub-sections describing pre-impl state - ADR-0024/0026: same migration-flavor cleanup; 0026 also drops D6 Migration and D8 docs-update sub-decisions - ADR-0030: status simplified (blocker ADR-0031 now superseded) - SPEC.md: R10 + §0.2 reflect PA / VA / LA model names - ADR-0008/0012/0013: refresh ADR-0011 subtitle in Links 21 files changed, 553 insertions(+), 1290 deletions(-). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -200,9 +200,10 @@ General fallbacks. Apply to anything not explicitly covered above.
|
||||
> Specific to this repo's domain (SIP/CUBE/PE topology, runtime API, sim_engine).
|
||||
> Replace this entire Part when adapting the framework to another repo.
|
||||
>
|
||||
> Contains **foundations** (Authority & Scope → Terminology → Mental Model →
|
||||
> Common Failure Modes) followed by **rules** (Non-Trivial, Verification Plan,
|
||||
> CLI, Derived Artifacts, runtime API / sim_engine Boundaries).
|
||||
> Contains **foundations** (Authority & Scope → Terminology → Terminology
|
||||
> Discipline → Mental Model → Common Failure Modes) followed by **rules**
|
||||
> (Non-Trivial, Verification Plan, CLI, Derived Artifacts, runtime API /
|
||||
> sim_engine Boundaries).
|
||||
|
||||
## Authority & Scope
|
||||
|
||||
@@ -215,6 +216,20 @@ General fallbacks. Apply to anything not explicitly covered above.
|
||||
- Do NOT silently change architecture.
|
||||
- The repository structure reflects architectural intent; Claude Code MUST respect existing module boundaries and file locations.
|
||||
|
||||
### ADR Lifecycle
|
||||
|
||||
- `docs/adr/` contains ADRs reflecting current implementation or
|
||||
work-in-progress designs.
|
||||
- `docs/history/` contains superseded ADRs as historical record.
|
||||
- When an ADR is superseded:
|
||||
1. The superseding ADR includes a "Supersedes ADR-NNNN" line.
|
||||
2. The superseded ADR's Status is set to "Superseded by ADR-MMMM".
|
||||
3. The superseded ADR file is **moved** (git mv) to `docs/history/`.
|
||||
- Cross-references between ADRs use the ADR-NNNN ID and remain
|
||||
valid regardless of file location.
|
||||
- ADR numbers are **immutable**; never renumber. Numbering holes
|
||||
from moved ADRs are expected.
|
||||
|
||||
## Terminology
|
||||
|
||||
- runtime API:
|
||||
@@ -224,6 +239,14 @@ General fallbacks. Apply to anything not explicitly covered above.
|
||||
- components:
|
||||
Device-side nodes modeling hardware behavior (IO_CPU, M_CPU, PE_CPU, routers, engines, etc.).
|
||||
|
||||
## Terminology Discipline
|
||||
|
||||
Use only terms established in SPEC.md, ADRs, existing notes, or code.
|
||||
Do not coin new terms (status labels, tiers, classifications, role names)
|
||||
without explicit user approval. When a needed term is missing or ambiguous,
|
||||
ask before introducing one. When proposing a rename, show the existing
|
||||
term and the proposed change side-by-side and wait for approval.
|
||||
|
||||
## Mental Model
|
||||
|
||||
The simulator is layered along **request flow**:
|
||||
@@ -270,6 +293,11 @@ If your change does any of these, STOP and reconsider.
|
||||
See *Authority & Scope* above.
|
||||
- **weakening tests to make Phase 2 pass** — fix the code, not the test.
|
||||
See *Part 1 → Phase 2 → Failure Path*.
|
||||
- **asserting from memory without source check** — quantitative
|
||||
architectural facts (topology counts, sizes, latencies, address widths,
|
||||
port arities) must be sourced from SPEC.md or a specific ADR before
|
||||
assertion. Memory is unreliable. If the source is silent, surface the
|
||||
gap rather than guessing.
|
||||
|
||||
## What Counts as "Non-Trivial"
|
||||
|
||||
|
||||
Reference in New Issue
Block a user