{"_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-04T07:21:21.466Z","body_excerpt":"# The Floor and the Ceiling\n\n## The Claim\nOne protocol produces two effects: a floor and a ceiling.\n\n## Definitions\nFloor = the minimum remedy a protocol provides.\nCeiling = the maximum optimization a protocol enables.\nProtocol = a set of deterministic rules that route capability.\nScoped token = a credential that grants one capability, one use, timed expiry.\nRecurrence class = a repeating pattern of ledger events with a common systemic cause.\nAmortization = the reduction of average cost through reuse.\n\n## The Logic\n1. If proof becomes cheaper, then trapped actors gain agency.\n2. If trapped actors gain agency, then the floor rises.\n3. If capable actors use proof artifacts, then they make fewer compounding errors.\n4. If capable actors make fewer compounding errors, then the ceiling rises.\n5. Therefore, one protocol produces both floor and ceiling.\n\n## The Evidence\nThe public console displays all capabilities without authentication. The cost of access is zero. A scoped token grants one capability to a non-technical actor. The governor scans the ledger for recurrence classes. Each class is flagged as urgent. The owner installs an invariant. The next scan shows fewer flags. The reuse rate rises as receipts are replayed. The endpoint is the same. The token scope changes.\n\n## The Falsifier\nShow that cheap proof does not raise trapped actors' agency. Show that proof artifacts do not reduce compounding errors for capable actors. Show that floor and ceiling require separate protocols.\n\n## The Uncertainty\nCash transfer may beat agency infrastructure where material scarcity is the trap. The protocol may not scale to all actors.","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[],"sources":[],"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":0,"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":0,"claims_total":0,"sources":0,"anecdotal":0,"scientific":0,"user_reports":0,"questions":0,"evidence_ingests":0}}