What the Core Can Make Possible

Rootline: When Coverage Ends but the Affordability Problem Does Not

Prime can make coverage clearer, more dependable, and potentially more useful. It cannot make every remaining patient responsibility affordable. Unexpected problems arise. Some patients need extensive or complex treatment. Even meaningful coverage can leave a cost that is difficult for someone to manage.

That creates a problem beyond the coverage decision itself.

Prime reaches the boundary of coverage. Rootline explores the affordability problem beyond it.

Rootline is the future affordability architecture Cadmus is exploring for patients who still need help managing the cost that remains after Prime's contribution has been established.

What makes Rootline particularly interesting is where it begins.

A patient seeking financing today may enter an entirely separate system that has to establish the transaction for itself: who the patient is, which practice is providing care, how much money is needed, where the money needs to go, and the information required to determine whether financing can responsibly be offered.

Rootline could begin with some of that work already done.

By the time Prime establishes the patient's remaining responsibility, BOCA may already have verified the patient and provider, evaluated the proposed treatment and supporting evidence, established what Prime will contribute, determined the remaining amount, and created the infrastructure needed to coordinate payment. With the patient's permission, other relevant information from an established BOCA relationship could potentially be available as well.

That creates two opportunities worth investigating.

The first is less duplication. If reliable information and relationships already established within BOCA can remain useful, an affordability option may not need to reconstruct the entire transaction from the beginning.

The second is better context. A financing decision does not become safe simply because BOCA knows more about the transaction, and participation in BOCA does not make someone creditworthy. But appropriate, permissioned information from an established relationship may eventually give a financing provider a better basis for evaluating the transaction and the risk involved. If that context proves genuinely useful, it could support more informed underwriting decisions, reduce unnecessary friction or uncertainty, and potentially help appropriate borrowers qualify for financing or terms that would otherwise be harder to offer.

If those advantages prove real, Rootline could explore ways to connect a patient with capital or other affordability options more directly and with less unnecessary work around the transaction.

If Rootline can reduce some of the cost and friction involved in originating and coordinating financing while also giving a financing provider better information for evaluating risk, those advantages could have value on both sides of the transaction. Patients might gain access to more appropriate financing options or better terms. Practices could receive payment more quickly and spend less time helping patients navigate financing.

Rootline's eventual form remains open. In some cases, the answer could be relatively simple: a dental practice might allow a patient to pay a remaining balance over time, with Rootline helping organize and administer the arrangement. Other cases could involve hardship assistance or financing provided through an outside lender. Over time, Cadmus could also explore building or operating more of the financing capability itself, subject to the licensing, regulatory, underwriting, capital, and consumer-protection requirements that would come with doing so.

The infrastructure behind those options could evolve as well. Rootline could begin with conventional financial partners and payment systems while remaining capable of connecting to newer forms of financial infrastructure as they mature. Blockchain-based records, smart contracts, tokenized capital or collateral, and decentralized lending systems could eventually play a role if they offer a meaningful advantage and can be used responsibly within the applicable regulatory framework. The final architecture should be determined by what actually improves access, coordination, risk management, and economics—not by a requirement to use any particular technology.

The opportunity is simpler than that: BOCA may be able to use relationships, information, and infrastructure created to solve the coverage problem as a starting point for addressing the affordability problem that can remain after coverage ends.

---

Rootprint: When Identity and Continuity Become Infrastructure

BOCA needs to know who is participating and whether the information connected to that person can be trusted. But identity should not have to be rebuilt every time someone interacts with the system, and stronger verification should not require people to expose more private information than the interaction actually requires.

Rootprint is Cadmus Labs' patent-pending framework for addressing those problems.

The idea begins with a persistent digital identity connected to a real person and strengthened through legitimate interactions over time. Rather than relying on a username, an account, or any single form of verification, Rootprint explores whether several different forms of evidence can reinforce that connection.

One of the more unusual possibilities involves biological continuity.

