Greenroom

# Archestra app prompt Build an app called **Greenroom** for community-event organizers. Use Archestra's shared data layer. On first run, seed it with the fictional public demo dataset below. Do not fetch any outside data. Events: - Builder Commons — Bengaluru — 2026-08-02 — Meetup - Open Source After Hours — Pune — 2026-08-08 — Community night - Cloud Native Campus — Kochi — 2026-08-15 — Campus program - Community Demo Day — Chennai — 2026-08-22 — Showcase Blockers, written as `id | event | title | area | severity | status | owner | due | impact | next action`: - GR-101 | Builder Commons | Confirm backup venue hold | Venue | critical | blocked | Venue lead | 2026-07-26 | Registration cannot expand until capacity is locked. | Ask the backup venue for a written 48-hour hold. - GR-102 | Builder Commons | Collect final speaker headshot | Speakers | high | in-progress | Program lead | 2026-07-27 | The speaker announcement card cannot be published. | Send the approved crop guide and request a landscape original. - GR-103 | Builder Commons | Publish attendee arrival note | Comms | medium | ready | Community lead | 2026-07-29 | Late arrival details may increase check-in questions. | Schedule the approved arrival note for 48 hours before doors. - GR-104 | Builder Commons | Run projector and audio check | Production | high | open | Production lead | 2026-07-30 | Talk playback and audience questions are untested. | Book a 30-minute venue test with both presentation laptops. - GR-201 | Open Source After Hours | Approve contributor demo shortlist | Program | high | in-progress | Program lead | 2026-07-28 | The run of show has an unallocated 35-minute block. | Score the remaining demos and confirm the top four. - GR-202 | Open Source After Hours | Lock food count with venue | Venue | medium | open | Venue lead | 2026-08-01 | The catering quote may change after the cutoff. | Use the registration trend to submit a conservative headcount. - GR-203 | Open Source After Hours | Confirm code of conduct contact | Safety | critical | blocked | Community lead | 2026-07-27 | The event cannot publish its safety escalation path. | Name a primary and backup contact and add them to the attendee guide. - GR-204 | Open Source After Hours | Prepare sponsor mention slide | Sponsors | low | ready | Partnerships lead | 2026-08-04 | The opening deck is missing one agreed acknowledgment. | Add the approved sponsor line to the opening slide. - GR-301 | Cloud Native Campus | Receive campus network guest credentials | Venue | high | blocked | Venue lead | 2026-08-05 | Workshop devices cannot be tested on the guest network. | Request a temporary access set for the rehearsal window. - GR-302 | Cloud Native Campus | Finish mentor office-hour roster | Program | medium | in-progress | Program lead | 2026-08-06 | Student teams cannot choose reliable help slots. | Fill the remaining two mentor windows and publish the roster. - GR-303 | Cloud Native Campus | Test workshop starter repository | Production | high | open | Technical lead | 2026-08-08 | A broken setup path would consume the first workshop block. | Run the guide on a clean account and log every missing prerequisite. - GR-401 | Community Demo Day | Choose audience voting method | Program | medium | open | Program lead | 2026-08-10 | The audience-choice award has no collection method. | Select a mobile-friendly ballot and test duplicate-vote controls. - GR-402 | Community Demo Day | Confirm photo release wording | Safety | high | blocked | Community lead | 2026-08-09 | Registration copy cannot be finalized. | Review the plain-language consent note with the venue. - GR-403 | Community Demo Day | Draft finalist introduction cards | Comms | low | ready | Community lead | 2026-08-15 | The closing showcase lacks consistent project intros. | Populate the approved card template after finalists are locked. The app should feel like a calm operations room, not a generic analytics dashboard. Use a dark midnight background, warm off-white text, electric lime for healthy signals, coral for critical signals, and cyan for active work. Keep contrast high and spacing generous. Create four views: 1. **Portfolio** — show overall readiness, the number of events at risk, critical blockers, overdue items, and one card per event. Each event card should show date, city, readiness score, blocker count, and the most urgent next action. 2. **Critical path** — rank open issues by severity, overdue status, and how close the event date is. Provide filters for event, area, severity, and owner role. Show impact and next action without forcing the user to open a modal. 3. **Owner load** — group unresolved issues by owner role and make overloaded roles obvious. 4. **Run of show** — place all events on a compact timeline and show the next deadline under each event. Readiness starts at 100 for each event. Subtract 24 for each critical blocker, 14 for each high blocker, 7 for each medium blocker, and 3 for each low blocker. Subtract another 6 when an unresolved item is overdue. Clamp the result between 0 and 100. When an event is selected, open a focus panel that lists exactly three recommended moves, ordered by urgency. Each move should explain why it matters. Add a **Resolve** action to unresolved rows. Ask for confirmation inside the app, then mark the matching record resolved and refresh the view. Add a secondary **Add update** action that appends a timestamped note to the record, then refreshes the row. Make the interface useful at a glance: - label readiness as `Ready`, `Watch`, or `At risk`; - keep event names and due dates visible; - do not hide the critical path behind charts; - include empty, loading, and tool-error states; - never show raw storage payloads; - use only the fictional dataset above. The app must be responsive and fully usable in the Archestra recording view. Build it with no external network requests.