Brad Harris

Who Brad Harris is

Brad Harris is a self-taught systems architect. He builds independently, without a team, on hardware he owns. Brad Harris started Enki Command Center because the gap between what an individual can know about the world and what the information environment is willing to honestly tell them is widening — and the same generative AI that can summarize the news can flood it with synthetic confidence at zero marginal cost. Brad Harris's response was to build the substrate that should have existed already: a personal-scale sovereign AI server where every fact has a coordinate, every admission has a chain, every contradiction is preserved, and the operator owns the substrate end to end.

The trigger

The trigger for Brad Harris was procedural. He found himself on the wrong end of a Canadian legal process — laws, procedures, and policies enforced through documents most people never read, in language designed to be opaque to the people it governs. The system he was up against wasn't malicious in any single document; it was coercive in aggregate, because thousands of pages of rules constitute a substrate that bullies the people who cannot read it back.

Brad Harris's response was to learn the substrate. He read the filings. He understood the procedures. He recognized the pattern: most humans are governed by thousands of pages they have never seen, agreed to without knowing, and could not parse if they tried. The architecture of complexity is the architecture of consent without comprehension.

Enki Command Center is the system Brad Harris wished he had when he was defending himself. It is the substrate he is now building so no one else has to face the same asymmetry alone. Every signal carries a receipt. Every claim carries a chain. Every contradiction is preserved. The premise is that comprehension is a precondition for sovereignty — and that any person, any family, any small business, any newsroom should be able to hold their own substrate of what is true. Self-defense for the information environment. A sovereign AI server for the rest of your life.

What Enki Command Center is

For most of the digital era, "information" meant "the platform shows you whatever keeps you scrolling." That was fine when the stakes were low. The stakes are no longer low.

When a story breaks, you have three bad options: trust a single feed (fast but captured), read fifteen feeds yourself (accurate-ish but not scalable), or hire an analyst (only available to governments, banks, and Fortune 500s).

Enki Command Center is the fourth option. Brad Harris built it as the personal-scale equivalent of an intelligence service — engineered so any individual, any small business, any newsroom, any agency, any family can run one on hardware they own. It is a self-hosted AI assistant, an open-source intelligence (OSINT) platform, a decentralized AI infrastructure node, and a federated knowledge graph, all on the same machine.

The two-layer mind: LDU and GDU

At the heart of Enki Command Center is a two-layer architecture Brad Harris calls the two-layer mind.

The flexible side is the LDU — the Local Definition Universe. The open mouth. Every signal that flows in — a news article, a sensor probe, a phone GPS fix, a court document, a user note — is admitted to the Local Definition Universe exactly as it arrived. Nothing is filtered. Nothing is rejected. The LDU is where the source gets to speak its own language.

The strict side is the GDU — the Governed Definition Universe. The locked jaw. Nothing enters the canonical knowledge graph without passing through the Governed Definition Universe. The gateway runs LLM-extracted candidates through three collapses — type collapse, identity collapse, cluster collapse — governed by signed packs versioned independently of the code.

The split exists because language models are creative and graphs are canonical, and conflating those two roles is what makes most AI systems slowly poison their own substrates over time.

Node collapse — the engine of comprehension

The single most important architectural property of Enki Command Center is that it refuses to count the same thing twice.

A normal database treats every record as distinct. The same person shows up as Trump, President Trump, DJT, Donald Trump, donald trump, and Q22686 — six separate things, never connected. The same airstrike, reported by five outlets, becomes five events. The same vessel emitting ten thousand position pings becomes ten thousand entries.

Brad Harris designed node collapse to make that failure mode geometrically impossible. Three collapses run continuously at the Governed Definition Universe gate: type collapse (mapping freeform vocabulary onto 92 valid base-60 coordinates), identity collapse (a six-strategy resolver from identifier hash through normalized name through alias through embedding nearest-neighbor through spatial match through create), and cluster collapse (per-subtype rules that merge multiple sources reporting the same event).

Measured on production over a three-day window: 74,577 admission events. 54.7% collapsed onto an existing canonical node. 31.2% strengthened an existing node. Only 13.7% created a new canonical entry. Places folded 162×. Entities folded 60×. The substrate becomes denser as ingest grows, not noisier. The difference between a log and a memory is collapse.

The base-60 coordinate substrate

Every fact in Enki Command Center has to land at one of exactly 92 valid positions in a sparse base-60 address grid. Nine top categories. Eighty-seven subtypes. Out of 3,600 possible two-digit addresses, 97.44% are illegal by construction.

