Repository map
NeKiro is maintained as a set of independently released repositories. This page gives one entry point without copying their source into Core.
| Repository | Canonical responsibility | Repository | Wiki |
|---|---|---|---|
| NeKiro Core | Control Plane, A2A Router, contracts, service-owned migrations, Core tests, architecture, and Core usage | NeKiro-project/NeKiro | This RepoWiki |
| NeKiro Console | Production Console and browser behavior | NeKiro-project/NeKiro-Console | Central RepoWiki |
| nekiro-sdk-go | Public Go Agent and application SDKs | NeKiro-project/nekiro-sdk-go | Central RepoWiki |
| NeKiro Samples | Independent sample Agent Runtimes, Cards, and sample-specific tests | NeKiro-project/NeKiro-Samples | Central RepoWiki |
| NeKiro Stack | Multi-component assembly, immutable release pins, and product acceptance | NeKiro-project/NeKiro-Stack | Central RepoWiki |
| nekiro-a2a-transport-go | Reusable A2A HTTP, JSON-RPC, and SSE transport mechanics | NeKiro-project/nekiro-a2a-transport-go | Central RepoWiki |
Release and verification order
- Core publishes versioned contracts and a verified Core revision.
- SDK, Console, Samples, and transport repositories verify against that identity.
- Stack pins immutable compatible revisions and runs product acceptance.
- Compatibility evidence remains visible for the exact Core commit.
The central Wiki documents this order; it does not become an alternate release authority. See ADR 0009 for the accepted ownership decision.