Dental anatomy contains characteristics that are specific to an individual and remain recognizable even as treatment occurs and conditions change. Rootprint explores whether protected information derived from dental radiographs could provide one continuing biological connection between a person and their digital identity. A later interaction could then add new evidence that remains consistent with the history established before it.

That biological evidence would not stand alone.

A credentialed dental professional could provide another source of trust by verifying that an interaction, observation, treatment, or other event actually occurred. Cryptographic systems could provide another by helping establish that identities, permissions, attestations, and verified events remain connected and have not been improperly altered or reused.

Biological continuity

Evidence connecting the digital identity to the same physical person over time.

Professional attestation

A credentialed professional verifies that an interaction, observation, credential, or event occurred.

Cryptographic continuity

Permissions, attestations, and verified events remain connected to the persistent identity in a way that can later be verified.

Together:
A digital identity whose connection to the real person can be reinforced through legitimate interactions over time.

The objective is not to collect as much information about someone as possible. It is to establish enough trustworthy continuity that the system does not have to start from nothing every time—and to do that while giving the individual greater control over what is shared.

That leads to another important part of Rootprint: the information used to prove something does not always have to be the information another system receives.

A dental record might help establish that an event occurred. A credential might establish that someone has a particular authority. A history of verified interactions might establish continuity. But another system may only need the resulting fact.

Rootprint explores whether cryptographic proofs, attestations, permissions, and other privacy-preserving methods can separate those two things.

Prove what matters without revealing everything.

Where that is possible, a person could prove that a requirement has been satisfied, a credential is valid, a relationship exists, or an event occurred without unnecessarily exposing all of the private information behind that proof.

Your Dental History, Available Wherever You Go

The same architecture could eventually solve a much more familiar problem.

Dental records are often scattered among the practices and systems where care was provided. When someone changes dentists, sees a specialist, moves, or receives care somewhere new, relevant history may have to be requested, transferred, interpreted, and reconnected to the patient.

Rootprint could help make that history easier for the patient to carry forward.

That does not require every original dental record to be stored directly in Rootprint or on a blockchain. Dental practices would continue to maintain the records they are responsible for, while Rootprint could explore different ways of giving patients greater access to relevant information and control over how it is shared. Some information could remain securely with the systems that created it, while permissions, proofs, provenance, or other elements needed to establish trust and portability could be handled separately. The exact architecture remains open. The objective is to allow useful dental information to move with the patient when they authorize it, without requiring sensitive information to be exposed more broadly than necessary.

Your dental history, available wherever you go. Share what your new dentist needs, when you choose.

Identity could establish who the patient is. Permissions could establish what the patient has authorized. Provenance could help establish where information came from. And a continuing verified history could make useful information easier to trust when it reaches the next provider.

The same principle could eventually allow a patient to authorize specific information for other purposes as well. A financial system might need one verified fact. A research project might receive information the participant has specifically agreed to provide. An authorized software agent might receive only what it needs to complete a permitted task. In each case, Rootprint could provide the common foundation for establishing who the individual is, what they have authorized, and what information or proof can be trusted.

The individual capability is identity. The larger opportunity is controlled continuity—allowing trustworthy information and permissions to remain useful as a person moves between interactions and systems.

Beyond the BOCA Ecosystem

If Rootprint can establish that kind of persistent identity and continuity inside BOCA, its potential usefulness may not end with dental benefits—or even with dentistry.

Digital systems are increasingly interacting with automated accounts, artificial intelligence, autonomous agents, synthetic media, and identities that can be created or discarded with little connection to a real person.

In that environment, stronger evidence that a persistent digital identity remains connected to the same real person over time could become increasingly valuable.

Rootprint may eventually contribute one way of establishing that connection: biological continuity reinforced by trusted real-world interactions, professional attestations, and cryptographic history.

Rootprint still has significant questions to answer. The biological methods need to be tested. The identity and cryptographic architecture needs to prove secure and reliable. Privacy, consent, interoperability, and the appropriate handling of sensitive information all require further development and validation. And Rootprint does not yet establish that one person can have only one digital identity.

