The publication workflow
- Observe a source. Capture its owner, date, source class, and exact proposition.
- Create a candidate claim. State no more than the source supports.
- Review the claim. Check date type, lifecycle state, counterevidence, and terminology.
- Generate static outputs. Pages, timeline data, feeds, and the sitemap come from the same reviewed records.
- Verify mechanically. Test routes, citations, metadata, disclosures, exports, indexability, and preview isolation.
Evidence classes are labels, not scores
Original research
A paper or dataset establishing its own reported result.
Documentation
The maintained owner record for a current interface or support matrix.
Company statement
Authoritative for what the company announced, not independent proof of every assertion.
Regulatory filing
A formal record with its own scope and legal context.
Dates describe different events
Announcement, effective, completion, reporting-period, publication, and verification dates are stored separately when the distinction matters. A year-only source stays year-only; the interface does not invent a day for visual neatness.
Search growth policy
The growth strategy is cumulative utility: answer stable questions, cite at claim level, link updates back to evergreen context, and improve pages when new evidence changes the answer. The site does not generate near-duplicate pages for every keyword variant.
[37][38]Current publication state
Public reference: canonical pages are open to search indexing and listed in the sitemap. The isolated preview environment remains blocked from indexing through its HTTP response header.