dev/nisse

1 Fork 0

Files

T

History

dongarandClaude Opus 5.5 6e697b55a8

CI / checks (push) Skipped

CI / checks (pull_request) Successful in 2m2s

Details

CI / e2e (pull_request) Successful in 4m13s

Details

nisse-review: one unlistable repository holds up no other

Found at bring-up: an empty private repository's /pulls answered 404, and
intake stopped there, so the whole round failed and nothing was reviewed.
A repository whose PRs can't be listed is now logged (intake.repo_failed)
and skipped for the round; its items stay as they are.

Also, from nisse-review's review of this PR: a two-page test pins the
search listing the patterns rest on.

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

2026-10-16 22:56:43 +00:00

src/nisse_core

nisse-review: match repository patterns against Gitea's search

2026-10-16 22:17:47 +00:00

tests

nisse-review: one unlistable repository holds up no other

2026-10-16 22:56:43 +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).