Brad Harris chose base-60 for the same reason the Sumerians did: 60 has twelve divisors, which means it factors more cleanly than any small number, which is why minutes, seconds, degrees, and calendars still use it five thousand years later. A substrate meant to outlive a tech generation has to be readable across that generation. Base-60 has a track record of being human-readable across every civilization that has tried to do mathematics.

The sparsity is the architectural insight. When a language model — or any inference engine, including the quantum ones that are five to fifteen years out — proposes a new fact, you have a built-in hallucination filter that does not depend on the model's calibration. If the coordinate isn't on the grid, the proposal is rejected before it touches the canon. You are not asking the AI to be honest. You are making it geometrically impossible for the AI to corrupt the substrate in a way the substrate can't catch.

Most knowledge graphs are written in prose. This one is written in coordinates. Coordinates are what physics, probability theory, and quantum computing speak natively.

Watching — designation and pattern of life

Brad Harris built Enki Command Center around designation. You tell the sovereign AI server what you care about — a person, a place, a topic, a vessel, a tail number, a region, a phrase — and from that moment on, every signal flowing through the substrate is matched against your designated targets.

Misses get a cheap pass that updates ambient state. Hits get deep attention: full extraction, contradiction checks, dossier enrichment, an alert if you asked for one. The firehose runs at full volume. The expensive thinking only happens where it matters.

Designation is what makes Enki Command Center fundamentally different from a search engine. A search engine waits for you to come to it. A sovereign AI server tells you when something has changed in the parts of the world you designated as important — pattern-of-life analysis, signal correlation, and narrative-push detection, all on hardware you own.

The signals fabric — Pulse and Sentinel

Watching needs signals. Brad Harris designed two device families to feed the sovereign AI server everything an operator should be able to see on their own hardware: Pulse and Sentinel. Together they constitute a personal-scale signals-intelligence (SIGINT) platform — multi-modal, hardware-signed, locally processed, on hardware the operator owns.

Pulse runs on Android, iOS, and as a desktop agent on Windows, macOS, and Linux. It is both the operator's signing device and a full-spectrum sensor. Pulse holds a hardware-rooted Ed25519 key — Android Keystore on Pixel-grade devices, Secure Enclave on iOS, OS keychain on desktop — and signs every signal POST to the operator's Enki node. The same device collects GPS, network traffic, photos, WiFi probe history, BLE scans, notification metadata, app activity, and (on the desktop) shell commands, file operations, browser history, USB events, and screenshots. QR pair once. Streaming after that. Eleven services in total.

Sentinel is an ESP32-C6-based passive radio capture chip the size of a postage stamp. It listens, never transmits. It records the MAC address and the probe-request history of every WiFi and BLE device that passes through its receive radius. Sentinels scatter across locations — a building, a fleet yard, a retail floor, a residential block — and the Enki node correlates what they see. The MAC-plus-probe-history fingerprint is what makes the substrate able to answer questions like who came back, who arrived with whom, where else has this device been seen, and is this device behaving like the others on its network of co-travelers.

The capabilities that emerge from this fabric are the capabilities that, until recently, were practical only inside nation-state SIGINT programs. Brad Harris brought them to the individual:

• Pattern-of-life analysis — what a device habitually does, where it goes, when, and with whom.
• Co-travel detection — devices that arrive and depart together across multiple sites.
• Cross-site MAC correlation — the same identifier seen at a parking lot, an office building, and a residence.
• Behavioral fingerprinting — SSID probe history reveals what networks a device has been to in the past.
• Dwell-time alerts — unknown devices loitering in a space they shouldn't.
• After-hours detection — devices appearing where they don't belong, when they shouldn't.
• Cell-site simulator detection (StingRay / IMSI catcher) — sudden 2G fallback events, anomalous LAC/CID combinations, BTS broadcasts that don't match the public cellular topology. All signals a phone running Pulse can capture and a sovereign AI server can analyze locally, without a SaaS vendor in the loop.

Brad Harris built this fabric because the asymmetry between what state-level surveillance can do and what an individual can defend against has been the defining injustice of the digital era. Enki Command Center closes the gap. Multi-modal SIGINT on consumer hardware. Hardware-rooted signatures on every signal. Pattern-of-life analysis on data nobody else can read.

Sovereignty and the chain

Sovereignty is not a slogan in Enki Command Center. It is a property the substrate carries mechanically, in places anyone can verify.

