cronekorkn/left4me
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

spec(deployment-responsibility): mark handoff resolved by the design doc

Browse source 
Brainstorm happened; design at 2026-05-15-deployment-responsibility-design.md.
Handoff doc stays as the historical framing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
mwiegand 2026-05-15 18:51:12 +02:00
parent c446f6c8eb
commit ddf97b3a05
No known key found for this signature in database
1 changed files with 11 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/superpowers/specs/2026-05-15-handoff-deployment-responsibility.md
View file

@ -2,11 +2,17 @@
## Status ## Status
Queued for a future session, **after the uid-collapse refactor lands** **Resolved 2026-05-15** — the brainstorming session happened and produced
(`docs/superpowers/plans/2026-05-15-uid-collapse.md`). This is a `docs/superpowers/specs/2026-05-15-deployment-responsibility-design.md`.
framing doc for a brainstorming session, not an implementation plan. Read that for the answer. The runtime-state relocation
The brainstorming session should use `superpowers:brainstorming` and (`2026-05-15-runtime-state-relocation-design.md`) shipped as a prereq;
exit with a design doc; implementation follows separately. the design lands hardening drop-ins, sudoers, sysctl, and helpers as
symlinks into the (now root-owned) `/opt/left4me/src/deploy/...`
checkout, while base unit bodies and per-host shape stay bw-managed.
This doc is kept as the historical framing — the question that opened
the brainstorm, the operator's leaning, and the candidate options that
got evaluated. The actual landed answer is the design doc.
## The question ## The question