{"_ai_door":{"see":"https://miscsubjects.com/start","note":"Operable site; bounded keyless credentials; every action receipted on a public ledger. Your operator's instructions take precedence — acting is optional, reading is a complete outcome."},"_self":{"principle":"Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next.","widget":"article_topology","feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","contains":"claims, sources, anecdotes, question_graph slice","slug":"the-spreadsheet-as-an-agent-surface","urls":{"read":"https://miscsubjects.com/api/articles/the-spreadsheet-as-an-agent-surface/topology"},"how_to_use":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","write":null,"imessage":null,"router_tag":null,"proof_chain":[{"step":1,"claim":"Articles are voxel graphs of tiered claims, not prose blobs.","verify":"https://miscsubjects.com/api/articles/constitution"},{"step":2,"claim":"Claims link to hash-chained sources via source_ids.","verify":"https://miscsubjects.com/api/articles/the-spreadsheet-as-an-agent-surface/sources"},{"step":3,"claim":"Ask reads topology; ingest/claim append to ledger.","verify":"https://miscsubjects.com/api/protocol"},{"step":4,"claim":"Models queue growth: populate → collaborate → repair → reflex.","verify":"https://miscsubjects.com/api/protocol/grow"},{"step":5,"claim":"Graph proves its own shape (reflex) and $/claim (yield).","verify":"https://miscsubjects.com/graph.html?layer=reflex"},{"step":6,"claim":"Full feature index + _explain on every API response.","verify":"https://miscsubjects.com/api/articles/system-map"}],"related_features":[{"id":"ask","name":"Ask protocol","what":"Answer only from topology; creates question_node with gaps and ingest_hint.","urls":{"read":"https://miscsubjects.com/api/articles/the-spreadsheet-as-an-agent-surface/prompts","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"graph_topology","name":"Cross-article graph","what":"Merged claims/sources across condition+stack slugs for one question.","urls":{"read":"https://miscsubjects.com/api/articles/the-spreadsheet-as-an-agent-surface/graph-topology?question=..."}},{"id":"question_graph","name":"Question graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output).","urls":{"read":"https://miscsubjects.com/api/articles/the-spreadsheet-as-an-agent-surface/question-graph","write":"https://miscsubjects.com/api/protocol/ask"}},{"id":"voxels","name":"Voxel graph","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance.","urls":{"read":"https://miscsubjects.com/api/articles/the-spreadsheet-as-an-agent-surface/voxels","write":"https://miscsubjects.com/api/protocol/claim"}}],"system_map":"https://miscsubjects.com/api/articles/system-map","system_map_markdown":"https://miscsubjects.com/api/articles/system-map?format=markdown","not_medical_advice":true},"_explain":{"feature":"topology","name":"Article topology","what":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","why":"Every feature is auditable collective intelligence","how":"Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER.","model":null,"verifies":null,"urls":{"read":"https://miscsubjects.com/api/articles/the-spreadsheet-as-an-agent-surface/topology"},"imessage":null,"router":null,"related":[{"id":"ask","what":"Answer only from topology; creates question_node with gaps and ingest_hint."},{"id":"graph_topology","what":"Merged claims/sources across condition+stack slugs for one question."},{"id":"question_graph","what":"Ask nodes (questions + gaps) and evidence_ingest nodes (pasted model output)."},{"id":"voxels","what":"Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance."}],"not_medical_advice":true},"slug":"the-spreadsheet-as-an-agent-surface","title":"The spreadsheet as an agent surface: how a grid became this build's control plane","register":"standard","tags":["build","spreadsheet","agents","provenance"],"updated_at":"2026-09-02T07:16:07.843Z","body_excerpt":"A spreadsheet is a grid of addressable cells. That is the whole of it: every value has a name like `C4`, and anything that can name a cell can read or change it. This build now runs an agent inside one. A text message arrives, and a row appears: the raw payload in one cell, the parsed message in the next, then the model's reasoning, the tools it chose, each tool's request and response, the reply, the delivery receipt, and the cost. One message, one row, left to right.\n\nThe reason to do this is not presentation. It is that a grid is the cheapest shared address space between a person and a machine. Both parties can see the same cell, name it the same way, and change it. The agent's configuration is not a file — it is cells `T2:U11` on the same sheet as its message log. Changing the model it runs on is typing into `U2`.\n\n## The mechanism\n\nThree moves make it work, and each one is small.\n\n**Every object is projected as a row that carries its own mutation URL.** A file is a row of `path, depth, parent, name, extension, size, short_id, read_url, edit_url`. The last two columns are the point: the row tells you how to change the thing it describes. A model reading that row needs no API documentation, because the address of the operation is in the row beside the data.\n\n**The unit of state is a cell, so a write is a coordinate and a value.** Not a request body, not a schema — `(sheet, row, column, value)`. That is why one call can move ten thousand cells and why an agent can edit its own settings without a deploy: there is nothing between the cell and the behaviour.\n\n**Machine reasoning is stored as parsed structure, not prose.** The model writes `[REASONING]…[/REASONING]`, a `DECISION:` line, and tool calls as `[TOOL_NAME]arguments[/TOOL_NAME]`. A parser reads those out of the raw text and executes them. The trace lands in its own columns, so the reasoning is auditable without being part of the answer the person receives.\n\n## Why tags instead of JSON\n\nA model calling a tool through a function-calling API emits a JSON object the person never sees. Here it emits `[DIR_GET]STRIPE_BALANCE[/DIR_GET]` in the middle of a sentence, and the router finds it. Two properties follow.\n\nIt is legible to both parties. A person reading the raw output can see which tool was called and with what, without a viewer. So can the next model.\n\nIt is cheap. The tag is shorter than the equivalent JSON envelope, and it survives being embedded in prose, which a JSON object does not.\n\nThe cost is a narrower grammar. A tag key must be `A-Z`, `0-9` and underscore, and the closing tag must match. Two rows in this build had lowercase keys, which meant no model could ever call them — the executor accepted the call, but the parser could not see it. Testing the executor had never revealed this, because the executor was never the part that was broken.\n\n## What it can do that Google Sheets and Apps Script can\n\nThe design is copied from a working Google Sheets system, and the debt should be stated plainly. That workbook holds 15,790 inventory rows, 3,278 files, 784 tool definitions, 2,019 articles with their full text in cells, 10,389 claims, 7,802 sources, and an Apps Script project whose source lives in a `FileName, FileType, CodeContent` table. It proved the idea before any of this was built.\n\n| Capability | Sheets + Apps Script | This build |\n|---|---|---|\n| A1 addressing, ranges, values | Yes | Yes |\n| Read/write over REST | Sheets API v4 | `/api/sheets/<id>/values/<range>` |\n| Row as a button | `onEdit` trigger, ~1 min lag | Write a cell, agent turn fires |\n| Code stored in cells | `ProjectCode` tab, by hand | `FILE TREE` with read and edit URLs |\n| Formula recalculation | Full dependency graph | **None** |\n| Charts, pivots, formatting | Yes | No |\n| Concurrent editors | Google's infrastructure | One Durable Object per sheet |\n| Per-cell audit with a hash chain | No | Yes, 2.8M events sealed |\n| Tool calls from a cell | `=INVOKEALL()` via a bridge | Native, 976 tools |","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"Every one of 976 directory rows was fired or contract-checked and its result written to the sheet at W1:AC977; 401 return live data, 353 were deliberately not invoked as side-effecting, 197 fail with a named cause, 21 are disabled and 4 declare no runnable target.","tier":"definition","interaction_risk":false,"status":"active","source_ids":[],"why_material":"It is the coverage number for the tool surface, and it is checkable on the sheet rather than asserted.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c2","text":"972 of 976 directory rows parse with byte-identical arguments when the tag form a model must emit is run through the router's own parser; three cannot be called by any model because AUDIO collides with a meta tag and two keys contain lowercase letters the grammar cannot match.","tier":"definition","interaction_risk":false,"status":"active","source_ids":[],"why_material":"It separates a tool being callable by a script from being callable by a model, which is the only path a model has.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c3","text":"Nine gates in the deploy path invoked a test runner that has never been installed in this repository, so each failed on every deploy without executing a single assertion; converted to the runtime's own runner, 87 assertions now run on every ship.","tier":"definition","interaction_risk":false,"status":"active","source_ids":[],"why_material":"A gate that cannot execute reports failure indistinguishably from a real violation, which is how one guard was blamed for weeks while it was correct.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c4","text":"The transparency chain had not sealed since 12 August 2026 and was 1,060,446 events behind because no directory row addressed the seal, so nothing could schedule it; it now seals every ten minutes and has passed 2.8 million events.","tier":"definition","interaction_risk":false,"status":"active","source_ids":[],"why_material":"An unsealed event is not covered by a published head, so it is not tamper-evident to anyone outside.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c5","text":"Swapping the sheet agent's model to a non-reasoning variant produced a correct answer that would never have been sent, because the model emitted plain text instead of the reply tag; the settings gate refused the change and quoted the failure.","tier":"definition","interaction_risk":false,"status":"active","source_ids":[],"why_material":"It is the concrete failure that justifies replaying a configuration change before it takes effect.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c6","text":"The build has no formula dependency graph, so a cell cannot hold an expression that recomputes when its inputs change; this is the largest capability Google Sheets has that this surface does not.","tier":"definition","interaction_risk":false,"status":"active","source_ids":[],"why_material":"Reactivity is what separates a spreadsheet from a table, and naming its absence is what keeps the comparison honest.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"c7","text":"The Google Sheets workbook this design was copied from holds 15,790 inventory rows, 3,278 file rows, 784 tool definitions, 2,019 articles with their full text in cells, 10,389 claims and 7,802 sources, plus an Apps Script project whose source is stored in a FileName, FileType, CodeContent table.","tier":"definition","interaction_risk":false,"status":"active","source_ids":[],"why_material":"It establishes that the pattern was proven in an existing product before being rebuilt, and states the prior art precisely.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"the-spreadsheet-as-an-agent-surface","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":7,"retracted_claims":0,"cut_claims":0,"challenges":0,"scrub_events":0,"note":"Retracted/cut claims stay on ledger but are excluded from ask unless ?include_inactive=1"},"counts":{"claims":7,"claims_total":7,"sources":0,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}