See what Harmonia does
Understand the product promise, operator experience, and governed content loop.
Run the stack
Start the web app, ADK worker, Firestore emulator, and Pub/Sub emulator locally.
Follow a content job
Trace ingestion, analysis, strategy, production, approval, publishing, and proof.
Meet the agent team
Learn how seven bounded specialists research, plan, write, review, present, and assist.
Operate with confidence
Inspect authority, recovery, observability, replay, deployment, and durable state.
Use exact references
Look up routes, contracts, states, configuration, storage, budgets, and receipts.
The content loop
- Ingest an authorized YouTube URL, uploaded video, or operator brief.
- Understand the source with Gemini and grounded research.
- Strategize with specialist agents that preserve evidence and uncertainty.
- Approve the exact strategy and consequential effects through deterministic gates.
- Produce reviewed posts, clips, schedules, and content packs.
- Publish and verify through official integrations, idempotent commands, receipts, and fresh provider reads.
Built for bounded autonomy
- Agents judge; code authorizes. Google ADK specialists analyze, plan, write, review, and compose operator surfaces. Application code owns stage transitions, policy, and authority.
- State survives interruption. Firestore is workflow truth; Pub/Sub delivers resumable work; failures remain visible and recoverable.
- Approval is payload-bound. A conversational “yes” cannot publish by itself. It opens the same exact confirmation flow used by the dashboard.
- Effects are idempotent and auditable. Approved actions carry stable identities, produce receipts, and are independently verified.
- Interfaces stay consistent. Dashboard, conversational chat, and allow-listed Telegram entry points share the same pipeline and approval boundaries.
Explore by role
- Operators: start with Product overview, Pipeline, and Approval and audit.
- Developers: use the Quickstart, Platform map, and Reference.
- Reviewers: inspect Architecture, Evaluation, and Evidence runbook.
- SREs and maintainers: follow Operations, Failure recovery, and Observability.
Evidence and deployment status
Harmonia documents implemented contracts separately from authenticated deployment evidence. Repository tests and local emulator runs prove local behavior only; provider and cloud claims require captured authenticated evidence. The currently reachable Cloud Run revision is a web-only preview and does not prove a deployed worker, Scheduler, Agent Engine invocation, Memory Bank retrieval, or live publish. Use the evidence runbook before presenting deployment, model, publishing, or verification claims.Start with the quickstart for local inspection. Use configuration and deployment only when you are ready to supply real Google Cloud and platform credentials.