dongarandClaude Opus 5.5
2c9a082e5b
CI / checks (push) Skipped
CI / checks (pull_request) Successful in 53s
"Project" was carrying several things at once: the repo, the effort through arch plan and milestones, and the transcript's scope. The Sysadmin Agent needs the same distinctions in a different shape, with standing duties that produce many efforts over one scope. New section 0.2 names them: - Duty: a standing responsibility that produces work items, and owns deduplication of its findings - Work item: the unit of state, identified by a locally minted id (A9's task_id), optionally linked to an external record - Scope: what a work item operates on, shared across work items - Park-and-switch: one active work item, switching only at safe points, nothing lost while parked; the schema does not assume one 0.1 records this as a bounded exception to extract-after-it-works: identity is designed ahead, behaviour is not. A2, A4, A9, A10, B1/B2 and C4 now speak in these terms; the transcript is scoped per work item, and a milestone no longer mints a task_id. Part H parks concurrency with its costs, and leaves open when a work item must have an external record. Co-Authored-By: Claude Opus 5.5 (1M context) <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.