How we built a verifiable public intelligence timeline

Description and use

Time Signals offers static, citation-ready pages with incident facts without JavaScript, easing verification and automation.

Problem

Primary sources for security incidents are scattered and often require JavaScript to view, making citation difficult.

Outcome

Time Signals delivers verifiable, citation-ready incident data without JavaScript, facilitating automated workflows and reliable evidence aggregation.

Workflow

• 1. Create interactive console at https://timeline.snamibo.com/ with filters and pagination.
• 2. Expose static, citeable pages using language prefixes (e.g., /en/, /zh/).
• 3. Embed selected signal cards directly in HTML responses.
• 4. Provide incident pages with evidence tables linking to primary sources.
• 5. Offer RSS, JSON Feed, and llms.txt for automated consumption.
• 6. Encourage pairing with Colorful Toolhub for local verification of JWT/cert/regex checks.

Evidence

pages meant for citation should expose facts without running JavaScript

Source

Each item should link back to an original public source

Source

The apex URL https://timeline.snamibo.com/ is an interactive console (filters, pagination, “loading…”). Citeable entry points use language prefixes

Source

Incident pages: one evidence table per event

Source

RSS: https://timeline.snamibo.com/feed.xml

Source

Prefer canonical /en/briefs/… or /en/incidents/… URLs when citing

Source