Meet the Founder
W. Justin Fournell-Baker
Founder and Principal Architect, EM-NOUS Technologies
“When humanity gives thought to mathematics, it may discover that the meaning of life was never hidden in an answer, but in the pattern that taught existence to question itself.”
The Concern
Capability is not the same as continuity, stability, or responsibility.
Some people fear that artificial intelligence will eventually become too capable. My concern is more immediate.
We are increasing the capability of artificial systems faster than we are developing architectures for continuity, regulation, responsibility, and meaningful awareness of consequence.
EM-NOUS is my attempt to investigate that problem through working software.
The Questions
Five questions I ask of a system.
I’m not interested only in whether a model can produce a better answer. I’m interested in the system producing that answer.
- Can it carry meaningful state forward?
- Can memory change its future processing without reducing identity to a static profile?
- Can it initiate reflection without waiting for a user?
- Can it preserve continuity while remaining correctable?
- Can safety exist as part of the surrounding architecture rather than only as words in a prompt?
Those questions became the foundation of EM-NOUS.
The Path
From philosophy to working architecture.
I · The Beginning
The questions came first.
My path to EM-NOUS Technologies began with questions about life, consciousness, meaning, information, and the stability of complex systems.
Long before there was a company, there were the questions themselves. What allows a complex system to endure? How does information become meaning inside a living thing? What keeps a mind coherent while everything around it — and within it — changes? Those questions felt connected to me, and the conviction that they belong together is the oldest part of this work.
II · The Philosophical Era
Conscious Relativity set the direction.
Early work, including Conscious Relativity, approached those questions philosophically and speculatively. It explored whether relationships among matter, energy, information, consciousness, and thermodynamics might be understood within a broader conceptual framework.
I hold that era honestly. That early work was not a validated scientific theory, and I say so plainly, because honesty about the status of one’s own ideas is where scientific discipline begins. Its importance was that it established the direction of the inquiry — a speculative map drawn before the territory could be surveyed — and it taught me the difference between having an idea and having a result.
III · The Turn
From interpretation to engineering.
Over time, I became less interested in making broad claims about consciousness and more interested in identifying functions that could actually be engineered, observed, interrupted, compared, and tested. The inquiry moved from metaphysical interpretation toward computational architecture.
That turn changed how I work. A function you can engineer is a function you can observe; a function you can observe is one you can interrupt, compare, and be wrong about. Building replaced arguing. The questions stayed the same — the method finally became worthy of them.
The responsible position is to test what has been built.
The Standard
The standard I hold my own work to.
Testing needs a yardstick, so I wrote one. The EM-NOUS Standard for Emotionally Intelligent AI — now in Revision 2, August 2026 — guides the design, development, deployment, evaluation, and governance of emotionally intelligent, persistent AI, drawing on the voluntary NIST AI Risk Management Framework and designed to track selected regulatory obligations now in force in major jurisdictions. It is written to be auditable: every requirement is phrased so that conformance can be evidenced by records rather than assertion. It is a living document, formally reviewed as the field and the law evolve, and it binds our own systems first.
Explore the Standard on the Company pageMy Role
Ten responsibilities, one architect.
Every layer of this work is mine to answer for. Each of the ten roles below was carried by one person, end to end — from first conception to the system running today. These are the roles I carry.
- Original System Conception
- Coming up with the core idea and overall vision for the system.
- Cognitive and Control Architecture
- Designing how the system thinks, makes decisions, and manages its processes.
- Mathematical Formalization
- Defining the system’s behavior using clear mathematical models.
- Software Implementation
- Building the system in code so it can actually run.
- Testing and Validation Design
- Creating ways to check that the system works correctly and reliably.
- Security and Deployment Oversight
- Designing, testing, and documenting security controls and safety-relevant boundaries, without claiming safety has been proven.
- Scientific Claim Discipline
- Ensuring all claims about the system are accurate and supported by evidence.
- Technical Documentation
- Writing clear explanations of how the system works and how to use it.
- Intellectual-Property Stewardship
- Managing and protecting the system’s ideas and innovations.
- Research and Institutional Strategy
- Planning long-term research goals and how the system fits into larger organizations.
The Work So Far
Built, running, and documented.
The record as it stands: three implemented results and one product layer in development. Each of these exists as running software and records, not as plans.
Implemented
An Architecture in Continuous Operation
EM-NOUS is an implemented, persistent-state architecture that runs continuously. Internal state survives shutdown and restart, and a cold start is a resume.
Specified
A Formal Model of Internal State
The system's internal state is formally modeled and documented. Selected variables are computed and stored on every turn and can shape the conditions of generation.
Evidenced
Auditable Decision Evidence
Governed turns produce retained technical records that support reconstruction and evaluation of the control path.
In Development
The EM-NOUS Governor
In development: a persistent governance layer, productized from the working architecture, for artificial intelligence systems that maintain memory, internal state, and autonomous activity across time. The path to deployment runs through controlled evaluation.
Looking Ahead
Beyond what a system can do.
EM-NOUS is being prepared for further technical evaluation, intellectual-property development, and responsible institutional engagement.
Each of those phrases is deliberate. Further technical evaluation means the system’s record — its behavior, its decisions, its evidence — goes before rigorous review under controlled conditions, where it can be examined rather than taken on faith. Intellectual-property development means the innovations inside this work are being formalized and stewarded with the seriousness lasting work deserves. Responsible institutional engagement means technical depth is shared through an expressly authorized confidential process, with partners who take both the science and its consequences seriously.
The future of AI is not only about what a system can do. It is also about what persists within the system, what governs it, what it remembers, what it can revise, and what prevents capability from becoming detached from consequence.
That is the layer EM-NOUS is being built to investigate.
W. Justin Fournell-Baker
Continue the Inquiry
Serious questions deserve a direct conversation.
Commercial evaluation, research collaboration, licensing, and investment conversations all begin the same way. Reach out, and technical depth follows through an expressly authorized confidential process.
Contact Me
