dev/nisse

1 Fork 0

Files

T

History

dongarandClaude Opus 5.5 dd060566b2

CI / checks (push) Skipped

CI / checks (pull_request) Successful in 2m54s

Details

CI / e2e (pull_request) Successful in 4m20s

Details

The call record: every model call, for the operator's study (M6.6a)

nisse-core records each model call of every agent into a file beside its
state store (<state>.calls.db), for the status page (L7, X6):

- the request body exactly as sent (never headers), the raw response with
  its reasoning, the model asked and the one that answered, time, tokens
  and llama-server's own prompt reuse (timings.cache_n);
- its work item, role, run and purpose: Driver.run and nisse-dev's
  delegation loop open runs, nested; compaction, expert consults, the
  classifier and the go-ahead reader label their calls;
- provenance, worked out in BudgetedClient by comparing the events at
  each stage: each event sent with its log id and content as sent, which
  a compaction replaced, which fitting shortened (by how much) and
  dropped.

Content is stored once by hash, compressed. It is diagnostic only: the
agent never reads it, a failed write is logged once and recording stops
while the call goes on, and the file is deleted when the agent starts,
so its layout never migrates; CallReader refuses a layout it doesn't
know. While recording, the system prompt ends with one sentence saying
so. `call_record: false` in either agent's YAML turns it off.

The benchmark records each run beside that run's own state store, and
`--keep-runs DIR` keeps both for the page.

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

2026-10-24 06:28:53 +00:00

src/nisse_core

The call record: every model call, for the operator's study (M6.6a)

2026-10-24 06:28:53 +00:00

tests

The call record: every model call, for the operator's study (M6.6a)

2026-10-24 06:28:53 +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).