nisse-core: group modules into packages by architecture section
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 1m37s
CI / e2e (pull_request) Successful in 4m5s

A pure move; behaviour unchanged.

- models (L9, L7): llm, catalog, probe, render, render_anthropic, context
- log (L7, L6): canonical, views
- state (L8): store (was state), reconcile, worker, cancel, dump
- knowledge (L10, L6.4): vault, memory
- conversation (L5): transport, matrix
- execution (L13): ssh (was execution), testing
- authority (P3, P4, L4): actions
- gitea, oplog, envfile stay at the top until each gains a second module.

Every import, monkeypatch target, script and doc reference rewritten.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk
This commit is contained in:
dongarandClaude Opus 5.5 committed 2026-10-13 21:16:09 +00:00
1 parent 06759d5d70
commit e351d0a74e
117 files changed
+291 -265

No files matched your search

+19 -17
View File
@@ -1,22 +1,24 @@
# nisse-core
The shared library the Nisse agents sit on (Part L of the architecture). It
never imports an agent.
never imports an agent. Packages follow the architecture's sections:
- **Transcript and models:** `canonical` (the log's events, L7), `render` and
`render_anthropic`, `llm` (the one client, L9), `catalog` and `probe` (what
the models are), `context` (fitting a request to its window, L6), `views`
(what each role is shown of the others).
- **Durability:** `state` (the store, L8; an agent subclasses it for its own
tables, roles and views), `reconcile`, `worker`, `cancel`, `dump`.
- **Conversation:** `transport`, `matrix` (L5).
- **Execution:** `execution` (SSH to a tool VM, L13); `testing` (a throwaway
sshd for tests).
- **Knowledge:** `vault` (L10), `memory` (L6.4).
- **Operations:** `oplog`, `envfile` (L12); `gitea` (the tracker and forge, L1).
- **Authority:** `actions` (P3, P4, L4): `Action`, `Verdict`, and static
reading of shell commands, which each agent's fast-path rules build on
(`nisse-dev`'s are in `nisse_dev.loop.actions`).
- `models` (L9, L7): `llm` (the one client), `catalog` and `probe` (what the
models are), `render` and `render_anthropic` (request bodies from the log),
`context` (fitting a request to its window, L6).
- `log` (L7, L6): `canonical` (the log's events), `views` (what each role is
shown of the others).
- `state` (L8): `store` (an agent subclasses `StateStore` for its own tables,
roles and views), `reconcile`, `worker`, `cancel`, `dump`.
- `knowledge` (L10, L6.4): `vault`, `memory`.
- `conversation` (L5): `transport`, `matrix`.
- `execution` (L13): `ssh` (SSH to a tool VM); `testing` (a throwaway sshd for
tests).
- `authority` (P3, P4, L4): `actions` (`Action`, `Verdict`, and static reading of
shell commands, which each agent's fast-path rules build on; `nisse-dev`'s are
in `nisse_dev.loop.actions`).
- At the top, until each gains a second module: `gitea` (the tracker and forge,
L1), `oplog` and `envfile` (L12).
The loop is still `nisse-dev`'s, until `nisse-ops` has one to share it with
(Development Plan M7.2).
The parts of a loop (`loop`) and shared configuration arrive with Development
Plan M7.2; each agent keeps its own scheduler.