Skip to content

Appendix K — Product Roadmap by Layer and Expansion Phase

This appendix explains the future of SUMMA in one unified map.

Its job is to connect:

  • the engine layers
  • the premium ladder
  • the commercial appendices
  • the legal expansion path
  • the non-legal adjacency path

Without a map like this, the company can start sounding like a pile of smart ideas. With a map like this, the company starts looking like a system.

That is the purpose of this appendix.

1. The core roadmap rule

SUMMA should not be built as a random list of features.

It should be built in layers.

And it should not expand in random directions.

It should expand in phases.

That means the roadmap has two dimensions at once:

Both matter. The company gets stronger when they move in the right order.

2. The layer model

The layer model is the vertical logic of the product.

Layer A — Source and record integrity

This is the bottom layer.

It includes: - source preservation - stable return paths - provenance discipline - exact reference handling - record identity - continuity of evidence objects

Without this layer, the whole product becomes soft.

Layer B — Structured object and issue layer

This is where record mass begins turning into structure.

It includes: - object extraction - issue concentration - witness/fact/event structure - contradiction zones - timeline-aware grouping - support for usable record segmentation

This is where the file stops being only mass.

Layer C — Workbench and continuity layer

This is the inhabitable-review layer.

It includes: - workbench movement - re-entry support - handoff preservation - posture tracking - session survivability - continuity over time

This is the layer that reduces reconstruction pain directly.

Layer D — Pressure and prioritization layer

This is the ranked-attention layer.

It includes: - pressure-aware sorting - issue ranking - posture-shift detection - what-changed logic - concentration of reviewer attention - separation of loud versus dangerous

This is where the file stops being merely structured and starts becoming strategically navigable.

Layer E — Strategic pressure support

This is the highest premium layer.

It includes: - counsel-facing pressure support - what deserves attention next - strategic pressure surfacing - ranked issue focus - stronger support for human judgment under file strain

This is Level 9 territory.

It should be earned from below, not faked from above.

3. The phase model

The phase model is the horizontal expansion logic of the company.

Phase 1 — Ontario criminal wedge

This is the first battlefield.

Goal: prove that the engine works in severe Ontario criminal-review files.

What matters here: - sharp wedge - strong pain fit - serious demos - structured pilots - proof of survivability - no fake universality

This phase is about credibility.

Phase 2 — Other Canadian criminal jurisdictions

Goal: expand the same criminal-review engine into nearby jurisdictions where the structural pain is similar.

What matters here: - jurisdiction translation - local legal surface adaptation - preserving the same deep engine - proving that the wedge travels inside Canada

This phase is about controlled portability.

Phase 3 — Selected U.S. criminal jurisdictions

Goal: test the engine in a larger and more varied criminal market.

What matters here: - deeper jurisdiction modeling - stronger translation layer - careful selection of target states - disciplined adaptation rather than naive copying

This phase is about cross-system validation.

Goal: expand from criminal into nearby legal environments where the same structural pain reappears.

Likely targets: - civil monster files - appeals / post-conviction review - regulatory investigations - internal investigations - enforcement review - public-sector oversight matters

This phase is about domain expansion without engine drift.

Goal: bring the engine into adjacent non-legal environments where ugly records still create serious posture, continuity, and prioritization pain.

Likely targets: - insurance investigations - fraud review - public-safety review - compliance casework - oversight review - institutional inquiry - incident reconstruction - complex administrative casework

This phase is about substrate realization.

4. How layers and phases interact

The layers should deepen while the phases widen.

That means:

During early phases, the company should get better vertically before it gets too ambitious horizontal expansionly.

A weak roadmap widens before deepening. A stronger roadmap deepens first, then widens.

In practical terms:

  • Phase 1 should prove Layers A through C strongly
  • Phase 2 should strengthen Layer D while portability improves
  • Phase 3 should stress-test translation plus pressure logic
  • Phase 4 should prove that the same engine survives domain change
  • Phase 5 should confirm that the substrate really does travel beyond law

That is the clean interaction between depth and breadth.

5. What should come earlier

The things that should come earlier are the ones closest to actual survivability:

Why: if the lower structure is weak, higher strategic claims become fake very quickly.

The company should therefore earn its premium story by making the painful file inhabitable first.

6. What should come later

The things that should come later are the ones most likely to be oversold if introduced too early:

  • strategic pressure claims
  • broader jurisdiction expansion
  • civil / investigative expansion
  • non-legal adjacency expansion
  • investor-facing platform language
  • anything that sounds universal before the wedge is fully proven

These are not bad ambitions. They are just later ambitions.

That distinction matters.

7. Commercial roadmap by phase

Phase 1 commercial motion

  • founder-led
  • trust-heavy
  • wedge-first
  • demo + pilot
  • pain-matched positioning

Phase 2 commercial motion

  • still founder-led, but more repeatable
  • stronger documentation
  • more disciplined regional translation
  • clearer early references / proof points

Phase 3 commercial motion

  • more formalized sales narrative
  • more explicit jurisdiction-adaptation language
  • more operational partner conversations

Phase 4 commercial motion

  • domain-specific packaging
  • more than one serious buyer profile
  • stronger platform story without losing wedge discipline

Phase 5 commercial motion

  • engine/substrate narrative becomes more public
  • broader partner / investor story becomes more credible
  • company begins sounding like a severe-record platform rather than only a criminal wedge product

8. Product risks at each stage

Early-stage risk

Sounding broader than the proof.

Middle-stage risk

Confusing portability with effortless translation.

Expansion-stage risk

Losing identity while chasing adjacent markets.

Late-stage risk

Becoming a vague platform story with no clear first principles.

That is why the roadmap needs discipline.

9. The right internal language

Internally, the company should use language like:

  • deepen the layer before widening the phase
  • preserve the engine while translating the surface
  • prove the wedge before expanding the story
  • treat adjacency as structural similarity, not category vanity
  • let premium claims rise from lower-layer proof

That language will keep the roadmap honest.

10. The wrong internal language

Internally, the company should avoid language like:

  • we can sell this everywhere now
  • the engine works, so jurisdiction doesn’t matter
  • Level 9 is the whole story
  • once the criminal wedge works, all domains are basically the same
  • platform first, proof later

That kind of language causes drift.

11. Simple summary lines

If this appendix needs to be explained simply, the cleanest lines are:

SUMMA should deepen before it widens.

Or:

First prove the engine in one painful lane. Then widen into nearby lanes where the same structural pain reappears.

Or:

The roadmap is vertical first, horizontal expansion second.

Or:

Earn the premium layer. Then earn the next jurisdiction. Then earn the next domain.

Those are the right summary lines.

12. Final takeaway

The product roadmap should not be treated as: feature pile first, expansion later.

It should be treated as: layered engine first, wedge proof second, premium depth third, controlled expansion after that.

That is the right roadmap.

It gives the company: - stronger product discipline - cleaner commercial logic - more believable expansion - better investor story - better long-term moat

That is the roadmap SUMMA should follow.