UKRRS/MOPAC
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

DESIGN: verticals first-class, SoR-only interaction layer

Browse Source
This commit is contained in:
mrcharles
2026-08-28 18:45:45 -05:00
parent 518effbadc
commit 162ecc38c5
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
DESIGN.md
+10
View File
@@ -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. subagents (weak/medium/strong tiers), MCP client, sessions/resume, skills.
v1 skeleton (tonight) = the headless subset; parity items land in ordered v1 skeleton (tonight) = the headless subset; parity items land in ordered
phases after the pilot. TUI explicitly stays out of scope. 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.