<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Writings — Suraj Sharma, XO Labs</title>
    <link>https://quirq.ai/</link>
    <description>Long-form research on agentic systems and the measurement of work.</description>
    <language>en</language>
    <atom:link rel="self" href="https://quirq.ai/feed.xml" type="application/rss+xml" />
    <item>
      <title>What Each File Wants</title>
      <link>https://quirq.ai/what-each-file-wants/</link>
      <guid>https://quirq.ai/what-each-file-wants/</guid>
      <pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate>
      <description>No best compressor, only the right match. A measured field guide to compressing JSON, small messages, config files, logs, tables, images, audio and video in October 2026 — which codec, which level or quality, when a format beats a compressor, and when to leave a file alone.</description>
    </item>
    <item>
      <title>What Compression Keeps</title>
      <link>https://quirq.ai/what-compression-keeps/</link>
      <guid>https://quirq.ai/what-compression-keeps/</guid>
      <pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate>
      <description>Compression keeps all the information in fewer bits; compaction keeps only the present. A long explainer of both — entropy, coders, the 2026 codecs, prediction, lossy coding, HTTP and attacks, then LSM trees, Kafka, VACUUM, GC, git gc and agent context compaction — measured and compared side by side.</description>
    </item>
    <item>
      <title>What the Parser Hears</title>
      <link>https://quirq.ai/what-the-parser-hears/</link>
      <guid>https://quirq.ai/what-the-parser-hears/</guid>
      <pubDate>Fri, 09 Oct 2026 00:00:00 GMT</pubDate>
      <description>A configuration file has two readers. A field guide to JSON, YAML and TOML as configuration formats in October 2026 — their specs, every pitfall that still bites, what 34 real parsers hear for the same 71 inputs, and a practice for choosing and guarding a config format.</description>
    </item>
    <item>
      <title>Turborepo or Nx</title>
      <link>https://quirq.ai/turborepo-vs-nx/</link>
      <guid>https://quirq.ai/turborepo-vs-nx/</guid>
      <pubDate>Fri, 02 Oct 2026 00:00:00 GMT</pubDate>
      <description>Both now call themselves the build system for coding agents. A sourced comparison of Turborepo 2.11 and Nx 23.2 — graph models, cache keys, remote caching, distributed CI, polyglot support, governance, agent features, pricing and supply-chain history — with a benchmark of both on one workspace.</description>
    </item>
    <item>
      <title>Where the JSON Lives</title>
      <link>https://quirq.ai/where-the-json-lives/</link>
      <guid>https://quirq.ai/where-the-json-lives/</guid>
      <pubDate>Thu, 01 Oct 2026 00:00:00 GMT</pubDate>
      <description>Relational versus non-relational is the wrong first question. A field guide to both families, the 2024–2026 licence ledger, best practices that survive production, and a measured answer to where JSON that is loaded and stored all day should live — built from free, open-source parts.</description>
    </item>
    <item>
      <title>A Table With Two Columns</title>
      <link>https://quirq.ai/page-registries/</link>
      <guid>https://quirq.ai/page-registries/</guid>
      <pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate>
      <description>A page registry is a table: a shape name in your data on the left, the code allowed to draw it on the right. The three shapes a page can have, six ways to build the lookup, what one entry must carry, where to validate, how to version against two deploy clocks — and where MagicPath fits, with an honest ledger.</description>
    </item>
    <item>
      <title>Nothing Runs While You're Gone</title>
      <link>https://quirq.ai/game-timers/</link>
      <guid>https://quirq.ai/game-timers/</guid>
      <pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate>
      <description>A build timer is one integer on one row. It is also the cheapest server design for a game with a hundred million players, and the mechanism that decides when you next open the app. How the two halves are the same object — and where that stops being a fair trade.</description>
    </item>
    <item>
      <title>The State Is Enough</title>
      <link>https://quirq.ai/markov-processes/</link>
      <guid>https://quirq.ai/markov-processes/</guid>
      <pubDate>Mon, 28 Sep 2026 00:00:00 GMT</pubDate>
      <description>A Markov process is a bet: that you can choose a description of &quot;now&quot; so complete that the past adds nothing. What that bet buys, and where computer science cashes it — PageRank, MCMC, Viterbi, Kalman, MDPs, branch predictors, queueing, and the state-size fight between attention and state-space models.</description>
    </item>
    <item>
      <title>Anatomy of a Codex session</title>
      <link>https://quirq.ai/codex-session/</link>
      <guid>https://quirq.ai/codex-session/</guid>
      <pubDate>Fri, 25 Sep 2026 00:00:00 GMT</pubDate>
      <description>What a Codex session contains, how it runs, where it persists, and how to control it: threads, turns, items, projects, commands, permissions, forks, SDKs, and background execution. A versioned anatomy for designing an operating system that can route work into Space and other products.</description>
    </item>
    <item>
      <title>Anatomy of a Claude Code session</title>
      <link>https://quirq.ai/claude-code-session/</link>
      <guid>https://quirq.ai/claude-code-session/</guid>
      <pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate>
      <description>What a Claude Code session is made of, read from the 2.1.280 binary and measured on one machine: four identities, nine boot steps, the transcript graph, 120 options, the state file every process rewrites, 66 control requests, seven doors, and the friction map for building an OS around it.</description>
    </item>
    <item>
      <title>Blink, taken apart</title>
      <link>https://quirq.ai/chromium/blink/</link>
      <guid>https://quirq.ai/chromium/blink/</guid>
      <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
      <description>Chromium's rendering engine read end to end at commit f288fed6 (Chrome 156.0.8067.0): the tree and its DEPS-enforced layering, the process and thread model, the RenderingNG pipeline, Oilpan on cppgc, Web IDL bindings, runtime-enabled features and web tests.</description>
    </item>
    <item>
      <title>DEPS, gclient and what replaced goma</title>
      <link>https://quirq.ai/chromium/deps-and-goma/</link>
      <guid>https://quirq.ai/chromium/deps-and-goma/</guid>
      <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
      <description>A teardown of Chromium's dependency machine: depot_tools, the DEPS grammar, gclient sync step by step, submodules, autorollers, toolchain pinning — and goma, reclient and Siso.</description>
    </item>
    <item>
      <title>The tree that configures the fleet</title>
      <link>https://quirq.ai/chromium/ci-cd-and-releases/</link>
      <guid>https://quirq.ai/chromium/ci-cd-and-releases/</guid>
      <pubDate>Wed, 23 Sep 2026 00:00:00 GMT</pubDate>
      <description>A teardown of Chromium's CI/CD: the LUCI stack, infra/config Starlark and the generated cfgs, tests on bots, bot_update, the commit queue, tree closers and gardeners, the two-week release cycle and the release scripts.</description>
    </item>
    <item>
      <title>Liveblocks, read for XO Space</title>
      <link>https://quirq.ai/liveblocks-for-xo-space/</link>
      <guid>https://quirq.ai/liveblocks-for-xo-space/</guid>
      <pubDate>Fri, 18 Sep 2026 00:00:00 GMT</pubDate>
      <description>What Liveblocks is, where a room-per-project would sit inside xo-space, whether it installs inside the container (the SDKs do, the room server does not), and what autonomous building and sharing of a Space would actually mean — with a bounded pilot.</description>
    </item>
    <item>
      <title>The ten hardest open problems in mathematics</title>
      <link>https://quirq.ai/hardest-problems/</link>
      <guid>https://quirq.ai/hardest-problems/</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <description>Ten problems, ranked by how much of mathematics moves when they move — what each claims, what is actually proved as of August 2026, where mathematics is genuinely NP-hard or undecidable, how many kinds of infinity there are, and a dated forecast of which problems fall by 2050.</description>
    </item>
    <item>
      <title>XO Space: the architecture</title>
      <link>https://quirq.ai/xo-space-architecture/</link>
      <guid>https://quirq.ai/xo-space-architecture/</guid>
      <pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate>
      <description>The implementation reference for xo-space: install and run, the xo-project folder contract, and the full data model — every entity collected, what bounds each file, and where the plane duplicates itself.</description>
    </item>
    <item>
      <title>The J-Space: a construction manual</title>
      <link>https://quirq.ai/j-space/</link>
      <guid>https://quirq.ai/j-space/</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
      <description>What the Jacobian Lens is, why averaging is the whole trick, and exactly how to build a J-space — compute routes, sparse decomposition, read and write operations, and a validation protocol.</description>
    </item>
    <item>
      <title>One Graph, No Boxes</title>
      <link>https://quirq.ai/chromium/sea-of-nodes-paper/</link>
      <guid>https://quirq.ai/chromium/sea-of-nodes-paper/</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
      <description>A close reading of Click and Paleczny's 1995 paper, the origin of the Sea of Nodes — every figure redrawn — and the general recipe inside it for representing any process over any data.</description>
    </item>
    <item>
      <title>The Sea of Nodes, explained simply</title>
      <link>https://quirq.ai/chromium/sea-of-nodes/</link>
      <guid>https://quirq.ai/chromium/sea-of-nodes/</guid>
      <pubDate>Sat, 01 Aug 2026 00:00:00 GMT</pubDate>
      <description>A plain-language explanation of the program representation behind V8's TurboFan: three kinds of edges, why pure instructions float, how the graph becomes a program again, and why V8 left it.</description>
    </item>
    <item>
      <title>Anatomy of an Agent Control Plane</title>
      <link>https://quirq.ai/xo-space/</link>
      <guid>https://quirq.ai/xo-space/</guid>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
      <description>A teardown of xo-space, the local control plane for AI coding agents: one capability seam, agents declared as data, four transports under one streaming contract, and a session index that holds no messages.</description>
    </item>
    <item>
      <title>Anatomy of a Personal Memory Engine</title>
      <link>https://quirq.ai/personal-memory-engine/</link>
      <guid>https://quirq.ai/personal-memory-engine/</guid>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
      <description>A component-by-component teardown of iai-pme, a fully local memory engine for coding agents: fail-safe capture hooks, an encrypted verbatim store, a vector index that isn't HNSW, and nightly consolidation.</description>
    </item>
    <item>
      <title>What is a unit of work?</title>
      <link>https://quirq.ai/what-is-quirq/</link>
      <guid>https://quirq.ai/what-is-quirq/</guid>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
      <description>A prompt asks for an action. A unit of work owns an outcome from definition through verification. The quirq is the proposed unit for measuring that verified work.</description>
    </item>
    <item>
      <title>quirq: A Unit of Work for Intelligence</title>
      <link>https://quirq.ai/whitepaper/</link>
      <guid>https://quirq.ai/whitepaper/</guid>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
      <description>The token meters what AI consumes. The quirq is proposed as the output meter: budgeted by an owner, minted by verification, costed all-in, read as a trajectory.</description>
    </item>
  </channel>
</rss>
