Claude Code / claude code
8 articles
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.
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.
Your AI assistant’s memory should belong to you
Check whether AI memory survives a change of tool or machine, using my 35-file audit and a practical handoff test for a durable, versioned project record.
Directing an AI assistant across search and hosting tools
Directing an AI assistant through Search Console, Bing and Cloudflare kept a recovery moving while I made the decisions, checked results and managed exceptions.
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.
The Tiered Context Architecture: Managing AI Working Memory at Scale
Organize AI project memory into active work, reference and history, with a worked migration, recovery checks and a practical path toward compiled context.
Synthesis Project Management: Keeping AI Work Moving Across Sessions
A working method for human-AI projects: keep current context small, preserve decisions and lessons, and carry useful work across sessions, people and AI tools.