Skip to content

Wikipedia/Wikimedia import pipeline — seed the KNOWLEDGE_COMMONS corpus as derivative attestations (NOT canonical authority) #5

Description

@emooreatx

Tracking issue for the CIRISProxy → KNOWLEDGE_COMMONS import pipeline. Design authority: FSD-005 §0.1 (CIRISConstitution/FSD/FSD-005_KNOWLEDGE_COMMONS.md).

The one rule that governs everything

Import Wikipedia's STATEMENTS, never Wikipedia's AUTHORITY. The accord/canonical trust root is NOT involved — blessing the import as canonical truth would rebuild the appeal-to-authority the whole system replaces, make one import key a corpus-wide capture point, and kill contestability (you can't render "Contradicted by: 12" against root-canonical content). CIRISProxy is just a registered federation key — an institutional attester, not a root.

What the trust root needs: nothing beyond CIRISProxy being a registered peer

  • No canonical/anchor ceremony. register_federation_key for CIRISProxy, done.
  • The import's trustworthiness rides on provenance + transparency-log, not root blessing.

Import shape (per imported claim)

A scores attestation on truth_grounding:{subject}:

  • epistemic_mode: derivative (relaying another source — NOT a direct witness)
  • witness_relation: external
  • evidence_refs: [enwiki://{title}?oldid={R}, sha256:{content_hash}]
  • context: "enwiki '{title}' rev {R} imported {T}"
  • score/confidence mean "Wikipedia asserts this," NOT "this is true"
  • a transparency_log:inclusion anchor (tamper-evident, auditable)

A freshly-imported-only claim therefore reads "attested by CIRISProxy (Wikipedia import), 1 source, derivative" — modest, single-source, honestly labelled. Real diversity accrues only as independent attesters engage; the UI must never render an import-only claim as high confidence.

Channel-trust, not content-trust (the only place trust attaches)

Optionally give CIRISProxy a partner_role / "faithful-relay" credential: consumers weight "faithfully relays a known source," never "the source is true."

Pipeline tasks

  • Register CIRISProxy federation key (institutional attester); optional faithful-relay credential.
  • Fetcher: MediaWiki API/dumps → (title, oldid, wikitext/HTML, content_hash, fetched_at).
  • Granularity split: hand-decompose the ~5 FSD flagship subjects into sentence-level claims (so the Evidence Panel + "show me why" demo lands); bulk-import everything else as article-blobs (holds_bytes) with lazy claim-extraction later. Do NOT block the corpus on an NLP extraction pipeline. (Extraction, when it runs, is itself a derivative attestation "article X contains claim Y".)
  • Revision-as-supersession: a later Wikipedia revision is a supersedes on the import claim → the CEG timeline natively renders edit history. Imports MUST carry oldid so supersession has a key.
  • Emit via the persist attestation write path; anchor each in the transparency log.
  • Licensing: CC BY-SA — attribution satisfied by construction (evidence_refs + provenance chain ARE the attribution); carry the SA notice on any derived/summary layer.
  • Scale = the substrate's first real load test. ~7M enwiki articles → that many Contributions + holds_bytes blobs + persist V106 projection rows. Start with a bounded slice (the flagship subjects + one category) before the full dump; coordinate with the persist v17.4.0 read-surface + commons-scale fountain/blob wiring.

Dependencies

  • Persist v17.4.0 (the resolve_scores/list_scores read surface + V106 subject projection) — in flight.
  • FSD-005 §0.1 / Appendix C (the read contract) — CIRISConstitution/FSD.

What NOT to do (explicit)

  • Do NOT route imports through the accord/canonical trust root.
  • Do NOT score imports as "true" — they are derivative "Wikipedia asserts."
  • Do NOT render import-only claims as high-confidence.
  • Do NOT make imported claims un-contestable.

🤖 Generated with Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions