Preview and archive labels both say Registration open. The preview owner now wants an invitation; the archive must preserve its wording.
Elsewhere, badges and manifests share one organization-owned identifier rule. When that rule changes, both outputs must follow it.
| Change | Keep together? | Why? |
|---|---|---|
| Preview wording | No | Preview and archive have separate owners and purposes. |
| Official identifier rule | Yes | Both consumers must follow the same policy. |
Share the rule that is jointly owned. Keep unrelated presentation choices separate. Identical lines alone do not decide ownership.
Engineering Depth
Separate functions can keep preview and archive independent. A shared policy contract can serve both identifier consumers.
Before adding a mode flag to a helper, ask which product requirement needs that shared behavior. A current boundary may justify an abstraction with one implementation; hypothetical reuse does not. CS-05.
Your Reflection
The badge layout changes. Must the identifier policy or manifest change too?
Notes are browser-local. Export a copy to keep them; they are not submitted or judged.
Worked Discussion
Only if the requirement changes them. Sharing the identifier rule does not make the consumers' layouts jointly owned.