Story: Audit and classify FK-like/lookup entities for badge/image/plain-text rendering
Table of Contents
This page documents a story in Sprint 24. It captures the goal, current status, acceptance criteria, and the tasks that compose it.
Goal
Split from Roll out badge/image/plain-text rendering across classified domain entities (formerly the merged classification+rollout story) at sprint 24 health review: keep the completed audit/classification work recorded as shipped, separate from the still-STARTED implementation work that consumes it.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent sprint | Sprint 24 |
| Now | Audit/classification complete: all 120 candidate entities classified, documented, and batched for implementation. |
| Waiting on | Nothing. |
| Next | Nothing – see the rollout story for implementation. |
| Last touched | 2026-08-03 |
Acceptance
- A written audit/classification exists covering every FK-like/code/lookup domain_entity model (all 120, not just the 10 already badged): each is classified as colour badge, image/flag, or plain text/neither, with the reasoning documented (not just the verdict), and a stated policy/criteria for the classification. The classified list is split into ready-to-annotate vs needs-new-badge-definition/image-data, then batched into groups for implementation.
Tasks
| Task | State | Start | End | Description |
|---|---|---|---|---|
| Audit and classify entities: badge, image, or plain text | DONE | 2026-07-30 | 2026-07-30 | Inventory every FK-like/code/lookup domain_entity model; classify each as colour badge, image/flag, or plain text/neither, with documented reasoning and a stated policy. Split the result into batches for implementation. |