2026-10-04-adopt-context-standard

Decision

Learning Platform keeps its product material in .context/, in the ten folders every product under ~/git/products uses, and its website has a design set built to ~/git/personal/STYLE-GUIDE.md.

Why

The root docs/ folder held a roadmap, a feature audit and two runbooks, and there were no design files at all: the only description of a screen was its code.

Impact

• docs/ROADMAP.md is split into features/, one page per phase, text preserved.
• The two how-tos are runbooks under ops/runbooks/. The audit is feature-completeness.
• designs/web/ is drawn from the routes in apps/website. The app exists, so where a screen and the app disagree, the app is the fact.
• routes.js is the screen inventory. Nothing else lists the screens.
• Drawing the screens from source found copy and behaviour worth a second look. They are on the surface pages and in tasks.md T003.

Status

Active.

Sources

• ~/git/products/CONTEXT-MIGRATION.md
• .context/designs/web/routes.js