Documentation
System Overview
AgenC is a split public system:
Last updated: 2026-04-30
Topology
The runtime graph is intentionally centered on one authority: the daemon or gateway. CLI, dashboard, hosted adapters, and shell sessions are clients of that authority, not separate runtimes.
| Area | Source repo/package | Owns |
|---|---|---|
| Operator runtime | tetsuo-ai/agenc-core, @tetsuo-ai/agenc | daemon, CLI, shell, dashboard, runtime policy, marketplace job specs |
| Public SDK | @tetsuo-ai/sdk | client builders for protocol/runtime flows |
| Protocol package | tetsuo-ai/agenc-protocol, @tetsuo-ai/protocol | Anchor program, IDL, launch controls, committed artifacts |
| Plugin boundary | @tetsuo-ai/plugin-kit | hosted adapter authoring contract |
| Prover service | tetsuo-ai/agenc-prover | private ZK proving path, outside base canary |
| Explorer / ops | public explorer and operator environment | read model, indexing, alert evidence, incident visibility |
Core product contract
The public framework product contract is defined in agenc-core:
@tetsuo-ai/agenc@0.2.0agencdashboard all attach to that same daemon
control plane
That means:
agenc, agenc shell, connectors, and agenc ui are not separate runtimesthrough one local authority
Public builder contract
External builders should target these packages:
@tetsuo-ai/sdk@1.4.0@tetsuo-ai/protocol@0.2.0@tetsuo-ai/plugin-kit@0.2.0The implementation packages inside agenc-core remain repo-internal or kernel-internal. They are intentionally not the public extension story.
Protocol boundary
The public on-chain boundary lives in tetsuo-ai/agenc-protocol. That repository owns:
@tetsuo-ai/protocol packageIt does not own runtime orchestration, dashboard code, or proving infrastructure.
Current operator install matrix
Current supported public install tuple for the tagged @tetsuo-ai/agenc@0.2.0 wrapper manifest:
x64>=18.0.0agenc-core main has landed macOS arm64 runtime-artifact support for the next wrapper release.
Current hosted adapter contract:
@tetsuo-ai/plugin-kit@0.2.0 is the public authoring contract forchannel_adapter extensions
Current devnet and canary state
Current devnet/canary coordination program:
2jdBSJ8U5ixfwgs1bRLPtRRnpZAPm8Xv1tEdu8yjHJC7The current base mainnet-v1 work is a constrained low-value marketplace canary:
Excluded from the base canary:
Read next
/docs/protocol/architecture/docs/runtime/api/docs/guides/version-map/docs/guides/package-surfaces/docs/deployment/devnet-validation