ops(svos): U20 settings grants issued on Prime's word and approved by him (ns:interface-settings read + autonomous write)

2026-10-18 23:56:40 -07:00
parent f281bfb830
commit 44221e65b0
2 changed files with 6 additions and 3 deletions
@@ -39,8 +39,11 @@ configuration, enrollment and acceptance.
 - **Card:** `card:892d7886…` (manifest, app-interface revision 5, `6759c436e0be`) was raised 2351:50, spoken in ~6 s, and approved by Prime
  through Matrix at 2352:16. The interface was down (`refused stale`) from 2351:53 to 2352:23. All 8 apps were up again, and the new
  `state/apps/interface/settings.sqlite3` existed.
- **After:** Prime's two runtime grants on `ns:interface-settings` (read, not autonomous; write, autonomous) from the page console, then
-  the /settings and panel checks plus his listening test (svos-dev's list).
+- **Grants (Prime's "issue the grant", 2355):** infra-ops sent both `POST /verbs/kernel/grant` requests as Prime over loopback,
+  with the front door's identity headers (`Tailscale-User-Login: Vuong`, Host, `X-Forwarded-Proto`, Origin, `Sec-Fetch-Site`) and an
+  `Idempotency-Key`, because the verb is human-only and needs a key. Two cards were raised at 2355:52, and Prime approved both at
+  2356:09 and 2356:12. They are runtime grants: id 207 `prime → ns:interface-settings write, autonomous`; id 208 `… read, not
+  autonomous`. Remaining: the /settings and panel checks plus his listening test (svos-dev's list).
 - **Rollback:** `current → releases/15c2d04`, run `svos-front-inventory`, restart svos-interface. That reverts the manifest to 0.0.6, which
  raises another held card. `settings.sqlite3` is additive and can stay.