A RECORD
NOBODY CAN EDIT.

A history that can be corrected is a history that can be corrected in somebody's favor. Once a record can be edited, every number derived from it becomes a claim about what the current state of the database says rather than about what happened.

Getting something wrong does not mean rewriting it. It means recording the correction as its own entry, with its own time, so the sequence shows both what was believed and when it changed. That is more useful than a clean record, not less.

Contribution scores, tiers, ownership and residuals are all computed from the log rather than stored as editable fields. A score somebody can set is a score somebody can sell.

Financial entries are double-entry and are checked by invariants that run before every deployment: every transaction sums to zero, no ledger row is ever updated or deleted, and the derived balance must equal the cached one. A violation fails the deploy rather than being reported later.