mu-model: validate the `create` path

[huiyu]

mu-model ships with its create path unvalidated. This issue collects field reports until it can drop the 🧪.

Status

Path	Basis	Status
update	aflaj restructure — 23 concepts re-tagged, spine derived, 7-section rebuild	✅ from a real run
sync	aflaj — two state machines + their guarantees moved up from prd/objects.md, downstream left with references	✅ from a real run
create	Reasoned from Event Modeling (Dymitruk) and Four-Color archetypes (Coad)	❌ never run on a project starting from zero

Both proven runs started from an existing set of concepts and only reorganized them. create has to produce concepts from a case and a conversation — a different act, with no practical basis behind the current steps.

Exit criterion

create drops its 🧪 after running on two independent projects with no process fix. One clean run is luck.

What I most want to know

1. Step 2 — does change-first questioning actually surface concepts from nothing?
The step says to ask "what changes, and when?" rather than "what concepts are there?", on the theory that concept-first yields a lifeless noun list. Did nouns genuinely fall out of the lifecycles, or did you end up enumerating concepts anyway and back-filling the time axis?

2. Step 3 — does the degradation path fire?
On a stateless or pure-transformation project, does the skill say "no spine survived verification, organize by data flow" — or does it invent a centre because the template has a slot for one?

3. Step 6 — where do the principles come from with no MRD?
The skill extracts them from docs/mrd/ or docs/brief/ when present, otherwise fills §1 at step 6. Did that ordering hold, or did you have to state the principles up front to make step 2 tractable at all?

Report template

Repo type:         product / library / CLI / infra / …
Starting state:    no docs / has PRD / has code but no docs / …
Stance taken:      create | update | sync
Step that broke:
What I did instead:
Concepts landed:   N   (any isolates? — zero in-degree ∧ zero out-degree ∧ absent from spine/overview/example)
Spine:             <concept>, or "none — organized by data flow"
Time spent:

Where the pieces live

• knowledge/principles/domain-model.md — qualification test, dependency direction, maintenance moves
• knowledge/templates/context-md.md — the 7-section skeleton
• skills/mu-model/SKILL.md — the process itself

Worked originals: this repo's own CONTEXT.md (spine = Artifact), and aflaj's (spine = 定义版本, private).