disk: a minted scratch Zuse pair, for v4 work with Zuse attached
disk/zuse-scratch/artemis.img and zuse-thumb-ident.img, minted from blank by a system=v3 amd64 boot (genesis minted) and confirmed by a second (identity confirmed); both logs included. The genesis marker is on the Artemis disk, so the two are a pair. The committed artemis.img and thumbdrives/zuse-thumb-ident.img are not touched. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5.5
parent
eef6c15c28
commit
1f157e9785
@@ -146,6 +146,20 @@ carrying timestamp noise in git history.
|
||||
GPT-partition-relative offset together once a GPT parser exists, not
|
||||
attempted ahead of that.
|
||||
|
||||
- `zuse-scratch/artemis.img` + `zuse-scratch/zuse-thumb-ident.img` — a minted
|
||||
Zuse pair, added 2026-10-26 (Captain Bob: "mint a scratch zuse drive", and
|
||||
commit it) so that v4 work can go ahead with Zuse attached (`ENGINE.md` §2,
|
||||
the identity gate). Minted from blank (1 GiB / 64 MiB) by a `system=v3` amd64
|
||||
boot (`logs/20261026-081016`: "Zuse: genesis minted onto attached
|
||||
thumbdrive") and confirmed by a second (`logs/20261026-081116`: "Zuse:
|
||||
identity confirmed from attached thumbdrive"). **The two are a pair:** the
|
||||
genesis marker naming Zuse's public key is on the Artemis disk's metadata
|
||||
fence, so the thumbdrive is recognised only with this `artemis.img`. Boot
|
||||
with `ARTDISK=` and `ZUSEDISK=` pointing at *copies*, so the committed pair
|
||||
stays as minted. Not a re-mint of the committed `artemis.img` /
|
||||
`thumbdrives/zuse-thumb-ident.img`, which stay blank (that call is Captain
|
||||
Bob's).
|
||||
|
||||
**Convention, standing as of 2026-08-22: every virtual disk/thumb-drive image
|
||||
used for testing — Artemis persistence disks above, and USB Mass Storage
|
||||
backing images alike — lives in this directory and is a tracked, committed
|
||||
|
||||
Binary file not shown.
Binary file not shown.
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user