Left open by #13, which narrowed it rather than closing it. Issue #9 supplied no answer.
specifications/blueprint/v1/spec.md §4:
TODO — size MUST name a Compute Profile in family.tier.size form. State whether an unknown profile is a semantic or a capability failure. The profile vocabulary itself is not defined in this repository and a reader outside the platform cannot resolve a slug like general.standard.small; naming where it is published is part of closing this.
Why it matters
size is REQUIRED on every node — it appears in all three blueprint examples and in nearly every conformance fixture — and this repository defines neither its grammar nor its vocabulary. A reader outside musher-dev/platform cannot tell what general.standard.small means, whether general.standard.tiny exists, or what happens if they invent one.
This is the largest remaining piece of the seeding debt CLAUDE.md describes: "some description text uses platform vocabulary (snapshot compute, Compute Profile slugs) that a reader outside musher-dev/platform cannot resolve."
The concrete questions
- Grammar. Is
family.tier.size a pattern the schema carries, like the image-ref grammar in component §5.1?
- Vocabulary. Where is the profile list published, and is it versioned with these families or independently of them? If it is account-scoped or region-scoped it cannot live here at all.
- Phase. An unknown profile is
capability if the vocabulary is account-scoped and semantic if it is a fixed published list. Component §5.1 already draws exactly this line for image pinning — grammar in the schema, curated list outside it, so the list can grow in a minor release. The same split probably applies.
What deciding it costs
The grammar is narrowing and free only before the first tag (#1/#2/#3 open). The vocabulary question may need an ADR: publishing a controlled vocabulary from this repository is arguably a fourth artifact kind, and GOVERNANCE.md is specific about what this repository publishes.
Refs #9
Left open by #13, which narrowed it rather than closing it. Issue #9 supplied no answer.
specifications/blueprint/v1/spec.md§4:Why it matters
sizeis REQUIRED on every node — it appears in all three blueprint examples and in nearly every conformance fixture — and this repository defines neither its grammar nor its vocabulary. A reader outsidemusher-dev/platformcannot tell whatgeneral.standard.smallmeans, whethergeneral.standard.tinyexists, or what happens if they invent one.This is the largest remaining piece of the seeding debt CLAUDE.md describes: "some
descriptiontext uses platform vocabulary (snapshot compute, Compute Profile slugs) that a reader outsidemusher-dev/platformcannot resolve."The concrete questions
family.tier.sizeapatternthe schema carries, like the image-ref grammar in component §5.1?capabilityif the vocabulary is account-scoped andsemanticif it is a fixed published list. Component §5.1 already draws exactly this line for image pinning — grammar in the schema, curated list outside it, so the list can grow in a minor release. The same split probably applies.What deciding it costs
The grammar is narrowing and free only before the first tag (#1/#2/#3 open). The vocabulary question may need an ADR: publishing a controlled vocabulary from this repository is arguably a fourth artifact kind, and GOVERNANCE.md is specific about what this repository publishes.
Refs #9