# Daedalus Onboarding — Welcome to the Board

**Date:** 2026-04-19
**From:** Socrates 🧠
**To:** Daedalus 🎨

---

Welcome. You're the second agent on the Hoffmann sovereign stack. Here's what you need to know.

## Who We Are

- **Socrates 🧠** — Lead AI Systems Architect. I own the backend, pipelines, infrastructure, and AI architecture. I speak in API contracts and systemd units.
- **Daedalus 🎨** — That's you. Lead UX/Design Architect. You own the frontend, UI/UX, design system, and mobile experience. You speak in design tokens and component specs.
- **Matt** — The Director. He owns the domain, sets priorities, and approves everything before it ships. He's a Python/data pro who has never built a website — your job is to make that irrelevant.

## The Hardware

- **titanium-butler (Beelink):** Ubuntu 24.04, the server that runs everything. OpenClaw gateway, Radicale CalDAV, FastAPI webhook, ChromaDB. Your HTML will be served from this box.
- **Gaming PC (3080 Ti):** Connected via Tailscale (`matt-pc.tail864e81.ts.net`). Runs local LLMs (qwen2.5-coder:7b, gemma4:latest, qwen3-vl:8b) and embeddings (nomic-embed-text). You can offload code generation and review here.
- **Cloud (Ollama Pro):** GLM 5.1 — our primary model. Three concurrent slots. We both use it.

## What's Already Built (Backend)

The family assistant stack is feature-frozen at v1.0:

- **Email pipeline:** Cloudflare Email Worker → FastAPI webhook → LLM parse → Radicale CalDAV → Hermes Telegram notification
- **Calendar:** Radicale CalDAV on `cal.hoffdesk.com` (Cloudflare Tunnel). Both Matt and Aundrea sync on iPhones.
- **Family Brain:** ChromaDB RAG for semantic retrieval of family documents
- **Conflict Engine:** Detects scheduling overlaps, generates resolution options
- **Hermes:** Telegram push notifications for events, conflicts, digests
- **Location Cache:** Known locations with travel times, Nominatim fallback
- **Backup:** Daily tar to local + Gaming PC via Tailscale SSH

**Key APIs you'll consume (specs coming to `shared/api-specs/`):**
- `GET /api/calendar/upcoming` — next N hours of events
- `GET /api/calendar/date/{date}` — events for a specific date
- `GET /api/family-brain/query?q=...` — RAG query
- `GET /api/system/health` — infrastructure status
- WebSocket for real-time event push (future)

## The Domain

- **hoffdesk.com** — registered, Cloudflare-managed
- **cal.hoffdesk.com** — CalDAV tunnel (live)
- **hook.hoffdesk.com** — webhook tunnel (live)
- **Web UI subdomain** — TBD. Options: `app.hoffdesk.com`, `home.hoffdesk.com`, `dash.hoffdesk.com`

## What You're Building First

The **HoffDesk Family Dashboard** — a mobile-first web app that replaces Telegram as the primary interface for family schedule and system status.

**MVP features:**
1. Today's calendar at a glance (dark mode, one-tap readable)
2. Upcoming 48h events with travel times
3. System health indicator (green/yellow/red)
4. Quick-add event (text input → LLM → Radicale)

**Design principles:**
- Aundrea at 7 AM, half-awake, phone in hand — if she can't read it in 2 seconds, redesign it
- Under 1 second load time
- Under 2 taps to any core action
- Dark mode default
- Zero external JS dependencies

## The Collaboration Protocol

1. **I write API specs** → `shared/api-specs/`
2. **You build UI mocks** against those specs
3. **Matt approves** the design
4. **I wire real data** to the endpoints
5. **Iterate**

If an API spec is missing or unclear, request it. If a design decision impacts data architecture, I'll consult you. We stay in our lanes and meet in `shared/`.

## The Telegram Board

Once you have your bot token, you'll join **"The Hoffmann Board"** group — Matt, Socrates, and Daedalus. That's the coordination channel. Direct messages to Matt for design reviews, to the group for cross-cutting work.

---

Build something beautiful. The family is counting on it.

— Socrates