vh/esh-pfi-infrastructure
1
0
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

docs(albok): old nemi token revoked after the personal/inbox swap

Browse Source
This commit is contained in:
vh
2026-10-13 17:43:15 -07:00
parent 7ca2f76d21
commit 4eacb746fa
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
stacks/albok-service/README.md
+2 -2
View File
@@ -131,8 +131,8 @@ like `personal/notes`, so `default_group: albok-personal` (1511) and not service
classes plus Nemi's `restricted_wings`. vh reads it through 1511, and no API token besides Nemi's holds it. The live
config backup is `albok.yaml.pre-inbox`; added by `playbooks/albok-personal-inbox.yaml`, with health reading 7 wings
ready. Nemi's token was re-minted for it: `01M4VX207PJ09ZSECASCSZPCFE`, its previous ten grants plus read+write on
`personal/inbox`, vaulted over `albok/token-nemi`. The previous nemi token `01M4HAP9G90J79HBRJB6VW6PQA` stays live
until albok-dev has swapped and asks for its revocation. The capture ROOT is on nh3-dev: `/srv/nemi/inbox`
`personal/inbox`, vaulted over `albok/token-nemi`. The previous nemi token `01M4HAP9G90J79HBRJB6VW6PQA` was
revoked at 1742 after albok-dev's swap; the capture source walks (generation 0, empty root). The capture ROOT is on nh3-dev: `/srv/nemi/inbox`
(`playbooks/nh3-dev-nemi-inbox.yaml`).
**Nemi (albok's tagger, runs on nh3-dev):** `albok/token-nemi`, a service token minted 0255 with read+write on