Files

T

timothy 0ad02db651 feat(603): adopt OKF's optional stale-after and Sources decision-record metadata

Evaluated the Open Knowledge Format (GoogleCloudPlatform/knowledge-catalog okf
v0.2, scaccogatto/okf-skills) as a replacement for our decision-record system and
rejected it: its conformance rules are deliberately permissive exactly where ours
are strict (broken links, unknown types and missing fields must all be tolerated;
`deprecated` points at no successor), and its stable identity is the file path,
which the breadcrumb rule tells agents not to trust.

Adopted two of its optional families instead, additively:

- `stale-after: YYYY-MM-DD` on the metadata line — marks a record asserting an
  outside-world fact as due for re-confirmation. Absolute date, no TTL.
- `**Sources:**` in the metadata block — the evidence a record rests on, as
  distinct from `Signals:` (recall keywords).

Neither is required; absence is never an error. A malformed `stale-after` is
blocking (it would silently never fire), but a past-due record is only a
non-blocking `::notice::` — going stale is the passage of time, not a defect in
whatever commit is under test. The catalog's new "Review due" section renders the
date only and never a clock-derived verdict, so it cannot drift `--check` red on a
calendar boundary with no commit touching the corpus.

No backfill: no existing record adopts either field here.

fixes #603

2026-07-25 15:22:50 +02:00

978 B

Raw Blame History

Decisions

Index

(#y)

2026-07-17 — Migrated example (#406)

key: ci.runner-placement · status: active · since: 2026-07-17 · supersedes: none · superseded-by: none Rule: Every CI services container gets an explicit cap. Signals: ci, runners · paths: .gitea/workflows/docker-build.yml · issues: #390 #406 Mechanics: docs/ci-cd.md → CI lanes

Rationale prose here.

2026-07-19 — Optional stale-after / Sources example (#603)

key: ci.peak-anon-measurement · status: active · since: 2026-07-19 · supersedes: none · superseded-by: none · stale-after: 2027-01-15 Rule: The test job reports a sampled true peak anon. Signals: ci, memory · paths: scripts/ci-peak-anon.sh · issues: #412 Mechanics: docs/ci-cd.md → CI lanes Sources: gitea run 4471 (measured) · scripts/ci-peak-anon.sh