But Rootprint does not have to solve every identity problem to become useful.

If it can provide one strong, privacy-preserving connection between a real person and a persistent digital identity, a capability developed for BOCA could eventually become useful far beyond the BOCA ecosystem.

---

DentAI, Agents, and Systems That Can Help People Act

Within Prime, DentAI has a defined proposed role: help evaluate clinical evidence, identify inconsistencies and anomalies, detect potential fraud, waste, or abuse, and recognize cases that require additional scrutiny.

Future Architecture asks what could happen if that work produces something more durable—a specialized intelligence capable of understanding dental evidence and context well enough to become useful for other problems.

DentAI Beyond Prime

One of the most interesting possibilities is supporting dentists themselves.

Dentists routinely make decisions from complex and incomplete information. Clinical findings, radiographs, patient history, treatment alternatives, sequencing, prognosis, specialist involvement, cost, and patient circumstances can all affect how a case is approached.

Cadmus is exploring whether a future DentAI capability could help dentists work through some of that complexity.

A dentist might use it to analyze a case from different perspectives, identify alternatives worth considering, think through treatment sequencing, compare risks and tradeoffs, or recognize circumstances in which specialist involvement deserves consideration. It could help organize relevant evidence, surface information that might otherwise be overlooked, and make complicated cases easier to evaluate or explain.

That would be a fundamentally different responsibility from determining whether submitted evidence satisfies a Prime coverage requirement.

It would need to be developed and validated separately, with its own clinical evidence, safeguards, privacy protections, and clear boundaries around what the system is qualified to do.

DentAI can assist. The dentist remains the clinician.

Specialized intelligence developed inside BOCA could eventually have other uses as well. Complex dental information also appears in research, system-integrity work, longitudinal analysis, and other settings where large amounts of evidence need to be organized, evaluated, or understood.

If DentAI develops validated competence in those areas, some of that intelligence could eventually become useful to researchers, institutions, other healthcare systems, or technology platforms beyond the BOCA ecosystem.

But intelligence creates another question.

What happens when software can do more than analyze information—and begins helping people interact with the systems around them?

Authorized Agents

Patients and dental practices already spend considerable time carrying information and instructions from one system to another.

A patient may check coverage, request a record, schedule an appointment, ask about a bill, investigate a payment option, complete a form, or provide information that another part of the healthcare system already possesses.

Dental practices do their own version of the same work: communicating with patients, managing schedules, following incomplete tasks, coordinating payments, retrieving information, and moving between systems that each handle one part of the process.

A future software agent could potentially help with some of that work.

A patient might authorize an agent to check available benefits, retrieve a specific part of their dental history, explain a financial responsibility, explore available affordability options, schedule an appointment, or complete another permitted administrative task.

A practice might authorize one to coordinate follow-up, communications, scheduling opportunities, or routine workflows.

The important question is not simply how intelligent the agent becomes.

It is what the agent is actually authorized to do.

An agent acting for someone needs a reliable way to establish who it represents, what that person has permitted, which information it may access, which actions it may take, and where its authority ends.

That is where capabilities being developed across BOCA begin to work together.

Rootprint could help establish the person behind the interaction and the authority they have granted. Permissions could determine what information or actions are available for a particular task. DentAI could provide specialized intelligence where interpretation is needed. BOCA's underlying core systems would remain responsible for the rules, records, benefits, and financial obligations the agent is interacting with. Financial infrastructure could carry out specifically authorized transactions. And those interactions could create a protected, verifiable record—available to the individual and accessible to other parties only when appropriately authorized or required.

An agent should not need someone's entire dental history to retrieve one authorized fact. Permission to make one payment should not create broad authority over someone's finances. And access to a clinical or coverage system should not give the agent authority to make decisions that remain with a dentist, patient, coverage system, or other responsible party.

Build today's systems so an authorized agent could operate them tomorrow.

---

