coulomb/glas-harness
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: route legacy identifier grandfathering
Some checks failed
ci / validate (push) Has been cancelled
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0233b-178d-7162-b92f-31a31ea8ca9b
This commit is contained in:
tegwick 2026-08-22 23:54:29 +02:00
parent 862292486d
commit fc774e5e9a
1 changed files with 27 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/intakes/residuals.md
View file

@ -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.
```