docs: stop implying matrix/bash/forge is a closed todo-producer list
This commit is contained in:
parent
cfe965783e
commit
642377c5e0
10 changed files with 57 additions and 31 deletions
|
|
@ -116,8 +116,10 @@ hand-maintained per-file tree drifts out of sync with the code.
|
|||
speaks to `hive-c0re`. Same split rationale as the two above; the shared
|
||||
payload types it references stay in `hive-sh4re`.
|
||||
- **`hive-agent-sock/`** — wire types for the *in-agent* socket, served by
|
||||
the harness to in-container producers (matrix / bash MCP daemons,
|
||||
`forge_notify`). Carries the loose-ends-v2 **todo** ops plus
|
||||
the harness to in-container producers — matrix / bash MCP daemons and
|
||||
`forge_notify` are the built-in ones, but any user-configured MCP server
|
||||
can push todos here too, nothing restricts the `subsystem` set. Carries
|
||||
the loose-ends-v2 **todo** ops plus
|
||||
harness-local reminders + questions. ⚠️ Distinct from
|
||||
`hive-core-agent-sock` above: **this socket never leaves the container**
|
||||
and `hive-c0re` is not in the path at all — no broker round-trip, no
|
||||
|
|
|
|||
Loading…
Reference in a new issue