Document Company OKRs and Goals in the Platform

Phased plan

Phase	Scope	Outcome
Phase 1	Document the plan and get it in the repo.	This phased plan and the full Company OKRs plan are versioned (e.g. in vault); PR merged. No implementation.
Phase 2	Option A implementation.	Company Goals page at `/internal/company-goals`; API reads from GTM Review sheet (and optionally Management Operations, Notion, vault); nav added. Single source of truth remains sheets/Notion.
Phase 3	Option B / Extended plan.	DB-backed company objectives, OKRs, AOR; sync from sheets/Notion; platform-only fields (e.g. Linear links, status history). See Extended plan section.

Implementation work (Phases 2 and 3) is tracked in the Linear project Company Objectives in Platform: project.

GTM Review sheet (Google): Brainforge Objectives, BAU OKRs, Aspirational OKRs, Q2 OKRs — see original plan for structure.
Brainforge Management Operations (xlsx / second sheet): Separate operations workbook with GTM OKRs Q1 2026, Active OKRs Q4 2025, Q3 2025 OKRs, Q126 AOR, Sales OKRs snapshots.
Notion: OKRs 2025 - Objectives database, Q3 Marketing OKRs, Q4 OKR Planning, Recruiting AORs and OKRs.
Vault: Recruiting-AORs-and-OKRs.md – Company-Level Objectives (3), Recruiting/Operations BAU and Aspirational OKRs and AORs.
Platform today: No company-level goals/OKRs surface. Client-scoped weekly goals exist (weekly_goals table).

Company objectives – From GTM Review: Brainforge Objectives + Why + Exec Focus.
OKRs by period and type – From GTM Review: BAU OKRs, Aspirational OKRs, Q2 OKRs (department, objective, key results, owner, workspace link, commentary, status).
Management Operations OKRs – GTM OKRs Q1 2026, Active OKRs Q4 2025 (Status, Value, Key Update, Next Step).
Areas of Responsibility (AOR) – From Management Operations “Q126 AOR”: Department, AOR Description, Importance, DRI, Backup, Status.
Notion: OKRs 2025 - Objectives, Q3/Q4 planning pages, Recruiting AORs and OKRs.
Vault: Recruiting-AORs-and-OKRs.md – Company-Level Objectives, Recruiting and Operations OKRs and AORs.

New internal page: Company Goals at /internal/company-goals (or /internal/okrs), linked from Internal hub and Sidebar.
Sections: Company objectives; OKRs by period (Q1 2026, Q2 2026); AOR; optional Past OKRs (2025); links to “Edit in Sheet” and Notion.

Option A (for initial implementation): Read from Google Sheets (and Notion/vault as needed). Single source of truth stays in sheets/Notion; platform reads on load or manual refresh. No DB for company goals yet.
Option B (preferred eventually, not implementing now): Store in DB (company_objectives, company_okrs, company_aor); “Refresh from sheet” or sync; platform-only fields (Linear links, status history). Captured in Extended plan below.

Option B data model – Supabase (internal) tables; sync from GTM Review, Management Operations, Notion; “Refresh from sheet” or scheduled job.
Platform-only fields – Link OKRs to Linear initiatives; weekly status history for bonus/retro; last synced and sync logs.
Other extensions – Status updates in platform; API for agents/skills; export for board; Past OKRs archive. Deferred until Option B or explicit ask.

Decide where Management Operations lives (xlsx import vs Google Sheet).
Define exact ranges for GTM Review and Management Operations.
Backend: GET /api/brainforge/company-goals returning structured JSON from sheets/Notion/vault (Phase 2); or from DB after sync (Phase 3).
Frontend: Company Goals page; fetch from API; render objectives, OKRs, AOR; link to sources.
Navigation: Add to Internal tools list and Sidebar.
Operating decks: Align with Company Goals when Q2 is live.

Sources: GTM Review sheet, Brainforge Management Operations, Notion, Vault (Recruiting-AORs-and-OKRs.md).
Place: Internal page Company Goals at /internal/company-goals.
Data: Option A first (read from Sheets/Notion). Option B (DB + sync) preferred long-term; see Extended plan.
Linear: Phases 2 and 3 tracked in project Company Objectives in Platform (Platform team).