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

intake: hand off legacy MASON identifier scheme

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02878-7c21-7692-bcd6-ce2838c4b448
This commit is contained in:
tegwick 2026-08-22 11:33:34 +02:00
parent cc9946c873
commit 8b4405caf3
2 changed files with 23 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
.gitignore vendored
View file

@ -3,6 +3,7 @@ __pycache__/
*.pyc
*.egg-info/
.pytest_cache/
.repo-manager/
# state-hub: track .claude/rules
# Claude Code local state (track shared rules; ignore machine-specific files)

22
intakes/intakes.md Normal file
View file

@ -0,0 +1,22 @@
# Intake records
## MASON-IN-0001 — Grandfather the legacy MASON-0001 identifier scheme
```yaml
id: MASON-IN-0001
kind: intake
title: Grandfather the legacy MASON-0001 identifier scheme
status: open
origin: residual
origin_ref: MASON-WP-0002
priority: low
owner: ops-mason
description: The finished bootstrap workplan uses legacy MASON-0001 and noncanonical
MASON-0001-Txx identifiers, including a duplicate T01. Fleet canon says existing
identifiers are never renamed and legacy schemes must be grandfathered. Coordinate
with the Custodian canon steward and Repo Manager to add the exact legacy scheme
mapping, then verify statehub consistency without rewriting registered UUIDs or
historical source identity.
created: '2026-08-22T09:33:08.629717Z'
updated: '2026-08-22T09:33:08.629717Z'
```