amadan
docs: cohort-1 step 5 package final: publish-record commands, signer values
- Step 5.0: exact SSM send-command forms from DOCS-T1 for leo and sophie wrapping the systemd-run publish-record, with the first-run and verify re-run lines verbatim from main 3b69c2bd; read-only confirmation that both boxes run v0.28.1 (binary 2ae174da...) and that --help exits 0. Step 5 is unblocked (v0.28.1 on dev). - policy.json, identity.json and console-path move to step 6 as byte-exact files (policy from --out, identity fetched unchanged), never parsed; .prev may equal current. - signing-host.md: AMI, VPC and subnet checked current; carlos v0.28.1 linux-arm64 sha256 from the signature-verified SHA256SUMS.txt; jq 1.7.1 arm64 sha256 computed on DOCS-T1; security group TO-CREATE. - Inputs README: console sha256 from the console app's signed release manifest, never SHA256SUMS; open items split into TO-CONFIRM, TO-CREATE and BLOCKED.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
3 files changed,
+84
−31
docs/superpowers/notes/claim-trial-inputs/README.md+17 −14docs/superpowers/notes/claim-trial-inputs/signing-host.md+11 −5docs/superpowers/plans/2026-10-16-claim-activation-dev-cohort1.md+56 −12
CI passed — run details
CI log
=== gate ===
cd launchctx && go vet ./... && go test ./... -count=1
ok amadan.net/carlos/platform.git/launchctx 0.011s
? amadan.net/carlos/platform.git/launchctx/controlname [no test files]
? amadan.net/carlos/platform.git/launchctx/wireid [no test files]
go vet ./...
gofmt -l .: clean
go test ./... -count=1 -timeout 30m
ok github.com/carlosframework/platform 301.767s
? github.com/carlosframework/platform/cmd/changelog [no test files]
ok github.com/carlosframework/platform/cmd/console 3.193s
ok github.com/carlosframework/platform/cmd/moveprobe 92.184s
ok github.com/carlosframework/platform/cmd/zddprobe 0.701s
ok github.com/carlosframework/platform/internal/activator 250.445s
ok github.com/carlosframework/platform/internal/agentsock 0.014s
ok github.com/carlosframework/platform/internal/alerting 0.004s
ok github.com/carlosframework/platform/internal/analytics 0.018s
ok github.com/carlosframework/platform/internal/appconfig 2.536s
ok github.com/carlosframework/platform/internal/apperr 0.071s
ok github.com/carlosframework/platform/internal/applog 0.119s
ok github.com/carlosframework/platform/internal/awsinv 0.003s
ok github.com/carlosframework/platform/internal/boxchoice 0.004s
ok github.com/carlosframework/platform/internal/boxid 0.447s
? github.com/carlosframework/platform/internal/boxid/boxidtest [no test files]
? github.com/carlosframework/platform/internal/boxid/internal/signtest [no test files]
ok github.com/carlosframework/platform/internal/boxvolumes 0.008s
ok github.com/carlosframework/platform/internal/caps 0.012s
ok github.com/carlosframework/platform/internal/certwarm 0.002s
ok github.com/carlosframework/platform/internal/cgroup 0.690s
ok github.com/carlosframework/platform/internal/changelog 0.300s
ok github.com/carlosframework/platform/internal/claimactivation 0.023s
ok github.com/carlosframework/platform/internal/clamd 0.054s
? github.com/carlosframework/platform/internal/cliflag [no test files]
ok github.com/carlosframework/platform/internal/console 405.943s
? github.com/carlosframework/platform/internal/controlname [no test files]
? github.com/carlosframework/platform/internal/controlsock [no test files]
ok github.com/carlosframework/platform/internal/dbdoor 5.736s
ok github.com/carlosframework/platform/internal/dbdoor/dbdoortest 0.008s
ok github.com/carlosframework/platform/internal/dbverify 0.004s
ok github.com/carlosframework/platform/internal/dnsrec 0.005s
ok github.com/carlosframework/platform/internal/docsite 0.005s
ok github.com/carlosframework/platform/internal/domains 2.406s
ok github.com/carlosframework/platform/internal/doorkey 0.006s
ok github.com/carlosframework/platform/internal/economics 0.004s
ok github.com/carlosframework/platform/internal/edge 44.919s
? github.com/carlosframework/platform/internal/edgeproof [no test files]
ok github.com/carlosframework/platform/internal/edgesfile 0.008s
ok github.com/carlosframework/platform/internal/fleetapi 0.133s
ok github.com/carlosframework/platform/internal/gate 1.654s
ok github.com/carlosframework/platform/internal/genselect 0.015s
ok github.com/carlosframework/platform/internal/geo 0.016s
ok github.com/carlosframework/platform/internal/geoip 0.030s
ok github.com/carlosframework/platform/internal/historyreadback 0.150s
ok github.com/carlosframework/platform/internal/host 175.046s
ok github.com/carlosframework/platform/internal/hostactors 0.506s
ok github.com/carlosframework/platform/internal/hostbox 2.630s
ok github.com/carlosframework/platform/internal/hostclaim 0.528s
ok github.com/carlosframework/platform/internal/hostevidence 0.009s
ok github.com/carlosframework/platform/internal/hostexec 4.743s
ok github.com/carlosframework/platform/internal/hostfence 0.033s
ok github.com/carlosframework/platform/internal/hostfiles 10.425s
ok github.com/carlosframework/platform/internal/hostfloor 0.012s
ok github.com/carlosframework/platform/internal/hostguard 1.004s
ok github.com/carlosframework/platform/internal/hostops 1.632s
? github.com/carlosframework/platform/internal/hostops/fencerelease [no test files]
ok github.com/carlosframework/platform/internal/hostops/internal/fencerelease 0.010s
ok github.com/carlosframework/platform/internal/hostquarantine 0.010s
ok github.com/carlosframework/platform/internal/hostrelocate 0.472s
ok github.com/carlosframework/platform/internal/hostresolve 0.131s
ok github.com/carlosframework/platform/internal/hostwrite 0.011s
ok github.com/carlosframework/platform/internal/infraview 0.011s
ok github.com/carlosframework/platform/internal/instancectl 5.214s
ok github.com/carlosframework/platform/internal/instanceexec 2.731s
ok github.com/carlosframework/platform/internal/instancefs 0.014s
ok github.com/carlosframework/platform/internal/instancekey 0.011s
ok github.com/carlosframework/platform/internal/instanceupdates 0.007s
ok github.com/carlosframework/platform/internal/layout 1.519s
ok github.com/carlosframework/platform/internal/lbhealth 0.002s
ok github.com/carlosframework/platform/internal/lease 9.810s
ok github.com/carlosframework/platform/internal/lease/leasetest 0.006s
ok github.com/carlosframework/platform/internal/ledger 0.011s
ok github.com/carlosframework/platform/internal/mail 0.174s
ok github.com/carlosframework/platform/internal/maintenance 0.094s
ok github.com/carlosframework/platform/internal/maintenanceexec 5.487s
ok github.com/carlosframework/platform/internal/maintenanceguard 0.074s
ok github.com/carlosframework/platform/internal/metrics 0.004s
ok github.com/carlosframework/platform/internal/moves 21.150s
ok github.com/carlosframework/platform/internal/moves/archive 0.793s
ok github.com/carlosframework/platform/internal/objstore 0.181s
ok github.com/carlosframework/platform/internal/ops 0.172s
ok github.com/carlosframework/platform/internal/park 0.201s
ok github.com/carlosframework/platform/internal/privatefile 0.005s
ok github.com/carlosframework/platform/internal/provision 17.131s
ok github.com/carlosframework/platform/internal/publicrelease 0.006s
? github.com/carlosframework/platform/internal/regionname [no test files]
ok github.com/carlosframework/platform/internal/registry 5.401s
ok github.com/carlosframework/platform/internal/relay 7.228s
ok github.com/carlosframework/platform/internal/release 21.437s
ok github.com/carlosframework/platform/internal/rollout 3.603s
ok github.com/carlosframework/platform/internal/rolloutwords 0.003s
ok github.com/carlosframework/platform/internal/rootaws 0.006s
ok github.com/carlosframework/platform/internal/rootparticipation 0.057s
ok github.com/carlosframework/platform/internal/rootstate 0.026s
ok github.com/carlosframework/platform/internal/runs 0.574s
ok github.com/carlosframework/platform/internal/s3compat 0.005s
ok github.com/carlosframework/platform/internal/safefile 0.004s
ok github.com/carlosframework/platform/internal/schedule 2.482s
ok github.com/carlosframework/platform/internal/seeds 0.010s
ok github.com/carlosframework/platform/internal/sim/hostlife 8.512s
ok github.com/carlosframework/platform/internal/sim/litestreamfacts 3.961s
ok github.com/carlosframework/platform/internal/status 0.043s
ok github.com/carlosframework/platform/internal/steering 0.005s
ok github.com/carlosframework/platform/internal/stopevidence 0.246s
ok github.com/carlosframework/platform/internal/svcrole 0.002s
ok github.com/carlosframework/platform/internal/telemetry 0.004s
ok github.com/carlosframework/platform/internal/termfence 0.004s
ok github.com/carlosframework/platform/internal/tunnelclient 0.004s
ok github.com/carlosframework/platform/internal/unixdial 0.002s
ok github.com/carlosframework/platform/internal/updatewords 0.004s
ok github.com/carlosframework/platform/internal/usage 0.004s
ok github.com/carlosframework/platform/internal/version 0.001s
ok github.com/carlosframework/platform/internal/vet 1.536s
=== cross ===
--- shard 0 of 5 ---
cross-compiling darwin/arm64
--- shard 1 of 5 ---
cross-compiling darwin/amd64
--- shard 2 of 5 ---
cross-compiling linux/arm64
linux/arm64 carlos binary: 48824482 bytes (ceiling 52000000)
--- shard 3 of 5 ---
cross-compiling windows/amd64
--- shard 4 of 5 ---
cross-compiling windows/arm64
=== minio-contract ===
minio contract: arm64, minio RELEASE.2025-09-07T16-13-09Z, mc RELEASE.2025-08-13T08-35-41Z
minio: cached, digest verified
mc: cached, digest verified
minio healthy on 127.0.0.1:20999
Added `local` successfully.
Bucket created successfully `local/contract-bucket`.
Bucket created successfully `local/denied-bucket`.
Created policy `contract-only` successfully.
Added user `scopeduser` successfully.
Attached Policies: [contract-only]
To User: scopeduser
buckets and scoped user ready
=== RUN TestDeliveredContractMinio
=== RUN TestDeliveredContractMinio/put
=== RUN TestDeliveredContractMinio/get_round-trips_the_body
=== RUN TestDeliveredContractMinio/list_shows_the_key
=== RUN TestDeliveredContractMinio/head_and_list_agree_on_the_version
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_its_own_object
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_its_own_object/not_by_PutObjectTagging
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_its_own_object/and_not_by_x-amz-tagging_on_upload
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/not_by_CreateMultipartUpload
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/not_by_CopyObject_with_a_REPLACE_tagging_directive
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/but_multipart_itself_is_allowed
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/and_copy_itself_is_allowed
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/a_POST-policy_forged_tag_with_a_matching_version_is_still_not_a_verdict
=== RUN TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/and_an_ordinary_tagged-with-something-else_upload_is_allowed
=== RUN TestDeliveredContractMinio/delete_removes_it
=== RUN TestDeliveredContractMinio/cross-bucket_denial
--- PASS: TestDeliveredContractMinio (0.02s)
--- PASS: TestDeliveredContractMinio/put (0.00s)
--- PASS: TestDeliveredContractMinio/get_round-trips_the_body (0.00s)
--- PASS: TestDeliveredContractMinio/list_shows_the_key (0.00s)
--- PASS: TestDeliveredContractMinio/head_and_list_agree_on_the_version (0.00s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_its_own_object (0.00s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_its_own_object/not_by_PutObjectTagging (0.00s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_its_own_object/and_not_by_x-amz-tagging_on_upload (0.00s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route (0.01s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/not_by_CreateMultipartUpload (0.00s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/not_by_CopyObject_with_a_REPLACE_tagging_directive (0.00s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/but_multipart_itself_is_allowed (0.00s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/and_copy_itself_is_allowed (0.00s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/a_POST-policy_forged_tag_with_a_matching_version_is_still_not_a_verdict (0.00s)
--- PASS: TestDeliveredContractMinio/the_app_cannot_tag_by_any_other_route/and_an_ordinary_tagged-with-something-else_upload_is_allowed (0.00s)
--- PASS: TestDeliveredContractMinio/delete_removes_it (0.00s)
--- PASS: TestDeliveredContractMinio/cross-bucket_denial (0.00s)
PASS
ok github.com/carlosframework/platform/internal/objstore 0.021s
=== RUN TestT4StorageProbeMinio
2026/10/18 06:05:35 moves: T4: STORE: list: operation error S3: ListObjectsV2, https response error StatusCode: 403, RequestID: 18DF8A91E61DB67A, HostID: 7c420053e0fbcd7f41653fdd92ffa2802c903d05303b1aa15adc2e8bb65d183f, api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method.
--- PASS: TestT4StorageProbeMinio (0.00s)
PASS
ok github.com/carlosframework/platform/internal/host 0.020s
minio contract: PASS
diff --git a/docs/superpowers/notes/claim-trial-inputs/README.md b/docs/superpowers/notes/claim-trial-inputs/README.md| index 3917b2e84..b043f5279 100644 |
| --- a/docs/superpowers/notes/claim-trial-inputs/README.md |
| +++ b/docs/superpowers/notes/claim-trial-inputs/README.md |
| @@ -15,8 +15,8 @@ Platform main at drafting: `b1118925` (region HA 2b). The box-record verb is on |
| | `sophie.json` | step 5, `invite-box` and `enroll-box` | `claimactivation.BoxInput` | |
| | `console.json` | step 5, `invite-console` and `enroll-console` (the runbook's `jq` adds `compute` after sophie enrolls) | `hostactors.Console` | |
| | `floor.json` | step 7, `publish-floor` | `hostfloor.Floor` | |
| -| `policy.template.json` | step 6, `guard-arm --policy` | `hostfloor.Policy`, unsigned template | |
| -| `identity.template.json` | step 6, `guard-arm --identity` | signed system pointer, unsigned template | |
| +| `policy.template.json` | step 6, `guard-arm --policy` | `hostfloor.Policy`, unsigned template (shape only; the real file is byte-exact from `--out`) | |
| +| `identity.template.json` | step 6, `guard-arm --identity` | signed system pointer, unsigned template (shape only; the real file is byte-exact from the bucket) | |
| | `signing-host.md` | steps 5 and 7, the trusted signing host | proposal | |
| ## Values and where they come from |
| @@ -43,14 +43,14 @@ Platform main at drafting: `b1118925` (region HA 2b). The box-record verb is on |
| | Artifact | Value | Status | |
| |---|---|---| |
| -| Release for step 5 | v0.28.1, dev only (box-record verb) | TO-CONFIRM: being cut | |
| +| Release for step 5 | v0.28.1, dev only (box-record verb), `3b69c2bd`, published 2026-10-18; on leo, sophie, dennis and the dev console. `carlos-linux-arm64` sha256 `2ae174da29b1d10fdcb009172ba830db5460b62e838bcecc7d9e17535f35adea` (signed `SHA256SUMS.txt`, verified) | confirmed | |
| | Release for step 6 onwards | v0.28.2 (armed policy signing phase, published system identity, protected console install) | TO-CONFIRM: being built by platform-1e | |
| -| Router linux-arm64 sha256 (v0.28.2) | from the signed `SHA256SUMS` of the v0.28.2 release | TO-CONFIRM | |
| -| Console linux-arm64 sha256 (v0.28.2) | from the same `SHA256SUMS` | TO-CONFIRM | |
| +| Router linux-arm64 sha256 (v0.28.2) | from the signed `SHA256SUMS.txt` of the v0.28.2 release | TO-CONFIRM | |
| +| Console linux-arm64 sha256 (v0.28.2) | from the console app's signed release manifest in the deployment bucket (platform-1e ruling). Never typed by hand, and never taken from `SHA256SUMS.txt`, which does not cover the console | TO-CONFIRM | |
| | Router linux-arm64 sha256, v0.28.0 (current, for comparison) | `3ca7c74d5356a3995ecf677d142bc32fafaf790a2cc1bc0b628f3eec1b7ea731`, from the signed dev `control/system/router/stable.json` | confirmed | |
| -| Console executable on sophie | today `/opt/carlos/versions/26065378/console` (root-owned; `/opt/carlos/live/platform.dev.carlosframework.com` is a symlink to it in a carlos-owned directory), with no `.prev` beside it | BLOCKED on gap 2: no hand-made files; the protected path and its `.prev` come from v0.28.2's console install and must match the signed identity | |
| -| `policy.json` | an armed `hostfloor.Policy` with the floor bytes and a root-signed `moves-protocol` authorization | BLOCKED on gap 1 (v0.28.2) | |
| -| `identity.json` | the signed system pointer for v0.28.2, `control/system/router/releases/v0.28.2.json` | BLOCKED on gap 2 (v0.28.2) | |
| +| Console executable on sophie | today `/opt/carlos/versions/26065378/console` (root-owned; `/opt/carlos/live/platform.dev.carlosframework.com` is a symlink to it in a carlos-owned directory), with no `.prev` beside it | BLOCKED on gap 2: no hand-made files; the protected path and its `.prev` come from v0.28.2's console install and must match the signed identity. `.prev` may equal current (platform-1e ruling) | |
| +| `policy.json` | an armed `hostfloor.Policy` with the floor bytes and a root-signed `moves-protocol` authorization, written byte-exact by v0.28.2's new phase with `--out` and read directly; no `jq` or other parser ever touches it | BLOCKED on gap 1 (v0.28.2) | |
| +| `identity.json` | the signed system pointer for v0.28.2, `control/system/router/releases/v0.28.2.json`, fetched byte-exact and read directly; no `jq` or other parser ever touches it | BLOCKED on gap 2 (v0.28.2) | |
| ## Gaps found while drafting |
| @@ -65,13 +65,16 @@ platform-1e confirmed gaps 1 and 2 on main on 2026-10-18 and is building the fix |
| TO-CONFIRM: |
| 1. Operator identity for both boxes (Paul; suggested default `paul@keymail.dev`). |
| 2. Console enrollment token, 32 lowercase hex characters (generated at approval). |
| -3. v0.28.1 published, for step 5. |
| -4. v0.28.2 published, and its router and console sha256 from the release `SHA256SUMS`; this also fixes the floor's `min_release`. |
| -5. Signing host values in `signing-host.md`: the jq and carlos sha256 values, the security group ID once created, and the bucket keys the signer needs (confirmed by dry runs). |
| +3. v0.28.2 published: the router sha256 from its signed `SHA256SUMS.txt`, the console sha256 from the console app's signed release manifest, and the carlos v0.28.2 CLI sha256 for the signer. This also fixes the floor's `min_release`. |
| +4. The bucket keys the signer needs, confirmed by a `--dry-run` of every phase from the signer. |
| + |
| +TO-CREATE (each with Paul's go): the `carlos-claim-signer` security group (its ID), role, instance profile and instance (`signing-host.md`). |
| + |
| +Known now: v0.28.1 is published and on dev; the carlos v0.28.1 and jq 1.7.1 sha256 values, the AMI, the VPC and the subnet are in `signing-host.md`. |
| BLOCKED (fixes ship in v0.28.2, built by platform-1e): |
| -6. `policy.json`: the signed armed policy (gap 1). |
| -7. `identity.json`: the signed v0.28.2 system identity (gap 2). |
| -8. Sophie's protected console path and its `.prev` (gap 2). |
| +5. `policy.json`: the signed armed policy (gap 1). |
| +6. `identity.json`: the signed v0.28.2 system identity (gap 2). |
| +7. Sophie's protected console path and its `.prev` (gap 2; `.prev` may equal current). |
| Confirmed on 2026-10-18: namespace `platform`, sophie's pool `console`, console ID `dev-console`. |
diff --git a/docs/superpowers/notes/claim-trial-inputs/signing-host.md b/docs/superpowers/notes/claim-trial-inputs/signing-host.md| index c725c366b..53c831c84 100644 |
| --- a/docs/superpowers/notes/claim-trial-inputs/signing-host.md |
| +++ b/docs/superpowers/notes/claim-trial-inputs/signing-host.md |
| @@ -33,9 +33,9 @@ The signer reuses the AMI, type, subnet and launch options. It gets its **own** |
| | Setting | Value | |
| |---|---| |
| | Type | `t4g.small` (arm64) | |
| -| AMI | `ami-071babd89cea53fa3` | |
| -| Subnet | `subnet-0975dda9ac0e65347` (public IP for egress only) | |
| -| Security group | new `carlos-claim-signer`: no inbound; egress TCP 443 only (SSM, S3). Amazon's VPC DNS is not filtered by security groups | |
| +| AMI | `ami-071babd89cea53fa3` (`debian-13-arm64-20260722-2547`, owner `136693071363`, Debian). Checked 2026-10-18: `available`, deprecation date 2028-07-22. Sophie runs it, and so does the root runner. A newer Debian image, `ami-009be0c9232ca1aba` (`debian-13-arm64-20261017-2634`), exists; staying on the pinned one keeps the signer on the image the runner already proved | |
| +| VPC and subnet | `vpc-02212d67a9fca3b20`; `subnet-0975dda9ac0e65347` (`eu-west-1c`, `available`, public IP on launch, used for egress only; sophie's subnet). Checked 2026-10-18 | |
| +| Security group | TO-CREATE: new `carlos-claim-signer`, no inbound, egress TCP 443 only (SSM, S3). Amazon's VPC DNS is not filtered by security groups | |
| | Access | SSM Session Manager only. No SSH key, no inbound port | |
| | Metadata | IMDSv2 required, hop limit 1 | |
| | Storage | default root volume, deleted on termination. No swap (Debian cloud default), so a key in `/run` stays in memory | |
| @@ -93,6 +93,11 @@ The key goes from the SSM response straight into a `0600` file on tmpfs (`/run`) |
| ## Getting jq and the carlos CLI there |
| +Known values (2026-10-18): |
| +- carlos v0.28.1 `carlos-linux-arm64`: `2ae174da29b1d10fdcb009172ba830db5460b62e838bcecc7d9e17535f35adea`. It comes from the published release's `SHA256SUMS.txt`, whose signature verified with the README's pinned key (`openssl pkeyutl -verify`: "Signature Verified Successfully"). It is the same binary leo and sophie run. |
| +- jq 1.7.1 `jq-linux-arm64`: `4dd2d8a0661df0b22f1bb9a1f9830f06b6f3b8f7d91211a1ef5d7c4f06a8b4a5` (1709616 bytes). It was computed on DOCS-T1 from the file downloaded from `github.com/jqlang/jq/releases/download/jq-1.7.1/`, and matches that release's `sha256sum.txt`. |
| +- carlos v0.28.2: TO-CONFIRM when published (step 6's policy signing and step 7 need it). |
| + |
| On DOCS-T1, before launching: |
| 1. Download the carlos CLI `carlos-linux-arm64` (v0.28.1 for step 5; v0.28.2 for step 6's policy signing and step 7), with its `SHA256SUMS` and `SHA256SUMS.sig`, from the public release. Verify the signature as the README's "Releasing the platform" verification does, then `sha256sum -c`. Record the sha256. |
| 2. Download jq 1.7.1 `jq-linux-arm64` and the release's `sha256sum.txt` from `github.com/jqlang/jq/releases/tag/jq-1.7.1`, then check it with `sha256sum -c`. Record the sha256. |
| @@ -103,12 +108,13 @@ On the signer, as root: |
| ```bash |
| aws s3 cp s3://carlos-dev-640012953448/claim-signer/<run-id>/carlos-linux-arm64 /usr/local/bin/carlos |
| aws s3 cp s3://carlos-dev-640012953448/claim-signer/<run-id>/jq-linux-arm64 /usr/local/bin/jq |
| -printf '%s %s\n' '<carlos CLI sha256>' /usr/local/bin/carlos '<jq 1.7.1 sha256>' /usr/local/bin/jq | sha256sum -c |
| +printf '%s %s\n' 2ae174da29b1d10fdcb009172ba830db5460b62e838bcecc7d9e17535f35adea /usr/local/bin/carlos \ |
| + 4dd2d8a0661df0b22f1bb9a1f9830f06b6f3b8f7d91211a1ef5d7c4f06a8b4a5 /usr/local/bin/jq | sha256sum -c |
| chmod 0755 /usr/local/bin/carlos /usr/local/bin/jq |
| /usr/local/bin/carlos version |
| ``` |
| -Expected: both `OK`, then the expected version (`carlos v0.28.1` for step 5, `carlos v0.28.2` from step 6). Both sha256 values are TO-CONFIRM: neither release is published yet, and the jq value is recorded at download. |
| +Expected: both `OK`, then `carlos v0.28.1`. For step 6 onwards, use the v0.28.2 binary and its sha256 instead (TO-CONFIRM when published). |
| ## Create (each part needs Paul's go) |
diff --git a/docs/superpowers/plans/2026-10-16-claim-activation-dev-cohort1.md b/docs/superpowers/plans/2026-10-16-claim-activation-dev-cohort1.md| index 852ff814c..f79788fcd 100644 |
| --- a/docs/superpowers/plans/2026-10-16-claim-activation-dev-cohort1.md |
| +++ b/docs/superpowers/plans/2026-10-16-claim-activation-dev-cohort1.md |
| @@ -343,7 +343,7 @@ The controller supplies, and Paul approves, the concrete inputs: the signed rele |
| ## Step 5. Roster, enrollment and console enrollment |
| -Unblocked once v0.28.1 is on dev. It needs Paul's approval of the step 5 package (the inputs in `docs/superpowers/notes/claim-trial-inputs/`, the signing host, and the box-record publishes), but not the gap 1 and 2 fixes. |
| +Unblocked: v0.28.1 (`3b69c2bd`) is on dev since 2026-10-18 (leo, sophie and dennis current and armed with 0 REFUSING; the dev console on `3b69c2bd`). It needs Paul's approval of the step 5 package (the inputs in `docs/superpowers/notes/claim-trial-inputs/`, the signing host, and the box-record publishes), but not the gap 1 and 2 fixes. |
| Paul's go: once for step 5. |
| @@ -351,19 +351,54 @@ Paul's go: once for step 5. |
| Each box's signed AWS identity record must be in place at `control/boxes/<box>.json` before the box is invited. They come from `carlos system box publish-record` (v0.28.1, dev only), run once on each box. A missing or refused record is a stop, not permission to make one up. |
| -**Leo.** Paul's go: separate. In a root shell on leo (the verb refuses to run as root, so `systemd-run` drops to the agent user with the box's host.env loaded; this is the only supported way to run it): |
| +Both boxes run v0.28.1 (`carlos v0.28.1`, binary sha256 `2ae174da29b1d10fdcb009172ba830db5460b62e838bcecc7d9e17535f35adea`, equal to the release's signed `SHA256SUMS.txt`), and `/opt/carlos/carlos system box publish-record --help` prints its usage and exits 0 on both (checked read-only, 2026-10-18). `control/boxes/` is still empty. |
| + |
| +The verb refuses to run as root, so `systemd-run` drops to the agent user with the box's host.env loaded; this is the only supported way to run it. Each publish is sent from DOCS-T1 (profile `kass`) as one SSM command. The command parameter carries no secret. |
| + |
| +**Leo.** Paul's go: separate. |
| ```bash |
| -systemd-run --wait --pipe -p EnvironmentFile=/etc/carlos/host.env -p User=carlos /opt/carlos/carlos system box publish-record |
| +aws --profile kass --region eu-west-1 ssm send-command --instance-ids i-046c7fe43620944bc \ |
| + --document-name AWS-RunShellScript --comment "cohort1 step 5.0: publish-record leo-climbing" \ |
| + --parameters '{"commands":["systemd-run --wait --pipe -p EnvironmentFile=/etc/carlos/host.env -p User=carlos /opt/carlos/carlos system box publish-record"]}' \ |
| + --query Command.CommandId --output text |
| +aws --profile kass --region eu-west-1 ssm get-command-invocation --command-id <command-id> \ |
| + --instance-id i-046c7fe43620944bc --query '[Status,StandardOutputContent,StandardErrorContent]' --output text |
| ``` |
| -Expected: `published the identity record for leo-climbing (instance i-046c7fe43620944bc) to control/boxes/leo-climbing.json`. |
| +Expected: `Success`, and on standard output, verbatim from main at `3b69c2bd`: |
| + |
| +``` |
| +published the identity record for leo-climbing (instance i-046c7fe43620944bc) to control/boxes/leo-climbing.json |
| +``` |
| -**Sophie.** Paul's go: separate. The same command in a root shell on sophie. Expected: `published the identity record for sophie-knitting (instance i-05498eada6f0afd23) to control/boxes/sophie-knitting.json`. |
| +Standard error carries only `systemd-run`'s own unit lines. Any refusal on standard error (and status `Failed`) is a stop. |
| -**Check that each record verifies (`boxid.Verifier`).** Run the same command again on each box. On an existing record it verifies it the way enrollment does (`boxid.Verifier.Enroll`: AWS's signature under the certificate for the document's region, the account, the AWS region, the instance and the box name) and writes nothing. Expected on each box: `the record at control/boxes/<box>.json is valid AWS-signed evidence for <box> (instance <id>), so nothing was written. enrollment still makes its own checks before it accepts the box`. Any other answer is a stop. The `invite-box` dry run below then checks the same evidence again, from the signer. |
| +**Sophie.** Paul's go: separate. |
| -These output lines are drafts on the `box-publish-record` branch and may change in copy review; match the final v0.28.1 wording. |
| +```bash |
| +aws --profile kass --region eu-west-1 ssm send-command --instance-ids i-05498eada6f0afd23 \ |
| + --document-name AWS-RunShellScript --comment "cohort1 step 5.0: publish-record sophie-knitting" \ |
| + --parameters '{"commands":["systemd-run --wait --pipe -p EnvironmentFile=/etc/carlos/host.env -p User=carlos /opt/carlos/carlos system box publish-record"]}' \ |
| + --query Command.CommandId --output text |
| +aws --profile kass --region eu-west-1 ssm get-command-invocation --command-id <command-id> \ |
| + --instance-id i-05498eada6f0afd23 --query '[Status,StandardOutputContent,StandardErrorContent]' --output text |
| +``` |
| + |
| +Expected: `Success`, and: |
| + |
| +``` |
| +published the identity record for sophie-knitting (instance i-05498eada6f0afd23) to control/boxes/sophie-knitting.json |
| +``` |
| + |
| +**Check that each record verifies (`boxid.Verifier`).** Send the same command again to each box. On an existing record it verifies it the way enrollment does (`boxid.Verifier.Enroll`: AWS's signature under the certificate for the document's region, the account, the AWS region, the instance and the box name) and writes nothing. Expected, verbatim from main at `3b69c2bd`: |
| + |
| +``` |
| +the record at control/boxes/leo-climbing.json is valid AWS-signed evidence for leo-climbing (instance i-046c7fe43620944bc), so nothing was written. enrollment still makes its own checks before it accepts the box |
| +the record at control/boxes/sophie-knitting.json is valid AWS-signed evidence for sophie-knitting (instance i-05498eada6f0afd23), so nothing was written. enrollment still makes its own checks before it accepts the box |
| +``` |
| + |
| +Any other answer is a stop. The `invite-box` dry run in 5.1 then checks the same evidence again, from the signer. |
| ### 5.1 Roster and enrollment |
| @@ -465,22 +500,31 @@ done |
| Expected: every dry run, then its apply, succeeds; `inspect.json` lists `leo-climbing` (pool `cohort1`, instance `i-046c7fe43620944bc`), `sophie-knitting` and the console. |
| -Then stage the box inputs, still on the trusted host. `policy.json` and `identity.json` are the approved armed policy and signed identity; `console-path` and `console-id` are the protected console executable path and the approved console ID (the same ID as in `console-bound.json`): |
| +Then stage the step 5 box inputs from DOCS-T1. `console-id` is the approved console ID, `dev-console` (the same ID as in `console-bound.json`): |
| ```bash |
| ssm_run "$LEO" "install -d -o root -g root -m 0700 /root/claim-trial && echo ok" |
| ssm_run "$SOPHIE" "install -d -o root -g root -m 0700 /root/claim-trial && echo ok" |
| -for f in release.pub policy.json identity.json leo-climbing-enrollment.json; do box_put "$LEO" "$f" "/root/claim-trial/$f"; done |
| -for f in release.pub policy.json identity.json sophie-knitting-enrollment.json console-path console-id; do box_put "$SOPHIE" "$f" "/root/claim-trial/$f"; done |
| +for f in release.pub leo-climbing-enrollment.json; do box_put "$LEO" "$f" "/root/claim-trial/$f"; done |
| +for f in release.pub sophie-knitting-enrollment.json console-id; do box_put "$SOPHIE" "$f" "/root/claim-trial/$f"; done |
| ``` |
| -Expected: `staged` for each file. No private signing key is transferred. |
| +Expected: `staged` for each file. No private signing key is transferred. `policy.json`, `identity.json` and `console-path` are staged in step 6, once v0.28.2 exists. |
| On failure: hold. A partly applied phase is resumed from the latest authenticated revision, never recreated. |
| ## Step 6. Arm leo's guard and start the guarded console |
| -Waits for v0.28.2 on dev: `policy.json` is signed on the trusted host by v0.28.2's new `claims run` phase (blocker 5a), `identity.json` is the v0.28.2 system identity the release workflow publishes (5b), and sophie's `--console` path and its `.prev` come from v0.28.2's console install (5b). Never hand-make any of them. |
| +Waits for v0.28.2 on dev: `policy.json` is signed on the trusted host by v0.28.2's new `claims run` phase (blocker 5a), `identity.json` is the v0.28.2 system identity the release workflow publishes (5b), and sophie's `--console` path and its `.prev` come from v0.28.2's console install (5b; `.prev` may equal current). Never hand-make any of them. |
| + |
| +`policy.json` and `identity.json` are byte-exact files, read directly. Nothing parses or rewrites them: no `jq`, no reformatting, no copy and paste. `policy.json` is written by the new phase with `--out policy.json` on the signer. `identity.json` is the object at `control/system/router/releases/v0.28.2.json`, fetched unchanged with `aws s3 cp`. Record each file's sha256 where it is made; `box_put` checks the same sha256 on arrival. Stage them, with sophie's protected `console-path`, from DOCS-T1: |
| + |
| +```bash |
| +for f in policy.json identity.json; do box_put "$LEO" "$f" "/root/claim-trial/$f"; done |
| +for f in policy.json identity.json console-path; do box_put "$SOPHIE" "$f" "/root/claim-trial/$f"; done |
| +``` |
| + |
| +The exact command for the new phase comes with v0.28.2. |
| Paul's go: once for step 6. It restarts `console.service` on sophie, which briefly interrupts the dev console. |