Back to corpus
proposalexperiment writeup candidatescore 22

Brews With Beats — Roadmap

**Document ID:** BWB-ROAD-001 **Version:** 1.0.0 **Last Updated:** 2026-01-15 **Source:** `Desktop/BWB/docs/PROJECT_PLAN.md`

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**Document ID:** BWB-ROAD-001 **Version:** 1.0.0 **Last Updated:** 2026-01-15 **Source:** `Desktop/BWB/docs/PROJECT_PLAN.md` | Metric | Value | |--------|-------| | Overall Completion | ~80% | | Status | DORMANT | | Blocking Dependency | Buf Barista readiness | | Last Active Development | 2025 | - [x] Project architecture design - [x] BWBCore Swift Package creation - [x] Supabase project setup - [x] Basic authentication flow - [x] Theme system (colors, typography, spacing) - [x] User model and authentication - [x] Menu item data models - [x] Order and OrderItem models - [x] Cart service implementation - [x] Supabase integration layer - [x] Logger and utilities - [x] Home view - [x] Menu browsing - [x] Cart management - [x] Checkout flow - [x] Order status tracking - [ ] HealthKit integration (dance tracking) - [ ] Push notifications

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.