We have systems of record for customers, money and code. We still have no system for judgment management.
Corporate knowledge management stored what people had written down. The part that matters most, what experts know and decide, was never managed. Agents can now interview, draft and score, and a named person can confirm. That makes a system for judgment management possible, and knowledge management ripe for rebirth.
From paper to open source. The Mission Room ideas in our working paper are being built as open-source software under Apache-2.0, free to fork for any kind of work. We are seeking design partners for the first missions, academic feedback and industry collaboration, and a few investors who see the category early.
01The missing system
Every generation of enterprise software gave one kind of asset a system of record. Judgment, meaning who knows what, what an expert decided on what evidence, and who stood behind it, is still managed in meetings, chat, shared files and slides.
| Era | What it managed | The system of record |
|---|---|---|
| 1990s, knowledge management | Documents and written-down know-how | Intranets, document and knowledge repositories |
| 2000s to 2010s, enterprise software | Customers, money, people, work | CRM, ERP, HR systems, issue trackers |
| 2020s, agents | Explicit traces and memory inside one enterprise | Knowledge bases, context graphs, decision logs |
| Next | Judgment across a provider and its client: who knows what, what was decided, on what evidence, confirmed by whom | A system for judgment management (the Mission Room, proposed) |
02Why knowledge management disappointed, and why it can be reborn
Lineage: Polanyi (1966) on tacit knowing; Nonaka and Takeuchi (1995) on converting tacit knowledge; Davenport and Prusak (1998) on managing what organizations know. Full references are in the working paper.
03Why now
04The wedge: the boundary, not the memory layer
A Mission Room runs the Judgment Work pattern (Draft, Confirm, Commit) in a governed, time-boxed engagement between two organisations: agents draft, a named Lead confirms, client context stays the client's, provider method stays the provider's. The output is a scored, confirmed decision record with provenance to the source interview. That is a system of record, not a knowledge base. Decision logs and context graphs record what an enterprise does inside its own walls; a Mission Room records expert judgment across the boundary between two organisations.
05Where it bends to financial services
The same base serves any provider that must understand how a client really operates before delivering. Two shapes the paper sketches for financial institutions (illustrative, not built):
| Mission | Provider → client | What the Lead confirms | |
|---|---|---|---|
| Customer onboarding discovery | Fintech implementation team → bank or credit union | Each process step or control gap, owner, severity, before go-live | illustrative |
| Third-party risk go-live | RegTech vendor → regulated firm | Each vendor relationship, evidence, readiness | illustrative |
| AI adoption assessment | Advisory firm → enterprise | Each AI use case, owner, controls, score | specified |
Implementation and onboarding are where B2B fintech vendors lose time. A Mission Room is a candidate for the discovery stage of that motion.
06Why open source
Adoption first. Consulting firms and vendors will not put their method into a closed tool owned by a competitor. Apache-2.0, a published playbook format and a rule that no fork can remove the human confirmation gate make the Chassis a standard others can build on. Honest caveat: open-source users will be builders, not consultants, so the hosted route has to serve the rest.
07How it could earn
Request detail
08What would change our mind
Seven public hypotheses. Three that matter most to a buyer:
| ID | If this holds… | …the case strengthens; if not, it weakens |
|---|---|---|
| H1 | Leads override a stable, measurable share of agent scores | Evidence that the human gate is real value, not ritual |
| H2 | Missions reach Commit faster than comparable work on general tools, at no loss of quality | The efficiency case |
| H3 | Interviews change conclusions that documents alone would reach | Why elicitation is the product |
09Milestones we'd be judged on
10Risks we can name
The category is crowded and moving fast
Analysts and funded startups are already in the space. Our difference is the provider-client boundary, which has to hold up in practice.The name
Others use similar names in adjacent spaces. We are reviewing the name and our trademark position.Audience mismatch
Consultants won't self-host. Builders adopt the code; the hosted route has to reach the rest.Claims ahead of the build
No SOC 2 examination has been performed. State of each safeguard is published, including what is still in development.11What we are asking for
A 30-minute conversation to pressure-test the thesis. For investors with bank and vendor networks, we would value introductions to implementation teams and institutions that could run one real mission as design partners.
Book 30 minutesRead the paper