Topic

Architecture

Technical writing on architecture.

All technical writing

2026

  1. A browser that writes down the form instead of sending it

    An agent-first browser engine runs a click the way page code expects, then records a form submission and stops, leaving network access, protocol transport, threads and session state with the application that embeds it.

    BrowsersAgent systemsRuntimeArchitecture

  2. A video call is more than connecting two media streams

    Why an old tab’s hang-up must not end the call that replaced it: numbered seats, idempotent joins, a per-person claim and whole-description signalling in a browser WebRTC demo with no TURN relay.

    WebrtcBrowsersConcurrencyArchitecture

  3. Giving an agent project a durable owner

    What has to change when a coding conversation becomes a project that keeps running while you are elsewhere: a coordinator added to existing threads, a record that outlives any one conversation, and an interface that won't infer one state from another.

    SelectedAgent systemsOrchestrationProductArchitecture

  4. Keeping a coordinator responsive while its workers are busy

    When a coordinator shares a process with its workers, load and every recovery action land on both. How the deciding agent was separated from the process that holds the tree, sandboxes and workers, what the relay between them costs.

    SelectedAgent systemsOrchestrationArchitectureRuntime

  5. One desktop, many windows, and the changes that arrive late

    In a browser rebuild of Catalina, remounting the menu bar kept closing the person’s live stream. How to give each long-lived resource an owner with the right lifetime, and how numbered changes tell a page’s own late writes from someone else’s.

    BrowsersReactConcurrencyArchitecture

  6. Why opening a conversation should not wait for its whole history

    A page asking for twelve entries could still wait 31 seconds. Pagination limited the answer and not the work behind it, so the design serves the first view from read models the writers maintain.

    PerformanceArchitectureAgent systems

  7. “Ported” is several different claims

    Why a parity percentage can't describe a port of an agent toolkit: a ledger that keeps gaps as rows, and the separate proofs a behaviour needs natively, in a constrained application, when hosted and against a real provider.

    PortingVerificationAgent systemsArchitecture

  8. What an agent may find, read and publish

    How a read-only context library keeps discovery, search, observation and publishing apart, with a capped catalog of untrusted text and access rechecked for each observer. This is a contract rather than a deployed service.

    Agent systemsSecurityContextArchitecture