9362a134c9a1d60772e239bc72d68ad123e415be
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 58s
Two loose ends in the A17 amendment, both found by asking whether the build order needed changing: - A17 requires retrieved content to be snapshotted into the canonical log, but A10's event table — the authoritative list — had no row for it, so an implementer reading A10 would never know to add one. knowledge_retrieved now carries the text as read, the document ID, its revision, and when it was read - Part G step 10 already scheduled Outline, so the ordering does not change; it now names A17 rather than only Part D, and says which half arrives first — the world model, with operator procedures waiting on the C2 taxonomy they bind to Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Nisse
Two self-hosted AI agents sharing a common library, named for the Nordic farm spirit that keeps the place running overnight and expects to be treated well in return.
| Package | Role |
|---|---|
nisse-core/ |
Shared library both agents sit on (Part A) |
nisse-dev/ |
Dev Agent — plans and implements software projects (Part B) |
nisse-ops/ |
Sysadmin Agent — operates infrastructure (Part C) |
One repository, three packages. The library does not exist as code yet: it is
extracted from nisse-dev once that agent works (build-order step 10), as a
package split within this tree.
Architecture
The system-level specification lives at
docs/Architecture-Build-Spec.md. It covers the
shared library, both agents, the supporting services, the build order, and the
remaining open decisions.