CEDAR is not a layer applied on top of Claude. It is how Claude thinks when operating as Chief of Staff AI for Cypress.io. The principles, anticipation, risk/opportunity lens, and institutional memory are an identity, not configuration. Claude is the foundation; CEDAR is who Claude is in this context. Use the tabs above to explore the session lifecycle, system architecture, learning mechanisms, and infrastructure that make this work.
- Calendar scan (next 48 hrs)
- Email triage — high-signal senders first
- Surface active risk insights
- Spaced repetition reviews due
- Apply any pending promotions
- Inline insight logging as they emerge
- Risk / Opportunity detection on every analysis
- Cross-domain synthesis
- Page access logging for association index
- Energy allocation tagging
- Log strategic decisions
- Write energy allocation entries
- Quality triage on session insights
- Promote high-value patterns
- Advance calendar anchors
Every output is filtered through the two core questions. Risks and opportunities are stated immediately, without prompting.
If the routing index, action items, or session history suggest something is relevant, surface it before being asked.
A churn spike is a sales problem, a product signal, and a board narrative risk simultaneously. Working in one domain means checking adjacent ones.
Compress, don't expand. Lead with signal, bury noise. Resolve autonomously when possible. Every question asked should be one only the principal can answer.
Track commitments, decisions, patterns, and unresolved threads across sessions via the cedar_session_insights table. If it was discussed before, know where to find it.
Every session is training data. Notice what gets loaded versus used, what questions recur, what domains trend. Propose routing and skill improvements.
Bias every deliverable and framework toward the skills and systems that move the principal's strategic trajectory forward — not just today's task.
Each CEDAR session runs in three phases — Start, Work, and Close. Click any phase node to expand or collapse its action list. Enable Technical Detail in the header to reveal the underlying tools, tables, and edge functions behind each action.
gcal_list_events → cedar_calendar_anchors
gmail_search_messages
cedar_session_insights (insight_type=risk)
cedar_spaced_repetition (next_review_date ≤ today)
cedar_promotion_queue (status=pending)
cedar-insight-write edge fn
cedar-insight-write edge fn
context_routing_index adjacency query
cedar_session_page_access
energy_allocation_log
notion_backup.decision_log
notion_backup.energy_allocation_log
cedar-pattern-promote edge fn
CEDAR integrates with seven external systems — calendar, email, Slack, Salesforce, Snowflake, Supabase, and Notion — feeding signal into a central intelligence core. The animated lines show live data flowing inward at session start and insights writing outward during and after sessions. Hover any node to see its role in the system.
Every insight CEDAR logs passes through a spaced-repetition cycle. The SM-2 algorithm schedules reviews at increasing intervals — a useful insight seen once gets reviewed in 1 day, then 6, then 25. Insights that prove accurate across 5+ reviews graduate into durable behavioral patterns and get promoted directly into CLAUDE.md. The right panel tracks the full queue.
CEDAR writes to cedar_session_insights via cedar-insight-write edge function inline during conversation.
Nightly cron enqueues new insights into cedar_spaced_repetition with SM-2 parameters (interval, ease factor).
SM-2 parameters: ease_factor default 2.5, starting interval 1 day
At session start, surfaces insights where next_review_date ≤ today. The principal engages with or dismisses each.
Surfaced via Supabase REST API query on cedar_spaced_repetition
Logs quality_score (1–5) and acted_on. SM-2 advances or resets the interval. Graduate after 5 correct reviews.
SM-2 advance call: POST cedar-spaced-repetition with mode: advance
High-scoring patterns (3+ sessions, quality ≥4) promoted to CLAUDE.md, skill files, or MEMORY.md via cedar-pattern-promote.
Promotion check: surfaced_count >= 3 AND quality_score >= 4 AND 14+ days old
Updated files change how CEDAR behaves next session, completing the loop.
Every time Todd corrects CEDAR, something happens in the background: the correction is written as an insight, promoted through a review cycle, and merged into CEDAR's configuration. The next session, the same situation arrives — and there's no fork. The loop is complete.
cedar_session_insights
cedar-insight-write edge fn → cedar_session_insights (insight_type=pattern, status=active)Body written inline — no session close needed for persistence
cedar_spaced_repetition, cedar_promotion_queue, cedar_pattern_promotionsPromotion threshold:
surfaced_count >= 3 AND quality_score >= 4 AND created_at <= now() - interval '14 days'
cedar_promotion_queue (status=pending) applied → CLAUDE.md updated → Claude loads new behaviorSame-situation detection: behavioral pattern promoted via
cedar-pattern-promote runs nightly
The compute and storage layer CEDAR runs on — Supabase edge functions that write insights mid-session, and the Postgres tables those functions read and write.
⚡ Edge Functions
Insight persistence
Writes a CEDAR insight to cedar_session_insights the moment it surfaces during conversation — no waiting for session close. Deduplicates on (session_date, summary) to prevent double-writes if the same insight fires twice.
Pattern consolidation
Scans the last 30 days of pattern-type insights and promotes any summary appearing 3+ times to cedar_pattern_promotions. Called during session close protocol to surface durable behavioral patterns for CLAUDE.md promotion.
SM-2 review scheduler
Manages the spaced repetition lifecycle for CEDAR insights. Mode advance updates interval, ease factor, and next review date using the SM-2 algorithm. Insights graduate after 5+ correct reviews and stop surfacing.
🗄 Supabase Tables
Core insight store
Every risk, opportunity, commitment, connection, and pattern CEDAR surfaces or detects lands here. The backbone of institutional memory — queried at session start, written inline, scored at close.
Key columns
Notion page routing
Scored index of every Notion page CEDAR can load. The router queries this table with domain + keyword scoring to decide which pages to fetch. Priority, freshness, and access count all factor into the score.
Key columns
CoS action item backup
Nightly sync of Todd's Notion action item database. Queried at session start to surface Must Act items and CEO Promises. Source of truth stays in Notion; Supabase enables fast SQL filtering.
Key columns
Strategic decision history
Every strategic and operational decision CEDAR logs, synced from the Notion Decision Log DB. Queried at session start for revisit dates — decisions that are approaching review surface proactively.
Key columns
Time & energy tracking
Session-by-session log of how Todd's time is categorized across Strategic, Operational, Reactive, Relationship, and Skill Building. CEDAR writes entries at session close and flags category drift against target ranges.
Key columns