CADMUS LABS / ABOUT
01 / ABOUT CADMUS LABS
Cadmus Labs begins with a tendency to question systems that have become difficult to question.
Complex systems rarely begin as irrational systems. They evolve over time—through regulation, changing incentives, technological limitations, institutional priorities, necessary compromises, and solutions to problems that existed at the time.
Eventually, however, complexity can become self-perpetuating. Processes created to solve one problem create others. Layers accumulate. Assumptions harden. And "that's how the system works" can begin to substitute for asking whether the system should still work that way.
Cadmus Labs was created to keep asking that question.
The premise is not that complexity is inherently bad, institutions are inherently flawed, or every established system should be disrupted.
Some complexity is unavoidable. Some exists for good reason. And replacing an established system with something new can introduce consequences that are worse than the problems it was intended to solve.
But when a problem persists despite repeated attempts to improve the machinery surrounding it, there may be value in examining the structure underneath it.
Cadmus Labs exists to investigate those problems from first principles: to understand why a system behaves as it does, distinguish necessary complexity from accumulated complexity, and explore whether a different architecture could produce a better result.
That approach grew from firsthand experience with institutions whose outcomes can depend heavily on administrative processes, fragmented responsibilities, opaque decisions, and incentives that are difficult for the people relying on them to see or influence. Over time, those experiences made the influence of system design increasingly difficult to ignore. Structures, incentives, and administrative processes can shape institutional behavior for decades, even as the circumstances that originally produced them change.
Dental benefits became the first place where that broader perspective intersected with deep domain experience and a problem substantial enough to pursue.
Nearly two decades inside dental practice provided a view of the system from within: rising costs, administrative friction, delayed payments, reimbursement pressure, and the growing distance between what patients and providers expect from coverage and how that coverage often functions in practice.
What began as questioning that particular system eventually became something larger: an effort to understand which problems were inherent to providing coverage, which were consequences of the architecture used to administer it, and whether some of those assumptions could be reconsidered rather than inherited.
That investigation became BOCA.
And BOCA became the first undertaking of Cadmus Labs.
The name Cadmus reflects much of the philosophy behind that work.
It comes from an ancient story of confrontation, transformation, and ultimately creation—of building something new from what came before.
02 / ABOUT CADMUS LABS
The name Cadmus comes from one of the oldest foundation stories in Greek mythology.
Cadmus was a Phoenician prince who, according to the mythic tradition, became the founder of Thebes. Before the city could be established, he confronted and killed a dragon guarding a sacred spring. Athena then instructed him to sow the dragon's teeth into the earth. From them emerged a group of armed men known as the Spartoi—the Sown Men. After fighting among themselves, five remained. Those survivors became Cadmus's allies and were remembered as ancestors of Thebes' founding families.
The parallels are imperfect, but they resonated—and seemed fitting for what Cadmus Labs is attempting to build.
For us, the dragon came to represent chaos and entrenched complexity: the difficult problem that must first be confronted before something different can be built.
Then come the dragon's teeth.
That part of the story carried an especially fitting parallel: Cadmus Labs was founded by a dentist, and the first difficult system it set out to confront was dental.
Then Athena—the goddess associated with wisdom and strategic thought—instructed Cadmus to sow what remained of the dragon. From those teeth emerged the people who ultimately helped him establish something larger than he could have created alone.
The parallel felt particularly relevant to BOCA. Cadmus Labs is confronting a deeply established system and attempting to build an alternative. But the architecture has also been designed with participation in mind from the beginning. The first step must create practical value on its own. If that value earns trust and participation, some of those early participants may eventually become part of the community that helps inform, shape, and build what follows.
Something that begins as an attempt to solve a problem can become the foundation for a community capable of building something larger.
The mythology carries one additional parallel. Ancient tradition credits Cadmus with bringing Phoenician letters to Greece—an association with the transmission of an alphabet that helped enable new forms of communication and coordination.
Cadmus Labs is also interested in infrastructure: the rules, technologies, relationships, and shared mechanisms that allow people to coordinate differently.
The parallels are not intended as a literal retelling of the company's strategy. They are simply part of why the name felt appropriate.
Cadmus is a story about confronting something difficult, gathering others around what emerges, and building from there.
And Labs describes the method: investigate, build, test, learn, and revise.
The name came to reflect a philosophy that was already taking shape through the work.
What began as questions about a problem experienced firsthand gradually became BOCA, evolving as each answer revealed another problem that needed to be solved.
03 / ABOUT CADMUS LABS
BOCA did not begin as the architecture described across this website.
It began with questions.
Years inside dental practice had exposed recurring problems in the relationship among patients, practices, and dental benefits. What initially seemed like individual frustrations became harder to view independently. Reimbursement pressure connected to provider participation. Administrative burden connected to cost. Patient affordability connected to coverage design. Each question exposed another part of the system.
Following those connections changed the nature of the problem.
What began as an attempt to imagine a better dental-benefit model gradually became an investigation into how coverage is funded, administered, verified, coordinated, and governed—and which parts of that structure might be reconsidered or rebuilt.
The first ideas were imperfect.
Some assumed technology could solve problems that turned out to be economic, regulatory, actuarial, clinical, or behavioral. Others underestimated why existing systems had developed the complexity they carry today.
Working through those limitations forced the idea to evolve.
Research led to business-model work. Business-model questions led to economic and regulatory questions. Those questions exposed technical requirements. Technical work raised new questions about identity, privacy, verification, trust, incentives, and governance.
The result was not a single moment of invention. BOCA developed by repeatedly following the problem wherever it led.
That process also changed the role of technology within the project.
Blockchain was part of BOCA's earliest conception and remains part of its proposed architecture. But as the problem became better understood, the architecture expanded around it. Questions of clinical verification helped give rise to DentAI. Questions of identity, continuity, privacy, and trust led to Rootprint. Questions of affordability led to Rootline. Other requirements proved better suited to conventional software, financial infrastructure, or other technologies.
BOCA itself grew to describe that larger system. The name retains a deliberate connection to both the project's technological origins and its beginnings in dentistry—boca means “mouth” in Spanish and, from inception, has also served as the acronym for Blockchain Orchestrated Care Alliance. As the architecture has evolved, BOCA has evolved with it: rooted in where the project began without allowing any single technology to define where it can go.
That evolution has been additive rather than doctrinal: understand the problem more completely, identify the capabilities it requires, and use the technologies that can satisfy those requirements responsibly.
The architecture will continue to evolve as those choices are tested. The problem remains the constant.
The same process shaped not only what BOCA became, but how Cadmus Labs decided to pursue it.
BOCA Direct emerged as the practical commercial starting point: something that can create value for dental practices independently while generating operating experience, relationships, and evidence.
BOCA Prime developed as the larger coverage hypothesis—one that should be informed by what Cadmus learns from the work that comes before it.
The sequence became part of the architecture: build what can create value now, learn from real participation, and allow evidence to inform what earns the right to come next.
That evolution reflects more than the history of BOCA.
It reflects how Cadmus Labs intends to work: begin with the problem, make the reasoning visible, test assumptions, and allow better evidence to change the answer.
04 / ABOUT CADMUS LABS
Ambitious ideas create a particular kind of risk: the larger the vision becomes, the easier it is to become invested in proving the vision right.
Cadmus Labs is being built around a different discipline.
Ideas should be challenged. Assumptions should be visible. Important decisions should have reasons behind them. And when evidence changes the answer, the work should be allowed to change with it.
The principles below are intended to make that discipline part of how the company operates.
Technology is useful when it solves a problem better than the available alternatives.
Cadmus begins by asking what a system needs to accomplish, where the existing constraints actually come from, and which capabilities are required to address them. Only then should a particular technology earn a place in the architecture.
That standard applies whether the technology is conventional software, artificial intelligence, blockchain, cryptography, or something else.
Important decisions deserve more than conclusions.
Cadmus documents the reasoning behind major architectural and strategic choices so that assumptions can be examined, challenged, and revisited as new information becomes available.
Where appropriate, Cadmus makes that reasoning available alongside the work itself. Showing how a conclusion was reached can be as important as showing the conclusion.
Cadmus Labs is pursuing ideas that extend well beyond what has been proven today.
That distinction should remain visible.
Products being built should be distinguished from future architecture. Research should be distinguished from validation. Hypotheses should be identified as hypotheses. Possibility should not be presented as inevitability.
Ambition becomes more credible when the remaining uncertainty is acknowledged rather than concealed.
A larger vision does not make every part of that vision necessary.
Cadmus intends to build in stages so that each stage can produce evidence relevant to the decisions that follow. BOCA Direct should create practical value independently. What it teaches Cadmus may inform BOCA Prime. What Prime eventually demonstrates—or fails to demonstrate—should influence which parts of the broader architecture deserve further development.
Evidence precedes expansion.
The architecture described today is the product of repeated revision, and that process is expected to continue.
An idea should not survive simply because Cadmus Labs proposed it first. Technologies, business models, assumptions, and even parts of the architecture should remain open to challenge when evidence suggests a better answer.
The objective is to build something that works—not to preserve the elegance of the original plan.
These principles describe how Cadmus Labs intends to approach the work.
The perspective behind them, however, did not begin in a laboratory or a technology company. It developed through years spent working inside the problem itself.
05 / ABOUT CADMUS LABS
Cadmus Labs was founded by Chris Wiles, DDS, a practicing dentist and independent practice owner with nearly two decades spent working directly with patients and navigating the operational and economic realities of dental practice.
That experience provided more than familiarity with dentistry. It provided a view of the relationships among care, coverage, practice economics, administration, and patient affordability from inside the system itself.
The work that became BOCA grew from repeatedly encountering those relationships in practice and questioning why they worked the way they did.
Problems that initially appeared isolated often connected to something larger. Reimbursement affected practice economics. Administrative requirements consumed time and resources. Coverage affected the choices available to patients and the financial decisions they faced. Rising costs created pressure throughout the relationship.
Years of working within those constraints eventually led to a different kind of question:
Why hadn't dental coverage kept pace with the changing cost and reality of providing care?
The founder's experience explains where the work began. The company is being built so that where the work goes next will depend on more than any one person's perspective—bringing together additional expertise, evidence, disciplines, and people as the problems require them.
Cadmus Labs is still early.
BOCA is its first major undertaking, but the company is being built with the expectation that the capabilities, disciplines, and people required to pursue difficult problems will grow with the work.
06 / ABOUT CADMUS LABS
Cadmus Labs is still early.
BOCA is its first major undertaking, and the company's immediate responsibility is to turn that work into something real, useful, and capable of producing evidence.
But Cadmus Labs was created with a broader purpose in mind.
The long-term ambition is to build an organization capable of taking on difficult systems problems—investigating how they came to work as they do, building practical alternatives where better approaches may be possible, and allowing evidence to determine how far those ideas deserve to go.
That kind of organization cannot be built around one founder, one discipline, or one predetermined technology.
As the work develops, Cadmus Labs is intended to bring together the expertise the problems themselves require: practitioners who understand them firsthand; researchers and analysts who can interrogate the evidence; engineers and technologists who can build; legal, regulatory, financial, and economic expertise where those constraints matter; and leadership capable of turning promising ideas into durable organizations.
Growth should follow the work rather than precede it.
New capabilities, products, disciplines, and potentially new areas of investigation should be pursued when the evidence and opportunity justify them—not simply because they can be imagined.
BOCA provides the first test of that model.
If BOCA Direct creates practical value, Cadmus learns from operating a real business.
If BOCA Prime earns the evidence required to advance, Cadmus learns what it takes to develop a substantially more ambitious system.
If capabilities created along the way prove useful beyond their original purpose, the Future Architecture provides room to investigate where else they may matter.
And if some ideas fail those tests, they should change or stop.
Cadmus Labs is being built to pursue promising ideas with enough discipline to determine which deserve deeper investment, development, and ultimately the opportunity to become something real.
Cadmus Labs began by questioning one difficult system.
Where that work ultimately leads will depend on what can be built, what can be learned, and what the evidence earns the right to pursue next.
Investigate. Build. Test. Learn. Earn the next step.