dev/nisse

1 Fork 0

Files

T

History

dongarandClaude Opus 5.5 a8e2023183

CI / checks (push) Skipped

CI / checks (pull_request) Successful in 2m41s

Details

CI / e2e (pull_request) Successful in 4m25s

Details

The status page's walkthrough (M6.6b)

A new package, nisse-ui: a read-only page for studying how the agents
work. For each work item it shows the steps (what people and the
orchestrator said, and each run), each run's turns, and each turn's
request read against the log it was made from:
- each message beside the events it came from, tagged unchanged,
  labelled, narrated, shortened (by how much) or a compaction, with what
  fitting dropped;
- what is new since the turn before, and where the request first
  differs (where prompt reuse had to stop), next to the server's count;
- the reply with its reasoning, and the raw JSON.

Runs going in circles are flagged by nisse_core.loop.circles (repeated
near-identical replies, one correction given again and again, repeated
apologies), a pure function M7.8 can reuse in Driver.run.

In nisse-core:
- render.py: message_indexes(), from the same code render() uses, so
  the page's matching can't drift from what was sent.
- calls.py: the record notes when recording began; the reader gains
  calls_for(item) and call(id).
- state/readonly.py: opens an agent's SQLite file without creating its
  -wal/-shm files (mode=ro alone does, once the writer has closed).

The page reads only through read-only connections, escapes everything,
and sends a Content Security Policy that allows no script. It listens on
127.0.0.1; until M6.6d puts it behind Authelia, reach it over an SSH
tunnel. Jinja2 is its one new dependency, for autoescaping.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk

2026-10-25 03:36:50 +00:00

src/nisse_core

The status page's walkthrough (M6.6b)

2026-10-25 03:36:50 +00:00

tests

The status page's walkthrough (M6.6b)

2026-10-25 03:36:50 +00:00

pyproject.toml

M7.1: extract nisse-core

2026-10-13 18:37:01 +00:00

README.md

M7.2: share the loop's parts

2026-10-13 21:31:29 +00:00

README.md

nisse-core

The shared library the Nisse agents sit on (Part L of the architecture). It never imports an agent. Packages follow the architecture's sections:

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).
loop (L2): driver (a driver run, with the agent's waiting tools and executor), tools (the control tools any agent offers), expert (ask_expert, L9). Each agent keeps its own scheduler.
knowledge also has handlers: the vault and memory as control tools.
config: the shared parts of an agent's configuration.
At the top, until each gains a second module: gitea (the tracker and forge, L1), oplog and envfile (L12).