// StaleSeal

Docs that prove they're fresh.

Documentation goes stale quietly. A doc describes code that moved on, and nobody knows which pages to trust. StaleSeal seals each doc to the code it covers — then tells you, deterministically, whether the seal still holds.

Hackathon prototype — built for the GitLab Transcend hackathon, October 2026.

Try the live demoView the code on GitLab
// What the live demo shows

The demo runs a small fictional codebase, ParcelTrack, with three docs. Its current report: 3 FRESH docs, 0 STALE, 75.0% doc coverage of source files — and one uncovered file, src/notifications.py, that no doc covers. The inverted coverage map is the point: it shows not only which docs are stale, but which code has no doc at all. The loop already ran end-to-end: a stale shipping-rates doc was fixed by a Duo-drafted merge request and re-sealed.

▸ 1 · Declare

Each doc names the code it covers

A Markdown doc lists the code files it documents in covers: front-matter. No guessing which pages describe which code — the mapping is written in the doc itself.

▸ 2 · Seal

A fingerprint is stored in the doc

StaleSeal computes a SHA-256 fingerprint over the covered files and stores it in the doc. The seal is the doc’s own claim about the code it describes.

▸ 3 · Verdict

Every scan recomputes, and names names

Recompute the fingerprints: a doc is FRESH or STALE, and a stale verdict names exactly which files changed. No confidence scores, no LLM judgment — the same inputs always give the same verdict.

▸ 4 · Loop

Stale docs get fixed, then re-sealed

A stale verdict lists the doc for review. A GitLab Duo flow drafts the doc fix as a merge request, a human approves and merges, and the doc is re-sealed. The loop is supervised: Duo opens merge requests and stops — it never merges.

// Honest notes