dongarandClaude Opus 5 67aa82371e
CI / checks (push) Failing after 6s
Externalise plans to Gitea and accept approvals there (A4, Part H)
- approvals.py: PlanBoard opens one issue per project and posts each
  plan revision as a comment carrying its rev tag. The state store
  keeps only a pointer, so gate state can be re-derived from Gitea
  after a state-volume loss — external truth wins
- Gitea comments are a second approval source: revision binding, the
  typed word approve, and first-approval-wins work exactly as over
  transport, with a per-channel allowlist because a Gitea login is
  not a Matrix MXID
- Outcomes are echoed to the other channel, so the two records cannot
  silently disagree about what was approved
- A Gitea outage degrades durability of the record, not the ability
  to approve: planning proceeds and Matrix remains a complete channel
- Live test now asserts the server refuses the agent's own merge and
  its push to the protected branch. That property was previously
  true only because our code did not attempt it; branch protection
  makes it structural, and this test fails if the protection is ever
  relaxed
- Fixed a race in the process-group test: killing a group is
  asynchronous and the grandchild is an orphan, so its exit is not
  synchronised with our return; the test now waits for death

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-07 22:14:05 +00:00

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.

S
Description
LLM Agents for specialized tasks.
Readme
4.4 MiB
1 Stars 2 Watchers 0 Forks
v0.1.0
Latest
2026-10-07 22:39:30 +00:00
Languages
Python 98.1%
Shell 1.6%
Dockerfile 0.3%