agentteams

Version	2026.223.1500
Repo	box/github.com/opencharly/layer-agentteams:v2026.240.0118

The AgentTeams top composition: the controller plus the four foundation services it embeds in one container — agentteams-minio (MinIO S3 + mc-mirror), agentteams-matrix (Tuwunel Matrix homeserver), agentteams-element (Element Web via rootless nginx), agentteams-higress (the Higress AI gateway: apiserver, controller, pilot, envoy gateway, console), and agentteams-controller (the kine-backed kube-apiserver + Manager/Worker/Team/Human reconciler serving the REST API on :8090). Every service runs as the image user (uid 1000) against its own home-relative volume (~/.agentteams/minio, ~/.agentteams/matrix, ~/.agentteams/higress, ~/.agentteams/controller) — the rootless charly architecture, no root anywhere, and each candy installable alone or together with any other. All service start scripts are charly-owned (written by the candies), not upstream AgentTeams scripts. Spawned Manager/Worker containers join the charly network and reach the controller — and every in-container service — by the controller container’s DNS name.

Acceptance plan

This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.

Intent	Step
check	the full AgentTeams composition is present (controller, minio, matrix, element, higress)