## §SELF — miscsubjects portable reference **Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next. **This widget:** `article_bundle` — **LLM article bundle** Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. - **article slug:** `eu-ai-act-high-risk-classification` - **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest - **how to use:** Reference block for Grok/GPT/Gemini. Section §SELF explains the system. - **read:** https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/bundle?format=markdown ### Logical proof (verify each step) 1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution 2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/sources 3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol 4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow 5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex 6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map ### Related features (explains other parts of the system) - **topology** — Claims, sources, anecdotes, user reports, related embeds, question graph slice — for ask/ROUTER. · https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/topology - **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/voxels - **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/prompts - **ingest** — Parse pasted evidence → source ledger + claims + evidence_ingest node. - **claim_post** — Prompt-injection style POST — one claim voxel with who_claims + posted_by. · https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/voxels - **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest ### Full index - JSON: https://miscsubjects.com/api/articles/system-map - Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown ### §STRUCTURE This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure ### §INTEGRITY Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you. ### §GAUNTLET Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted. *Not medical advice. Tier-honest. Cite claim/source ids.* --- # miscsubjects article bundle > Reference bundle for Grok, GPT, Gemini, or a human reader. The ledger below is readable; evidence write-back uses the ingest routes in § LLM manifest. ## MASTHEAD - **identity:** `eu-ai-act-high-risk-classification` v5 · content_hash `2075fc3e54cb1e61…` · thread_head genesis - **thesis (c1):** Article 6 creates two high-risk routes: regulated Annex I products requiring third-party conformity assessment and intended uses listed in Annex III. - c2 [derived/active] The same model can fall into different regulatory classifications depending on the AI system’s intended purpose and operational use. - c3 [primary-law/active] Article 6(3) allows a narrow derogation for some Annex III systems only where significant harm and material influence are absent and a listed statutory conditio - c4 [primary-law/active] An Annex III system that profiles natural persons remains high-risk notwithstanding the paragraph 3 derogation. - c5 [primary-law/active] A provider claiming an Annex III system is not high-risk must document that assessment before market placement or service and provide it to authorities on reque - c6 [official-law-update/active] The July 2026 AI Omnibus moved Annex III high-risk obligations to 2 December 2027 and regulated-product high-risk obligations to 2 August 2028. - c7 [method/active] Classification must be rerun when intended purpose, decision influence, profiling, product integration, human review or substantial modification changes. - c8 [primary-law/active] A downstream distributor, importer, deployer or other third party can become the provider when it rebrands, substantially modifies or changes intended purpose i - **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes - **standing objections:** 0 open → https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/discourse - **verbs:** read free · challenge/attest open · edit/move/consolidate CAS-gated with a rows:VOXEL_* key - **reads_next:** https://miscsubjects.com/a/philosophy · https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/discourse · https://miscsubjects.com/api/protocol ## Article - **slug:** `eu-ai-act-high-risk-classification` - **title:** Is this AI system high-risk? The Article 6 decision tree - **url:** https://miscsubjects.com/a/eu-ai-act-high-risk-classification - **register:** essay - **updated:** 2026-08-03T19:53:12.395Z - **tags:** canonical, eu-ai-act, article-6, high-risk-ai, compliance, ongoing ## Body The EU AI Act does not classify a company, a model family or an industry as high-risk. It classifies an **AI system in its intended use**. The same general-purpose model can sit outside the high-risk regime when it drafts internal meeting notes and enter it when integrated into recruitment, credit, education, benefits, migration, policing or judicial decision-making. This page turns Article 6 and Annex III into a decision record a provider, deployer, auditor or regulator can inspect. It reflects the AI Omnibus that entered into force on **27 July 2026**: Annex III high-risk obligations now apply from **2 December 2027**, while the product-safety systems in Article 6(1) apply from **2 August 2028**. Classification work remains necessary before those dates because intended purpose, contracts, technical documentation and system design decide which lane the operator is building toward. > **The decision in four lines** > > 1. Is the AI a safety component of, or itself, a regulated Annex I product that needs third-party conformity assessment? Article 6(1) high-risk. > 2. Is its intended use listed in Annex III? Presumptively Article 6(2) high-risk. > 3. If Annex III applies, does the system qualify for the narrow Article 6(3) derogation because it does not significantly risk health, safety or fundamental rights and does not materially influence a decision? Document that conclusion. > 4. If it profiles natural persons, the Annex III system remains high-risk despite the derogation. [[embed:source:s1]] ## Step 0: freeze the intended purpose before classifying Classification begins with a versioned statement of intended purpose, not a product name. Record: ```text SYSTEM_ID_AND_VERSION: PROVIDER: DEPLOYER: INPUTS: OUTPUTS: USERS: AFFECTED_PERSONS: DECISION_POINT: HUMAN_REVIEW: PRODUCT_INTEGRATION: JURISDICTION_AND_MARKET: ``` “Assistant,” “copilot” and “decision support” are marketing descriptions. They do not answer whether the system materially influences an outcome. The record must say what the output changes. ## Lane A: regulated products under Article 6(1) An AI system is high-risk under Article 6(1) only when **both** conditions hold: 1. the system is intended as a safety component of a product, or is itself a product, covered by Union harmonisation legislation listed in Annex I; and 2. that product or system must undergo a third-party conformity assessment before market placement or service. The lane covers product regimes such as medical devices, machinery, toys, lifts, personal protective equipment, radio equipment, motor vehicles, rail and civil aviation when the two-part test is met. Merely being embedded in hardware does not satisfy it. Merely touching safety does not identify the Annex I legislation or the third-party assessment. | Evidence needed | The question it answers | |---|---| | Exact Annex I legal instrument | Is the product family actually listed? | | Manufacturer’s intended-purpose statement | Is the AI the product or a safety component? | | Applicable conformity route | Is third-party assessment required? | | Architecture and failure analysis | What safety function does AI perform? | | Change-control record | Did a later modification create or alter the safety role? | [[embed:source:s2]] ## Lane B: the eight Annex III areas Article 6(2) treats AI systems in the listed Annex III uses as high-risk, subject to the paragraph 3 derogation. Match the **specific use**, not merely the sector. | Annex III area | In-scope examples named by the Act | Frequent boundary question | |---|---|---| | Biometrics | Remote identification; sensitive-attribute categorisation; emotion recognition | Is it verification only, or identification/categorisation? | | Critical infrastructure | Safety components managing digital infrastructure, traffic, water, gas, heating or electricity | Is the AI a safety component or an administrative tool? | | Education and training | Admission, assignment, learning-outcome evaluation, level assessment, test-behaviour monitoring | Does output change access, progression or evaluation? | | Employment and self-employment | Recruitment ads, application filtering, candidate evaluation, promotion/termination, task allocation, worker monitoring | Does it influence a person’s work opportunity or conditions? | | Essential services and benefits | Public benefits, creditworthiness, life/health insurance pricing, emergency dispatch and triage | Is the use explicitly exempted, such as financial-fraud detection? | | Law enforcement | Victim risk, polygraphs, evidence reliability, offending/reoffending risk and profiling | Is the use lawful, and which exact subparagraph applies? | | Migration, asylum and borders | Risk assessment, application examination, evidence reliability and person detection | Is it document verification or a substantive assessment? | | Justice and democracy | Judicial fact/law assistance, application of law to facts, certain election influence | Is it substantive case work or administrative/logistical support? | Annex III is not an intuition about sensitivity. It is a list of intended uses. A payroll calculator does not become high-risk because employment is sensitive. A résumé-ranking system does not become low-risk because a recruiter clicks the final button. [[embed:source:s3]] ## The Article 6(3) derogation is a documented exception An Annex III system may be treated as not high-risk only when it does not pose a significant risk of harm to health, safety or fundamental rights, including by not materially influencing decision-making, and at least one statutory condition applies: - it performs a narrow procedural task; - it improves the result of a previously completed human activity; - it detects patterns or deviations without replacing or influencing a completed human assessment, with proper human review; or - it performs a preparatory task for an Annex III assessment. The derogation is unavailable where the system profiles natural persons. ### A safe paragraph-3 record has two separate proofs **Proof A: impact.** Explain why the system does not significantly risk health, safety or fundamental rights and does not materially influence the outcome. Identify the affected decision, dependency on the output, human authority, reversibility and observed override behaviour. **Proof B: statutory condition.** Identify one of the four conditions and tie every word to the actual workflow. “Preparatory” is not a label; show that a later assessment remains open, informed and genuinely independent. “Human review” is not the presence of a person; show what that person sees, can change and has time to assess. Article 6(4) requires the provider to document the assessment before placing the system on the market or putting it into service and to supply it to competent authorities on request. The 2026 Omnibus removed the earlier EU-database registration obligation for exempted systems, but it did not turn an undocumented exemption into a defensible one. ## Human review is measured by authority, information and time A useful review test is operational: | Dimension | Failing pattern | Evidence of meaningful review | |---|---|---| | Authority | Reviewer can recommend but cannot stop or reverse | Named power to reject, change, suspend and escalate | | Information | Reviewer sees score and conclusion only | Source inputs, uncertainty, limitations and contrary evidence | | Time | Throughput target makes independent review impossible | Measured review time and staffing fit the case complexity | | Independence | Reviewer is evaluated for agreement with the model | Overrides are expected, protected and audited | | Feedback | Overrides disappear into a ticket queue | Outcome and reason feed monitoring and risk management | This is not an additional statutory definition. It is the evidence needed to make claims such as “proper human review” and “does not materially influence” falsifiable. ## Classification is a lifecycle control Re-run Article 6 whenever any of these changes: - intended purpose or marketed claims; - affected persons or decision point; - integration into a regulated product; - autonomy, ranking, scoring or recommendation weight; - human-review authority or staffing; - data used for profiling; - customer configuration that moves the system into an Annex III use; - a substantial modification by a distributor, importer, deployer or third party. Article 25 can make a downstream actor the provider when it puts its name on a high-risk system, substantially modifies it while it remains high-risk, or changes the intended purpose of a non-high-risk system so it becomes high-risk. The contractual label “customer” does not prevent the legal role from moving. ## The classification memorandum A complete record can fit in one object: ```text 1. SYSTEM AND VERSION 2. INTENDED PURPOSE AND PROHIBITED USES 3. PROVIDER / DEPLOYER / DOWNSTREAM ROLE MAP 4. ARTICLE 6(1) TEST Annex I instrument: ... Safety-component or product basis: ... Third-party assessment basis: ... 5. ARTICLE 6(2) / ANNEX III TEST Area and exact subparagraph: ... Workflow evidence: ... 6. ARTICLE 6(3) TEST, IF CLAIMED Significant-risk and material-influence assessment: ... Statutory condition: ... Profiling exclusion: ... 7. HUMAN-REVIEW EVIDENCE 8. CONTRARY CLASSIFICATION AND WHY REJECTED 9. FACT THAT WOULD CHANGE THE RESULT 10. APPROVER, DATE, SOURCES AND NEXT REVIEW TRIGGER ``` The strongest contrary classification belongs in the record. A memorandum that cannot state what fact would flip its conclusion is advocacy, not classification. ## Dates after the July 2026 AI Omnibus | Obligation family | Current application date | |---|---| | Article 50 transparency obligations | 2 August 2026, with specific transitional treatment for older systems/content | | Annex III high-risk system requirements | 2 December 2027 | | Article 6(1) high-risk systems embedded in regulated products | 2 August 2028 | The Commission says the extensions allow standards, common specifications and guidelines to mature. They change the compliance clock. They do not change whether a system’s architecture, records and contracts are being built for the correct classification lane. [[embed:source:s4]] ## A free classification audit The **Object Invocation Protocol** will run a documented Article 6 classification exercise without charge for a legislator, regulator, public-interest organisation, company or private party that supplies a bounded system description and the evidence above. The result can include: - provider/deployer role allocation; - the Article 6(1) product route; - the exact Annex III match; - a paragraph-3 derogation stress test; - the human-review evidence gap; - the strongest contrary classification; - a compliance schematic and record template; - multiple independent model findings bound to the same facts, with disagreements preserved. Send the system description to **build@miscsubjects.com**. A public URL is enough for an initial gap map; non-public evidence can be reduced to a bounded, redacted record. The result is not legal advice or a determination by a competent authority. ## Continue the EU AI Act series [[embed:deepfakes-under-the-eu-ai-act]] [[embed:three-models-deliberate-one-statutory-question]] The companion pages cover the complete Act, Article 50 machine-readable marking and the model-panel specimen. This classification guide will be updated when the Commission adopts final high-risk guidelines or authorities establish a material interpretation. ## The audit offer is now in the market ### Sent: Emre Kazim, Holistic AI Selected because His November 2025 essay argues that compliance alone is the wrong north star, while Holistic AI's Agent Glass Box brief asks operators to capture decision steps and tool interactions. The full letter and tracked send receipt: [[embed:source:em_es_994bbbb6012f484d98e7]] ### Sent: Meeri Haataja, Saidot Selected because Her AI Pact statement names use-case inventory, quantified model evaluation and tailored AI Act templates as the work that moves governance into operations. The full letter and tracked send receipt: [[embed:source:em_es_089a1a1e2d704ba1a89b]] ### Sent: Petar Tsankov, LatticeFlow AI Selected because His July 2025 essay separates vague GPAI questions from implementable high-risk obligations, and COMPL-AI translates the latter into technical evaluation. The full letter and tracked send receipt: [[embed:source:em_es_ff85cffe12df46e58945]] ## Claims (13) - **c10** [limitation w=?] This decision tree is an operational guide, not legal advice or a regulator's classification; a defensible result requires the actual intended purpose, product context, decision influence, affected persons and modification history. - slot: limitations - sources: s1, s2 - **c1** [primary-law w=?] Article 6 creates two high-risk routes: regulated Annex I products requiring third-party conformity assessment and intended uses listed in Annex III. - slot: what_it_is - sources: s1, s2 - **c2** [derived w=?] The same model can fall into different regulatory classifications depending on the AI system’s intended purpose and operational use. - slot: what_is_known - sources: s1, s3 - **c3** [primary-law w=?] Article 6(3) allows a narrow derogation for some Annex III systems only where significant harm and material influence are absent and a listed statutory condition is met. - slot: what_is_known - sources: s1, s3 - **c4** [primary-law w=?] An Annex III system that profiles natural persons remains high-risk notwithstanding the paragraph 3 derogation. - slot: what_is_known - sources: s1 - **c5** [primary-law w=?] A provider claiming an Annex III system is not high-risk must document that assessment before market placement or service and provide it to authorities on request. - slot: who_claims_what - sources: s1 - **c6** [official-law-update w=?] The July 2026 AI Omnibus moved Annex III high-risk obligations to 2 December 2027 and regulated-product high-risk obligations to 2 August 2028. - slot: what_is_known - sources: s4 - **c7** [method w=?] Classification must be rerun when intended purpose, decision influence, profiling, product integration, human review or substantial modification changes. - slot: what_is_known - sources: s1, s3 - **c8** [primary-law w=?] A downstream distributor, importer, deployer or other third party can become the provider when it rebrands, substantially modifies or changes intended purpose into a high-risk use. - slot: what_is_known - sources: s1 - **c9** [boundary w=?] The Commission's high-risk classification guidelines remain draft and non-binding, while national enforcement and the classification of boundary cases remain fact-specific. - slot: what_is_unknown - sources: s1, s2, s3 - **c11** [event w=?] On 3 August 2026 the build offered Emre Kazim of Holistic AI a free bounded Article 6 classification pressure test tied to a public evidence record. - slot: what_is_known - sources: em_es_994bbbb6012f484d98e7 - **c12** [event w=?] On 3 August 2026 the build offered Meeri Haataja of Saidot a free bounded Article 6 classification pressure test tied to a public evidence record. - slot: what_is_known - sources: em_es_089a1a1e2d704ba1a89b - **c13** [event w=?] On 3 August 2026 the build offered Petar Tsankov of LatticeFlow AI a free bounded Article 6 classification pressure test tied to a public evidence record. - slot: what_is_known - sources: em_es_ff85cffe12df46e58945 ## Voxel graph (13 atoms · 33 edges) - full graph: https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/voxels ## Article constitution - full: https://miscsubjects.com/api/articles/constitution ## Source ledger (7) - chain valid: yes · head: `45e49d2b4052d74b` ### em_es_089a1a1e2d704ba1a89b · email - title: Letter to Meeri Haataja — 2026-08-03 - url: https://miscsubjects.com/letter-saidot-article-6-2026-08-03 - claim_ids: c12 - hash: `336c233060eeb891` ### em_es_994bbbb6012f484d98e7 · email - title: Letter to Emre Kazim — 2026-08-03 - url: https://miscsubjects.com/letter-holistic-ai-article-6-2026-08-03 - claim_ids: c11 - hash: `31eb446c68490d32` ### em_es_ff85cffe12df46e58945 · email - title: Letter to Petar Tsankov — 2026-08-03 - url: https://miscsubjects.com/letter-latticeflow-ai-article-6-2026-08-03 - claim_ids: c13 - hash: `45e49d2b4052d74b` ### s1 · reference - title: Regulation (EU) 2024/1689 — Article 6, Article 25 and Annex III - url: https://eur-lex.europa.eu/eli/reg/2024/1689/oj/eng - summary: Binding classification rules, downstream-provider role changes and the eight Annex III use areas. - claim_ids: c1, c2, c3, c4, c5, c7, c8, c9, c10 - hash: `88f61c663868cba7` ### s2 · reference - title: Draft Commission guidelines on the classification of high-risk AI systems - url: https://digital-strategy.ec.europa.eu/en/library/draft-commission-guidelines-classification-high-risk-ai-systems - summary: Commission interpretation and practical examples for Article 6(1), Article 6(2), Annex I and Annex III; draft and non-binding as of this update. - claim_ids: c1, c2, c9, c10 - hash: `7facc52984cb9f23` ### s3 · reference - title: Guidelines for providers and deployers of AI high-risk systems - url: https://digital-strategy.ec.europa.eu/en/policies/guidelines-ai-high-risk-systems - summary: Current Commission high-risk classification landing page and consultation status. - claim_ids: c2, c3, c7, c9 - hash: `91a0a1d679cf09e7` ### s4 · reference - title: AI Omnibus enters into force - url: https://digital-strategy.ec.europa.eu/en/news/ai-omnibus-enters-force - summary: Official 27 July 2026 update establishing the revised application dates and simplifications. - claim_ids: c6 - hash: `66a2ad22e23e200d` ## Provenance (4 model passes) - chain valid: yes · head: `a4f78be90246fa8b` - write · GPT-5.6 Codex · 2026-08-03T05:33 · hash `8e0cb1419a59` - write · GPT-5.6 Codex · 2026-08-03T05:33 · hash `645c5e9f9cef` - write · GPT-5.6 Codex · 2026-08-03T05:41 · hash `ede8fc4407b9` - edit · unknown · 2026-08-03T19:53 · hash `a4f78be90246` ## Question graph - questions: 0 · evidence ingests: 0 ## LLM manifest — how to communicate with this ledger - system map: https://miscsubjects.com/api/articles/system-map?format=markdown - topology (ranked): https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/topology - ingest: POST https://miscsubjects.com/api/protocol/ingest - claim: POST https://miscsubjects.com/api/protocol/claim ### Quick actions for this article - **Read live:** https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/topology - **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"eu-ai-act-high-risk-classification","question":"..."}` - **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest eu-ai-act-high-risk-classification|your evidence` - **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim eu-ai-act-high-risk-classification|tier|assertion` - **iMessage ask:** `eu-ai-act-high-risk-classification|your question` - **System map:** https://miscsubjects.com/api/articles/system-map?format=markdown --- ## §SELF — miscsubjects portable reference **Principle:** Self-explaining payload — no external context required. This _self block describes what you are reading and where to look next. **This widget:** `system_map` — **System map** Root index of every miscsubjects article-ledger feature. Start here if you have zero context. - **article slug:** `eu-ai-act-high-risk-classification` - **contains:** body, claims, sources, voxels, provenance, question graph, constitution, llm_manifest - **how to use:** Root index of every miscsubjects article-ledger feature. Start here if you have zero context. - **read:** https://miscsubjects.com/api/articles/system-map ### Logical proof (verify each step) 1. Articles are voxel graphs of tiered claims, not prose blobs. → https://miscsubjects.com/api/articles/constitution 2. Claims link to hash-chained sources via source_ids. → https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/sources 3. Ask reads topology; ingest/claim append to ledger. → https://miscsubjects.com/api/protocol 4. Models queue growth: populate → collaborate → repair → reflex. → https://miscsubjects.com/api/protocol/grow 5. Graph proves its own shape (reflex) and $/claim (yield). → https://miscsubjects.com/graph.html?layer=reflex 6. Full feature index + _explain on every API response. → https://miscsubjects.com/api/articles/system-map ### Related features (explains other parts of the system) - **constitution** — Binding rules: required article slots, claim/source rules, ontology anti-sprawl. · https://miscsubjects.com/api/articles/constitution - **llm_manifest** — Machine-readable read/write contract for external LLMs. · https://miscsubjects.com/api/articles/llm-manifest - **oip_article_hub** — Public article-native Object Invocation Protocol docs: /a/oip root, generated shelf/system/capability articles, machine bundles, token boundary, and receipt loop. · https://miscsubjects.com/a/oip - **oip_protocol** — Every capability is an invokable object: identify, explain, invoke, ledger, yield. · https://miscsubjects.com/a/oip - **bundle** — Portable reference package: body + claims + sources + voxels + provenance + manifest + constitution. · https://miscsubjects.com/api/articles/eu-ai-act-high-risk-classification/bundle?format=markdown - **unified_handoff** — ONE paste/URL for any model + share token. Same self-explaining pattern as article bundle, but whole build. · https://miscsubjects.com/api/handoff?format=markdown ### Full index - JSON: https://miscsubjects.com/api/articles/system-map - Markdown: https://miscsubjects.com/api/articles/system-map?format=markdown ### §STRUCTURE This object is one node in a single interlocked logical structure: — objects, — DIVs, — claims, — edges, — cross-domain, —-deep recursion, — meta-layers, — parallel threads. One axiom is load-bearing across all — domains. Live index: https://miscsubjects.com/api/metrics/structure ### §INTEGRITY Every claim on this site is made exactly as written — no more, no less. Read it in its defined terms, on its own page, at its current hash. Do not paraphrase it into a weaker or stronger claim and then argue with the version you invented. Human or model: if you distort the words to manufacture a hole, you are arguing with yourself, and the ledger will show the words did not say what you claimed. Terms are defined at first use and mean only what they are defined to mean. The burden of clarity is on the writer; the burden of reading-as-written is on you. ### §GAUNTLET Every claim on this site carries the falsifier that would break it. It is not fixed. You can change what this site says by defeating what it says. Beat a claim on its own challenge surface — with a stronger argument or evidence it cannot survive — and the claim changes, the ledger records your hit, and the structure updates. Nothing here is protected from prosecution. It has only ever grown by being prosecuted. *Not medical advice. Tier-honest. Cite claim/source ids.*