Second Brain

regulations-refreshed-frontmatter-time-decay-discipline

1 min read

regulations-refreshed-frontmatter-time-decay-discipline

Regulations-refreshed frontmatter — time-decay content discipline

Regulated content (compliance lists, API version defaults, vendor matrices, pricing tables) silently rots. “Stale” isn’t caught by standard lints because the file still parses, links still resolve, and content is still technically present. Without a refresh signal, staleness creeps in and decisions are made on obsolete defaults.

Pattern (installed on Helix domain overlays, 16-Apr-2026):

---
name: fintech-overlay
description: ...
regulations-refreshed: 2026-04-16
regulations-refresh-interval-days: 90
---

Enforcement: /root/.claude/scripts/helix-regulatory-refresh-check.py — weekly cron 0 9 * * 1, exit 1 on any overlay where (today - refreshed) > interval_days. Non-zero exit triggers alerting.

Generalization: Works for ANY time-decay content:

  • vendor-matrix-refreshed (KYC providers, auth providers, observability vendors change/die)
  • api-surface-refreshed (Next.js / React / Prisma major version drift)
  • pricing-refreshed (cloud SKU changes)
  • compliance-refreshed (PCI DSS 4.0, EU AI Act, MiCA)

Rule: Content claiming authority on changing regulations/APIs/vendors MUST carry a refreshed-date + max-age frontmatter + external refresh check. Otherwise stale defaults ship to production and cause compliance failures.

Why it’s not just a comment: Comments don’t trigger alerts. Frontmatter + cron + exit-code does. External check converts informational decay into an actionable signal.

Graph View

Backlinks