Skip to main content
NEW LOTOR A record the vendor does not hold. Signed receipts for what your agent actually did. READ ON

// SYS.INIT

COGNITIVE WORKFLOWS, PROTOCOLS, DATA SCIENCE, & BUSINESS STRATEGY

I build infrastructure, privacy layers, and systems that hold up under audit. The handshake is just the warm-up; the ledger is the witness.

EXPLORE AIP EXPLORE LOTOR READ ESSAYS
IKE raccoon mark

// FILE 01 · THE FOUNDER

ISAAC LIEM

Fourteen years shipping data and analytics systems, most of it in rooms where the requirements were still forming. Government, agriculture and logistics, healthcare, finance. Lately the work is cognitive workflows and the protocols underneath them.

Data science tells you what is true. Protocols decide what stays true when the system is under load. Business strategy is the same read one layer up, where the constraint is people instead of compute. I do not treat those as four jobs. The art is how I see systems. The strategy is how I move through them. The two are the same, the core and the transient, and the only part I insist on is the floor: the layer that does not move when everything above it does.

READ THE FULL FILE
Isaac Liem
> the audit · > the privacy · > the trust

Show up. Find the floor. Hold the tempo while the rest of the band figures out where the song is going.

// FILE 02 · AUDIT

AIP PROTOCOL

The receipts layer for autonomous agents. A local, signed, hash-chained audit log.

STATUS: ACTIVE

Proof of Build

AIP is not a platform. It is a primitive. When agents negotiate and transact on your behalf, you need a mathematically sound record of what happened and why.

  • • Cryptographically signed logs
  • • Hash-chained state validation
  • • Selective disclosure
VIEW SOURCE // GITHUB 
{
  "entry_id": "aip_0x9f82...",
  "timestamp": "2026-07-20T14:32Z",
  "agent_signature": "sig_...",
  "previous_hash": "hash_...",
  "payload": {
    "action": "NEGOTIATE_COMPUTE",
    "status": "COMMITTED"
  },
  "hash": "0x...a1b2c3"
}

// FILE 03 · THE WRITING

ESSAYS & MANIFESTOS

VIEW ALL ESSAYS //
15 min

Load-Bearing Memory: The Bones Remember

In April someone gave the third layer of the agent stack a name. The name is context. It is the wrong name, and the wrong name is the reason nobody has built the right thing.

#agents#receipts#evidence
12 min

Order of Arrival

The part you recognize a thing by and the part that makes it durable are almost never the same part. A note, a dog, and a system, on the same argument.

#core-and-transient#architecture#strategy
8 min

The Unarmed Gate

I run every session with permissions bypassed. That is not the absence of a floor. It is the removal of one that was never load bearing, and the installation of one that is.

#agents#receipts#sovereignty
5 min

The Dumb Lock

There is a room under every life now. A low hum of everything you have ever written down, every contact, every decision with its reasons still attached, sitting in one place and vibrating at a frequency only you are supposed to hear.

#memory#sovereignty#architecture

// FILE 04 · OPEN SOURCE

CODE & INFRASTRUCTURE

I build in public. Verifiable systems require transparent source.

aip-protocol

Local, signed, hash-chained audit log protocol for autonomous agents.

• JavaScript
lotor

Receipt layer for AI agent sessions. Public beta.

• Node
github.com/githubscum

// FILE 05 · LOTOR

LOTOR

PUBLIC BETA

A record the vendor does not hold.

A signed, append-only log of what your agent's session reported doing, written to your machine and nowhere else. Consequential actions stop and wait for your signature. Scoped custodial integrations pending — reach out for details.

• LOCAL FIRST • YOUR KEY • GATED ACTIONS
EXPLORE LOTOR

// FILE 06 · THE STORY

THE IKE SERIES

A small raccoon in a world built by somebody else, learning that the difference between two true accounts is who held the pen. The argument underneath all of this, told as a graphic novel.

the shelf

Every chapter, both arcs. What he can do, and what he cannot.

a fragment

The opening of chapter one. Text only, ahead of publication.

the riverbed

Your own record. What you stopped on is what you carry, kept in this browser and nowhere else.

READ THE SERIES
Context is a retrieval word. It describes something you fetch and put in front of a model so it answers better. Under that name the design space collapses into a search problem: embed better, rank better, forget less. Every system built in that lane...Here is what changed. I stopped thinking of the prompt as a wall and started hearing it for what it actually is, which is a doorbell with no door behind it. It rings on everything. It rings the same way for a directory listing and for a command that...I adopted Copper, an Australian cattle dog, which means he likes to work. I have never raised this breed before, so I enlisted a consultant.There is a room under every life now. A low hum of everything you have ever written down, every contact, every decision with its reasons still attached, sitting in one place and vibrating at a frequency only you are supposed to hear. The industry...There is a frequency beneath every system that most people never hear. A low, humming truth that sits under the noise and the polish and the architecture diagrams. You only notice it when the pressure rises. When the cables buzz. When the whole...An autonomous software agent is a program that takes a goal, makes a plan, calls tools, and produces an output. Many such agents exist. They are built by different teams, on different runtimes, with different model backends, and they live in...Every protocol has to answer the same first question: how do you know it's the real one? AIP answers that question with itself. The protocol I built is the system I used to build the protocol. Each piece of proof I produce is itself a build event....