Author the agentic-agency runtime topology DEC + spec (OKF→persona/runbook/team; coordinator/dispatch; per-tenant fleet isolation; Atrium+board+reconcile+MCP composition)
task-agency-runtime-topology-spec
Author the agentic-agency runtime topology DEC + spec
DONE (2026-06-18) — satisfied by DEC-0053. The ratifying topology DEC was authored and recorded via the log-auditor (per board convention, writing the DEC fulfills this task). It ratifies + PROMOTES DEC-0052's proposed OKF→agent mapping (
proposed→ratified), specifies the activation (delegateclaim()toDefaultBoardWorker, implementexecute()as a bounded Agent SDK session + the newcompilePersona), pins per-tenant fleet isolation (cross-tenant by construction; serialize intra-tenant drains → per-task worktrees) and the composition of board +reconcile()+ MCP, and the governance dial (human-onlydone; two-tier budget; thereviewgate). The DEC itself carriesconfidence: assertedwith its own Phase-0-implementation verification gate — but the authoring task is complete. Acceptance criteria annotated below.
One loop, three faces — ship an agentic Digital Experience Agency "in a box" (the Agency) plus an adoption-ladder readout product (the Ladder) over the OKF Company Brain, dogfood-first committed the north-star direction — an agentic Digital Experience Agency "in a box" grounded in the org's own OKF — but deliberately framed its architecture mapping as PROPOSED, to be ratified in a follow-on topology DEC. This task is that follow-on.
The work
Author the decision record + spec for the agentic-agency runtime topology:
- Ratify the OKF→agent mapping:
role→ subagent persona;process/workflow→ agent runbook/skill;capability→ a team; GraphRAG via MCP → shared context. - Coordinator / dispatch model: a coordinator agent (the Factory pattern) decomposes goals and dispatches to role-bounded teams; each agent is briefed from the org's own memory and writes back into it.
- Per-tenant fleet isolation: extend MCP agentic foundation — tenant-scoped GraphRAG over the OKF KB's one-server-one-tenant boundary to a whole agent fleet — no cross-tenant memory or dispatch leakage.
- Composition: how Atrium + the board (Agentic "sprint board" architecture — a git-resident OKF task board worked by bounded, hook-governed Agent SDK loops) +
reconcile()(The compounding merge — the per-tenant learning loop accumulates by id + confidence instead of overwriting (okf reconcile() + opt-in reconcile in extraction/runtime)) + MCP (MCP agentic foundation — tenant-scoped GraphRAG over the OKF KB) compose into one governed loop. - Governance dial: autonomy as a per-team/per-action setting sliding from deterministic (Alex L11) toward self-guided (Alex L14), gated by the human approve/ship loop.
Why a task, not a fix-in-place
This is a consequential architecture decision that needs the Principal Platform Architect's judgment to frame — exactly the "needs an owner's judgment" case the recorder routes to a task rather than authoring itself. confidence: inferred (agent-filed from DEC-0052's named follow-up).
Coordinate, don't duplicate
Ordering-hint dependency on Author the "Atrium" DEC — the live-layer-over-git co-working room (Yjs + self-hosted Y-Sweet; snapshot bridge → reconcile) — the topology composes Atrium, so the live-surface DEC should land (or co-land) so the composition is specified against a real surface. Board globbed before filing: Build the runtime BoardWorker seam (DefaultBoardWorker + reserved AgentSdkBoardWorker) is the narrower board-worker seam, not the full agency fleet topology.