Compare the rule with concrete cases
Fictional parent setting begins as standard. Record C copies it on creation; record I inherits it live. The parent later changes to compact. C stays standard and I becomes compact. Both policies are plausible, so “use the default” does not choose one.
| Record | Binding policy | At creation | After parent becomes compact |
|---|---|---|---|
| C | Copy once | Standard | Standard |
| I | Live inheritance | Standard | Compact |
| New copied C2 | Created after change | Compact | Compact |
Work through the distinction
The copied value is stored on the record; the inherited value is resolved from its parent. Keep the binding mode beside the value so a later parent edit has a defined effect.
Must C change when the parent changes again?
Show the worked answer
No under its copy-on-creation policy. A separate edit to C is needed to change its stored value.
Acceptance wording to adapt
For copy-mode records, store the current parent default at creation and leave it unchanged after parent edits. For inherit-mode records, resolve the current parent value on use. Keep the modes explicit.