Agent team

Harmonia separates agentic judgment from deterministic workflow authority. Agents analyze, strategize, plan, write, review, compose interfaces, and answer read-only questions. Firestore and application code own stage transitions, approvals, scheduling effects, publishing, receipts, and verification. Use Agent skills, tools, prompts, and traces for the canonical runtime inventory and Agent contracts for exact handoff boundaries.

Agent	Runtime role	Output	Filesystem skills	Separate runtime tools
Nimi	Evidence analyst	`SourceAnalysis`	`nimi-analysis-skills`	Isolated Google Search; optional isolated Vertex AI Search
Ryan	Content strategist	`StrategistResult` / `ContentStrategy`	`ryan-strategy-skills`	Isolated request-bound Google Search
Temi	Editorial planner	`EditorialPlan`	`temi-editorial-planning-skills`	Six immutable planning-snapshot reads
Noni	Copywriter	`ContentDraft`	`noni-writing-skills`	Verified-publication read; isolated Google Search
Dara	Editor	`EditorialAssessment`	`dara-editing-skills`	None
Maya	A2UI presenter	`SurfacePlan`	None	None
Nova	Read-only liaison	`LiaisonAnswer`	Five routing skills	Six bounded read-only tools

Memory Bank provides eligible context only. It never grants approval, permissions, policy exceptions, or authority to cause an external effect.

ADK agent platform

Coordinator, specialists, sequential drafting team, skills, managed sessions, and authority boundaries.

Last modified on August 28, 2026

Research and strategy

Planning and production

Experience and liaison

Agent runtime

ADK agent platform