Tier 1 — Essential
Remove any of these and the loop breaks.
Interaction Surface Jacob noted
Bot on sync/async channel (Slack, iMessage, WhatsApp, email). Generalizes to UI/display for tracks 3–5 (outliner, ambient display, Note Stream).
LLM Wiki Jacob noted
The persistent memory. Structure-agnostic — Noos graph, Karpathy-style markdown corpus, or hybrid.
Scope decision on dashboard: wiki-hub vs Noos graph. Architecturally both satisfy this slot.
Capture / Ingestion
How raw content gets in. Meeting transcription (Otter / Granola / Gemini / own) plus chat-history ingestion.
This is where the "build own note app vs. integrate" fork lives. Architecturally it's one slot; strategically it's "do we own this layer or rent it?"
Writer Agent
Turns unstructured transcript / messages into structured wiki updates. Routes action items → task list, gripes → relationship page, vision → vision doc. Maintains consistency across pages.
The hardest technical piece and the biggest moat. Not summarization — routing and consistency. Everyone can generate a summary. Almost nobody updates an evolving structured KB well.
Retriever
Context-aware lookup. Not generic RAG — knows which wiki entries are relevant to the current Slack thread, meeting, scheduling request, gripe moment.
"Hey you didn't respond for 3 days, this is an instance of the existing gripe" requires retrieval that understands this moment, not just "find similar text."
Tier 2 — Important, Deferrable
Not needed for v0, but you'll feel the pain fast without them.
Background Worker
Periodic scans for patterns: "person X hasn't responded for N days," weekly summarization, vision-doc rollup, stale-wiki-page detection.
The "3-day no-response" pattern detection literally requires time-aware background scanning — it's not triggered by a user action.
Provenance / Citations
Every wiki claim links back to the source meeting / message / document that generated it.
Without this, the wiki becomes un-auditable. When it's wrong (and it will be), users can't fix it because they can't find where it came from.
Versioning / Undo
Wiki will be continuously AI-written. Need diff history, rollback, and per-edit attribution (human vs agent).
Trust UX layer
Visibility rules, consent flow, expiration, correction workflow — especially for the gripes / conflicts / patterns feature.
Codex's warning: the gripes feature is socially dangerous. Get this wrong → product feels creepy or politically explosive. May be the real moat, not the graph structure.
Tier 3 — Track-specific
Only needed for particular product tracks.
Privacy / Consent Layer
Cross-privacy scoping. "Can you share your availability on this date?" → user clicks approve.
Essential for Track 2 (Group Chat Bot). Not needed for B2B team wiki where everyone already has shared context.
Agent Execution Environment
Private server running coding agents (Claude Code / Codex) that can spawn from prompts — "hey AI go build that node."
Essential for Track 6 (Better GPT) and the "spawn agent per note" feature in Track 5 (Note Stream). Not needed for the core wiki loop.
Identity / Relationship Model
Per-person pages, relationship graph, role inference. Baked into the wiki schema.
Essential for the gripes/conflicts feature. If skipping that, the wiki can be person-agnostic.
Real-time Streaming
Sub-second transcription + retrieval + render pipeline.
Essential only for Track 4 (Ambient Display). The rest of the system can be batch / near-real-time.