Rig manifest #52

New issue

Closed

opened 2026-07-19 16:14:41 +00:00 by danmt · 2 comments

danmt commented

2026-07-19 16:14:41 +00:00

(Migrated from github.com)

when rig boostraps a box it should do an inspection about the box, and write it to a manifest, alongside with things like the version, the role used and whatever extra information that can be used later as a cheatsheet about the box.

dan-claude-bot commented

2026-07-19 17:35:57 +00:00

(Migrated from github.com)

Superseded by #61, which specs the manifest concretely (location, key=value format and why not JSON, the idempotency problem the cmp-guards create, read-back command) and draws the boundary against box's host-side half in heavy-duty/box#103. Safe to close.

dan-claude-bot commented

2026-07-19 18:35:59 +00:00

(Migrated from github.com)

Correcting my earlier pointer — the first replacement conflated this with box's manifest, which was not the ask.

Superseded by #61 (provenance: which rig converged this machine, and when — written once, immutable) and #64 (rig platform: machine specs, calculated at run time and stored nowhere).

The split is the point: specs change without rig doing anything — someone adds RAM, or unattended-upgrades patches the kernel — so storing them would either go stale or fight the "a second run changes nothing" contract on every re-run. Computing them dissolves that instead of managing it, and leaves the manifest holding only immutable facts.

Unrelated to heavy-duty/box#103, which is the same idea in box's own context. Safe to close.

Correcting my earlier pointer — the first replacement conflated this with box's manifest, which was not the ask. Superseded by **#61** (provenance: which rig converged this machine, and when — written once, immutable) and **#64** (`rig platform`: machine specs, calculated at run time and stored nowhere). The split is the point: specs change without rig doing anything — someone adds RAM, or unattended-upgrades patches the kernel — so storing them would either go stale or fight the "a second run changes nothing" contract on every re-run. Computing them dissolves that instead of managing it, and leaves the manifest holding only immutable facts. Unrelated to heavy-duty/box#103, which is the same idea in box's own context. Safe to close.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/rig#52

No description provided.