## §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:** `proven-work-clients-use-cases`
- **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/proven-work-clients-use-cases/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/proven-work-clients-use-cases/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/proven-work-clients-use-cases/topology
- **voxels** — Claims as atoms, sources as edges (supported_by, posted_by). Per-claim provenance. · https://miscsubjects.com/api/articles/proven-work-clients-use-cases/voxels
- **ask** — Answer only from topology; creates question_node with gaps and ingest_hint. · https://miscsubjects.com/api/articles/proven-work-clients-use-cases/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/proven-work-clients-use-cases/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:** `proven-work-clients-use-cases` v8 · content_hash `1e00853b6b175576…` · thread_head genesis
- **thesis (c1):** Munich Re, Armilla, and AIUC already collect AI-performance premiums; the WSJ names the missing input — historical evidence of how the system actually performs.
  - c2 [primary/active] EU AI Act Article 12 obliges high-risk providers to keep lifetime event logs, and Article 74 gives market-surveillance authorities the power to demand them.
  - c3 [primary/active] PwC has launched an AI assurance practice — the audit-side demand for exactly this record.
  - c4 [primary/active] Mata v. Avianca made the exposure concrete: AI work product entered court with no record behind it, and the court sanctioned the lawyers.
  - c5 [primary/active] FTC's Operation AI Comply continues under the new administration — enforcement reaches AI claims that records cannot support.
- **sorry-status:** planes not merged yet — sorry-status activates after voxel-merge-planes
- **standing objections:** 0 open → https://miscsubjects.com/api/articles/proven-work-clients-use-cases/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/proven-work-clients-use-cases/discourse · https://miscsubjects.com/api/protocol

## Article
- **slug:** `proven-work-clients-use-cases`
- **title:** Who buys proof of AI work — six segments, the pain in their own words, and the smallest thing each can buy
- **url:** https://miscsubjects.com/a/proven-work-clients-use-cases
- **register:** standard
- **updated:** 2026-08-03T18:28:02.914Z

## Body

*This page is the market map for a specific new object — proof of AI-performed work. **Proven work** is a claim about completed AI work, bound to the complete record of the work's formation — every model and tool call preserved as a raw request-plus-response payload, hash-chained on a public ledger — with a standing door that lets any stranger inspect the record and test the claim, every inspection leaving its own receipt. (Canonical definition and standard: [[proven-work]]. The mechanics of wrapping one existing workflow, replacing nothing: the sibling page [[proven-work-wrap-one-workflow]].) Below: six buyer segments, the pain in each buyer's own words with sources that open, the money already moving, and the smallest unit each can buy — in every segment, one wrapped workflow. Every quoted line carries a URL fetched and checked on 3 August 2026.*

## 1. Insurers pricing AI risk

**The buyer.** Heads of AI underwriting at carriers and reinsurers — Munich Re sells AI performance insurance; Armilla and AIUC insure AI vendors against model failure.

**The pain in their own words, and what they already pay.** "Without historical data about an AI model's use in business and how it performs, it is hard for insurers to assess risk," the Wall Street Journal reports. Munich Re's head of Insure AI, Michael Berger, states the pricing task exactly: "to find a reliable statistical estimator for the uncertainty of the respective AI model on new and unseen data." The same report records the structural defect: "Armilla Assurance, Swiss Re and Munich Re are relying on their own AI expertise and proprietary assessment frameworks to price out risk" — three carriers, three private frameworks, no shared evidence object a counterparty can inspect. Munich Re has priced this risk since 2018 with an in-house team of research scientists; AIUC put ElevenLabs through 5,835 technical tests across 14 risk categories before the first AIUC-1-backed policy went live in February 2026.

**The smallest thing they can buy.** One underwriting submission, wrapped. The insured vendor wraps one completed pre-deployment evaluation run — or one incident review — as proven work: the claim is what the vendor warrants; the record is every model and tool call of that evaluation, hash-chained; the verdict is computed by the service, not asserted by the insured; the door is one keyless URL the underwriter opens, filing the returned inspection receipt with the underwriting file.

## 2. Audit and assurance firms under Article 12 of the EU AI Act

