What is covered
The machine-readable content-review.json currently covers 26 reviewed items: six learning guides, three browser worksheets, six curated source-toolkit card pages, and all eleven CBT Cards-owned practices.
The registry uses stable resource or practice IDs. It does not track users, worksheet answers, app journals, or other private data.
What a review checks
- Sources and evidence notes still support the wording being published.
- Mechanism claims remain narrower than diagnosis, treatment, or efficacy claims.
- Safety exclusions still preserve genuine danger, protective boundaries, professional instructions, and high-stakes decisions.
- Public worksheet privacy wording still matches the no-submit browser behavior.
- Curated source-toolkit pages still match their pinned source IDs and publication overlay.
- Owned practices still match their evidence, ontology, recommendation contract, and
avoid_whenboundaries.
Freshness target
The project uses an internal 365-day review target. This is a maintenance policy, not a clinical standard. Each covered item records last_reviewed and next_review_due; CI blocks the freshness gate when a covered item is overdue.
A material evidence, wording, safety, privacy, or product change should trigger an earlier review instead of waiting for the scheduled date.
Three different review layers
Publication review in toolkit-review.json decides whether a raw source record may have a standalone CBT Cards page. Unlisted source records remain unreviewed and source_only.
Source-corpus audit in toolkit-audit.json triages all 115 pinned source records for duplication, framework attribution, overclaim, treatment-like wording, and editorial priority. Audit status is not publication approval.
Freshness review in content-review.json tracks already published or CBT Cards-owned reviewed material after it enters the trusted layer.
What “reviewed” does not mean
Editorial and safety review does not mean clinical validation, proof of efficacy, medical-device review, diagnosis, or a recommendation that an exercise is appropriate for a particular person. CBT Cards does not make those claims.
For agents and downstream reuse
When freshness matters, join a catalog resource or owned practice to the content-review registry by stable ID. Do not infer a later review date from sitemap lastmod, Git history, a newer agent-skill release, or a translation timestamp.