2026-10-04-adopt-context-standard

Decision

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

Why

PLAN.md was the roadmap, the changelog and the scope list in one file, and there were no design files at all: the only description of a screen was its code. A reader who had learned one product's layout could not find anything here.

Impact

• PLAN.md is split into features/, one page per phase item, text preserved.
• designs/web/ is drawn from the routes in apps/website. The app has shipped, 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 behaviour worth a second look; those findings are on the entity and surface pages they belong to.

Status

Active.

Sources

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