Appendix J — Jurisdiction Expansion Map
This appendix explains how SUMMA should think about jurisdiction expansion.
The key rule is simple:
Not everything in SUMMA is jurisdiction-specific. Not everything in SUMMA is jurisdiction-generic either.
A serious expansion strategy has to separate the layers properly.
That means distinguishing among:
- what is Ontario-specific
- what is criminal-law generic
- what is engine-generic
- what must be translated when moving into another province, state, or legal domain
That is the purpose of this appendix.
1. The three-layer rule
A clean way to think about SUMMA is through three layers.
Layer 1 — Jurisdiction-specific layer
This includes things tied to one legal system’s: - procedure - terminology - disclosure rules - charging documents - court forms - naming conventions - timelines - local doctrinal expectations - forum-specific workflow
This is the layer that changes most when moving from Ontario to another province or from Canada to the United States.
Layer 2 — Criminal-review generic layer
This includes pain and structure that appear across many criminal-file environments: - disclosure burden - mixed-format evidence - witness contradiction - timeline pressure - re-entry pain - handoff pain - issue sprawl - source drift - pressure ranking
This layer is much more portable.
Layer 3 — Engine-generic layer
This includes the deepest architecture: - source-linked review - structured objects - issue concentration - workbench movement - continuity - re-entry support - pressure-aware ranking - serious review survivability
This is the most reusable layer of all.
That is the core expansion logic.
2. What is Ontario-specific
Ontario criminal work includes specific language, procedure, and record expectations.
Examples of Ontario-specific or Canada-specific surface material include: - provincial or Canadian charging-document language - Crown disclosure conventions - local procedural sequencing - court-form expectations - terminology around applications, motions, preliminary steps, and appeal materials - local naming conventions for records and filings - local workflow assumptions about how criminal defence files are assembled and argued
This material matters. It is not superficial.
But it sits higher than the engine.
That means it should be treated as a translation layer, not as the whole product.
3. What is criminal-generic
Much of the actual pain is not uniquely Ontario pain.
Across many criminal systems, severe files still involve: - large records - repeated disclosure - mixed evidence types - witnesses under pressure - contradictions - unstable timelines - hard re-entry - difficult prioritization - weak handoff - fatigue-driven loss of structure
That is why the wedge can travel more than the surface language can.
The criminal review burden is often structurally similar even when the doctrinal wrapper changes.
That is a major strategic strength.
4. What is engine-generic
The deepest parts of SUMMA are not really “Ontario criminal” at all.
They are a general architecture for ugly records:
- preserve source
- reduce structural drift
- turn mass into issues
- support movement through the file
- preserve posture across time
- reduce the cost of return
- help distinguish what is loud from what is dangerous
Those are engine-level promises.
They can survive across: - provinces - states - civil monster files - investigations - compliance review - oversight review - other severe-record environments
That is why the engine can expand.
5. Expansion from Ontario to other Canadian provinces
The first jurisdiction expansion should usually stay inside Canada before going wider.
Why: - some procedural family resemblance remains - criminal-review pain stays highly similar - language and legal culture are closer - the engine can stay the same while the surface translation layer adjusts
What likely changes: - local court workflow assumptions - province-specific terminology or filing habits - localized process expectations - local strategic emphasis in practice
What stays mostly stable: - severe-file pain - disclosure burden - record pressure - source-linked review value - issue concentration - continuity and re-entry value
This makes other Canadian provinces a strong early adjacency.
6. Expansion from Canada to U.S. states
This is a bigger move.
Why: - procedural language changes more - discovery/disclosure culture changes - terminology shifts more sharply - state-specific criminal workflow can differ significantly - court-document expectations change
But even here, the deeper criminal-review burden may still rhyme strongly.
The file can still be: - huge - unstable - mixed-format - contradiction-heavy - expensive to re-enter - hard to prioritize
That means U.S. expansion is plausible, but it requires a stronger translation layer and more deliberate jurisdiction modeling.
The engine may stay. The legal wrapper has to be rebuilt more carefully.
7. Expansion from criminal to civil or investigations
This is not a jurisdiction move in the narrow sense. It is a domain move.
But the same three-layer rule still works.
What changes: - doctrinal labels - record types - procedural expectations - language of hearings, examinations, motions, or productions
What may stay surprisingly stable: - mixed-format burden - source drift - issue concentration needs - chronology pressure - handoff pain - re-entry burden - ranked attention under pressure
That is why domain expansion should be thought of as structured translation, not total reinvention.
8. The translation-layer model
A clean expansion model is this:
Core engine
This should change the least.
Review-domain layer
This adapts for criminal, civil, investigations, oversight, claims, or compliance.
Jurisdiction layer
This adapts for Ontario, another province, a U.S. state, or another procedural environment.
That model matters because it stops the company from confusing: - engine identity with - jurisdiction-specific language
That confusion weakens strategy if left uncorrected.
9. What to avoid
Do not say: the product is already universal.
Do not say: jurisdiction barely matters.
Do not say: the engine is reusable, so legal translation is trivial.
Do not say: Ontario success automatically means instant U.S. success.
Those are weak claims.
The stronger claim is: the engine is portable, but the surface legal and procedural layer still has to be adapted carefully.
That is more believable and more strategic.
10. Best expansion order
The most disciplined expansion order is:
Phase 1
Ontario criminal
Phase 2
Other Canadian criminal jurisdictions
Phase 3
Selected U.S. criminal jurisdictions with strong structural similarity and clear demand
Phase 4
Adjacent severe-review legal domains: civil monster files, investigations, appeals, enforcement, regulatory review
Phase 5
Non-legal severe-record environments
That order keeps the company sharp while still preserving upside.
11. Simple summary lines
If this appendix needs to be explained simply, the cleanest lines are:
The legal wrapper changes by jurisdiction. The review pain often changes less than people think.
Or:
Ontario is the first legal surface. It is not the full limit of the engine.
Or:
The engine can travel farther than the procedural language can.
Or:
Jurisdiction expansion should be treated as careful translation, not careless generalization.
Those are the right summary lines.
12. Final takeaway
SUMMA should not think about expansion as one giant leap from Ontario into everywhere.
It should think in layers:
- preserve the engine
- translate the domain
- adapt the jurisdiction
- keep the wedge logic honest
That is the right expansion discipline.
It makes the company more believable, more portable, and less likely to confuse narrow early success with fake universality.