{"_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":"systems-design-the-architecture","urls":{"read":"https://miscsubjects.com/api/articles/systems-design-the-architecture/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/systems-design-the-architecture/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/systems-design-the-architecture/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/systems-design-the-architecture/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/systems-design-the-architecture/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/systems-design-the-architecture/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/systems-design-the-architecture/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":"systems-design-the-architecture","title":"Systems Design: The Architecture","register":"oip_protocol","tags":["OIP","systems-design","philosophy"],"updated_at":"2026-07-17T02:37:50.061Z","body_excerpt":"# The Architecture\n\nThe architecture is the expression of the nine axioms on the build itself. It is not a metaphor. It is the actual structure of the system, described in the language of the axioms.\n\n## Layer 0 — Ground Truths\n\nAll paths root to a₄ (injustice as the base unit of wrong). Without it, nothing downstream holds. This is not a design choice. It is a physical constraint. A system that does not know what it is against cannot know what it is for. The build is against opacity. It is against the capable actor withholding remedy from the trapped actor. The ledger is the expression of this. Every event is recorded. Every cost is visible. Every tool call is named. This is not a feature. It is the floor.\n\nThe other axioms provide the remaining ground truths. a₁ (polarity) requires the adversarial test. a₂ (the grain) requires the REST architecture and exact-name lookup. a₃ (convergence) requires that all values be recognized as one constraint. a₅ (inherited prejudice) requires continuous audit and removal of assumptions that were never questioned. a₆ (void state) requires periodic stripping of the system to its topology. a₇ (convergence) requires recognition of when different systems arrive at the same structure. a₈ (interoperability) requires that the system be a full externalization of the designer's ought. a₉ (interlock) requires that the pursuit of any value absolutely causes all values to converge.\n\nThese are not layers in a stack. They are gravity wells. Every decision in the system falls toward one or more of these truths. The architecture describes how the system channels that fall.\n\n## Layer 1 — Intermediary Functions\n\n### F₁: Auditability\nEvery logical step in the chain of events must be shown. This is not documentation. It is energy accounting. Each step, when expressed by a biological or mechanical thing, requires energy. The efficient use of energy is to determine what amount of auditable logical expression fits under a unit.\n\nDo you express the step at all? Do you express it multiple times? Do you express it and test it against its negation to prove it? Do you put it on a ledger to verify it? All of this balances against the energy requirement for its expression.\n\nIn the build, the ledger is the auditability function. Every turn costs tokens. Every tool call costs time. Every file edit costs context. The ledger records all three. The owner can see what was spent, what was produced, and whether the production was worth the spend. This is not a cost report. It is an auditability report. It answers the question: did the system do what it said it would do, and can you show your work?\n\n### F₂: Equilibrium\nThe ability for ratios to be held. The required energy, ratio, speed, and volume at which something ought to express itself to retain the optimal level of gain while experiencing the nominal level of risk.\n\nFrom a systems perspective: the gain-to-loss balance. How much of the structure to hedge and not expose. How to handle exposure when an idea is suboptimal or negotiable.\n\nIn the build, equilibrium is the cost cap. The `COST_CAP_USD` limits how much the system can spend per turn. The `DEPTH_CAP` limits how many iterations the system can run. The `ITER_CAP` limits how many tool calls the system can make. These are not safety rails. They are equilibrium expressions. They say: the system must produce value within a bounded energy envelope, or it must stop. A system that cannot produce value within its energy envelope is not in equilibrium. It is in runaway.\n\n### F₃: Energy Expenditure\nThe thermodynamic constraint. The actual electrical or heat requirement to move something from latent state to expressed state. Not metaphorical. Physical. Measurable in watts for hardware, in tokens and dollars for software, in attention and time for human operators.\n\nIn the build, energy expenditure is measured in `turn_costs`. Every model call has a token cost. Every API call has a latency cost. Every deploy has a compute cost. The","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[{"id":"c1","text":"The architecture is the expression of the nine axioms on the build itself. It is not a metaphor. It is the actual structure of the system, described in the language of the axioms.","tier":"runtime","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":"All paths root to a₄ (injustice as the base unit of wrong). Without it, nothing downstream holds. This is not a design choice. It is a physical constraint. A system that does not know what it is against cannot know what it is for. The build is against opacity. It is against the capable actor withholding remedy from the trapped actor. The ledger is the expression of this. Every event is recorded. E","tier":"runtime","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 layers in a stack. They are gravity wells. Every decision in the system falls toward one or more of these truths. The architecture describes how the system channels that fall.","tier":"runtime","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":"### F₁: Auditability\nEvery logical step in the chain of events must be shown. This is not documentation. It is energy accounting. Each step, when expressed by a biological or mechanical thing, requires energy. The efficient use of energy is to determine what amount of auditable logical expression fits under a unit.","tier":"runtime","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/systems-design-the-architecture","title":"Systems Design: The Architecture","quote":"The architecture is the expression of the nine axioms on the build itself. It is not a metaphor. It is the actual structure of the system, described in the language of the axioms.","summary":"Primary source for Systems Design: The Architecture.","claim_ids":["c1","c2","c3","c4"]}],"anecdotal_sources":[],"scientific_sources":[],"user_reports":[],"related_articles":[],"question_graph":{"slug":"systems-design-the-architecture","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}}