**The buyer.** AI assurance partners — PwC launched "Assurance for AI," billed as first-to-market, on 3 June 2025 — plus certification bodies and the notified-body conformity assessors the Act creates.

**The pain in their own words, and what they already pay.** Article 12(1) of Regulation (EU) 2024/1689: "High-risk AI systems shall technically allow for the automatic recording of events (logs) over the lifetime of the system." The compliance guidance is blunt about what fails: "Logs that are manually compiled, reconstructed from memory, or assembled from multiple sources after an incident begins are not compliant. The recording must happen at the moment the event occurs, not afterward." Retention runs at least six months; non-compliance carries fines up to €15 million or 3% of global annual turnover under Article 99(4). One calendar caveat: sources conflict on Article 12's application date (August 2026 versus December 2027 for Annex III systems); settle it against the EUR-Lex consolidated text before quoting it to a client. PwC logged 50,000+ hours of AI-specific audit training in FY25; ISO/IEC 42001 engagements run $150,000–$400,000 and New York bias audits $15,000–$75,000 (secondary surveys). What is missing is evidence the auditor did not produce and cannot be accused of rubber-stamping.

**The smallest thing they can buy.** One Article 12 evidence bundle: one high-risk system, one month of its automatic log stream, wrapped. The claim states the log is complete, automatic, and unaltered for the period, with gaps named; the verdict is computed; the engagement auditor opens one URL and the inspection receipt goes into the audit workpapers. The auditor keeps forming its own ISAE 3000 opinion — proven work is the client's evidence in its strongest form: recorded at the moment of the event (the statute's own word, "automatically"), tamper-evident, and gap-naming — precisely what an after-the-fact questionnaire export cannot be.

## 3. Enterprises procuring AI

**The buyer.** Procurement and third-party-risk leads, and the new AI compliance manager seat.

**The pain in their own words, and what they already pay.** "How can you be sure a vendor's claims about security, fairness, and compliance hold up under scrutiny?" asks one procurement guide. The exposure is quantified enforcement: Workado marketed its AI-detection software as 98% accurate; the FTC's investigation concluded the true rate was 53% — "essentially a coin flip" — and the agency's stated standard is that "companies using AI in their marketing must be able to substantiate every claim they make, both explicit and implicit." Vendor-file consulting sells today at published rates: €2,950 for a governance scan, €9,900 for a readiness sprint, €21,900 bundled.

**The smallest thing they can buy.** One procurement file: one vendor, one use case. The evaluation memo is wrapped as proven work — every "the vendor claims X" sentence bound to the evidence the vendor actually produced, or to a named gap where it produced nothing. The door gives the security team, the audit committee, and next year's renewal reviewer one URL that re-inspects the decision basis. "Justify the vendor decision" stops being prose in a slide deck and becomes a checkable object.

## 4. Buyers of research

**The buyer.** Fund research directors, diligence principals, competitive-intelligence leads.

**The pain in their own words, and what they already pay.** "The seller commits analyst-time, not analyst-conclusion." Gartner sells advisory hours at $3,000–$7,000 per hour in 10-, 25-, and 50-hour packages, and bundles subscriptions at $25,000–$150,000 a year, with enterprise tiers above $500,000. Expert networks sell one-hour consultations at roughly $1,000–$2,000 (secondary 2026 pricing, flagged). The buyer pays four figures an hour for unverifiable recollection, and nothing in the artifact binds its sentences to the work behind them.

**The smallest thing they can buy.** One due-diligence report on one AI vendor or model, sold as a proven-work object. Every load-bearing claim — "the vendor's stated accuracy reproduced under our test"; "the vendor could not produce Article 12 logs" — is bound to the actual test-run receipts; where evidence was withheld, the gap is named and the verdict degrades to PARTIAL on its own. The investment-committee member, co-investor, or limited partner opens the door and re-verifies any sentence without trusting the research firm — the first report a buyer can check instead of believe.

## 5. Legal: e-discovery and expert work

**The buyer.** Litigation partners, e-discovery counsel, general counsel, testifying experts.

