Every decision, with its source
Omne ERP's decisions were spread across calls, Slack threads, Jira comments and specs, and nobody could keep track of all of it. So in September 2026 I built a decision wiki with Claude. It reads all of those every night and keeps one record of what was decided.
- Built
- September 2026, with Claude
- Reads
- Meeting recordings, Slack, Jira, spec documents, the design-system code
- Updated
- Every night
- Used by
- The BA and design team
The problem
Before the wiki, the source of truth was split three ways: the spec documents, the designs and Jira. A design got updated and the stories didn't. The spec changed and the design didn't. Sometimes a meeting changed something and none of the three got updated.
An ERP runs on thousands of small calls like that. Which units can a stock count accept? Who sees the cost of a new serial number? Can a cancelled quote be reopened? Each one got answered once, then answered again a bit differently in another call. The decisions were buried in more than 1,800 recorded calls, a lot of them in a mix of Urdu and English, and QA and developers kept sending me the same questions.
What the wiki holds
Meetings
Every recorded product meeting since July 2023, written up from the full transcript.
Decisions
One page per ruling: who decided, when, what kind of call, and whether it still stands.
Modules
For each module, the rulings in force and how they changed.
Release scope
For each module in the release: what's in, what's hidden, what's on the backlog, what's still open.
What it does for the team
The wiki is the team's hub now. It merges the spec documents, the designs and Jira into one record, and it updates every night, so whoever picks up work in the morning has the latest.
- When analysts write user stories, they check them against the wiki to make sure nothing's been missed.
- When the handoff review skill runs, an extension I added makes it check the designs against the wiki. Every feature stakeholders approved has to be there, and nothing they didn't approve can be.
- QA and developers get answers with a source: the ruling in force, its page and its date. If an answer isn't certain, it goes to the CEO in a thread before anyone acts on it.
- Every module in the current release has a scope page showing what's in, what's hidden, what's on the backlog and what isn't decided yet.
- When two rulings clash and nothing says which one stands, the wiki flags them for me instead of picking one.
The result is that the stories, the designs and the specs say the same thing.
In numbers
Decision pages, each with who decided and when. More than 13,700 are still in force.
Meetings written up from their full transcripts since July 2023.
Business rules, each linked to its module.
Module pages, each listing its rulings in force and how they changed.
Source: the Omne decision wiki, counted on 16 November 2026. The counts grow every night.
More of the work
Tell me what's stuck
Send a few lines about your product, your team and the problem. If I'm not the right person for it, I'll say so.