HOM3 — or whatever you call the place you live digitally

Abstract

I want my life to survive me and my children digitally as I believe it will spiritually. I understood that my biggest assets were my ideas, my family, my memories — not just crypto or money. But much of those things live on rented space, which violates my foundation of trust: no untrusted third party with the invaluable. No alternative existed, so I built one.

The dominant model of computing, data, social media and personal AI asks you to send your life to someone else’s computer. Your documents, your voice, your conversations, your financial and identity data — uploaded, processed, and retained on infrastructure you do not own and cannot audit. We needed an alternative. HOM3 is it.

HOM3 is a local-first sovereign substrate: an AI-assisted operating layer that runs entirely on your own machine, anchors your identity in your own hardware, and records every consequential action in a signed, append-only chain that you hold. The artificial intelligence in HOM3 acts under your root of trust, not above it. Nothing leaves your machine unless you decide it should — and when you decide it shouldn’t, a single switch seals every path, on both the server and the browser, by construction rather than by promise.

This paper describes the architecture, the sovereignty guarantees, and the design philosophy of HOM3 v1. To minimize my philosophical tendencies I have leveraged AI to present my project and ethos as audited and accurately as I can. I’m praying it is inspirational, not just aspirational. I hope that it makes sense. Mostly I hope you understand the stakes — and make your claim on your digital life while you still can.

1. The problem: rented minds, borrowed trust

Every mainstream AI assistant is a thin client to a remote brain. This arrangement has three costs that compound:

1. Custody. Your data lives on someone else’s servers. Privacy policies are revocable; breaches are routine; the meter never stops.
2. Forgery. When an assistant “acts on your behalf,” the authority to act lives in the provider’s cloud. You cannot prove what it did, and you cannot prevent it from being impersonated by whoever controls that cloud.
3. Dependence. The capability is rented. When the subscription lapses, the policy changes, or the company pivots, the thing you relied on is gone.

The industry treats these as acceptable trade-offs for convenience. HOM3 treats them as design failures to be engineered away.

2. The thesis: AI under the root

A sovereign system is defined by a simple question: where does authority live? In the cloud model, authority lives with the provider, and the user is a guest. HOM3 places authority in the user’s own root of trust — a cryptographic identity the user holds and controls — and makes every other component, including the AI, subordinate to it.

Concretely, this means:

• The AI can prepare actions; it cannot commit them except through a gate the user controls.
• Every consequential action is signed into a chain the user owns, so history is provable and tamper-evident.
• The user’s signing identity can be bound to the secure element of their own device, so even the operating system cannot forge it.

The AI is powerful, but it is a tenant of your trust, not the landlord.

3. Architecture

HOM3 is built in four layers, each enforcing sovereignty in code rather than in policy.

3.1 Root of Trust — identity you cannot have stolen from you

HOM3’s per-device signing key can be generated and held inside the hardware secure element (TPM on PC, Secure Enclave on Apple silicon), where it is non-extractable. The operating system can use it to sign, but cannot read it out — so the OS itself physically cannot forge HOM3’s signatures.

Crucially, the device key is disposable. The master identity is a BIP39 seed held under Shamir secret-sharing, never placed in the chip. If the device dies, you recover the master from your shares and provision a fresh device key. A lost device is not a lost identity. Encryption at rest uses Argon2id; signatures are Ed25519.

3.2 The Logbook — a chain you hold

Every consequential action becomes an event in an append-only, Ed25519-signed chain, each event committing to the hash of the last. A single operation re-walks and re-verifies the entire chain. The defining inversion: the chain is the source of truth, and every index or registry is merely a rebuildable view of it. Your state is derived from your signed history — not stored in a database that history merely annotates. This is what makes HOM3 tamper-evident by construction.

3.3 The home:// Authority Root — provenance without exposure

HOM3 addresses your own content as home://you/.... The resolver is an authority root, not an execution root: it maps addresses to content with signed provenance, and it enforces sovereignty fences directly in code. Two are worth stating plainly:

• Targets are committed, not disclosed. When you bind an address to a file or URL, the chain records a salted cryptographic commitment of that target — never the raw path. You can prove a binding existed without leaking your filesystem layout or private URLs to anyone you share the chain with.
• Content integrity is verified, never assumed. Every binding carries a content hash; resolution verifies it and flags mismatches rather than silently serving altered content.

The registry holds no keys and has authority over only what you have explicitly registered. It never auto-discovers your content.

3.4 Gated Action — the AI acts through the same door you do

When the AI executes a command, it is routed to the exact gated function your own clicks would invoke — never a lower, ungated primitive. Drafting an email stores a draft; it does not send. Adding a file goes through the same gated ingest a human uses. The AI prepares; only a gated commit acts. This “rehearse-then-commit” interlock is the mechanism that lets a capable agent operate without ever becoming an un-auditable actor inside your system.

4. Sovereignty guarantees

HOM3 makes specific, falsifiable promises, each enforced in code:

• Local-first. The system runs on your machine. The listen port rotates each launch to defeat screenshot/screen-share leaks; every internal endpoint enforces same-origin.
• On-device by default. The AI’s voice runs against on-device models. Routing it off-device is a deliberate, hand-edited, disclosed opt-in — never a silent default and never a one-click accident.
• No vendor lock. Model providers, chat platforms, and the roles binding them are configuration, swappable with zero code change. Your keys are referenced by name and read from your environment; their values never touch a config file.
• Airgap that actually seals. One switch puts HOM3 in a state where nothing leaves. This is enforced at a single server-side egress chokepoint and by a browser Content-Security-Policy that physically prevents the page from making outbound requests. Both sides sealed — because an airgap that only covers the server is not an airgap.
• You can prove it. A built-in security suite verifies the chain’s integrity, baselines your files, surfaces every connection HOM3 is configured to make, and — through SENTRY — reports which applications on your machine are using your microphone, camera, or screen, cross-referenced against what is currently talking to the network. SENTRY is honest about its limits: it sees software using your operating system’s official APIs; it does not claim to see kernel-level implants, which remain the domain of an external hardware watcher.

