From 5e93ef70bd735726fd79a2cc1af15086806eb470 Mon Sep 17 00:00:00 2001 From: fred Date: Tue, 18 Aug 2026 19:10:09 -0500 Subject: [PATCH] guides: fix the cross-reference direction in SEAT-IDENTITY 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. --- packages/mosaic/framework/guides/SEAT-IDENTITY.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/mosaic/framework/guides/SEAT-IDENTITY.md b/packages/mosaic/framework/guides/SEAT-IDENTITY.md index 5bb1db1c..8b79daab 100644 --- a/packages/mosaic/framework/guides/SEAT-IDENTITY.md +++ b/packages/mosaic/framework/guides/SEAT-IDENTITY.md @@ -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. 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 -provisioning. +directly; a store entry pointing at a slot is the bridge described in **Where a seat's token lives** above, +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 is safe to launch in — the seat is told at launch so it does not discover it mid-task.