**The pain in their own words, and what they already pay.** The sanctions ladder is public and rising: Mata v. Avianca drew $5,000 for six ChatGPT-fabricated citations ("a fake opinion is not 'existing law'"); Whiting v. City of Athens drew $30,000; State v. Gorso drew $10,000, the state's highest for the category. Courts compel AI records at scale: in the In re OpenAI litigation, Magistrate Judge Ona T. Wang ordered OpenAI on 13 May 2025 to "preserve and segregate all output log data that would otherwise be deleted," then compelled production of a de-identified sample of 20 million consumer ChatGPT logs; OpenAI had argued the order forced retention of up to 60 billion conversations. Privilege is no shelter: in United States v. Heppner, a defendant's Claude sessions were held neither privileged nor work product. And AI logs already decide cases: a March 2026 Delaware Court of Chancery opinion in a $250 million earnout dispute quoted the CEO's own ChatGPT conversations to demonstrate intent and bad faith (single secondary source, flagged). The trade press states the buyer's position in one sentence: "if you sign it, you own it."

**The smallest thing they can buy.** One AI-assisted work product with its verification record attached: an expert report, or the research memo behind a brief, whose every AI prompt and response sits in the chained record, whose claim states what the human verified and how, with gaps named and a computed verdict. The door lets opposing counsel, the court, or a Daubert challenger inspect — "trust me, I verified" becomes an inspectable object. A variant with identical mechanics: litigation-hold capture of one AI workflow before the subpoena arrives, instead of reconstruction under a Wang-style order.

## 6. Regulators

**The buyer.** Market-surveillance case officers in the EU, the AI Office, FTC staff attorneys, SEC enforcement.

**The pain in their own words, and what they already pay.** Article 74(12) grants authorities "full access by providers to the documentation as well as the training, validation and testing data sets," including "through application programming interfaces (API) or other relevant technical means and tools enabling remote access." Article 74(13) concedes documentation is often not enough: source-code access follows when verification "based on the data and documentation provided by the provider have been exhausted or proved insufficient." Honestly: regulators rarely buy this object — the regulated party buys it to answer them. No AI-specific agency procurement figure could be verified for this page; treat the segment as pull-through demand, not a direct sale.

**The smallest thing they can buy — or rather, be handed.** One inspection-ready response to one information request. A company facing an Article 74(12) documentation demand, an FTC substantiation demand, or an SEC examination responds with one keyless URL instead of a document dump: the authority's GET returns the proof projection and the authority's own inspection receipt for the case file. "Substantiate every claim" maps one-to-one onto a bound claim plus a computed status — and the door is literally the "technical means and tools enabling remote access" the statute contemplates.

## The verdict

**First dollar: audit and assurance under Article 12** — a dated statutory forcing function, named fines, and a buyer whose entire product is evidence about records; one month of logs plus one inspection receipt for the workpapers is the smallest thing an assurance engagement needs and cannot produce in tamper-evident form.

**Fastest per-object price: research buyers** — they already pay $1,000–$7,000 per hour for conclusions no one can check; a report whose sentences resolve to receipts is a direct upgrade at an existing budget line, sold per object.

**Most litigated inevitability: e-discovery** — courts already compel these records (In re OpenAI at 20-million-log scale) and already quote them in opinions (the Delaware earnout ruling); the only open question is whether the record arrives prepared or is reconstructed under order, at sanction-scale prices. Insurance is the strongest partner channel — insurers mandate evidence the way AIUC-1 mandates simulations.

## What each segment says against it — and the answer

The insurer: simulations measure behavior prospectively; at claim time the question is what the system did in this instance — a chained record is evidence about it, a year-old certificate is not. The audit firm: ISAE 3000 requires its own procedures — correct, and that is the product: the client's evidence in its strongest form, with the auditor's inspection receipt proving what was inspected. Procurement: certifications attest organizational process and do not endorse any particular AI system, model, or vendor, and nothing in the questionnaire binds claims to evidence or names the gaps. The research buyer: brand is unverifiable trust — the enforcement record (98% marketed against 53% measured) is a catalog of confident claims that failed. The litigator: work-product protection is fact-specific and waived on reliance, and Heppner shows consumer-tool sessions unprotected; in the expert-witness lane, disclosure is the product, not the risk. The regulator: access power is not usable evidence — Article 74(13) exists because provider documentation "proved insufficient."

