One clear view of what’s next.
Discovery is taking shape. The website foundation is being specified. Follow the current work, what we’ve captured, and what still needs a decision.
Two workstreams, moving together.
The foundations for delivery tracking are in place.
- Both discovery transcripts re-read in full. Tone, mood and experience direction are captured; in-house writers supply the content.
- Six 1A briefs are ready for deliverable review. Johnathan establishes the criteria; no separate client approval of each check is needed.
- SCRUM-8, SCRUM-9 and SCRUM-10 are complete; their checked criteria are preserved. The remaining 17 stories have three focused checks.
- Project progress dashboard completed and confirmed by Johnathan; live at lumistproject.info.
The dashboard, documentation hub and requirements repository are complete. Remaining discovery and foundation deliverables continue through their Jira workflows.
No entire milestone is recorded as accepted. Future milestone progress is unmeasured.
What will move the project forward.
Quick direction check
Review the six remaining brief summaries as deliverables and flag only material corrections. Tone/mood and discovery principles are documented; final writing stays with your in-house team.
Brand discovery · SCRUM-11 ↗Existing files when needed
Share an existing Gigi product/item/price file when available. Johnathan tracks missing setup inputs and asks for operating choices only when the affected implementation needs them.
Product discovery · SCRUM-12 ↗Public research prepared
Named permits and tax accounts researched for all ten states. Forward the licensed seller/ship-from details and existing license/application folder; Johnathan matches the evidence. Counsel validates final applicability.
Compliance inputs · SCRUM-17 ↗The work behind each milestone.
How the percentages are calculated
Delivery completion = Jira Done deliverables ÷ tracked deliverables × 100. Each deliverable counts once. SCRUM-8, SCRUM-9 and SCRUM-10 are Done: 3/10 for 1A (30%) and 3/20 across the current 1A + 1C scope (15%). This is a count of finished deliverables, not an estimate of hours or the whole future project.
Documentation coverage = captured checkpoints ÷ applicable checkpoints × 100. Partial checkpoints remain visible but receive no invented fractional credit. Missing checkpoints receive no credit. Learning-phase checkpoints are excluded from the denominator. Counts are equal checkpoint counts, not equal-effort estimates.
A checkpoint shows 100% when its documentation is Captured, 0% when Missing, and “Partial” when no reliable fraction is supplied. Milestone bars roll up their checkpoints, not averages of rounded item percentages. Jira Done counts and formal acceptance remain separate. A documented requirement does not mean implemented software.
The full project roadmap.
Future milestone deliverables are known scope; progress percentages remain unmeasured until Jira work and evidence checkpoints are defined. No calendar delivery date, payment or formal acceptance is inferred from the proposal. Sprint end: October 16, 2026; this is a planning date, not an acceptance deadline.
Requirements, kept traceable.
Sources, freshness and evidence limits
Jira supplies workflow status, owners and story requirements. Confluence supplies documented input checkpoints and remaining asks. The local master memory supplies the 16-milestone proposal map. This page is a published snapshot, refreshed as project work is recorded; it does not continuously poll Jira.
1A progress notes · 1C progress notes · Source register · Decisions & open questions
All 22 milestone epic/story records were retrieved; the 20 child stories are the dashboard’s delivery scope. Two Jira sample tasks are excluded. Status, summary, description, parent, assignee, labels, priority and update date were checked. Input-review contacts are documented separately from actual Jira assignees, which remain unassigned. No assignee capacity, software deployment, executed test, reviewed milestone criteria, contract, payment or acceptance record is inferred.
Search indexing is discouraged through noindex / nofollow directives. Linked Jira and Confluence records retain their own access requirements.