Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

chore(docs): ratchet the freshness budget to the measured 127 and queue order 403 to drain it

nirholas01ccc75cb0e4
diff --git a/data/docs-freshness-budget.json b/data/docs-freshness-budget.json
index 965f1a338..08e218cef 100644
--- a/data/docs-freshness-budget.json
+++ b/data/docs-freshness-budget.json
@@ -1,7 +1,7 @@
{
"$doc": "/docs/freshness",
"$comment": "Ratchet for `npm run check:docs-freshness`. maxStale is the number of docs allowed to be describing code that moved after they were written. It goes DOWN as docs are refreshed and never up without a reason recorded below, which is what stops drift from being permanently normal.",
- "maxStale": 5,
+ "maxStale": 130,
"history": [
{
"date": "2026-07-31",
@@ -17,6 +17,11 @@
"date": "2026-09-17",
"maxStale": 5,
"reason": "Full sweep of the whole stale queue, 110 docs (109 ranked at the start, plus one that crossed the line during the pass): 82 corrected against the commits that drifted, 22 read and found already accurate, 6 classified as dated records. Review baselines landed in the same pass (data/docs-freshness-reviews.json), so a doc verified without an edit can now be recorded instead of staying measured-stale, which is what let this reach 0. The check is wired into `npm run gate` from here, so 5 is deliberate headroom for normal churn between passes rather than a backlog allowance: 367 docs sit in watch and a few cross the line most weeks."
+ },
+ {
+ "date": "2026-10-23",
+ "maxStale": 130,
+ "reason": "Raised from 5 under work order 402 (restore a green gate): 30 docs were re-verified and committed (157 stale down to 127), but the corpus drifted well past the 2026-09-17 baseline after a month of fast shipping. 130 is the measured 127 plus 3 headroom. The remaining backlog is owned by order 403 (prompts/finish/403-auto-drain-docs-freshness.md), which ratchets this back down to 5."
}
]
}
diff --git a/prompts/finish/403-auto-drain-docs-freshness.md b/prompts/finish/403-auto-drain-docs-freshness.md
new file mode 100644
index 000000000..ab0636406
--- /dev/null
+++ b/prompts/finish/403-auto-drain-docs-freshness.md
@@ -0,0 +1,18 @@
+# 403. Drain the docs-freshness backlog: 127 docs describe code that moved
+
+How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now, no gate. Written 2026-10-23 as the remainder of [402](402-auto-restore-green-gate.md), which refreshed 30 docs (commit 38d2e8eec) and could not drain the rest in one session.
+
+## Measurement
+
+`npm run check:docs-freshness` reports 127 stale docs. `data/docs-freshness-budget.json` carries `maxStale: 130` for now, with a dated reason citing order 402. This order brings it back to 5.
+
+## Task
+
+1. Run the docs-freshness workflow in batches of 30 (`Workflow({ name: "docs-freshness", args: { limit: 30 } })`) until `npm run check:docs-freshness` reports at most 5 stale.
+2. Commit each batch topically with explicit paths (the doc edits, `data/docs-freshness-reviews.json`, `public/docs-freshness*.json`). No dashes of the em or en kind in added lines.
+3. After every batch, lower `maxStale` in the budget file to the measured count plus 3, with a dated history entry.
+4. Generated docs (for example `docs/agent-abilities/ABILITIES.md`) are fixed by editing their source and regenerating, never by hand.
+
+## Done when
+
+`npm run check:docs-freshness` exits 0 with `maxStale` at 5, `npm run audit:docs` is clean, and this file is removed with a dated entry in `prompts/finish/_context/production-100-PROGRESS.md`.