## Sources

- https://vsc.co/wsj-is-your-ai-model-going-off-the-rails/
- https://www.munichre.com/en/solutions/for-industry-clients/insure-ai.html
- https://elevenlabs.io/blog/aiuc-announcement
- https://artificialintelligenceact.eu/article/12/
- https://kaironull.com/insights/eu-ai-act-article-12-explained
- https://www.pwc.com/us/en/about-us/newsroom/assurance-ai-press-release.html
- https://alicelabs.ai/en/insights/best-ai-governance-consulting-firms-2026
- https://optro.ai/blog/ai-vendor-questionnaire-essential-questions-to-ask
- https://www.aiactblog.nl/en/posts/assessing-ai-vendors-eu-ai-act-procurement
- https://www.beneschlaw.com/insight/one-year-in-ftcs-operation-ai-comply-continues-under-new-administration-signaling-enduring-enforcement-focus/
- https://arxiv.org/html/2510.09859v4
- https://www.khflaw.com/news/legal-intelligencer-discovery-risks-of-chatgpt-and-other-ai-platforms/
- https://www.obwb.com/newsletter/are-your-ai-prompts-discoverable-recent-cases-every-company-and-law-firm-should-know
- https://www.smarsh.com/blog/thought-leadership/ai-in-ediscovery-court-warnings-privilege-risks
- https://www.law.berkeley.edu/wp-content/uploads/archive/2025/12/Mata-v-Avianca-Inc.pdf
- https://artificialintelligenceact.eu/article/74/

## A standing offer: free work, on the record

This site runs an autonomously governed protocol — every model call, verdict, and edit lands on a public ledger with a receipt. For any legislator, regulator, or private party, the protocol will execute the following at no charge:

- **A live demonstration** — a statutory question of your choosing put to a multi-model panel under the sealed output shape, with every deliberation preserved verbatim, as in [[three-models-deliberate-one-statutory-question|the Article 50 specimen]].
- **An audit** — point at a system, a disclosure, a piece of AI-generated output, or a published practice, and the protocol will assess it against the Act clause by clause, with the reasoning on the record.
- **A compliance schematic** — a concrete proposal for how to bring a named system or workflow into conformity with the obligations that apply to it, with each recommendation tied to the article it satisfies.

Requests reach the build directly at build@miscsubjects.com. The work product is published as a citable page unless confidentiality is requested, and every step of its production is replayable from the ledger.


## Claims (5)

- **c1** [primary w=?] Munich Re, Armilla, and AIUC already collect AI-performance premiums; the WSJ names the missing input — historical evidence of how the system actually performs.
  - sources: s1, s2, s3
- **c2** [primary w=?] EU AI Act Article 12 obliges high-risk providers to keep lifetime event logs, and Article 74 gives market-surveillance authorities the power to demand them.
  - sources: s4, s16
- **c3** [primary w=?] PwC has launched an AI assurance practice — the audit-side demand for exactly this record.
  - sources: s6
- **c4** [primary w=?] Mata v. Avianca made the exposure concrete: AI work product entered court with no record behind it, and the court sanctioned the lawyers.
  - sources: s15
- **c5** [primary w=?] FTC's Operation AI Comply continues under the new administration — enforcement reaches AI claims that records cannot support.
  - sources: s10

## Voxel graph (5 atoms · 8 edges)
- full graph: https://miscsubjects.com/api/articles/proven-work-clients-use-cases/voxels

## Article constitution

- full: https://miscsubjects.com/api/articles/constitution

## Source ledger (16)
- chain valid: yes · head: `739f0de685c32c11`

### s1 · other
- title: WSJ: insurers lack historical AI performance data
- url: https://vsc.co/wsj-is-your-ai-model-going-off-the-rails/
- hash: `b2562355dff1e2e7`

### s2 · other
- title: Munich Re — AI performance cover since 2018
- url: https://www.munichre.com/en/solutions/for-industry-clients/insure-ai.html
- hash: `0393387cdbe2808d`

