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.
- Three new documents read: Jasmine email responses, A/B intelligence update and the House reservation planning draft. Nine client-supplied sources now indexed.
- Jasmine approved the brand brief and accepted the refined personas for 1A. Both stories are now complete.
- Eight 1A deliverables are complete. Existing checks and Jasmine’s original comments are preserved; final milestone sign-off remains separate.
- Project progress dashboard completed and confirmed by Johnathan; live at lumistproject.info.
Eight 1A discovery deliverables are complete. The wine/product file and final regulatory validation remain; 1C implementation continues separately.
No entire milestone is recorded as accepted. Future milestone progress is unmeasured.
What will move the project forward.
Quick direction check
Eight discovery deliverables are complete. Raise any material corrections during final review; no extra brief-by-brief approval round is required. Final writing stays in-house; master learning remains organic.
Brand discovery · SCRUM-11 ↗Existing files when needed
Gigi/winemaker are consolidating the product file. Await Wangqi’s inventory/logistics plan and the Wangqi/Eason payment plan. The House concept is received; final policies follow before booking implementation.
Product discovery · SCRUM-12 ↗Public research prepared
Jasmine will forward the ten-state research to counsel. Final validation and actual seller/permit evidence remain pending. Planned House venues need their own on-premise/operating review.
Compliance inputs · SCRUM-17 ↗Start the working foundation.
1C progress comes from working features and test evidence. The discovery inputs are sufficient to start the foundation.
- Establish the development environment. Confirm the full client domain, hosting/staging ownership and authorized admin access. Quote any new paid services for company approval and direct payment. A local foundation can use sample data while access is arranged.
- Build the first website path. WordPress Journal → wine Dossier → twelve-bottle case cart. Use the received logo, sample records and standard web-font options; leave final editorial content and design polish for their later milestone.
- Add accounts and the membership framework. Email verification, international phone entry, cart retention and private account records. Normal website pricing for every account; no mature VIC scoring required.
- Resolve the specific commerce inputs in parallel. Gigi/winemaker: wine/vintage/SKU/price file. Wangqi: stock units, inventory and fulfillment plan. Wangqi/Eason: payment operating plan, merchant entity and provider decision.
- Demonstrate checkout in an eligible provider’s sandbox. Test successful/failed payments, stock changes, case quantities and private order history. Actual shipping permissions and final legal terms gate live commerce. Full House booking needs its own scope/milestone decision.
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, SCRUM-10, SCRUM-11, SCRUM-13, SCRUM-14, SCRUM-15 and SCRUM-16 are Done: 8/10 for 1A (80%) and 8/20 across current 1A + 1C scope (40%). Learning and later implementation dependencies do not reduce 1A completion. 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. This reference inventory also tracks downstream setup and operating details; an outstanding inventory row is not automatically a 1A completion requirement. 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.