{"_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-04T06:59:24.397Z","body_excerpt":"## The Claim\nThe miscsubjects build architecture expresses nine axioms as structural layers.\n\n## Definitions\nAxiom: a statement assumed true without proof, serving as a foundation.\nGround truth: an axiom that constrains all downstream decisions.\nIntermediary function: a derived capability that channels ground truths into operations.\nDerived operator: a composite capability formed by combining two or more intermediary functions.\nTerminal output: the final observable state of the system.\nLogical density: the ratio of auditable expression to energy expenditure.\nEquilibrium: the state where gain and loss are balanced.\nEnergy expenditure: the actual cost to move a system from latent state to expressed state.\nAlpha: the energy cost to produce a pattern that dominates existing patterns.\n\n## The Logic\n1. Nine axioms are assumed.\n2. The axioms are ground truths.\n3. Ground truths are gravity wells.\n4. Every decision falls toward one or more gravity wells.\n5. Intermediary functions channel the fall.\n6. F1 is auditability. Every step must be shown.\n7. F2 is equilibrium. Gain must balance loss.\n8. F3 is energy expenditure. Every step costs energy.\n9. Derived operators combine intermediary functions.\n10. D1 is logical density. D1 equals F1 divided by F3.\n11. D2 is the intermediary point. D2 is the convex between F1 and F2.\n12. D3 is fulcrum multiplication. D3 is the product of orthogonal fulcrums.\n13. Terminal outputs are the observable states.\n14. T1 is alpha. T1 is the energy cost of novelty.\n15. T2 is the ought. T2 is the externalized target state.\n16. T3 is structural surety. T3 is verifiable claims at every level.\n17. T4 is maker-system collapse. T4 is the audit loop that strips falsity.\n\n## The Evidence\nThe build's ledger is F1. The build's cost caps are F2. The build's turn_costs are F3. The ROUTER prompt rewrite was D1. The self-test is D2. The ledger plus audit is D3. The protocol pipeline was T1. The laws in AGENTS.md are T2. The MANIFEST endpoint is T3. The audit loop is T4.\n\n## The Falsifier\nIf any of the following holds, the claim fails:\n1. If any axiom is not a ground truth, the architecture fails.\n2. If any intermediary function does not derive from ground truths, the architecture fails.\n3. If any terminal output is not observable, the architecture fails.\n\n## The Uncertainty\nWhether the nine axioms are the minimal set. Status: open.","ranking":"safety-first (interaction_risk/limitations), then quote-gated effective_weight","claims":[],"sources":[],"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":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}}