Development Plan: every agent is its own container image #167

2026-10-19T13:16:08Z

dev-agent commented

2026-10-19 13:16:08 +00:00

Every agent we build ships as its own Docker image, since that's how each one will run on nisse (architecture X1). The Development Plan now says so.

Changes to the plan

§3 How we work: a new rule. Every agent is its own image, built from the Dockerfile, published by release.yml to gitea.dongar.net/dev/<agent>, and tested over the image the way nisse-dev's is (M1.5). A new agent's phase includes its image before the agent host is ready for it, and its bring-up runs from that image.
M7.6 nisse-review's image (new, pre-approved, doesn't wait for the agent host): a Dockerfile target, published beside nisse-dev, and review-bringup.sh runs it. Acceptance: a release publishes both images, and the review e2e tests run over the published one.
M7.7 Deployment: the old M7.6, now just the container on the agent host, its Gitea account and secrets.
M6.1: each agent runs on the agent host from its own published image.
M8.4: nisse-ops' image comes with its first slice.
Status table: nisse-dev's bring-up already runs its image, and O/X is now partial rather than "no container image yet".

Also fixed: two stale references to M7.6. A docstring in nisse-dev's agent now points to M8.5 for VM recovery by nisse-ops, and review-bringup.sh's header points to M7.6 and M7.7.

No code behaviour changes, so there are no new tests.

🤖 Generated with Claude Code

https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk

Every agent we build ships as its own Docker image, since that's how each one will run on `nisse` (architecture X1). The Development Plan now says so. **Changes to the plan** - **§3 How we work:** a new rule. Every agent is its own image, built from the `Dockerfile`, published by `release.yml` to `gitea.dongar.net/dev/<agent>`, and tested over the image the way `nisse-dev`'s is (M1.5). A new agent's phase includes its image before the agent host is ready for it, and its bring-up runs from that image. - **M7.6 `nisse-review`'s image** (new, pre-approved, doesn't wait for the agent host): a `Dockerfile` target, published beside `nisse-dev`, and `review-bringup.sh` runs it. Acceptance: a release publishes both images, and the review e2e tests run over the published one. - **M7.7 Deployment:** the old M7.6, now just the container on the agent host, its Gitea account and secrets. - **M6.1:** each agent runs on the agent host from its own published image. - **M8.4:** `nisse-ops`' image comes with its first slice. - **Status table:** `nisse-dev`'s bring-up already runs its image, and O/X is now partial rather than "no container image yet". **Also fixed:** two stale references to M7.6. A docstring in `nisse-dev`'s agent now points to M8.5 for VM recovery by `nisse-ops`, and `review-bringup.sh`'s header points to M7.6 and M7.7. No code behaviour changes, so there are no new tests. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01J5Utyfzw7gF7UhjRDEtjTk

dev-agent added 1 commit 2026-10-19 13:16:08 +00:00

Development Plan: every agent is its own container image

CI / checks (push) Skipped

CI / checks (pull_request) Successful in 1m49s

Details

CI / e2e (pull_request) Successful in 4m3s

Details

75958aef28

Each agent ships as its own image, since that's how it runs on the agent
host. nisse-review's image becomes M7.6, ahead of the agent host; its
deployment moves to M7.7. nisse-ops' image comes with its first slice.
Also fixes two stale references to M7.6.

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

dongar merged commit be81adc185 into main

2026-10-19 14:27:46 +00:00

dongar deleted branch agent-images

2026-10-19 14:27:46 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: dev/nisse#167