the brief — prediction table and agreed on
Prediction table
| Signal | Baseline (before design) | Target | Check date | Method | Owner |
|---|---|---|---|---|---|
| Grading time per exam cycle | 47 min — session recording with Gal, 14 April 2026 | < 10 min | 30 days post-release | Session recording, Gal's next exam cycle | Project Lead |
| Submission confirmation rate | 0% — email only, no receipt exists | 100% receive a platform receipt | 30 days post-release | PostHog: grading.submission.confirmed fires per exam | Project Lead |
Agreed on
The brief is agreed on when the trio has reached genuine alignment — on the problem, the Decisions, and the Prediction — and has said so explicitly. Before this moment, any member of the trio can reopen any section without friction. After it, the brief is the shared truth the team builds from. Changes require reconvening — not because of process, but because silent changes to an agreed brief are how the direction drifts during implementation without anyone noticing.
text
Project Lead Designer / DevOps Tech Lead Date agreed
───────────── ─────────────────── ───────── ───────────Discovery Gate — before the first Epic is named
- The Experience Snapshot contains something witnessed — not described, not recalled, not summarised from a meeting.
- Decisions contain a direction the trio agreed on, with rejected options written down.
- The Prediction contains a baseline measured before any design or code began.
All three before Scope starts.