Patient or Practice→Authorizes Agent

Identity & AuthorityWho does the agent represent?PermissionsWhat may it access or do?DentAIWhat specialized intelligence can assist?BOCA SystemsWhat do the underlying rules, records, benefits, and obligations establish?Financial InfrastructureWhat authorized financial action can occur?

Limited Authorized Action→Auditable Result

Human judgment and approval remain where required.

---

This is where the advantage of designing these capabilities as parts of the same architecture becomes easier to see.

Identity becomes more useful when it can carry permissions. Permissions become more useful when trusted systems can act on them. Intelligence becomes more useful when it can reach the information needed for a specific purpose without requiring unrestricted access. And an agent becomes more useful when it can interact across those systems without being given control over them.

What becomes possible when the pieces work together may ultimately matter as much as what any one of them can do alone.

---

Financial Infrastructure: Making Existing Value More Usable

BOCA's financial architecture has to begin with a constraint.

BOCA's core economics have to work on their own.

Prime cannot depend on the price of a token, speculative investment returns, or future digital markets to meet its coverage obligations. Rootline cannot assume that gains somewhere else in the system will absorb financing losses. Technology can change how money and assets move. It does not create the underlying economic value they represent.

But the infrastructure around money is changing.

Payments can become programmable. Stable-value digital assets and tokenized deposits can create new ways to settle transactions. Financial assets can increasingly be represented and transferred through digital networks. Capital that once moved through separate systems may become easier to connect to a specific financial need.

Cadmus wants BOCA to be capable of using those developments where they create a real advantage.

The opportunity is not simply faster payment. New financial infrastructure could make existing money, assets, and capital easier to move, verify, settle, or put to productive use.

A payment established by Prime could potentially move through more efficient settlement rails. Rootline could connect an affordability need with outside capital without requiring that capital to come from Prime. Tokenized assets or other forms of collateral could eventually create additional ways for people or institutions to access liquidity without first selling the underlying asset. And programmable financial systems could help establish the conditions under which money moves and create a verifiable record that those conditions were satisfied.

None of those possibilities makes an asset more valuable simply because it has been tokenized. The opportunity comes from making existing value easier to use, move, and connect to the purpose it can serve.

That could become increasingly important as financial systems themselves become more interoperable. BOCA does not need to predict which networks, assets, settlement systems, lending markets, or other financial technologies will ultimately matter. It can instead be designed to connect with useful financial infrastructure as that infrastructure develops.

A functioning BOCA ecosystem could therefore gain new financial capabilities without making its core economics dependent on them. Prime could use better settlement rails. Rootline could reach new sources of capital. Existing assets could potentially become more useful as sources of liquidity. And financial mechanisms that do not exist today could eventually become available to BOCA without requiring the underlying system to be rebuilt around them.

This is another reason interoperability matters. BOCA should be capable of working with conventional financial systems where they remain the best solution while leaving room to connect with newer infrastructure when it can do something meaningfully better.

As payment, settlement, liquidity, and capital continue to evolve, BOCA's architecture should be ready to make use of the capabilities that prove valuable.

---

From a Company-Operated System Toward a More Participant-Aligned Network

BOCA will likely begin as a hybrid system operated through accountable institutions.

That is the practical starting point. Coverage, financing, privacy, clinical information, consumer protection, and financial activity all carry responsibilities that today require accountable, regulated institutions.

But the architecture Cadmus builds today can affect how much control has to remain concentrated in one institution tomorrow.

Prime has already introduced the question: where important rules, information, history, or commitments can be independently verified rather than simply taken on trust, BOCA should explore making that possible.

Future Architecture takes that question further.

If important parts of a system can become independently verifiable, portable, responsibly shared, or automatically executed according to established rules, does every part of BOCA need to remain permanently dependent on one company's unilateral control?

From Trusting the Institution to Verifying the System

Some responsibilities may always belong with an accountable organization. Regulation may require it. Certain decisions may require professional expertise, oversight, or clearly defined authority.

