AI agents / ai agents
17 articles
The Action Sheet: one page for everything your AI agents still need you to do
The decision packet's companion: after AI agents act on your rulings, one page shows what's done, what waits for your approval, and what's left for you, with the exact text ready to send yourself or to hand to an agent.
Two vendors, one standard: running a real upgrade with synthesis engineering
An upgrade with Claude and Codex exposed a disabled safeguard and an invisible project record. The repairs show how to test the workflow that actually runs.
The Decision Packet: batching AI agents' questions without rubber-stamping them
Batch AI agents' questions into one clear review page, preserve exceptions and deliberate choices, and keep each answer tied to its evidence and authority.
The migration that was finished until a stranger looked
A synthesis engineering story about Blind-Spot Rotation: how an AI reviewer with fresh context can find gaps the original inventory and checks missed.
Why I built synthesis engineering to work across AI runtimes
Why synthesis engineering separates model, runtime and state portability, preserving native strengths while keeping projects and methods under your control.
My AI executive assistant writes in its own voice. My AI chief of staff writes in mine.
Ragbot and Ragenie, EA AI and chief-of-staff AI: why my executive assistant agent writes in its own voice while my chief of staff agent writes in my voice.
My design record ruled out agent-to-agent messaging. Six days later I shipped it.
I documented why session-to-session agent messaging would fail, then built it six days later. Why a design record is not a constraint, and what actually is.
What agent memory research taught me about twenty years of notes
Tiered memory for a personal knowledge base: what MemGPT, Zep, and Mem0 teach about structuring two decades of notes so AI agents find the right ten files.
AI tools should copy GitHub's identity model, not your employer's
AI tools should give people lasting identities and organizations scoped roles. My GitHub account and shared-agent schema show why that design choice matters.
What should survive when you change AI tools
Preserve project decisions, methods, authority and evidence across AI tools, with explicit ownership of the adapters and tests that keep the work portable.
A green config is not a working agent
Check source, installation, live behavior, continuity and capability. Use native client adapters and shared outcome tests to earn trust in an AI environment.
I gave my AI agents a chief-of-staff job description
AI agents as chief of staff: how I encoded absence coordination, notification tiers, send gates, and silent-failure validators into open-source config.
Ask Your AI to Refute You
Commission AI reviewers to challenge your claims, then test their findings. Use distinct lenses, concrete counterexamples and honest unresolved states.
AI disclosure guards: approval is the boundary
Build AI disclosure guards around approved facts, their sources and where they will appear, with a precedent ledger and five practical contextual review tests.
I built a validator for Google’s Open Knowledge Format
Check an OKF v0.1 bundle against its specification, distinguish checker coverage from conformance, and preserve knowledge and navigation during conversion.
When I use chat, workflows, and a visual console
How I choose between chat, repeatable workflows and a visual console, while keeping project records I own and deciding what must survive a change of tools.
I made project memory portable between Claude Code and Codex
Carry project decisions, unfinished work, and verification between Claude Code and Codex while checking each tool's instructions, skills, hooks, and access.