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
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
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
register_federation_keyfor CIRISProxy, done.Import shape (per imported claim)
A
scoresattestation ontruth_grounding:{subject}:epistemic_mode: derivative(relaying another source — NOT a direct witness)witness_relation: externalevidence_refs: [enwiki://{title}?oldid={R}, sha256:{content_hash}]context: "enwiki '{title}' rev {R} imported {T}"score/confidencemean "Wikipedia asserts this," NOT "this is true"transparency_log:inclusionanchor (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
holds_bytes) with lazy claim-extraction later. Do NOT block the corpus on an NLP extraction pipeline. (Extraction, when it runs, is itself aderivativeattestation "article X contains claim Y".)supersedeson the import claim → the CEG timeline natively renders edit history. Imports MUST carryoldidso supersession has a key.Dependencies
resolve_scores/list_scoresread surface + V106 subject projection) — in flight.What NOT to do (explicit)
derivative"Wikipedia asserts."🤖 Generated with Claude Code