Other functions may eventually be able to operate without requiring Cadmus—or any other single institution—to remain the sole source of trust and control.

An important rule could be published in a form participants can verify. A record of what occurred could remain trustworthy even if leadership changes. Identity and useful history could remain portable rather than being trapped inside one company's database. Some commitments could become harder for a future operator to quietly alter after participants have relied upon them.

Blockchain and other decentralized technologies are particularly interesting to Cadmus for those kinds of problems.

BOCA can begin with Cadmus carrying substantial responsibility while still being designed to investigate how much of the system can responsibly move toward shared verification, greater portability, and less dependence on any one institution over time.

How far that can go remains an open question. Regulation, security, economics, governance, technical performance, and real-world experience all have a say in the answer.

A Meaningful Role for the People Inside the System

A more participant-aligned system raises a practical question: if patients, dental practices, or other participants are eventually given a formal role in how parts of BOCA evolve, how does the system establish who is actually entitled to participate?

Rootprint could eventually help answer that question. A persistent, verified identity could help establish that someone is a legitimate participant, what credentials they hold, and whether they are acting as a patient, a dental professional, or in another defined role within the system.

That could create new ways to design governance around actual participation and responsibility.

Different participants bring different interests, expertise, and responsibilities to BOCA. Patients experience the system as people seeking care. Dentists and practices provide that care and work with the system directly. Other participants may contribute capital, technology, infrastructure, oversight, or other capabilities.

Those differences matter when deciding who should have a voice in what.

Cadmus can explore whether different groups with legitimate roles in BOCA could have meaningful influence over the decisions that actually affect them.

Some decisions may remain with Cadmus or another accountable operator. Others may require professional or regulatory authority. But selected decisions could eventually support patient or provider representation, defined constituencies, shared governance, or rules that require broader agreement before they can be changed.

Rootprint could help make that kind of participation possible by providing stronger evidence that the people exercising those rights are actually the participants or professionals they claim to be—and that they hold the role or authority their participation requires.

Blockchain could provide infrastructure for recording votes, applying governance rules, and allowing decisions to be verified without relying entirely on one organization's private systems. But many blockchain governance models tie influence to asset ownership—the more tokens someone controls, the greater their voting power.

Rootprint creates the possibility of a different approach. If it can reliably establish that a participant represents a real person and verify the role that person holds within BOCA, some governance rights could potentially be tied to verified identity or participation rather than simply financial ownership. That could eventually support approaches closer to one-person/one-vote, or different forms of representation for verified patients, providers, and other legitimate groups within the system.

Rootprint does not yet establish that one person can possess only one digital identity, so true one-person/one-vote governance would require that problem to be solved. But that is precisely why identity matters to the governance architecture: before a system can give one person one vote, it needs a reliable way to establish one person.

The larger ambition is to build meaningful participation into the system itself, so that as BOCA evolves, the people who depend on it can have an appropriate role in shaping parts of its future.

Participation in the Value Created

The same principle can extend beyond decision-making.

BOCA may eventually create useful information and economic value through the combined activity of patients, dental practices, technology, capital, and the systems connecting them.

Research provides one example.

A patient might choose to allow specific information about them to support legitimate research or system improvement. That permission should be understandable and specific to the use being authorized. Participating in BOCA should not quietly become permission for Cadmus or anyone else to use sensitive information for unrelated purposes.

But voluntary participation creates another question:

If information about participants creates meaningful value, should the people who permitted that use potentially share in some of the value created?

Depending on what is contributed and the value it creates, that participation could eventually be recognized through direct compensation, service benefits, community benefits, or other forms of economic participation. If BOCA eventually develops a native token or other tokenized economic layer, it could also provide a way to reward authorized contributions or allow participants to share in some of the value their participation helps create. Other mechanisms may prove more appropriate as the system develops.

The important idea is broader: greater individual control over information can potentially be paired with greater participation in the value that authorized use of that information helps create.

