a-d-d-guidance/GLOBAL.md → First Session — Discovery → Interview
- What does success look like? - Does this need a web presence? ...+ - What unit convention? Metric, imperial, or dual? (Default: dual — both everywhere.)+ - If there's a visual design: what colors? Dark or light theme? Confirm — never assume from source material.+ - If there are print deliverables: what size? What color mode (B&W or color)? Content checklist before building. - What do you want to call this project? ...
Retro issue: Unit convention, theme color, and print specs were all discovered mid-demo instead of during discovery. 3 issues that cost multiple iterations each.
1b. Presentation Rule
a-d-d-guidance/GLOBAL.md → new section after Architecture Review
### Presentation++ All structured deliverables are presented as **HTML opened in the browser**+ — never as terminal markdown. Reviews, retros, status reports, demo+ walkthroughs — anything the human needs to read and approve gets rendered.+ Terminal output is for status updates and short responses only.
Retro commitment: "Always present to me as HTML." Terminal markdown is throwaway. HTML is reviewable.
1c. Data Model — Triples Everywhere
a-d-d-guidance/GLOBAL.md → new section after Board Format
### Triples as Universal Data Model++ The triple format `{subject, predicate, object}` is not just for boards.+ All structured data — retros, issues, reviews, inventories — is stored as+ triples. One format, one mental model, one query pattern. If it has+ structure, it gets triples.
Retro commitment: "Data should always be stored underneath as triples." Composable, queryable, consistent.
1d. Issue Tracking — Triple Format
a-d-d-guidance/GLOBAL.md → Issue Tracking section
- **Format:** each issue is a triple block appended to `a-d-d/issues.md`:-- ```- {issue-<n>, summary, <one-line description>}- {issue-<n>, work-item, <board item that surfaced it>}- {issue-<n>, detail, <what happened, what was expected, what was done>}- {issue-<n>, category, <spec | tooling | guidance | process | platform>}- {issue-<n>, resolved, <yes | no | workaround>}- ``` (Note: issues.md in current project used numbered prose. Migrate to triple format for consistency with the universal data model.)
Consistency: Issues journal was numbered prose in this project. Should be triples like everything else. The format already exists in guidance — just enforce it.
1e. UI Design Rule
a-d-d-guidance/GLOBAL.md → Web Hosting section, after Pattern 2
### Web Design Rules++ - **No emoji as UI elements.** Emoji render inconsistently across platforms+ and clash with dark themes. Use clean text, dots, arrows, borders.+ - **Warnings near the action.** Medical disclaimers, destructive-action+ warnings, etc. go immediately before the thing they warn about — not at+ the top of the page blocking content.+ - **Verify claims against reality.** Before publishing formulas, numbers,+ or subjective claims (age appearance, timelines), confirm with the user+ against their actual experience. "What do you actually do every day?"
Retro issues: Emoji icons were ugly on dark mode (issue #4). Warning at top was too aggressive (issue #3). Formula was 1L but actual usage was 1.5L. Age claim said 20s, reality was 30s.
1f. Print Deliverables
a-d-d-guidance/GLOBAL.md → Web Hosting section, after Web Design Rules
### Print Deliverables++ When a project includes printable materials:++ 1. **Confirm specs before building** — size, color mode, content checklist.+ 2. **Print = white paper.** Screen = dark theme. Different concerns, different+ files. Never apply screen theme to print.+ 3. **QR codes** — use raster PNG (not SVG strokes) for reliable scanning.+ Generate with `segno` + Pillow, embed as `<img>` with+ `image-rendering: pixelated`.+ 4. **Standard sizes** — confirm with user. Common: 102×152 mm (4×6 in)+ photo print, A4, letter. Dual metric + standard in all references.
Retro issues: Print cards took 5+ iterations — wrong size (#6), wrong colors (#7), SVG QR didn't scan. All preventable with upfront specs.
2. Project — a-d-d/inform/share/CLAUDE.md
2a. Formula spec — 1.5 liters
a-d-d/inform/share/CLAUDE.md
(Already updated during demo — confirming for the record)- The formula: 1,000 mg sodium, 200 mg potassium, 60 mg magnesium per liter+ The formula: 1,000 mg sodium, 200 mg potassium, 60 mg magnesium per 1.5 liters (48 oz)
Already applied. Verified against Joey's actual daily LMNT usage in a Filipino-sized pitcher (48 oz).