A spreadsheet is easy to change and impossible to review. Alter one cell, and afterwards nobody can see what was changed, by whom, or why.
Safe and locked away, or open and unreliable
Keep a project's facts in a database and they are safe - and locked away: nobody sees a change go by, nobody reviews it. Keep them in documents and anyone can edit them - and within a month they contradict each other.
Tables, kept as plain text
tad - text as data - keeps each table as a plain text file, one line for each row, in the same place as the code. So a change to a fact is a change to one line: it can be read, reviewed, discussed and undone like any other change.
A guard stands at the door. Whatever is edited is loaded, checked against the rules the data must obey, and written back in one fixed form. Anything else is refused.
A ledger, not a whiteboardOn a whiteboard the latest hand wins and the past is wiped away. In a ledger every entry stays, in order, with its author.
Pages drawn from the data
The pages people read are drawn from the tables. So a page cannot say something the data does not.
What it is for, and not
It suits facts that people decide and review - hundreds or thousands of rows, not millions. And it began as a set of scripts.
Where it stands
Working, and in use by several repositories. It is kept as it is: what it taught lives on in ocoeco, where the new work goes.