← Mimir docs
The decision we're here to make: do we commit to building Phase 1 — one real product, end to end, on the Mimir engine — with the pack boundary as the explicit success test? Plus: resourcing for Phase 1, and a greenlight for a first design-partner pilot.
Running order
| # | Topic | What we cover | Time |
|---|
| 1 | Why we're here | The problem shape, and the decision on the table | 5 min |
| 2 | The thesis | One engine, domain knowledge as packs; the two planes; the component map | 8 min |
| 3 | One case, end to end | The 8-step example, then "swap the pack" → a different product, same engine | 8 min |
| 4 | How we pressure-tested it | The back-test: 13 products on paper → 18 requirements; what it forced us to add | 8 min |
| 5 | Execution, models & compliance | Sync/async + priority; Model Gateway; compliance as a USP (and its real build items) | 8 min |
| 6 | Build phases & buy-vs-build | Phase 1→3; what we integrate (commodities) vs what we own (the moat) | 7 min |
| 7 | Risks & open questions | The honest thin-ice list — where we are not yet proven | 8 min |
| 8 | The ask | What we need from each role to start Phase 1 | 6 min |
| 9 | Discussion & next steps | Decision, owners, follow-ups | open |
What we want your read on
Open questions for the room
- Do we agree the buy-vs-build line — integrate OCR / vision / LLM / workflow / model-gateway; build the Signal model, fused Detect, pack & compliance layer?
- Which domain is pack #2 (health · lending · KYC)? It's how we prove "domain-agnostic."
- Risk appetite for the Agent Runtime and the cross-tenant link graph (both Phase 3)?
- Compliance priorities — which regimes / certifications matter first?
Not deciding today
- The final product / market name (separate track).
- Pricing & packaging.
- The cross-tenant link-graph design — Phase 3, needs legal review.
- Any published-accuracy number — nothing is measured yet.
Honesty note for the room: every figure on the slides is illustrative; the 13 products are a design exercise, not shipped software. No named customers, sample data throughout. "Agentic" and the link graph are roadmap, not built. "Domain-agnostic" is design intent until pack #2 ships with zero engine change.
Pre-reads: the docs hub · the back-test (one page) · the architecture map · the deck