Answers are grounded in this paper and cite their sources.
Where everything is now — and why it changed. A file-and-code map for people who build software by talking to an AI every day. It keeps the *current* state of every file, and a change ledger in which **every edit carries a reason and a reverse patch** — tied back to the conversation section that caused it. No git. A dated public record of the design. The implementation is not published. More: https://subtractlab.com
No takes yet. Share an insight, caveat, or question.
Koji Okuda (2026) studied this question.
Synapse has enriched 8 closely related papers on similar clinical questions. Consider them for comparative context: