03 — Master Terminology Dictionary
This chapter is the canonical internal lexicon for the SUMMA environment.
It is intentionally extensive.
The purpose of this chapter is not to give the reader a few friendly definitions and move on. The purpose is to give the reader a durable vocabulary strong enough to understand the company, the product, the legal-review environment, the repository, the engineering workflow, and the deeper premium architecture without constantly guessing what words mean.
A serious legal-tech company cannot operate on fuzzy vocabulary. If the terms are weak, the thinking becomes weak. If the thinking becomes weak, the product becomes shallow, the training becomes brittle, and the internal standards become inconsistent.
This chapter is therefore written as a true internal lexicon.
It is designed for readers who may have little prior background, but who are fully capable of learning serious language if it is explained properly. It assumes intelligence. It does not assume prior legal training. It does not assume prior software-company experience. It does not assume prior familiarity with criminal procedure, Git, GitHub, repositories, or internal product architecture.
Each entry in this chapter should aim to provide:
- the term
- a formal definition
- a plain explanation
- why the term matters
- where it appears in the SUMMA environment
- where useful, a distinction from similar terms
This chapter is organized into the following major sections:
3A — Product and Review Terms
Terms used to describe the product, its functions, and the review behavior it supports.
3B — Criminal-Law and Procedure Terms
Terms drawn from criminal process, hearings, motions, trial stages, appellate logic, and lawyer workflow.
3C — Evidence, Record, and Document Terms
Terms used to describe records, exhibits, productions, evidentiary material, file structure, and review burden.
3D — Technical, Repository, Git, GitHub, and Deployment Terms
Terms used in the engineering and documentation environment.
3E — Internal SUMMA Architecture and Workflow Terms
Terms used internally to describe phases, layers, premium ladder components, workbench concepts, training structures, and internal system language.
3F — Latin and Formal Legal Expressions
Common Latin and formal legal expressions that appear in legal writing, legal discussion, or internal explanation of legal process.
3G — Cross-Reference Index
A later section used to map similar terms, overloaded terms, ambiguous terms, and internal synonym relationships.
The reader should treat this chapter as a working reference, not a decorative appendix.
3A — Product and Review Terms
[To be expanded in full.]
3B — Criminal-Law and Procedure Terms
[To be expanded in full.]
3C — Evidence, Record, and Document Terms
[To be expanded in full.]
3D — Technical, Repository, Git, GitHub, and Deployment Terms
[To be expanded in full.]
3E — Internal SUMMA Architecture and Workflow Terms
[To be expanded in full.]
3F — Latin and Formal Legal Expressions
[To be expanded in full.]
3G — Cross-Reference Index
[To be expanded in full.]
3B — Criminal-Law and Procedure Terms
Introduction to this section
This section gathers terms from criminal process, criminal procedure, hearings, trial stages, and related legal workflow. It is written for readers who may have no formal legal education but who need to become comfortable with serious legal language inside a criminal-review environment.
The goal is not to turn the reader into a lawyer. The goal is to ensure that the reader can follow what lawyers are saying, understand what stage of the process a file may be in, recognize what kinds of procedural events matter, and understand why certain legal terms carry more weight than ordinary English might suggest.
Many of these terms are terms of art. That means they may sound familiar in ordinary language while carrying a more precise meaning in law.
Core actors and roles
accused
Definition:
The accused is the person formally alleged to have committed a criminal offence.
Plain explanation:
The accused is the person facing the charge.
Why it matters:
This is one of the most basic role words in the entire criminal system. The reader must understand it immediately and precisely.
Where it appears:
Throughout criminal workflow, procedural material, court records, and case simulation.
Distinction:
The accused is not the same thing as a witness, complainant, or suspect in ordinary conversation. Once formal charges exist, the accused is the charged person in the proceeding.
co-accused
Definition:
A co-accused is another accused person involved in the same proceeding or related matter.
Plain explanation:
A co-accused is one of multiple charged people connected to the same case structure.
Why it matters:
Multi-accused files are structurally harder. Role clarity, evidence separation, and thread separation become much more important.
Where it appears:
Multi-thread complexity, party liability, conspiracy, and procedural case structure.
complainant
Definition:
The complainant is the person said to be the victim or target of the alleged offence, particularly in certain criminal contexts.
Plain explanation:
The complainant is the person whose complaint or victimization is central to the allegation.
Why it matters:
The term appears frequently in criminal proceedings and may shape how records, statements, and credibility issues are framed.
Where it appears:
Witness statements, procedural records, trial material, and case summaries.
Crown
Definition:
The Crown is the prosecuting side in a criminal case, acting on behalf of the state.
Plain explanation:
The Crown is the prosecution.
Why it matters:
Readers must understand that the Crown and the defence are reading the same record from different positions and for different purposes.
Where it appears:
Every criminal workflow chapter, procedural stage, and same-record-different-sides discussion.
Crown counsel
Definition:
Crown counsel is the lawyer representing the prosecution.
Plain explanation:
Crown counsel is the prosecutor handling the case.
Why it matters:
The reader must distinguish between “the Crown” as the prosecuting side generally and Crown counsel as the lawyer or lawyers acting for that side.
Where it appears:
Procedural records, motions, hearings, resolution discussions, and trial workflow.
defence counsel
Definition:
Defence counsel is the lawyer acting for the accused.
Plain explanation:
Defence counsel is the accused person's lawyer.
Why it matters:
SUMMA is especially interested in defence-side review pain, so this role is central to the product worldview.
Where it appears:
Throughout the manual, especially workflow, review burden, and user-reality sections.
duty counsel
Definition:
Duty counsel is a lawyer available to provide limited legal assistance to unrepresented persons at court.
Plain explanation:
Duty counsel is not usually the full long-term lawyer on the file. It is immediate court-based legal assistance.
Why it matters:
This role often appears at early procedural stages and can affect how a reader understands first appearances and early hearings.
Where it appears:
Early criminal process, bail settings, and court workflow.
surety
Definition:
A surety is a person who promises to supervise or support the accused’s release under bail conditions and may pledge a sum of money or responsibility.
Plain explanation:
A surety helps guarantee that the accused will follow release conditions.
Why it matters:
Sureties often appear in bail hearings and are important in understanding release structure.
Where it appears:
Bail proceedings, release orders, and criminal-process records.
witness
Definition:
A witness is a person who gives evidence, whether through testimony or, in some contexts, recorded statements that later become relevant.
Plain explanation:
A witness is someone whose account or evidence forms part of the record.
Why it matters:
Witness handling is one of the major drivers of pressure, contradiction, credibility, and review complexity.
Where it appears:
Statements, transcripts, trial stages, credibility analysis, and issue formation.
justice of the peace
Definition:
A justice of the peace is a judicial officer who may handle certain early criminal-process matters, including bail and other preliminary proceedings.
Plain explanation:
A justice of the peace is not the same thing as the trial judge, but can make important early-stage decisions.
Why it matters:
Readers will often see this role in early criminal workflow and should not confuse it with later-stage trial or appellate roles.
Where it appears:
Bail, first appearance, warrants, and some early procedural records.
trial judge
Definition:
The trial judge is the judge responsible for the adjudication of the case at trial.
Plain explanation:
The trial judge rules on evidence, procedure, law, and — depending on the mode of trial — may also decide the facts.
Why it matters:
A great many procedural events, evidentiary rulings, and strategic decisions revolve around what the trial judge permits or rejects.
Where it appears:
Trial workflow, voir dires, motions, evidentiary rulings, and appeals.
Case initiation and charging
charge
Definition:
A charge is the formal allegation that a person committed a criminal offence.
Plain explanation:
A charge is the legal accusation itself.
Why it matters:
Everything in the case record is ultimately tied to one or more charges.
Where it appears:
Informations, indictments, court records, bail, trial, and sentencing.
count
Definition:
A count is an individual allegation or offence listed within a charging document.
Plain explanation:
A case may contain more than one count. Each count is one legal unit of accusation.
Why it matters:
Some files become confusing because different pieces of evidence relate differently to different counts.
Where it appears:
Informations, indictments, verdicts, and sentencing materials.
information
Definition:
An information is a formal charging document used to initiate criminal proceedings in many contexts.
Plain explanation:
The information is one of the documents that formally sets the criminal case in motion.
Why it matters:
The information is a core procedural document. A reviewer should know what it is and why it matters.
Where it appears:
Early criminal process, court records, and procedural file structure.
indictment
Definition:
An indictment is a formal charging document used in indictable matters or later procedural stages.
Plain explanation:
An indictment is a more formal charge document associated with more serious procedure.
Why it matters:
Readers must know the difference between ordinary references to charges and the specific document structure of an indictment.
Where it appears:
Serious criminal matters, trial records, and appellate materials.
appearance notice
Definition:
An appearance notice is a document requiring a person to attend court rather than being held in custody immediately.
Plain explanation:
It is a formal notice telling the person they must appear in court.
Why it matters:
This is part of understanding how a case begins procedurally.
Where it appears:
Early criminal process and case-initiation records.
summons
Definition:
A summons is a formal order requiring a person to attend court.
Plain explanation:
A summons is a command to appear.
Why it matters:
It is one of the procedural tools by which a matter formally moves into court.
Where it appears:
Charging and attendance procedures.
undertaking
Definition:
An undertaking is a written promise to comply with specified conditions.
Plain explanation:
It is a formal promise tied to release or process conditions.
Why it matters:
Undertakings matter in early criminal process and affect the structure of release and obligations.
Where it appears:
Release-related records and early court process.
release order
Definition:
A release order is the formal order governing the accused’s release and its conditions.
Plain explanation:
It sets the terms on which the accused is out of custody.
Why it matters:
Release structure can become important to later workflow, strategy, and procedural understanding.
Where it appears:
Bail and release records.
recognizance
Definition:
A recognizance is a formal binding promise, often backed by conditions and sometimes money, to comply with release terms.
Plain explanation:
It is a structured legal promise connected to release.
Why it matters:
It appears frequently in bail language and should not be treated as a casual synonym for “promise.”
Where it appears:
Bail and release proceedings.
detention order
Definition:
A detention order is a judicial order that the accused remain in custody.
Plain explanation:
The accused is not released.
Why it matters:
This is a major procedural outcome and affects the posture and urgency of the case.
Where it appears:
Bail and detention proceedings.
first appearance
Definition:
The first appearance is the accused’s first formal appearance before the court in the matter.
Plain explanation:
It is the beginning of the case’s visible court life.
Why it matters:
This stage often sets the initial procedural rhythm of the file.
Where it appears:
Early process and court scheduling.
remand
Definition:
A remand is the postponement or adjournment of the matter to a later date.
Plain explanation:
The case is pushed forward to another court date.
Why it matters:
Many criminal files move through repeated remands, and this affects continuity, pressure, and timing.
Where it appears:
Court records, scheduling, early procedural history.
election
Definition:
An election is the accused’s procedural choice, where available, regarding mode of trial or related procedural route.
Plain explanation:
It is a formal choice about how the case will proceed.
Why it matters:
Mode of proceeding can affect the entire future shape of the case.
Where it appears:
Serious criminal matters and procedural planning.
direct indictment
Definition:
A direct indictment is a procedural route by which the Crown proceeds by indictment without the usual preliminary step.
Plain explanation:
It is a significant procedural move that changes the route of the case.
Why it matters:
It can materially affect how the reader understands the case structure and procedural path.
Where it appears:
Serious criminal procedure and case-shape discussions.
Pre-trial process and hearings
disclosure
Definition:
Disclosure is the body of material the Crown is obliged to provide to the defence in relation to the case.
Plain explanation:
Disclosure is the evidentiary and related record the defence must review.
Why it matters:
Disclosure is one of the central realities that SUMMA is built to help handle.
Where it appears:
Throughout the manual.
disclosure obligation
Definition:
The disclosure obligation is the legal obligation of the prosecution to provide relevant material to the defence.
Plain explanation:
The Crown does not simply choose whether to share the file. There is a legal duty.
Why it matters:
This duty is foundational to criminal-file review and explains why disclosure arrives, evolves, and matters so much.
Where it appears:
Criminal workflow, Stinchcombe discussions, and file-pressure chapters.
Stinchcombe disclosure
Definition:
Stinchcombe disclosure refers to the disclosure principles associated with R. v. Stinchcombe, the leading case on prosecutorial disclosure obligations in Canada.
Plain explanation:
This is one of the main legal foundations for why the Crown must disclose relevant material.
Why it matters:
A serious criminal-review product cannot be understood properly without understanding the disclosure world shaped by Stinchcombe.
Where it appears:
Disclosure discussions, legal workflow, and training on criminal process.
application
Definition:
An application is a formal request to the court for a ruling or order.
Plain explanation:
A party asks the court to decide something.
Why it matters:
Many important legal battles occur through applications rather than through the full trial itself.
Where it appears:
Pre-trial and trial procedure, Charter issues, evidentiary disputes.
motion
Definition:
A motion is a procedural request asking the court to make a ruling or order on a particular issue.
Plain explanation:
A motion is a formal procedural ask.
Why it matters:
Readers need to understand that much of legal process happens through targeted procedural requests, not just trial testimony.
Where it appears:
Procedure, evidentiary disputes, Charter matters, and workflow chapters.
preliminary inquiry
Definition:
A preliminary inquiry is a procedural hearing in certain cases used to test whether there is sufficient evidence to commit the accused to trial.
Plain explanation:
It is not the trial itself. It is an earlier filtering or testing stage.
Why it matters:
Its presence changes how a case develops and what records may exist.
Where it appears:
Criminal workflow and serious-case procedural structure.
Charter
Definition:
The Charter usually refers to the Canadian Charter of Rights and Freedoms.
Plain explanation:
It is the constitutional rights framework that often matters in criminal litigation.
Why it matters:
Many criminal applications, evidentiary disputes, and major strategic issues arise through Charter arguments.
Where it appears:
Charter applications, voir dires, motions, and advanced review chapters.
Charter application
Definition:
A Charter application is an application arguing that Charter rights were breached and that legal consequences should follow.
Plain explanation:
A party says a constitutional right was violated and asks the court to do something about it.
Why it matters:
Charter issues can radically change posture and are often among the most consequential parts of criminal review.
Where it appears:
Applications, hearings, motions, trial preparation, and case strategy.
voir dire
Definition:
A voir dire is a trial-within-a-trial or focused evidentiary hearing used to determine a specific legal question, often about admissibility or rights.
Plain explanation:
A voir dire is a separate courtroom process used to decide whether some evidence or legal issue should be treated a certain way before or during trial.
Why it matters:
This is one of the most important criminal-procedure terms in the manual. It is a major place where file review, legal strategy, rights arguments, and evidentiary structure converge.
Where it appears:
Motions, Charter issues, admissibility disputes, trial workflow, and advanced review.
Formal note:
The term is French in origin and remains standard legal vocabulary.
admissibility
Definition:
Admissibility is the question whether evidence may be received and used by the court.
Plain explanation:
Not every piece of evidence can simply be used because it exists.
Why it matters:
A large amount of criminal procedure turns on whether evidence is admissible.
Where it appears:
Voir dires, Charter applications, evidentiary rulings, trial and appeal.
exclusion
Definition:
Exclusion is the court’s refusal to admit certain evidence or its decision that evidence should not be used.
Plain explanation:
Evidence may be kept out.
Why it matters:
Exclusion can reshape the case dramatically.
Where it appears:
Charter litigation, evidentiary rulings, and trial-preparation logic.
abuse of process
Definition:
Abuse of process refers to proceedings or conduct so unfair or improper that the court may intervene to protect the integrity of the justice system.
Plain explanation:
This is a serious claim that something has gone wrong in a way the court cannot accept as normal.
Why it matters:
It is a high-level procedural concept with major strategic consequences.
Where it appears:
Applications, Charter-adjacent arguments, serious procedural disputes.
severance
Definition:
Severance is the procedural separation of charges, counts, accused persons, or issues that would otherwise be heard together.
Plain explanation:
Instead of everything being tried or handled in one combined structure, the court separates part of the case.
Why it matters:
Severance can radically change how a case is organized, reviewed, and argued.
Where it appears:
Multi-accused cases, multi-count cases, applications, and trial-management decisions.
publication ban
Definition:
A publication ban is a court order restricting what may be publicly reported or published about certain aspects of the case.
Plain explanation:
Some parts of the case may not be publicly reported in the ordinary way.
Why it matters:
Publication bans affect how information may be discussed, circulated, and handled.
Where it appears:
Pre-trial proceedings, trial rulings, victim-related matters, and sensitive evidentiary hearings.
in camera
Definition:
“In camera” refers to proceedings held privately rather than in open court.
Plain explanation:
Part of the hearing happens behind closed doors or outside the normal public setting.
Why it matters:
Readers need to understand that not every procedural event happens in fully public view.
Where it appears:
Sensitive hearings, protected materials, publication-ban matters, and some procedural applications.
ex parte
Definition:
“Ex parte” refers to a proceeding or request made by one side without the other side being present or heard at that moment.
Plain explanation:
One side goes to the court alone for a limited purpose.
Why it matters:
This is a formal term of art and should not be confused with ordinary unfairness. Some ex parte steps are legally recognized procedural mechanisms.
Where it appears:
Certain applications, urgent requests, and warrant-related contexts.
arraignment
Definition:
Arraignment is the formal stage at which the accused is called upon to answer to the charge.
Plain explanation:
This is the point where the charge is formally put and the plea is taken.
Why it matters:
It is one of the basic structural markers in criminal procedure.
Where it appears:
Trial process and formal court records.
plea
Definition:
A plea is the accused’s formal response to the charge.
Plain explanation:
The plea states how the accused answers the accusation.
Why it matters:
The plea determines the procedural route forward.
Where it appears:
Arraignment, resolution, trial, and sentencing process.
guilty plea
Definition:
A guilty plea is a formal admission of guilt to the charge or count.
Plain explanation:
The accused accepts criminal responsibility for the offence as pleaded.
Why it matters:
A guilty plea changes the posture of the case dramatically and moves the matter away from contested trial.
Where it appears:
Resolution process, plea discussions, and sentencing workflow.
not guilty plea
Definition:
A not guilty plea is the accused’s formal denial of criminal guilt.
Plain explanation:
The case remains contested and moves toward trial or other procedural litigation.
Why it matters:
This is the usual route into a contested evidentiary and procedural file.
Where it appears:
Arraignment, trial preparation, and case progression.
agreed statement of facts
Definition:
An agreed statement of facts is a written statement of facts accepted by the parties for use in the proceeding.
Plain explanation:
Instead of proving every fact through live evidence, some facts are formally agreed.
Why it matters:
Agreed facts can simplify parts of the record while still leaving other issues contested.
Where it appears:
Resolution, pleas, sentencing, and some focused proceedings.
opening
Definition:
An opening is the initial statement by counsel outlining what the case is expected to show.
Plain explanation:
It is the front-end roadmap of the party’s case theory.
Why it matters:
Openings help frame how the record is being organized and understood.
Where it appears:
Trial process and narrative-pressure discussions.
examination-in-chief
Definition:
Examination-in-chief is the questioning of a witness by the party who called that witness.
Plain explanation:
This is the witness’s own side asking the first set of substantive questions.
Why it matters:
It is one of the basic structures of trial evidence.
Where it appears:
Trial process, witness handling, and transcript review.
direct examination
Definition:
Direct examination is another term for examination-in-chief.
Plain explanation:
It means the same basic stage: the witness is questioned by the side that called them.
Why it matters:
Readers may see both expressions and should know they refer to the same concept.
Where it appears:
Trial discussions, training materials, and general legal vocabulary.
cross-examination
Definition:
Cross-examination is the questioning of a witness by the opposing party.
Plain explanation:
This is where the other side tests, challenges, narrows, or weakens the witness’s account.
Why it matters:
Cross-examination is one of the central engines of pressure in trial work.
Where it appears:
Trial chapters, credibility discussions, witness-pressure analysis, and transcripts.
re-examination
Definition:
Re-examination is the follow-up questioning of a witness by the party who first called the witness, usually after cross-examination.
Plain explanation:
It is a limited chance to clarify issues raised in cross.
Why it matters:
Readers should understand the sequence of witness examination stages.
Where it appears:
Trial process and transcript review.
impeachment
Definition:
Impeachment is the process of attacking or undermining the credibility of a witness.
Plain explanation:
It means trying to show that the witness should not be believed fully, or should be believed less than they appear.
Why it matters:
A large amount of criminal pressure can develop through impeachment logic.
Where it appears:
Cross-examination, credibility analysis, contradiction review, and strategy.
corroboration
Definition:
Corroboration is support given to one piece of evidence by another independent or reinforcing piece of evidence.
Plain explanation:
Something else in the record backs it up.
Why it matters:
Corroboration often affects confidence, pressure, and case theory.
Where it appears:
Trial reasoning, issue bundles, witness assessment, and appellate review.
hearsay
Definition:
Hearsay is an out-of-court statement offered to prove the truth of its contents, subject to complex rules and exceptions.
Plain explanation:
It is evidence of what someone said outside court, used for the truth of what they said.
Why it matters:
Hearsay is one of the foundational evidence concepts and often drives admissibility litigation.
Where it appears:
Voir dires, evidentiary rulings, trial objections, and appellate analysis.
credibility
Definition:
Credibility is the degree to which a witness is believed.
Plain explanation:
Credibility asks: is this person believable?
Why it matters:
Many files turn on credibility, and a large amount of review pressure is really credibility pressure.
Where it appears:
Witness analysis, trial reasoning, contradictions, omissions, and appellate review.
reliability
Definition:
Reliability is the degree to which evidence can be depended on as accurate or trustworthy.
Plain explanation:
Reliability asks: can this evidence be relied on?
Why it matters:
A witness may appear sincere yet still be unreliable. Credibility and reliability are related but not identical.
Where it appears:
Witness analysis, hearsay disputes, expert evidence, and appellate arguments.
voluntariness
Definition:
Voluntariness is the legal requirement that certain statements, especially confessions, be made freely and not through improper pressure or inducement.
Plain explanation:
The law may ask whether the statement was truly made voluntarily.
Why it matters:
Voluntariness often becomes the subject of a voir dire and can determine whether evidence is admissible.
Where it appears:
Confession litigation, Charter-related arguments, and evidentiary rulings.
confession
Definition:
A confession is a statement by the accused acknowledging guilt or incriminating involvement, subject to legal rules about admissibility.
Plain explanation:
It is an incriminating statement by the accused, but the fact that it exists does not automatically settle whether it can be used.
Why it matters:
Confessions can be central, but they are also legally sensitive.
Where it appears:
Police interviews, voir dires, voluntariness disputes, and trial records.
admission
Definition:
An admission is a statement or acceptance of fact that may be used evidentially.
Plain explanation:
An admission is not always a full confession. It may be a smaller acknowledgment that still matters.
Why it matters:
Admissions can become important anchors inside a file even when they do not amount to a complete confession.
Where it appears:
Statements, interviews, agreed facts, and evidentiary arguments.
similar-fact evidence
Definition:
Similar-fact evidence is evidence of other conduct or acts used to support an inference in the case, subject to strict legal limits.
Plain explanation:
It is evidence that says, in effect, “this other conduct is relevant because it resembles what is alleged here.”
Why it matters:
This is often highly contested evidence with significant prejudicial risk.
Where it appears:
Applications, evidentiary rulings, trial strategy, and appeals.
circumstantial evidence
Definition:
Circumstantial evidence is evidence from which a fact is inferred rather than directly observed.
Plain explanation:
It does not show the fact directly; it points toward it indirectly.
Why it matters:
Many serious cases depend heavily on circumstantial reasoning.
Where it appears:
Trial theory, evidence review, and appellate analysis.
trier of fact
Definition:
The trier of fact is the person or body responsible for deciding the facts of the case.
Plain explanation:
This is the decision-maker on the factual record.
Why it matters:
The way evidence is presented and argued often depends on who is deciding the facts.
Where it appears:
Trial procedure, evidentiary reasoning, and appellate review.
burden of proof
Definition:
The burden of proof is the obligation to prove the case to the required legal standard.
Plain explanation:
In criminal law, the prosecution carries the burden of proving guilt.
Why it matters:
This is one of the most basic structural ideas in criminal law.
Where it appears:
Trial reasoning, jury instructions, appellate review, and core legal education.
evidentiary burden
Definition:
An evidentiary burden is the burden of putting enough evidence into play to make an issue live for legal decision.
Plain explanation:
It is not always the full burden of proving the case. Sometimes it is the burden of raising the issue properly in the first place.
Why it matters:
Readers need to distinguish between proving everything and producing enough evidence to trigger legal analysis of a particular issue.
Where it appears:
Applications, defences, evidentiary arguments, and trial structure.
reasonable doubt
Definition:
Reasonable doubt is the high legal standard that protects the accused from conviction unless the case is proven to the required criminal standard.
Plain explanation:
The court cannot convict simply because guilt seems likely or suspicious. The doubt must be overcome to the criminal standard.
Why it matters:
This is one of the foundational concepts of criminal adjudication.
Where it appears:
Trial judgments, jury instructions, appellate review, and basic criminal-law education.
presumption of innocence
Definition:
The presumption of innocence is the principle that the accused is presumed innocent unless proven guilty according to law.
Plain explanation:
The case begins with innocence, not guilt.
Why it matters:
This principle shapes the whole structure of criminal proof and criminal fairness.
Where it appears:
Core criminal-law education, Charter analysis, trial process, and appellate reasoning.
sentencing
Definition:
Sentencing is the stage at which punishment or legal consequences are determined after conviction or a guilty plea.
Plain explanation:
Once guilt is established, sentencing determines what follows.
Why it matters:
Sentencing is a major stage with its own evidence, submissions, and legal standards.
Where it appears:
Post-conviction records, agreed facts, reports, submissions, and appeals.
appeal
Definition:
An appeal is a request for a higher court to review a decision of a lower court.
Plain explanation:
The case is taken up to a higher level to challenge part of what happened below.
Why it matters:
Appeals create a new layer of record logic and often depend heavily on transcript, rulings, and preserved issues.
Where it appears:
Appellate records, factums, standard-of-review analysis, and later-stage workflow.
leave to appeal
Definition:
Leave to appeal is permission required in some circumstances before an appeal may proceed.
Plain explanation:
Not every appeal can simply be launched automatically. Sometimes permission must first be granted.
Why it matters:
This affects how appellate strategy and procedure are understood.
Where it appears:
Appellate process and procedural law.
standard of review
Definition:
The standard of review is the legal framework governing how deferentially or strictly an appellate court examines the lower decision.
Plain explanation:
It tells the appeal court how hard it should push on the decision below.
Why it matters:
A reader cannot understand appeals properly without understanding that not every lower-court error is reviewed the same way.
Where it appears:
Appeals, factums, appellate judgments, and higher-order legal analysis.
factum
Definition:
A factum is the formal written argument filed on appeal or in certain other proceedings.
Plain explanation:
It is the structured written case a party presents to the appeal court.
Why it matters:
Factums are central appellate documents and important examples of highly structured legal reasoning.
Where it appears:
Appeals and appellate records.
fresh evidence
Definition:
Fresh evidence is evidence sought to be introduced on appeal that was not part of the original trial record, subject to legal tests.
Plain explanation:
It is new evidence offered later, but it is not automatically accepted.
Why it matters:
Fresh-evidence motions can become significant in appellate litigation.
Where it appears:
Appeal records and appellate applications.
order
Definition:
An order is a formal direction or ruling made by the court.
Plain explanation:
It is the court’s operative command or determination.
Why it matters:
Orders are what actually structure procedure, obligations, and legal consequences.
Where it appears:
Throughout the life of a case.
judgment
Definition:
A judgment is the court’s decision in the matter or on a particular issue.
Plain explanation:
The judgment is the court’s formal decision.
Why it matters:
It is one of the core outputs of adjudication and a key object of review on appeal.
Where it appears:
Trial, motions, applications, and appeals.
reasons for judgment
Definition:
Reasons for judgment are the court’s explanation of why it reached its decision.
Plain explanation:
This is the reasoning, not just the outcome.
Why it matters:
Reasons are essential to understanding how the case was decided and what may later be attacked or defended on appeal.
Where it appears:
Trial and appellate decisions, legal analysis, and training on case logic.
3D — Technical, Repository, Git, GitHub, and Deployment Terms
Introduction to this section
This section explains the technical vocabulary of the SUMMA environment.
A new team member does not need to begin as a professional software engineer in order to understand this system, but they do need to become comfortable with the language of repositories, version control, local development, documentation, builds, and deployment. A legal-tech company cannot operate seriously if its internal technical vocabulary remains vague or magical.
These terms should therefore be learned as real working language, not as decorative jargon.
Repository and file-structure terms
repository
Definition:
A repository is the tracked body of files, folders, and history that make up a project under version control.
Plain explanation:
A repository is the project as a managed code-and-document environment.
Why it matters:
The repository is the main container of the product’s code, docs, scripts, training material, and tracked change history.
Where it appears:
Everywhere in engineering, docs, and internal workflow.
repo
Definition:
“Repo” is the short form of “repository.”
Plain explanation:
It means the same thing, just shorter.
Why it matters:
This is one of the most commonly used words in technical conversation.
Where it appears:
Daily technical discussion, documentation, and onboarding.
directory
Definition:
A directory is a folder in the file system.
Plain explanation:
A directory is a container holding files or other directories.
Why it matters:
A great deal of terminal and repo work is really path and directory navigation.
Where it appears:
Terminal usage, repo maps, docs-site setup, and script paths.
file tree
Definition:
A file tree is the hierarchical structure of directories and files inside a repository or subfolder.
Plain explanation:
It is the project’s folder-and-file shape.
Why it matters:
Readers need to learn how to picture the repo as a tree, not as a random pile.
Where it appears:
Repo maps, onboarding, code navigation, and docs-site structure.
path
Definition:
A path is the address of a file or directory in the file system.
Plain explanation:
A path tells the system where something lives.
Why it matters:
Most terminal and script work depends on paths being correct.
Where it appears:
Commands, scripts, documentation, builds, and deployment.
absolute path
Definition:
An absolute path is the full path from the root of the file system.
Plain explanation:
It starts from the very top and gives the full address.
Why it matters:
Absolute paths are useful when precision matters and ambiguity is risky.
Where it appears:
Terminal commands, debugging, scripts, and documentation.
relative path
Definition:
A relative path is a path written in relation to the current working directory.
Plain explanation:
It tells the system where something is from where the user currently stands.
Why it matters:
Many commands and config files rely on relative paths.
Where it appears:
Git commands, MkDocs config, scripts, and repo navigation.
current working directory
Definition:
The current working directory is the directory the shell is presently operating in.
Plain explanation:
It is “where you are” right now in Terminal.
Why it matters:
A command can behave differently depending on where it is run.
Where it appears:
Terminal usage, scripts, builds, and file operations.
source file
Definition:
A source file is a file treated as an original maintained input rather than a generated output.
Plain explanation:
It is the file humans are supposed to edit directly.
Why it matters:
Confusing source files with generated files causes wasted work and bad workflow.
Where it appears:
Docs, code, config, and export pipelines.
generated file
Definition:
A generated file is an output created by a script, build step, or export process.
Plain explanation:
It is produced by the system rather than written directly by hand.
Why it matters:
Generated files may need different handling, storage, or regeneration logic than source files.
Where it appears:
Build outputs, exports, site folders, manifests, and reports.
canonical file
Definition:
A canonical file is the authoritative file to be treated as the official source of truth for a given purpose.
Plain explanation:
It is the file that counts.
Why it matters:
A serious project must be explicit about which file is the official one when multiple similar files exist.
Where it appears:
README anchors, internal manuals, docs-site material, and outputs.
source of truth
Definition:
The source of truth is the authoritative place or artifact from which correct information should be taken.
Plain explanation:
It is the version or object the team trusts as official.
Why it matters:
Without a source of truth, projects drift into duplication, contradiction, and confusion.
Where it appears:
Documentation, repo protocol, internal workflow, and canonical files.
Git terms
Git
Definition:
Git is the version-control system used to track changes in the project over time.
Plain explanation:
Git is the tool that remembers what changed, when it changed, and how the project got from one state to another.
Why it matters:
Without Git, serious software and docs work becomes fragile, opaque, and much harder to manage safely.
Where it appears:
Every tracked change in the repo.
version control
Definition:
Version control is the disciplined management of change over time in a tracked project.
Plain explanation:
It is the practice of keeping a history of changes instead of editing blindly.
Why it matters:
Version control allows teams to experiment, recover, compare, and collaborate without losing the history of the work.
Where it appears:
Git workflow, repo management, and collaborative development.
working tree
Definition:
The working tree is the current checked-out set of files on disk that the user is actively editing or inspecting.
Plain explanation:
It is the live copy of the project in front of you.
Why it matters:
Changes happen in the working tree before they are committed.
Where it appears:
Git status, diff, add, commit, and branch workflow.
tracked file
Definition:
A tracked file is a file already known to Git and monitored for change.
Plain explanation:
Git is already watching it.
Why it matters:
Tracked files are part of the project history and can be diffed, staged, and committed.
Where it appears:
Git status, add, commit, and repository management.
untracked file
Definition:
An untracked file is a file present in the working tree that Git is not yet tracking.
Plain explanation:
It exists in the folder, but Git has not started managing it.
Why it matters:
Untracked files may be important new work, junk, or accidental outputs.
Where it appears:
Git status and workflow cleanup.
ignored file
Definition:
An ignored file is a file Git is instructed not to track.
Plain explanation:
Git is told to leave it alone.
Why it matters:
Some files should not be committed, such as temporary outputs, caches, or local environment files.
Where it appears:
.gitignore, local workflow, and build hygiene.
.gitignore
Definition:
.gitignore is the file that tells Git which files or patterns to ignore.
Plain explanation:
It is the ignore rulebook.
Why it matters:
A clean .gitignore helps keep junk, secrets, caches, and irrelevant outputs out of the repository.
Where it appears:
Repo root or subproject directories.
staging area
Definition:
The staging area is the intermediate place where changes are selected before commit.
Plain explanation:
It is where you tell Git which edits are about to become part of the next saved history point.
Why it matters:
Staging gives precision. A user can choose exactly what to commit.
Where it appears:
git add, git status, and commit workflow.
index
Definition:
The index is another term for the staging area.
Plain explanation:
It is the technical name for the staged state.
Why it matters:
Readers may see “index” in Git explanations and should know it means the staged content.
Where it appears:
Git internals and command explanations.
commit
Definition:
A commit is a saved snapshot of selected project changes in the repository’s history.
Plain explanation:
A commit is a durable checkpoint in the project.
Why it matters:
Commits are the atoms of tracked project history.
Where it appears:
Daily development workflow, docs updates, and release history.
commit message
Definition:
A commit message is the descriptive text attached to a commit explaining what changed.
Plain explanation:
It is the label for the checkpoint.
Why it matters:
A bad commit message weakens the usefulness of project history. A good one makes the history intelligible.
Where it appears:
git commit, GitHub history, audits, and repo review.
hash
Definition:
A hash is a unique identifier generated from content or from Git objects.
Plain explanation:
It is the compact fingerprint used to identify a commit or other content precisely.
Why it matters:
Hashes are essential for exact reference, integrity, and reproducibility.
Where it appears:
Commit IDs, manifests, checksums, and evidence-related product logic.
SHA
Definition:
SHA usually refers to the secure hash identifier used in Git object references or file checksums.
Plain explanation:
It is the hash label people use when referring to commit IDs or file fingerprints.
Why it matters:
Readers will often hear someone say “the SHA” when they mean the hash of a commit or artifact.
Where it appears:
Git history, integrity checks, and evidence-tracking contexts.
branch
Definition:
A branch is an independent line of tracked development history.
Plain explanation:
A branch lets work move forward without disturbing another line of work.
Why it matters:
Branching is how teams build features, fixes, or experiments without editing everything directly on the main line.
Where it appears:
Git workflow, GitHub, pull requests, and project safety.
local branch
Definition:
A local branch is a branch that exists in the user’s own copy of the repo.
Plain explanation:
It lives on the current machine.
Why it matters:
A local branch may exist before it is pushed to GitHub.
Where it appears:
Development workflow and branch management.
remote branch
Definition:
A remote branch is a branch stored on the remote repository service, such as GitHub.
Plain explanation:
It is the branch as known on the server, not just on the local machine.
Why it matters:
Readers need to distinguish what exists locally from what exists remotely.
Where it appears:
Push, pull, fetch, branch comparison, and collaboration.
main
Definition:
main is the primary branch name in many repositories.
Plain explanation:
It is often the central branch from which other work branches off.
Why it matters:
A protected main branch helps prevent careless changes to the project’s central line of history.
Where it appears:
Repo workflow, pull requests, releases, and branch policy.
feature branch
Definition:
A feature branch is a branch created to build or modify a particular feature or body of work.
Plain explanation:
It is a dedicated lane for one piece of work.
Why it matters:
Feature branches isolate change and make review safer.
Where it appears:
Everyday development and pull-request workflow.
hotfix branch
Definition:
A hotfix branch is a branch used for urgent corrective work.
Plain explanation:
It is the fast lane for a problem that must be fixed quickly.
Why it matters:
Readers should understand that not all branch work has the same urgency or purpose.
Where it appears:
Production fixes, release support, and emergency workflow.
merge
Definition:
A merge combines the history of one branch into another.
Plain explanation:
It joins one line of work back into another.
Why it matters:
Merging is how isolated work becomes part of the main project history.
Where it appears:
Pull requests, branch workflow, and release management.
merge conflict
Definition:
A merge conflict happens when Git cannot automatically reconcile competing changes.
Plain explanation:
Two sets of edits collide and need human resolution.
Why it matters:
Conflicts are normal in serious development and documentation workflows. They are not signs of failure, but they must be resolved carefully.
Where it appears:
Merge, rebase, and collaborative editing.
rebase
Definition:
A rebase rewrites the branch’s position in history so it sits on top of another base point.
Plain explanation:
It rearranges how the work is attached to the project history.
Why it matters:
Rebase can keep history cleaner, but because it rewrites history, it must be used carefully.
Where it appears:
Advanced Git workflow and branch cleanup.
cherry-pick
Definition:
Cherry-pick copies a specific commit from one branch onto another.
Plain explanation:
It takes one change without taking the whole branch.
Why it matters:
This is useful when one particular fix or commit needs to move separately.
Where it appears:
Selective history management and hotfix work.
diff
Definition:
A diff is the comparison showing how one state differs from another.
Plain explanation:
It is the before-and-after view of changes.
Why it matters:
Diffs are how humans and tools inspect what actually changed.
Where it appears:
Git, pull requests, review, and quality control.
patch
Definition:
A patch is a set of changes represented in a transferable diff-like form.
Plain explanation:
It is a portable package of edits.
Why it matters:
Patches can be shared, applied, or reviewed separately from a whole branch.
Where it appears:
Advanced Git workflow and tooling.
reset
Definition:
Reset moves branch pointers and optionally changes the working tree or staging area to an earlier state.
Plain explanation:
It rewinds or repositions part of the current Git state.
Why it matters:
Reset can be powerful and destructive if misunderstood.
Where it appears:
Undo and cleanup workflows.
revert
Definition:
Revert creates a new commit that undoes the effect of an earlier commit.
Plain explanation:
It reverses a change without erasing history.
Why it matters:
Revert is often safer than reset for shared history because it preserves the fact that something happened and was later undone.
Where it appears:
Shared repos, release fixes, and collaborative rollback.
tag
Definition:
A tag is a named reference to a specific commit, often used to mark releases or important checkpoints.
Plain explanation:
A tag is a durable label placed on a known point in history.
Why it matters:
Tags make it easier to identify stable milestones, reboot points, or releases.
Where it appears:
Release workflow, project checkpoints, and memory anchors.
release
Definition:
A release is a defined published state of the project or artifact.
Plain explanation:
It is a named version intended to be treated as a real deliverable or milestone.
Why it matters:
Releases separate everyday work from known, meaningful publication points.
Where it appears:
GitHub, product delivery, and versioning.
GitHub and collaboration terms
GitHub
Definition:
GitHub is the hosted platform used to store, review, and collaborate on Git repositories.
Plain explanation:
GitHub is where the repo lives online and where teams collaborate around it.
Why it matters:
A major part of project history, review, and collaboration happens there.
Where it appears:
Repo hosting, pull requests, issue tracking, releases, and team workflow.
pull request
Definition:
A pull request is a request to merge changes from one branch into another, usually accompanied by review.
Plain explanation:
It is the formal proposal to bring one body of work into the main line.
Why it matters:
Pull requests are one of the main quality-control and collaboration gates in modern repo workflow.
Where it appears:
GitHub workflow, code review, docs review, and release preparation.
PR
Definition:
PR is the short form of pull request.
Plain explanation:
It means the same thing.
Why it matters:
This is one of the most common abbreviations in engineering conversation.
Where it appears:
GitHub, team discussions, and workflow notes.
review
Definition:
Review is the process of inspecting and evaluating proposed changes before they are accepted.
Plain explanation:
Someone checks the work before it becomes part of the main project.
Why it matters:
Review helps catch mistakes, improve wording, and maintain quality standards.
Where it appears:
Pull requests, docs updates, and code collaboration.
approve
Definition:
Approve means formally accepting a pull request or change as ready to merge.
Plain explanation:
The reviewer signs off on it.
Why it matters:
Approval is part of the control structure of collaborative change.
Where it appears:
GitHub reviews and merge workflow.
request changes
Definition:
Request changes means the reviewer is not yet willing to approve the proposed work.
Plain explanation:
The work needs revision before it can go in.
Why it matters:
This is a formal checkpoint in review workflow.
Where it appears:
GitHub pull-request review.
protected branch
Definition:
A protected branch is a branch with rules that prevent careless direct modification.
Plain explanation:
It is guarded.
Why it matters:
Protected branches reduce the risk of accidental or low-quality changes to core project history.
Where it appears:
GitHub branch settings and repo policy.
default branch
Definition:
The default branch is the branch GitHub treats as the project’s primary branch.
Plain explanation:
It is the main landing branch of the project.
Why it matters:
Many repo actions assume or target the default branch.
Where it appears:
GitHub settings, pull requests, and repo navigation.
issue
Definition:
An issue is a tracked unit of work, problem, idea, or discussion point in GitHub.
Plain explanation:
It is a formal project task or problem record.
Why it matters:
Issues help organize work outside the code itself.
Where it appears:
GitHub project management and collaboration.
discussion
Definition:
A discussion is a GitHub conversation space used for broader topics not necessarily tied to a specific change set.
Plain explanation:
It is a discussion board inside the project environment.
Why it matters:
Discussions can separate open conversation from formal issue or PR workflow.
Where it appears:
GitHub collaboration and community management.
Actions
Definition:
GitHub Actions is GitHub’s automation system for workflows such as testing, building, and deployment.
Plain explanation:
It is the automation engine attached to the repository.
Why it matters:
Automation is often critical to serious quality control and deployment.
Where it appears:
GitHub CI/CD, test runs, build jobs, and deployment workflows.
workflow
Definition:
A workflow is a defined automated process or a repeatable pattern of human process, depending on context.
Plain explanation:
It is the way a task is structured from start to finish.
Why it matters:
SUMMA uses the term in both product and engineering senses, so context matters.
Where it appears:
GitHub Actions, internal process, product behavior, and documentation.
artifact
Definition:
An artifact is a produced output from a workflow, build, test, or export process.
Plain explanation:
It is something the system generated and kept.
Why it matters:
Artifacts often serve as evidence of what a run, build, or export produced.
Where it appears:
Build systems, GitHub Actions, exports, and internal product logic.
Local development and environment terms
CLI
Definition:
CLI stands for command-line interface.
Plain explanation:
It means working with the system by typed commands in Terminal instead of only by clicking.
Why it matters:
A large amount of serious development and docs work is faster and clearer through the CLI.
Where it appears:
Terminal workflow, scripts, automation, and repo operations.
terminal
Definition:
Terminal is the application or environment through which command-line work is performed.
Plain explanation:
It is the window where commands are typed and executed.
Why it matters:
The SUMMA build workflow relies heavily on terminal comfort.
Where it appears:
Setup, editing, Git, scripts, builds, and deployment.
shell
Definition:
A shell is the command interpreter running inside Terminal.
Plain explanation:
It is the language environment that receives and runs typed commands.
Why it matters:
Different shells may behave slightly differently.
Where it appears:
Terminal use, scripts, and environment behavior.
zsh
Definition:
zsh is a specific shell commonly used on macOS systems.
Plain explanation:
It is one of the command languages the terminal may be running.
Why it matters:
Readers using macOS will often encounter zsh-specific prompt behavior and shell configuration.
Where it appears:
Local development and terminal sessions.
bash
Definition:
bash is another widely used shell.
Plain explanation:
It is another command interpreter with its own conventions.
Why it matters:
Some scripts or documentation may mention bash even if the user currently works in zsh.
Where it appears:
Shell scripts, docs, and cross-platform instructions.
Python
Definition:
Python is the programming language heavily used in the SUMMA environment.
Plain explanation:
It is one of the main languages used to build scripts, tools, parsers, and supporting logic.
Why it matters:
A great deal of SUMMA’s tooling and docs support relies on Python.
Where it appears:
Scripts, pipelines, build helpers, and automation.
virtual environment
Definition:
A virtual environment is an isolated Python environment with its own packages and dependencies.
Plain explanation:
It keeps one project’s Python setup from colliding with another’s.
Why it matters:
Without virtual environments, package conflicts become much more likely.
Where it appears:
Local setup, docs site, scripting, and builds.
venv
Definition:
venv is the common shorthand for a Python virtual environment.
Plain explanation:
It means the project’s isolated Python package environment.
Why it matters:
This term appears constantly in setup and execution commands.
Where it appears:
Terminal prompts, setup instructions, and Python workflow.
dependency
Definition:
A dependency is a required package or library the project relies on.
Plain explanation:
It is something the project needs in order to run properly.
Why it matters:
Dependencies shape reproducibility, setup, and build reliability.
Where it appears:
Python environments, package files, and docs-site setup.
package
Definition:
A package is an installable unit of code or functionality.
Plain explanation:
It is a library or tool brought into the environment for use.
Why it matters:
Much of modern development depends on packages rather than everything being written from scratch.
Where it appears:
Python, documentation tooling, and build configuration.
requirements.txt
Definition:
requirements.txt is the file listing Python packages needed for a given environment.
Plain explanation:
It tells the environment what Python dependencies to install.
Why it matters:
It is central to reproducible Python setup, especially for the docs site and deployment.
Where it appears:
Python projects, docs-site folders, and Netlify builds.
environment variable
Definition:
An environment variable is a named value available to programs and scripts at runtime.
Plain explanation:
It is a setting the system can read while running commands or builds.
Why it matters:
Environment variables are often used to control behavior without hardcoding values into files.
Where it appears:
Shell sessions, builds, deployment, and configuration.
Documentation and deployment terms
Markdown
Definition:
Markdown is a lightweight plain-text markup format used for structured writing.
Plain explanation:
It is a simple text format used to write headings, lists, links, and structured prose without a heavy word processor.
Why it matters:
A large amount of SUMMA documentation and training material is written in Markdown.
Where it appears:
Manual chapters, booklets, docs site, README files, and notes.
YAML
Definition:
YAML is a structured text format often used for configuration files.
Plain explanation:
It is a human-readable way of expressing structured settings.
Why it matters:
Many config files and structured project artifacts use YAML.
Where it appears:
Config files, metadata files, and some project tooling.
JSON
Definition:
JSON is a structured text format used for data representation.
Plain explanation:
It is a machine-friendly way of representing structured data objects.
Why it matters:
JSON is common in exports, structured artifacts, metadata, and product outputs.
Where it appears:
Exports, APIs, manifests, and generated outputs.
schema
Definition:
A schema is the defined structure of a class of data.
Plain explanation:
It is the shape the data is supposed to follow.
Why it matters:
Without clear schema discipline, structured outputs become inconsistent and hard to trust.
Where it appears:
Casecards, manifests, exports, and structured models.
config
Definition:
A config file or config setting defines how a tool or environment should behave.
Plain explanation:
It is the rulebook for setup and behavior.
Why it matters:
Many systems depend less on code changes than on correct configuration.
Where it appears:
MkDocs, Netlify, scripts, and build systems.
MkDocs
Definition:
MkDocs is the static documentation generator used to build the SUMMA docs site.
Plain explanation:
It takes Markdown files and turns them into a navigable documentation website.
Why it matters:
The internal manual and training site depend on MkDocs for readable publication.
Where it appears:
Docs-site folder, local serve, local build, and deployment.
Material for MkDocs
Definition:
Material for MkDocs is the theme and documentation interface layer used on top of MkDocs.
Plain explanation:
It controls the docs site’s presentation, navigation, and look.
Why it matters:
It shapes how the manual is experienced by the reader.
Where it appears:
Docs-site theme configuration and live documentation portal.
docs site
Definition:
The docs site is the published documentation portal built from Markdown and configuration files.
Plain explanation:
It is the readable website version of the internal manual and related materials.
Why it matters:
A docs site is often a better reading environment than raw Markdown folders.
Where it appears:
MkDocs workflow, local preview, and Netlify deployment.
build
Definition:
A build is the process of generating a structured output from source files.
Plain explanation:
It turns source materials into a usable product or artifact.
Why it matters:
The docs site is built from Markdown into a static site output.
Where it appears:
MkDocs, scripts, artifacts, and deployment.
serve
Definition:
Serve means running a local development server so the output can be previewed in a browser.
Plain explanation:
It lets the user see the site locally before deployment.
Why it matters:
Serve is central to fast docs iteration and preview.
Where it appears:
MkDocs local workflow.
deploy
Definition:
Deploy means publishing a built output into an environment where others can access it.
Plain explanation:
It is the act of making the built thing live.
Why it matters:
A build that never gets deployed remains private local output.
Where it appears:
Netlify, site publication, and release workflow.
static site
Definition:
A static site is a website made of generated files served as-is, without a complex live application backend.
Plain explanation:
It is a site built from files rather than dynamically assembled by a heavy server application at runtime.
Why it matters:
The SUMMA training manual is currently being published as a static docs site.
Where it appears:
MkDocs, Netlify, and docs-site architecture.
Netlify
Definition:
Netlify is the hosting platform used to publish the static docs site.
Plain explanation:
It is where the generated docs site can be put online.
Why it matters:
It is part of the publication environment of the manual.
Where it appears:
Docs deployment and public/internal hosting workflow.
netlify.toml
Definition:
netlify.toml is the Netlify configuration file that defines how the site should be built and published.
Plain explanation:
It tells Netlify what command to run and what output folder to publish.
Why it matters:
Without correct deployment configuration, the docs site may fail to build or publish correctly.
Where it appears:
Docs-site deployment setup.
base directory
Definition:
The base directory is the subdirectory of the repo from which a build system should run.
Plain explanation:
It tells the deploy platform where the real project lives.
Why it matters:
If the base directory is wrong, the build will run in the wrong place.
Where it appears:
Netlify configuration and project deployment settings.
publish directory
Definition:
The publish directory is the folder containing the built output that should be served.
Plain explanation:
It is the output folder Netlify or another host should expose.
Why it matters:
If the publish directory is wrong, the host may publish nothing or publish the wrong thing.
Where it appears:
Netlify and static-site deployment.
internal link
Definition:
An internal link is a link from one page or section of the docs site to another within the same site.
Plain explanation:
It is a hyperlink that stays inside the manual.
Why it matters:
Heavy internal linking makes a serious manual more navigable and more useful.
Where it appears:
Docs site, chapter cross-references, and roadmap design.
anchor link
Definition:
An anchor link is a link to a specific heading or section on a page.
Plain explanation:
It jumps to an exact point, not just to the top of a page.
Why it matters:
Anchor links are critical for deep navigation in long manuals and dictionaries.
Where it appears:
Table of contents, in-page navigation, and cross-reference design.
table of contents
Definition:
A table of contents is the structured list of headings or sections in a document or page.
Plain explanation:
It is the map of where the reader can go inside a page or manual.
Why it matters:
Long chapters become much more usable when the table of contents is strong.
Where it appears:
Docs site layout and chapter navigation.
3E — Internal SUMMA Architecture and Workflow Terms
Introduction to this section
This section defines the internal language that belongs specifically to the SUMMA environment.
These are not merely generic software-company terms and not merely generic legal terms. They are the project’s own working vocabulary: the words used to describe how the product is organized, how the repo is explained, how the premium architecture is understood, how training materials are packaged, and how internal thinking is structured.
A new team member who learns these terms well will understand not only what SUMMA does, but how the company thinks about its own machine.
General internal structure terms
phase
Definition:
A phase is a named stage of development or conceptual progress inside the project roadmap.
Plain explanation:
A phase is one chunk of work in the evolution of the system.
Why it matters:
Phases help the team understand what has already been built, what is being built now, and what belongs later.
Where it appears:
Roadmaps, README anchors, development planning, and training materials.
layer
Definition:
A layer is a conceptual or structural unit of explanation, capability, or product behavior.
Plain explanation:
A layer is one meaningful slice of the system or one focused slice of the training manual.
Why it matters:
SUMMA uses layered thinking heavily. Readers need to understand that the project is often explained not only by features but by layers of function, maturity, or review behavior.
Where it appears:
Training manuals, premium-ladder discussion, roadmap language, and internal docs.
booklet
Definition:
A booklet is a grouped training or explanation artifact that gathers multiple related layers into one reading unit.
Plain explanation:
A booklet is a packaged manual section meant to be read as a coherent block.
Why it matters:
Booklets are part of how internal knowledge is organized for readers.
Where it appears:
Luke training materials, internal docs packaging, and reading-roadmap design.
roadmap
Definition:
A roadmap is a structured view of intended development, progression, or reading order.
Plain explanation:
It is the map of where the work is going or how someone should move through it.
Why it matters:
Without a roadmap, the project becomes harder to navigate and easier to misunderstand.
Where it appears:
Training docs, internal planning, reading guides, and phase tracking.
reading path
Definition:
A reading path is a curated order in which training materials should be read.
Plain explanation:
It tells the reader what to read first, what to read later, and how to avoid drowning.
Why it matters:
A system as large as SUMMA needs guided entry, not only raw document access.
Where it appears:
Training manuals, docs site, and internal onboarding.
fast path
Definition:
A fast path is a shortened reading or learning route for a particular kind of reader.
Plain explanation:
It is the efficient version of the training path.
Why it matters:
Not every reader needs the same depth at the same time.
Where it appears:
Reading guides, docs site, onboarding, and role-based training.
docs portal
Definition:
The docs portal is the published documentation site through which internal manuals and training materials are read.
Plain explanation:
It is the website version of the manual and supporting documents.
Why it matters:
A docs portal is often the best way to make large internal knowledge readable and hyperlinked.
Where it appears:
MkDocs, Netlify, internal training environment.
source material
Definition:
Source material is the underlying content from which a more polished or assembled training artifact is built.
Plain explanation:
It is the raw chapter, layer, or file set used to produce the final reading experience.
Why it matters:
The project often separates source writing from compiled or deployed reading artifacts.
Where it appears:
Training-manual build process, docs-site compilation, and booklet generation.
Project memory and continuity terms
memory anchor
Definition:
A memory anchor is a designated file or artifact used to preserve project state, decisions, history, and resumption context.
Plain explanation:
It is the file the project can come back to in order to remember where it was.
Why it matters:
Large projects drift badly without a clear memory anchor.
Where it appears:
README_FOR_AI files, reboot protocols, and internal continuity workflow.
reboot point
Definition:
A reboot point is a stable state of the project from which work can be resumed reliably later.
Plain explanation:
It is the restart checkpoint.
Why it matters:
The more complex the project becomes, the more important it is to know where safe resumption begins.
Where it appears:
README anchors, tags, release checkpoints, and internal resumption notes.
canonical path
Definition:
A canonical path is the path designated as the official location of an important file or artifact.
Plain explanation:
It is the official address of something important.
Why it matters:
Canonical paths prevent file-location ambiguity.
Where it appears:
README anchors, project instructions, and docs-site structure.
handoff pack
Definition:
A handoff pack is a packaged set of information designed to let another person resume, understand, or continue work safely.
Plain explanation:
It is the transfer package for continuity.
Why it matters:
Projects become fragile when knowledge lives only in one person’s head.
Where it appears:
Training materials, roadmap design, continuity workflow, and archive logic.
Core SUMMA architecture terms
structured review
Definition:
Structured review is the discipline of treating the file as a navigable, source-linked, pressure-aware environment rather than a flat pile of documents.
Plain explanation:
It means reviewing with real structure instead of just scrolling and remembering.
Why it matters:
This is one of the core worldview terms of the product.
Where it appears:
Product overview, architecture chapters, and advanced review behavior.
source-linked review
Definition:
Source-linked review is review that remains tied to exact underlying record points rather than drifting into unsupported summary.
Plain explanation:
The understanding stays connected to where it came from.
Why it matters:
This reduces false confidence and strengthens trust.
Where it appears:
Anchors, citations, workbench logic, and company standards.
local-first
Definition:
Local-first is the design principle that the user’s own storage and trust boundary remain primary rather than being displaced by mandatory cloud dependency.
Plain explanation:
The files stay anchored to the user’s own environment.
Why it matters:
This is one of the identity choices of the SUMMA worldview.
Where it appears:
Product philosophy, deployment discussions, and trust positioning.
court-ready
Definition:
Court-ready refers to outputs, structure, and product behavior disciplined enough to support real legal use rather than toy demonstrations.
Plain explanation:
It means serious enough for actual legal work.
Why it matters:
This term separates aspirational prototypes from real legal-tech standards.
Where it appears:
Product standards, export logic, and company expectations.
reviewability
Definition:
Reviewability is the degree to which the file can actually be worked through intelligently.
Plain explanation:
It asks whether the file is truly workable, not just present.
Why it matters:
This is one of the main pain points the system is meant to improve.
Where it appears:
File hygiene, architecture, advanced review, and company language.
continuity
Definition:
Continuity is the preservation of working understanding across time, people, and stages of review.
Plain explanation:
The file stays intelligible even as time passes or people change.
Why it matters:
Without continuity, the review process keeps breaking and restarting.
Where it appears:
Handoff, re-entry, memory-anchor logic, and human-work chapters.
traceability
Definition:
Traceability is the ability to move reliably from higher-order understanding back to the source material it depends on.
Plain explanation:
It means the chain back to source stays intact.
Why it matters:
Traceability is a major trust requirement.
Where it appears:
Anchors, citations, workbench logic, and standards chapters.
auditability
Definition:
Auditability is the degree to which the system’s outputs and structure can be inspected, checked, and traced.
Plain explanation:
It means the work can be examined and justified later.
Why it matters:
A serious legal-tech product must be inspectable, not mystical.
Where it appears:
Exports, manifests, hashes, logs, and quality standards.
Casecards and structured-object terms
casecards
Definition:
Casecards is the internal structured-object lane used to normalize and preserve meaningful units of legal-file understanding.
Plain explanation:
It is the part of the system where the file begins turning into structured objects rather than staying a flat document pile.
Why it matters:
Casecards are foundational to the higher-order premium architecture.
Where it appears:
Repo structure, premium ladder, workbench architecture, and README anchors.
card
Definition:
A card is a normalized structured object representing a meaningful unit inside the file.
Plain explanation:
A card is a formal container for one kind of structured understanding.
Why it matters:
Cards are how the system begins holding meaning in durable, navigable units.
Where it appears:
Casecards, issue bundles, strategy structures, and workbench logic.
CitationRef
Definition:
CitationRef is the structured citation object representing a precise source-linked reference.
Plain explanation:
It is the formal citation unit used by the system.
Why it matters:
Without citation discipline, higher-order review becomes vague quickly.
Where it appears:
Casecards architecture, citations, store/load logic, and exporter flows.
FactCard
Definition:
A FactCard is a structured object representing a fact or asserted fact linked back to source.
Plain explanation:
It is one formal way the system preserves a factual unit inside the case.
Why it matters:
Facts are more useful when they stop floating loosely and become structured, linked, and revisitable.
Where it appears:
Casecards, extract logic, issue bundles, and strategy packaging.
EntityCard
Definition:
An EntityCard is a structured object representing a person, organization, place, or other identifiable actor/entity in the record.
Plain explanation:
It is the system’s structured way of holding “who or what this is.”
Why it matters:
Entity clarity becomes important quickly in large or multi-person files.
Where it appears:
Casecards schema and linking logic.
EventCard
Definition:
An EventCard is a structured object representing a meaningful event or occurrence in the record.
Plain explanation:
It is the system’s formal way of holding “what happened.”
Why it matters:
Events are central to timelines, sequences, and case logic.
Where it appears:
Casecards architecture and timeline-linked work.
IssueCard
Definition:
An IssueCard is a structured object representing a legal or review issue.
Plain explanation:
It is the formal issue container at the card level.
Why it matters:
Issue structure is one of the bridges from raw record to higher-order strategic work.
Where it appears:
Casecards, issue bundles, and premium-ladder logic.
CardLink
Definition:
A CardLink is the structured relationship connecting cards to one another.
Plain explanation:
It expresses how the structured objects are related.
Why it matters:
Without links, cards become isolated islands rather than a working network.
Where it appears:
Casecards linking, graph logic, and issue assembly.
CaseWorkspace
Definition:
CaseWorkspace is the structured working environment holding the organized case objects and related state.
Plain explanation:
It is the workspace where the case’s structured memory lives.
Why it matters:
Workspace logic is central to higher-order review continuity.
Where it appears:
Casecards storage, manifests, and workbench architecture.
Workbench and pressure terms
workbench
Definition:
The workbench is the higher-order review environment where structured issues, pressure, navigation, and source-linked understanding interact.
Plain explanation:
It is where the file stops being just stored and starts being actively worked.
Why it matters:
The workbench is one of the central premium ideas of SUMMA.
Where it appears:
Premium ladder, architecture, advanced review behavior, and README anchors.
pressure board
Definition:
The pressure board is the structured layer that organizes and surfaces pressure inside the file.
Plain explanation:
It is a board-like structure for where the file is pushing back hardest.
Why it matters:
This is one of the key bridges from record structure to strategic review value.
Where it appears:
Casecards/operator lane, workbench logic, and pressure-engine discussions.
pressure ranking
Definition:
Pressure ranking is the ordering of issue or bundle significance by how much they matter to posture or review urgency.
Plain explanation:
It is the attempt to rank what matters most.
Why it matters:
A product that cannot help distinguish more and less important pressure remains stuck at shallow organization.
Where it appears:
Advanced review, workbench logic, and strategic pressure engine.
strategic pressure engine
Definition:
The strategic pressure engine is the premium layer aimed at surfacing what matters most, what changed posture, and where the true strategic pressure lies.
Plain explanation:
It is the highest-level pressure-ranking logic of the system.
Why it matters:
This is one of the defining advanced ambitions of SUMMA, especially at Level 9.
Where it appears:
Premium-ladder explanation, architecture, and product ambition.
posture
Definition:
Posture is the current strategic position or working stance created by the file as presently understood.
Plain explanation:
It is the shape of the case as it stands right now.
Why it matters:
Files change posture as new material arrives or pressure becomes more visible.
Where it appears:
Version drift, escalation, strategy, and pressure analysis.
posture shift
Definition:
A posture shift is a meaningful change in how the case should be understood or approached.
Plain explanation:
The case no longer stands where it stood before.
Why it matters:
One of the most valuable things a mature system can help reveal is when posture has changed.
Where it appears:
Pressure ranking, version drift, escalation, and advanced review.
dangerous file
Definition:
A dangerous file is a file whose pressure, instability, contradictions, or strategic consequences are materially serious.
Plain explanation:
It is not just large or annoying. It contains real legal danger.
Why it matters:
One of the product’s goals is to help distinguish danger from mere burden.
Where it appears:
Advanced review chapters and file-behavior training.
noisy file
Definition:
A noisy file is a file that feels burdensome because of volume or clutter without necessarily containing the same degree of real strategic danger.
Plain explanation:
It is loud, but not necessarily lethal.
Why it matters:
Readers must learn to distinguish pressure from mere noise.
Where it appears:
Advanced review and file-shape analysis.
strategic maturity
Definition:
Strategic maturity is the degree to which the file has become rich, structured, and stable enough for premium workbench behavior to pay off.
Plain explanation:
It describes when the file is ready for deeper strategic handling.
Why it matters:
Not every file is mature enough for every premium layer immediately.
Where it appears:
Premium ladder, workbench discussions, and advanced review.
anchor exhibit
Definition:
An anchor exhibit is an exhibit with unusually high structural importance to the case.
Plain explanation:
It is a high-weight exhibit the review keeps returning to.
Why it matters:
A small number of exhibits often carry disproportionate pressure.
Where it appears:
Advanced review, case simulation, and high-value-exhibit logic.
high-value exhibit
Definition:
A high-value exhibit is an exhibit that matters more than the average piece of material because of its strategic, evidentiary, or structural importance.
Plain explanation:
It is one of the exhibits doing real work in the case.
Why it matters:
The system should help distinguish high-value material from background mass.
Where it appears:
Anchor-material chapters, issue bundles, and workbench behavior.
Operator and export terms
operator
Definition:
An operator is the person or role using the system in an active working capacity.
Plain explanation:
The operator is the hands-on user inside the environment.
Why it matters:
SUMMA often uses operator language to describe workflow perspective distinct from abstract system description.
Where it appears:
Operator lanes, dashboards, exports, and training material.
operator dashboard
Definition:
The operator dashboard is the summary or command-center view presented for active case handling.
Plain explanation:
It is the high-level working surface for the operator.
Why it matters:
Dashboards are where structured outputs become usable at a glance.
Where it appears:
Operator exports and workbench-related architecture.
command center
Definition:
The command center is the top-level coordinating view above detailed lower-level structures.
Plain explanation:
It is the place from which the operator can see the broader state of the file environment.
Why it matters:
This is one of the higher-order organizational ideas of the operator lane.
Where it appears:
Dashboard artifacts and top-level workspace summaries.
archive lane
Definition:
The archive lane is the part of the system concerned with preservation, packets, bundles, and durable exportable state.
Plain explanation:
It is the preservation and packaging side of the project.
Why it matters:
Archive logic helps distinguish active work from preserved output and session state.
Where it appears:
Archive packet layers, rebuild logic, and export architecture.
packet
Definition:
A packet is a bundled artifact or structured collection of material prepared for preservation, export, or review.
Plain explanation:
It is a packaged unit of related output.
Why it matters:
Packet logic is common in archive and operator export structures.
Where it appears:
Archive lane, operator exports, and rebuild structures.
manifest
Definition:
A manifest is the structured record of what a package, export, or workspace contains.
Plain explanation:
It is the inventory and structural summary of a bundle or environment.
Why it matters:
Manifests are key to auditability, integrity, and reproducibility.
Where it appears:
Archive lane, exports, workspaces, and generated artifacts.
exporter
Definition:
An exporter is code that converts structured internal data into a deliverable artifact or external format.
Plain explanation:
It is the part that turns internal structure into output.
Why it matters:
Without exporters, structured internal work remains trapped inside the system.
Where it appears:
Casecards exports, operator artifacts, archive bundles, and reports.
counsel notebook
Definition:
The counsel notebook is the structured layer intended to hold lawyer-facing narrative or working analysis.
Plain explanation:
It is the notebook-like output or structured thought space for counsel use.
Why it matters:
This is one of the places where raw review turns into more human-usable strategic writing.
Where it appears:
Casecards/counsel notebook models, exports, and workbench architecture.
brief
Definition:
A brief is a condensed structured statement of key material, issues, or reasoning.
Plain explanation:
It is a shorter, more distilled working document.
Why it matters:
Briefs are where compression begins to matter without losing important structure.
Where it appears:
Counsel notebook exports and structured legal reasoning artifacts.
Training and internal-document terms
internal training manual
Definition:
The internal training manual is the formal onboarding and knowledge-transfer manual for the SUMMA environment.
Plain explanation:
It is the serious company manual, not just scattered notes.
Why it matters:
This manual is the front door into the company’s thinking and vocabulary.
Where it appears:
Docs portal, repo structure, onboarding.
chapter
Definition:
A chapter is a major prose section of the manual.
Plain explanation:
It is one substantial teaching unit.
Why it matters:
The project uses chapter structure for deeper, more serious exposition.
Where it appears:
Internal manual and docs portal.
lexicon
Definition:
A lexicon is the full structured vocabulary of the environment.
Plain explanation:
It is the project’s serious dictionary.
Why it matters:
A weak lexicon creates weak thinking.
Where it appears:
Terminology chapter and training design.
3F — Latin and Formal Legal Expressions
Introduction to this section
Legal language often preserves older Latin and formal expressions long after ordinary speech has moved on. Some of these terms appear constantly. Some appear occasionally but carry high importance when they do. A serious legal-tech manual should not avoid them out of fear that the reader will be intimidated. The better move is to explain them clearly and make them part of the reader’s working vocabulary.
The purpose of this section is not to turn the reader into a classicist. It is to ensure that formal legal expressions stop feeling mystical.
prima facie
Definition:
“Prima facie” means “at first sight” or “on its face,” referring to something sufficient on initial appearance unless rebutted or displaced.
Plain explanation:
It means there appears to be enough to make the issue live, at least initially.
Why it matters:
This phrase often appears when courts discuss whether a threshold has been met.
Where it appears:
Applications, evidentiary thresholds, preliminary reasoning, and legal argument.
mens rea
Definition:
“Mens rea” refers to the mental element of an offence.
Plain explanation:
It is the guilty mind component: what the accused knew, intended, foresaw, or accepted mentally.
Why it matters:
A criminal offence usually has not only an external act but also a required mental state.
Where it appears:
Substantive criminal law, trial reasoning, appellate analysis, and offence structure.
actus reus
Definition:
“Actus reus” refers to the external or physical element of an offence.
Plain explanation:
It is the guilty act component: what was done, caused, or physically brought about.
Why it matters:
Readers need to understand that criminal liability is often analyzed through the relationship between actus reus and mens rea.
Where it appears:
Substantive criminal law, case theory, and appellate reasoning.
ratio decidendi
Definition:
“Ratio decidendi” is the legal principle or reasoning necessary to the court’s decision.
Plain explanation:
It is the binding core of why the case was decided the way it was.
Why it matters:
Not everything written in a judgment carries the same precedential weight.
Where it appears:
Case law reading, precedent analysis, and appellate/legal research.
obiter dictum
Definition:
“Obiter dictum” refers to observations in a judgment that are not strictly necessary to the decision.
Plain explanation:
It is what the court said along the way, but not the binding core holding.
Why it matters:
Readers must distinguish between the binding ratio and persuasive but non-binding obiter.
Where it appears:
Judgment reading, precedent analysis, and legal reasoning.
stare decisis
Definition:
“Stare decisis” is the doctrine that courts should follow binding precedent.
Plain explanation:
It is the rule that prior authoritative decisions matter and must often be followed.
Why it matters:
A legal system cannot function predictably if precedent is ignored casually.
Where it appears:
Case-law hierarchy, appellate reasoning, and legal research.
de novo
Definition:
“De novo” means “anew” or “from the beginning.”
Plain explanation:
It means the issue is considered fresh rather than simply deferred to as already decided.
Why it matters:
This phrase matters when discussing standards of review or the scope of reconsideration.
Where it appears:
Appeals, review standards, and some procedural contexts.
inter alia
Definition:
“Inter alia” means “among other things.”
Plain explanation:
It signals that the listed items are part of a larger set.
Why it matters:
It appears frequently in formal legal writing and judgments.
Where it appears:
Factums, judgments, pleadings, and legal analysis.
viva voce
Definition:
“Viva voce” refers to spoken testimony given orally in court.
Plain explanation:
It means live verbal evidence.
Why it matters:
This term distinguishes oral testimony from written or documentary forms of evidence.
Where it appears:
Trial proceedings, evidentiary rulings, and legal writing.
habeas corpus
Definition:
“Habeas corpus” is a legal remedy used to challenge unlawful detention or imprisonment.
Plain explanation:
It is the formal legal mechanism for asking the court to examine whether detention is lawful.
Why it matters:
It is one of the most important liberty-protecting concepts in legal history.
Where it appears:
Detention challenges, constitutional litigation, and advanced legal discussion.
certiorari
Definition:
“Certiorari” is a prerogative remedy used to quash or review decisions of lower courts or tribunals in certain contexts.
Plain explanation:
It is a formal superior-court review mechanism.
Why it matters:
It matters in judicial review and procedural-control contexts.
Where it appears:
Administrative law, review procedure, and advanced legal remedies discussion.
mandamus
Definition:
“Mandamus” is a prerogative remedy compelling a public official, court, or tribunal to perform a legal duty.
Plain explanation:
It is a court order telling a decision-maker to do what the law requires.
Why it matters:
It is an important formal remedy in public-law and review contexts.
Where it appears:
Judicial review, public-law litigation, and advanced procedural discussion.
functus officio
Definition:
“Functus officio” means that a court or decision-maker has completed its formal task and generally lacks authority to re-decide the matter except in limited circumstances.
Plain explanation:
The decision-maker is done and usually cannot simply reopen the matter at will.
Why it matters:
This principle matters in understanding finality and limits on judicial reconsideration.
Where it appears:
Post-decision procedure, appeals, and finality discussions.
audi alteram partem
Definition:
“Audi alteram partem” means “hear the other side.”
Plain explanation:
It is a foundational fairness principle requiring that a person affected by a decision have a chance to be heard.
Why it matters:
It is one of the basic procedural-fairness principles underlying adjudicative systems.
Where it appears:
Natural justice, procedural fairness, and review contexts.
res judicata
Definition:
“Res judicata” refers to the principle that matters already finally decided should not be relitigated in the same way.
Plain explanation:
A final decision is not supposed to be endlessly reopened.
Why it matters:
It protects finality, efficiency, and fairness in adjudication.
Where it appears:
Civil procedure more often, but conceptually relevant in finality discussions and broader legal literacy.
res gestae
Definition:
“Res gestae” is an older expression used in evidence law to refer to statements or events considered part of the transaction itself, though its use is more historically loaded and context-sensitive now.
Plain explanation:
It is a formal expression for material treated as part of the event in issue.
Why it matters:
Readers may encounter it in older case law or in evidence discussions and should not be thrown by it.
Where it appears:
Evidence law, older authorities, and legal terminology study.
ultra vires
Definition:
“Ultra vires” means “beyond the powers.”
Plain explanation:
It means a body acted outside its legal authority.
Why it matters:
This is a basic public-law concept and useful for legal literacy generally.
Where it appears:
Administrative law, constitutional discussion, and legal reasoning.
intra vires
Definition:
“Intra vires” means “within the powers.”
Plain explanation:
It means the action stayed inside lawful authority.
Why it matters:
It is the counterpart to ultra vires.
Where it appears:
Administrative and constitutional law discussion.
sui generis
Definition:
“Sui generis” means “of its own kind” or unique in legal category.
Plain explanation:
It means the thing is treated as special or not fitting neatly into ordinary categories.
Why it matters:
Courts often use this phrase when saying that something should not be forced into an imperfect legal box.
Where it appears:
Judgments, doctrinal classification, and legal writing.
locus standi
Definition:
“Locus standi” refers to standing: the right or entitlement to bring a matter before the court.
Plain explanation:
It asks whether the person has the legal position needed to bring the case or issue.
Why it matters:
A strong argument still fails if the party lacks standing to raise it.
Where it appears:
Applications, constitutional litigation, public-law matters, and procedure.
per curiam
Definition:
“Per curiam” refers to a judgment issued by the court as a whole rather than attributed to one named judge.
Plain explanation:
It is an opinion of the court collectively.
Why it matters:
The authorship style of a judgment can matter to how it is read and cited.
Where it appears:
Appellate judgments and case-law reading.
mutatis mutandis
Definition:
“Mutatis mutandis” means “with the necessary changes having been made.”
Plain explanation:
It means apply the same idea here, but adjust it as needed for the new context.
Why it matters:
This phrase appears often in formal legal writing and can confuse readers who have never seen it before.
Where it appears:
Judgments, statutory interpretation, and legal writing.
nolle prosequi
Definition:
“Nolle prosequi” is a formal decision by the prosecution to discontinue the proceeding or a charge.
Plain explanation:
The prosecution decides not to continue.
Why it matters:
It is a formal legal act with procedural significance, not just an informal abandonment.
Where it appears:
Criminal procedure and formal legal terminology.
Deep SUMMA-native architecture and workflow terms
operator lane
Definition:
The operator lane is the internal product/workflow lane concerned with active handling, oversight, session state, and practical working use of the structured case environment.
Plain explanation:
This is the part of SUMMA focused on the hands-on working user and the surfaces that help that user manage the file actively.
Why it matters:
Readers need to understand that the system is not organized only by technical modules. It is also organized by operational lanes with different purposes.
Where it appears:
Operator dashboards, review packets, session summaries, workspace posture exports, and related artifacts.
counsel lane
Definition:
The counsel lane is the internal lane oriented toward lawyer-facing structured outputs, reasoning surfaces, and narrative/legal work product.
Plain explanation:
This is the part of the system that bends more toward counsel use than toward raw technical handling.
Why it matters:
The system must support not only storage and structure, but the transition toward lawyer-usable reasoning and presentation.
Where it appears:
Counsel notebook, brief exports, issue bundles, and strategy-oriented structures.
review lane
Definition:
The review lane is the internal lane centered on the active inspection, comparison, triage, and structured understanding of the record.
Plain explanation:
This is the lane where the actual act of serious file review is most directly taking place.
Why it matters:
A file may be preserved well yet still be weak as a review environment. Review lane language helps keep that distinction visible.
Where it appears:
Review packets, workbench logic, issue handling, and training material.
session summary
Definition:
A session summary is a structured record of what happened in a given review or work session.
Plain explanation:
It captures the state of the work after a period of active handling.
Why it matters:
Session summaries are important for re-entry, handoff, continuity, and reducing loss of context over time.
Where it appears:
Operator exports, workbench session state, continuity material, and advanced review workflow.
workspace manifest
Definition:
A workspace manifest is the structured inventory and state description of a workspace.
Plain explanation:
It is the formal summary of what the workspace contains and how it is configured.
Why it matters:
A manifest helps preserve auditability, reproducibility, and safe return into structured working environments.
Where it appears:
CaseWorkspace persistence, store/load logic, and exported workspace state.
workspace posture
Definition:
Workspace posture is the current strategic and structural state of the workspace as a working environment.
Plain explanation:
It describes where the file stands right now as a review space.
Why it matters:
A workspace is not static. Posture helps express its current maturity, pressure level, and usefulness.
Where it appears:
Workspace posture exports, operator views, and advanced review discussions.
issue registry
Definition:
An issue registry is the structured set or inventory of issues known inside the case environment.
Plain explanation:
It is the organized ledger of the issues the system currently recognizes as meaningful.
Why it matters:
Without an issue registry, issue work can become scattered and repetitive.
Where it appears:
Issue bundles, strategy packs, workbench surfaces, and advanced review logic.
strategy pack
Definition:
A strategy pack is a bundled higher-order artifact organized around a meaningful issue or strategic problem in the file.
Plain explanation:
It is a structured package that gathers the material, links, pressure, and working logic relevant to one strategic issue.
Why it matters:
Strategy packs are a key sign that the system has risen above flat review into concentrated legal-work support.
Where it appears:
Casecards exporters, issue-bundle registry exports, and premium-ladder architecture.
review packet
Definition:
A review packet is a bundled artifact designed to support structured file review over a defined scope or session.
Plain explanation:
It is a package prepared to make review easier and more coherent.
Why it matters:
Review packets help turn raw file mass into usable working sets.
Where it appears:
Operator/review exports and packet-layer discussions.
master packet
Definition:
A master packet is a top-level bundled artifact intended to collect or summarize a broader working state than narrower packet types.
Plain explanation:
It is the bigger parent package above smaller focused packets.
Why it matters:
Master packet language helps distinguish top-level export states from narrower review slices.
Where it appears:
Typed operator master packet layers and related exporter logic.
command deck
Definition:
A command deck is a high-level structured artifact intended to support oversight, command-level orientation, or coordinated review leadership.
Plain explanation:
It is a more executive or top-level package than an ordinary review slice.
Why it matters:
This term reflects the project’s move toward premium, command-center-like summary artifacts.
Where it appears:
Archive/export layers and internal packet architecture.
crown packet
Definition:
A crown packet is a specific named packet type within the archive/export architecture.
Plain explanation:
It is one of the specialized bundled artifact forms used in the project’s internal naming system.
Why it matters:
Even when the naming is internal or stylized, team members need to know it refers to a real export layer or packet type, not decorative language.
Where it appears:
Archive packet layers and export history.
throne deck
Definition:
A throne deck is a specialized high-tier archive/export deck in the project’s internal packaging language.
Plain explanation:
It is one of the more elevated named deck artifacts in the archive structure.
Why it matters:
These deck names reflect internal artifact hierarchy and must be understood as actual architecture language, not jokes.
Where it appears:
Archive deck exports and packet hierarchy.
apex deck
Definition:
An apex deck is a top-tier deck artifact in the archive/export hierarchy.
Plain explanation:
It is a high-ranking structured export layer.
Why it matters:
Apex-level naming implies elevated position in the artifact structure.
Where it appears:
Archive deck exports and internal packet/deck naming.
imperial packet
Definition:
An imperial packet is a named high-tier packet artifact in the archive structure.
Plain explanation:
It is one of the project’s formal export bundle types.
Why it matters:
The internal packet taxonomy needs to be learnable and not mysterious.
Where it appears:
Archive packet exports and rebuild-related structures.
runner packet
Definition:
A runner packet is a packet artifact associated with execution or run-state support.
Plain explanation:
It is a packet tied to run-level workflow or runner logic.
Why it matters:
The packet architecture becomes easier to understand when each packet type is named and located clearly.
Where it appears:
Archive/export layers and rebuild/run orchestration.
regeneration plan
Definition:
A regeneration plan is the structured plan for rebuilding or regenerating a target state or artifact.
Plain explanation:
It is the recovery or rebuild recipe.
Why it matters:
A serious system must know not only how to create outputs, but how to recreate them safely when needed.
Where it appears:
Archive audit models, rebuild workflow, and repair-oriented exports.
repair plan
Definition:
A repair plan is the structured plan for correcting or restoring a damaged, inconsistent, or incomplete state.
Plain explanation:
It is the fix plan for a broken or weakened condition.
Why it matters:
Repair planning is part of making the system resilient, auditable, and operationally serious.
Where it appears:
Archive/export helpers and rebuild/verification architecture.
integrity manifest
Definition:
An integrity manifest is a manifest specifically focused on recording and preserving integrity-related information about artifacts or states.
Plain explanation:
It is the integrity inventory.
Why it matters:
Integrity manifests support auditability, trust, and reproducibility.
Where it appears:
Export helpers, archive manifests, and integrity-oriented packet logic.
forensic scaffold
Definition:
A forensic scaffold is the early structural framework for forensic-comparison capabilities before deeper logic is fully implemented.
Plain explanation:
It is the starting structural frame for forensic functionality.
Why it matters:
Scaffolds are often how the project stages ambitious functionality safely before full maturity.
Where it appears:
Forensic phase planning, smoke gates, and README anchor history.
forensic overlap
Definition:
Forensic overlap refers to measured overlap between media or source materials used to determine likely relationship, continuity, or match.
Plain explanation:
It is the degree to which two materials overlap in a meaningful forensic way.
Why it matters:
Overlap logic helps support more disciplined matching than vague resemblance alone.
Where it appears:
Forensic audio overlap, matching logic, and confidence-gate discussions.
forensic fingerprint
Definition:
A forensic fingerprint is the structured signature used to compare media or source material for likely match or overlap.
Plain explanation:
It is the comparison signature of the material.
Why it matters:
Fingerprinting is central to forensic-style comparison where exact equality is not the only useful relationship.
Where it appears:
Forensic fingerprint v1/v2 work, matching logic, and smoke-gate testing.
diff PDF forensics
Definition:
Diff PDF forensics refers to the structured comparison of PDF versions with forensic-awareness features.
Plain explanation:
It means comparing PDFs not just visually, but with more disciplined match/change logic.
Why it matters:
PDF comparison becomes much more valuable when it can preserve and expose meaningful change safely.
Where it appears:
Diff-report architecture, forensic PDF hotfixes, and export logic.
index delta
Definition:
Index delta is the structured difference between one index state and another.
Plain explanation:
It is the change layer between two indexed states.
Why it matters:
This allows the system to focus on what changed rather than re-treating the whole file universe as new every time.
Where it appears:
Index delta builds, diff workflows, and page-aware indexing repair history.
page-aware indexing
Definition:
Page-aware indexing is indexing that preserves page-level structure rather than treating a document only as an undifferentiated whole.
Plain explanation:
The index understands pages as pages.
Why it matters:
For legal review, page position often matters a great deal.
Where it appears:
PDF indexing, citations, page_num logic, and repair phases.
citation byte ranges
Definition:
Citation byte ranges are byte-level position ranges used to locate cited material in certain text contexts.
Plain explanation:
They are machine-level boundaries marking where cited content lives.
Why it matters:
Byte ranges can make text citations more exact and reproducible.
Where it appears:
Citation output, stable cite_id logic, and text-anchoring systems.
workspace enriched search
Definition:
Workspace enriched search is search behavior that operates with awareness of workspace structure, diff context, or forensic-related enrichment.
Plain explanation:
It is search that knows more than just raw keyword matching.
Why it matters:
A mature search environment should become increasingly context-aware.
Where it appears:
Search contract work, enriched search logic, and workspace-aware architecture.
pressure board session status
Definition:
Pressure board session status is the structured session-state view of the pressure board.
Plain explanation:
It is the current status snapshot of the pressure board during working use.
Why it matters:
Session-aware board state helps support continuity, review rhythm, and handoff.
Where it appears:
Pressure board lifecycle, session workflows, and workbench state logic.
counsel notebook brief
Definition:
A counsel notebook brief is the shorter structured output built from the counsel-notebook layer.
Plain explanation:
It is the brief-form product of the counsel notebook.
Why it matters:
This term marks the transition from structured internal state to more concise counsel-facing output.
Where it appears:
Counsel notebook exports and typed notebook-object workflows.
3C — Evidence, Record, and Document Terms
Introduction to this section
This section explains the vocabulary of the record itself: the documents, media, productions, evidentiary forms, and review-facing structures that make a serious legal file difficult to handle well.
A criminal-review system lives or dies by how well it understands the difference between simply having material and being able to work with it intelligently. For that reason, the language of the record is just as important as the language of procedure or the language of engineering.
record
Definition:
The record is the total body of material associated with the case or proceeding.
Plain explanation:
It is the whole evidentiary and procedural body of what exists in the matter.
Why it matters:
The system is not dealing with isolated documents. It is dealing with a record.
Where it appears:
Throughout the manual, especially in review, architecture, and case-simulation chapters.
case record
Definition:
The case record is the record as it exists in relation to one particular case.
Plain explanation:
It is the whole body of materials tied to that one matter.
Why it matters:
This helps distinguish the total file environment from one isolated exhibit or one production batch.
Where it appears:
Workflow, case simulation, and structured review discussions.
disclosure record
Definition:
The disclosure record is the portion of the case record constituted by disclosure materials and their evolving structure across time.
Plain explanation:
It is the working disclosure body as it actually arrives and develops.
Why it matters:
A disclosure-heavy case often becomes difficult because the disclosure record is large, staged, mixed, and unstable.
Where it appears:
Criminal workflow, simulation, and review-pressure chapters.
production
Definition:
A production is a delivered body of material provided into the record, often as part of disclosure.
Plain explanation:
It is a package or release of file material into the case environment.
Why it matters:
Productions often arrive in stages and may need to be compared over time.
Where it appears:
Disclosure handling, intake, version comparison, and record-tracking logic.
corrected production
Definition:
A corrected production is a production that replaces, fixes, or updates an earlier delivered set of material.
Plain explanation:
Something was delivered before, and now a corrected version has arrived.
Why it matters:
Corrected productions create one of the main engines of version drift and re-review burden.
Where it appears:
Disclosure evolution, version comparison, and file-stability discussions.
version
Definition:
A version is one identifiable state of a document, record slice, or output at a particular time.
Plain explanation:
It is one specific edition or state of the material.
Why it matters:
Without version awareness, a reviewer can easily work from stale understanding.
Where it appears:
Version drift, re-entry, corrections, and diff logic.
version drift
Definition:
Version drift is the gradual divergence between the reviewer’s mental picture of the file and the file’s current actual state as changes accumulate.
Plain explanation:
The file has moved, but the understanding has not kept up.
Why it matters:
Version drift is one of the major hidden dangers in serious record review.
Where it appears:
Advanced review behavior, re-entry, correction handling, and diff-aware logic.
source record
Definition:
A source record is the original underlying record object from which later understanding, structure, or exports derive.
Plain explanation:
It is the original thing the system is referring back to.
Why it matters:
The source record anchors trust and traceability.
Where it appears:
Source-linked review, citations, anchors, and architecture.
metadata
Definition:
Metadata is structured information about a file or record object rather than the substantive content itself.
Plain explanation:
It is data about the material: dates, size, type, path, timestamps, and similar fields.
Why it matters:
Metadata often becomes crucial in sorting, indexing, comparison, and forensic review.
Where it appears:
Intake, manifests, evidence handling, forensic logic, and export structure.
exhibit
Definition:
An exhibit is a document, object, recording, or other item formally used as evidence.
Plain explanation:
It is an evidentiary item in the case.
Why it matters:
Exhibits are one of the basic units of evidentiary work and often become anchors of review.
Where it appears:
Trial material, disclosure, issue bundles, and high-value-exhibit discussions.
exhibit brief
Definition:
An exhibit brief is a grouped set of exhibits or exhibit materials prepared for structured use.
Plain explanation:
It is a packaged body of exhibits organized for handling or presentation.
Why it matters:
Exhibit briefs reduce evidentiary sprawl by giving the material a more usable shape.
Where it appears:
Trial prep, record organization, and structured review workflow.
anchor document
Definition:
An anchor document is a document with unusually high structural importance to understanding the file.
Plain explanation:
It is a document the review keeps needing to come back to.
Why it matters:
A serious file often depends disproportionately on a smaller number of anchor documents.
Where it appears:
Advanced review behavior, workbench logic, and high-value-material discussions.
anchor exhibit
Definition:
An anchor exhibit is an exhibit that acts as a recurring structural reference point in the file.
Plain explanation:
It is one of the exhibits doing major work in the review.
Why it matters:
Anchor exhibits help stabilize navigation and issue development.
Where it appears:
Advanced review, case simulation, and workbench maturity.
high-value exhibit
Definition:
A high-value exhibit is an exhibit whose strategic, evidentiary, or structural importance exceeds that of most other materials in the file.
Plain explanation:
It is an exhibit that matters more than average.
Why it matters:
The system should help distinguish high-value material from background burden.
Where it appears:
Anchor-material logic, issue bundles, and pressure analysis.
transcript
Definition:
A transcript is the written text of spoken proceedings, interviews, or recorded material.
Plain explanation:
It is the text version of speech.
Why it matters:
Transcripts are often critical review objects because they turn spoken material into searchable and citable form.
Where it appears:
Trial review, interviews, evidentiary analysis, and appeal records.
transcript excerpt
Definition:
A transcript excerpt is a selected portion of a larger transcript.
Plain explanation:
It is a smaller slice taken out for focused use.
Why it matters:
Excerpts become important when the reviewer needs precision without dragging the whole transcript everywhere.
Where it appears:
Issue bundles, briefs, argument support, and review notes.
witness statement
Definition:
A witness statement is a recorded account given by a witness about relevant events.
Plain explanation:
It is the witness’s version of what happened, preserved in recorded form.
Why it matters:
Witness statements are central sources of timeline, contradiction, omission, and credibility pressure.
Where it appears:
Disclosure review, issue bundles, witness-pressure analysis, and simulation.
police notes
Definition:
Police notes are contemporaneous or near-contemporaneous notes made by police officers in relation to the investigation or case.
Plain explanation:
They are the officers’ recorded working notes.
Why it matters:
Police notes often become key materials for contradiction, sequence, and credibility analysis.
Where it appears:
Disclosure review, cross-examination prep, and evidentiary comparison.
occurrence report
Definition:
An occurrence report is a formal police report documenting an incident, complaint, or event.
Plain explanation:
It is one of the structured report forms generated by police activity.
Why it matters:
Occurrence reports often become central orientation documents in the disclosure record.
Where it appears:
Police material, disclosure packages, and record review.
forensic report
Definition:
A forensic report is a report produced from technical or scientific examination of evidence.
Plain explanation:
It is the written result of forensic analysis.
Why it matters:
Forensic reports can radically affect posture, confidence, and issue development.
Where it appears:
Disclosure, trial preparation, expert evidence, and simulation.
expert evidence
Definition:
Expert evidence is evidence given by a qualified expert on matters requiring specialized knowledge.
Plain explanation:
It is technical or specialized evidence beyond ordinary lay knowledge.
Why it matters:
Expert evidence often carries heavy strategic weight and must be understood carefully.
Where it appears:
Forensic reports, trial process, evidentiary rulings, and appeals.
surveillance
Definition:
Surveillance is the monitoring or recording of persons, places, or events for evidentiary or investigative purposes.
Plain explanation:
It is observed or recorded watching.
Why it matters:
Surveillance material can become central in timeline, identification, and contradiction analysis.
Where it appears:
Disclosure materials, media review, forensic comparison, and case simulation.
media file
Definition:
A media file is an audio, video, or image file used as part of the record.
Plain explanation:
It is non-text evidentiary material.
Why it matters:
Media files often create a different kind of review burden than documents do.
Where it appears:
Disclosure, forensic work, and structured review.
surveillance file
Definition:
A surveillance file is a media or record object specifically tied to surveillance evidence.
Plain explanation:
It is the surveillance material as a file unit.
Why it matters:
Such files often require comparison, timing analysis, and authenticity/continuity care.
Where it appears:
Media review, forensic comparison, and case simulation.
warrant package
Definition:
A warrant package is the grouped body of materials associated with obtaining or executing a warrant.
Plain explanation:
It is the warrant-related document set.
Why it matters:
Warrant packages can become central to Charter, admissibility, and investigative review.
Where it appears:
Search-and-seizure review, Charter issues, and evidentiary analysis.
search return
Definition:
A search return is the formal record of what was seized or returned under warrant authority.
Plain explanation:
It is the documented output of the search process.
Why it matters:
It helps connect seizure authority to actual recovered material.
Where it appears:
Search-and-seizure records and evidentiary continuity review.
communications record
Definition:
A communications record is a record of calls, messages, emails, or other communications relevant to the matter.
Plain explanation:
It is the communications layer of the record.
Why it matters:
Communications often become central to sequence, relationship, intent, and contradiction analysis.
Where it appears:
Disclosure, digital-evidence review, and issue formation.
call detail record
Definition:
A call detail record is a structured record of telephone-call metadata, such as time, duration, and parties involved.
Plain explanation:
It is not usually the content of the call, but the record about the call.
Why it matters:
Call detail records can be crucial in timelines and movement/association analysis.
Where it appears:
Digital evidence, record review, and timeline work.
message log
Definition:
A message log is a structured list or record of messages and their associated metadata or content.
Plain explanation:
It is the organized message record.
Why it matters:
Message logs often become dense sources of sequence and contradiction pressure.
Where it appears:
Digital disclosure, communication review, and issue bundles.
continuity of evidence
Definition:
Continuity of evidence is the evidentiary continuity showing how an item moved through handling, storage, or custody without compromising its identity.
Plain explanation:
It is the chain showing that the evidence remained the evidence.
Why it matters:
Weak continuity can undermine trust in the item.
Where it appears:
Exhibits, forensic evidence, chain-of-custody review, and trial argument.
chain of custody
Definition:
Chain of custody is the documented history of possession, handling, transfer, and storage of an item of evidence.
Plain explanation:
It is the evidence-handling trail.
Why it matters:
Chain of custody is one of the main trust structures supporting evidentiary integrity.
Where it appears:
Forensic evidence, exhibits, continuity review, and trial disputes.
redaction
Definition:
A redaction is the removal or masking of part of a document or record before disclosure or use.
Plain explanation:
Part of the material is blacked out or withheld.
Why it matters:
Redactions can affect reviewability, context, and issue development.
Where it appears:
Disclosure, sensitive material handling, and record review.
missing material
Definition:
Missing material is material that appears absent from the record in a way that may matter.
Plain explanation:
Something should be there, but is not.
Why it matters:
The record is often pressured as much by what is absent as by what is present.
Where it appears:
Disclosure review, omissions analysis, and gap assessment.
omitted material
Definition:
Omitted material is material left out of the record, production, summary, or account.
Plain explanation:
Something was not included.
Why it matters:
Omission can change meaning, credibility, and pressure dramatically.
Where it appears:
Statements, summaries, disclosure disputes, and issue bundles.
gap
Definition:
A gap is a missing connection, absence, or unresolved hole in the record.
Plain explanation:
The file does not join up properly at some point.
Why it matters:
Gaps are often what turn large records into unstable ones.
Where it appears:
Disclosure analysis, timeline work, contradiction review, and strategic assessment.
unresolved issue
Definition:
An unresolved issue is an issue that has not yet been clarified, stabilized, or worked through sufficiently.
Plain explanation:
It is still open.
Why it matters:
A serious file often contains several unresolved issues at once, and the system should help keep them visible.
Where it appears:
Issue bundles, session summaries, re-entry, and workbench logic.
contradiction cluster
Definition:
A contradiction cluster is a grouped zone in the record where multiple contradictions accumulate around a related topic or timeline area.
Plain explanation:
It is not just one contradiction. It is a whole hotspot of them.
Why it matters:
Clusters often matter more strategically than isolated inconsistencies.
Where it appears:
Issue bundles, witness-pressure analysis, and advanced review.
witness-pressure zone
Definition:
A witness-pressure zone is a part of the file where witness evidence becomes especially unstable, contested, or strategically important.
Plain explanation:
It is a hotspot around witness-related pressure.
Why it matters:
Witnesses often become the place where the case starts pushing hardest against itself.
Where it appears:
Credibility review, contradiction analysis, and workbench logic.
pattern formation
Definition:
Pattern formation is the process by which isolated details begin to form recurring, meaningful structures across the file.
Plain explanation:
The record starts showing shape rather than only fragments.
Why it matters:
Pattern formation is one of the turning points from flat review to higher-order review.
Where it appears:
Issue bundles, workbench maturity, and simulation.
stale understanding
Definition:
Stale understanding is an outdated mental picture of the file that no longer matches the file’s current actual state.
Plain explanation:
The reviewer still thinks the case stands where it used to stand.
Why it matters:
This is one of the great hidden risks in evolving disclosure environments.
Where it appears:
Version drift, re-entry, handoff, and posture-shift discussions.
re-entry path
Definition:
A re-entry path is the structured route by which a reviewer gets back into the file after time away.
Plain explanation:
It is the designed path back into the record.
Why it matters:
A serious file needs more than storage; it needs a safe return path.
Where it appears:
Re-entry, continuity, docs design, and review workflow.
practice management
Definition:
Practice management is software or workflow infrastructure used to run the operational side of a law practice.
Plain explanation:
It helps run the firm: matters, tasks, calendars, billing, contacts, intake, and related office workflow.
Why it matters:
SUMMA should be distinguished from generic practice management. Practice management helps run the business of law. SUMMA is aimed more at the structural review pain inside severe files.
Where it appears:
Competitor analysis, go-to-market, and positioning.
matter management
Definition:
Matter management is the organization and administration of an individual legal matter or case.
Plain explanation:
It is the workflow layer for tracking one file: documents, deadlines, tasks, communications, and status.
Why it matters:
Many competitor platforms are strong at matter management without solving the deeper review-structure problem SUMMA targets.
Where it appears:
Competitor map and positioning.
fact chronology
Definition:
A fact chronology is a structured timeline of facts, events, and related evidence in a legal matter.
Plain explanation:
It is a timeline built from the facts of the case.
Why it matters:
Fact chronology tools are among the closest adjacent competitors to SUMMA’s timeline and issue-structure layers.
Where it appears:
Competitor map, case analysis, and timeline discussion.
case chronology
Definition:
A case chronology is a structured timeline of case events, factual events, or both.
Plain explanation:
It is the ordered timeline view of what happened and when.
Why it matters:
Chronology work becomes crucial in disclosure-heavy and timeline-sensitive matters. SUMMA goes beyond chronology by linking timeline pressure to issue state and ranked review.
Where it appears:
Competitor map, timeline chapters, and dictionary/reference use.
eDiscovery
Definition:
eDiscovery is the process of identifying, collecting, processing, reviewing, and producing electronically stored information for legal matters.
Plain explanation:
It is the large-scale legal review workflow for digital documents, data, and evidence.
Why it matters:
eDiscovery platforms are serious competitors in large review environments, but they do not automatically solve the full criminal-review workbench problem SUMMA targets.
Where it appears:
Competitor map, commercial strategy, and product comparison.
legal hold
Definition:
A legal hold is a preservation directive used to prevent relevant information from being destroyed or altered during actual or anticipated legal proceedings.
Plain explanation:
It is the instruction to preserve material because it may matter in the case.
Why it matters:
Legal hold is a common eDiscovery and litigation-governance term that helps distinguish broader review platforms from SUMMA’s specific review posture.
Where it appears:
Competitor map, review platform terminology, and dictionary expansion.
privilege log
Definition:
A privilege log is a record listing documents withheld from production on the basis of legal privilege, usually with enough description to support the claim without revealing the protected content.
Plain explanation:
It is the formal list explaining which documents are being withheld because they are privileged.
Why it matters:
It is part of the language of serious review and production systems, especially in eDiscovery-heavy workflows.
Where it appears:
Competitor map and review terminology.
redaction
Definition:
Redaction is the removal or obscuring of sensitive, privileged, or protected content from a document, image, audio, or video before sharing or production.
Plain explanation:
It is hiding the part that cannot safely be shown.
Why it matters:
Redaction becomes especially important in criminal and media-heavy files involving sensitive information, witnesses, minors, or protected material.
Where it appears:
Competitor map, digital evidence workflows, and disclosure handling.
early case assessment
Definition:
Early case assessment is the structured early-stage evaluation of a legal matter to understand scope, risk, data volume, and review priorities.
Plain explanation:
It is the first serious assessment of what kind of case this is and how hard it is going to be.
Why it matters:
SUMMA’s intake, structure, and early disclosure handling are closely related to this concept, even though the product’s lane is narrower and more review-structural.
Where it appears:
Competitor map, disclosure handling, and early review.
predictive coding
Definition:
Predictive coding is a machine-learning-assisted review method used to help identify likely relevant material in large document sets.
Plain explanation:
It is software-assisted review that tries to learn what looks important based on examples and patterns.
Why it matters:
It is a major eDiscovery term and helps explain how some review systems differ from SUMMA’s pressure-aware criminal-review lane.
Where it appears:
Competitor map, eDiscovery language, and technical terminology.
technology-assisted review
Definition:
Technology-assisted review is the use of software, analytics, or machine learning to support legal document review.
Plain explanation:
It is software helping sort and review large amounts of legal material.
Why it matters:
This is a broader category term around predictive coding and assisted review, and it helps place SUMMA among adjacent review technologies without confusing the products.
Where it appears:
Competitor map and legal-tech terminology.
digital evidence management
Definition:
Digital evidence management is the handling, storage, organization, sharing, and review of digital evidence such as video, audio, images, and related files.
Plain explanation:
It is the system for managing media-heavy evidence safely and usefully.
Why it matters:
It is especially important in criminal matters with video, audio, bodycam, phone extractions, and other mixed-format evidence.
Where it appears:
Competitor map, media-heavy review, and criminal-file workflows.
deposition management
Definition:
Deposition management is the organization, review, and use of deposition transcripts, exhibits, designations, and related testimony workflows.
Plain explanation:
It is the system for handling deposition records and the work around them.
Why it matters:
Although more common in civil litigation language, it appears in competitor categories and helps distinguish transcript-focused workflow tools from SUMMA’s core criminal-review lane.
Where it appears:
Competitor map and transcript workflow terminology.
transcript designation
Definition:
Transcript designation is the process of marking selected transcript portions for later use, such as hearings, motions, trial preparation, or presentation.
Plain explanation:
It is choosing the exact transcript passages that matter most.
Why it matters:
It is part of transcript-heavy review and litigation-prep workflows, especially in platforms adjacent to SUMMA’s workbench logic.
Where it appears:
Competitor map and transcript terminology.
go-to-market
Definition:
Go-to-market is the strategy for bringing a product to the right buyers through the right messaging, channels, proof, and sales motion.
Plain explanation:
It is the plan for how the company actually gets customers.
Why it matters:
SUMMA’s commercial success depends on a wedge-first, proof-led go-to-market approach rather than generic legal-AI marketing.
Where it appears:
Commercial section and strategy chapters.
positioning
Definition:
Positioning is the disciplined explanation of what a product is, who it is for, and in what situation it becomes especially valuable.
Plain explanation:
It is the product’s place in the buyer’s mind.
Why it matters:
Weak positioning makes SUMMA sound generic. Strong positioning makes the wedge clear.
Where it appears:
Commercial section, messaging, and go-to-market.
wedge
Definition:
A wedge is the sharp, high-pain entry point where a product’s value is most immediately credible.
Plain explanation:
It is the first slice of the market where the product makes the strongest sense.
Why it matters:
SUMMA’s wedge is the criminal file that has crossed from ordinary inconvenience into structural review pain.
Where it appears:
Commercial section, positioning, and go-to-market.
sales motion
Definition:
Sales motion is the practical way a company sells a product: who leads the sale, how the conversation works, and how trust is built from first contact to adoption.
Plain explanation:
It is the real-world pattern of how the product gets sold.
Why it matters:
SUMMA’s early sales motion should be founder-led, diagnostic, and proof-driven.
Where it appears:
Commercial section and go-to-market.
pilot
Definition:
A pilot is a limited, structured evaluation period in which a buyer tests the product on a real workflow or file burden.
Plain explanation:
It is the trial that is serious enough to prove whether the product works.
Why it matters:
SUMMA’s early commercial strategy depends heavily on structured pilots rather than shallow free trials.
Where it appears:
Commercial section, packaging, and sales strategy.
proof point
Definition:
A proof point is a concrete, believable result or signal that supports the product’s claimed value.
Plain explanation:
It is the evidence that the product is helping in the way it says it helps.
Why it matters:
SUMMA should sell with operational proof points like better re-entry, cleaner handoff, and stronger issue concentration.
Where it appears:
Commercial section, pilots, and sales motion.
founder-led sales
Definition:
Founder-led sales is a sales approach in which the founder personally leads early demos, buyer conversations, qualification, and adoption learning.
Plain explanation:
It means the founder is the one doing the early selling.
Why it matters:
For a wedge product like SUMMA, founder-led sales is the strongest early way to learn the market, sharpen the message, and prove value honestly.
Where it appears:
Go-to-market, sales motion, and pricing/packaging strategy.
case strategy
Definition:
Case strategy is the structured legal approach for how a matter will be understood, prioritized, argued, and advanced.
Plain explanation:
It is the plan for how to handle and argue the case.
Why it matters:
SUMMA should support case strategy without pretending to replace counsel judgment. This is especially relevant to Level 9 and strategic pressure support.
Where it appears:
Competitor appendix, pressure engine, and commercial positioning.
case dynamics
Definition:
Case dynamics refers to the changing relationships among facts, issues, evidence, witnesses, timing, and procedural posture within a legal matter.
Plain explanation:
It means how the case shifts as different parts start affecting one another.
Why it matters:
A monster file is hard partly because its dynamics keep changing. This term helps explain why static storage is not enough.
Where it appears:
Competitor appendix, workbench logic, and issue/pressure discussion.
audit trail
Definition:
An audit trail is a record of actions, changes, access events, or handling history associated with a file, system, or evidence object.
Plain explanation:
It is the trace showing what happened to something and when.
Why it matters:
Audit trails are important in digital evidence and serious review environments because they support trust, accountability, and later verification.
Where it appears:
Competitor appendix, digital evidence workflows, and source-discipline thinking.
chain of custody
Definition:
Chain of custody is the documented sequence showing who handled an item of evidence, when, and under what conditions.
Plain explanation:
It is the custody history proving how the evidence moved from one hand or system to another.
Why it matters:
It is crucial in criminal and digital-evidence environments because evidentiary trust can weaken if custody handling is unclear.
Where it appears:
Competitor appendix, evidence-handling language, and criminal-file workflows.
disclosure portal
Definition:
A disclosure portal is a secure system or environment used to provide, share, or receive disclosure materials digitally.
Plain explanation:
It is the online place where disclosure gets delivered or accessed.
Why it matters:
Digital disclosure environments matter in modern criminal files, but portal access alone does not solve structural review pain.
Where it appears:
Competitor appendix, disclosure handling, and digital-evidence workflow discussion.
bulk redaction
Definition:
Bulk redaction is the automated or semi-automated redaction of many files or many sensitive elements at scale.
Plain explanation:
It means hiding sensitive information across lots of material quickly.
Why it matters:
This is especially important in media-heavy and disclosure-heavy files where manual redaction becomes punishing.
Where it appears:
Competitor appendix and digital-records processing.
transcript summary
Definition:
A transcript summary is a condensed explanation of the main substance of a transcript, often highlighting key points, themes, or testimony segments.
Plain explanation:
It is the short version of what mattered in the transcript.
Why it matters:
Transcript summaries can be useful, but they become dangerous if they outrun source return and exact passage access.
Where it appears:
Competitor appendix, transcript workflow, and summary-vs-source discussion.
witness summary
Definition:
A witness summary is a condensed account of what a witness said, what they matter to, and where their key pressure points appear.
Plain explanation:
It is the short version of a witness’s role and significance.
Why it matters:
Witness summaries are useful in severe files, but they must remain tied to exact source and contradiction structure.
Where it appears:
Competitor appendix, witness-pressure chapters, and review workflow.
deposition outline
Definition:
A deposition outline is a structured questioning plan prepared for a deposition, usually organized by topics, facts, exhibits, and goals.
Plain explanation:
It is the planned roadmap for how the questioning should go.
Why it matters:
Even though deposition language is more common in civil litigation, it appears in competitor positioning and helps distinguish transcript/workflow products from SUMMA’s core lane.
Where it appears:
Competitor appendix and transcript/deposition terminology.
exhibit linking
Definition:
Exhibit linking is the structured connection of exhibits to transcripts, facts, issues, events, or other parts of the case record.
Plain explanation:
It means tying the exhibit to the exact places it matters.
Why it matters:
This becomes valuable in complex matters because evidence only becomes truly usable when its relationships are preserved.
Where it appears:
Competitor appendix, evidence workflow, and workbench logic.
synced transcript video
Definition:
Synced transcript video is a workflow in which transcript text is linked directly to the matching video segment.
Plain explanation:
It means the transcript and the video are connected so the reviewer can jump between them.
Why it matters:
This matters in testimony-heavy and media-heavy environments because it reduces friction between reading and viewing.
Where it appears:
Competitor appendix, transcript/video workflow, and mixed-format review discussion.
substrate
Definition:
A substrate is the deeper underlying layer or foundation on which more visible features or workflows are built.
Plain explanation:
It is the base layer underneath the product.
Why it matters:
SUMMA’s wedge may be narrow, but its substrate is broader: source-linked, issue-aware, pressure-aware review.
Where it appears:
Expansion strategy, company story, and engine discussion.
adjacency
Definition:
An adjacency is a nearby market or use case that is close enough in structure or pain profile to be a realistic expansion path.
Plain explanation:
It is a neighboring lane the product can expand into without losing its identity.
Why it matters:
SUMMA should expand through true adjacencies, not random industries.
Where it appears:
Expansion strategy, investor narrative, and market planning.
expansion path
Definition:
An expansion path is the sequence by which a product grows from its initial wedge into adjacent markets or use cases.
Plain explanation:
It is the roadmap for where the product goes next.
Why it matters:
SUMMA should follow a wedge-first expansion path rather than going broad too early.
Where it appears:
Expansion strategy and company narrative.
severe-record environment
Definition:
A severe-record environment is a workflow or domain in which the record becomes large, unstable, mixed-format, and difficult to inhabit or prioritize honestly.
Plain explanation:
It is a place where the file or record becomes ugly enough that ordinary tools start breaking down.
Why it matters:
This is one of the best general descriptions of the broader class of environments SUMMA can eventually serve.
Where it appears:
Expansion appendix, company story, and long-term strategy.
mixed-format record
Definition:
A mixed-format record is a case or review environment containing multiple evidence or information formats, such as documents, audio, video, transcripts, images, and reports.
Plain explanation:
It is a record made of many different kinds of material, not just documents.
Why it matters:
Mixed-format burden is one of the key reasons ordinary tools stop being enough.
Where it appears:
Product architecture, competitor analysis, and expansion discussion.
reusable engine
Definition:
A reusable engine is a core system whose underlying logic can be applied across multiple adjacent domains without losing its structural identity.
Plain explanation:
It is a core machine that can work in more than one lane.
Why it matters:
SUMMA should be narrow in wedge but broad in reusable engine.
Where it appears:
Expansion appendix, investor narrative, and company story.
wedge-first
Definition:
Wedge-first describes a strategy that begins in one sharp, painful, high-fit market before expanding outward.
Plain explanation:
It means win one hard lane first, then expand.
Why it matters:
This is the correct strategic discipline for SUMMA.
Where it appears:
Go-to-market, founder sales, and expansion strategy.
optionality
Definition:
Optionality is the strategic value of having believable future paths available without needing to commit to all of them immediately.
Plain explanation:
It means keeping real future options open.
Why it matters:
A wedge-first company with a reusable engine has stronger future optionality than a narrow dead-end product.
Where it appears:
Investor narrative and expansion planning.
public-safety review
Definition:
Public-safety review is the structured examination of records, evidence, incidents, or case materials in law enforcement, oversight, prosecutorial, defence, or related public-safety environments.
Plain explanation:
It is serious record review in justice and public-safety systems.
Why it matters:
This is one of the clearest adjacent domains for a source-linked, evidence-aware engine.
Where it appears:
Expansion appendix and adjacency planning.
post-conviction review
Definition:
Post-conviction review is the examination of records, evidence, procedure, and issues after conviction, often in appeals, innocence work, or other post-judgment proceedings.
Plain explanation:
It is the serious re-review of a case after the original judgment.
Why it matters:
These files are often record-heavy, posture-heavy, and perfect examples of long-span review burden.
Where it appears:
Expansion appendix and legal adjacency discussion.
regulatory investigation
Definition:
A regulatory investigation is an inquiry conducted by or in response to a regulatory body, often involving large records, fact reconstruction, and compliance-sensitive review.
Plain explanation:
It is a serious investigation tied to rules, regulators, and large evidence burden.
Why it matters:
This is a strong legal adjacency because the structural pain often resembles severe-file review.
Where it appears:
Expansion appendix and adjacency planning.
internal investigation
Definition:
An internal investigation is an inquiry conducted inside an organization into misconduct, risk, compliance, or other serious internal matters.
Plain explanation:
It is a company or institution investigating itself or one of its people.
Why it matters:
This is one of the strongest non-criminal adjacent domains for a source-linked, posture-preserving review engine.
Where it appears:
Expansion appendix and non-legal adjacency discussion.
oversight review
Definition:
Oversight review is the structured examination of conduct, incidents, records, or decisions by an external or supervisory body.
Plain explanation:
It is serious review done by people checking whether others acted properly.
Why it matters:
Oversight environments are often mixed-format, politically sensitive, and pressure-heavy.
Where it appears:
Expansion appendix and public-sector adjacency discussion.
administrative adjudication
Definition:
Administrative adjudication is the formal decision-making process used by tribunals, agencies, boards, or similar bodies outside ordinary court proceedings.
Plain explanation:
It is serious case decision-making outside normal court.
Why it matters:
These environments can still involve ugly records, continuity burden, and issue concentration needs.
Where it appears:
Expansion appendix and non-court adjacency discussion.
record pressure
Definition:
Record pressure is the burden created when a record becomes too large, unstable, mixed, or interconnected to be handled comfortably with ordinary tools and memory alone.
Plain explanation:
It is the strain the file puts on the people trying to work inside it.
Why it matters:
This is one of the best cross-domain descriptions of the pain SUMMA is built around.
Where it appears:
Expansion appendix, company story, and pressure logic.
jurisdiction layer
Definition:
The jurisdiction layer is the part of the system that adapts to the legal procedure, terminology, forms, and workflow expectations of a specific jurisdiction.
Plain explanation:
It is the local legal wrapper for one province, state, or court system.
Why it matters:
SUMMA’s engine may stay stable while the jurisdiction layer changes from Ontario to another province or state.
Where it appears:
Jurisdiction expansion strategy and engine portability discussion.
review-domain layer
Definition:
The review-domain layer is the part of the system that adapts to the type of review environment, such as criminal, civil, regulatory, investigative, or oversight review.
Plain explanation:
It is the layer that changes depending on what kind of case world the system is working in.
Why it matters:
This layer helps separate domain changes from jurisdiction changes.
Where it appears:
Jurisdiction expansion map and engine-translation model.
translation layer
Definition:
A translation layer is the adapting layer that converts a stable underlying engine into the terminology, process, and expectations of a new jurisdiction or domain.
Plain explanation:
It is the layer that helps the same engine speak the local language of a new lane.
Why it matters:
SUMMA should treat expansion as careful translation, not careless copying.
Where it appears:
Jurisdiction expansion, domain adaptation, and engine portability.
criminal-review generic
Definition:
Criminal-review generic describes pain, structure, or workflow patterns that recur across many criminal-file environments regardless of local jurisdiction.
Plain explanation:
It means the part of criminal review that stays similar even when local legal language changes.
Why it matters:
This helps explain why the wedge can travel farther than Ontario alone.
Where it appears:
Jurisdiction expansion and wedge-portability discussion.
engine-generic
Definition:
Engine-generic describes the deepest parts of the system that remain reusable across jurisdictions and domains because they are structural rather than doctrinal.
Plain explanation:
It is the part of the engine that can travel the farthest.
Why it matters:
This is the basis of SUMMA’s long-term expansion story.
Where it appears:
Expansion strategy, company story, and engine architecture discussion.
procedural wrapper
Definition:
A procedural wrapper is the surface legal process layer that surrounds a case environment, including sequencing, filings, motion practice, and procedural expectations.
Plain explanation:
It is the local procedure shell around the deeper record problem.
Why it matters:
Different jurisdictions can have different procedural wrappers even when the deeper review pain is similar.
Where it appears:
Jurisdiction expansion and legal translation discussion.
doctrinal wrapper
Definition:
A doctrinal wrapper is the legal-concept layer that includes the local legal categories, doctrines, and formal labels through which the file is interpreted.
Plain explanation:
It is the local law language wrapped around the record.
Why it matters:
SUMMA’s engine should not be confused with one specific doctrinal wrapper.
Where it appears:
Jurisdiction and domain expansion strategy.
portability
Definition:
Portability is the degree to which a system, workflow, or underlying architecture can be reused across jurisdictions, domains, or adjacent environments.
Plain explanation:
It is how far the engine can travel without losing itself.
Why it matters:
SUMMA’s engine has more portability than its first Ontario criminal surface layer.
Where it appears:
Expansion strategy, engine discussion, and investor narrative.
jurisdiction modeling
Definition:
Jurisdiction modeling is the structured process of adapting a system to the procedure, terminology, forms, and expectations of a specific jurisdiction.
Plain explanation:
It is the disciplined work of making the engine fit a new legal place properly.
Why it matters:
This prevents the company from pretending Ontario success automatically translates everywhere.
Where it appears:
Jurisdiction expansion map and product strategy.
legal surface
Definition:
Legal surface is the visible outer layer of a legal product that reflects local jurisdictional language, process, and filing expectations.
Plain explanation:
It is the legal face the product shows in one specific system.
Why it matters:
Ontario is SUMMA’s first legal surface, not the full limit of the engine.
Where it appears:
Jurisdiction expansion and company narrative.
forum-specific workflow
Definition:
Forum-specific workflow is the sequence of actions, expectations, and document behavior that belongs to a particular court, tribunal, or legal forum.
Plain explanation:
It is the local way work gets done in that legal place.
Why it matters:
This often changes across jurisdictions even when deeper review pain remains similar.
Where it appears:
Jurisdiction-specific layer and translation discussion.
jurisdiction layer
Definition:
The jurisdiction layer is the part of the system that adapts to the legal procedure, terminology, forms, and workflow expectations of a specific jurisdiction.
Plain explanation:
It is the local legal wrapper for one province, state, or court system.
Why it matters:
SUMMA’s engine may stay stable while the jurisdiction layer changes from Ontario to another province or state.
Where it appears:
Jurisdiction expansion strategy and engine portability discussion.
review-domain layer
Definition:
The review-domain layer is the part of the system that adapts to the type of review environment, such as criminal, civil, regulatory, investigative, or oversight review.
Plain explanation:
It is the layer that changes depending on what kind of case world the system is working in.
Why it matters:
This layer helps separate domain changes from jurisdiction changes.
Where it appears:
Jurisdiction expansion map and engine-translation model.
translation layer
Definition:
A translation layer is the adapting layer that converts a stable underlying engine into the terminology, process, and expectations of a new jurisdiction or domain.
Plain explanation:
It is the layer that helps the same engine speak the local language of a new lane.
Why it matters:
SUMMA should treat expansion as careful translation, not careless copying.
Where it appears:
Jurisdiction expansion, domain adaptation, and engine portability.
criminal-review generic
Definition:
Criminal-review generic describes pain, structure, or workflow patterns that recur across many criminal-file environments regardless of local jurisdiction.
Plain explanation:
It means the part of criminal review that stays similar even when local legal language changes.
Why it matters:
This helps explain why the wedge can travel farther than Ontario alone.
Where it appears:
Jurisdiction expansion and wedge-portability discussion.
engine-generic
Definition:
Engine-generic describes the deepest parts of the system that remain reusable across jurisdictions and domains because they are structural rather than doctrinal.
Plain explanation:
It is the part of the engine that can travel the farthest.
Why it matters:
This is the basis of SUMMA’s long-term expansion story.
Where it appears:
Expansion strategy, company story, and engine architecture discussion.
procedural wrapper
Definition:
A procedural wrapper is the surface legal process layer that surrounds a case environment, including sequencing, filings, motion practice, and procedural expectations.
Plain explanation:
It is the local procedure shell around the deeper record problem.
Why it matters:
Different jurisdictions can have different procedural wrappers even when the deeper review pain is similar.
Where it appears:
Jurisdiction expansion and legal translation discussion.
doctrinal wrapper
Definition:
A doctrinal wrapper is the legal-concept layer that includes the local legal categories, doctrines, and formal labels through which the file is interpreted.
Plain explanation:
It is the local law language wrapped around the record.
Why it matters:
SUMMA’s engine should not be confused with one specific doctrinal wrapper.
Where it appears:
Jurisdiction and domain expansion strategy.
portability
Definition:
Portability is the degree to which a system, workflow, or underlying architecture can be reused across jurisdictions, domains, or adjacent environments.
Plain explanation:
It is how far the engine can travel without losing itself.
Why it matters:
SUMMA’s engine has more portability than its first Ontario criminal surface layer.
Where it appears:
Expansion strategy, engine discussion, and investor narrative.
jurisdiction modeling
Definition:
Jurisdiction modeling is the structured process of adapting a system to the procedure, terminology, forms, and expectations of a specific jurisdiction.
Plain explanation:
It is the disciplined work of making the engine fit a new legal place properly.
Why it matters:
This prevents the company from pretending Ontario success automatically translates everywhere.
Where it appears:
Jurisdiction expansion map and product strategy.
legal surface
Definition:
Legal surface is the visible outer layer of a legal product that reflects local jurisdictional language, process, and filing expectations.
Plain explanation:
It is the legal face the product shows in one specific system.
Why it matters:
Ontario is SUMMA’s first legal surface, not the full limit of the engine.
Where it appears:
Jurisdiction expansion and company narrative.
forum-specific workflow
Definition:
Forum-specific workflow is the sequence of actions, expectations, and document behavior that belongs to a particular court, tribunal, or legal forum.
Plain explanation:
It is the local way work gets done in that legal place.
Why it matters:
This often changes across jurisdictions even when deeper review pain remains similar.
Where it appears:
Jurisdiction-specific layer and translation discussion.
layer depth
Definition:
Layer depth is the degree to which the product has developed its lower and higher structural layers in a serious, working way.
Plain explanation:
It means how deep the engine has really been built.
Why it matters:
SUMMA should deepen its layers before widening too aggressively into new markets.
Where it appears:
Roadmap strategy, premium ladder, and expansion planning.
expansion phase
Definition:
An expansion phase is a staged step in the widening of the product into new jurisdictions, domains, or adjacent environments.
Plain explanation:
It is one stage in how the product expands outward.
Why it matters:
SUMMA should expand in controlled phases rather than jumping everywhere at once.
Where it appears:
Roadmap planning and market expansion discussion.
source-linked review
Definition:
Source-linked review is review work that stays tied to exact underlying source material rather than drifting into detached summaries or unsupported abstraction.
Plain explanation:
It means the review always has a clean path back to the real source.
Why it matters:
This is one of the deepest engine promises in SUMMA.
Where it appears:
Roadmap, architecture, workbench logic, and survivability discussion.
stable record identity
Definition:
Stable record identity is the preservation of what a record item is, where it came from, and how it should be returned to consistently across time.
Plain explanation:
It means the system keeps the file pieces from losing who they are.
Why it matters:
Without stable record identity, higher review layers become unreliable.
Where it appears:
Roadmap, source layer, provenance, and continuity logic.
handoff preservation
Definition:
Handoff preservation is the maintenance of usable context, posture, and structure when a file moves from one reviewer or session to another.
Plain explanation:
It means the next person does not inherit chaos.
Why it matters:
This is one of the strongest practical value points in ugly-file environments.
Where it appears:
Roadmap, workbench layer, and pilot success criteria.
posture-shift detection
Definition:
Posture-shift detection is the ability to notice when new material or new understanding changes the strategic or structural meaning of the file.
Plain explanation:
It means spotting when the case has changed shape.
Why it matters:
This is central to the pressure layer and premium support logic.
Where it appears:
Roadmap, Level 9, and pressure ranking discussion.
strategic pressure support
Definition:
Strategic pressure support is the higher-layer function of helping surface where serious human attention should go next without pretending to replace legal judgment.
Plain explanation:
It helps show where the real pressure in the file lives.
Why it matters:
This is the honest framing for SUMMA’s top premium layer.
Where it appears:
Premium ladder, messaging, demo flow, and roadmap.
wedge proof
Definition:
Wedge proof is the evidence that the product genuinely works in its first sharp, painful target lane.
Plain explanation:
It is proof that the first battlefield is real and winnable.
Why it matters:
SUMMA should prove the wedge before broadening the story.
Where it appears:
Roadmap, founder sales, and expansion strategy.
controlled expansion
Definition:
Controlled expansion is growth into adjacent jurisdictions or domains in a staged, disciplined way that preserves product identity.
Plain explanation:
It means expanding carefully instead of flailing outward.
Why it matters:
This protects SUMMA from becoming broad and weak too early.
Where it appears:
Roadmap, jurisdiction strategy, and adjacency discussion.
substrate realization
Definition:
Substrate realization is the stage at which the broader underlying engine is clearly proven to matter across more than the initial wedge.
Plain explanation:
It means the deeper engine has finally shown that it can travel.
Why it matters:
This is when SUMMA stops sounding like only a niche wedge and starts sounding like a serious reusable platform.
Where it appears:
Roadmap and long-term company story.
vertical first
Definition:
Vertical first describes a strategy that deepens the product stack within one lane before widening into many adjacent lanes.
Plain explanation:
It means build deeper before spreading wider.
Why it matters:
This is the right roadmap discipline for SUMMA.
Where it appears:
Roadmap and product strategy.
horizontal expansion
Definition:
Horizontal expansion is movement outward into new jurisdictions, domains, or adjacent use cases.
Plain explanation:
It means widening into new lanes.
Why it matters:
Horizontal expansion should come after enough vertical depth has been earned.
Where it appears:
Roadmap and expansion strategy.
product line
Definition:
A product line is a named product branch under a broader company or platform umbrella, usually tied to a specific domain or use case.
Plain explanation:
It is one product lane inside the bigger company family.
Why it matters:
SUMMA should treat SUMMA_CRIM as a product line under the broader SUMMA umbrella.
Where it appears:
Naming strategy, expansion planning, and packaging discussion.
umbrella brand
Definition:
An umbrella brand is the broader parent identity under which multiple product lines, modules, or domain variants can sit.
Plain explanation:
It is the big top-level name that holds everything underneath it.
Why it matters:
SUMMA should function as the umbrella brand while SUMMA_CRIM remains the first wedge product.
Where it appears:
Naming strategy and company story.
wedge product
Definition:
A wedge product is the first sharp product built for a narrow, painful, high-fit lane where the company can prove itself.
Plain explanation:
It is the first serious product that wins the first battlefield.
Why it matters:
SUMMA_CRIM is the wedge product beneath the broader SUMMA umbrella.
Where it appears:
Go-to-market, naming, and expansion strategy.
domain variant
Definition:
A domain variant is a version of the product adapted to a different legal or non-legal domain while preserving the same deeper engine identity.
Plain explanation:
It is the same core machine adapted to a different lane.
Why it matters:
Future SUMMA variants should be created only when the adjacent domain is real enough to justify its own identity.
Where it appears:
Naming, expansion, and product-line strategy.
package naming
Definition:
Package naming is the naming of commercial tiers or capability levels inside a product line.
Plain explanation:
It is the naming of what level the buyer gets.
Why it matters:
Package naming should answer capability depth, not confuse buyers about domain identity.
Where it appears:
Packaging strategy and product-line discussion.
module naming
Definition:
Module naming is the naming of internal functional components within a product.
Plain explanation:
It is what the pieces inside the product are called.
Why it matters:
SUMMA should keep module naming disciplined and functional rather than chaotic or theatrical.
Where it appears:
Naming strategy and internal product design.
naming discipline
Definition:
Naming discipline is the practice of keeping company, product, package, and module names clear, consistent, and structurally meaningful.
Plain explanation:
It means naming things in a way that stays clean and understandable.
Why it matters:
As SUMMA expands, naming discipline will protect wedge clarity, expansion credibility, and buyer trust.
Where it appears:
Naming strategy and brand clarity discussion.
brand architecture
Definition:
Brand architecture is the organized relationship among the company name, umbrella identity, product lines, packages, and modules.
Plain explanation:
It is the structure of how all the names fit together.
Why it matters:
SUMMA needs a clean brand architecture to avoid looking either too narrow or too vague.
Where it appears:
Naming appendix and investor/company narrative.
feature zoo
Definition:
Feature zoo is the messy state where too many features or modules are named and presented like separate mini-products without a clear structure.
Plain explanation:
It is the chaos that happens when every feature gets its own dramatic identity.
Why it matters:
SUMMA should avoid becoming a feature zoo as the engine grows.
Where it appears:
Naming strategy and module discipline discussion.
capability depth
Definition:
Capability depth is the level of engine power, workflow support, or premium functionality included in a package or offering.
Plain explanation:
It means how deep into the system the buyer is getting.
Why it matters:
Packages should reflect capability depth while product lines reflect domain identity.
Where it appears:
Packaging, naming, and premium-ladder discussion.
company identity
Definition:
Company identity is the broader stable idea of what the company is, what it stands for, and how it should be understood across products and markets.
Plain explanation:
It is the big-picture identity of the company itself.
Why it matters:
SUMMA needs to preserve a broader company identity even while the first wedge remains sharply criminal-focused.
Where it appears:
Naming strategy, investor narrative, and long-term expansion discussion.
end user
Definition:
An end user is the person who directly uses the product inside the real workflow or file environment.
Plain explanation:
It is the person living inside the tool day to day.
Why it matters:
SUMMA’s end user often feels the pain most directly, especially in severe-file review.
Where it appears:
Persona map, product design, and demo strategy.
operator
Definition:
An operator is the person responsible for actively working, maintaining, or steering the review process inside the file environment.
Plain explanation:
It is the person keeping the review work alive.
Why it matters:
Operators often care most about continuity, structure, and workbench survivability.
Where it appears:
Persona map, workflow design, and pilot evaluation.
decision-maker
Definition:
A decision-maker is the person with the authority to approve, reject, or fund adoption of the product.
Plain explanation:
It is the person who can say yes or no.
Why it matters:
The decision-maker is not always the same person as the end user.
Where it appears:
Sales motion, qualification, and buyer analysis.
internal champion
Definition:
An internal champion is a person inside the buyer organization who pushes for the product because they understand the pain clearly and want adoption to happen.
Plain explanation:
It is the insider helping the product survive and move forward.
Why it matters:
A good champion often makes the difference between interest and actual adoption.
Where it appears:
Discovery, demo follow-up, pilot strategy, and buyer mapping.
strategic audience
Definition:
A strategic audience is a higher-level audience evaluating the company or product from a market, investment, partnership, or long-term perspective rather than daily workflow use.
Plain explanation:
It is the bigger-picture audience, not the day-to-day user.
Why it matters:
This audience needs a different narrative from operators and buyers.
Where it appears:
Investor narrative, partner narrative, and company story.
pain band
Definition:
A pain band is a level of operational pain intensity used to distinguish low, moderate, high, or extreme workflow burden.
Plain explanation:
It is the level of pain the file environment is causing.
Why it matters:
SUMMA becomes more obviously valuable as pain bands rise.
Where it appears:
Persona appendix, wedge logic, qualification, and buyer fit.
strong-fit buyer
Definition:
A strong-fit buyer is a buyer whose file environment and pain profile closely match the wedge the product is built to solve.
Plain explanation:
It is the buyer who really has the problem the product is for.
Why it matters:
Strong-fit buyers are the right early battlefield for SUMMA.
Where it appears:
Qualification, go-to-market, and persona mapping.
weak-fit buyer
Definition:
A weak-fit buyer is a buyer whose current pain is too low, too different, or too generic for the product to be urgent or believable yet.
Plain explanation:
It is the buyer who may be interested, but not really ready or right.
Why it matters:
SUMMA should avoid forcing a fit where the wedge is not real.
Where it appears:
Qualification, sales discipline, and persona mapping.
workflow-aware partner
Definition:
A workflow-aware partner is a senior legal decision-maker who understands that structural workflow pain is costing the team real time and judgment.
Plain explanation:
It is the partner who sees the workflow problem clearly, not just the legal problem.
Why it matters:
This is one of the strongest early buyer types for SUMMA.
Where it appears:
Persona appendix and buyer-type analysis.
continuity-minded operator
Definition:
A continuity-minded operator is an operator who cares strongly about re-entry, handoff, and preserving file posture across time.
Plain explanation:
It is the person obsessed with not losing the thread.
Why it matters:
This person often understands the real value of SUMMA very quickly.
Where it appears:
Persona appendix and workflow-value discussion.
severe-file specialist
Definition:
A severe-file specialist is a user or buyer who regularly works in the kinds of files where disclosure, evidence burden, contradiction, and continuity pain become unusually high.
Plain explanation:
It is the person who lives in the worst files often enough to know the pain is real.
Why it matters:
This is prime wedge territory for SUMMA.
Where it appears:
Persona appendix, target-user analysis, and go-to-market.
low-burden generalist
Definition:
A low-burden generalist is a user or buyer whose matters are usually simple enough that ordinary tools still mostly work.
Plain explanation:
It is the person whose files are not painful enough yet.
Why it matters:
This is often a weak-fit early buyer for SUMMA.
Where it appears:
Persona appendix and qualification logic.
generic-AI tourist
Definition:
A generic-AI tourist is a prospect attracted mainly by broad AI excitement rather than by real severe-file workflow pain.
Plain explanation:
It is the person chasing hype more than solving a deep problem.
Why it matters:
SUMMA should avoid shaping its product story around this kind of buyer.
Where it appears:
Qualification, sales discipline, and buyer-fit analysis.
pure admin buyer
Definition:
A pure admin buyer is a buyer whose main problems are operational administration, such as billing, intake, contacts, or broad practice management, rather than severe review structure.
Plain explanation:
It is the buyer whose problem is mostly office admin, not ugly-file review.
Why it matters:
This is usually not SUMMA’s sharpest early lane.
Where it appears:
Persona appendix and weak-fit buyer discussion.
too-early believer
Definition:
A too-early believer is a prospect who understands the idea and may even like it, but whose current pain has not yet become severe enough to justify serious adoption.
Plain explanation:
It is the person who gets it, but does not need it badly enough yet.
Why it matters:
This kind of prospect should often be kept warm rather than forced into the wrong sales motion.
Where it appears:
Qualification and buyer-fit discussion.
drift
Definition:
Drift is the gradual loss of clarity, discipline, or alignment between product, company story, wedge, naming, and execution.
Plain explanation:
It means the company slowly stops being exact about what it is.
Why it matters:
Drift is one of the biggest risks to SUMMA because it can weaken the wedge, the moat, and the whole story without one obvious dramatic failure.
Where it appears:
Risk analysis, strategy, and product discipline discussion.
summary drift
Definition:
Summary drift is the weakening of trust that happens when summaries, abstractions, or higher-order interpretations become detached from exact source return.
Plain explanation:
It means the summary starts replacing the source instead of staying tied to it.
Why it matters:
This can make the product look smart while becoming less safe and less trustworthy.
Where it appears:
Risk analysis, source-linked review, and product integrity discussion.
feature zoo
Definition:
Feature zoo is the messy state where too many features, mini-products, or named modules accumulate without a clear structure.
Plain explanation:
It is the chaos that happens when every idea becomes its own thing.
Why it matters:
This can kill clarity, weaken demos, and confuse buyers.
Where it appears:
Naming strategy, product discipline, and risk analysis.
fake premium layering
Definition:
Fake premium layering is the practice of selling higher-order strategic or intelligence claims before the lower structural layers are truly strong enough to support them.
Plain explanation:
It means promising the fancy top layer before the base is real.
Why it matters:
This is especially dangerous around Level 9 and strategic-pressure language.
Where it appears:
Risk analysis, premium ladder, and messaging discipline.
weak-fit customer capture
Definition:
Weak-fit customer capture is the process by which a company starts optimizing around buyers who are easier to reach but do not actually match the wedge strongly.
Plain explanation:
It means the wrong customers slowly start reshaping the product.
Why it matters:
This can pull SUMMA away from severe-file pain and toward weaker, less defensible lanes.
Where it appears:
Risk analysis, go-to-market, and buyer-fit discussion.
moat delusion
Definition:
Moat delusion is the false belief that the company already has a durable advantage before the product proof, workflow value, and wedge ownership are truly strong enough to justify that belief.
Plain explanation:
It means thinking you have a moat before you’ve earned it.
Why it matters:
This can make the company complacent, inflated, or strategically sloppy.
Where it appears:
Risk analysis, investor narrative, and company discipline.
narrative inflation
Definition:
Narrative inflation is the gap that opens when the company story becomes broader, smarter, or more impressive-sounding than the actual product proof.
Plain explanation:
It means the story gets bigger than the truth.
Why it matters:
Once narrative inflation gets ahead of product reality, the company becomes fragile.
Where it appears:
Risk analysis, investor narrative, and messaging discipline.
buyer inertia
Definition:
Buyer inertia is the resistance buyers show to adopting a new workflow even when the pain is real, because habits, current tools, and organizational friction are hard to change.
Plain explanation:
It means people keep doing the old thing even when the old thing hurts.
Why it matters:
SUMMA has to beat not only competing products, but also workflow inertia.
Where it appears:
Risk analysis, sales motion, and pilot design.
category confusion
Definition:
Category confusion is the failure of buyers to understand what kind of product the company actually is because its positioning overlaps too many adjacent categories.
Plain explanation:
It means people can’t tell what box the product belongs in.
Why it matters:
If buyers cannot place SUMMA clearly, sales and trust weaken.
Where it appears:
Risk analysis, positioning, and competitor discussion.
operational slippage
Definition:
Operational slippage is the weakening of execution quality when good ideas fail to become usable demos, credible workflows, or repeatable buyer experiences.
Plain explanation:
It means execution starts slipping even if the ideas are strong.
Why it matters:
A company can lose not only because the idea is wrong, but because it cannot operationalize the idea well enough.
Where it appears:
Risk analysis and execution planning.
wedge erosion
Definition:
Wedge erosion is the weakening of the company’s first sharp, painful, high-fit lane because of broadening, weak-fit customers, vague messaging, or expansion before proof.
Plain explanation:
It means the first battlefield stops being sharp.
Why it matters:
If the wedge erodes, the company loses one of its strongest forms of discipline and protection.
Where it appears:
Risk analysis, go-to-market, and expansion strategy.
disciplined pessimism
Definition:
Disciplined pessimism is the practice of looking clearly at failure modes, risks, and weak points without falling into panic or vagueness.
Plain explanation:
It means being sober about what could go wrong.
Why it matters:
This is one of the healthiest ways to protect a serious company from self-deception.
Where it appears:
Risk appendix and company strategy.
structural reliability
Definition:
Structural reliability is the degree to which the lower layers of the system are stable, trustworthy, and strong enough to support serious higher-layer use.
Plain explanation:
It means the base of the system is solid enough to build on.
Why it matters:
SUMMA should not move upward into premium claims before structural reliability is real.
Where it appears:
Execution sequencing, lower-layer proof, and product discipline.
inhabitable review
Definition:
Inhabitable review is a review environment that a serious user can re-enter, navigate, and continue using without repeatedly rebuilding context from scratch.
Plain explanation:
It means the file becomes livable, not just stored.
Why it matters:
This is one of the clearest practical milestones in SUMMA’s first year.
Where it appears:
Execution sequence, workbench logic, and continuity discussion.
pressure-value gate
Definition:
A pressure-value gate is the proof threshold showing that ranked attention and pressure surfacing are useful enough to influence real review behavior.
Plain explanation:
It is the point where the pressure layer becomes actually useful, not just interesting.
Why it matters:
SUMMA should not overclaim the premium layer before this gate is met.
Where it appears:
Execution appendix and premium-ladder proof logic.
commercial-proof gate
Definition:
A commercial-proof gate is the threshold at which strong-fit buyers can see, verify, and repeatably recognize the product’s value without narrative inflation.
Plain explanation:
It is the point where buyers can believe the product for real reasons.
Why it matters:
This is what should exist before broader sales or expansion claims.
Where it appears:
Execution appendix, pilots, demos, and go-to-market discipline.
dependency order
Definition:
Dependency order is the build sequence determined by what later layers require from earlier layers in order to work honestly.
Plain explanation:
It means building things in the order they actually depend on each other.
Why it matters:
SUMMA should sequence execution by dependency, not by excitement.
Where it appears:
Execution appendix and roadmap discipline.
sequence gate
Definition:
A sequence gate is a proof checkpoint that must be met before the company should move to the next build or expansion stage.
Plain explanation:
It is a checkpoint you have to earn before moving on.
Why it matters:
This keeps SUMMA from pretending that time passed equals progress earned.
Where it appears:
Execution appendix and roadmap sequencing.
proof ladder
Definition:
A proof ladder is the ordered chain of evidence the company must earn as it moves from lower-layer reliability to higher-layer claims and broader expansion.
Plain explanation:
It is the step-by-step proof staircase.
Why it matters:
SUMMA should climb the proof ladder instead of jumping straight to broad stories.
Where it appears:
Execution sequencing and expansion discipline.
mis-sequencing
Definition:
Mis-sequencing is the mistake of building, selling, or expanding layers out of order, especially when higher claims are made before lower proof exists.
Plain explanation:
It means doing the right things in the wrong order.
Why it matters:
Mis-sequencing is one of the easiest ways to waste the first year.
Where it appears:
Execution appendix and company-risk discussion.
market education
Definition:
Market education is the process of helping an audience understand that a real problem exists and why it deserves a stronger category of solution.
Plain explanation:
It means teaching the pain before selling the product.
Why it matters:
SUMMA needs market education because many prospects feel the pain without yet having a clean name for it.
Where it appears:
Advertising, awareness content, and demand-creation strategy.
demand creation
Definition:
Demand creation is the process of generating interest by helping the market recognize a problem and its importance before buyers are actively shopping for a solution.
Plain explanation:
It means creating the want before the search begins.
Why it matters:
SUMMA likely needs demand creation early because severe-file structural pain is real but not always cleanly named in the market.
Where it appears:
Advertising, funnel strategy, and founder-led marketing.
demand capture
Definition:
Demand capture is the process of converting people who already know they want a solution and are actively looking for one.
Plain explanation:
It means catching demand that already exists.
Why it matters:
SUMMA needs demand capture too, but early on it may need demand creation even more.
Where it appears:
Funnel strategy and conversion discussion.
awareness stage
Definition:
The awareness stage is the stage of the funnel where the audience first recognizes that a meaningful problem exists.
Plain explanation:
It is the moment the person realizes, “yes, this is a real issue.”
Why it matters:
SUMMA awareness content should teach pain, not pitch product too aggressively.
Where it appears:
Marketing funnel and content strategy.
consideration stage
Definition:
The consideration stage is the stage of the funnel where the audience begins comparing categories, approaches, and possible solutions.
Plain explanation:
It is when the person asks, “what kind of thing solves this?”
Why it matters:
This is where SUMMA should clarify how it differs from practice management, eDiscovery, chronology tools, and generic AI products.
Where it appears:
Marketing funnel, comparison content, and category positioning.
conversion stage
Definition:
The conversion stage is the stage of the funnel where a qualified prospect is ready to take a concrete next step.
Plain explanation:
It is when the person is ready to act.
Why it matters:
SUMMA conversion content should ask for a serious next step, not try to re-educate the whole market from zero.
Where it appears:
Landing pages, demo requests, and pilot calls to action.
channel strategy
Definition:
Channel strategy is the deliberate choice of where and how the company communicates with the market.
Plain explanation:
It is the plan for which places the message should go through.
Why it matters:
SUMMA should stay narrow and high-signal in its early channel choices.
Where it appears:
Advertising, demand creation, and founder-led marketing.
founder-led marketing
Definition:
Founder-led marketing is marketing driven directly by the founder’s voice, thinking, and direct understanding of the pain the product is built for.
Plain explanation:
It is the founder teaching the market directly.
Why it matters:
This is often the strongest early marketing style for a sharp and nuanced wedge product like SUMMA.
Where it appears:
Demand creation and early-stage channel strategy.
landing-page logic
Definition:
Landing-page logic is the disciplined structure of a page designed to move a qualified visitor toward one clear next step.
Plain explanation:
It is the rule for what a serious landing page should do and not do.
Why it matters:
SUMMA landing pages should stay narrow, clear, and pain-specific.
Where it appears:
Conversion strategy and public marketing.
qualified curiosity
Definition:
Qualified curiosity is interest from the kind of person whose pain profile actually matches the wedge the product is built for.
Plain explanation:
It is curiosity from the right kind of prospect, not just random attention.
Why it matters:
SUMMA advertising should create qualified curiosity, not empty buzz.
Where it appears:
Advertising and demand-creation strategy.
content marketing
Definition:
Content marketing is the use of useful public-facing material to educate, attract, and move qualified audiences through the funnel.
Plain explanation:
It means using strong content to earn attention and trust.
Why it matters:
SUMMA’s early public motion should rely heavily on pain-first educational content.
Where it appears:
Awareness and consideration-stage strategy.
proof point
Definition:
A proof point is a concrete piece of evidence that supports the company’s claim that the product solves a real pain in a meaningful way.
Plain explanation:
It is a believable reason to trust the claim.
Why it matters:
Proof points are essential in moving prospects from interest to serious consideration.
Where it appears:
Marketing, sales, pilots, and landing-page strategy.
positioning statement
Definition:
A positioning statement is a concise explanation of who the product is for, what problem it solves, and how it is meaningfully different from alternatives.
Plain explanation:
It is the short clear statement of what the product really is.
Why it matters:
SUMMA needs strong positioning to avoid category confusion and generic-AI noise.
Where it appears:
Marketing, messaging, and company story.
CTA
Definition:
CTA stands for call to action, the explicit next step the audience is being asked to take.
Plain explanation:
It is the action button or ask.
Why it matters:
SUMMA should use narrow, serious CTAs instead of vague or noisy ones.
Where it appears:
Conversion-stage content and landing pages.
retargeting
Definition:
Retargeting is the practice of showing follow-up marketing to people who have already interacted with the company’s content or site.
Plain explanation:
It means following up with people who already showed interest.
Why it matters:
Retargeting can support SUMMA later, once the funnel is mature enough.
Where it appears:
Advertising and channel strategy.
qualified lead
Definition:
A qualified lead is a prospect whose pain, role, and context make them a believable fit for the product’s wedge.
Plain explanation:
It is a lead that is actually worth talking to.
Why it matters:
SUMMA should prefer fewer qualified leads over broad noisy attention.
Where it appears:
Demand creation, conversion, and sales qualification.
ICP
Definition:
ICP stands for ideal customer profile, the description of the kind of buyer or organization the product is best built to serve.
Plain explanation:
It is the clearest picture of the right kind of customer.
Why it matters:
SUMMA’s ICP should stay aligned with severe-file structural pain, not drift into weak-fit categories.
Where it appears:
Marketing, sales, positioning, and expansion planning.
nurture sequence
Definition:
A nurture sequence is a structured series of follow-up communications designed to move an interested prospect toward a more serious stage of engagement.
Plain explanation:
It is the follow-up path that warms someone up over time.
Why it matters:
SUMMA may use nurture sequences for prospects who recognize the pain but are not yet ready for a demo or pilot.
Where it appears:
Demand creation and conversion strategy.
source discipline
Source discipline is the practice of preserving exact awareness of what a record item is, where it came from, what body it belongs to, what state or version it is in, and how to return to it precisely. In SUMMA, source discipline is one of the main protections against drift, false summary, and later strategic thinking becoming detached from the record.
source preservation
Source preservation is the act of keeping the identity, provenance, and return path of record material intact as higher-order structures are built above it. It means the source object remains recoverable even when the reviewer is working through bundles, workbench views, summaries, or pressure-ranked problem zones.
contradiction zone
A contradiction zone is a region of the file where multiple forms of inconsistency, instability, omission, or cross-pressure gather around the same witness, event cluster, timeline band, or issue area. It is more serious than one isolated contradiction because it represents a structured hotspot of evidentiary or interpretive strain.
witness pressure
Witness pressure is the burden created when human accounts begin pressing against one another or against surrounding evidence in ways that destabilize confidence. It includes omission, sequence conflict, confidence mismatch, reinterpretation, contradiction, memory weakness, and interaction with external records.
technical-evidence pressure
Technical-evidence pressure is the instability created when forensic, scientific, or media-heavy evidence appears important but remains difficult to interpret safely. It arises where method, scope, timing, identity, completeness, or technical limitation materially affect how much trust can be placed in the evidence.
procedural pressure
Procedural pressure is the burden created when disclosure handling, admissibility questions, investigative sequence, continuity issues, or other procedural developments begin affecting how safely the file can be understood. It marks areas where process is no longer background and starts changing the practical reading of the case.
theory pressure
Theory pressure is the strain placed on the current working understanding of the case when multiple issue lines begin converging into a broader challenge to posture, strategy, or interpretation. It usually signals that the reviewer is moving beyond isolated issues and into a possible reshaping of the file’s overall meaning.
disclosure burden
Disclosure burden is the difficulty created not just by the volume of disclosure, but by its unevenness, instability, corrections, duplicates, later additions, and shifting significance over time. In severe files, disclosure burden is as much about changing relationships as it is about page count.
modern intake
Modern intake is the real-world arrival condition of a case in a contemporary disclosure and review environment. It includes first productions, later drops, corrections, supplemental materials, and early structural pressures that emerge before the file has stabilized.
monster case
A monster case is a file severe enough in volume, contradiction, timing burden, witness difficulty, evidentiary complexity, disclosure instability, and cognitive punishment that ordinary review habits start failing. In the SUMMA worldview, monster cases are the clearest test of whether the system is structurally serious.
issue bundle
An issue bundle is a structured working unit that gathers the source material, contradictions, timing context, and current uncertainty surrounding one real problem inside the case. It is more than a folder of related documents; it is a named, returnable problem zone that can be worked, updated, and handed off without collapsing back into raw file mass.