Eden AI — Command Center project plan (consolidated)
Last updated: 2026-04-16
Owner (SL): Uttam Kumaran
CSO (per Notion engagement table): Pranav Narahari (confirm current CSO of record if this has rotated.)
Purpose: Single source for scope, milestones, LOE framing, quick links, and risks. Content merged from Notion Eden AI Project Plan, Eden AI (Project Command Center) hub, and Eden — Project Milestones; those Notion pages are retired or pointed here (see PR #854).
Canonical copy (this file)
| Location | URL / path |
|---|---|
| Vault (this doc) | knowledge/clients/eden/resources/eden-ai-command-center-project-plan.md |
| PR tracking merge + Notion cleanup | brainforge-platform#854 |
| Notion (index only) | Eden AI Project Plan — keep as lightweight pointer + sign-offs; detailed narrative lives here |
| Long-form export (vault) | knowledge/clients/eden/plans/Eden AI Project Plan.md |
| Linear | EDE3 |
| Application repo | brainforge-ai/eden-command-center — mastra-app/ |
| Operating | Command Center / Eden AI project 168008 — see knowledge/clients/eden/resources/operating-allocations-remediation.md |
Quick links (from Notion client hub)
Use the Notion client hub for live embedded DBs (client health, docs index): Eden AI (Project Command Center) — hub.
| Resource | Link |
|---|---|
| SOW | Google Doc — Project Command Center SOW |
| Drive | Engagement folder |
| Diagrams | Figma — Diagram Kit |
| Signed SOW (PDF) | Drive PDF |
| 1Password client vault | 1Password link from Notion hub |
Engagement overview (from Notion)
- Client: Eden
- Engagement period: March → May (align dates with SOW + Linear)
- Commercial (from plan export): ~$32,000 · ~120 hrs total · ~15 hrs/week × 8 weeks framing in milestones doc
- Linear team: EDE3
Initiative
Command Center — Leverage Google Workspace + Slack to surface themes across the business; delivery date target May 15. Services: Data / AI / Strategy & Analytics.
Projects
| Project | Parent | Service line | Start | Target |
|---|---|---|---|---|
| Data Access + Chat Integration | Command Center | AI / Data | Mar 23 | Apr 20 |
| Theme Discovery and Tailored Reports | Command Center | AI / Strategy + Analytics | Apr 20 | May 15 |
Milestones M1–M8 (client-facing)
Aligned to Notion Eden AI Project Plan and LOE notes previously in Eden — Project Milestones (now archived in Notion).
| Milestone | Parent project | What the client receives | Target date |
|---|---|---|---|
| M1 | Data Access + Chat Integration | Danny’s Slack + Danny’s Google workspace interactable via chat | Apr 6 |
| M2 | Data Access + Chat Integration | Eden’s Google Workspace interactable via chat | Apr 13 |
| M3 | Data Access + Chat Integration | Eden’s Google Workspace + Slack via chat with anonymization | Apr 20 |
| M4 | Theme Discovery and Tailored Reports | Baseline theme package: discovered themes, sample redacted signals, short interpretation each | May 4 |
| M5 | Theme Discovery and Tailored Reports | Themes reviewed/tuned with Eden; business-readable labels; less overlap/noise | May 7 |
| M6 | Theme Discovery and Tailored Reports | Bandwidth + friction signals report (interpretable) | May 11 |
| M7 | Theme Discovery and Tailored Reports | Production weekly pulse email incl. WoW / MoM trends | May 14 |
| M8 | Theme Discovery and Tailored Reports | Final report, repeatable workflow, documentation to operate and extend | May 15 |
Hard dependency: Meaningful theme work stays blocked until M3 (anonymized cross-tool access).
LOE checkpoint framing (from retired “Eden — Project Milestones” page)
Retainer framing: milestones are progress checkpoints; scope may evolve with learning.
Phase 1 — data path (technical memo alignment)
| Checkpoint | Est. hours (plan) | Completion means (summary) |
|---|---|---|
| Connections + setup | 10–15 | GCP + Calendar/Slack/Gmail/Drive access validated; service accounts; connectivity checks |
| Ingestion + backfill | 30–40 | Four pipelines → BQ; 4–6 weeks historical backfill; cleaned tables |
| Anonymization | 10–15 | DLP + role-ID anonymization on all paths; validation before analysis |
Phase 2 — client-facing analytics
| Milestone | Est. hours (plan) | Notes |
|---|---|---|
| M4 Theme baseline | 25–35 | Clustering / labeling hardest risk; strategy may co-own validation |
| M5 Theme quality | 5–10 | Eden working session |
| M6 Bandwidth / friction | 10–15 | analytics.*-style metrics in BQ + narrative |
| M7 Weekly Pulse v1 | 10–15 | Scheduler + email from prod; outbound email may be net-new vs readonly agent |
| M8 Handoff | 5–10 | Runbooks, cost envelope, final demo |
(Prior deep links to closed PR #492 in Notion are superseded by this vault doc + BQ/Mastra spine discussion below.)
What we are building (one paragraph)
Eden Project Command Center delivers leadership visibility into how time and attention flow across the org: ingest signals from Calendar, Slack, Gmail, and Drive under HIPAA-aligned controls (DLP + anonymization), land structured data for analytics, run theme discovery and bandwidth / friction style metrics, and ship a weekly Pulse (narrative + metrics) plus a lightweight Command Center view. Text-to-theme quality and week-over-week theme stability are the hardest parts and need explicit review gates with the COO.
Architecture at a glance
Target path (SOW-shaped): Sources → Cloud Functions → Cloud DLP → anonymization → BigQuery → Vertex AI (embeddings + Gemini) → Pulse report + Command Center.
Current shipped application path: The eden-command-center repo runs a Mastra agent with Slack MCP and readonly workspace_* tools (service account + domain-wide delegation). Gmail bodies are not fully exposed to the agent today; several roadmap items assume expanding readonly tools or batch ingestion.
SL decision (Week 0): Confirm with CSO + eng whether BQ-first batch analytics, Mastra-first agent workflows, or a hybrid (e.g. Mastra for interactive + BQ for reporting) is the authoritative delivery spine for the next milestone set—then align Linear initiatives / projects to that choice so tickets do not fork.
Technical approach — Part 1 (Data access + chat) — summary
From Notion (condensed):
- Source auth — GCP SA + DWD; Slack app scopes; Eden IT approval.
- Identity + redaction — Role tokens (e.g.
Provider_A); PII stripped before LLM context. - Slack tools — Search / threads / channels via RTS or MCP; outputs anonymized.
- GWS tools — Drive, Activity, Gmail metadata, Calendar, directory via approved APIs; anonymized.
- Orchestration — Agent plans parallel Slack + GWS calls; unified anonymized answer.
- UI (if in scope) — OAuth, chat UI, API proxy (confirm whether Next.js app is in scope vs Mastra-only.)
- Deploy + validate — Vertex + hosting; Danny-led validation matrix.
Risks called out in Notion: DWD delay; Slack tier / history limits; storage choice for theme snapshots before M7; CLI/MCP depth for scheduled reports → possible light ingestion pipeline.
Technical approach — Part 2 (Theme discovery + reports) — summary
- Theme extraction baseline against live Slack + GWS → store structured baseline (M4).
- Eden validation session for labels / overlap (M5).
- Bandwidth + friction report layer (M6).
- Scheduled report agent with snapshots + WoW/MoM (M7) — two-agent compare pattern optional.
- Handoff + documentation (M8).
Resourcing (Notion): ~1 AI engineer on pipeline + scheduling; analyst on framework / M5 validation.
Part 2 — Linear ticket discipline (from prior draft PR #838)
Window: ~Apr 20 → May 15. Initiative: Command Center; project: Theme Discovery and Tailored Reports. Link Part 2 issues blocked by Part 1 M3 until done. Repo pointers in ticket bodies: eden-command-center / mastra-app.
Open questions: snapshot storage (GCS vs LibSQL), Gmail bodies / Docs requirement, report format owner, scheduler owner (Cloud Scheduler + Cloud Run vs Dagster), production recipient list.
Sign-offs (track in Notion index page)
Keep checklists on Eden AI Project Plan: CSO, SL, HoD, client sponsor.
Related vault docs
knowledge/clients/eden/resources/NAVIGATION.mdknowledge/clients/eden/resources/design-identity-mapping-schema.mdknowledge/clients/eden/resources/operating-allocations-remediation.mdknowledge/clients/eden/resources/spike-command-center-data-access.md— deep spike / alternatives
Changelog
- 2026-04-16: Initial consolidation from draft GitHub PRs #492 / #838.
- 2026-04-16: Merged Notion Eden AI Project Plan, Eden AI (Project Command Center) hub quick links + engagement table, and Eden — Project Milestones LOE framing; aligned the Notion index page and archived the standalone milestones doc (see PR #854 discussion).
- 2026-04-16 (Notion): Eden AI Project Plan — removed “Deprecated” banner; added vault canonical callout at top. Eden — Project Milestones — title prefixed
ARCHIVED, body replaced with pointer to this vault file + PR #854. Client Health stub page linked from the hub — replaced with archive pointer; relink the hub’s “Client Health” property to a fresh Client Health row when you resume delivery tracking (the old relation may show stale content).