From fc774e5e9aaeadc07d7a3a385d3f4c9c524c8c18 Mon Sep 17 00:00:00 2001
From: tegwick <bernd.worsch@gmail.com>
Date: Sat, 22 Aug 2026 23:54:29 +0200
Subject: [PATCH] docs: route legacy identifier grandfathering

Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0233b-178d-7162-b92f-31a31ea8ca9b
---
 docs/intakes/residuals.md | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/docs/intakes/residuals.md b/docs/intakes/residuals.md
index 48f63d5..238c7f7 100644
--- a/docs/intakes/residuals.md
+++ b/docs/intakes/residuals.md
@@ -73,3 +73,30 @@ description: |
   explicit, and teardown removes the sandbox workspace.
 state_hub_intake_id: "01a02b76-f020-7d60-a3ce-12a34c13ebce"
 ```
+
+## GLAS-IN-0003 — Grandfather the legacy bootstrap identifier scheme
+
+```yaml
+id: GLAS-IN-0003
+kind: intake
+title: "Grandfather the legacy GLAS-0001 bootstrap identifiers"
+lane: green
+status: todo
+priority: medium
+owner: repo-manager
+repo: glas-harness
+origin: residual
+origin_ref: GLAS-0001
+description: |
+  The finished bootstrap workplan predates the fleet kind registry and uses
+  GLAS-0001 plus GLAS-0001-T01 through T03. Those records already have stable
+  State Hub UUIDs and must not be renamed. Repo Manager's primary registrar
+  reports them as C-35 contradictory identities, while State Hub also reports
+  the three task ids as C-31 unregistered species.
+
+  Coordinate with the canon steward to grandfather this exact historical
+  scheme, matching the treatment for other pre-canon bootstrap identifiers.
+  Keep the existing file ids and UUID bindings unchanged. Done when Repo
+  Manager identity preflight and statehub fix-consistency accept the four
+  legacy identifiers without C-35 or C-31 warnings.
+```