# 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
lane: green
status: closed
outcome: absorbed
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.
notes: Custodian decision 3c487545-ee40-4049-89fa-34b41747a7eb grandfathered
  the exact MASON-0001 workplan and MASON-0001-TNN task schemes. Registered UUIDs
  remain unchanged, and the duplicate MASON-0001-T01 source blocks are indexed as
  one logical task while retaining both source locations as diagnostic provenance.
  Absorbed by that decision and the CUST-WP-0063 canon/validator update.
created: '2026-08-22T09:33:08.629717Z'
updated: '2026-08-22T21:19:02Z'
state_hub_intake_id: "01a028d1-c4af-7a06-adb5-c90399721872"
```