Does waiting mean approval? Archive raw status, display aliases and reply eligibility
A display category is not a source rewrite, approval or reply permission
CollieRadarTaskState.classify trims/lowercases then matches explicit aliases. waiting/pending can map to waiting; done/completed to completed; unmatched stays unknown. Display meaning neither rewrites source text into another status nor independently proves approval, completion or reply eligibility.
Different from missing defaults, roles and batch review
Defaults concern placeholders, roles concern who confirms, batches concern original inputs. Here nonempty raw status versus derived display categories need separate retention. No source edit/enum migration or relabeling to unlock writes is performed.
| Check | Verified scope | Manual review | Not established |
|---|---|---|---|
| Raw status | Actual supplied string | Original/source/version | Category is the raw value |
| Classification | Trim/lowercase explicit aliases | Derived versus raw | Every control/write path normalizes identically |
| waiting/pending | Can map to waiting | What is awaited | Your approval/acceptance necessarily awaited |
| done/completed | Can map to completed | Source claim versus actual evidence | Execution or PM acceptance proven |
| Unknown alias | Falls to unknown | Keep original/gap | Nearest known state guessed |
| Reply eligibility | Actual target/capability/version separately | Original entry/fresh target | Waiting icon grants writes |
| Translation/editing | Label editorial presentation | Original versus explanation | Relabeling creates approval |
| Comparison/retention | Raw status/category/reason | Same category/different source/scope | Same category means same event |
Synthetic status record
A has raw pending and derived waiting. B has raw 等你验收, also waiting. Shared category does not establish the same recipient, operation authority or approval. Do not replace A with B’s source wording.
Source status is still a source claim requiring truth/completion evidence. Reply availability depends on the original flow/current target; classification alone establishes neither always writable nor never writable, and cannot bypass guards.
FAQ
Can pending be treated as 等你验收?
No. Grouping does not equate original text, awaited person or approval scope.
Does done prove backend execution?
Not independently. It classifies explicit source state; execution/acceptance need evidence.
Does unknown guess the nearest state?
Unmatched classification stays unknown; invent no business conclusion.
Does display trimming apply to every write path?
No inference follows. Inspect each entry’s conditions.
Can relabeling status grant reply eligibility?
No. Target/capability/version/identity authority is not granted by edited labels.
Can shared category merge history or approvals?
No such feature is added. Retain raw values/events/scopes instead of replacing associations with categories.
Reading and source
Placeholders · Roles/confirmation · Batch scope · Request identity · Start · Privacy
Explicit classification · Raw display/entry · Current reply guards
