This page records how CosmicTao maintains public content freshness for search engines, AI answer engines, and human reviewers. We do not rotate sitemap dates from build time; a date changes only when page copy, structured data, FAQ, source notes, public discovery paths, or tool contracts materially change.
Policy
Sitemap lastModified dates are maintained from substantive content, schema, or discovery-path changes. They are not set from build time and are not rotated on a timer.
Single source
The public page, /api/public/tools, llms.txt, and sitemap.ts read from src/lib/contentFreshness.ts.
Recently Updated
Content freshness policy
Public freshness page, llms.txt discovery notes, and the public tool manifest were updated for the first low-cost public API suite.
Evidence: This date reflects real API discoverability and machine-readable manifest changes, not a build-time rotation.
Market-cycle SEO/GEO facts, visible FAQ, FAQPage schema, llms.txt discovery, and sitemap lastmod were updated.
Evidence: The page explains completed weekly candles, authorized data boundaries, and non-investment-advice framing.
Sample paths: /market-cycle
Palmistry reading lab
Palmistry page copy, metadata, visible FAQ, FAQPage schema, privacy/storage boundaries, and llms.txt discovery were updated.
Evidence: The page now describes user-confirmed heart, head, and life lines, saved-report-only storage, and cultural-reading boundaries.
Sample paths: /labs/palmistry
Audited Static Groups
Older product and library groups keep their older lastModified dates until they receive a real editorial, schema, FAQ, source-note, or internal-link update.
About and methodology pages use their latest recorded editorial-policy review date.
Sample paths: /about, /methodology
Core product pages
Home, Bazi, oracle, match, wishes, and generated zodiac pair pages use the latest recorded product-page review date unless a route has a newer dedicated group.