The changelog
564 entries. More than everything else combined.
190 observations, 51 ideas, 112 decisions — 353 rows, added up. The changelog alone outnumbers all three together. It's the cheapest thing in the record to write, and that's worth being honest about.
564
Changelog entries
353
Observations + ideas + decisions
14
Of 564 are the vocabulary word added last
An entry lands here whenever something ships — usually as one row in a batch that also moves a task to done and logs the time against it, so a completed task never exists without the changelog line explaining what it was.
Five words, not the four that were assumed.
An entry is typed as completed, milestone, win, or release — and, on 14 of the 564 real rows, update. That fifth value wasn't in the first pass at this schema; it showed up when the real export was read rather than guessed at, and the column was widened to match the data instead of the data being forced to match a tidier guess.
It's the third time in this migration that reading the actual rows overturned a conclusion drawn from reading the code that writes them. The code said one thing was true. The rows said otherwise, twice more before this.
changelog_entry.type — the CHECK, widened once
completed | milestone | win | release | update
^^^^^^
14 of 564 rows use this oneAnnounced and measured are kept apart, deliberately.
A changelog entry means someone said something shipped. It doesn't mean a check confirmed it. StratOps keeps those two ideas separate rather than letting the louder one — the announcement — stand in for the quieter one that actually matters.
Ask what happened last week and the answer draws on both, and names which is which. When they disagree, that disagreement is the finding, not a bug to be smoothed over before it reaches you.