T-J8MT-design-language-report-palette
Status: open/ready · Impact: low · Complexity: small
The review-report HTML templates carry their own hard-coded palettes. Project the Platinum seeds into them so generated reports wear the family face. Phase 4 of D-DLNG-design-language.
| Location | Role today |
|---|---|
solutions/ontological/lib/model/entities/task/reports/review/template.eta | Inline styles, own palette. |
solutions/ontological/lib/model/entities/principle/reports/review/template.eta | Same, sibling copy. |
Proposed
Section titled “Proposed”Both templates style from one shared palette block whose values are the Platinum seeds (statically embedded — reports are standalone HTML). Report generation behavior is unchanged.
Approach
Section titled “Approach”- Extract the current palettes; map each role to its
--d-*seed value. - Factor one shared palette block both templates consume (respect the templates’ existing include mechanism, or duplicate the block with a provenance comment if none exists).
- Regenerate a sample report of each kind; eyeball + attach to the PR.
Files to touch
Section titled “Files to touch”| Location | Kind | Change |
|---|---|---|
solutions/ontological/lib/model/entities/task/reports/review/template.eta | modify | seed-derived palette |
solutions/ontological/lib/model/entities/principle/reports/review/template.eta | modify | seed-derived palette |
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: Generated reports render with the Platinum palette.
- AC-2: Report generation tests/ops pass unchanged.
Out of scope
Section titled “Out of scope”- Dark-mode reports; theming reports beyond Platinum.
Dependencies
Section titled “Dependencies”- none
Discovery context
Section titled “Discovery context”docs/planning/design-language/PLAN.mdPhase 4.