Aurora — Project Hub

The team kept hitting the problem of schedules and to-dos discussed in a meeting scattering afterward. Aurora solves this with automation. When you upload a meeting recording (audio file), the Spec: Audio-to-Events Pipeline runs transcription and LLM analysis to extract candidate events and action items; after the user reviews them, they are reflected in the shared calendar and Slack. The ultimate aim is a state where "when a meeting ends, the next steps are already in the team's systems." [Aurora — Kickoff Brief.md]

The project was shaped at the planning meeting on 2026-06-09. The Planning Meeting 2026-06-09.md transcript captures four key decisions — transcription engine selection, date-resolution policy, Slack notification scope, and calendar view priority — all tracked chronologically in Aurora — Decision Log. [Planning Meeting 2026-06-09.md]

The MVP consists of three core features.

First, audio import & event extraction — upload a meeting recording and events (title, time, attendees) and action items (task, owner, due) are extracted automatically. The detailed spec for this flow is defined in Spec: Audio-to-Events Pipeline, and the source spec document is Feature Spec — Audio to Events.md. [Feature Spec — Audio to Events.md]

Second, shared team calendar (week view) — extracted events are reflected automatically in a team-shared calendar. The week view ships first in the MVP; the month view is deferred to a later stage. [Planning Meeting 2026-06-09.md]

Third, Slack action-item notifications — when an action item is assigned to a specific person, only that person gets a Slack notification. Not notifying on every event is intentional, to avoid notification fatigue. The specs for these two features are in Spec: Shared Team Calendar and Spec: Slack Notifications. [Planning Meeting 2026-06-09.md]

The items explicitly excluded from the MVP matter too. A mobile app, recurring-event rules, and external calendar (e.g., Google Calendar) sync are all out of scope — a deliberate decision to focus on core value within the Q3 deadline. [Aurora — Kickoff Brief.md]

Aurora's data flow can be understood as a pipeline.

[Feature Spec — Audio to Events.md], [Planning Meeting 2026-06-09.md]

ElevenLabs was chosen as the transcription engine for two reasons — its accuracy on overlapping speech is better than competing products, and the team already holds an API key. This decision was led by engineering lead Jun Lee at the 2026-06-09 planning meeting and is recorded as #3 in Aurora — Decision Log. However, the ElevenLabs contract must be signed by 2026-06-20; if it slips, even starting the pipeline alpha is delayed. [Planning Meeting 2026-06-09.md]

The date-resolution policy is also a core pipeline design decision. Relative date expressions like "next Tuesday" are resolved against the meeting date, and low-confidence items get a flag asking the user to confirm. Events with no date at all are saved as unscheduled and the user is asked to fill them in. Dates are stored internally in UTC and displayed in local time. [Feature Spec — Audio to Events.md], [Planning Meeting 2026-06-09.md]

Every decision made on the project can be found in date order on Aurora — Decision Log. It is the first document to check when onboarding a new team member or when scope is debated. The flow of decisions, summarized:

Combining the four-stage milestones defined in Aurora — Kickoff Brief.md with the intermediate checkpoints added in Planning Meeting 2026-06-09.md gives the Gantt chart below.

[Aurora — Kickoff Brief.md], [Planning Meeting 2026-06-09.md]

The riskiest stretch is the alpha (July 15). If the ElevenLabs contract (June 20) slips, even starting pipeline development is delayed, and if the alpha slips past July 15, the beta (August 15) and pilot launch (September 15) cascade into risk. [Planning Meeting 2026-06-09.md]

[Aurora — Kickoff Brief.md]

The full checklist and dependency analysis are on Aurora — Action Items. The most pressing items, summarized:

This page is the hub for understanding everything about the Aurora project in one flow. The details of each area are on the pages below.