Skip to content

Appendix I — Engine Generality, Expansion Path, and Adjacency Map

This appendix explains a strategic distinction that matters greatly:

SUMMA should remain narrow in wedge, but broad in substrate.

That means the company should start with a sharp first battlefield — severe criminal-review pain — while recognizing that the engine underneath is more general than the first use case.

That distinction protects two things at once.

It protects focus, because the company does not try to sell to everyone at the beginning.

And it protects long-term upside, because the core engine is not merely a one-case trick for one tiny niche. It is a deeper review architecture for ugly record environments.

That is the starting point of this appendix.

1. Wedge versus engine

The wedge is where the company first wins.

For SUMMA, that wedge is the criminal file that has crossed from ordinary inconvenience into structural review pain: - disclosure-heavy - mixed-format - contradiction-prone - painful to re-enter - difficult to hand off - hard to prioritize honestly

That wedge should stay sharp.

But the engine underneath is broader than that wedge.

The engine is really a system for: - preserving source - structuring issues - holding posture across time - supporting re-entry - handling contradiction and timeline pressure - surfacing where the real pressure appears to live

Those are not exclusively criminal-law problems.

They are severe-record problems.

That is why expansion should be understood as adjacency, not as abandonment of the wedge.

2. What the engine is actually generic at

The most reusable parts of SUMMA are not the criminal labels.

The most reusable parts are:

  • source-linked review
  • structured objects and issue concentration
  • workbench movement
  • continuity and re-entry
  • ranked attention under pressure
  • mixed-format record survivability
  • honest abstraction without severing source return

Those are generic capabilities.

The criminal wedge is simply the first place where those capabilities become most obviously necessary.

That is why the company story should not sound like: we are only a criminal-law specialty app forever.

It should sound more like: we are beginning in the hardest clear lane where the need is already undeniable.

The first legal expansions should stay close to the original pain structure.

That usually means moving into other legal environments where the record becomes large, unstable, contradictory, and hard to inhabit.

The best first legal adjacencies include:

A. Civil litigation with monster records

This includes matters with: - huge productions - multiple witnesses - expert reports - long timelines - contradictory document trails - deposition/transcript-heavy environments

Why it fits: the structure problem is very close to criminal-file pain even if the legal setting differs.

B. Regulatory and enforcement investigations

This includes: - internal investigation - external enforcement response - regulatory document review - second requests - compliance-driven fact reconstruction

Why it fits: these environments are already being described by adjacent vendors as data-heavy, review-heavy, and investigation-centered.

C. Public-sector and government investigations

This includes: - agency investigations - disciplinary files - inspector-general style review - public-corruption or misconduct case review - evidence-heavy administrative matters

Why it fits: the burden often involves mixed evidence, chain-of-custody sensitivity, auditability, and repeated review by multiple stakeholders.

D. Appeals and post-conviction review / post-judgment review

Why it fits: these matters are often posture-heavy, record-heavy, and dependent on preserving source, chronology, contradiction, and issue concentration over long time spans.

The common rule is simple: stay close to severe-review environments first.

A weak strategy says: if the engine is broad, sell it broadly now.

That is the wrong move.

The better strategy is: prove the engine in one painful lane first, then expand into nearby lanes where the same structural pain reappears in a different doctrinal wrapper.

That matters because category language changes across legal domains, but the underlying review pain may stay surprisingly similar.

The company should therefore expand by preserving the engine and translating the surface language.

Criminal today. Adjacent severe legal review tomorrow. Broader record-pressure environments later.

That is the right order.

The engine can also matter outside law.

But again, expansion should be by structural similarity, not by vanity.

The best non-legal adjacencies are not “anything with documents.” They are environments where the real burden is: - mixed record - repeated intake - uncertain posture - source sensitivity - high re-entry cost - pressure-heavy prioritization - handoff and continuity failure

Strong non-legal adjacencies include:

A. Insurance claims and special investigations

Examples: - fraud review - complex casualty files - large claims with mixed evidence - repeated intake over time - witness/account contradiction zones - surveillance / media / report interaction

Why it fits: the problem often becomes structural review under pressure rather than simple claim storage.

B. Corporate investigations and compliance review

Examples: - internal misconduct review - whistleblower matters - workplace investigations - financial/compliance incident review - data-heavy internal inquiries

Why it fits: these environments depend heavily on defensible source handling, chronology, issue concentration, and honest posture preservation.

C. Public-safety / incident review / oversight review review

Examples: - major incident review - civilian oversight review review - misconduct or use-of-force review - mixed video/audio/report environments - multi-stakeholder evidentiary handoff

Why it fits: this is one of the clearest non-legal-but-record-heavy lanes because evidence burden, chain of custody, and pressure-aware review are central.

D. Forensic and investigative review environments

Examples: - corporate security investigations - intelligence-style review - private investigative case assembly - multi-source incident reconstruction

Why it fits: the engine’s source-linked, issue-aware, posture-preserving behavior is naturally useful here.

E. Complex knowledge and casework environments outside formal law

Examples: - ombuds investigations - grievance or disciplinary review - institutional inquiry - serious audit casework - mixed-record administrative adjudication

Why it fits: the record may not be a court file, but the structural burden is similar.

6. What should not be called an adjacency too early

The company should resist fake breadth.

Weak expansion language would include: - “all enterprise knowledge work” - “all document-heavy industries” - “every workflow with AI” - “all verticals”

That is too vague.

The real adjacency test should be:

Does this environment suffer from the same structural review pain: source drift, issue sprawl, re-entry burden, posture loss, and difficulty ranking what matters inside an ugly record?

If yes, it may be a real adjacency. If not, it is probably just noise.

7. The expansion model

The cleanest model is:

Phase 1 — Criminal wedge

Prove the engine where pain is already undeniable.

Expand into nearby severe-review legal environments: civil monster files, investigations, enforcement, appeals.

Expand into claims, investigations, oversight review, compliance, and incident-review systems.

Phase 4 — Broader platform identity

Only after the company has earned it should it speak as a broader severe-record review platform.

That sequencing matters. It keeps the company from becoming diffuse before it has earned its broader story.

8. What must stay constant across expansion

Whatever the surface market becomes, the company should keep the same deep promises:

  • preserve source
  • reduce structural drift
  • make the record more inhabitable
  • improve continuity and re-entry
  • surface issue pressure honestly
  • support serious human judgment rather than replacing it

That is the true engine identity.

If those promises survive across domains, the expansion is real. If they do not, the company is just stretching language.

9. Why this creates strategic strength

A wedge-first company with a reusable deep engine has a better strategic profile than either of these extremes:

  • a tiny narrow company with no adjacency
  • a broad vague company with no clear wedge

SUMMA should aim for the middle: sharp first lane, expandable underlying architecture.

That gives the company: - clearer early positioning - better product discipline - stronger future optionality - more believable moat logic - a cleaner investor and partner story

That is the right structural ambition.

10. Simple summary lines

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

SUMMA begins in criminal review, but the engine underneath is a broader system for severe-record environments.

Or:

The wedge is criminal. The substrate is source-linked, issue-aware, pressure-aware review.

Or:

SUMMA should expand not by chasing industries, but by following the recurrence of the same structural review pain into adjacent domains.

Those are the cleanest lines.

11. Final takeaway

The future of SUMMA should not be framed as: one narrow criminal product forever.

And it should not be framed as: a generic platform for everything.

It should be framed as: a wedge-first company whose underlying engine is reusable across legal and non-legal environments wherever ugly records become difficult to inhabit, difficult to preserve honestly, and difficult to prioritize under pressure.

That is the deepest long-term expansion story.