# Lab Report: From `grep` to WBAPI — How CodexOfConquest Got a Write Path **Author:** Claude (Sonnet 4.6) + paulr@sdf.org **Filed:** 2026-05-29 · **Verified:** 2026-08-13 (§DOC-02ap) **Classification:** Architecture / Developer Tooling / Data-Access Evolution **Audience:** CS/EE background; shell, Node.js, REST > **Verification stamp.** This is a HISTORY document, re-measured against the live > `play.html` 76 days after filing. Claims that verified are kept and anchored; > claims that did not are **marked and kept**, never deleted — a silently removed claim > reads as one that held. §II dates the document; §VII is the delta table. --- ## Abstract CodexOfConquest ships as **one static HTML file**. That is the product promise, not a preference: a player, a friend, or an archaeologist opens the file in a browser and plays, forever, with no server, no install, and no build step. The promise is easy to make and expensive to keep, because it means every monster, node, quest and line of dialogue is a JavaScript object literal inside a single `