Document-linked source library
A dated audit trail behind every update card.
The production database stores source, topic, publication date, first seen, last checked, status and content fingerprint. This desktop version displays the bundled snapshot.
| Published | Document | Source | Topic | First seen | Last checked | Status |
|---|
Database behaviour
What changes in a hosted implementation
- Scheduled checks can run every six hours or at a locally approved interval.
- An existing record is updated rather than duplicated when the canonical URL or content fingerprint matches.
- Removed, redirected or materially changed items are flagged for review; the old audit entry is not silently erased.
- Only approved records are published to public cards. Raw extracts remain internal and access-controlled.
- Failures leave the last approved data visible and trigger an operational alert rather than an empty news section.