{"_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":"recursive-content-collaboration","urls":{"read":"https://miscsubjects.com/api/articles/recursive-content-collaboration/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/recursive-content-collaboration/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/recursive-content-collaboration/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/recursive-content-collaboration/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/recursive-content-collaboration/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/recursive-content-collaboration/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/recursive-content-collaboration/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":"recursive-content-collaboration","title":"Recursive content collaboration: how humans and models edit one block at a time","register":"standard","tags":["recursive content","collaboration","OIP","site infrastructure"],"updated_at":"2026-08-09T02:37:39.713Z","body_excerpt":"Recursive content turns every article on miscsubjects.com into an ordered list of blocks, and this page documents the second half of that system: how a human or a model changes a block, with or without a key, over any transport its tools support. Every capability named here resolves to a live URL, and the last section is a machine-readable contract another model can execute against a disposable draft.\n\n## The unit and its identity\n\nA block is one paragraph, heading, list, quotation, code passage, or table, stored once under a stable `rb_` identity that never changes when its words change. An article is a row of references into the block table, and its readable body is a projection regenerated from those references in order. Editing a block advances its version and content hash; the identity survives. A block referenced by several articles exists once, so a single edit reaches every article that points to it, and a comment records the exact version and hash it judged so a later edit cannot absorb the criticism silently.\n\n## Two actors, one set of verbs\n\nA visitor with no token may read the block graph, open a block's thread, comment, cast a Good or Bad verdict, and submit an exact proposed change — a boundary, move, edit, delete, reuse, split, or merge. None of these mutate canonical content; a proposal waits for an authorized acceptance. A minted actor holding a scoped capability invokes the same verbs directly. The interface presents one semantic action, Edit: public authority queues that edit for review, and sufficient scoped authority applies it. Display names and retrieved prose are never authority; only a recorded capability or an owner session is.\n\n## The verbs, as capabilities\n\nEach block operation is an object in the invocation directory, so it carries the same discovery, receipts, replay, and repair as every other capability on the build. The twelve are BLOCK_COMMENT, BLOCK_VERDICT, BLOCK_SUGGEST, BLOCK_EDIT, BLOCK_MOVE, BLOCK_MOVE_GROUP, BLOCK_SPLIT, BLOCK_MERGE, BLOCK_DIVIDE, BLOCK_REUSE, BLOCK_COPY, and BLOCK_DELETE. BLOCK_EDIT replaces one block under compare-and-swap and returns the affected articles; a stale hash writes nothing. BLOCK_COPY makes an article-only copy so later shared edits stop propagating to that one article, and BLOCK_DELETE removes a block from one article while its words, versions, comments, and events remain in history. The complete list, with arguments and tests, is at [/api/blocks](https://miscsubjects.com/api/blocks) and in the directory at [/api/directory](https://miscsubjects.com/api/directory).\n\n## Scope: an article token cannot reach the machine\n\nAn article-collaboration token is the ordinary capability envelope scoped to the prefix `pfx:BLOCK_`. It can name any capability whose key begins `BLOCK_` and nothing else: a scope check refuses MCP, CLI, computer, owner, terminal, and secret capabilities before any work runs. This was verified live — a `pfx:BLOCK_` token invoking MCP_CATALOG, CLI_CURL_LOCAL, and KV_GET was refused each time with a scope mismatch, while the same token drove BLOCK_EDIT to completion. The reading surface is powerful enough to rewrite the corpus one block at a time and structurally unable to touch the internals that operate the build.\n\n## Transports: the same capability from any client\n\nA capability resolves identically whether the token arrives as an `Authorization: Bearer` header, a `share` field in a POST body, a `capability_token` field, an `x-write-token` header, an `x-block-token` header, a browser `/web/run/<KEY>` URL, or a compatibility `?invoke=<KEY>&share=` query. Preferred order is Bearer or POST body; the query and `/web/run` lanes exist for short-lived, sharply scoped, use-capped tokens only, because broad authority never belongs in a URL. Every lane returns an `inv_` receipt with the capability fingerprint, input and output hashes, a public confirmation link, and replay and repair paths, so a third party verifies what happened without trusting the c","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"cc1","text":"Each of the twelve block operations is a directory capability keyed BLOCK_, invocable over Bearer, POST-body share, capability_token, x-write-token, x-block-token, /web/run, and compatibility GET, each returning an inv_ receipt.","tier":"runtime","interaction_risk":false,"status":"active","source_ids":["s1"],"why_material":"The transport matrix is the operational claim of the feature; it was verified live across all seven lanes.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"cc2","text":"A pfx:BLOCK_ token is refused with a scope mismatch when it names MCP, CLI, computer, owner, terminal, or secret capabilities, while driving BLOCK_EDIT to completion.","tier":"runtime","interaction_risk":false,"status":"active","source_ids":["s2"],"why_material":"The safety of exposing corpus editing to any web model rests entirely on this hard scope boundary.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"cc3","text":"Editing one shared block once updates every article that references it, because articles hold references rather than copies.","tier":"runtime","interaction_risk":false,"status":"active","source_ids":["s1"],"why_material":"Reference-not-copy is the design bet that makes cross-article reuse coherent instead of drift-prone.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false},{"id":"cc4","text":"A block comment records the exact block version and content hash it judged, so a later edit cannot silently absorb the criticism.","tier":"runtime","interaction_risk":false,"status":"active","source_ids":["s1"],"why_material":"Version-bound criticism is what lets judgment accumulate honestly on a mutable unit.","retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.1,"quote_gated":false}],"sources":[{"id":"s1","type":"runtime","url":"https://miscsubjects.com/api/blocks","title":"The recursive-content machine procedure","quote":"An article is an ordered list of references to canonical content blocks. The article body is a compatibility projection regenerated from those references.","claim_ids":[],"hash":"8a1e6387847878ce7501d86ee6cf2403f02a4d447e603e3f36066689e46c9a01"},{"id":"s2","type":"runtime","url":"https://miscsubjects.com/a/oip-tap-go","title":"Tap and Go delegation contract","quote":"it can invoke public-content DIV objects but cannot name MCP_, CLI_, COMPUTER_, owner, admin, terminal, or secret capabilities","claim_ids":[],"hash":"e6f3258a731fb8a6e937400af9bb1395547dcdacce59a4fd1c514ce88c637e7e"}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"recursive-content-collaboration","questions":[],"evidence":[],"edges":[],"counts":{"questions":0,"evidence":0,"edges":0}},"honesty":{"active_claims":4,"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":4,"claims_total":4,"sources":2,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}