Realtime Agentic Development
Agent harnesses are already becoming realtime development environments. Loops, goals, living specs, salience, and software feedback start to look less like ticket workflows and more like musical looping.
A Spreadsheet at Google-Sheets Scale: Cell Families and Focused Recompute in lazily-rs
lazily-rs now backs a full-capacity Google Sheets workbook — 10,000,000 cells — and the part that matters isn't the build time, it's that editing one cell and reading a 1,000-cell viewport costs ~11 microseconds no matter how big the sheet is. This post walks through the two new keyed primitives that make it possible — CellMap and CellFamily — and the lazy pull-based model that recomputes only the cells you focus on, with diagrams of coarse-vs-fine-grained reactivity and the spreadsheet graph.
Reactive State Machines: How lazily-rs Drives agent-doc's Cycle State
A finite state machine shouldn't be a pile of scattered if-checks. This post shows how lazily-rs's StateMachine primitive — a Cell-backed FSM with a pure transition function and reactive observers — became the single transition authority for agent-doc's per-document cycle state, replacing ad-hoc phase guards with one declared table. With diagrams of the phase graph, the FSM-plus-durable-journal architecture, and how the same reactive graph that runs your UI can run your protocol.
The lazily Architecture: One Reactive Graph from Local Memory to the Network
A full-architecture tour of lazily — the reactive core (Context, Cell, Slot, Signal, Effect), the three execution contexts (single-threaded, thread-safe, async), the Snapshot/Delta wire protocol that carries the same graph state across IPC, WebSocket, WebRTC, and FFI, and the cross-language family. With use cases and diagrams.
Slot → Cell → Signal: Composing Lazy and Eager Reactivity in One Graph
How lazily-rs composes three primitives — Cell, Slot, and Signal — so you can pick lazy (compute-on-read) or eager (recompute-on-change, no unset window) per derived value inside a single dependency graph. With use cases and diagrams.
Runbooks — On-Demand Procedural Context for AI Agents
A convention for externalizing step-by-step procedures from CLAUDE.md and AGENTS.md into on-demand runbook files, saving context window tokens while keeping agent workflows discoverable.
532 Commits in One Day: What Multi-Agent Sessions Reveal About Security and Debugging
A single day with 11 parallel agent-doc sessions produced 532 git commits across bug fixes, correspondence, and feature development. The debugging session alone took 292 commits to untangle snapshot rollbacks, duplicate writes, and session lifecycle failures. Here's what dog-fooding an agentic tool teaches you about multi-user security and complex debugging.
Existence-Lang: Pneuma, Noumena & Phenomena in Software Ontology
A deep dive into existence-lang ontology development — building a formal language for modeling reality in software systems. Explores pneuma, noumena, phenomena, universal applicability, precision as possibility space, and permaculture as systemic design.
Agent-Doc: Building a Cross-Platform FFI Plugin with Socket IPC
Live session replacing file-based IPC with cross-platform socket communication in agent-doc's FFI plugin backend — centralizing editor plugin logic in Rust rather than duplicating across JetBrains, VS Code, Vim, and Zed.
Module Harness, Back-Testing, and Building a Domain Ontology with Agents
A live session exploring module-level harness context for agent-doc, back-testing concepts for evaluating harness effectiveness, agent teams vs organic architecture, and the first real usage of existence language to build a domain ontology — with the agent defining its own terminology.
Brian Takita's Posts
The articles that I have posted to this site…