Quantum Pipes Technologies LLC
The AI operating system itself.
One AI operating system, many surfaces. Lucy is the medical one. The substrate is licensed from QP Technologies LLC to Lucy in the Loop, Inc. The sovereignty is structural, the verifiability is inherited, and the clinical operating company is kept separate so the substrate can serve any domain where verifiable intelligence matters.
Lucy is one persona in the application layer. Everything beneath her is shared infrastructure. That is the licensing relationship, rendered architecturally.
Application personas
Where the OS reaches a user
Policy & audit
What makes the OS verifiable
AI runtime
What does the thinking
Sovereign hardware
The substrate the OS stands on
Three legal entities, one operating logic. Read left to right: the substrate, the company that licenses it for healthcare, the surfaces where it reaches people.
Quantum Pipes Technologies LLC
The AI operating system itself.
Lucy in the Loop, Inc.
The clinical operating company.
3 consumer surfaces.
Future siblings inherit the same chain.
See /governance for the related-party disclosure between the IP holder and the operating company.
The same licensing structure delivers a different inheritance to each kind of reader. Here is what you should expect to receive.
Lucy is auditable by your hospital's CIO, not just by us.
Because the substrate is a licensed product, any party with access to the capsule chain can audit Lucy's decisions, the literature she cited, and the model versions she ran on. The license is a public document. The chain is verifiable without our cooperation.
When you evaluate Lucy, you are evaluating Quantum Pipes.
The cryptographic posture, the sovereignty contract, the air-gap capability, the post-quantum signature primitives, all of it sits in the platform layer. Lucy in the Loop, Inc. inherits. Procurement diligence on QP transfers, in full, to Lucy.
The IP lives upstream. The clinical risk lives downstream.
The platform company holds the substrate and licenses it to any operating entity that meets the standard. The operating company carries the healthcare regulatory surface alone. Capital decisions, exit decisions, and risk decisions separate cleanly along the licensing seam.
Healthcare imposes a different liability surface than infrastructure. The two-entity structure keeps them aligned but cleanly separable. The IP holder owns the substrate and can license it to any operating company that meets the standard. The operating company carries the clinical relationships, the deployment risk, and the regulatory surface. The founder, the capital, and the board each sit on the side of the seam where they actually belong.
It also lets the same intelligence layer power non-medical siblings (Quantum Pipes itself for builders, the consumer surfaces for families, future portfolio companies for adjacent domains) without dragging the healthcare regulatory posture onto everything else. One substrate. Many sanctioned front doors.
For the cryptographic primitives Lucy inherits from the substrate, see /security. For the related-party disclosure between the IP holder and the operating company, see /governance. For the portfolio of surfaces Lucy operates across, see /portfolio.
For the parent platform itself, visit www.quantumpipes.com.