4b. Freshness & re-verification#

Concepts can carry a re-verification date (stale_after) — a date after which the knowledge needs a fresh human look. It gets set three ways:

• Per-source content shelf life (Workspace tab → Sources): admins pick 1 day / 30 days / 1 year or a custom day count per source; concepts curated from that source get a re-verification date that far out.
• Workspace re-verification interval (Settings → Knowledge freshness, admin): promoting a concept to authoritative dates it this many days out. A source's own shelf life takes precedence for its concepts. Applies from the next promotion on (no backfill); blank turns it off — the default.
• Import: an OKF bundle's stale_after frontmatter travels in (§7).

Past its date, a concept is flagged "needs re-verification", joins the Insights re-curation queue, and is left out of the agent onboarding digest (§9b) — in both enforcement modes. Re-promoting it after a fresh human look extends the date (per the interval/shelf life in force).

Enforcement modes (Settings → Knowledge freshness, admin — two buttons):

• Surface (default): past-due concepts are flagged and queued but still answer questions — the signal shows everywhere, nothing else changes.
• Archive: past-due concepts are additionally excluded from retrieval (Ask, /v1/query, /v1/answer, agent search) until someone re-verifies them or restores them. Nothing is deleted or demoted either way.

Restoring from archive (admin): the Insights Archive list shows every past-due concept excluded by Archive mode, with a Restore to review button — it sends the concept back to the review lane as a draft (its re-verification date is cleared) so it flows through curation again. Alternatively, re-promote it from its concept page after a fresh look to extend the date in place.