Ownership, versioning, and contribution

Ownership

This pilot establishes documentation conventions for Thomas’s Radarist project. It does not claim a company-wide governance program previously existed. The process below is a proposed operating model for keeping the new reference useful.

Change process

Drift controls

• Source hashes provide a trigger for review, not automatic proof of inconsistency.
• If a palette or component changes, inspect both isolated specimens and the screens that use it.
• Treat data/model changes as documentation changes when they alter a workflow or action’s meaning.
• Do not retain a screenshot as current evidence after the underlying behavior has materially changed.

Pilot release

Documentation version 0.1 records the first source-grounded Radarist reference, with a WIP product status and explicit readiness register. Future releases should record concrete changes and verification rather than promotional claims.

Reusable template

The site renderer, section hierarchy, structured block types, screenshot controls, source references and readiness model can carry forward. Every other project still needs its own audit, authored decisions, component examples and realistic capture fixtures.