From 162ecc38c5710df3acb9326197bd6cc8ac07c385 Mon Sep 17 00:00:00 2001 From: reachableceo Date: Fri, 28 Aug 2026 18:45:45 -0500 Subject: [PATCH] DESIGN: verticals first-class, SoR-only interaction layer --- DESIGN.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/DESIGN.md b/DESIGN.md index 04f5bd2..7ce36e0 100644 --- a/DESIGN.md +++ b/DESIGN.md @@ -63,3 +63,13 @@ Harness aims for crush FEATURE PARITY on the agent core: tool calling, subagents (weak/medium/strong tiers), MCP client, sessions/resume, skills. v1 skeleton (tonight) = the headless subset; parity items land in ordered phases after the pilot. TUI explicitly stays out of scope. + +## Org model + interaction layer (Charles, 2026-08-28 evening) +- VERTICALS are first-class config: each vertical/stack = identity + LiteLLM + virtual key + budget + scope query + allowed tools. The harness natively + models the whole org (5 onstage + 3 offstage), not one loop. +- INTERACTION LAYER = Redmine (work/SoR), Discourse (docs/specs), Gitea (code, + PRs). Humans and other agents talk to a stack ONLY through these + git. +- _crossfeed files/doorbells/screens = internal implementation detail of the + legacy bash stack; harness keeps file state locally but never requires a + human to touch it. Chaining is in-process, not screen-stuffing.