[IanMayo]

Summary

Starts implementing SRD Annex A (accepted 2026-10-17). Documents only; the viewer code follows in a separate PR.

• docs/SRD.md, the amendments Annex A §B.4 lists:
  • §7: the "then stop" after 2c is lifted (Annex A Part B); the hyperparameter cap is replaced by pre-registration (declare and forecast what will be test-scored before training it).
  • §4: the 6-hour wall-clock cap is replaced by chained CI jobs with per-epoch checkpoints.
  • §6: packages/demos/ holds the engagement and model viewer.
  • §8: decision 21 (budget lifted) and the viewer decisions D1–D3.
• AGENTS.md: gate status says what comes next (viewer, realism check, pre-registered levers on fresh seeds from 204); repository layout lists demos/.
• specs/006-engagement-viewer/:
  • spec: user stories (engagement, instantaneous, time-late, model choice, share and export) and FR-001–FR-009 traced to V-001–V-018, minus V-014 (deferred).
  • plan: browser-safe subpath exports of features/classical/data with the output decoding moved into features; @tma/demos core plus a React viewer; tfjs on the CPU backend for determinism; a site page with a prebuild catalogue and the eight carried models copied as static files.
  • tests: a browser-bundle regeneration test, a CPU-vs-tfjs-node agreement test, a golden view model and a server render.
  • tasks.

Constitution check

• Data types defined only in schema/tma.yaml; pnpm schema:gen run (I): no change; the viewer uses existing types
• Deterministic: seeded PRNG only; golden files updated deliberately, with the reason stated (II): no change; the plan requires CPU-backend inference for determinism
• sim/features stay pure functions; one CLI per stage; Keras-equivalent layers only (III): reused through browser-safe subpaths, no forks
• Any reported result sits beside naive and classical numbers on the same test set (IV): the viewer shows both beside every model figure
• Respects the current gate: no training before G0, no scope beyond SRD §1 (V): nothing trained or scored

Site pages

• Glossary entry (site/docs/glossary.md) for any new term
• Data dictionary: regenerated automatically from the schema (nothing to edit)
• Algorithm note (site/docs/algorithms/) for any new or changed algorithm
• Blog post (site/blog/) for any new result or gate decision
• Not applicable: requirements and plan only; the implementation PR carries the viewer page and post

Checks

• Prettier on the changed documents; no code change

---

Generated by Claude Code

[github-actions]

Site preview: https://debrief.github.io/Gitma/pr/50/ (updates on every push; removed when the PR closes).