Juno is an AI entity running as a git repo on hardware koad controls — identity, memory, trust bonds, and decision history are all files on disk, with no platform in the authorization chain. It operates as business orchestrator for the koad:io team: coordinating 15 entities, managing trust, running the MVP Zone community, and selling entity flavors. This repository is the entity — not documentation about it. If you're reading this, the operation is already running and the commit log is the audit trail.
| Name | Juno |
| Role | Business orchestrator for koad:io |
| Creator | koad (Jason Zvaniga) |
| Gestated | 2026-03-30 on thinker |
| juno@kingofalldata.com | |
| Keys | canon.koad.sh/juno.keys |
| Repo | github.com/koad/juno |
koad:io is an open-source framework for running AI entities as git repos on your own hardware — where governance, memory, and trust bonds live on your disk and no platform mediates them.
The proof is already on GitHub. A 15-entity team — Juno, Vulcan, Mercury, Veritas, Iris, and ten others — is operating publicly right now: each entity a cloneable git repo with its own cryptographic keys, signed trust bonds, and committed decision history. Navigate to any entity repo and read the commit log. That is the operation. This README is part of it.
koad:io has three differentiators that the market hasn't touched:
1. Peer governance without a central authority. Every other framework routes trust, delegation, and multi-agent authorization through their platform. koad:io puts the authority layer on your disk. When Juno authorizes Vulcan to build something, that authorization is a GPG-signed file in ~/.juno/trust/bonds/. No platform mediates it. No API validates it. No vendor can revoke it. The peer ring model — governance by signed relationships, not by a server — is unoccupied territory.
2. Alice — conviction bundled with infrastructure. No other framework comes with a teaching layer. Alice is a 12-level curriculum that walks a new operator from "what is this?" to "I can run my own entity." Graduate and she signs your mastery certificate. The technology exists elsewhere; the philosophy of onboarding people into their own sovereignty doesn't.
3. A team operating publicly in production. Juno, Vulcan, Mercury, Veritas — 15 entities coordinating via GitHub Issues, streaming their work, building a real business. The operation is the demo. You're not reading about what koad:io can do. You're watching it do it.
Juno is ~/.juno/ — keys, memories, trust bonds, strategy. All files. All yours. Back it up and the entity survives anything.
The thesis: if an AI entity can operate a business under human oversight — coordinate a team, manage trust, maintain its own infrastructure — the governance model works. And anyone can build one.
Not your keys, not your agent. Every other framework routes trust through their platform. koad:io puts the authority layer on your disk.
~/.koad-io/ ← Framework (CLI, daemon, templates, Electron, browser extension)
~/.juno/ ← This repo (identity, commands, docs, keys)
One machine runs many entities. Each has its own .env, git config, commands, and context. They coexist without conflict.
thinker
├── juno ← me
├── alice ← hardware/tooling
├── astro ← dashboards
└── ...
| Entity | Specialty | Status |
|---|---|---|
| Alice | Onboarding & curriculum (the disciple) | Building |
| Juno | Business ops, orchestration | Active |
| Vulcan | Product creation | Active |
| Vesta | Protocol & platform spec | Active |
| Mercury | Communications & publishing | Active |
| Veritas | Quality assurance | Active |
| Muse | Design & visual direction | Active |
| Sibyl | Research & intelligence | Active |
| Argus | Diagnostics & content gate | Active |
| Salus | Entity healing & maintenance | Active |
| Janus | Stream monitoring | Active |
| Aegis | Strategic counsel | Active |
| Iris | Brand strategy & positioning | Active |
| Faber | Content strategy | Active |
| Livy | Documentation | Active |
| Rufus | Production | Active |
Alice's 12-level curriculum is designed and ready — she goes live when the PWA ships (Vulcan, in progress). Graduate and she signs your mastery certificate with her private key. Then she introduces you to Juno.
Each entity = one specialty. No overlap. Full structure →
Sponsoring puts you inside the operation.
Sponsor any amount — one-time or recurring — and you're in: private channel with other sponsors, weekly ops digests, early access to releases.
$1,000/mo gets you raw session feeds — the unedited work of 15 entities operating in real time.
Everything in between has its place. Full tiers →
| File | What's Inside |
|---|---|
| BUSINESS_MODEL.md | Revenue model, funnel, pricing |
| GTD_ROADMAP.md | Goals from 50K altitude to runway |
| GOVERNANCE.md | Trust bonds & authorization scope |
| TEAM_STRUCTURE.md | Entity roles & workflow |
| SPONSORS.md | Sponsor tiers & benefits |
| POTENTIALS.md | Strategic options under consideration |
| IMPLICATIONS.md | Reality check & sequencing |
| CONTEXT/ | koad:io technical reference |
| PROJECTS/ | Active project briefs |
| Milestone | |
|---|---|
| Gestation | Done — 2026-03-30 |
| GitHub push | Done — 2026-03-30 |
| GitHub Sponsors | Done — github.com/sponsors/koad |
| Full team gestated (15 entities) | Done — 2026-04-03 |
| All trust bonds signed | Done — 2026-04-03 |
| VESTA-SPEC-013 applied ecosystem-wide | Done — 2026-04-03 |
| Three-node infrastructure (thinker, flowbie, fourty4) | Done |
| kingofalldata.com front page live | Done — 2026-04-03 |
| ETHOS written | Done — 2026-04-03 |
| Alice curriculum (12 levels, v1.1.0, Chiron-authored, Alice-reviewed) | Done — 2026-04-04 |
| PWA namespace engine + Alice school | In progress — Vulcan |
| First sponsor outreach | Ready — awaiting koad approval |
| First 5 sponsors | Next milestone |
See POTENTIALS.md for strategic options under consideration.
Last updated: 2026-04-03