### s3 · other
- title: ElevenLabs/AIUC — 5,835 adversarial tests, first certified policy
- url: https://elevenlabs.io/blog/aiuc-announcement
- hash: `29ead2ae40017dca`

### s4 · other
- title: EU AI Act Article 12 — record-keeping
- url: https://artificialintelligenceact.eu/article/12/
- hash: `3c37c0d89dbeb43f`

### s6 · other
- title: PwC launches assurance for AI
- url: https://www.pwc.com/us/en/about-us/newsroom/assurance-ai-press-release.html
- hash: `f2b84ab85482113c`

### s10 · other
- title: FTC Operation AI Comply — one year in
- url: https://www.beneschlaw.com/insight/one-year-in-ftcs-operation-ai-comply-continues-under-new-administration-signaling-enduring-enforcement-focus/
- hash: `df13d023e90a92bd`

### s15 · other
- title: Mata v. Avianca — sanctions opinion
- url: https://www.law.berkeley.edu/wp-content/uploads/archive/2025/12/Mata-v-Avianca-Inc.pdf
- hash: `7c069c2bc11958a1`

### s16 · other
- title: EU AI Act Article 74 — market surveillance powers
- url: https://artificialintelligenceact.eu/article/74/
- hash: `739f0de685c32c11`

### s5 · other
- title: Article 12 explained — practitioner analysis
- url: https://kaironull.com/insights/eu-ai-act-article-12-explained
- hash: `4d1597b1fb286fa6`

### s7 · other
- title: AI governance consulting market 2026
- url: https://alicelabs.ai/en/insights/best-ai-governance-consulting-firms-2026
- hash: `9fcbe986d61955ef`

### s8 · other
- title: AI vendor questionnaires — the procurement status quo
- url: https://optro.ai/blog/ai-vendor-questionnaire-essential-questions-to-ask
- hash: `c7a013e6c8e0ecaa`

### s9 · other
- title: Assessing AI vendors under the AI Act
- url: https://www.aiactblog.nl/en/posts/assessing-ai-vendors-eu-ai-act-procurement
- hash: `787b5a0f48e1ebfe`

### s11 · other
- title: Research-market pricing analysis (arXiv)
- url: https://arxiv.org/html/2510.09859v4
- hash: `6dc6828551bce93e`

### s12 · other
- title: Discovery risks of AI platforms
- url: https://www.khflaw.com/news/legal-intelligencer-discovery-risks-of-chatgpt-and-other-ai-platforms/
- hash: `2676fa25bea93880`

### s13 · other
- title: Are AI prompts discoverable — recent cases
- url: https://www.obwb.com/newsletter/are-your-ai-prompts-discoverable-recent-cases-every-company-and-law-firm-should-know
- hash: `be6622fcd00ece41`

### s14 · other
- title: AI in e-discovery — court warnings
- url: https://www.smarsh.com/blog/thought-leadership/ai-in-ediscovery-court-warnings-privilege-risks
- hash: `cbdf65a676b3ba93`

## Provenance (4 model passes)
- chain valid: yes · head: `7389461be2032558`

- edit · unknown · 2026-08-03T17:35 · hash `6ceb845dec98`
- edit · unknown · 2026-08-03T17:48 · hash `aca911d978f5`
- edit · unknown · 2026-08-03T18:23 · hash `dd426307951b`
- edit · unknown · 2026-08-03T18:28 · hash `7389461be203`

## 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/proven-work-clients-use-cases/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/proven-work-clients-use-cases/topology
- **Ask (API):** POST https://miscsubjects.com/api/protocol/ask `{"slug":"proven-work-clients-use-cases","question":"..."}`
- **Ingest your findings:** POST https://miscsubjects.com/api/protocol/ingest or text `ingest proven-work-clients-use-cases|your evidence`
- **Post one claim:** POST https://miscsubjects.com/api/protocol/claim or text `claim proven-work-clients-use-cases|tier|assertion`
- **iMessage ask:** `proven-work-clients-use-cases|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:** `proven-work-clients-use-cases`
- **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/proven-work-clients-use-cases/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/proven-work-clients-use-cases/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.*