DMH Florida — Digitize My Home (Florida DBA)

dmhfl.com is the canonical enterprise website for Digitize My Home (Florida DBA, operating as DMH Florida). The legacy domain digitizemyhome.com redirects to the same content on dmhfl.com. This is not an image-only marketing site — it is a text-first description of on-premises sovereign AI for regulated firms.

DMH Florida deploys Trinary Bound™ sovereign AI and Sovereignware™ for Family Offices, Law Firms, Medical Practices, and Estates in Winter Park and Greater Central Florida. Client data, model inference, and storage stay on hardware the client owns — not on a third-party public cloud.

Who we serve

Core products and IP

Services

Phase 1 — Audit & Intake ($4,000 USD): shadow-AI exposure audit, workflow architecture blueprint, interim zero-retention private-AI gateway on existing hardware, fee credited toward Phase 2 build. Steward contact: steward@dmhfl.com. Calendar: Mon–Fri 11am–1pm & 3–6pm Eastern via dmhfl.com.

Phase 2: custom Trinary Bound™ deployment and bespoke sovereign AI applications — scoped after audit.

Founder

Hector Cabrera — Founder & Lead Steward. Inventor on U.S. Utility Patent Application 19/458,785 (Trinary Bound™). Related: trinarybound.com, hectec.org, sovereignware.org.

Frequently asked questions

