Skip to content

Fix: amended dots in the policy field could never appear - #82

Merged
l0cka merged 1 commit into
mainfrom
fix/observatory-amended
Aug 8, 2026
Merged

Fix: amended dots in the policy field could never appear#82
l0cka merged 1 commit into
mainfrom
fix/observatory-amended

Conversation

@l0cka

@l0cka l0cka commented Aug 8, 2026

Copy link
Copy Markdown
Owner

Sharp catch from review of the live hero: the Policy Field legend advertises an amber "Amended" category, but the dots were coloured by policy status — and no record carries status amended, because this register treats amendment as an event: the policy stays active and gains an amended date (12 records have one).

Dots now colour by the primary date's type, so a policy whose latest lifecycle event is an amendment shows amber. The 30-day "New" override keeps precedence, so fresh amendments show blue first and turn amber as they age.

Verified on Argus: typecheck, lint, 442/442 tests, build; screenshot confirms roughly a dozen amber dots across five jurisdictions, none before.

🤖 Generated with Claude Code

…o record uses

The register treats amendment as an event: policies stay active and carry
an amended date. The beeswarm coloured by status, so its amber legend
entry could never occur. Twelve dots now show it, with the 30-day new
override keeping precedence.
@l0cka
l0cka merged commit 980440e into main Aug 8, 2026
3 checks passed
@l0cka
l0cka deleted the fix/observatory-amended branch August 8, 2026 04:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant