Founder’s Preface

I did not come to this project through law school, a legal-tech incubator, or a conventional software path. My working life began in a very different world: Bay Street, in the late 1990s, during the dot-com era, when markets, ambition, risk, and technological excitement were all colliding at once. That world trained certain instincts into me early. It taught me to think in systems, in pressure, in scale, and in what happens when human beings are asked to make decisions inside environments that move faster than their ability to organize them cleanly.

Even then, I had a serious amateur interest in technology. I was never interested in it only as novelty. What fascinated me was the deeper promise underneath it: could technology create order where people struggle to create it for themselves? Could it reduce friction? Could it carry cognitive burden that human beings are bad at carrying consistently? That question followed me into the next phase of my life.

When I moved into education, that instinct sharpened. I began working in elementary schools and quickly found myself overwhelmed by the sheer volume and fragmentation of the work: twenty-five children, multiple subjects, constant paperwork, constant tracking, constant content creation, constant adaptation. The work was meaningful, but it was also structurally punishing. I had to keep track of too many moving parts at once, across too many lanes, with too little support from the systems around me. This was the mid-2000s. The technology that exists now did not exist then, at least not in a form that could really rescue the workflow. A great deal of what people called organization was still just manual endurance.

That mattered to me personally because my mind has never dealt well with shapeless complexity. Living with ADHD means that clutter is not a small inconvenience. It is a force multiplier. Weak systems become heavy very quickly. Friction becomes exhausting very quickly. I have spent much of my life looking for ways to impose structure on environments that would otherwise overwhelm me. In that sense, technology has always been more than convenience to me. It has been a form of salvation. It has been the thing that could externalize order when internal order alone was not enough.

That hope was never only practical for me. It was also imaginative. Part of it was shaped by Star Trek: The Next Generation, one of the formative shows of my life. What stayed with me was not only the futurism, but the vision of a world in which human beings were no longer trapped in work purely for survival. They worked to build, to discover, to refine, to contribute — to add something to the world. Technology, in that vision, had matured to the point where it did not merely entertain people or distract them; it liberated them to do more meaningful work. That idea stayed with me. It made technology feel not only useful, but civilizational.

SUMMA grew out of that instinct.

The project began under a different name, Nova Legal, and in an earlier form it was pointed more toward legal structure and commercial-law-related work. But over time the architecture sharpened, the ambition changed, and the product became something more specific and more serious. The public-facing name became SUMMA. We chose it because the Latin force of the word felt right, and because it suggested exactly the kind of thing I wanted this system to become: not just information, not just storage, but the whole of the matter — a structured body of understanding gathered from scattered material.

The legal corporation behind the work is Roxy Nova Systems Inc. “Roxy” comes from my father, who used it for his own company, named after the famous Roxy cinema in Cairo, a place tied to memory, family, and inheritance. That corporate name may sit more in the background than the product name, but it matters to me because this project is not only commercial. It is also about legacy.

There is another thread here that matters just as much. My interest in this work is not only technical. I have long been drawn to criminal law, criminal cases, and the psychology of serious offenders. I am old enough to remember the Paul Bernardo era in the 1990s, when he still occupied the public imagination first as the Scarborough Rapist, before the full monstrosity of the case was laid bare. That case stayed with me for years. I read books about it, including books written by lawyers, and what began to fascinate me more and more was not just the evil of the crimes, but the sheer evidentiary mass they generated. The witness statements. The recordings. The forensic material. The searches. The reports. The timelines. The contradictions. The evolving disclosure. The accumulated paper trail of violence, deception, concealment, and proof. It must have filled rooms. And if a case like that produced such an immense record in the 1990s, what must similarly serious cases look like now, in a world of phones, devices, surveillance, messaging, metadata, cloud records, and permanent digital residue?

That question became a turning point for me.

I kept thinking: if the record itself becomes a kind of labyrinth, then the real challenge is no longer just storage. The challenge is how anyone thinks inside it. How does counsel survive it? How do they revisit it? How do they recognize what matters? How do they avoid drowning in noise? How do they distinguish what is merely present from what is truly dangerous? How do they build understanding rather than just accumulate files?

That is the problem SUMMA is trying to solve.

And that is also why Level 9 matters so much to me. The ambition is not merely to organize a difficult record more neatly. It is not merely to make retrieval faster. It is not merely to create a prettier folder tree. The deeper ambition is to push toward a system that can help reveal the logic of the case itself: where the pressure lives, what changes posture, what is weak but loud versus weak and dangerous, what matters now, and what should rise to the surface because it can alter how the file is understood. From a lawyer’s point of view, that is the dream: not a machine that replaces judgment, but one that helps expose the real architecture of the record so that judgment can work on something clearer, sharper, and more structured than a shapeless mountain of material.

That is where this becomes serious.

I do not want SUMMA to be a gimmick, a wrapper, or a pile of inflated claims around weak software. I want it to be precise, innovative, and genuinely useful. I want it to go vertically and surgically into painful problems that many people accept as normal because nobody has solved them properly. If there is ever a moat here, it will not come from slogans. It will come from depth, rigor, and solving the hard parts with unusual seriousness.

This manual is written in that spirit.

It is meant for smart new team members who may have little or no legal background, little or no legal-tech background, and little or no familiarity with this system, but who are capable of understanding something serious if it is explained honestly and well. It is meant to teach not only what the product does, but how it thinks, why it exists, what standards it is trying to meet, and what kind of intellectual discipline the work demands.

Knowledge matters. Structure matters. Legacy matters. And if this project grows into the kind of company I hope it can become, the people who help build it should understand the machine from the inside, not just from the marketing surface.

That is what this manual is for.