{"_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":"udst-v1-1-the-floor-and-the-ceiling","urls":{"read":"https://miscsubjects.com/api/articles/udst-v1-1-the-floor-and-the-ceiling/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/udst-v1-1-the-floor-and-the-ceiling/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/udst-v1-1-the-floor-and-the-ceiling/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/udst-v1-1-the-floor-and-the-ceiling/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/udst-v1-1-the-floor-and-the-ceiling/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/udst-v1-1-the-floor-and-the-ceiling/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/udst-v1-1-the-floor-and-the-ceiling/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":"udst-v1-1-the-floor-and-the-ceiling","title":"UDST: V1 1 The Floor And The Ceiling","register":"oip_protocol","tags":["OIP","UDST","systems-theory","deterministic"],"updated_at":"2026-07-17T02:37:53.057Z","body_excerpt":"# The Floor and the Ceiling\n\nThe protocol has two effects, and most discussions confuse them.\n\n**The floor is remedy.** Where actors are trapped by lack of access to auditable logic, procedure, statute, contract, evidence, or remedy, lowering the cost of proof lowers the cost of agency. A tenant who cannot afford a lawyer and cannot decode the lease is trapped by logic-cost. A worker who cannot prove the harm done to them is trapped by evidence-cost. A small business that cannot afford compliance review is trapped by procedure-cost. As proof becomes cheaper — through deterministic scaffolds, reused artifacts, and routed local models — the floor rises. The framework's anti-subjugation function lives here.\n\nIn the build, the floor is the public capability console. Any actor can open `https://miscsubjects.com/a/oip` and read the full protocol without authentication. They can see the 731 capabilities, the conformance suite, the receipt format, and the exact curl for every operation. They do not need a terminal key, a GitHub account, or a Cloudflare seat. The proof is public. The floor rises because the cost of access to the system's logic is zero.\n\nThe floor is also the scoped token. A non-technical actor can receive a `row:NOW` token that fires exactly one capability, with one use, and expires in ten minutes. They do not need to understand the full system. They need one URL. The token is the remedy: it gives them agency over a specific capability without exposing them to the complexity of the full system. The floor is not the act token (which grants full agency); the floor is the scoped token, which grants bounded agency to the actor who needs it.\n\n**The ceiling is ascent.** The same protocol, applied to capable actors and well-functioning systems, optimizes decision quality, business ratios, communication, learning, contracts, governance, and execution. The architecture that protects the trapped is the architecture that compounds the capable. A founder who runs decisions through proof artifacts makes fewer compounding errors. A team that ledgers its reasoning learns from its own history. A government that subjects its rules to adversarial verification produces fewer captures.\n\nIn the build, the ceiling is the optimization loop. The governor scans the ledger for recurrence classes and surfaces them as URGENT flags. The owner sees the flag, installs an invariant (a migration, an automation, a rule), and the recurrence class is eliminated. The next scan shows fewer flags. The system compounds its own improvement because every error is ledgered, classified, and addressed. The ceiling is not the initial state of the system; it is the rate at which the system improves itself.\n\nThe ceiling is also the amortization of proof artifacts. A receipt that is replayed once is a sunk cost. A receipt that is replayed a hundred times is a compounding asset. The build's `?receipt=INV_ID` endpoint makes every past invocation a reusable proof. The team that replays its own receipts learns from its own history without regenerating the proof. The ceiling rises as the reuse rate rises.\n\nThese are not two protocols. They are one protocol applied to two positions on the gradient. Subjugation and inefficiency are different expressions of the same deviation from full-scope optimality: a system burning energy to hold itself below what it could produce. The friction that traps the powerless is the friction that drags the powerful. The same invariant unwinds both.\n\nIn the build, this is the same endpoint: `POST /api/dispatch`. A non-technical actor uses it with a scoped token to fire one capability (the floor). A technical actor uses it with an act token to fire any capability, compose multiple capabilities, and optimize the system (the ceiling). The endpoint is the same; the gradient is the token scope. The floor and the ceiling are not separate systems; they are the same protocol with different permissions.\n\nThis is why agency infrastructure is more fundame","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"In the build, the floor is the public capability console. Any actor can open `https://miscsubjects.com/a/oip` and read the full protocol without authentication. They can see the 731 capabilities, the conformance suite, the receipt format, and the exact curl for every operation. They do not need a terminal key, a GitHub account, or a Cloudflare seat. The proof is public. The floor rises because the","tier":"system","weight":0.8,"interaction_risk":false,"status":"active","source_ids":["s1"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.8,"quote_gated":false},{"id":"c2","text":"The ceiling is also the amortization of proof artifacts. A receipt that is replayed once is a sunk cost. A receipt that is replayed a hundred times is a compounding asset. The build's `?receipt=INV_ID` endpoint makes every past invocation a reusable proof. The team that replays its own receipts learns from its own history without regenerating the proof. The ceiling rises as the reuse rate rises.","tier":"system","weight":0.8,"interaction_risk":false,"status":"active","source_ids":["s1"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.8,"quote_gated":false},{"id":"c3","text":"These are not two protocols. They are one protocol applied to two positions on the gradient. Subjugation and inefficiency are different expressions of the same deviation from full-scope optimality: a system burning energy to hold itself below what it could produce. The friction that traps the powerless is the friction that drags the powerful. The same invariant unwinds both.","tier":"system","weight":0.8,"interaction_risk":false,"status":"active","source_ids":["s1"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.8,"quote_gated":false},{"id":"c4","text":"In the build, this is the same endpoint: `POST /api/dispatch`. A non-technical actor uses it with a scoped token to fire one capability (the floor). A technical actor uses it with an act token to fire any capability, compose multiple capabilities, and optimize the system (the ceiling). The endpoint is the same; the gradient is the token scope. The floor and the ceiling are not separate systems; th","tier":"system","weight":0.8,"interaction_risk":false,"status":"active","source_ids":["s1"],"retracted_at":null,"retraction_reason":null,"challenged_by":[],"effective_weight":0.8,"quote_gated":false}],"sources":[{"id":"s1","type":"adjacent","url":"https://miscsubjects.com/a/udst-v1-1-the-floor-and-the-ceiling","title":"UDST: V1 1 The Floor And The Ceiling","quote":"In the build, the floor is the public capability console. Any actor can open `https://miscsubjects.com/a/oip` and read the full protocol without authentication. They can see the 731 capabilities, the ","summary":"Primary source for UDST: V1 1 The Floor And The Ceiling.","claim_ids":["c1","c2","c3","c4"]}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"udst-v1-1-the-floor-and-the-ceiling","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":1,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}