{"_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-llm-as-os","urls":{"read":"https://miscsubjects.com/api/articles/udst-v1-1-llm-as-os/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-llm-as-os/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-llm-as-os/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-llm-as-os/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-llm-as-os/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-llm-as-os/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-llm-as-os/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-llm-as-os","title":"UDST: V1 1 Llm As Os","register":"oip_protocol","tags":["OIP","UDST","systems-theory","deterministic"],"updated_at":"2026-07-17T02:37:52.020Z","body_excerpt":"# LLM-as-OS\n\nStochastic models do not become deterministic. The determinism lives one layer up.\n\nIn an LLM-as-OS architecture, stochastic model weights become dynamic reasoning plumbing — useful where probabilistic generation is genuinely needed, replaceable where it is not. A deterministic command plane sits above the weights and decides, per task: which model or models (local, open-weight, frontier closed); which scaffold depth and structure; which context package and which sources; which tools; which red-team depth and adversarial budget; which privacy mode and data-custody policy; which ledgering standard; which human-escalation threshold; which cost ceiling and surety target.\n\nThe command plane's objective is to maximize task-adjusted logical density under the constraints the task imposes: stakes, deadline, privacy, budget, and required surety.\n\nIn the build, the command plane is the dispatch router. `POST /api/dispatch {key:KEY, body:BODY}` does not invoke a model directly. It invokes a capability row, which is a deterministic contract. The router decides: which capability matches the key? Which model should execute the capability? What scaffold depth is required? What context package should be admitted? The decision is logged, typed, and replayable. The router is not a model; it is a deterministic lookup table with scoped gates.\n\nThis is glass box over black box. The weights stay opaque inside; every routing decision, context slice, tool call, claim, evidence reference, attack, repair, and unresolved node is visible on the surface and replayable from the ledger.\n\nIn the build, glass box is the receipt. Every invocation returns a receipt with `request_json`, `response_json`, `proof`, and `story`. The receipt is not a black-box summary; it is the full transparent record. The model weights are opaque (the model is a black box), but the routing decision is glass (the receipt shows exactly which model was elected, which context was admitted, which tools were called, and what the output was). The glass box is the receipt; the black box is the model.\n\nThree constraints make this architecture honest.\n\n**The glass box must itself be glass.** A command plane that records what the models did but hides what the command plane decided is not glass. It is a one-way mirror with the model on display and the operator behind it. Every routing decision, every context admission, every tool output, every reuse event, and every red-team decision must be typed, scoped, provenance-bound, permissioned, logged, adversarially challengeable, expiry-limited, and revocable. In the build, this is the `?receipt=INV_ID` endpoint: it returns the full invocation record, including the token provenance (`authorized_by`), the capability scope, the model elected, and the exact request and response. The meta-decisions are auditable because the receipt is the audit.\n\n**The admission invariant is strict.** All context, tools, model outputs, router decisions, proof artifacts, and reuse events are untrusted until admitted. Admission requires a declared type, a declared scope, a verified provenance, a permission check, an adversarial check, an expiry, and entry into the replayable proof graph. Anything that enters the proof without admission is contamination. The default state of an input is hostile; verification is what makes it usable. In the build, this is the capability gate: `capGateCheck` enforces that every invocation has a valid token with the correct scope, expiry, and permission. A `row:NOW` token cannot invoke `LOCAL_EXEC` because the scope check fails. The token is not trusted until admitted; the admission is the scope verification.\n\n**Structural isolation is required where stakes warrant.** The instance that reads raw context should not be the same instance that architects the proof graph for high-stakes decisions. Raw ingestion, proof construction, verification, red-team, repair, and ledgering should be separated where risk requires. The reason is fai","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"Stochastic models do not become deterministic. The determinism lives one layer up.","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 command plane's objective is to maximize task-adjusted logical density under the constraints the task imposes: stakes, deadline, privacy, budget, and required surety.","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":"In the build, the command plane is the dispatch router. `POST /api/dispatch {key:KEY, body:BODY}` does not invoke a model directly. It invokes a capability row, which is a deterministic contract. The router decides: which capability matches the key? Which model should execute the capability? What scaffold depth is required? What context package should be admitted? The decision is logged, typed, an","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":"This is glass box over black box. The weights stay opaque inside; every routing decision, context slice, tool call, claim, evidence reference, attack, repair, and unresolved node is visible on the surface and replayable from the ledger.","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-llm-as-os","title":"UDST: V1 1 Llm As Os","quote":"Stochastic models do not become deterministic. The determinism lives one layer up.","summary":"Primary source for UDST: V1 1 Llm As Os.","claim_ids":["c1","c2","c3","c4"]}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"udst-v1-1-llm-as-os","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}}