Project · Product Hub

Aurora — Decision Log

Q: Aurora — Decision Log

Key decisions throughout the Aurora project, listed newest-first with rationale, impact, and source citations.

High confidenceansweredited by Cairni · 방금 · AIv3

This page tracks key decisions made throughout the Aurora project. Entries are listed newest-first. Refer to the Kickoff Brief for foundational scope and team context.

Decision Log

#	Date	Decision	Rationale	Affects	Source
12	2026-06-09	Use ElevenLabs for audio transcription with diarization	Better accuracy on overlapping speech; diarization identifies multiple speakers; key already available	Audio-to-Events Pipeline	Feature Spec — Audio to Events.md
11	2026-06-09	Resolve ambiguous dates relative to meeting date; flag low-confidence ones for user confirmation	Handles edge cases like "next Tuesday" without external context; user confirms when uncertain	Audio Pipeline	Planning Meeting 2026-06-09.md
10	2026-06-09	Slack notifications only for assigned action items, not every event	Reduces notification noise; focuses on personal accountability	Slack Notifications Spec	Planning Meeting 2026-06-09.md
9	2026-06-02	Ship MVP to 3 pilot teams by end of Q3 2026	Limits initial rollout to a controlled group for feedback before wider launch	All workstreams; Project Overview	Aurora — Kickoff Brief.md
8	2026-06-02	Exclude mobile app from MVP scope	Out of scope to reduce MVP complexity and delivery risk	Shared Team Calendar, Slack Notifications	Aurora — Kickoff Brief.md
7	2026-06-02	Exclude recurring-event rules from MVP scope	Out of scope to simplify the Audio-to-Events Pipeline and calendar logic	Audio Pipeline, Calendar Spec	Aurora — Kickoff Brief.md
6	2026-06-02	Exclude external calendar sync from MVP scope	Out of scope to avoid third-party integration complexity in the MVP	Shared Team Calendar	Aurora — Kickoff Brief.md
5	2026-06-02	Use Slack (not email or other channels) for action item notifications	Slack chosen as the notification channel for assigned action items	Slack Notifications Spec, Action Items	Aurora — Kickoff Brief.md
4	2026-06-02	Input format limited to audio recordings only	MVP scope explicitly states "import meeting recordings (audio)"; video/transcript import not mentioned	Audio Pipeline Spec	Aurora — Kickoff Brief.md
3	2026-06-02	Calendar view limited to week view only	Out of scope to build day/month/agenda views for MVP	Shared Team Calendar Spec	Aurora — Kickoff Brief.md
2	2026-06-02	Default action owner to meeting speaker when not explicitly assigned	Minimizes ambiguity; speaker is most likely owner of their own statements	Audio-to-Events Pipeline	Feature Spec — Audio to Events.md
1	2026-06-02	User review step required before events/actions go live	Confidence-flagged items and unscheduled entries need human confirmation	Audio Pipeline, Calendar, Slack Notifications	Feature Spec — Audio to Events.md

How to Use This Log

Add new decisions at the top of the table (newest-first).
Each row should include: a date, a clear one-sentence decision statement, the rationale behind it, who or what it affects (link to relevant spec or team member pages), and a source citation.
Decisions that are later reversed or superseded should be noted with a ~~strikethrough~~ and a reference to the superseding entry.

Risk & Timeline Notes

Per Planning Meeting 2026-06-09.md, alpha delivery by July 15 is critical — if it slips, beta (and pilot launch) are at risk. The action items reflect this constraint.