Compare the rule with concrete cases
Fictional record types use code R differently: a reading task uses R for reviewed, while a draft uses R for requires-edit. The meaningful pair is record type plus code. A global label lookup by R alone would mislabel one of them.
| Type | Code | Meaning | Lookup identity |
|---|---|---|---|
| Reading task | R | Reviewed | reading/R |
| Draft | R | Requires edit | draft/R |
| Draft | C | Checked | draft/C |
Work through the distinction
Reusing a symbol is allowed only when its scope is retained. Shared storage or a shared component must not silently impose one process’s meaning on the other.
A draft with R is shown as reviewed. Is that supported?
Show the worked answer
No. draft/R means requires edit. The reviewed label belongs to reading/R.
Acceptance wording to adapt
Resolve a display meaning using the full pair (record_type, status_code). Return “requires edit” for draft/R and “reviewed” for reading/R. Reject a missing type instead of guessing a global R meaning.