dev/nisse

1 Fork 0

Files

T

History

dongarandClaude Opus 5.5 d02f8c1fbb

CI / checks (push) Skipped

CI / checks (pull_request) Successful in 2m35s

Details

CI / e2e (pull_request) Successful in 4m6s

Details

The status page's overview (M6.6c)

The home page now shows, per agent: the run under way (or idle since
when, and runs a crash may have left open), the active item, nisse-dev's
queue in its own order with items on a blocked build VM held out, parked
items with their wait and note, blocked items and VM blocks, review PRs
by position, and the last ten closed. Kept benchmark runs follow.

Item data is read tolerantly (nisse-dev's own parser refuses unknown
fields); contract tests write items with the agents' own code. Links to
issues, PRs and threads come from --config NAME=YAML, reading only the
Gitea address, the Matrix room and each project's repo and build VM.
The page reloads every minute by meta refresh; ?refresh=0 stops it.

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

2026-10-26 04:45:38 +00:00

src/nisse_core

The status page's overview (M6.6c)

2026-10-26 04:45:38 +00:00

tests

The status page's overview (M6.6c)

2026-10-26 04:45:38 +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).