A short guide.

Momentum models the work of an Innovation department as discovery → backlog → delivery. Each is a first-class surface in the app, not a free-text afterthought, so every shipped change traces back to a documented conversation.

See the full pipeline diagrammed at /help/workflow — Discovery → Pain Point → Backlog Item → Project → Shipped, with the exact paths to take at each step.

Open /discovery. Click New session. Capture the date, duration, and a transcript or notes. Inside the editor, type / to insert headings, lists, callouts, code, or toggles. Drag the handle on the left of any block to reorder. Autosaves to the district database; status is shown in the top-right of the notes panel.

As you talk, tag pain points in the right rail. Each pain point gets a 1–5 severity and optional comma-separated tags. When you find a pain point that has a tractable solution, click the Promote to backlog arrow next to it.

/backlog renders the same data three ways:

• Board (default) — drag a card across columns to transition status. Each transition writes an audit-log entry.
• Table — sort, search, and scan with all metadata visible.
• Calendar — items appear on their shipped date if shipped, otherwise their creation date.

Your view preference is remembered per browser. Items that reach Shipped will eventually publish to the changelog automatically.

/departments tracks engagement status across the district: unengaged, scheduled, engaged, piloting, adopted. Add new departments as you encounter them; the directory is itself a rollout dashboard.

• ⌘K / Ctrl+K — open the command palette (navigate, create, sign out).
• ?— open the feedback drawer to send a note about whatever you’re looking at.
• / inside the discovery notes editor — open the slash menu (heading, list, callout, code, toggle, etc.).
• Esc — close any modal.

Postgres, hosted today on Vercel-managed Neon during the discovery phase. Production target is a district-managed Linux VM with Microsoft Entra single sign-on. No institutional data ever leaves the boundary; all incidental references in notes are covered by the audit log and the FERPA posture in docs/INCIDENT_RESPONSE.md.