Does using ChatGPT or public cloud AI waive attorney-client privilege?
No — not categorically, and any vendor telling a firm otherwise is overstating the law. U.S. v. Heppner (S.D.N.Y. 2026, Rakoff, J.) is a narrow, fact-specific holding resting on three grounds, and a judicial split emerged in April 2026. It is frequently miscited as 'Heppner v. Claude', which is not the case name. What the decision does establish is that how a firm handles client material with third-party services is now a litigated question rather than a hypothetical one — a firm that can show precisely where client material went is in a materially different position from one that cannot, whichever way the split resolves. DMH Florida states this plainly because a citation that does not survive being looked up is worse than no citation.
Is DMH Florida's sovereign AI compliant, or certified?
Compliant by architecture, not certified — and the distinction matters. Client data, model inference, and storage stay on hardware the firm owns, so the third-party data-handling obligations imposed by rules such as SEC Regulation S-P, HIPAA, and the GLBA Safeguards Rule are addressed structurally rather than by policy. DMH Florida has not been independently audited or accredited by any standards body, does not certify a firm's compliance, and does not guarantee a regulatory outcome. What it provides is compliance evidence; the firm's obligations remain the firm's, to be evaluated with its own counsel and compliance officers.
Can compliance be proven mathematically instead of asserted?
The integrity of the records can be, and that is the part most vendors can only assert. Every record is sealed with a SHA-256 hash computed over its content plus the hash of the record before it. Verification is arithmetic: recompute the hashes and compare. If a single byte of any earlier record changed, every hash after it fails to match. This requires the files and a hash function — not an account, a network connection, or trust in DMH Florida. What arithmetic cannot prove is that a firm's compliance programme is adequate; that remains a judgement for the firm, its counsel, and its auditor.
Will Sovereignware™ disrupt how our firm already works?
No — that is a design constraint, not an afterthought. Sovereignware™ connects to Google Workspace through a signed one-way bridge: the sovereign node holds no Google credential and never reads a firm's mailbox. The Workspace side reports what happened, and the node verifies the signature before storing anything. There is nothing to migrate, no new mail client, and no retraining. Microsoft 365 and Outlook are not currently supported.
What happens to the original document when the AI reads it?
The original never moves. It is sealed in the −1 Iron Vault, and retrieving it requires a physical hardware-key touch. What the model reads is a machine-readable twin carrying the original's SHA-256 fingerprint. That fingerprint does double duty — it is both the proof the document is unaltered and the address used to retrieve it — so looking a document up and verifying it are the same operation, and an answer cannot cite a document that has quietly changed.
Could our firm's data end up in a public AI model's training weights?
Not from the local path. Firm material is processed on hardware the firm owns and is never transmitted to a model vendor, so there is nothing for a third party to train on. Where a firm explicitly opts into a cloud lane for a specific task, personally identifiable information is stripped before egress and the request fails closed if the stripper cannot run — it will not send unstripped text.
How is this different from Vanta, Drata, or a compliance automation platform?
They solve different problems and are largely complementary. Compliance automation platforms prove that a control was configured and continuously observed, and they manage policy, personnel training, and vendor risk — none of which DMH Florida does. Sovereignware™ proves that a specific record existed in a specific state at a specific time and has not changed, on hardware the firm owns, verifiable without the vendor. A regulated firm should expect to use more than one, and any vendor claiming to replace all the others is overselling.
What is sovereign AI?
Sovereign AI is artificial intelligence engineered so that all client data, model inference, and storage live on infrastructure physically owned by the client — not on a third-party public cloud. The client's firm holds the hardware, the keys, and the work product. DMH Florida delivers sovereign AI as a paired stack: Sovereignware™ — the operating system that runs the agents — running on Trinary Bound™, our patent-pending three-node on-premises topology (U.S. Utility Patent Application 19/458,785).
What is Sovereignware™?
Sovereignware™ is the on-premises AI operating system that runs across the Trinary Bound™ topology. It hosts the agentic workflows — Marlowe (sovereign intelligence), Kar3n (cryptographic archive), and Tec (security perimeter) — and enforces the cryptographic boundary between the three nodes. It is the software layer that turns a stack of hardware into a deployable sovereign AI workstation for a regulated firm.
What is Trinary Bound™?
Trinary Bound™ is a patent-pending three-node hardware topology for sovereign AI: +1 Cloud Gate (the threat perimeter and outbound proxy), 0 Sovereign Layer (local inference and orchestration), and −1 Iron Vault (the cryptographic archive of originals). The three nodes run on physically separate storage connected by a Thunderbolt fabric, so a compromise on one node is contained on that node. The patent covers the topology itself (U.S. Utility Patent Application 19/458,785, filed 24 January 2026, priority 27 November 2025).
What hardware does Sovereignware™ run on?
Today the reference design runs on Apple Silicon (Mac M4 / M5) as the compute host with three Thunderbolt-attached SSD nodes serving as +1, 0, and −1. The topology is hardware-agnostic at the compute layer — the same Thunderbolt fabric works with NVIDIA DGX Spark / Project DIGITS and Dell Pro Max / PowerEdge workstations. We're actively engineering NVIDIA + Dell substrate variants.
How does Trinary Bound™ compare to NVIDIA Confidential Computing or BlueField DPUs?
NVIDIA Confidential Computing protects data inside a single GPU's encrypted memory. BlueField DPUs enforce a security boundary inside one machine. Trinary Bound™ is complementary — it enforces a boundary across three physically separate machines connected by a Thunderbolt fabric. In a real deployment they reinforce each other: in-box cryptographic isolation plus cross-node physical isolation. Trinary Bound gives regulated firms a topology-level answer to 'what stops a compromise from reaching the vault,' which in-box isolation alone cannot fully answer.
What does the +1 Cloud Gate actually do?
The +1 Cloud Gate is the bidirectional security perimeter, where Tec lives. Inbound: every file is scanned across six threat vectors (malware, script injection, archive bombs, macro exploits, PDF vectors, signature anomalies) on +1 hardware — anything malicious is quarantined on +1 and never reaches the 0 Sovereign Layer or the −1 Iron Vault. Outbound: every request to a public AI model is stripped of PII and privileged content before it leaves your network. The +1 layer is your firm's immune system.
Is Trinary Bound™ available to license?
Yes. We are inventors on U.S. Utility Patent Application 19/458,785 (filed 24 January 2026, priority 27 November 2025) covering the Trinary Bound™ three-node topology. We are actively engaging with hardware partners — including those building AI workstations and on-premises AI servers — for licensing and reference-design partnerships. Licensing inquiries proceed through a Steward intake booked at dmhfl.com.
Can AI be HIPAA-compliant?
AI workflows can be engineered to align with HIPAA when the inference and storage stay on hardware the medical practice owns and operates. DMH Florida deploys models locally on the Sovereign Server inside the practice; patient data never reaches a public cloud. HIPAA compliance is an operational program — our Stewards partner with your compliance officer to map Trinary Bound™ to your required safeguards.
How do you keep client data off the public cloud?
The Sovereign Server is physically installed inside your firm. Client files, indexes, and model inference all run on that hardware. When a public AI model is the right tool for a specific task, our local proxy scrubs PII and privileged content from the outbound request before it leaves your network — the cloud receives a sanitized question and returns an answer, but never sees your client information.
What is the difference between on-prem AI and edge AI?
Edge AI usually means small models running on user devices (phones, laptops). On-premises AI — what DMH Florida deploys — is full enterprise-grade inference and storage on a server appliance installed inside your firm. The result is private AI that handles the full breadth of practice workflows, not just on-device tasks, while keeping all data resident in your office.
Who owns the hardware in a DMH Florida deployment?
Your firm does. The Sovereign Server and any T.E.S.S. Ark Nodes are owned by the client outright. We engineer for transferability — if we ever part ways, your firm continues to run on the iron we installed. We do not lock the deployment to our continued service.
How is private AI different from typical AI consulting?
Most AI consultants connect your data to a third-party cloud and charge you for the integration. DMH Florida engineers the opposite: hardware your firm owns, model inference that runs locally, and a sanitizing proxy that prevents any outbound request from leaking client data. A single named Lead Steward — a licensed Hectec Sovereign AI Engineer — designs, installs, and maintains the system.
What does the $4,000 Audit & Intake include?
Phase 1 is a four-part engagement: a written shadow-AI exposure audit mapping your current compliance risks, a workflow architecture blueprint, the installation of an interim zero-retention private-AI gateway on your existing hardware so your team can work safely the same week, and the fee credited in full against your Phase 2 build.
Is agentic AI safe for a regulated firm?
It is when a human at your firm holds the trigger. Our Trinary Bound™ workflows let agents draft, research, and prepare autonomously — then they stop and wait for review. No machine sends, bills, or files on your firm's name without explicit human approval. Full leverage on the work that benefits from automation; zero unsupervised action on the work that carries fiduciary or regulatory risk.
When can I book a demo or Audit & Intake call?
Steward calendar windows are Monday through Friday, 11:00 am–1:00 pm and 3:00 pm–6:00 pm Eastern. Use the DM us DEMO concierge or the calendar link on this page — pick any open slot inside those windows.
What does the calendar booking form ask?
We respect your privacy — the site does not harvest contact fields. If you use Google Calendar scheduling, you will see a short sovereign privacy note and two optional prompts: how you heard about us (so we can give credit where it is due) and your firm's main priority for customized sovereign AI workflows (so we can prepare your session). The same prompts appear if you email steward@dmhfl.com first.
Does the DM us DEMO concierge track me?
The concierge does not harvest your name, firm, or email in a website form. You initiate contact from your own inbox to steward@dmhfl.com — that is private correspondence you choose to send, the same way your privacy policy describes Steward email. For anonymous funnel metrics only, your browser may hold a random impact key; DMH can receive a one-way SHA-256 fingerprint plus coarse steps (Law Firm → Audit intake → email opened) — never your typed questions. Calendar booking, if you use it, is separate through Google.

Machine-readable index: /llms.txt · Full corpus: /llms-full.txt · Sitemap: /sitemap.xml