Verification

Documentation rots quietly. Verification makes freshness visible — on every doc, including published ones.

The three fields

Any doc can carry:

• Owner — the person answerable for this doc's accuracy.
• Verified — a stamp saying "I checked this, it's right," with who and when.
• Review due — a date after which the doc should be re-checked. Past-due shows amber wherever the doc appears.

Set them from the doc's inspector in the Library. Verifying is self-asserted — the stamp records who made the call, no approval chain.

Where it shows

Internally, verification state appears in the Library tree and doc views. On a published site, verified articles carry a public verify strip — "✓ verified · by Olof · review due Sep 12" — so customers can see the doc is maintained, not abandoned.

Why it matters

A knowledge base your team doesn't trust gets abandoned; one with visible owners and freshness dates gets maintained. The review-due amber is deliberately public pressure — a stale doc embarrasses its owner slightly, which is exactly the mechanism that keeps docs alive.