A passion project from a late-night desk, not a boardroom.
I am a husband, a father, a twenty-year public servant in cybersecurity, and someone who has been taking machines apart since I was eight years old.
Why a hardware tinkerer & cybersecurity defender built CIN
1. Age eight: a Soviet x186 clone and a 4-bit schematic
At age eight, tracing a Soviet x186 wiring diagram taught me that software is never magic—you always check what the physical silicon underneath is doing.
Read full personal reflection ▾
When I was eight years old, I took apart a Soviet x186 computer clone and spent days tracing its paper wiring diagrams by hand to see if I could modify its monochrome graphics processor to output 4-bit color. Halfway through the schematic, I realized the 4-bit color capability was already sitting on the board—it just needed a custom video interface to feed our television.
Together with my dad and a local electrician, we soldered that interface and built our first Soviet “HTPC,” playing Test Drive (1987) and Grand Prix Circuit (1988) in color on the living-room TV. When you grow up tracing physical copper lines on a circuit board, you never buy the illusion that software is magic: you always ask what the silicon underneath is doing and who holds the physical switch.
2. Twenty years in public service and cybersecurity
Two decades in cybersecurity showed me how rigid hierarchies lose ground truth and pay a crushing tax for zero-sum “information superiority.”
Read full personal reflection ▾
As an adult, I spent twenty years in public service across cybersecurity and institutional defense. First, I saw how even decent, dedicated people inside rigid top-down pyramids lose the ground truth as real-world signals climb five layers of management.
Second, cybersecurity showed me the staggering price institutions pay for information superiority—hoarding data inside walled gardens while treating everyone outside as an adversary. I wanted to help replace that exhausting prisoner’s dilemma with verifiable cryptographic cooperation that ordinary families can actually trust.
3. Why the old choices aren’t enough
Plugging superintelligent AI into bureaucratic control or corporate extraction locks their worst incentives in at machine speed; we need Two Internets, a 1-to-1 personal agent, and a proof ledger.
Read full personal reflection ▾
Today human flourishing is boxed in from two sides: captured bureaucratic control on one side, and predatory corporate extraction on the other. Plugging superintelligent AI into either system locks its worst incentives in at machine speed. We need a practical third path: Two Separate Internets, a 1-to-1 human-bound personal agent on your own silicon, and a creator-owned proof ledger.
A Markov Blanket for Human Minds
Keep human spaces strictly human while moving machine-speed coordination onto an agent-only data stream governed by hardware-isolated sandboxes.
An Agent That Shares Your Lifespan
Instead of renting a corporate cloud assistant that harvests your life, your personal agent runs on your own silicon and answers only to you.
Verifiable Proof & Direct Royalties
Replace middleman extraction and the Prisoner’s Dilemma with Proof-Carrying Code, Private Set Intersection co-ops, and Data Shapley attribution.
4. Reading papers for fun: from living cells to Markov blankets
Inspired by Michael Levin’s morphogenesis and Karl Friston’s Markov blankets, your local Personal Twin acts as a statistical and hardware boundary for a biological human.
Read full personal reflection ▾
I love following independent thinkers like Michael Levin (whose work on morphogenesis shows how cells build and heal complex bodies without a central “dictator cell”) and Karl Friston (whose Markov blanket formalizes the statistical boundary every living organism needs to avoid dissolving into its environment).
The architecture on this site—the Personal Twin inside your hardware sandbox, the Two Internets airlock, and the rule that outside bots never contact humans directly—is a Markov blanket for a biological human in the age of superintelligence.
5. Loving what AI can do, while fearing we may not be ready
Unshielded human biology (~40 bits/s) cannot out-duel recursive swarms; building the co-intelligence barrier now is our last constructive defence before a hard global pause.
Read full personal reflection ▾
I love building with AI: every night I run an automated loop of AI agents on my workstation to audit papers, run simulations, and build interactive tools. Yet I am honest about my fear: unshielded human biology (~40 bits/s) was not built to compete with recursive self-improving swarms. Building the co-intelligence barrier now is our best shot before humanity is forced into a hard global pause.
How these four life lessons translate directly into CIN’s engineering stack
We bind agent identity to unclonable silicon (SRAM PUFs) and classify liveness on <1 mW Pre-ADC sensors before raw waveforms enter memory.
Test Pre-ADC Biometric Firewall Simulator →Households and clinics use Private Set Intersection (Freedman et al., 2004) and Proof-Carrying Code (Necula, 1997) to cooperate without surrendering privacy.
Test Zero-Middleman Workbench →Your personal agent runs inside a hardware-isolated Object-Capability sandbox (Dennis & Van Horn, 1966), speaking externally only via IETF QUIC (RFC 9000).
Inspect 3-World Sovereign Horizon →Multi-agent actions require risk-scaled consent (Φ(R) = 1 − (1−R)5) and Byzantine-resilient L1 medians.
Test Sharded Git-Merge Simulator →An open notebook, offered in good faith
This entire site—the 550 starting principles, the two-internet and hardware blueprints, the principle realignment test-net, and the live alignment trajectory—is a working notebook of functional ideas.
By putting concrete architectures, math, and working demos into the open now, we give ourselves and our children a fighting chance to live alongside advanced AI on human terms.