runtime

Universal execution-substrate contract for the TAU ecosystem.

go get github.com/tailored-agentic-units/runtime

Status

Pre-contract, scaffolding only. The module is initialized; the Runtime interface and its implementations land in Phase 3 of the TAU platform execution plan, after the kernel's post-extraction refactor clarifies what the contract needs.

See _project/README.md for the project overview and _project/runtime-contract.md for the guiding concept doc.

Intended Architecture

The root module will expose the Runtime interface, a factory registry, and the supporting types for the four universal responsibility areas (perception, actuation, capability declaration, attach/detach lifecycle). Concrete implementations live in sub-modules with their own go.mod.

runtime (root)             — Runtime interface, registry, shared types
  native/                  — direct execution on physical hosts (dev, edge, embedded)
  container/               — container family (lifecycle, images, manifest, labels)
    docker/                — Docker backend

• native — reference implementation. Platform variation (development machines, edge devices, embedded systems) is an internal concern of the sub-module, not a reason to split further.
• container — container-family base. Adds OCI-flavored concerns (image lifecycle, capability manifest, labels) on top of the universal contract.
• container/docker — Docker Engine API backend.

Sub-modules are created as their phase arrives: native/ in Phase 3, container/ and container/docker/ in Phase 6.

Dependencies

• Root: standard library only (contract types, registry).
• Sub-modules: root + substrate-specific dependencies (Docker client, etc.).