A Kernel module is authoritative when it governs the accepted provider-neutral fact, validates its invariants, and exposes sanctioned ways to read or change it. Authority belongs to a dataset and boundary—not automatically to an entire application.
Why “source of truth” can mislead
A provider may be authoritative for the exact record it produced. Ledger may be authoritative for retained accounting-provider evidence. Kernel may be authoritative for the accepted invoice fact shared across products. Retainer OS may be authoritative for a versioned margin projection.
All three statements can be true because they describe different datasets.
Calling one whole application “the source of truth” hides evidence, workflow, and projection boundaries. Prefer a precise sentence: “The Kernel Time module is authoritative for confirmed time facts; the provider remains the origin and evidence authority for its records.”