Reference Source Alerts
Confirmed source changes, checked every six hours.
Confirmed source-change days are shown with category counts, source links, and signal quality diagnostics for Decide reference applications.
Stable compatibility feed
This route and JSON endpoint stay live for existing integrations and registry references that still call this feed policy alerts.
Operational alert packet
This page is a utility packet for source-change review. It does not decide customer actions by itself. It gives operators a confirmed feed, source links, quality diagnostics, and a response path for reference applications.
Signal
Confirmed semantic source-change days are separated from continuity rows, pending candidates, volatile indicators, and fetch holds.
Source
Rows link back to source pages, workflow runs, and issue records so a reviewer can inspect the evidence directly.
Quality
Diagnostics make fallback-derived rows, missing fields, and pending-age risk visible instead of hiding feed uncertainty.
Response
Confirmed changes route to reference-app review before any docs, example, or source-backed rule is updated.
Snapshot
Signals are sourced from the Supabase-backed policy alert feed maintained by scheduled checks in decidefyi/decide.
A vendor appears on multiple dates only when a new semantic source diff is confirmed. Default mode includes continuity rows so intentional no-change days are explicit.
Alerts loaded
Latest alert date
Latest confirmed changes
Confirmed rate
Pending half-life
Volatile ratio
Age-threshold rows
Alert response path
The alert feed is useful only when the response is explicit. Confirmed rows should create review work; quality flags should slow down changes until a human can inspect the source.
| Signal | Operator response | Decision lifecycle impact |
|---|---|---|
| Confirmed change | Open source page and workflow run, confirm affected category, then update the reference application or docs if the source change is relevant. | Future Decision Records should use the updated evidence path after the source-backed rule is changed. |
| Continuity row | No source change is claimed. Keep the row for review continuity and feed health. | No change to customer-facing policy behavior. |
| Pending or volatile | Do not treat as a confirmed semantic change. Inspect the candidate and wait for confirmation or manual review. | Do not update source-backed evidence codes until the signal stabilizes. |
| Fetch hold or coverage gap | Review workflow health and source coverage before relying on the feed window. | Route source-backed changes to owner review until coverage is healthy. |
Lifecycle context
Source alerts sit upstream of the Decision API lifecycle. They inform reference applications and evidence mappings, while Decision Records and packets remain the proof artifacts attached to customer actions.
Scheduled checks detect a confirmed semantic source diff and link the source page, issue, and workflow run.
An owner decides whether the source change affects a reference application, evidence code, or public example.
After review, future /api/decide calls can cite the updated source-backed evidence in their Decision Records.
Decision Packet v1 remains the portable proof for customer actions; this feed is supporting source-change evidence, not the customer action record itself.
Signal legend
Confidence levels summarize feed quality. Flags describe instability signals per day.
Confidence badges
Row flags
`n/a` means the field was not present in the latest source payload, often during fallback reconstruction.
Quality summary
Loaded-range quality totals help separate confirmed changes from unstable/fallback periods.
Escalated days
Volatile days
Fallback-derived days
Rows with n/a fields
Alert Feed
| Date (UTC) | Status | Changes | By category | Source pages | Links |
|---|---|---|---|---|---|
| Loading source alerts… | |||||