Descriptile enum gaps: CLADE lineage.type lacks hub/satellite; STATE status lacks planned/reserved

[hyperpolymath]

Found 2026-09-02 while minting the Stealth Glider line (metadatastician/stealth-glider-ecosystem hub + seven satellites, all instantiated from rsr-template-repo at 2283f12). Two descriptile enums cannot express a coordination hub, its satellites, or a reserved-but-not-started repo, so eight live repos now carry the nearest wrong value. Filing here because standards is the canon source; the enum comments themselves ship in rsr-template-repo's machine-readable/descriptiles/ and the a2ml-templates/ here.

1. CLADE.a2ml [lineage] type has no hub / satellite value

Template comment (rsr-template-repo machine-readable/descriptiles/CLADE.a2ml, and every mint):

[lineage]
type = "standalone"           # standalone | monorepo | monorepo-child | inflated | deflated

A coordination hub (a2ml-ecosystem, k9-ecosystem, stealth-glider-ecosystem) and the members it coordinates are neither standalone nor a monorepo relationship. All eight Stealth Glider repos were minted type = "standalone" as the least-wrong choice; the hub relationship is only recoverable from ECOSYSTEM.a2ml [pipeline] coordination and ANCHOR.a2ml [semantic-authority] policy = "satellite". Nothing in CLADE, the identity file that gv-clade-index registers, records it.

Proposal: add hub and satellite to the enum (a satellite's parent stays "" because parent is a monorepo parent), or document that hub membership is deliberately ECOSYSTEM-only and CLADE must not encode it. Either is fine; today the choice is undocumented.

2. STATE.a2ml top-level status has no "planned" / "reserved" value

Template comment (rsr-template-repo machine-readable/descriptiles/STATE.a2ml:14):

status = "active"  # active | paused | archived

Four of the new repos are reserved placeholders: CLADE [status] phase = "reserved" exists and was used, but STATE has no matching value, so they carry status = "paused", which reads as "was active, stopped". a2ml-templates/STATE.a2ml.template:77 already uses planned for milestones, so the vocabulary exists one level down.

Proposal: add planned (or reserved, matching the CLADE phase) to the top-level status enum, and state which of CLADE phase / STATE status is authoritative when they disagree.

Witnesses

metadatastician/{stealth-glider-ecosystem,x15-rocket-glider,planer-1,enterglide-ncc-137-k,tardis-rule-disruption} — CLADE type = "standalone", STATE status = "paused", CLADE phase = "reserved" (satellites) / "incubating" (hub).

Related: hyperpolymath/rsr-template-repo#56 (template defects found in the same mint).