Skip to content

Appendix L — Naming, Packaging, and Product-Line Strategy

This appendix explains how SUMMA should name itself as the product grows.

That matters more than it sounds.

A weak naming system can make a serious company feel messy, vague, or fake. A strong naming system helps buyers, partners, investors, and internal operators understand what the company is building and how the parts fit together.

SUMMA is now reaching the point where that distinction matters.

The company is no longer just one narrow manual about one narrow product story. It now has: - a wedge - an engine - a premium ladder - an expansion path - multiple possible domains - multiple possible future product lines

That means naming discipline is now part of strategy.

1. The main naming rule

The cleanest naming rule is:

SUMMA is the company and engine family.
SUMMA_CRIM is the first wedge product.

That is the right starting point.

Why: - it preserves the broader company identity - it lets the first wedge stay specific - it leaves room for later legal and non-legal variants - it stops the company from sounding trapped inside one domain forever

That distinction should stay stable.

2. What SUMMA should mean

SUMMA should mean the broader system identity.

It should represent: - the company - the engine family - the long-term architecture - the broader severe-record review vision - the reusable substrate underneath the first wedge

In plain terms:

SUMMA is the bigger umbrella.

That makes it the right name for: - the company story - investor narrative - platform narrative - engine narrative - broader roadmap narrative

It should not be reduced too early to meaning only one niche wedge.

3. What SUMMA_CRIM should mean

SUMMA_CRIM should mean the criminal-review wedge product.

That means: - first battlefield - first market fit - first sharp product identity - first commercial proof zone - first serious user group

This is important because buyers should not be forced to decode whether the company is: - criminal only - legal broadly - platform broadly - or something else entirely

SUMMA_CRIM makes the first lane legible.

That is a strength, not a limitation.

4. Why this naming split matters

Without a naming split, two bad things happen.

Bad outcome 1

The company sounds broader than the product proof.

Example: if everything is just called SUMMA too early, buyers may think the company is already a broad universal platform when it has not yet earned that story.

Bad outcome 2

The company sounds narrower than the engine.

Example: if everything is named only as criminal forever, the broader engine and expansion story become harder to explain later.

The SUMMA / SUMMA_CRIM split avoids both mistakes.

5. Product-line logic

The cleanest future logic is this:

Company level

SUMMA

First wedge product

SUMMA_CRIM

Future possible wedge or domain products

  • SUMMA_CIV
  • SUMMA_INV
  • SUMMA_REG
  • SUMMA_OVERSIGHT
  • SUMMA_CLAIMS
  • SUMMA_PUBLICSAFE
  • other carefully chosen domain names later

These are examples, not final commitments.

The point is the structure: broad umbrella above, wedge/domain products below.

That is much cleaner than inventing unrelated names for every adjacent lane.

6. Module naming inside a product

Inside SUMMA_CRIM, the company should not name every useful thing like a separate mini-startup.

That creates clutter.

The internal modules should usually stay under the product umbrella and be described by function, for example:

  • source layer
  • issue layer
  • workbench
  • pressure layer
  • strategic pressure support
  • casecards
  • exports
  • comparison / diff layer
  • continuity layer

These can have internal names, but externally they should not be allowed to become a zoo.

That discipline matters.

7. Packaging logic

Naming and packaging should match.

The product-line naming should describe what world the product is for. The package naming should describe what level of capability the buyer is getting.

That means:

Product line answers:

What domain is this built for?

Package answers:

How deep into the engine / premium ladder is this buyer getting?

Those are different questions.

A weak strategy confuses them. A stronger strategy keeps them separate.

8. Example of clean product vs package naming

Product line

SUMMA_CRIM

Packages inside it

  • Pilot
  • Core Review
  • Strategic / Premium
  • Enterprise / Team
  • other later variations if truly needed

That is clean because: - the product line says what lane this is for - the package says how much of it the buyer gets

The naming remains understandable.

9. What to avoid

Avoid these naming mistakes:

  • giving every feature a dramatic standalone brand
  • calling everything just SUMMA when the buyer needs wedge clarity
  • creating too many sub-brands too early
  • naming packages in a way that hides what they actually do
  • using futuristic names that sound clever but explain nothing
  • mixing company naming, product naming, and feature naming into one blur

That kind of naming drift weakens trust.

10. Naming rules for future expansion

As the company expands, it should follow these rules:

Rule 1

Keep SUMMA as the stable umbrella.

Rule 2

Use domain-specific product names only when the domain is real enough to justify them.

Rule 3

Do not launch a new named line before the wedge logic is proven.

Rule 4

Keep internal module language more functional than theatrical.

Rule 5

Let naming follow structure, not excitement.

These rules will matter more later than they do now.

11. How to explain the naming simply

If someone asks how the naming works, the simplest explanation is:

SUMMA is the company and engine family. SUMMA_CRIM is the first criminal-review product built on that engine.

Or:

SUMMA is the umbrella. SUMMA_CRIM is the first sharp wedge beneath it.

Or:

The company name is broader than the first product because the engine is broader than the first market.

Those are the cleanest lines.

12. Why naming affects moat

This is not just branding polish.

Good naming protects: - product clarity - wedge clarity - expansion credibility - investor understanding - internal discipline

Bad naming makes the company look either: - smaller than it is or - broader than it has earned

Neither is good.

That is why naming is part of moat logic too.

13. Final takeaway

The clean product-line strategy is:

  • SUMMA = company / umbrella / engine family
  • SUMMA_CRIM = first wedge product
  • future domain products = carefully added beneath the umbrella only when the expansion is real
  • package names = capability depth, not domain identity
  • module names = functional and disciplined, not chaotic

That is the naming system most likely to keep the company clear as it grows.