Compare the rule with concrete cases
Original fictional record K has category R, title Notes and derived key R: Notes. Each table case edits K from that same initial state. The key formula is category + ": " + title. An inconsistent supplied key rejects the edit, preserving K, rather than establishing a manual override.
| Category / title | Supplied key | Derived key | Result |
|---|---|---|---|
| R / Notes | Not supplied | R: Notes | Accept and derive |
| R / Notes | R: Notes | R: Notes | Consistent |
| R / Notes | X: Notes | R: Notes | Reject inconsistent request |
Work through the distinction
An override requires its own explicit mode and acceptance rule. It cannot be inferred from a user-provided string in a calculated field.
Title changes to Plans and no key is supplied. What key results?
Show the worked answer
R: Plans. The formula still supplies the key; no manual key is created.
Acceptance wording to adapt
Derive display_key as category + ": " + title. If a request supplies a different display_key, reject it without changing the record. Absence of the key must use the formula, not an empty value.