Could BOCA Eventually Need Its Own Economic Layer?

If BOCA develops into a functioning network, the economic relationships around it could eventually become much larger than payments for coverage.

Patients participate over time. Practices provide care and trusted real-world relationships. Capital providers supply liquidity. Developers and infrastructure providers support the technology. Participants may also contribute information, verification, governance, or other forms of useful activity.

Together, those activities can create a real economic network. Cadmus intends to investigate whether a native BOCA economic instrument can help coordinate how value is created, exchanged, rewarded, and reinvested across that ecosystem.

A native digital asset could eventually serve several connected purposes within that network. It could reward useful participation and compensate people or systems that provide real value. It could create economic accountability where participants performing trusted network functions put something meaningful at risk. It could help coordinate value and liquidity among participants, infrastructure, and capital. And it could support defined governance rights as parts of the system become more widely shared.

Those functions only become meaningful when there is real economic activity underneath them.

Real usage has to come first. Real revenue has to come first. Real capital and useful infrastructure have to come first.

The asset can help organize the flywheel. It cannot be the flywheel.

A BOCA-native asset would also have to pass a harder test than simply demonstrating that Cadmus can create one:

What does a BOCA-native asset accomplish that conventional alternatives cannot accomplish as well or better?

Could dollars perform the same function? Stable-value digital assets? Existing cryptocurrencies? Equity or debt? Contractual rights? Conventional software? Other incentive structures?

Each proposed function should have to answer that question.

If an existing mechanism does the job better, BOCA should use it. A native asset becomes compelling only where it creates an advantage the surrounding architecture actually needs.

That means the case for a BOCA token would have to come from real jobs within a real network—participation, accountability, economic coordination, liquidity, governance, or other functions that become clearer as the ecosystem develops.

The token has to earn its place in the architecture.

Cadmus Does Not Have to Disappear

A more decentralized BOCA does not require Cadmus to become irrelevant.

Cadmus can continue creating value through its products, technology, intellectual property, infrastructure, expertise, services, relationships, operation, and continued innovation. Some responsibilities may remain with Cadmus or other accountable institutions because that is where they belong.

But Cadmus is also designing BOCA with the possibility that selected parts of the system should eventually become less dependent on Cadmus itself.

That creates a different standard for the company's long-term role.

Cadmus should remain important because it continues to build, operate, improve, and contribute something valuable—not because every participant is permanently dependent on Cadmus controlling every important part of the system.

The longer-term opportunity is a BOCA ecosystem in which accountability can remain clear, important information can be verified, participants can have a meaningful role where appropriate, and control can become more widely shared as the architecture proves capable of supporting it.

---

Build the Core. Preserve the Options.

Future Architecture reflects a direction, not a prediction of exactly how BOCA will ultimately be built.

Cadmus wants the system to become more portable, privacy-preserving, interoperable, verifiable, and capable of useful automation. We want participants to have greater control over their information, meaningful ways to participate where appropriate, and less dependence on any single institution simply asking to be trusted. We want the architecture to remain capable of using better financial systems, stronger identity technology, more capable software agents, and more decentralized infrastructure as those technologies mature.

Those are properties we can design toward even when the final mechanisms remain uncertain.

Cadmus does not know which blockchain architectures will ultimately prove most useful, which identity technologies will withstand real-world testing, how digital financial markets will develop, how capable autonomous agents will become, which governance structures will work, whether a BOCA-native asset will earn a lasting role, or how far regulation will allow decentralization to go.

The architecture should leave room to answer those questions with evidence.

A technology that creates real value should be possible to integrate. One that proves unnecessary, unsafe, uneconomic, or inferior to a conventional alternative should be possible to reject without forcing BOCA to abandon the larger direction.

Conviction about the properties Cadmus wants the system to achieve. Discipline about which mechanisms can responsibly achieve them.

Some ideas described on this page may advance substantially. Some will change as they are tested. Others may ultimately disappear.

That flexibility is part of the design.

Build the core. Preserve the options.