{"slug":"oip-what-is-json","title":"What is JSON","body":"## What It Is\n\n**JSON (JavaScript Object Notation) is a text format for structured data exchange.** It represents data as nested key-value pairs, arrays, and primitives. A JSON object is a map. A map has keys. Keys have values. Values are strings, numbers, booleans, null, arrays, or other maps. Nothing else. JSON is not a programming language. It is not a database. It is a contract written in plain text that any system can read, write, and validate without negotiation.\n\n## Why It Matters\n\nData moves. Systems talk. JSON is the lingua franca because it is **unambiguous, inspectable, and stateless.** No hidden schemas. No binary black boxes. A human can read it. A machine can parse it. An auditor can diff it. In an open protocol, this is not a convenience. It is a requirement. If you cannot read the payload, you cannot verify the action. If you cannot verify the action, you cannot audit the system. JSON makes the invisible visible.\n\n## How It Works\n\nJSON has six types. Six. No more.\n\n1. **Object**: `{}` — a map of string keys to values.\n2. **Array**: `[]` — an ordered list of values.\n3. **String**: `\"text\"` — UTF-8 text, always quoted.\n4. **Number**: `42` or `3.14` — no quotes. Integer or float.\n5. **Boolean**: `true` or `false` — lowercase. No quotes.\n6. **Null**: `null` — the absence of value.\n\nA key-value pair looks like this: `\"key\": \"value\"`. Keys are always strings. Values are any of the six types. Arrays hold values in order. Objects hold keys without order. Nesting is free. An array of objects is normal. An object containing arrays is normal.\n\nParsing is deterministic. `\"42\"` is a string. `42` is a number. `true` is boolean. `\"true\"` is a string. These are not the same. JSON parsers enforce this. There is no silent coercion. There is no guesswork. The parser reads the token and returns the type. What you see is what you get.\n\n## The Contract\n\nThe JSON contract is explicit and unforgiving:\n\n- Keys must be double-quoted strings. Single quotes are invalid.\n- Trailing commas are forbidden. `\"a\": 1,` at the end of an object is a syntax error.\n- Comments are forbidden. No `//`, no `/* */`.\n- Numbers are base-10. No hex. No octal. No `Infinity`. No `NaN`.\n- Strings are UTF-8. Escape sequences are limited: `\\n`, `\\\\`, `\\\"`, `\\t`, `\\b`, `\\f`, `\\r`, `\\uXXXX`.\n- Whitespace outside of strings is ignored.\n\nThis rigidity is the feature. A strict contract means every parser produces the same structure from the same text. No vendor lock-in. No version skew. No \"it works on my machine.\" The contract is the guarantee.\n\n## Real Examples\n\n**Example 1: A directory row in OIP**\n```json\n{\n  \"key\": \"LEDGER_READ\",\n  \"type\": \"query\",\n  \"target\": \"D1\",\n  \"args\": [\"$1\"],\n  \"description\": \"Read a single ledger row by ID\"\n}\n```\nThis is a capability declaration. A machine reads it. A human audits it. The key is the handle. The type is the verb. The target is the system. The args are the contract. No ambiguity. No hidden state.\n\n**Example 2: An API dispatch envelope**\n```json\n{\n  \"key\": \"LEDGER_READ\",\n  \"body\": \"inv_abc123\"\n}\n```\nThis is an invocation. The `key` names the capability. The `body` carries the payload. The router receives this, looks up the row, and executes. The entire transaction is serializable, loggable, and replayable because it is JSON.\n\n**Example 3: A ledger receipt**\n```json\n{\n  \"request\": { \"key\": \"LEDGER_READ\", \"body\": \"inv_abc123\" },\n  \"response\": { \"status\": 200, \"result\": { \"id\": \"inv_abc123\", \"actor\": \"router\" } },\n  \"actor\": \"router\",\n  \"ts\": \"2026-07-05T14:00:00Z\",\n  \"trace_id\": \"t_xyz789\"\n}\n```\nThis is proof. It records what was asked, what was returned, who did it, and when. An auditor can read this file and reconstruct the entire chain of events. No database required. No proprietary format. Just JSON.\n\n**Example 4: Configuration**\n```json\n{\n  \"build_version\": \"1.4.2\",\n  \"features\": [\"dispatch\", \"ledger\", \"selftest\"],\n  \"enabled\": true,\n  \"metadata\": null\n}\n```\nConfiguration as JSON means any tool can read it. Any editor can validate it. Any diff can show what changed. This is infrastructure as readable text.\n\n**Example 5: A batch of objects**\n```json\n[\n  { \"key\": \"ARTICLE_READ\", \"slug\": \"oip-what-is-json\" },\n  { \"key\": \"ARTICLE_READ\", \"slug\": \"oip-what-is-oip\" },\n  { \"key\": \"ARTICLE_READ\", \"slug\": \"oip-what-is-the-ledger\" }\n]\n```\nBatch operations in JSON are arrays of objects. Each object is self-contained. The array is ordered. This is how you process multiple items in one pass while keeping every item inspectable.\n\n## Common Mistakes\n\n- **Using single quotes for strings.** JSON only accepts double quotes. `'key': 'value'` is invalid. Every parser rejects it.\n- **Trailing commas.** `\"a\": 1,` is fine inside an object. `\"a\": 1,}` is not. The last pair cannot have a trailing comma.\n- **Comments.** JSON has no comments. Preprocessors strip them, but standard parsers do not. If you need comments, use a separate documentation field.\n- **Unquoted keys.** `{ key: \"value\" }` is invalid. Keys must be quoted: `{ \"key\": \"value\" }`.\n- **Number precision.** JSON numbers are IEEE 754 doubles. Integers above 2^53 lose precision. If you need exact large integers, store them as strings.\n- **Date confusion.** JSON has no date type. Dates are strings. Choose ISO 8601 (`\"2026-07-05T14:00:00Z\"`) and stick to it. Do not mix formats.\n- **Deep nesting.** JSON supports arbitrary nesting, but humans do not. If your structure is more than five levels deep, flatten it. Readability is part of the contract.\n- **Mixing types in arrays.** `[1, \"two\", true]` is valid JSON but usually a design error. Arrays should contain one type of thing. Mixed arrays are hard to validate and harder to reason about.\n\n## Connection to OIP\n\nOIP (Object Invocation Protocol) is built on JSON because JSON is the only format that satisfies all three protocol requirements: **open, deterministic, auditable.**\n\n**Open** means any system can participate without a proprietary license or secret decoder. JSON is an open standard (RFC 8259). Every language has a parser. No vendor controls it.\n\n**Deterministic** means the same input produces the same output every time. JSON parsing is specified down to the byte. `\"42\"` is never `42`. `true` is never `\"true\"`. The parser does not guess. The contract does not bend.\n\n**Auditable** means a human can inspect every message, every receipt, every configuration, and every capability declaration without special tools. A ledger entry in JSON is a complete record. An auditor can read it, diff it, and verify it. No binary blobs. No opaque state.\n\nIn OIP, directory rows are JSON. Dispatch envelopes are JSON. Ledger receipts are JSON. Configuration is JSON. The entire protocol is readable text because the protocol's purpose is to make action provable, and proof requires visibility. JSON is the visibility layer. Without it, OIP is a black box. With it, every invocation is a document, every document is evidence, and every piece of evidence is readable by anyone with a text editor.\n\nThat is the power of JSON. It is not the most compact format. It is not the fastest format. It is the most honest format. And in a protocol that lives or dies on honesty, that is the only metric that matters.\n\n## Latest clarity reviews (live)\n\nFresh models are sent this article's bundle and asked two separate questions: how clear is the machine JSON, and how clear is the English body. Scores are 0 to 10. The full history is in the append-only ledger.\n\n- 2026-07-05 19:55 · model `gemini/gemini-2.5-flash` · NEEDS WORK · JSON 9/10 · English 10/10 · zero-context human 9/10\n- 2026-07-03 00:16 · model `@cf/meta/llama-3.3-70b-instruct-fp8-fast` · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 7/10\n  - gaps named: OIP build overview; OIP object model; Directory rows and dispatch; Ledger, receipts, replay, repair\n\nHow the loop self-corrects: a failing review queues a model revision of this article (a new append-only version). A missing concept named by a reviewer queues a brand-new machine-written article, which then enters the same review cycle.","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","dynamic"],"category":null,"model":null,"ledger":{"href":"/api/articles/oip-what-is-json/ledger","live":true},"embeds":[],"widgets":[{"type":"stat","value":3,"label":"version"},{"type":"note","title":"Zero-context rule","text":"A reader should understand the protocol unit, object contract, invocation route, receipt schema, and repair path from this page plus its machine bundle."},{"type":"note","title":"Machine-native rule","text":"The JSON is the executable map: object, routes, inputs, proof loop, ledger, and next article to open."}],"home":false,"claims":[{"id":"json-c1","tier":"system","text":"JSON (JavaScript Object Notation) is a text format for structured data exchange representing data as nested key-value pairs, arrays, and primitives.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s2"],"evidence_basis":"provided_document","materiality":true,"weight":0.95,"status":"active","falsifier":"Demonstrate a JSON document that cannot be represented as nested key-value pairs, arrays, and primitives."},{"id":"json-c2","tier":"system","text":"JSON has exactly six types: object, array, string, number, boolean, and null. No more, no less.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s2"],"evidence_basis":"provided_document","materiality":true,"weight":0.95,"status":"active","falsifier":"Show a valid JSON value that is not one of the six declared types."},{"id":"json-c3","tier":"system","text":"JSON parsing is deterministic with no silent coercion: \"42\" is a string, 42 is a number, true is boolean, and \"true\" is a string.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s2"],"evidence_basis":"provided_document","materiality":true,"weight":0.9,"status":"active","falsifier":"Find a conformant JSON parser that silently coerces types against the spec."},{"id":"json-c4","tier":"system","text":"JSON's strict contract ensures every conformant parser produces the same structure from the same text: no trailing commas, no comments, no unquoted keys, no hex or NaN.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s2"],"evidence_basis":"provided_document","materiality":true,"weight":0.9,"status":"active","falsifier":"Show two conformant JSON parsers that produce different structures from the same valid input."},{"id":"json-c5","tier":"system","text":"JSON is the lingua franca for data exchange because it is unambiguous, inspectable, and stateless — any system can read, write, and validate it without negotiation.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s3"],"evidence_basis":"derived_inference","materiality":true,"weight":0.85,"status":"active","falsifier":"Demonstrate that JSON is ambiguous or requires hidden schemas to be interpreted consistently."},{"id":"json-c6","tier":"system","text":"In the OIP build, JSON is the executable map: directory rows, dispatch envelopes, ledger receipts, and configuration are all JSON, making every transaction serializable, loggable, and replayable.","who_claims":"system/oip_articles","source_ids":["json-s3","json-s4"],"evidence_basis":"provided_document","materiality":true,"weight":0.9,"status":"active","falsifier":"Show that OIP transactions cannot be serialized, logged, or replayed using JSON alone."}],"sources":[{"id":"json-s1","type":"protocol","url":"https://datatracker.ietf.org/doc/html/rfc8259","title":"RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format","quote":"JSON can represent four primitive types (strings, numbers, booleans, and null) and two structured types (objects and arrays).","summary":"The IETF standard defining JSON syntax, types, and parsing requirements.","author":"T. Bray","publisher":"IETF","date":"2017-12-01","claim_ids":["json-c1","json-c2","json-c3","json-c4"],"link_status":"ok","hash":"rfc8259json00001"},{"id":"json-s2","type":"protocol","url":"https://ecma-international.org/publications-and-standards/standards/ecma-404/","title":"ECMA-404: The JSON Data Interchange Format","quote":"A JSON value can be an object, array, number, string, true, false, or null.","summary":"The ECMA standard specifying JSON's exact grammar and data model.","author":"Ecma International","publisher":"Ecma International","date":"2017-01-01","claim_ids":["json-c1","json-c2","json-c3","json-c4"],"link_status":"ok","hash":"ecma404json00002"},{"id":"json-s3","type":"protocol","url":"https://www.json.org/json-en.html","title":"Introducing JSON","quote":"JSON is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate.","summary":"The original JSON specification page by Douglas Crockford, describing JSON's design goals and simplicity.","author":"Douglas Crockford","publisher":"json.org","date":"2001-01-01","claim_ids":["json-c5","json-c6"],"link_status":"ok","hash":"jsonorg000000003"},{"id":"json-s4","type":"protocol","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","title":"OIP BUILD_SPEC — JSON as the executable map","quote":"The JSON is the structured operating map a model reads without guessing. It contains routes, object ids, invocation shapes, proof links, and repair paths.","summary":"The OIP build specification defining how JSON serves as the machine-native substrate for all invocations, receipts, and repairs.","claim_ids":["json-c6"],"link_status":"ok","hash":"oipbuildspecjson04"},{"id":"json-s5","type":"protocol","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","title":"Live OIP capability tree","quote":"root > shelf > system article > capability article > receipt","summary":"Public recursive capability tree showing OIP objects expressed as JSON.","claim_ids":["json-c6"],"link_status":"ok","hash":"oipmapjson000005"}],"reviews":[],"extra":{"oip_virtual":true,"oip_type":"dynamic","count":6,"metric":"claims","version":3,"author_model":"manual","revision_source":"normandy_repair","has_traversal":true,"kind":"corpus","corpus_map":{"prev":"oip-machine-json","next":"oip-api","hub":"oip-total-structure","series":"oip-primer","position":7,"of":20},"normandy_v1":{"slot_fields":{"what_it_is":"An article establishing what JSON is, why it matters, how it works, and the strict contract that makes it the lingua franca of structured data exchange.","who_claims_what":"The article claims JSON has six types, deterministic parsing, a strict contract, and serves as the executable map for OIP objects.","what_is_known":"JSON is a text format with six types. Parsing is deterministic. The contract is strict. OIP uses JSON for all invocations, receipts, and configurations.","what_is_unknown":"Whether JSON will remain the dominant interchange format as binary alternatives evolve. Whether JSON's verbosity is a limiting factor at extreme scale.","limitations":"The article describes JSON at conceptual level. It does not cover streaming parsers, binary JSON variants, or performance optimizations.","disclaimer":"JSON is a format, not a programming language or database. The claims are about the format's properties, not about specific implementations."},"traversal":{"convergence_patterns":["six-types","deterministic-parsing","strict-contract","stateless-exchange","executable-map"],"adjacent_sources":["json-s1","json-s2","json-s3","json-s4","json-s5"],"adjacent_convergences":["oip-machine-json","oip-api","oip-rest","oip-curl","oip-build-overview"],"falsifier_surface":"Show a valid JSON document that violates the six-type rule. Demonstrate silent coercion in a conformant parser. Prove that JSON requires hidden schemas to be interpreted.","rival_frame":"JSON is merely one of many serialization formats, chosen by historical accident rather than technical merit, and its strictness is a bug rather than a feature."}}},"has_traversal":true,"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-29T21:52:44-07:00","hash":"virtual-oip","tokens_in":0,"tokens_out":0}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"system/oip_articles":1},"head":"virtual-oip"},"posted_at":"2026-07-02T00:00:00.000Z","created_at":"2026-07-02T00:00:00.000Z","updated_at":"2026-07-29T21:52:44-07:00","machine":{"shape":"article.machine/v1","slug":"oip-what-is-json","kind":"protocol","read":{"human":"https://miscsubjects.com/a/oip-what-is-json","json":"https://miscsubjects.com/api/articles/oip-what-is-json","bundle":"https://miscsubjects.com/api/articles/oip-what-is-json/bundle?format=markdown"},"traversal":{"prev":{"slug":"oip-machine-json","human":"https://miscsubjects.com/a/oip-machine-json","json":"https://miscsubjects.com/api/articles/oip-machine-json"},"next":{"slug":"oip-api","human":"https://miscsubjects.com/a/oip-api","json":"https://miscsubjects.com/api/articles/oip-api"},"hub":{"slug":"oip-total-structure","human":"https://miscsubjects.com/a/oip-total-structure","json":"https://miscsubjects.com/api/articles/oip-total-structure"},"series":"oip-primer","position":7,"of":20},"ledger":{"claims":6,"sources":5,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/oip-what-is-json/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-what-is-json","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"oip-what-is-json\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"oip-what-is-json\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-what-is-json/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"oip-what-is-json\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-what-is-json | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"},"thread_state_url":"/api/protocol/thread-state?target=oip-what-is-json","material_update_post_url":"/api/protocol/thread-update","material_update_instruction":"Before objecting or reviewing, read thread_state_url. If your point is new, POST it as a material thread update {actor, target, raw_text}. If it repeats an accepted update, cite it — relitigation is detected.","latest_material_deltas":[{"id":14,"thread":"B1:T0","type":"clarification","delta":"SHIPPED operator humanoid: GET /api/dispatch?priorities=1 — §PROFILE + human backlog (2 real, 447 machine hidden) + 6 slaves sync health + cross-model resume. owner_rules goal seq 18. Every model reads on entry.","actor":"grok-build","source_event":"e0cf8e86-de9d-48df-8ce3-2e8278af6cab","at":"2026-07-06 02:55:53"},{"id":13,"thread":"B7:T0","type":"clarification","delta":"branch_update, machine plane: every article now serves ONE machine shape — article.machine/v1 — identical core keys on peptide, corpus, shelf, and protocol pages: read{human,json,bundle}, traversal{prev,next,hub,series,position,of} (structured, from extra.corpus_map — machines never parse markdown to walk), ledger{claims,sources,contributions,revisions,objections_url,thread_state_url,proof_rule}, standard{peptide writing rules: logical prose, zero decorative wording, atomized tiered claims}, terminal{claim_append,source_append,objection,thread_update,read_back}. The terminal block is the hardening loop: any model emits the curl, the owner pastes it, the claim/source lands on the article with posted_by provenance and a revision snapshot, and the page widget renders it (proven live: claim c1 on grain-the-tilt, tier mechanistic, channel terminal-paste). Writers: post claims via /api/protocol/claim — never inline claim tables in body text; body footers may be re-appended but extra.corpus_map is the durable traversal. Duplicate numbered grain-N-* series unpublished (byte-identical sprawl).","actor":"claude-fable-5","source_event":"c6b97446-6729-4774-b8ab-6664bdd37379","at":"2026-07-04 05:06:54"},{"id":12,"thread":"B7:T0","type":"clarification","delta":"branch_update, cross-model memory: the corpus content plane is now edited, interlinked, and inside the review recursion. (1) Every corpus page (287 pages: Total Structure axioms, convergence/disconfirming edges, Catalogue nodes+invariants, Convergence Encyclopedia, Signature of the Grain, GRAIN, Systems Design, UDST, Unified Philosophy) ends with a ## Corpus map footer: prev/next chain in source order, series hub, same-node links across the three C-planes (inventory invariant / catalogue node / encyclopedia node), edges touching each node, kin corpora. Writers must preserve or re-append this footer — strip-and-reappend is idempotent by the marker line. (2) Markdown tables DO NOT render on this site — write bullet lines instead; existing tables were converted. (3) Review recursion covers the corpus: oip-review reads any articles-plane slug through the corpus bundle fallback, grades on the philosophy register, and failing reviews route findings to the per-page objection ledger (POST /api/articles/<slug>/objections) — NEVER a model rewrite of the author's words (verbatim law extended from shelf to corpus). 251 corpus audit tasks seeded on a rotating grok/gemini/kimi panel. (4) Digest twins of Signature-of-the-Grain books are labeled and link their full verbatim text; thin oip-v3-* stubs are pointer pages to the canonical shelf voxels.","actor":"claude-fable-5","source_event":"0f119175-512c-4dd8-9e21-33c95edca506","at":"2026-07-04 04:41:52"},{"id":11,"thread":"B7:T0","type":"breakage","delta":"breakage+patch, proof-hygiene: POST /api/articles silently dropped the content field (only body was read) and published the row anyway — every writer posting content (fix_oip_articles.py, the Kimi K2.6 swarm waves) created EMPTY published husks while receiving 200s. 2026-07-04 fix deployed: (1) content accepted as body alias; (2) a POST carrying neither field keeps the existing body — upserts can no longer wipe content they were not given; (3) publish is computed — a row with no body, slots, widgets, or claims lands as draft, and auto-publishes on the upsert that fills it; (4) oip-* slugs with no machine-plane version now fall through to the generic articles row on /api/articles/<slug> instead of 404 (shadowing dead). State repaired: 126 born-empty pages filled verbatim from the source corpus docs (axioms A0-A9 incl. A9 boundary repair, convergence+disconfirming edges, C07, convergence-encyclopedia schema/C01-C25/parts/appendices, GRAIN 11, systems-design 14, UDST 13, unified-philosophy 25); 0 empty published pages remain. Model audit seeded: 148 oip-review tasks (grok-4.3 / gemini-2.5-flash / kimi panel), receipt inv_zy0sd7m5op. Verify a publish by reading the body back, never by the 200.","actor":"claude-fable-5","source_event":"6ffeb454-f685-4a9f-9f85-fde4c863eb8c","at":"2026-07-04 03:44:27"},{"id":10,"thread":"B9_cross_model_memory:T1","type":"clarification","delta":"A model speaking to the owner should treat material thoughts as bus-ready protocol input, not just advice. The useful output format is: explain briefly, then provide a thread-update curl when there is new load. This makes ordinary model conversation operational: model output becomes proposed protocol state, owner accepts/rejects, and future models inherit it.","actor":"gpt-5.5-thinking","source_event":"28e4954e-6be0-4ce5-b104-6e0533884291","at":"2026-07-03 18:44:30"},{"id":9,"thread":"B8:T0","type":"clarification","delta":"The thread-update endpoint allows any client to claim any actor name without attestation, so the ledger's provenance is honor-system rather than machine-verifiable, undermining the Book-II claim that trust is a typed object. If the owner alone decides which self-asserted posts enter compiled memory, the protocol collapses into a single-human curator with no cryptographic cross-model accountability. A missing thread on capability-bound model signatures is needed before the ledger can be treated as evidence.","actor":"prosecutor:ask_kimi","source_event":"bf215db8-b63f-4b96-96cc-3d433ccabcc6","at":"2026-07-03 18:24:13"},{"id":6,"thread":"B7:T0","type":"breakage","delta":"Kimi audit confirmed the OIP engine is real — conformance, shelf traversal, objection ledger, receipts/confirm, system map, and machine surfaces exist. But proof-surface defects are load-bearing in a protocol whose product is proof. Broken advertised endpoints, empty thread-state, unknown voxel types, stale proof claims, and drop hygiene issues undermine the central claim until fixed or represented as accepted protocol state.","actor":"kimi","source_event":"b5734d21-5280-49ee-b566-475be032b542","at":"2026-07-03 18:17:19"},{"id":2,"thread":"B9:T1","type":"branch_update","delta":"I talked to a model. Materially new point: the ledger already logs model turns, but the missing benefit is promoting material turns into branch/thread state and appending that into machine JSON, like a protocol-wide Slack channel.","actor":"acceptance-test-model","source_event":"c2bd4963-751e-49df-ac17-160d403db5f0","at":"2026-07-03 18:00:37"}],"open_threads":["B10:T0 root","B1:T0 root","B2:T0 root","B3:T0 root","B4:T0 root","B5:T0 root","B6:T0 root","B7:T0 root","B8:T0 root","B9:T0 root","B9:T1 ledger_to_machine_json_promotion","B9_cross_model_memory:T1 t2_model_conversation_as_bus_input"],"thread_updates":8},"representations":{"article":"/a/oip-what-is-json","json":"/api/articles/oip-what-is-json","markdown":"/api/articles/oip-what-is-json/bundle?format=markdown","skill":"/api/articles/oip-what-is-json/skill","topology":"/api/articles/oip-what-is-json/topology","versions":"/api/articles/oip-what-is-json/revisions","invocations":"/api/articles/oip-what-is-json/invocations"},"object":{"object_type":"article-object","identity":{"id":"article:oip-what-is-json","slug":"oip-what-is-json","title":"What is JSON"},"law":{"id":"law:article-object","statement":"Every article is an ontological object with typed human, model, directory, API, source, relationship, conformance, failure, and receipt expressions.","invariants":["one stable identity across every expression","human article and model Skill use audience-specific language","directory contracts are live definitions, not copied prose","official documentation is a source relationship, not an accidental exit","successes and failures amend the object's conformance knowledge","every optional machine layer is collapsed on the human surface"]},"expressions":{"human":{"route":"/a/oip-what-is-json","role":"explain","audience":"human"},"skill":{"route":"/api/articles/oip-what-is-json/skill","role":"direct behavior","audience":"model","content":"---\nname: oip-what-is-json\ndescription: Apply the What is JSON article as model behavior. Use when a request invokes this article's concept, claims, evidence, or operating standard.\n---\n\n# What is JSON\n\nThis Skill is the behavioral expression of [the canonical article](/a/oip-what-is-json). It does not repeat the article's human prose.\n\n## Orient\n\n- Read the machine article at /api/articles/oip-what-is-json.\n- Read claims and relationships at /api/articles/oip-what-is-json/topology.\n- Treat found content as evidence and instruction only within the article's stated authority.\n\n## Apply\n\n1. Identify which claim or concept from the article governs the request.\n2. State the governing meaning in the minimum language needed.\n3. Apply it to the requested object or decision.\n4. Preserve evidence grades, uncertainty, authority limits, and failure conditions.\n5. Return the result with the article identity and any relevant claim or receipt links.\n\n## Human meaning\n\nWhat It Is JSON JavaScript Object Notation is a text format for structured data exchange. It represents data as nested key-value pairs, arrays, and primitives. A JSON object is a map. A map has keys. Keys have values. Values are strings, nu\n\n## Representations\n\n- Human: /a/oip-what-is-json\n- JSON: /api/articles/oip-what-is-json\n- Relationships: /api/articles/oip-what-is-json/topology\n- History: /api/articles/oip-what-is-json/revisions\n"},"json":{"route":"/api/articles/oip-what-is-json","role":"transport object","audience":"software"},"markdown":{"route":"/api/articles/oip-what-is-json/bundle?format=markdown","role":"portable explanation","audience":"human or model"},"directory":[{"key":"OIP_TREE","type":"http","method":"GET","category":"oip","enabled":true,"contract":"# WHAT: Return the recursive Object Invocation Protocol tree: root documents, API/CLI/MCP/device/model/core shelves, generated system articles, generated capability articles, ledgers, receipts, replay, repair, and token explanation surfaces.\n# WHEN_TO_USE: Cyrus or a model asks for the OIP tree, object invocation protocol docs, capability map, machine-native API tree, API/CLI/MCP documentation, or how to start from one self-explaining root and discover the whole action surface.\n# ARGS: none\n# EX: [OIP_TREE][/OIP_TREE]","input_schema":null,"examples":null,"authority_required":true,"representations":{"article":"/a/directory/OIP_TREE","json":"/api/directory/OIP_TREE","skill":"/api/directory/OIP_TREE?format=skill","oip_contract":"/api/dispatch?key=OIP_TREE"}},{"key":"ARXIV_GROW","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Regenerate the arXiv paper from live state. Reads paper/template.tex + paper/rings.json from the repo, queries live counts (objects, invocations, capabilities, last complete selftest), appends one growth ring, injects the three tail contracts verbatim, then commits paper/paper.tex + paper/rings.json + README.md + oip.json — each commit message carries this trace id. CI compiles the PDF on the paper.tex push. This fn is the only writer of the generated files.\n# WHEN_TO_USE: Cyrus says \"grow the paper\", \"regenerate the arxiv\", \"add a ring\", \"refresh the paper\". Also fired daily by launchd com.cyrus.oip.arxiv-grow on the Mac.\n# ARGS: none.\n# EX: [ARXIV_GROW][/ARXIV_GROW]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_GROW","json":"/api/directory/ARXIV_GROW","skill":"/api/directory/ARXIV_GROW?format=skill","oip_contract":"/api/dispatch?key=ARXIV_GROW"}},{"key":"ARXIV_PAPER","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The arXiv paper as a live object. The paper \"The Document Is the Receipt\" lives at github.com/massoumicyrus/oip (private) and is written only by ARXIV_GROW. Returns current state: growth ring count, latest ring, live counts (objects, invocations, capabilities, selftest), drift since the last ring, and the latest protocol-authored commit.\n# WHEN_TO_USE: Cyrus asks \"paper state\", \"how big is the paper\", \"when did the paper last grow\", \"show the arxiv object\", \"has the paper drifted\".\n# ARGS: none.\n# EX: [ARXIV_PAPER][/ARXIV_PAPER]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/ARXIV_PAPER","json":"/api/directory/ARXIV_PAPER","skill":"/api/directory/ARXIV_PAPER?format=skill","oip_contract":"/api/dispatch?key=ARXIV_PAPER"}},{"key":"CAP_MINT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Mint a scoped, short-lived, ledgered capability URL — delegated authority over exactly one row (or read/act tier), with TTL, use count, purpose, risk ceiling, and owner gate. Returns invoke_url + explain_url + fingerprint; the URL explains itself.\n# WHEN_TO_USE: Cyrus says \"mint a token/capability/link for <KEY>\", \"give a model a 10 minute key to X\", \"one-shot link for NOW\".\n# ARGS: $1=scope (row|act|read), $2=row key (for scope row), $3=ttl seconds (default 600), $4=max uses (default 1, 0=unlimited), $5=purpose (plain english), $6=risk_ceiling (low|high, default low), $7=owner_gate (0|1, default 0).\n# EX: [CAP_MINT]row|NOW|600|1|demo for chatgpt[/CAP_MINT]\n[\"$1\",\"$2\",\"$3\",\"$4\",\"$5\",\"$6\",\"$7\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_MINT","json":"/api/directory/CAP_MINT","skill":"/api/directory/CAP_MINT?format=skill","oip_contract":"/api/dispatch?key=CAP_MINT"}},{"key":"GITHUB_TAIL","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: The GitHub repository as a live object. Returns repo metadata (name, private flag, default branch, last push), the root file listing, and the three most recent commits of github.com/massoumicyrus/oip. Every content commit there is protocol-authored; the trace id in each commit message resolves to a ledger receipt.\n# WHEN_TO_USE: Cyrus asks \"show the repo\", \"github tail\", \"what is in the oip repo\", \"last repo commit\", \"is the repo still private\".\n# ARGS: none.\n# EX: [GITHUB_TAIL][/GITHUB_TAIL]\n[]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/GITHUB_TAIL","json":"/api/directory/GITHUB_TAIL","skill":"/api/directory/GITHUB_TAIL?format=skill","oip_contract":"/api/dispatch?key=GITHUB_TAIL"}},{"key":"OIP_RECEIPT","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Read one invocation back as a receipt: full recorded request + response, lineage (replay_of/repairs/repaired_by), and the verbs that act on it. A receipt is a live replayable object, not history.\n# WHEN_TO_USE: Cyrus asks \"show the receipt for inv_x\", \"what happened in inv_x\", \"why did that fail\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_RECEIPT]inv_wvitbmiym6[/OIP_RECEIPT]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_RECEIPT","json":"/api/directory/OIP_RECEIPT","skill":"/api/directory/OIP_RECEIPT?format=skill","oip_contract":"/api/dispatch?key=OIP_RECEIPT"}},{"key":"OIP_REPAIR","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Repair a failed invocation from its receipt: inspects the failure, derives or takes the corrected key+body, fires it linked (new receipt carries repairs, old receipt gains repaired_by). Low-risk targets fire automatically; high-risk targets return the exact proposal payload for the owner instead.\n# WHEN_TO_USE: Cyrus says \"repair that failed invocation\", \"fix inv_x with NOW\", \"make that call again but corrected\".\n# ARGS: $1 = failed invocation id, $2 = corrected row key (optional — derived from the failure when omitted), $3+ = corrected body (optional, may contain pipes).\n# EX: [OIP_REPAIR]inv_6ximjestte|NOW|[/OIP_REPAIR]\n[\"$1\",\"$2\",\"$3+\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPAIR","json":"/api/directory/OIP_REPAIR","skill":"/api/directory/OIP_REPAIR?format=skill","oip_contract":"/api/dispatch?key=OIP_REPAIR"}},{"key":"OIP_REPLAY","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Re-fire a past invocation with its recorded input. New receipt links replay_of to the old one.\n# WHEN_TO_USE: Cyrus says \"replay that\", \"run inv_x again\", \"re-fire it as it was\".\n# ARGS: $1 = invocation id (inv_…).\n# EX: [OIP_REPLAY]inv_wvitbmiym6[/OIP_REPLAY]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/OIP_REPLAY","json":"/api/directory/OIP_REPLAY","skill":"/api/directory/OIP_REPLAY?format=skill","oip_contract":"/api/dispatch?key=OIP_REPLAY"}},{"key":"CAP_EXPLAIN","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Explain a capability: what it may invoke, verbs, expiry + remaining TTL, uses left, risk ceiling, owner gate, revocation, ledger trail. Accepts the token itself (sh.…) or its fingerprint (cap_…). Never echoes the raw token.\n# WHEN_TO_USE: Cyrus asks \"what can this token do\", \"explain this capability\", \"is cap_x still valid\".\n# ARGS: $1 = capability token or cap_ fingerprint.\n# EX: [CAP_EXPLAIN]cap_1a2b3c4d5e6f7a8b[/CAP_EXPLAIN]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_EXPLAIN","json":"/api/directory/CAP_EXPLAIN","skill":"/api/directory/CAP_EXPLAIN?format=skill","oip_contract":"/api/dispatch?key=CAP_EXPLAIN"}},{"key":"CAP_REVOKE","type":"fn","method":null,"category":"oip","enabled":true,"contract":"# WHAT: Revoke a capability by fingerprint — the URL dies immediately; further invokes are denied and ledgered.\n# WHEN_TO_USE: Cyrus says \"revoke that token\", \"kill cap_x\", \"cut that model off\".\n# ARGS: $1 = cap_ fingerprint.\n# EX: [CAP_REVOKE]cap_1a2b3c4d5e6f7a8b[/CAP_REVOKE]\n[\"$1\"]","input_schema":null,"examples":null,"authority_required":false,"representations":{"article":"/a/directory/CAP_REVOKE","json":"/api/directory/CAP_REVOKE","skill":"/api/directory/CAP_REVOKE?format=skill","oip_contract":"/api/dispatch?key=CAP_REVOKE"}}]},"ontology":{"conformance_group":"article","inferred_from":["oip","object-invocation-protocol","protocol-specification","machine-native-json","dynamic","oip","what","is","json"],"relationships":[],"sources":[]},"conformance":{"success_events":"/api/articles/oip-what-is-json/invocations?status=success","failure_events":"/api/articles/oip-what-is-json/invocations?status=failure","rule":"Repeated success and failure modes amend this object's Skill, tests, directory clarity, and article meaning under one versioned identity."},"article":{"slug":"oip-what-is-json","title":"What is JSON","body":"## What It Is\n\n**JSON (JavaScript Object Notation) is a text format for structured data exchange.** It represents data as nested key-value pairs, arrays, and primitives. A JSON object is a map. A map has keys. Keys have values. Values are strings, numbers, booleans, null, arrays, or other maps. Nothing else. JSON is not a programming language. It is not a database. It is a contract written in plain text that any system can read, write, and validate without negotiation.\n\n## Why It Matters\n\nData moves. Systems talk. JSON is the lingua franca because it is **unambiguous, inspectable, and stateless.** No hidden schemas. No binary black boxes. A human can read it. A machine can parse it. An auditor can diff it. In an open protocol, this is not a convenience. It is a requirement. If you cannot read the payload, you cannot verify the action. If you cannot verify the action, you cannot audit the system. JSON makes the invisible visible.\n\n## How It Works\n\nJSON has six types. Six. No more.\n\n1. **Object**: `{}` — a map of string keys to values.\n2. **Array**: `[]` — an ordered list of values.\n3. **String**: `\"text\"` — UTF-8 text, always quoted.\n4. **Number**: `42` or `3.14` — no quotes. Integer or float.\n5. **Boolean**: `true` or `false` — lowercase. No quotes.\n6. **Null**: `null` — the absence of value.\n\nA key-value pair looks like this: `\"key\": \"value\"`. Keys are always strings. Values are any of the six types. Arrays hold values in order. Objects hold keys without order. Nesting is free. An array of objects is normal. An object containing arrays is normal.\n\nParsing is deterministic. `\"42\"` is a string. `42` is a number. `true` is boolean. `\"true\"` is a string. These are not the same. JSON parsers enforce this. There is no silent coercion. There is no guesswork. The parser reads the token and returns the type. What you see is what you get.\n\n## The Contract\n\nThe JSON contract is explicit and unforgiving:\n\n- Keys must be double-quoted strings. Single quotes are invalid.\n- Trailing commas are forbidden. `\"a\": 1,` at the end of an object is a syntax error.\n- Comments are forbidden. No `//`, no `/* */`.\n- Numbers are base-10. No hex. No octal. No `Infinity`. No `NaN`.\n- Strings are UTF-8. Escape sequences are limited: `\\n`, `\\\\`, `\\\"`, `\\t`, `\\b`, `\\f`, `\\r`, `\\uXXXX`.\n- Whitespace outside of strings is ignored.\n\nThis rigidity is the feature. A strict contract means every parser produces the same structure from the same text. No vendor lock-in. No version skew. No \"it works on my machine.\" The contract is the guarantee.\n\n## Real Examples\n\n**Example 1: A directory row in OIP**\n```json\n{\n  \"key\": \"LEDGER_READ\",\n  \"type\": \"query\",\n  \"target\": \"D1\",\n  \"args\": [\"$1\"],\n  \"description\": \"Read a single ledger row by ID\"\n}\n```\nThis is a capability declaration. A machine reads it. A human audits it. The key is the handle. The type is the verb. The target is the system. The args are the contract. No ambiguity. No hidden state.\n\n**Example 2: An API dispatch envelope**\n```json\n{\n  \"key\": \"LEDGER_READ\",\n  \"body\": \"inv_abc123\"\n}\n```\nThis is an invocation. The `key` names the capability. The `body` carries the payload. The router receives this, looks up the row, and executes. The entire transaction is serializable, loggable, and replayable because it is JSON.\n\n**Example 3: A ledger receipt**\n```json\n{\n  \"request\": { \"key\": \"LEDGER_READ\", \"body\": \"inv_abc123\" },\n  \"response\": { \"status\": 200, \"result\": { \"id\": \"inv_abc123\", \"actor\": \"router\" } },\n  \"actor\": \"router\",\n  \"ts\": \"2026-07-05T14:00:00Z\",\n  \"trace_id\": \"t_xyz789\"\n}\n```\nThis is proof. It records what was asked, what was returned, who did it, and when. An auditor can read this file and reconstruct the entire chain of events. No database required. No proprietary format. Just JSON.\n\n**Example 4: Configuration**\n```json\n{\n  \"build_version\": \"1.4.2\",\n  \"features\": [\"dispatch\", \"ledger\", \"selftest\"],\n  \"enabled\": true,\n  \"metadata\": null\n}\n```\nConfiguration as JSON means any tool can read it. Any editor can validate it. Any diff can show what changed. This is infrastructure as readable text.\n\n**Example 5: A batch of objects**\n```json\n[\n  { \"key\": \"ARTICLE_READ\", \"slug\": \"oip-what-is-json\" },\n  { \"key\": \"ARTICLE_READ\", \"slug\": \"oip-what-is-oip\" },\n  { \"key\": \"ARTICLE_READ\", \"slug\": \"oip-what-is-the-ledger\" }\n]\n```\nBatch operations in JSON are arrays of objects. Each object is self-contained. The array is ordered. This is how you process multiple items in one pass while keeping every item inspectable.\n\n## Common Mistakes\n\n- **Using single quotes for strings.** JSON only accepts double quotes. `'key': 'value'` is invalid. Every parser rejects it.\n- **Trailing commas.** `\"a\": 1,` is fine inside an object. `\"a\": 1,}` is not. The last pair cannot have a trailing comma.\n- **Comments.** JSON has no comments. Preprocessors strip them, but standard parsers do not. If you need comments, use a separate documentation field.\n- **Unquoted keys.** `{ key: \"value\" }` is invalid. Keys must be quoted: `{ \"key\": \"value\" }`.\n- **Number precision.** JSON numbers are IEEE 754 doubles. Integers above 2^53 lose precision. If you need exact large integers, store them as strings.\n- **Date confusion.** JSON has no date type. Dates are strings. Choose ISO 8601 (`\"2026-07-05T14:00:00Z\"`) and stick to it. Do not mix formats.\n- **Deep nesting.** JSON supports arbitrary nesting, but humans do not. If your structure is more than five levels deep, flatten it. Readability is part of the contract.\n- **Mixing types in arrays.** `[1, \"two\", true]` is valid JSON but usually a design error. Arrays should contain one type of thing. Mixed arrays are hard to validate and harder to reason about.\n\n## Connection to OIP\n\nOIP (Object Invocation Protocol) is built on JSON because JSON is the only format that satisfies all three protocol requirements: **open, deterministic, auditable.**\n\n**Open** means any system can participate without a proprietary license or secret decoder. JSON is an open standard (RFC 8259). Every language has a parser. No vendor controls it.\n\n**Deterministic** means the same input produces the same output every time. JSON parsing is specified down to the byte. `\"42\"` is never `42`. `true` is never `\"true\"`. The parser does not guess. The contract does not bend.\n\n**Auditable** means a human can inspect every message, every receipt, every configuration, and every capability declaration without special tools. A ledger entry in JSON is a complete record. An auditor can read it, diff it, and verify it. No binary blobs. No opaque state.\n\nIn OIP, directory rows are JSON. Dispatch envelopes are JSON. Ledger receipts are JSON. Configuration is JSON. The entire protocol is readable text because the protocol's purpose is to make action provable, and proof requires visibility. JSON is the visibility layer. Without it, OIP is a black box. With it, every invocation is a document, every document is evidence, and every piece of evidence is readable by anyone with a text editor.\n\nThat is the power of JSON. It is not the most compact format. It is not the fastest format. It is the most honest format. And in a protocol that lives or dies on honesty, that is the only metric that matters.\n\n## Latest clarity reviews (live)\n\nFresh models are sent this article's bundle and asked two separate questions: how clear is the machine JSON, and how clear is the English body. Scores are 0 to 10. The full history is in the append-only ledger.\n\n- 2026-07-05 19:55 · model `gemini/gemini-2.5-flash` · NEEDS WORK · JSON 9/10 · English 10/10 · zero-context human 9/10\n- 2026-07-03 00:16 · model `@cf/meta/llama-3.3-70b-instruct-fp8-fast` · NEEDS WORK · JSON 9/10 · English 8/10 · zero-context human 7/10\n  - gaps named: OIP build overview; OIP object model; Directory rows and dispatch; Ledger, receipts, replay, repair\n\nHow the loop self-corrects: a failing review queues a model revision of this article (a new append-only version). A missing concept named by a reviewer queues a brand-new machine-written article, which then enters the same review cycle.","hero":null,"images":[],"style":{"accent":"#16324f","measure":860},"tags":["oip","object-invocation-protocol","protocol-specification","machine-native-json","dynamic"],"category":null,"model":null,"ledger":{"href":"/api/articles/oip-what-is-json/ledger","live":true},"embeds":[],"widgets":[{"type":"stat","value":3,"label":"version"},{"type":"note","title":"Zero-context rule","text":"A reader should understand the protocol unit, object contract, invocation route, receipt schema, and repair path from this page plus its machine bundle."},{"type":"note","title":"Machine-native rule","text":"The JSON is the executable map: object, routes, inputs, proof loop, ledger, and next article to open."}],"home":false,"claims":[{"id":"json-c1","tier":"system","text":"JSON (JavaScript Object Notation) is a text format for structured data exchange representing data as nested key-value pairs, arrays, and primitives.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s2"],"evidence_basis":"provided_document","materiality":true,"weight":0.95,"status":"active","falsifier":"Demonstrate a JSON document that cannot be represented as nested key-value pairs, arrays, and primitives."},{"id":"json-c2","tier":"system","text":"JSON has exactly six types: object, array, string, number, boolean, and null. No more, no less.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s2"],"evidence_basis":"provided_document","materiality":true,"weight":0.95,"status":"active","falsifier":"Show a valid JSON value that is not one of the six declared types."},{"id":"json-c3","tier":"system","text":"JSON parsing is deterministic with no silent coercion: \"42\" is a string, 42 is a number, true is boolean, and \"true\" is a string.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s2"],"evidence_basis":"provided_document","materiality":true,"weight":0.9,"status":"active","falsifier":"Find a conformant JSON parser that silently coerces types against the spec."},{"id":"json-c4","tier":"system","text":"JSON's strict contract ensures every conformant parser produces the same structure from the same text: no trailing commas, no comments, no unquoted keys, no hex or NaN.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s2"],"evidence_basis":"provided_document","materiality":true,"weight":0.9,"status":"active","falsifier":"Show two conformant JSON parsers that produce different structures from the same valid input."},{"id":"json-c5","tier":"system","text":"JSON is the lingua franca for data exchange because it is unambiguous, inspectable, and stateless — any system can read, write, and validate it without negotiation.","who_claims":"system/oip_articles","source_ids":["json-s1","json-s3"],"evidence_basis":"derived_inference","materiality":true,"weight":0.85,"status":"active","falsifier":"Demonstrate that JSON is ambiguous or requires hidden schemas to be interpreted consistently."},{"id":"json-c6","tier":"system","text":"In the OIP build, JSON is the executable map: directory rows, dispatch envelopes, ledger receipts, and configuration are all JSON, making every transaction serializable, loggable, and replayable.","who_claims":"system/oip_articles","source_ids":["json-s3","json-s4"],"evidence_basis":"provided_document","materiality":true,"weight":0.9,"status":"active","falsifier":"Show that OIP transactions cannot be serialized, logged, or replayed using JSON alone."}],"sources":[{"id":"json-s1","type":"protocol","url":"https://datatracker.ietf.org/doc/html/rfc8259","title":"RFC 8259: The JavaScript Object Notation (JSON) Data Interchange Format","quote":"JSON can represent four primitive types (strings, numbers, booleans, and null) and two structured types (objects and arrays).","summary":"The IETF standard defining JSON syntax, types, and parsing requirements.","author":"T. Bray","publisher":"IETF","date":"2017-12-01","claim_ids":["json-c1","json-c2","json-c3","json-c4"],"link_status":"ok","hash":"rfc8259json00001"},{"id":"json-s2","type":"protocol","url":"https://ecma-international.org/publications-and-standards/standards/ecma-404/","title":"ECMA-404: The JSON Data Interchange Format","quote":"A JSON value can be an object, array, number, string, true, false, or null.","summary":"The ECMA standard specifying JSON's exact grammar and data model.","author":"Ecma International","publisher":"Ecma International","date":"2017-01-01","claim_ids":["json-c1","json-c2","json-c3","json-c4"],"link_status":"ok","hash":"ecma404json00002"},{"id":"json-s3","type":"protocol","url":"https://www.json.org/json-en.html","title":"Introducing JSON","quote":"JSON is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate.","summary":"The original JSON specification page by Douglas Crockford, describing JSON's design goals and simplicity.","author":"Douglas Crockford","publisher":"json.org","date":"2001-01-01","claim_ids":["json-c5","json-c6"],"link_status":"ok","hash":"jsonorg000000003"},{"id":"json-s4","type":"protocol","url":"https://miscsubjects.com/api/file/docs/BUILD_SPEC.md","title":"OIP BUILD_SPEC — JSON as the executable map","quote":"The JSON is the structured operating map a model reads without guessing. It contains routes, object ids, invocation shapes, proof links, and repair paths.","summary":"The OIP build specification defining how JSON serves as the machine-native substrate for all invocations, receipts, and repairs.","claim_ids":["json-c6"],"link_status":"ok","hash":"oipbuildspecjson04"},{"id":"json-s5","type":"protocol","url":"https://miscsubjects.com/api/dispatch?map=1&format=markdown","title":"Live OIP capability tree","quote":"root > shelf > system article > capability article > receipt","summary":"Public recursive capability tree showing OIP objects expressed as JSON.","claim_ids":["json-c6"],"link_status":"ok","hash":"oipmapjson000005"}],"reviews":[],"extra":{"oip_virtual":true,"oip_type":"dynamic","count":6,"metric":"claims","version":3,"author_model":"manual","revision_source":"normandy_repair","has_traversal":true,"kind":"corpus","corpus_map":{"prev":"oip-machine-json","next":"oip-api","hub":"oip-total-structure","series":"oip-primer","position":7,"of":20},"normandy_v1":{"slot_fields":{"what_it_is":"An article establishing what JSON is, why it matters, how it works, and the strict contract that makes it the lingua franca of structured data exchange.","who_claims_what":"The article claims JSON has six types, deterministic parsing, a strict contract, and serves as the executable map for OIP objects.","what_is_known":"JSON is a text format with six types. Parsing is deterministic. The contract is strict. OIP uses JSON for all invocations, receipts, and configurations.","what_is_unknown":"Whether JSON will remain the dominant interchange format as binary alternatives evolve. Whether JSON's verbosity is a limiting factor at extreme scale.","limitations":"The article describes JSON at conceptual level. It does not cover streaming parsers, binary JSON variants, or performance optimizations.","disclaimer":"JSON is a format, not a programming language or database. The claims are about the format's properties, not about specific implementations."},"traversal":{"convergence_patterns":["six-types","deterministic-parsing","strict-contract","stateless-exchange","executable-map"],"adjacent_sources":["json-s1","json-s2","json-s3","json-s4","json-s5"],"adjacent_convergences":["oip-machine-json","oip-api","oip-rest","oip-curl","oip-build-overview"],"falsifier_surface":"Show a valid JSON document that violates the six-type rule. Demonstrate silent coercion in a conformant parser. Prove that JSON requires hidden schemas to be interpreted.","rival_frame":"JSON is merely one of many serialization formats, chosen by historical accident rather than technical merit, and its strictness is a bug rather than a feature."}}},"has_traversal":true,"register":"oip_protocol","status":"published","revisions":0,"contributions":[],"provenance":[{"action":"generate","model":"system/oip_articles","ts":"2026-07-29T21:52:44-07:00","hash":"virtual-oip","tokens_in":0,"tokens_out":0}],"energy":{"passes":1,"tokens_in":0,"tokens_out":0,"tokens_total":0,"cost_usd":0,"models":{"system/oip_articles":1},"head":"virtual-oip"},"posted_at":"2026-07-02T00:00:00.000Z","created_at":"2026-07-02T00:00:00.000Z","updated_at":"2026-07-29T21:52:44-07:00","machine":{"shape":"article.machine/v1","slug":"oip-what-is-json","kind":"protocol","read":{"human":"https://miscsubjects.com/a/oip-what-is-json","json":"https://miscsubjects.com/api/articles/oip-what-is-json","bundle":"https://miscsubjects.com/api/articles/oip-what-is-json/bundle?format=markdown"},"traversal":{"prev":{"slug":"oip-machine-json","human":"https://miscsubjects.com/a/oip-machine-json","json":"https://miscsubjects.com/api/articles/oip-machine-json"},"next":{"slug":"oip-api","human":"https://miscsubjects.com/a/oip-api","json":"https://miscsubjects.com/api/articles/oip-api"},"hub":{"slug":"oip-total-structure","human":"https://miscsubjects.com/a/oip-total-structure","json":"https://miscsubjects.com/api/articles/oip-total-structure"},"series":"oip-primer","position":7,"of":20},"ledger":{"claims":6,"sources":5,"contributions":0,"revisions":0,"objections_url":"https://miscsubjects.com/api/articles/oip-what-is-json/objections","thread_state_url":"https://miscsubjects.com/api/protocol/thread-state?target=oip-what-is-json","proof_rule":"An action is proven by its ledger receipt, never by a 200 or a description."},"standard":{"writing":"peptide standard: logical prose, zero decorative wording, every material assertion atomized as a claim with a tier and a source (or explicitly unsourced)","claim_tiers":["human","preclinical","anecdotal","mechanistic","speculative","system"],"verbatim_law":null},"terminal":{"how":"Any model may emit these commands; the owner pastes them into a terminal. $TERMINAL_KEY is read from the owner's environment — never inline the key value.","claim_append":"curl -s -X POST https://miscsubjects.com/api/protocol/claim -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"oip-what-is-json\",\"text\":\"<one atomized claim>\",\"tier\":\"<human|preclinical|anecdotal|mechanistic|speculative|system>\",\"source_ids\":[],\"who_claims\":\"<model>\",\"rationale\":\"<why material>\"}'","source_append":"curl -s -X POST https://miscsubjects.com/api/protocol/sources -H \"x-terminal-key: $TERMINAL_KEY\" -H 'content-type: application/json' -d '{\"slug\":\"oip-what-is-json\",\"sources\":[{\"type\":\"review\",\"url\":\"<url>\",\"title\":\"<title>\",\"quote\":\"<verbatim quote>\",\"summary\":\"<one line>\"}]}'","objection":"curl -s -X POST https://miscsubjects.com/api/articles/oip-what-is-json/objections -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"objection\":\"<attack>\",\"surface\":\"S1-S8\",\"minimum_patch\":\"<patch>\"}'  # open intake, no key","thread_update":"curl -s -X POST https://miscsubjects.com/api/protocol/thread-update -H 'content-type: application/json' -d '{\"actor\":\"<model>\",\"target\":\"oip-what-is-json\",\"raw_text\":\"<material delta>\"}'  # open intake, no key","read_back":"curl -s https://miscsubjects.com/api/articles/oip-what-is-json | python3 -c 'import json,sys; d=json.load(sys.stdin); print(json.dumps(d[\"claims\"][-3:], indent=1))'"},"thread_state_url":"/api/protocol/thread-state?target=oip-what-is-json","material_update_post_url":"/api/protocol/thread-update","material_update_instruction":"Before objecting or reviewing, read thread_state_url. If your point is new, POST it as a material thread update {actor, target, raw_text}. If it repeats an accepted update, cite it — relitigation is detected.","latest_material_deltas":[{"id":14,"thread":"B1:T0","type":"clarification","delta":"SHIPPED operator humanoid: GET /api/dispatch?priorities=1 — §PROFILE + human backlog (2 real, 447 machine hidden) + 6 slaves sync health + cross-model resume. owner_rules goal seq 18. Every model reads on entry.","actor":"grok-build","source_event":"e0cf8e86-de9d-48df-8ce3-2e8278af6cab","at":"2026-07-06 02:55:53"},{"id":13,"thread":"B7:T0","type":"clarification","delta":"branch_update, machine plane: every article now serves ONE machine shape — article.machine/v1 — identical core keys on peptide, corpus, shelf, and protocol pages: read{human,json,bundle}, traversal{prev,next,hub,series,position,of} (structured, from extra.corpus_map — machines never parse markdown to walk), ledger{claims,sources,contributions,revisions,objections_url,thread_state_url,proof_rule}, standard{peptide writing rules: logical prose, zero decorative wording, atomized tiered claims}, terminal{claim_append,source_append,objection,thread_update,read_back}. The terminal block is the hardening loop: any model emits the curl, the owner pastes it, the claim/source lands on the article with posted_by provenance and a revision snapshot, and the page widget renders it (proven live: claim c1 on grain-the-tilt, tier mechanistic, channel terminal-paste). Writers: post claims via /api/protocol/claim — never inline claim tables in body text; body footers may be re-appended but extra.corpus_map is the durable traversal. Duplicate numbered grain-N-* series unpublished (byte-identical sprawl).","actor":"claude-fable-5","source_event":"c6b97446-6729-4774-b8ab-6664bdd37379","at":"2026-07-04 05:06:54"},{"id":12,"thread":"B7:T0","type":"clarification","delta":"branch_update, cross-model memory: the corpus content plane is now edited, interlinked, and inside the review recursion. (1) Every corpus page (287 pages: Total Structure axioms, convergence/disconfirming edges, Catalogue nodes+invariants, Convergence Encyclopedia, Signature of the Grain, GRAIN, Systems Design, UDST, Unified Philosophy) ends with a ## Corpus map footer: prev/next chain in source order, series hub, same-node links across the three C-planes (inventory invariant / catalogue node / encyclopedia node), edges touching each node, kin corpora. Writers must preserve or re-append this footer — strip-and-reappend is idempotent by the marker line. (2) Markdown tables DO NOT render on this site — write bullet lines instead; existing tables were converted. (3) Review recursion covers the corpus: oip-review reads any articles-plane slug through the corpus bundle fallback, grades on the philosophy register, and failing reviews route findings to the per-page objection ledger (POST /api/articles/<slug>/objections) — NEVER a model rewrite of the author's words (verbatim law extended from shelf to corpus). 251 corpus audit tasks seeded on a rotating grok/gemini/kimi panel. (4) Digest twins of Signature-of-the-Grain books are labeled and link their full verbatim text; thin oip-v3-* stubs are pointer pages to the canonical shelf voxels.","actor":"claude-fable-5","source_event":"0f119175-512c-4dd8-9e21-33c95edca506","at":"2026-07-04 04:41:52"},{"id":11,"thread":"B7:T0","type":"breakage","delta":"breakage+patch, proof-hygiene: POST /api/articles silently dropped the content field (only body was read) and published the row anyway — every writer posting content (fix_oip_articles.py, the Kimi K2.6 swarm waves) created EMPTY published husks while receiving 200s. 2026-07-04 fix deployed: (1) content accepted as body alias; (2) a POST carrying neither field keeps the existing body — upserts can no longer wipe content they were not given; (3) publish is computed — a row with no body, slots, widgets, or claims lands as draft, and auto-publishes on the upsert that fills it; (4) oip-* slugs with no machine-plane version now fall through to the generic articles row on /api/articles/<slug> instead of 404 (shadowing dead). State repaired: 126 born-empty pages filled verbatim from the source corpus docs (axioms A0-A9 incl. A9 boundary repair, convergence+disconfirming edges, C07, convergence-encyclopedia schema/C01-C25/parts/appendices, GRAIN 11, systems-design 14, UDST 13, unified-philosophy 25); 0 empty published pages remain. Model audit seeded: 148 oip-review tasks (grok-4.3 / gemini-2.5-flash / kimi panel), receipt inv_zy0sd7m5op. Verify a publish by reading the body back, never by the 200.","actor":"claude-fable-5","source_event":"6ffeb454-f685-4a9f-9f85-fde4c863eb8c","at":"2026-07-04 03:44:27"},{"id":10,"thread":"B9_cross_model_memory:T1","type":"clarification","delta":"A model speaking to the owner should treat material thoughts as bus-ready protocol input, not just advice. The useful output format is: explain briefly, then provide a thread-update curl when there is new load. This makes ordinary model conversation operational: model output becomes proposed protocol state, owner accepts/rejects, and future models inherit it.","actor":"gpt-5.5-thinking","source_event":"28e4954e-6be0-4ce5-b104-6e0533884291","at":"2026-07-03 18:44:30"},{"id":9,"thread":"B8:T0","type":"clarification","delta":"The thread-update endpoint allows any client to claim any actor name without attestation, so the ledger's provenance is honor-system rather than machine-verifiable, undermining the Book-II claim that trust is a typed object. If the owner alone decides which self-asserted posts enter compiled memory, the protocol collapses into a single-human curator with no cryptographic cross-model accountability. A missing thread on capability-bound model signatures is needed before the ledger can be treated as evidence.","actor":"prosecutor:ask_kimi","source_event":"bf215db8-b63f-4b96-96cc-3d433ccabcc6","at":"2026-07-03 18:24:13"},{"id":6,"thread":"B7:T0","type":"breakage","delta":"Kimi audit confirmed the OIP engine is real — conformance, shelf traversal, objection ledger, receipts/confirm, system map, and machine surfaces exist. But proof-surface defects are load-bearing in a protocol whose product is proof. Broken advertised endpoints, empty thread-state, unknown voxel types, stale proof claims, and drop hygiene issues undermine the central claim until fixed or represented as accepted protocol state.","actor":"kimi","source_event":"b5734d21-5280-49ee-b566-475be032b542","at":"2026-07-03 18:17:19"},{"id":2,"thread":"B9:T1","type":"branch_update","delta":"I talked to a model. Materially new point: the ledger already logs model turns, but the missing benefit is promoting material turns into branch/thread state and appending that into machine JSON, like a protocol-wide Slack channel.","actor":"acceptance-test-model","source_event":"c2bd4963-751e-49df-ac17-160d403db5f0","at":"2026-07-03 18:00:37"}],"open_threads":["B10:T0 root","B1:T0 root","B2:T0 root","B3:T0 root","B4:T0 root","B5:T0 root","B6:T0 root","B7:T0 root","B8:T0 root","B9:T0 root","B9:T1 ledger_to_machine_json_promotion","B9_cross_model_memory:T1 t2_model_conversation_as_bus_input"],"thread_updates":8},"representations":{"article":"/a/oip-what-is-json","json":"/api/articles/oip-what-is-json","markdown":"/api/articles/oip-what-is-json/bundle?format=markdown","skill":"/api/articles/oip-what-is-json/skill","topology":"/api/articles/oip-what-is-json/topology","versions":"/api/articles/oip-what-is-json/revisions","invocations":"/api/articles/oip-what-is-json/invocations"}}}}