Infastructure debrif and Faculty setup planning session
Stephan + Brooke aligned on building Faculty Agents for Degen Daycare University using n8n + Kimi, with strict lane ownership to prevent stream-crossing between builders (Cursor = campus/progress/history/admin lanes; Antigravity = verify-proof lane; Claude = scripts/docs tooling lane). We also confirmed the near-term priority: ship a stage-ready investor demo (History → Progress → Verify) while prototyping the Faculty system as modular n8n workflows (each teacher as an agent with a “persona + tools + outputs” contract).
Problem solved
Problem Solved The Simple Goal You already have n8n + Kimi, so we can start building Faculty as simple “teacher bots” that: Receive a question (student message) Route it to the correct teacher persona (Volta / Sigma / Ouroboros / etc.) Return a structured response (lesson + drill + tiny sim prompt + disclaimer) Log the interaction (for later “office hours” history + analytics) Why this matters: it turns the “Faculty roster” into working infrastructure, not just lore — and keeps the demo lanes stable while the agent layer grows safely.
Touched
- NONE (planning + coordination only)
Security impact
- lane-boundaries-enforced
- no-service-role-in-client
- no-db-changes
- no-new-dependencies
How to verify
- n8n-workflow-runs
- teacher-router-returns-correct-persona
- response-includes-disclaimer
- logs-created
- no-crosslane-edits
Notes
- Notes (comma-separated) Faculty agents spec
- n8n teacher router plan
- office-hours workflow
- safe demo lanes
- stage readiness priority
- hackathon submission alignment