docs(albok): nemi token re-minted with personal/notes for the vault source
This commit is contained in:
@@ -132,7 +132,10 @@ classes plus Nemi's `restricted_wings`. vh reads it through 1511, and no API tok
|
||||
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` 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`
|
||||
revoked at 1742 after albok-dev's swap; the capture source walks (generation 0, empty root).
|
||||
**2026-10-15:** re-minted again for the vault source (Prime's notes, `/srv/nemi/vault` on nh3-dev → `personal/notes`):
|
||||
`01M4ZBJG3DMRF9Q9XEVZ8Q20GH` = the twelve grants above plus read+write on `personal/notes`, vaulted over `albok/token-nemi`.
|
||||
`01M4VX207PJ09ZSECASCSZPCFE` is revoked once albok-dev has swapped. 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
|
||||
|
||||
Reference in New Issue
Block a user