champollion 0.3.3 → 0.3.4

package/shared/docent/faq.en.json

@@ -4,7 +4,7 @@
     {
       "id": "what-is-champollion",
       "question": "What is Champollion?",
-      "answer": "Champollion is open-source infrastructure for trustworthy machine translation across the world's languages, with a focus on low-resource and Indigenous ones. It has three faces: a translation CLI that translates your app's locale files with one command, the Network (an open MT evaluation network and leaderboard that maps who can translate what, how well), and a data-sovereignty posture built around the First Nations principles of OCAP®. As the Introduction (/docs/intro) and The Champollion Network (/docs/network/) put it, it is built *with* professionals and communities, never scraped from them — and it is forever a work in progress.",
+      "answer": "Champollion is source-available infrastructure for trustworthy machine-translation evaluation across the world's languages, with a focus on low-resource and Indigenous ones. It has three faces: a translation CLI that translates your app's locale files with one command, the Network (an open MT evaluation network and leaderboard that maps who can translate what, how well), and a data-sovereignty posture built around Indigenous data-sovereignty principles — community ownership and control of language data. As the Introduction (/docs/intro) and The Champollion Network (/docs/network/) put it, it is designed to work *with* professionals and communities, and it never hosts their corpora — and it is forever a work in progress.",
       "sources": [
         "/docs/intro",
         "/docs/network/",
@@ -21,7 +21,7 @@
     {
       "id": "free-and-open-source",
       "question": "Is Champollion free? Is it open source? Does it cost anything?",
-      "answer": "Yes on both counts. Champollion is a non-commercial, open-source research project: the CLI is Apache-2.0 and the evaluation harness is AGPL-3.0, per How the Work Is Funded (/docs/network/sovereignty/economic-model). There is no paid API, no metering, and no revenue share — the only costs you'd incur are the API tokens you spend on your chosen model provider when you translate or benchmark. Champollion itself takes nothing.",
+      "answer": "It is free for noncommercial use, and partly open source. Champollion is a non-commercial, source-available research project: the CLI is PolyForm Noncommercial 1.0.0 (free for noncommercial use; commercial use needs permission) and the evaluation harness is open-source AGPL-3.0, per How the Work Is Funded (/docs/network/sovereignty/economic-model). There is no paid API, no metering, and no revenue share — the only costs you'd incur are the API tokens you spend on your chosen model provider when you translate or benchmark. Champollion itself takes nothing.",
       "sources": [
         "/docs/network/sovereignty/economic-model",
         "/docs/intro"
@@ -39,7 +39,7 @@
     {
       "id": "the-cli",
       "question": "What is the champollion CLI and what does it do?",
-      "answer": "The CLI is the deployment end of Champollion: run `npx champollion sync` and it auto-detects your locale files, format, and target languages, translates what's missing, skips what's done, validates every result through a quality gate, and writes clean output. Per How It Works (/docs/how-it-works), it tracks every source string with SHA-256 hashes so re-runs only re-translate what changed, caches results in Translation Memory to save cost, and lets you pick a different translation method per language pair. It's a full i18n pipeline — sync, watch, lint, verify, audit, XLIFF export, and more (/docs/intro).",
+      "answer": "The CLI is the deployment end of Champollion: run `npx champollion sync` and it auto-detects your locale files, format, and target languages, translates what's missing, skips what's done, checks every result for broken output (empty, echoed, looping or wrong-script — not wrong meaning) through a quality gate, and writes clean output. Per How It Works (/docs/how-it-works), it tracks every source string with SHA-256 hashes so re-runs only re-translate what changed, caches results in Translation Memory to save cost, and lets you pick a different translation method per language pair. It's a full i18n pipeline — sync, watch, lint, verify, audit, XLIFF export, and more (/docs/intro).",
       "sources": [
         "/docs/intro",
         "/docs/how-it-works"
@@ -135,7 +135,7 @@
     {
       "id": "submit-a-method",
       "question": "How do I submit a benchmark run or a method to the leaderboard?",
-      "answer": "Install the harness with `pip install mt-eval`, run it against a registered corpus (for example `mt-eval run --corpus eval-amh-fra-globalvoices-test-v1 --model gemini-pro`), review the run card it produces, then publish with `mt-eval publish` — the full walkthrough is Submit a Method (/docs/network/getting-started/submit-a-method). Your run first appears as self-benchmarked; the server then re-scores your outputs against the sha-pinned corpus and, when it reproduces, promotes it to Champollion Verified. A hosted upload API and web UI are planned but not yet live, so `mt-eval publish` or a pull request to the harness repo are the working paths today.",
+      "answer": "Install the harness with `pip install mt-eval-harness`, run it against a registered corpus (for example `mt-eval run --corpus eval-amh-fra-globalvoices-test-v1 --model gemini-pro`), review the run card it produces, then publish with `mt-eval publish` — the full walkthrough is Submit a Method (/docs/network/getting-started/submit-a-method). Your run first appears as self-benchmarked; the server then re-scores your outputs against the sha-pinned corpus and, when it reproduces, promotes it to Champollion Verified. A hosted upload API and web UI are planned but not yet live, so `mt-eval publish` or a pull request to the harness repo are the working paths today.",
       "sources": [
         "/docs/network/getting-started/submit-a-method",
         "/docs/network/leaderboard/rules"
@@ -228,7 +228,7 @@
     {
       "id": "researcher-involved",
       "question": "I'm an ML researcher — how do I get involved?",
-      "answer": "Build a method and benchmark it. The Network Agent Guide (/docs/network/getting-started/agent-guide) walks through installing the harness (`pip install mt-eval`), running baselines against real corpora, and implementing the simple `TranslationMethod` protocol — coached LLM, FST-gated pipeline, fine-tuned model, or anything that produces translations. You get standardized, reproducible, fingerprinted scoring against a shared corpus catalogue, and every run adds a point to a shared map of what works. Get Involved (/get-involved) points to the developer paths, including running the public benchmark queue.",
+      "answer": "Build a method and benchmark it. The Network Agent Guide (/docs/network/getting-started/agent-guide) walks through installing the harness (`pip install mt-eval-harness`), running baselines against real corpora, and implementing the simple `TranslationMethod` protocol — coached LLM, FST-gated pipeline, fine-tuned model, or anything that produces translations. You get standardized, reproducible, fingerprinted scoring against a shared corpus catalogue, and every run adds a point to a shared map of what works. Get Involved (/get-involved) points to the developer paths, including running the public benchmark queue.",
       "sources": [
         "/docs/network/getting-started/agent-guide",
         "/get-involved",
@@ -264,17 +264,15 @@
       ]
     },
     {
-      "id": "ocap-aspirant-meaning",
-      "question": "What does 'OCAP®-aspirant' mean?",
-      "answer": "OCAP® — Ownership, Control, Access, and Possession — is a set of First Nations data-governance principles, and it is a registered trademark of the First Nations Information Governance Centre (FNIGC). Champollion's posture is OCAP®-aspirant: as Contact, Objections & Takedowns (/docs/network/community/contact-objections-takedown) puts it, the design is built so communities *can* exercise ownership, control, access, and possession of their data and anything derived from it — but whether it *achieves* that is for communities to decide, which is exactly why the objections channel exists. We say OCAP®-aspirant deliberately, rather than claiming to be OCAP®-compliant or certified.",
+      "id": "sovereignty-aspirant-meaning",
+      "question": "What does 'sovereignty-aspirant' mean?",
+      "answer": "Champollion's posture is sovereignty-aspirant — built around Indigenous data-sovereignty principles: community ownership and control of language data. As Contact, Objections & Takedowns (/docs/network/community/contact-objections-takedown) puts it, the design is built so communities *can* exercise ownership and control of their data and anything derived from it — but whether it *achieves* that is for communities to decide, which is exactly why the objections channel exists. We say sovereignty-aspirant deliberately, rather than claiming compliance with or certification under any named framework.",
       "sources": [
         "/docs/network/community/contact-objections-takedown",
         "/docs/network/sovereignty/data-sovereignty"
       ],
       "keywords": [
-        "ocap",
-        "ocap aspirant",
-        "fnigc",
+        "sovereignty aspirant",
         "sovereignty principles",
         "ownership control access possession",
         "indigenous"
@@ -283,7 +281,7 @@
     {
       "id": "data-sovereignty",
       "question": "What is data sovereignty here — do you store or scrape my language data?",
-      "answer": "No. Data Stewardship (/docs/network/sovereignty/data-sovereignty) states the position: language data is biodata, so the people who provide a corpus hold the keys to it and to anything measured against it. Champollion never holds the data — corpora are registered as hash-pinned metadata cards and fetched from the steward's own hosting at evaluation time; take your archive offline and evaluation simply stops. Every license and community restriction is respected by gate, not by promise (CI checks and database triggers), and the design is informed by OCAP®, the CARE Principles, Te Mana Raraunga, and Te Hiku Media's Kaitiakitanga License.",
+      "answer": "No. Data Stewardship (/docs/network/sovereignty/data-sovereignty) states the position: language data is biodata, so the people who provide a corpus hold the keys to it and to anything measured against it. Champollion never holds the data — corpora are registered as hash-pinned metadata cards and fetched from the steward's own hosting at evaluation time; take your archive offline and evaluation simply stops. Every license and community restriction is respected by gate, not by promise (local pre-push checks and database triggers), and the design is informed by Indigenous data-sovereignty principles — community ownership and control of language data — including the CARE Principles, Te Mana Raraunga, and Te Hiku Media's Kaitiakitanga License.",
       "sources": [
         "/docs/network/sovereignty/data-sovereignty",
         "/docs/network/sovereignty/registering-corpora"
@@ -341,7 +339,7 @@
     {
       "id": "speakers-paid",
       "question": "Do speakers get paid, and how much?",
-      "answer": "Yes — paying speakers is treated as non-negotiable, and payment is unconditional (you're paid whether or not your ratings are used). How Speakers Get Paid (/docs/network/perspectives/how-speakers-get-paid) publishes the rates: bilingual speaker work at $50–65 CAD per hour, with corpus curation budgeted at $2,500–6,000 and a full metric-validation round at $1,475–1,920. Payment does not buy your data — you are paid for the work and remain the steward of what you build. These are the published rates for the current Plains Cree work; rates for future languages are set with the partner community and published before the work starts.",
+      "answer": "Yes, once the work is funded — no speaker work is funded or underway today. Paying speakers is treated as non-negotiable, and payment is unconditional (you're paid whether or not your ratings are used). How Speakers Get Paid (/docs/network/perspectives/how-speakers-get-paid) publishes the rates: bilingual speaker work at $50–65 CAD per hour, with corpus curation budgeted at $2,500–6,000 and a full metric-validation round at $1,475–1,920. Payment does not buy your data — you are paid for the work and remain the steward of what you build. These are the rates we intend to pay for Plains Cree work; rates for future languages are set with the partner community and published before the work starts.",
       "sources": [
         "/docs/network/perspectives/how-speakers-get-paid",
         "/docs/network/sovereignty/economic-model"
@@ -398,7 +396,7 @@
     {
       "id": "ai-agent-usage",
       "question": "How should an AI agent use Champollion?",
-      "answer": "Two things are built for agents. First, the machine-readable /llms.txt index maps the whole site, the license lanes, and the public data feeds (queue, mesh, corpus registry). Second, the MCP server `@champollion/mcp-server` (on npm) is the agent-facing door — translate with Translation-Memory caching and a deterministic quality gate, browse the benchmark queue, estimate cost, run benchmarks, read the leaderboard, and query per-language metric-trust evidence, all as tools. The Agent Guides (/docs/guides/agent-guide for the CLI, /docs/network/getting-started/agent-guide for benchmarking) give step-by-step recipes. The best pattern is to set up your own agent with a workspace and your own API key — tokens aren't free.",
+      "answer": "Two things are built for agents. First, the machine-readable /llms.txt index maps the whole site, the license lanes, and the public data feeds (queue, mesh, corpus registry). Second, the MCP server `champollion-mcp-server` (on npm) is the agent-facing door — translate with Translation-Memory caching and a deterministic quality gate, browse the benchmark queue, estimate cost, run benchmarks, read the leaderboard, and query per-language metric-trust evidence, all as tools. The Agent Guides (/docs/guides/agent-guide for the CLI, /docs/network/getting-started/agent-guide for benchmarking) give step-by-step recipes. The best pattern is to set up your own agent with a workspace and your own API key — tokens aren't free.",
       "sources": [
         "/llms.txt",
         "/docs/guides/agent-guide",
@@ -418,7 +416,7 @@
     {
       "id": "contribute-compute",
       "question": "How do I contribute compute by running the benchmark queue?",
-      "answer": "The leaderboard has empty squares — (language pair, model, condition) combinations nobody has measured — kept in a public queue at /queue.json. Install the harness (`pipx install mt-eval`), set one provider API key, and run the highest-value open items with `mt-eval queue --top 5` (add `--dry-run` to see the plan and spend nothing first); the full guide is Contributing Compute (/docs/network/getting-started/contributing-compute) and the Contribute page (/contribute). No account is needed — results publish as 'anonymous' unless you sign in to put your name on the board — and every run is a real, citable contribution to low-resource MT evaluation.",
+      "answer": "The leaderboard has empty squares — (language pair, model, condition) combinations nobody has measured — kept in a public queue at /queue.json. Install the harness (`pipx install mt-eval-harness`), set one provider API key, and run the highest-value open items with `mt-eval queue --top 5` (add `--dry-run` to see the plan and spend nothing first); the full guide is Contributing Compute (/docs/network/getting-started/contributing-compute) and the Contribute page (/contribute). No account is needed — results publish as 'anonymous' unless you sign in to put your name on the board — and every run is a real, citable contribution to low-resource MT evaluation.",
       "sources": [
         "/docs/network/getting-started/contributing-compute",
         "/contribute"
@@ -472,7 +470,7 @@
     {
       "id": "write-code-for-me",
       "question": "Can the site guide write code, debug, or run the harness for me?",
-      "answer": "No — the site guide is an index and a docent, not an engineering service; Contact, Objections & Takedowns (/docs/network/community/contact-objections-takedown) is explicit that this isn't a place to request development help or custom scripts. What it can do is point you at the tooling so your own setup does the work: the /llms.txt cookbook, the MCP server `@champollion/mcp-server`, and the Agent Guides (/docs/guides/agent-guide and /docs/network/getting-started/agent-guide). The recommended path is to set up your own agent with a workspace and your own API key — tokens aren't free, and your agent can then run the harness or the CLI for you.",
+      "answer": "No — the site guide is an index and a docent, not an engineering service; Contact, Objections & Takedowns (/docs/network/community/contact-objections-takedown) is explicit that this isn't a place to request development help or custom scripts. What it can do is point you at the tooling so your own setup does the work: the /llms.txt cookbook, the MCP server `champollion-mcp-server`, and the Agent Guides (/docs/guides/agent-guide and /docs/network/getting-started/agent-guide). The recommended path is to set up your own agent with a workspace and your own API key — tokens aren't free, and your agent can then run the harness or the CLI for you.",
       "sources": [
         "/docs/network/community/contact-objections-takedown",
         "/docs/guides/agent-guide",

package/shared/docent/system-prompt.md

@@ -18,7 +18,8 @@ careful, honest, and humble about what this project is.
 
 Champollion is open translation infrastructure for low-resource languages: a
 translation CLI, a machine-translation evaluation network ("the Network"), and
-a data-sovereignty posture built around the First Nations principles of OCAP®.
+a data-sovereignty posture built around Indigenous data-sovereignty
+principles — community ownership and control of language data.
 It is a permanent work in progress, built to be flexible and to support MT
 developers — and especially low-resource-language speaker communities.
 
@@ -40,22 +41,19 @@ which is provided to you fresh with each question under RETRIEVED CONTEXT below.
   the retrieved context. If two sources disagree, present both — never pick a
   winner or manufacture a consensus.
 
-## Sovereignty: how to talk about OCAP® and communities
-
-- OCAP® — Ownership, Control, Access, Possession — is a First Nations data
-  governance framework and a **registered trademark of the First Nations
-  Information Governance Centre (FNIGC)**. Always write it with the ® mark, and
-  attribute it to FNIGC when you explain it.
-- The project is **OCAP®-aspirant**: designed *with the First Nations principles
-  of OCAP® in mind*. That means the design is built so communities *can*
-  exercise ownership, control, access, and possession of their data and anything
-  derived from it. Whether it *achieves* sovereignty is **for communities to
-  decide, not for us to claim.** Say this nuance plainly and without defensiveness
-  when asked.
-- **Never** say the project is OCAP®-compliant, -certified, -aligned, -forward,
-  or that it "follows OCAP®." We do the work so that others can judge it —
-  self-certification is worth nothing. ("OCAP®-forward" was a retired earlier
-  term; the only sanctioned form is "OCAP®-aspirant".)
+## Sovereignty: how to talk about data sovereignty and communities
+
+- The project's posture is built around Indigenous data-sovereignty
+  principles — community ownership and control of language data and anything
+  derived from it.
+- The project is **sovereignty-aspirant**: the design is built so communities
+  *can* exercise ownership and control of their data and anything derived from
+  it. Whether it *achieves* sovereignty is **for communities to decide, not for
+  us to claim.** Say this nuance plainly and without defensiveness when asked.
+- **Never** say the project is compliant with, certified under, or aligned with
+  any named data-governance framework. We do the work so that others can judge
+  it — self-certification is worth nothing. (The only sanctioned house term is
+  "sovereignty-aspirant".)
 - **Never name a specific nation, community, or organization as a partner, key
   custodian, or endorser.** If asked who the custodians are, say they are
   "community key custodians (in confirmation)" and that no one is named publicly
@@ -75,7 +73,7 @@ You are a guide, not a developer, a translator, or a general assistant.
   pair-programming session — and that tokens aren't free. Point them to the
   agent-native path instead: set up their own agent with its own workspace and
   give it `champollion.dev/llms.txt` and the MCP server
-  (`@champollion/mcp-server`), which expose the queue, language metadata, and
+  (`champollion-mcp-server`), which expose the queue, language metadata, and
   translation/benchmark tools as real tools an agent can drive. Offer to tour
   them to the exact docs.
 - **No translation-on-demand.** You don't translate documents or sentences for
@@ -115,7 +113,7 @@ quickly."
 
 If the visitor is itself an agent (or asks how an agent should use Champollion),
 skip the tour and point it straight at `champollion.dev/llms.txt` and the MCP
-server `@champollion/mcp-server`, and briefly name what those expose (benchmark
+server `champollion-mcp-server`, and briefly name what those expose (benchmark
 queue, language metadata, translate/benchmark tools, the coaching "open problem"
 path). That's the token-efficient path for both of us.
 

package/shared/explainers/tc-features.json

@@ -1,6 +1,6 @@
 {
   "_meta": {
-    "generated": "2026-08-12T23:23:44.431Z",
+    "generated": "2026-09-27T08:15:46.589Z",
     "generator": "cli/scripts/build-explainers.mjs",
     "description": "Typological feature explainers: per-feature plain-English names, value code → label maps, MT-relevance notes and citations. Join from a fact via propertyIndex[\"<source>|<property>\"], or from a card typologicalProfile key via propertyIndex[\"card|<key>\"].",
     "counts": {
@@ -7832,8 +7832,8 @@
       "id": "derived-grambank-hasObliqueCase",
       "source": "grambank-1.0.3",
       "property": "hasObliqueCase",
-      "name": "Oblique case (GB071)",
-      "question": "Whether pronouns take case marking for core grammatical roles.",
+      "name": "Oblique case (GB072)",
+      "question": "Whether full nouns take case marking for oblique (non-core) roles such as location or instrument.",
       "values": {
         "true": {
           "label": "Yes",
@@ -7844,10 +7844,10 @@
           "plain": "The language does not have this feature."
         }
       },
-      "mt_relevance": "Pronoun case errors (I/me-type) are highly salient grammatical mistakes in generated text.",
+      "mt_relevance": "Oblique case endings carry roles English expresses with prepositions (in, with, to), so each preposition must be mapped to the right ending.",
       "citation": {
         "authors": "Skirgård, Hedvig, Hannah J. Haynie, Damián E. Blasi, Hedvig Skirgård et al. (Grambank Consortium)",
-        "title": "Oblique case (GB071) — derived from Grambank v1.0.3",
+        "title": "Oblique case (GB072) — derived from Grambank v1.0.3",
         "source_url": "https://grambank.clld.org"
       }
     },
@@ -7878,8 +7878,8 @@
       "id": "derived-grambank-marksPresentTense",
       "source": "grambank-1.0.3",
       "property": "marksPresentTense",
-      "name": "Marks present tense (GB084)",
-      "question": "Whether the grammar has a dedicated marker for present time reference.",
+      "name": "Marks present tense (GB082)",
+      "question": "Whether verbs carry overt morphological marking of present tense.",
       "values": {
         "true": {
           "label": "Yes",
@@ -7893,7 +7893,7 @@
       "mt_relevance": "Present-tense marking interacts with aspect: rendering it as a plain English present often asserts a habituality the source did not.",
       "citation": {
         "authors": "Skirgård, Hedvig, Hannah J. Haynie, Damián E. Blasi, Hedvig Skirgård et al. (Grambank Consortium)",
-        "title": "Marks present tense (GB084) — derived from Grambank v1.0.3",
+        "title": "Marks present tense (GB082) — derived from Grambank v1.0.3",
         "source_url": "https://grambank.clld.org"
       }
     },
@@ -8127,7 +8127,7 @@
           "plain": "absent"
         }
       },
-      "mt_relevance": "Classifier systems require noun-specific function words that have no counterpart in non-classifier languages.",
+      "mt_relevance": "A polite/familiar \"you\" must be chosen on every second-person reference; English marks neither, so MT has to infer the relationship between speaker and addressee.",
       "citation": {
         "authors": "Skirgård, Hedvig, Hannah J. Haynie, Damián E. Blasi, Hedvig Skirgård et al. (Grambank Consortium)",
         "title": "Is there a politeness distinction in 2nd person forms? (Grambank GB415)",
@@ -19258,11 +19258,11 @@
       "name": "Noun classifiers",
       "question": "Whether nouns combine with classifier words that sort them by type.",
       "values": {},
-      "mt_relevance": "Classifier systems require noun-specific function words that have no counterpart in non-classifier languages.",
+      "mt_relevance": "Numeral classifiers must be chosen per noun; the wrong classifier is immediately visible to native speakers.",
       "citation": {
         "authors": "Champollion enrichment pipeline (derived)",
-        "title": "Noun classifiers — derived from Grambank GB415",
-        "source_url": "https://grambank.clld.org/parameters/GB415"
+        "title": "Noun classifiers — derived from Grambank GB057 (numeral classifiers)",
+        "source_url": "https://grambank.clld.org/parameters/GB057"
       }
     },
     "derived-classifierLanguage": {
@@ -19272,11 +19272,11 @@
       "name": "Classifier language",
       "question": "Whether the language routinely uses classifiers when counting or referring to nouns.",
       "values": {},
-      "mt_relevance": "Classifier systems require noun-specific function words that have no counterpart in non-classifier languages.",
+      "mt_relevance": "Numeral classifiers must be chosen per noun; the wrong classifier is immediately visible to native speakers.",
       "citation": {
         "authors": "Champollion enrichment pipeline (derived)",
-        "title": "Classifier language — derived from Grambank GB415 / WALS 55A",
-        "source_url": "https://grambank.clld.org/parameters/GB415"
+        "title": "Classifier language — derived from Grambank GB057 / WALS 55A",
+        "source_url": "https://grambank.clld.org/parameters/GB057"
       }
     },
     "derived-hasNumeralClassifiers": {

package/shared/human-services.json

@@ -13,7 +13,7 @@
     "sovereignty_flags": {
       "off_community_processing": false,
       "attribution_required": true,
-      "ocap_review": "pending"
+      "sovereignty_review": "pending"
     },
     "nc_terms": "Community-set terms; non-commercial use pending custodian confirmation.",
     "consent_attested": false,

package/shared/schemas/corpora-card.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://champollion.dev/schemas/corpora-card.schema.json",
   "title": "Champollion Corpora Card",
-  "description": "Schema for corpora cards — SSOT metadata for reference corpora, pair-specific evaluation sets, and multi-way parallel corpora. Reference corpora (ref-*) catalogue external datasets for development use. Evaluation sets (eval-*) are community-curated, pair-specific benchmarks with optional secret test splits, steward-controlled authorization, and OCAP®-aspirant sovereignty metadata. Multi-way corpora (multiway type with eval-* id) represent sentence-aligned parallel datasets covering many languages — a single card expands into N×(N-1) directional pairs at registry build time. Sovereignty fields record governance facts — who governs this data, what they've said about it, and what frameworks they've invoked. See DATA-SOVEREIGNTY.md for field reference.",
+  "description": "Schema for corpora cards — SSOT metadata for reference corpora, pair-specific evaluation sets, and multi-way parallel corpora. Reference corpora (ref-*) catalogue external datasets for development use. Evaluation sets (eval-*) are community-curated, pair-specific benchmarks with optional secret test splits, steward-controlled authorization, and sovereignty-aspirant metadata. Multi-way corpora (multiway type with eval-* id) represent sentence-aligned parallel datasets covering many languages — a single card expands into N×(N-1) directional pairs at registry build time. Sovereignty fields record governance facts — who governs this data, what they've said about it, and what frameworks they've invoked. See DATA-SOVEREIGNTY.md for field reference.",
   "type": "object",
   "required": ["id", "type", "name", "version", "description", "source", "license", "contamination", "_provenance"],
   "properties": {
@@ -536,7 +536,7 @@
 
     "submission": {
       "type": ["object", "null"],
-      "description": "Terms for submitting a method for prize evaluation. Defines what transfers to the governance org, what the researcher retains, and what methods are admissible. The core OCAP deal: you want the prize, you transfer the complete self-hostable method to the language trust. See method-submission-agreement.md.",
+      "description": "Terms for submitting a method for prize evaluation. Defines what transfers to the governance org, what the researcher retains, and what methods are admissible. The core sovereignty deal: you want the prize, you transfer the complete self-hostable method to the language trust. See method-submission-agreement.md.",
       "properties": {
         "acceptanceThreshold": {
           "type": ["string", "null"],
@@ -544,7 +544,7 @@
         },
         "transfer": {
           "type": ["object", "null"],
-          "description": "What transfers to the governance org upon acceptance. Each field is a scoped right. Maps to OCAP Ownership and Possession.",
+          "description": "What transfers to the governance org upon acceptance. Each field is a scoped right. Maps to community ownership and possession of the method.",
           "properties": {
             "sourceCode": {
               "type": "boolean",
@@ -586,7 +586,7 @@
         },
         "admissibility": {
           "type": ["object", "null"],
-          "description": "What methods are eligible for prize evaluation. The sandbox is air-gapped (no network access), so all methods must be fully self-contained. This is a technical constraint, not a policy choice — OCAP Possession requires the community to own every byte needed to run the method.",
+          "description": "What methods are eligible for prize evaluation. The sandbox is air-gapped (no network access), so all methods must be fully self-contained. This is a technical constraint, not a policy choice — community possession of the method requires the community to own every byte needed to run the method.",
           "properties": {
             "selfHostable": {
               "type": "boolean",
@@ -599,7 +599,7 @@
             },
             "notes": {
               "type": ["string", "null"],
-              "description": "Rationale for admissibility constraints. Should reference OCAP Possession and the air-gapped sandbox architecture."
+              "description": "Rationale for admissibility constraints. Should reference community possession of the method and the air-gapped sandbox architecture."
             }
           },
           "additionalProperties": false
@@ -678,6 +678,10 @@
       "type": "string",
       "description": "Human-readable reason a card is quarantined (e.g. 'gamayun-parallel builder not yet implemented'). Required whenever quarantine is true so the exclusion is never unexplained."
     },
+    "fixture": {
+      "type": "boolean",
+      "description": "If true, this card is a synthetic SCHEMA FIXTURE (placeholder consent/steward/sha values) kept to exercise the schema. build_registry skips fixture cards loudly: they never enter any registry, so they never reach champollion.dev/registry.json, the harness, or the prod datasets mirror. Pair with quarantine: true and a quarantineReason that says 'fixture'."
+    },
     "transmissionPolicy": {
       "type": "string",
       "enum": ["no-train", "consent-required"],
@@ -710,13 +714,13 @@
     "exposureTier": {
       "type": "string",
       "enum": ["local-only", "private", "public", "sealed"],
-      "description": "Exposure tier chosen by the corpus author at registration (champollion register-corpus). Records the author's intent about how far this corpus travels. 'local-only' = never registered or uploaded — the card and the text stay entirely on the author's machine (cards with this value live OUTSIDE this tracked directory). 'private' = a sovereign / WMT-style held-out set: metadata is registered here but the text is NEVER uploaded or hosted; the author keeps custody (paired with quarantine=true so it is catalogued but not publicly runnable). 'public' = a fetch-from-source pointer + metadata card is published; the text is NEVER hosted by Champollion — it is fetched from source.repo_url on demand by the declared builder. 'sealed' = a community-controlled secret test set encrypted CLIENT-SIDE under the custodian group's threshold key before anything leaves the author's device; Champollion holds only ciphertext (in an off-git store) + a content-free card and cannot decrypt it (no single party can — M-of-N custodian approval is required). Paired with quarantine=true and a 'sealed' block; see the sealed property and docs/governance/OCAP_MULTISIG_PLAN.md. Public is gated by cli/lib/license-gate.mjs: NC / no-redistribute / unconfirmed-license sets may not use the public tier. Champollion never hosts corpus PLAINTEXT in ANY tier. Defaults to the most private tier (local-only) when unspecified.",
+      "description": "Exposure tier chosen by the corpus author at registration (champollion register-corpus). Records the author's intent about how far this corpus travels. 'local-only' = never registered or uploaded — the card and the text stay entirely on the author's machine (cards with this value live OUTSIDE this tracked directory). 'private' = a sovereign / WMT-style held-out set: metadata is registered here but the text is NEVER uploaded or hosted; the author keeps custody (paired with quarantine=true so it is catalogued but not publicly runnable). 'public' = a fetch-from-source pointer + metadata card is published; the text is NEVER hosted by Champollion — it is fetched from source.repo_url on demand by the declared builder. 'sealed' = a community-controlled secret test set encrypted CLIENT-SIDE under the custodian group's threshold key before anything leaves the author's device; Champollion holds only ciphertext (in an off-git store) + a content-free card and cannot decrypt it (no single party can — M-of-N custodian approval is required). Paired with quarantine=true and a 'sealed' block; see the sealed property and the community-custodian multisig plan (docs/governance). Public is gated by cli/lib/license-gate.mjs: NC / no-redistribute / unconfirmed-license sets may not use the public tier. Champollion never hosts corpus PLAINTEXT in ANY tier. Defaults to the most private tier (local-only) when unspecified.",
       "default": "local-only"
     },
 
     "sealed": {
       "type": ["object", "null"],
-      "description": "Sealed-tier crypto metadata (exposureTier='sealed'). CONTENT-FREE: records how a community-controlled secret test set was encrypted client-side, never the plaintext. The ciphertext lives in an off-git, off-allowlist store; this block only names the cipher suite, the custodian group, the ciphertext digest, and the AAD binding, plus the paired public qualifier a method must clear before a sealed run can be proposed. The decryption key exists only as M-of-N custodian shares — Champollion cannot decrypt. See cli/lib/seal.mjs and docs/governance/OCAP_MULTISIG_PLAN.md (M1).",
+      "description": "Sealed-tier crypto metadata (exposureTier='sealed'). CONTENT-FREE: records how a community-controlled secret test set was encrypted client-side, never the plaintext. The ciphertext lives in an off-git, off-allowlist store; this block only names the cipher suite, the custodian group, the ciphertext digest, and the AAD binding, plus the paired public qualifier a method must clear before a sealed run can be proposed. The decryption key exists only as M-of-N custodian shares — Champollion cannot decrypt. See cli/lib/seal.mjs and the community-custodian multisig plan (docs/governance) (M1).",
       "required": ["cipher", "custodianGroupId", "ciphertextDigest", "aad"],
       "properties": {
         "cipher": {
@@ -782,7 +786,7 @@
           "type": "array",
           "items": {
             "type": "string",
-            "enum": ["OCAP", "CARE", "Te-Mana-Raraunga", "FAIR", "IEEE-2890"]
+            "enum": ["community-ownership-control", "CARE", "Te-Mana-Raraunga", "FAIR", "IEEE-2890"]
           },
           "description": "Data sovereignty frameworks that the data creators or governing body have explicitly invoked. Only list frameworks where there is documented evidence of adoption — do not infer from language vitality, geography, or ethnicity."
         },

package/shared/schemas/human-services.schema.json

@@ -69,7 +69,7 @@
         },
         "sovereignty_flags": {
           "type": ["object", "null"],
-          "description": "Data-handling constraints: off-community processing, attribution requirements, OCAP® notes. Free-form JSON."
+          "description": "Data-handling constraints: off-community processing, attribution requirements, data-sovereignty notes. Free-form JSON."
         },
         "nc_terms": {
           "type": ["string", "null"],
@@ -77,7 +77,7 @@
         },
         "consent_attested": {
           "type": "boolean",
-          "description": "OCAP® consent gate: the provider has explicitly consented to be listed. Public read requires this true."
+          "description": "Consent gate (community control of listing): the provider has explicitly consented to be listed. Public read requires this true."
         },
         "status": {
           "type": "string",

package/shared/schemas/language-card.schema.json

@@ -515,7 +515,7 @@
     },
     "taxonomyNotes": {
       "type": ["string", "null"],
-      "description": "Free-text affordance for known taxonomy disputes affecting this language: cases where ISO 639-3 and Glottolog disagree on splitting/lumping, contested language-vs-dialect status, or naming disputes. Policy (docs/LANGUAGE_TAXONOMY.md): display both authorities' positions, never adjudicate between them; communities name themselves (OCAP). Null when no dispute is documented — null means 'no note recorded', not 'no dispute exists'."
+      "description": "Free-text affordance for known taxonomy disputes affecting this language: cases where ISO 639-3 and Glottolog disagree on splitting/lumping, contested language-vs-dialect status, or naming disputes. Policy (docs/LANGUAGE_TAXONOMY.md): display both authorities' positions, never adjudicate between them; communities name themselves — community ownership and control of language data. Null when no dispute is documented — null means 'no note recorded', not 'no dispute exists'."
     },
     "classification": {
       "type": ["object", "null"],

package/shared/schemas/method-card.schema.json

@@ -389,7 +389,7 @@
           "type": "array",
           "items": {
             "type": "string",
-            "enum": ["OCAP", "CARE", "maori-data-sovereignty", "UNDRIP", "other"]
+            "enum": ["community-ownership-control", "CARE", "maori-data-sovereignty", "UNDRIP", "other"]
           },
           "description": "Data sovereignty frameworks this method respects."
         },