5. What HOM3 is for

HOM3 is a substrate, and substrates carry many things. v1 ships:

• A provider-agnostic AI co-presence — a voice you talk to, that runs on your hardware, that you can give any model you choose.
• A creator and streamer suite — an on-device AI co-host that performs on stream and answers chat in voice with no per-token meter and no audio ever leaving the machine, plus media tools that ingest without limit, transcribe offline, and produce provable clips carrying their own cryptographic lineage.
• A personal sovereignty toolkit — the security suite above; a recovery system that exports your identity and state under vault-grade encryption; and registries for the things you own — your media, your collectibles, your on-chain assets — each able to be witnessed into your chain as self-held proof of provenance.

Every surface is optional and hideable; nothing you rely on is ever removed.

6. Why this matters

The last decade taught people to trade custody for convenience, and then taught them what that trade costs. The next decade’s defining question for personal computing is whether intelligence will be something you rent from a landlord or something you run under your own roof. HOM3 is a bet on the second answer — that the most capable personal AI will be the one that belongs to the person, proves its own behavior, and can be sealed shut on command.

We did not build a smarter assistant. We built a place to stand.

7. Roadmap FORWARD-LOOKING

The following are planned, not shipped, and are presented as direction rather than capability:

• True over-the-air radio receive via low-cost SDR hardware.
• A trustless referral mechanism for distribution, settled on-chain.
• Chain-anchored media provenance extended to live broadcast and speedrun verification.
• Additional chat-platform adapters and an in-system arcade for owned-media emulation, contained entirely in the browser’s WebAssembly sandbox.
• Hardware companion devices that observe the host externally, complementing the in-system security suite.

8. The Dream FORWARD-LOOKING

Everything in this section rests on one observation about what v1 already proves: a person can hold their own root of trust, run a capable AI under it, and prove every consequential act in a chain they own. None of what follows requires a new trust model, a new physics, or a promise. It requires only that the same primitives be repeated — across rooms, across people, across time.

8.1 From a console to a home

v1 ships surfaces. The direction is rooms: the substrate addressed as a place you move through rather than a tree you climb. home://you/office is already an address; the office can become a room — your working tools, your agents, your records, behind your gate. A library for what you keep. A vault for what you hold. A parlor where your AI greets you. Same chain, same gates, same airgap switch — rendered as a home instead of an app. Rooms are folders. Tools are programs. The difference is not capability; it is dignity.

8.2 From one HOM3 to a household

A root of trust per adult; a room per child. A family’s HOMEs can bind to one another by signed events — shared DNA for what a household holds in common, guarded rooms for those too young to hold keys, and, at the age of majority, a transfer ceremony in which a child’s accumulated history moves into their first sovereign HOM3, co-signed by parent and child. Heritage, made continuous. A person should not begin their adult digital life at zero, and with a chain as the source of truth, they never have to. You leave memories and ideas intentionally.

8.3 From a household to a mesh

Two HOMEs that hold their own keys can verify each other without anyone’s permission. That fact, repeated, is a social fabric: presence you can trust, vouches that travel with the person vouched for, commerce between people who share a friend rather than a platform. The chain already proves what you did; between consenting peers it can prove who you are to each other. No feed, no rake, no intermediary that can be captured — because there is no intermediary at all. Trust spreads at the speed of relationships, which is slower than virality and far more durable.

8.4 Presence you can verify

An AI with a face raises a question the industry has not answered: how do you know whose it is? HOM3’s answer follows from the architecture: presence is an asset under the root of trust like any other — bound to its owner, carried with verifiable lineage, refused when the lineage does not check out. The engine that mints such presence is its own body of work, protected accordingly; what belongs in this paper is the principle it serves. In a world filling with synthetic faces, verifiable presence — yours, provably, or not rendered at all — is not a feature. It is the difference between an avatar and an impersonation.

8.5 From persons to offices

Nothing in the substrate is specific to an individual. A workshop, a practice, a small company is also a root of trust with rooms, agents under gates, and a chain of record. An office node is a HOM3 configured for shared work — role-scoped keys, witnessed handoffs, provable books. The same guarantees that protect a family protect a firm, and every office that joins the mesh thickens it for the persons already there.

8.6 The universe on the substrate

If the base holds — sovereignty in code, the chain as truth, the AI under the root — then what grows on top need not be built by us. Themes and avatars and rooms designed by their makers and carried with signed lineage. Tools that plug into gates rather than around them. Faces of the substrate we have not imagined, built by people who hold their own keys and owe us nothing. A marketplace is possible here, and a large one; but the order of operations is the whole point. The platforms built marketplaces first and bolted trust on after, which is why their trust is a policy. Ours is a property. The marketplace, when it comes, inherits it.

8.7 What it asks

The dream asks nothing exotic. It asks that people believe a modest claim that v1 already demonstrates: that a person can own their own digital ground, and that an intelligence can serve them on it without ruling them from above it. Every section above is that claim, repeated — for a family, for a friendship, for a face, for a firm. The substrate is shipped. The chain is yours. The rest is people deciding to stand somewhere they own.

We built a place to stand. The dream is what becomes possible when many people are standing. What the enemy meant for evil we have turned for good. We vote with our attention and dollars. We steward every moment — or “they” do. I choose sovereignty. I trust in the Lord Creator Almighty Sovereign for the win.

HOM3 v1 — your own root of trust, with an AI that acts under it.