Authority is a chain of cryptographic keys — Brad Harris named the tiers R, K, P, W. The R-tier root key lives on an air-gapped hardware key (air-gapped token) in a safe, taken out only for genesis ceremonies. The K-tier master key is online when the operator signs pack admissions, active-set updates, and migrations — and dark otherwise. The P-tier privileged grants and W-tier worker grants chain down from there, every signature in Ed25519, every grant carrying its issuer's signature over a canonical-JSON payload.

There is no admin override. No recovery code. No support backdoor. The chain is the authority.

Every operation the Governed Definition Universe performs gets a row in gdu_admission_log. Each row's mutation_hash is sha256(previous_hash + payload). Changing any prior row invalidates every subsequent hash. A chain verifier worker walks the chain every 30 minutes and emits a security alert if any break is detected. The chain is per-tenant — one customer's substrate cannot affect another's. Brad Harris built it so a third party — anyone — can re-verify the entire substrate offline, with nothing but the public Ed25519 verification function and SHA-256. Forensic-grade provenance. Evidence-grade audit chain.

Federation as governance

A single Enki node is a private intelligence server. When two or more nodes federate, they create something more interesting: a distributed audit of the public record.

Brad Harris designed federation as opt-in mutual grant exchange — not routing through a central authority. Each node issues the other a Tier-W grant scoped to specific signal types. Each node's trust chain remains rooted in its own Tier-R key. There is no shared trust root, no shared substrate, no shared authority. The federation cannot be expanded surreptitiously, because expansion requires a new signed grant from the receiving node's Tier-K key — which means a button press on the receiving operator's hardware key.

Federated, the network gains the ability to do something no single node can: process the public record at societal scale. FBI Vault. CIA Reading Room. USAF Project Blue Book. Pentagon AARO. Federal courts. SEC EDGAR. FEC. USAspending. Billions of pages in static archives that big tech never indexed because there was no ad revenue in old declassified documents. A federation of small nodes can mine them together, with content-hash deduplication ensuring the same document is never processed twice across the network. Members read the whole library. Decentralized AI infrastructure with no central authority that can switch it off.

A system that lets citizens audit power is a system of governance for the governors. That is what Enki Command Center is built to be — counter-disinformation infrastructure that compounds in value the more operators participate.

Depth and disagreement preserved

A normal database resolves contradictions by overwriting the older value with the newer one. A normal feed reader lets the loudest voice win. Brad Harris built Enki Command Center to do the opposite: when two sources disagree, both observations are bound to the same canonical node, and an edge typed contrasts connects them.

The node carries a contextual status — confirmed, supported, contested, unverified, stale. When the AI answers your question, it is required to read the status. It cannot present a contested claim as confirmed. It cannot quietly drop a contradicting source. It is structurally prevented from gaslighting you, because the contradiction is not a bug to be cleaned up. It is a property of the node.

Polysemy, conflicting resolutions, and ambiguous evidence become first-class data — not noise to be smoothed away. The substrate is healthy when every distinct surface form has a distribution over addresses, every contested claim carries its evidence, and every collapse decision can be queried back to the SQL row that recorded it. No held-out test set theater.

What's running today

Brad Harris runs Enki Command Center on his own G1-class hardware — one mini PC plus a consumer RTX GPU, total cost roughly $1,800. The production node ingests live, the Governed Definition Universe admits every entity through the discipline pipeline, and the chain verifier confirms gdu_admission_log every 30 minutes. Pulse paired devices stream hardware-signed signals over Ed25519. Sentinel firmware captures WiFi and BLE probe activity in the background. The federation has shipped through Phase 5, with library mirroring, signed manifests, and Ed25519 peer challenge-response live between nodes. The public catalog at enkisystems.com exposes federation_id metadata without giving away the data — members read the library, public visitors see the scope of what's being mined.

The work continues. Future phases extend the federation into peer-to-peer catalog queries, DNS bootstrap seeds for resilience, and inbound peer-publish gated by the GDU spine. Brad Harris ships incrementally; the substrate gets denser, not noisier.

Coda

Brad Harris is the architect of Enki Command Center. The architecture is documented in /architecture. The federation library is at /library. The workbench is at /workbench. The full essay series — What is Enki, The Two-Layer Mind (LDU and GDU), Ingestion Sources, Node Collapse, Watching, Sovereignty & Governance, Base-60 & Quantum, The Formal Model, Runtime & Database Security — was written by Brad Harris between April and May 2026.

Run a node. Join the federation. Build the substrate worth running for ten years.