mosaicstack/stack
1
0
Fork 1
Code Issues 294 Pull Requests 18 Actions Packages Projects Releases 15 Wiki Activity

guides: fix the cross-reference direction in SEAT-IDENTITY
ci/woodpecker/pr/ci Pipeline was successful
Details

Browse Source 
rev-code-01's non-blocking nit on #1313 round 2. The no-linking-step paragraph
pointed at the bridge explanation as 'described below'; it is above. Now names the
section, which survives further reordering better than a direction word does.

Text-only. Verified with the repo's PINNED prettier (3.8.1 via pnpm-lock.yaml) and
the sanitization gate, both clean.
This commit is contained in:
fred
2026-08-18 19:10:09 -05:00
parent 3884f2de4d
commit 5e93ef70bd
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/mosaic/framework/guides/SEAT-IDENTITY.md
+2 -2
View File
@@ -104,8 +104,8 @@ is not how a system finds a credential; the helper resolving the right store is.
minting account**. Record the date in `ENTITY.md`. Never record the value. minting account**. Record the date in `ENTITY.md`. Never record the value.
There is no step that links the framework store to the slot. A seat-aware helper reads the slot There is no step that links the framework store to the slot. A seat-aware helper reads the slot
directly; a store entry pointing at a slot is the bridge described below, and it is not part of directly; a store entry pointing at a slot is the bridge described in **Where a seat's token lives** above,
provisioning. and it is not part of provisioning.
Until step 3, the seat is unminted and its git writes fail closed. That is the designed state and Until step 3, the seat is unminted and its git writes fail closed. That is the designed state and
is safe to launch in — the seat is told at launch so it does not discover it mid-task. is safe to launch in — the seat is told at launch so it does not discover it mid-task.