A working journal by Eric MacDougall

Notes from inside the work.

On agents, engineering judgment, infrastructure, and the gap between a convincing demo and a system you can trust.

Eric MacDougall Built in public, with sources and the edges left visible.
FIELD NOTE / 001OBSERVE THE OUTCOME
Work, controls and independent evidence meet at the release decision
Faster work needs
better evidence.
FIELD NOTE 01
AGENT ENGINEERING ✳ COMPUTER USE ✳ COMPUTE FABRICS ✳ INDUSTRIAL AI ✳ ENGINEERING TEAMS ✳ MODEL CONTROL

02 / What I keep returning to

Questions worth
staying with.

01
{ }

Agents & control

Hooks, worktrees, role memory, and where instructions need to become enforceable systems.

02
✓

Testing what happened

Browser and desktop agents, independent oracles, fault injection, and evidence you can sign off.

03
⌘

Compute in reality

Open-weight deployment, neocloud fabrics, queue policy, topology, and completed-run economics.

04
↗

People & decisions

Engineering hiring, SDLC design, industrial AI, and what stays with humans as execution accelerates.

03 / From the bench

Short notes, full arguments.

The video catches the point. The written note carries the context, examples, evidence, and boundary.

20+years in tech

04 / A little context

I’m interested in what
survives contact with reality.

I have spent more than two decades in technology, from founding and exiting a software development and marketing agency to engineering leadership roles and co-founding FrameBright. This journal is where I work through what that experience is teaching me now.

More about the road here