Beta-Techno

Autonomous Engineering System with Contract and Policy Authority

This page is the shortest complete map of the system. Left side is the agent execution plane. Right side is the machine and runtime substrate. Together they define what can run, what is allowed to run, and how outcomes stay auditable and replay-safe.

Contract First Policy Enforced Deterministic Replay No Silent Mutation Sovereign Runtime

Why

Run high-capability model work as an auditable system, not as untracked terminal sessions.

What

Swarm executes and reconciles agent work; Infra supplies identity, substrate, runtime hosting, and durability.

How

runfmt-spec and charter constrain behavior across repos; runtime components enforce those contracts.

Operator Promise

Every high-impact action is attributable, reversible where possible, and represented as machine-readable evidence.

Rendering topology…

Swarm Plane Repositories

Canonical execution, orchestration, policy, contract, memory, and operator surfaces.

Repo	Primary role	Authority	Status
`kernel`	Agent execution runtime	Session process + tool runtime + artifacts	active
`conductor`	Run adapter + validation boundary	Machine envelope + bundle verification	active
`daemon`	Authoritative mutation engine	State transitions + token fencing + durability	active
`console`	Turn/session reconciliation	Projection of daemon and run outcomes into canonical turn state	active
`gateway`	External ingress/egress boundary	Operator/API access mediation into swarm control-plane	active
`runfmt-spec`	Cross-repo contract authority	Machine-readable schemas and compatibility examples	active
`charter`	Policy authority	Governance requirements and compliance baselines	active
`deck`	Human command surface	Operator control and oversight UI over swarm components	active
`ledge`	Memory and retrieval substrate	Session/run indexing and retrieval for long-horizon context	active
`relay`	Sovereign comms abstraction	Unified cross-channel message layer for operator-agent interaction	planned

Infra Plane Repositories

Identity, machine bring-up, host config, runtime hosting, durability, and org-wide baseline enforcement.

Repo	Primary role	Authority	Status
`ops`	Substrate operations	Hypervisor/cloud substrate control	active
`bricks`	Provisioning modules	Reusable infrastructure building blocks	active
`boot`	Bootstrap bridge	First-run machine initialization path	active
`anvil`	Host state runtime	Mutable host/runtime integration layer	active
`flakes`	Declarative host/env model	Reproducible machine and toolchain configuration	active
`dotfiles`	Operator shell defaults	User-level runtime baseline	active
`atlas`/`mani`	Workspace graph	Repository topology and synchronization context	active
`key`	Bootstrap identity	Root key material initialization	active
`lock`	Secrets authority	SOPS-encrypted secret/config source of truth	active
`harbor`	Runtime hosting	Container/service execution substrate	active
`keep`	Durability and recovery	Backup/restore continuity boundary	active
`profile`	Org standard enforcer	Cross-repo baseline checks and policy execution	in progress

Operational Bring-up Order

runfmt-spec + charter loaded as contract/policy roots.
boot and identity roots (key/lock) initialize trust and secret context.
ops/bricks + anvil/flakes/dotfiles establish substrate and host behavior.
harbor + keep establish runtime hosting and durability.
Swarm services start in loop coherence: kernel → conductor → daemon → console → gateway.
deck and ledge surface operator control and memory.