CR-2026-04-10: Case Studies Modularization

Change Request

Field	Value
CR ID	CR-2026-04-10-case-studies-modularization
Title	Case Studies Modularization — Partials, Page Shells, Granular Nav
Requested By	Evan Rosado
Date Submitted	2026-04-10
Priority	P1 — documentation architecture compliance
Category	Documentation Infrastructure
Environment	domus-captures (all case studies)
Context	universal (affects both work and personal case studies)

Field

Value

CR ID

CR-2026-04-10-case-studies-modularization

Title

Case Studies Modularization — Partials, Page Shells, Granular Nav

Requested By

Evan Rosado

Date Submitted

2026-04-10

Priority

P1 — documentation architecture compliance

74 case studies (~26,800 lines) are monolithic page files with all content inline. This violates STD-001 (Project Structure: "partials hold content, pages are shells") and prevents granular navigation. Each case study should be independently navigable by section — an engineer looking for a rollback plan shouldn’t scroll through 500 lines to find it.

This CR brings every case study into compliance with the established pattern (demonstrated by CR-2026-04-15-srt-research-vlan), adds :context: work | personal tagging per STD-013, and rebuilds the nav with per-section entries.

Scope

In Scope

74 case studies across 5 categories:
- 41 Change Requests (~14,200 lines)
- 12 Incidents (~4,600 lines)
- 12 Root Cause Analyses (~4,500 lines)
- 7 Deployments (~2,200 lines)
- 2 TAC Cases (~1,300 lines)
Per-type partial directory structure
Page shells with single include:: per page
Granular nav entries (per-section, not per-document)
:context: work | personal tagging on every page
Case study template updates

Out of Scope

Content changes — text is moved, not rewritten
New case studies — only existing files are refactored
Other documentation areas (codex, projects, standards)

Schedule

Phase	Scope
Phase 1	Changes — 41 files (~14,200 lines) — 2-3 sessions
Phase 2	RCA — 12 files (~4,500 lines) — 1 session
Phase 3	Incidents — 12 files (~4,600 lines) — 1 session
Phase 4	Deployments — 7 files (~2,200 lines) — 1 session
Phase 5	TAC — 2 files (~1,300 lines) — 1 session
Phase 6	Nav rebuild — all 74 entries with granular sub-pages
Phase 7	Template update — case study templates use partial pattern

Phase

Scope

Phase 1

Changes — 41 files (~14,200 lines) — 2-3 sessions

Phase 2

RCA — 12 files (~4,500 lines) — 1 session

Phase 3

Incidents — 12 files (~4,600 lines) — 1 session

Phase 4

Deployments — 7 files (~2,200 lines) — 1 session

Phase 5

TAC — 2 files (~1,300 lines) — 1 session

Phase 6

Nav rebuild — all 74 entries with granular sub-pages

Phase 7

Template update — case study templates use partial pattern

Personnel

Role	Name
Implementer	Evan Rosado (with Claude Code)
Reviewer	Self-review — build must pass, nav must resolve, content must be unchanged

Role

Name

Implementer

Evan Rosado (with Claude Code)

Reviewer

Self-review — build must pass, nav must resolve, content must be unchanged