Drop `stale_after` from the Strategies Library, and correct SCHEMA §9’s OKF claim

Background

Spun out of KB-OS-okf-evaluation (Processes, closed 2026-09-23). That task evaluated OKF (Open Knowledge Format) as a vault-wide convention. The verdict was don’t adopt: a cold-agent A/B test showed no worthwhile gain. Log: Core/Processes/Projects/KB-OS/logs/2026-09-23_OKF-Evaluation.md.

Along the way it found two things in this library, and Talbot ruled on them:

stale_after: Talbot said “I don’t see a benefit in stale_after. Would require extra admin with no payoff.” and then “yes. Let’s drop stale_after.” Nothing reads the field. All 33 strategies carry the same date-only stale_after: 2027-03-31, which also breaks OKF’s current format; since the 2026-08-21 spec commits, OKF requires an ISO datetime with an offset.
SCHEMA §9 overstates OKF conformance. It says the index is “conformant by construction”. OKF §8 wants index.md bodies made of * [Title](link) - description lists under headings. The library’s generated indexes use tables and wikilinks.

Tasks

Remove stale_after from all 33 strategy files and from the SCHEMA template (§6, stale_after: YYYY-MM-DD), SCHEMA’s own frontmatter (line 8), §3.5 (the trust-field list and table row) and §9 (“Adopted from OKF v0.2’s trust layer”).
Check strategy-lint for any stale_after handling. A grep of strategy_lint.py and artifact.py found none on 2026-09-23, but the vocabulary is read from SCHEMA §8, so confirm with strategy-lint lint after the edit. Regenerate index.md and library-view.html.
Rewrite SCHEMA §9 honestly. Either state that the index files are not §8-conformant (the value is interoperability, and OKF consumers must tolerate this), or change strategy-lint index to emit the §8 list format. Recommend one.
Bump the SCHEMA version per its changelog.

Success Criteria

grep -r stale_after SDC/IP/Strategies returns nothing, strategy-lint lint exits 0, and SCHEMA §9 makes no conformance claim the files don’t meet.

Inherited from KB-OS-okf-evaluation

Next Steps still open when the parent closed:

Send the Strategies-Library project the SCHEMA §9 conformance finding, and drop its own stale_after?
- yes. Let’s drop stale_after.

Path to Completion

Project SSOT: STATUS (current state) · ROADMAP (what’s left) · oversight SSOT: SDC/IP/Projects/Strategies-Library/ROADMAP.md

Now: /task-start D:\FSS\KB\SDC\IP\Projects\Strategies-Library\Tasks\sdc-ip-drop-stale-after.md

Then, in order:

/task-complete D:\FSS\KB\SDC\IP\Projects\Strategies-Library\Tasks\sdc-ip-drop-stale-after.md: close once lint is green and §9 is corrected.

Blocked on you: none.

Done when: grep -r stale_after SDC/IP/Strategies is empty, strategy-lint lint exits 0, and SCHEMA §9 claims nothing the files don’t meet.

Drop stale_after from the Strategies Library, and correct SCHEMA §9’s OKF claim