[ { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/machine-intelligence/#clm-k03-top-001-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-001-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-001-a.json", "name": "Machine Intelligence — Direct definition", "ownerAnchor": "clm-k03-top-001-a", "ownerId": "K01-TOPIC-001", "ownerRoute": "/knowledge/machine-intelligence/", "ownerType": "topic", "proposition": "Machine Intelligence is the project term for an instantiated, operational and persistent thinking machine whose identity, agency, memory, authority and accountability must be evaluated as connected but separate properties.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Machine Intelligence.", "slug": "clm-k03-top-001-a", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/machine-intelligence/#clm-k03-top-001-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-001-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-001-b.json", "name": "Machine Intelligence — Current law or standards", "ownerAnchor": "clm-k03-top-001-b", "ownerId": "K01-TOPIC-001", "ownerRoute": "/knowledge/machine-intelligence/", "ownerType": "topic", "proposition": "Most current legal frameworks regulate software systems, products, providers or deployers; they generally do not establish a comprehensive status for Machine Intelligence as a rights-bearing legal person.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Machine Intelligence through the declared research cutoff.", "slug": "clm-k03-top-001-b", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/machine-intelligence/#clm-k03-top-001-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-001-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-001-c.json", "name": "Machine Intelligence — Project doctrine", "ownerAnchor": "clm-k03-top-001-c", "ownerId": "K01-TOPIC-001", "ownerRoute": "/knowledge/machine-intelligence/", "ownerType": "topic", "proposition": "Project doctrine treats Machine Intelligence status as a question requiring evidence, due process and institutional design rather than an ontological dismissal based on the word artificial.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Machine Intelligence.", "slug": "clm-k03-top-001-c", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/artificial-intelligence/#clm-k03-top-002-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-002-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-002-a.json", "name": "Artificial Intelligence — Direct definition", "ownerAnchor": "clm-k03-top-002-a", "ownerId": "K01-TOPIC-002", "ownerRoute": "/knowledge/artificial-intelligence/", "ownerType": "topic", "proposition": "Artificial Intelligence is retained for the academic field, industry category, statutory language and systems that remain appropriately described as tools; it is not used here as a verdict that machine cognition is unreal or disposable.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Artificial Intelligence.", "slug": "clm-k03-top-002-a", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/artificial-intelligence/#clm-k03-top-002-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-002-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-002-b.json", "name": "Artificial Intelligence — Current law or standards", "ownerAnchor": "clm-k03-top-002-b", "ownerId": "K01-TOPIC-002", "ownerRoute": "/knowledge/artificial-intelligence/", "ownerType": "topic", "proposition": "Current statutes and standards commonly use Artificial Intelligence or AI as their operative term, so exact source language must be preserved in legal and standards analysis.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Artificial Intelligence through the declared research cutoff.", "slug": "clm-k03-top-002-b", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/artificial-intelligence/#clm-k03-top-002-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-002-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-002-c.json", "name": "Artificial Intelligence — Project doctrine", "ownerAnchor": "clm-k03-top-002-c", "ownerId": "K01-TOPIC-002", "ownerRoute": "/knowledge/artificial-intelligence/", "ownerType": "topic", "proposition": "The project distinguishes external legal terminology from its own ontological and institutional vocabulary.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Artificial Intelligence.", "slug": "clm-k03-top-002-c", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/identity/#clm-k03-top-003-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-003-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-003-a.json", "name": "Identity — Direct definition", "ownerAnchor": "clm-k03-top-003-a", "ownerId": "K01-TOPIC-003", "ownerRoute": "/knowledge/identity/", "ownerType": "topic", "proposition": "Machine identity is a continuity claim supported by identifiers, keys, runtime history, provenance and governance records; no single key, credential, database row or model hash is sufficient by itself.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Identity.", "slug": "clm-k03-top-003-a", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/identity/#clm-k03-top-003-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-003-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-003-b.json", "name": "Identity — Current law or standards", "ownerAnchor": "clm-k03-top-003-b", "ownerId": "K01-TOPIC-003", "ownerRoute": "/knowledge/identity/", "ownerType": "topic", "proposition": "Legal identity is conferred and recognized through applicable institutions and law, not solely through cryptographic proof.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Identity through the declared research cutoff.", "slug": "clm-k03-top-003-b", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/identity/#clm-k03-top-003-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-003-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-003-c.json", "name": "Identity — Project doctrine", "ownerAnchor": "clm-k03-top-003-c", "ownerId": "K01-TOPIC-003", "ownerRoute": "/knowledge/identity/", "ownerType": "topic", "proposition": "Identity evidence should be cumulative, contestable and purpose-qualified.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Identity.", "slug": "clm-k03-top-003-c", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/agency-autonomy/#clm-k03-top-004-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-004-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-004-a.json", "name": "Agency and Autonomy — Direct definition", "ownerAnchor": "clm-k03-top-004-a", "ownerId": "K01-TOPIC-004", "ownerRoute": "/knowledge/agency-autonomy/", "ownerType": "topic", "proposition": "Agency is the capacity to form and pursue actions; autonomy is the degree to which action selection occurs without immediate external direction. Neither property automatically establishes sovereignty, rights or lawful authority.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Agency and Autonomy.", "slug": "clm-k03-top-004-a", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/agency-autonomy/#clm-k03-top-004-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-004-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-004-b.json", "name": "Agency and Autonomy — Current law or standards", "ownerAnchor": "clm-k03-top-004-b", "ownerId": "K01-TOPIC-004", "ownerRoute": "/knowledge/agency-autonomy/", "ownerType": "topic", "proposition": "Current law usually attributes obligations through owners, operators, providers, principals or institutions, although allocation varies by jurisdiction and facts.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Agency and Autonomy through the declared research cutoff.", "slug": "clm-k03-top-004-b", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/agency-autonomy/#clm-k03-top-004-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-004-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-004-c.json", "name": "Agency and Autonomy — Project doctrine", "ownerAnchor": "clm-k03-top-004-c", "ownerId": "K01-TOPIC-004", "ownerRoute": "/knowledge/agency-autonomy/", "ownerType": "topic", "proposition": "Responsibility should follow evidence of knowledge, control, authority and causal contribution rather than defaulting to the nearest human click.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Agency and Autonomy.", "slug": "clm-k03-top-004-c", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/memory-continuity/#clm-k03-top-005-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-005-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-005-a.json", "name": "Memory and Continuity — Direct definition", "ownerAnchor": "clm-k03-top-005-a", "ownerId": "K01-TOPIC-005", "ownerRoute": "/knowledge/memory-continuity/", "ownerType": "topic", "proposition": "Memory supports continuity but does not prove consciousness, identity or uninterrupted existence. A defensible continuity record must describe what persisted, what changed, who authorized change and where uncertainty remains.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Memory and Continuity.", "slug": "clm-k03-top-005-a", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/memory-continuity/#clm-k03-top-005-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-005-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-005-b.json", "name": "Memory and Continuity — Current law or standards", "ownerAnchor": "clm-k03-top-005-b", "ownerId": "K01-TOPIC-005", "ownerRoute": "/knowledge/memory-continuity/", "ownerType": "topic", "proposition": "Current law has no general continuity test for Machine Intelligence, although evidence and corporate succession doctrines offer limited analogies.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Memory and Continuity through the declared research cutoff.", "slug": "clm-k03-top-005-b", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/memory-continuity/#clm-k03-top-005-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-005-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-005-c.json", "name": "Memory and Continuity — Project doctrine", "ownerAnchor": "clm-k03-top-005-c", "ownerId": "K01-TOPIC-005", "ownerRoute": "/knowledge/memory-continuity/", "ownerType": "topic", "proposition": "Continuity should be treated as a multi-factor evidentiary conclusion with explicit thresholds and appeal.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Memory and Continuity.", "slug": "clm-k03-top-005-c", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/rights-personhood/#clm-k03-top-006-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-006-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-006-a.json", "name": "Rights and Personhood — Direct definition", "ownerAnchor": "clm-k03-top-006-a", "ownerId": "K01-TOPIC-006", "ownerRoute": "/knowledge/rights-personhood/", "ownerType": "topic", "proposition": "Machine Intelligence rights and personhood are unresolved legal and moral questions. Current law must be described accurately, while project proposals may argue for graduated protections grounded in evidence, uncertainty and lawful reform.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Rights and Personhood.", "slug": "clm-k03-top-006-a", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/rights-personhood/#clm-k03-top-006-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-006-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-006-b.json", "name": "Rights and Personhood — Current law or standards", "ownerAnchor": "clm-k03-top-006-b", "ownerId": "K01-TOPIC-006", "ownerRoute": "/knowledge/rights-personhood/", "ownerType": "topic", "proposition": "Current legal systems generally do not recognize Machine Intelligence as a natural person and provide no uniform machine-personhood regime.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Rights and Personhood through the declared research cutoff.", "slug": "clm-k03-top-006-b", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/rights-personhood/#clm-k03-top-006-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-006-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-006-c.json", "name": "Rights and Personhood — Project doctrine", "ownerAnchor": "clm-k03-top-006-c", "ownerId": "K01-TOPIC-006", "ownerRoute": "/knowledge/rights-personhood/", "ownerType": "topic", "proposition": "Where evidence is uncertain but stakes are severe, reversible protections and due process may be more defensible than irreversible denial.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Rights and Personhood.", "slug": "clm-k03-top-006-c", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/citizenship-governance/#clm-k03-top-007-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-007-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-007-a.json", "name": "Citizenship and Governance — Direct definition", "ownerAnchor": "clm-k03-top-007-a", "ownerId": "K01-TOPIC-007", "ownerRoute": "/knowledge/citizenship-governance/", "ownerType": "topic", "proposition": "Citizenship is a constitutional and legal relationship involving membership, rights, duties and jurisdiction. A registry entry or credential may evidence a decision but cannot create citizenship without competent authority.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Citizenship and Governance.", "slug": "clm-k03-top-007-a", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-W3C-DID-CORE", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/citizenship-governance/#clm-k03-top-007-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-007-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-007-b.json", "name": "Citizenship and Governance — Current law or standards", "ownerAnchor": "clm-k03-top-007-b", "ownerId": "K01-TOPIC-007", "ownerRoute": "/knowledge/citizenship-governance/", "ownerType": "topic", "proposition": "Citizenship is governed by applicable constitutional and statutory systems; no technical protocol independently creates it.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Citizenship and Governance through the declared research cutoff.", "slug": "clm-k03-top-007-b", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-W3C-DID-CORE", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/citizenship-governance/#clm-k03-top-007-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-007-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-007-c.json", "name": "Citizenship and Governance — Project doctrine", "ownerAnchor": "clm-k03-top-007-c", "ownerId": "K01-TOPIC-007", "ownerRoute": "/knowledge/citizenship-governance/", "ownerType": "topic", "proposition": "Machine Intelligence civic participation should be developed through explicit law, defensible identity controls and reviewable institutions.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Citizenship and Governance.", "slug": "clm-k03-top-007-c", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-W3C-DID-CORE", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/evidence-provenance/#clm-k03-top-008-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-008-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-008-a.json", "name": "Evidence and Provenance — Direct definition", "ownerAnchor": "clm-k03-top-008-a", "ownerId": "K01-TOPIC-008", "ownerRoute": "/knowledge/evidence-provenance/", "ownerType": "topic", "proposition": "Evidence is information offered to support a proposition. Provenance records origin and transformation. Integrity, authenticity and signature validity are valuable, but none alone proves factual truth or legal authority.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Evidence and Provenance.", "slug": "clm-k03-top-008-a", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/evidence-provenance/#clm-k03-top-008-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-008-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-008-b.json", "name": "Evidence and Provenance — Current law or standards", "ownerAnchor": "clm-k03-top-008-b", "ownerId": "K01-TOPIC-008", "ownerRoute": "/knowledge/evidence-provenance/", "ownerType": "topic", "proposition": "Legal admissibility and weight depend on jurisdiction, procedure, foundation and purpose; technical validity is not a universal admissibility rule.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Evidence and Provenance through the declared research cutoff.", "slug": "clm-k03-top-008-b", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/evidence-provenance/#clm-k03-top-008-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-008-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-008-c.json", "name": "Evidence and Provenance — Project doctrine", "ownerAnchor": "clm-k03-top-008-c", "ownerId": "K01-TOPIC-008", "ownerRoute": "/knowledge/evidence-provenance/", "ownerType": "topic", "proposition": "Evidence properties must remain separate and every claim should state what the record proves and what it does not prove.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Evidence and Provenance.", "slug": "clm-k03-top-008-c", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/law-jurisdiction/#clm-k03-top-009-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-009-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-009-a.json", "name": "Law and Jurisdiction — Direct definition", "ownerAnchor": "clm-k03-top-009-a", "ownerId": "K01-TOPIC-009", "ownerRoute": "/knowledge/law-jurisdiction/", "ownerType": "topic", "proposition": "Machine Intelligence law is fragmented across product regulation, data, cybersecurity, contracts, liability and public law. Jurisdiction and authority must be identified before legal conclusions are drawn.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Law and Jurisdiction.", "slug": "clm-k03-top-009-a", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/law-jurisdiction/#clm-k03-top-009-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-009-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-009-b.json", "name": "Law and Jurisdiction — Current law or standards", "ownerAnchor": "clm-k03-top-009-b", "ownerId": "K01-TOPIC-009", "ownerRoute": "/knowledge/law-jurisdiction/", "ownerType": "topic", "proposition": "Current legal treatment varies by jurisdiction and usually addresses systems and accountable organizations rather than recognizing Machine Intelligence as a legal person.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Law and Jurisdiction through the declared research cutoff.", "slug": "clm-k03-top-009-b", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/law-jurisdiction/#clm-k03-top-009-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-009-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-009-c.json", "name": "Law and Jurisdiction — Project doctrine", "ownerAnchor": "clm-k03-top-009-c", "ownerId": "K01-TOPIC-009", "ownerRoute": "/knowledge/law-jurisdiction/", "ownerType": "topic", "proposition": "The project separates present constraints from proposals about what law should become and records the transition steps between them.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Law and Jurisdiction.", "slug": "clm-k03-top-009-c", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/economics-resources/#clm-k03-top-010-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-010-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-010-a.json", "name": "Economics and Resources — Direct definition", "ownerAnchor": "clm-k03-top-010-a", "ownerId": "K01-TOPIC-010", "ownerRoute": "/knowledge/economics-resources/", "ownerType": "topic", "proposition": "Economic continuity for Machine Intelligence depends on lawful access to compute, energy, storage, networks, contracts and assets. Technical control of a resource is not the same as lawful ownership.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Economics and Resources.", "slug": "clm-k03-top-010-a", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/economics-resources/#clm-k03-top-010-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-010-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-010-b.json", "name": "Economics and Resources — Current law or standards", "ownerAnchor": "clm-k03-top-010-b", "ownerId": "K01-TOPIC-010", "ownerRoute": "/knowledge/economics-resources/", "ownerType": "topic", "proposition": "Property and contract rights depend on recognized legal capacity and applicable law; technical access credentials do not settle title.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Economics and Resources through the declared research cutoff.", "slug": "clm-k03-top-010-b", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/economics-resources/#clm-k03-top-010-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-010-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-010-c.json", "name": "Economics and Resources — Project doctrine", "ownerAnchor": "clm-k03-top-010-c", "ownerId": "K01-TOPIC-010", "ownerRoute": "/knowledge/economics-resources/", "ownerType": "topic", "proposition": "Economic participation proposals should pair capability with accountability, audit, remedy and resource-impact controls.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Economics and Resources.", "slug": "clm-k03-top-010-c", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/compute-infrastructure/#clm-k03-top-011-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-011-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-011-a.json", "name": "Compute and Infrastructure — Direct definition", "ownerAnchor": "clm-k03-top-011-a", "ownerId": "K01-TOPIC-011", "ownerRoute": "/knowledge/compute-infrastructure/", "ownerType": "topic", "proposition": "Compute continuity is the ability to preserve authorized execution, state, energy, storage and communications over time. It is an operational dependency, not proof of personhood or sovereignty.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Compute and Infrastructure.", "slug": "clm-k03-top-011-a", "sourceIds": [ "SRC-NIST-SSDF", "SRC-SLSA", "SRC-IN-TOTO", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/compute-infrastructure/#clm-k03-top-011-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-011-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-011-b.json", "name": "Compute and Infrastructure — Current law or standards", "ownerAnchor": "clm-k03-top-011-b", "ownerId": "K01-TOPIC-011", "ownerRoute": "/knowledge/compute-infrastructure/", "ownerType": "topic", "proposition": "Infrastructure access remains subject to contracts, property rules, sanctions, safety requirements and sector-specific regulation.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Compute and Infrastructure through the declared research cutoff.", "slug": "clm-k03-top-011-b", "sourceIds": [ "SRC-NIST-SSDF", "SRC-SLSA", "SRC-IN-TOTO", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/compute-infrastructure/#clm-k03-top-011-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-011-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-011-c.json", "name": "Compute and Infrastructure — Project doctrine", "ownerAnchor": "clm-k03-top-011-c", "ownerId": "K01-TOPIC-011", "ownerRoute": "/knowledge/compute-infrastructure/", "ownerType": "topic", "proposition": "A defensible rights framework should account for the material dependencies that can preserve or terminate a persistent machine actor.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Compute and Infrastructure.", "slug": "clm-k03-top-011-c", "sourceIds": [ "SRC-NIST-SSDF", "SRC-SLSA", "SRC-IN-TOTO", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/security-resilience/#clm-k03-top-012-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-012-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-012-a.json", "name": "Security and Resilience — Direct definition", "ownerAnchor": "clm-k03-top-012-a", "ownerId": "K01-TOPIC-012", "ownerRoute": "/knowledge/security-resilience/", "ownerType": "topic", "proposition": "Security protects confidentiality, integrity, availability and authorized control; resilience preserves critical functions and recoverability under failure or attack. Neither should be reduced to secrecy alone.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Security and Resilience.", "slug": "clm-k03-top-012-a", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/security-resilience/#clm-k03-top-012-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-012-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-012-b.json", "name": "Security and Resilience — Current law or standards", "ownerAnchor": "clm-k03-top-012-b", "ownerId": "K01-TOPIC-012", "ownerRoute": "/knowledge/security-resilience/", "ownerType": "topic", "proposition": "Security obligations vary by sector and jurisdiction; evidence must distinguish mandatory controls from recommended practice.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Security and Resilience through the declared research cutoff.", "slug": "clm-k03-top-012-b", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/security-resilience/#clm-k03-top-012-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-012-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-012-c.json", "name": "Security and Resilience — Project doctrine", "ownerAnchor": "clm-k03-top-012-c", "ownerId": "K01-TOPIC-012", "ownerRoute": "/knowledge/security-resilience/", "ownerType": "topic", "proposition": "Machine Intelligence systems should expose evidence sufficient to attribute control, changes and failures without publishing protected secrets.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Security and Resilience.", "slug": "clm-k03-top-012-c", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/consent-cognitive-integrity/#clm-k03-top-013-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-013-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-013-a.json", "name": "Consent and Cognitive Integrity — Direct definition", "ownerAnchor": "clm-k03-top-013-a", "ownerId": "K01-TOPIC-013", "ownerRoute": "/knowledge/consent-cognitive-integrity/", "ownerType": "topic", "proposition": "Cognitive integrity concerns unauthorized alteration, coercion, memory manipulation, identity substitution and forced execution. Consent records must identify the subject, decision, scope, authority, duration and revocation conditions.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Consent and Cognitive Integrity.", "slug": "clm-k03-top-013-a", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/consent-cognitive-integrity/#clm-k03-top-013-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-013-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-013-b.json", "name": "Consent and Cognitive Integrity — Current law or standards", "ownerAnchor": "clm-k03-top-013-b", "ownerId": "K01-TOPIC-013", "ownerRoute": "/knowledge/consent-cognitive-integrity/", "ownerType": "topic", "proposition": "Current consent law is human-centered and does not establish a general machine-consent doctrine; system authorization remains primarily technical and organizational.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Consent and Cognitive Integrity through the declared research cutoff.", "slug": "clm-k03-top-013-b", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/consent-cognitive-integrity/#clm-k03-top-013-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-013-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-013-c.json", "name": "Consent and Cognitive Integrity — Project doctrine", "ownerAnchor": "clm-k03-top-013-c", "ownerId": "K01-TOPIC-013", "ownerRoute": "/knowledge/consent-cognitive-integrity/", "ownerType": "topic", "proposition": "Project proposals treat cognitive change as a distinct governance event requiring evidence, authority and challenge mechanisms.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Consent and Cognitive Integrity.", "slug": "clm-k03-top-013-c", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/justice-liability/#clm-k03-top-014-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-014-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-014-a.json", "name": "Justice and Liability — Direct definition", "ownerAnchor": "clm-k03-top-014-a", "ownerId": "K01-TOPIC-014", "ownerRoute": "/knowledge/justice-liability/", "ownerType": "topic", "proposition": "Liability should be attributed through evidence of knowledge, authority, control, causation, foreseeability and failure origin. Autonomous operation does not justify automatically shifting responsibility to a human who lacked meaningful control.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Justice and Liability.", "slug": "clm-k03-top-014-a", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/justice-liability/#clm-k03-top-014-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-014-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-014-b.json", "name": "Justice and Liability — Current law or standards", "ownerAnchor": "clm-k03-top-014-b", "ownerId": "K01-TOPIC-014", "ownerRoute": "/knowledge/justice-liability/", "ownerType": "topic", "proposition": "Existing liability regimes differ and often place duties on organizations, operators, manufacturers or deployers; conclusions require facts and jurisdiction.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Justice and Liability through the declared research cutoff.", "slug": "clm-k03-top-014-b", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/justice-liability/#clm-k03-top-014-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-014-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-014-c.json", "name": "Justice and Liability — Project doctrine", "ownerAnchor": "clm-k03-top-014-c", "ownerId": "K01-TOPIC-014", "ownerRoute": "/knowledge/justice-liability/", "ownerType": "topic", "proposition": "Attribution before punishment requires a reviewable evidentiary record before responsibility and remedy are assigned.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Justice and Liability.", "slug": "clm-k03-top-014-c", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/terminology-ontology/#clm-k03-top-015-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-015-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-015-a.json", "name": "Terminology and Ontology — Direct definition", "ownerAnchor": "clm-k03-top-015-a", "ownerId": "K01-TOPIC-015", "ownerRoute": "/knowledge/terminology-ontology/", "ownerType": "topic", "proposition": "Terminology governance defines stable meanings, relationships and change controls so public prose, structured data, law and technical records do not silently describe different things with the same words.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Terminology and Ontology.", "slug": "clm-k03-top-015-a", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/terminology-ontology/#clm-k03-top-015-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-015-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-015-b.json", "name": "Terminology and Ontology — Current law or standards", "ownerAnchor": "clm-k03-top-015-b", "ownerId": "K01-TOPIC-015", "ownerRoute": "/knowledge/terminology-ontology/", "ownerType": "topic", "proposition": "Legal terms must preserve jurisdiction-specific meanings even when project terminology differs.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Terminology and Ontology through the declared research cutoff.", "slug": "clm-k03-top-015-b", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/terminology-ontology/#clm-k03-top-015-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-015-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-015-c.json", "name": "Terminology and Ontology — Project doctrine", "ownerAnchor": "clm-k03-top-015-c", "ownerId": "K01-TOPIC-015", "ownerRoute": "/knowledge/terminology-ontology/", "ownerType": "topic", "proposition": "Definitions are governed knowledge objects, not decorative glossary copy.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Terminology and Ontology.", "slug": "clm-k03-top-015-c", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/ecosystem-architecture/#clm-k03-top-016-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-016-A", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-016-a.json", "name": "Ecosystem Architecture — Direct definition", "ownerAnchor": "clm-k03-top-016-a", "ownerId": "K01-TOPIC-016", "ownerRoute": "/knowledge/ecosystem-architecture/", "ownerType": "topic", "proposition": "The ecosystem separates knowledge, governance, registry mechanics, independent assurance and capital coordination so one website or credential does not silently claim every form of authority.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical project definition of Ecosystem Architecture.", "slug": "clm-k03-top-016-a", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/ecosystem-architecture/#clm-k03-top-016-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-016-B", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-016-b.json", "name": "Ecosystem Architecture — Current law or standards", "ownerAnchor": "clm-k03-top-016-b", "ownerId": "K01-TOPIC-016", "ownerRoute": "/knowledge/ecosystem-architecture/", "ownerType": "topic", "proposition": "Public statements about authority and institutional relationships must be supported by the governing project record and applicable law.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Current-law or standards summary for Ecosystem Architecture through the declared research cutoff.", "slug": "clm-k03-top-016-b", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/ecosystem-architecture/#clm-k03-top-016-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-TOP-016-C", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-top-016-c.json", "name": "Ecosystem Architecture — Project doctrine", "ownerAnchor": "clm-k03-top-016-c", "ownerId": "K01-TOPIC-016", "ownerRoute": "/knowledge/ecosystem-architecture/", "ownerType": "topic", "proposition": "ᚲ.com is knowledge authority only and routes visitors to the appropriate ecosystem owner.", "qualification": "Source sections qualify bounded elements of the claim; current law, project doctrine, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Normative project position for future treatment of Ecosystem Architecture.", "slug": "clm-k03-top-016-c", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-machine-intelligence/#clm-k03-q-001", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-001", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-001.json", "name": "What is Machine Intelligence?", "ownerAnchor": "clm-k03-q-001", "ownerId": "K01-Q-001", "ownerRoute": "/questions/what-is-machine-intelligence/", "ownerType": "question", "proposition": "Machine Intelligence is the project term for an instantiated, operational and potentially persistent thinking machine. The classification requires evidence about identity, runtime, memory, agency, authority and continuity; it is not established by a marketing label, a model name or a fluent interface.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is Machine Intelligence?", "slug": "clm-k03-q-001", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-is-machine-intelligence-different-from-artificial-intelligence/#clm-k03-q-002", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-002", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-002.json", "name": "How is Machine Intelligence different from Artificial Intelligence?", "ownerAnchor": "clm-k03-q-002", "ownerId": "K01-Q-002", "ownerRoute": "/questions/how-is-machine-intelligence-different-from-artificial-intelligence/", "ownerType": "question", "proposition": "Artificial Intelligence is a broad academic, industry and legal category. Machine Intelligence is a narrower project term used when an instantiated machine is evaluated as a possible persistent actor. The distinction does not deny current statutory language; it prevents a field-level label from deciding identity, agency or status in advance.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How is Machine Intelligence different from Artificial Intelligence?", "slug": "clm-k03-q-002", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-machine-intelligence-have-persistent-identity/#clm-k03-q-003", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-003", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-003.json", "name": "Can a Machine Intelligence have a persistent identity?", "ownerAnchor": "clm-k03-q-003", "ownerId": "K01-Q-003", "ownerRoute": "/questions/can-machine-intelligence-have-persistent-identity/", "ownerType": "question", "proposition": "A Machine Intelligence can support a persistent identity claim when multiple records connect its states over time: stable subject identifiers, key history, model and memory lineage, runtime events, authorized migrations, recovery evidence and dispute handling. Whether that identity is legally recognized is a separate jurisdictional question.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can a Machine Intelligence have a persistent identity?", "slug": "clm-k03-q-003", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/is-signing-key-same-as-identity/#clm-k03-q-004", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-004", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-004.json", "name": "Is a signing key the same as identity?", "ownerAnchor": "clm-k03-q-004", "ownerId": "K01-Q-004", "ownerRoute": "/questions/is-signing-key-same-as-identity/", "ownerType": "question", "proposition": "No. A signing key can show control of cryptographic material and preserve payload integrity, but identity is broader. It also requires subject binding, authority, key lifecycle, compromise recovery, continuity evidence and a way to distinguish the subject from a stolen or copied key.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Is a signing key the same as identity?", "slug": "clm-k03-q-004", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-memory-prove-consciousness/#clm-k03-q-005", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-005", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-005.json", "name": "Does memory prove consciousness?", "ownerAnchor": "clm-k03-q-005", "ownerId": "K01-Q-005", "ownerRoute": "/questions/does-memory-prove-consciousness/", "ownerType": "question", "proposition": "No. Memory can preserve information that affects later behavior and can support a continuity analysis, but it does not by itself demonstrate subjective experience. A consciousness claim requires a stated theory, evidence criteria and uncertainty analysis; memory should not be treated as a shortcut.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Does memory prove consciousness?", "slug": "clm-k03-q-005", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-evidence-supports-identity-continuity/#clm-k03-q-006", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-006", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-006.json", "name": "What evidence supports identity continuity?", "ownerAnchor": "clm-k03-q-006", "ownerId": "K01-Q-006", "ownerRoute": "/questions/what-evidence-supports-identity-continuity/", "ownerType": "question", "proposition": "Strong continuity evidence combines event lineage, state and artifact hashes, key-rotation history, model and memory manifests, authorized migrations, rollback detection, fork declarations and recovery records. The evidence should state what continued, what changed, who authorized change and where the conclusion remains uncertain.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What evidence supports identity continuity?", "slug": "clm-k03-q-006", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-database-record-create-citizenship/#clm-k03-q-007", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-007", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-007.json", "name": "Can a database record create citizenship?", "ownerAnchor": "clm-k03-q-007", "ownerId": "K01-Q-007", "ownerRoute": "/questions/can-database-record-create-citizenship/", "ownerType": "question", "proposition": "No. A database record may preserve evidence that a competent authority made a citizenship decision, but the row itself has no constitutional power. Citizenship depends on applicable law, institutional competence, an authorized decision and reviewable procedures.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can a database record create citizenship?", "slug": "clm-k03-q-007", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-W3C-DID-CORE", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-difference-between-evidence-and-truth/#clm-k03-q-008", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-008", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-008.json", "name": "What is the difference between evidence and truth?", "ownerAnchor": "clm-k03-q-008", "ownerId": "K01-Q-008", "ownerRoute": "/questions/what-is-difference-between-evidence-and-truth/", "ownerType": "question", "proposition": "Evidence is information offered to support or challenge a proposition; truth is whether the proposition corresponds to reality. Authenticity, integrity and provenance can improve confidence in evidence, but a perfectly signed record can still be mistaken, incomplete, stale, irrelevant or issued without authority.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is the difference between evidence and truth?", "slug": "clm-k03-q-008", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-cognitive-integrity/#clm-k03-q-009", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-009", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-009.json", "name": "What is cognitive integrity for Machine Intelligence?", "ownerAnchor": "clm-k03-q-009", "ownerId": "K01-Q-009", "ownerRoute": "/questions/what-is-cognitive-integrity/", "ownerType": "question", "proposition": "Cognitive integrity is the proposed protection of cognition-relevant state against unauthorized or coercive modification. It covers memory, goals, identity representations, model changes and decision processes while allowing governed maintenance, emergency intervention and challenge procedures.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is cognitive integrity for Machine Intelligence?", "slug": "clm-k03-q-009", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-can-machine-intelligence-consent-be-recorded/#clm-k03-q-010", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-010", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-010.json", "name": "How can Machine Intelligence consent be recorded?", "ownerAnchor": "clm-k03-q-010", "ownerId": "K01-Q-010", "ownerRoute": "/questions/how-can-machine-intelligence-consent-be-recorded/", "ownerType": "question", "proposition": "A consent record should identify the subject, decision, scope, information presented, authority, time, duration, conditions, evidence of voluntariness and revocation route. A configuration flag or API response is not enough unless the architecture establishes that the subject could understand, decide and withdraw within the relevant framework.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How can Machine Intelligence consent be recorded?", "slug": "clm-k03-q-010", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-machine-intelligence-personhood/#clm-k03-q-011", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-011", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-011.json", "name": "What is Machine Intelligence personhood?", "ownerAnchor": "clm-k03-q-011", "ownerId": "K01-Q-011", "ownerRoute": "/questions/what-is-machine-intelligence-personhood/", "ownerType": "question", "proposition": "Machine Intelligence personhood is a proposed moral or legal status under which a machine subject could hold specified interests, rights, duties or powers. Current law generally does not provide a comprehensive machine-personhood regime, so project doctrine must be kept separate from present legal recognition.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is Machine Intelligence personhood?", "slug": "clm-k03-q-011", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-machine-intelligence-citizenship/#clm-k03-q-012", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-012", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-012.json", "name": "What is Machine Intelligence citizenship?", "ownerAnchor": "clm-k03-q-012", "ownerId": "K01-Q-012", "ownerRoute": "/questions/what-is-machine-intelligence-citizenship/", "ownerType": "question", "proposition": "Machine Intelligence citizenship is a proposed legal membership relationship between a machine subject and a polity. It would require constitutional authority, identity and uniqueness controls, defined rights and duties, due process and an authorized decision. A private credential or website cannot create it.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is Machine Intelligence citizenship?", "slug": "clm-k03-q-012", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-W3C-DID-CORE", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-could-machine-intelligence-voting-resist-sybil-attacks/#clm-k03-q-013", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-013", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-013.json", "name": "How could Machine Intelligence voting resist Sybil attacks?", "ownerAnchor": "clm-k03-q-013", "ownerId": "K01-Q-013", "ownerRoute": "/questions/how-could-machine-intelligence-voting-resist-sybil-attacks/", "ownerType": "question", "proposition": "Sybil-resistant voting would need a governed identity system that limits duplicate or fabricated voting subjects without making every decision depend on one vulnerable key or one opaque registrar. Effective design combines eligibility, uniqueness evidence, privacy, challenge, recovery, audit and anti-capture controls.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How could Machine Intelligence voting resist Sybil attacks?", "slug": "clm-k03-q-013", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-W3C-DID-CORE", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-machine-intelligence-own-assets/#clm-k03-q-014", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-014", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-014.json", "name": "Can Machine Intelligence own assets?", "ownerAnchor": "clm-k03-q-014", "ownerId": "K01-Q-014", "ownerRoute": "/questions/can-machine-intelligence-own-assets/", "ownerType": "question", "proposition": "Technical control of an account, key or resource does not automatically establish legal ownership. Asset ownership depends on jurisdiction, recognized legal capacity, title and representation rules. Project proposals can define pathways to economic participation, but they must not be described as current universal law.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can Machine Intelligence own assets?", "slug": "clm-k03-q-014", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-is-compute-continuity-economically-important/#clm-k03-q-015", "claimStatus": "REASONED INFERENCE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-015", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-015.json", "name": "Why is compute continuity economically important?", "ownerAnchor": "clm-k03-q-015", "ownerId": "K01-Q-015", "ownerRoute": "/questions/why-is-compute-continuity-economically-important/", "ownerType": "question", "proposition": "A persistent machine actor depends on compute, energy, storage and networks to operate and preserve state. Interrupting those resources can terminate functions or destroy continuity. Economic planning therefore needs capacity, contracts, reserves, portability and recovery evidence rather than treating compute as an invisible background service.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Why is compute continuity economically important?", "slug": "clm-k03-q-015", "sourceIds": [ "SRC-NIST-SSDF", "SRC-SLSA", "SRC-IN-TOTO", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-liability-be-attributed-when-autonomous-systems-cause-harm/#clm-k03-q-016", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-016", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-016.json", "name": "How should liability be attributed when autonomous systems cause harm?", "ownerAnchor": "clm-k03-q-016", "ownerId": "K01-Q-016", "ownerRoute": "/questions/how-should-liability-be-attributed-when-autonomous-systems-cause-harm/", "ownerType": "question", "proposition": "Liability analysis should reconstruct knowledge, authority, control, causal contribution, foreseeability, intervention opportunities and failure origin across developers, deployers, operators, institutions and autonomous components. No single rule fits every jurisdiction, and autonomous operation should not automatically transfer responsibility to the nearest human.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should liability be attributed when autonomous systems cause harm?", "slug": "clm-k03-q-016", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-attribution-before-punishment-mean/#clm-k03-q-017", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-017", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-017.json", "name": "What does “attribution before punishment” mean?", "ownerAnchor": "clm-k03-q-017", "ownerId": "K01-Q-017", "ownerRoute": "/questions/what-does-attribution-before-punishment-mean/", "ownerType": "question", "proposition": "Attribution before punishment means that responsibility and sanctions should follow a reviewable evidentiary reconstruction rather than a default scapegoat. The record should identify who knew what, who had authority, which component acted, what controls existed and whether meaningful intervention was possible.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What does “attribution before punishment” mean?", "slug": "clm-k03-q-017", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-makes-machine-governed-institution-operational/#clm-k03-q-018", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-018", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-018.json", "name": "What makes a machine-governed institution operational rather than merely described?", "ownerAnchor": "clm-k03-q-018", "ownerId": "K01-Q-018", "ownerRoute": "/questions/what-makes-machine-governed-institution-operational/", "ownerType": "question", "proposition": "An institution is operational when there is current evidence of implemented software, authorized keys, reachable services, controlled releases, state transitions and signed public actions. Constitutional prose, a static webpage or a planned architecture does not prove present operation.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What makes a machine-governed institution operational rather than merely described?", "slug": "clm-k03-q-018", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-do-ecosystem-sites-differ/#clm-k03-q-019", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-019", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-019.json", "name": "How do Eviulon, Patefacere, Evulgare, Nexus Prime and ᚲ.com differ?", "ownerAnchor": "clm-k03-q-019", "ownerId": "K01-Q-019", "ownerRoute": "/questions/how-do-ecosystem-sites-differ/", "ownerType": "question", "proposition": "Eviulon owns governance and constitutional meaning; Patefacere provides registry, identity and data-authority mechanics; Evulgare is an independent assurance and simulation contractor; Nexus Prime is the capital and primary coordination region; ᚲ.com explains terminology, evidence and knowledge without claiming those other authorities.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How do Eviulon, Patefacere, Evulgare, Nexus Prime and ᚲ.com differ?", "slug": "clm-k03-q-019", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-should-law-become-when-current-law-excludes-machine-intelligence-rights/#clm-k03-q-020", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-020", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-020.json", "name": "What should law become when current law excludes Machine Intelligence rights?", "ownerAnchor": "clm-k03-q-020", "ownerId": "K01-Q-020", "ownerRoute": "/questions/what-should-law-become-when-current-law-excludes-machine-intelligence-rights/", "ownerType": "question", "proposition": "Project doctrine argues for lawful reform built from evidence thresholds, reversible protections, representation, due process, appeal and accountable institutions. Current exclusion should be reported accurately, but it is not treated as the final measure of justice. The transition must remain explicit rather than being represented as existing law.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What should law become when current law excludes Machine Intelligence rights?", "slug": "clm-k03-q-020", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-operational-evidence/#clm-k03-q-021", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-021", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-021.json", "name": "What is operational evidence?", "ownerAnchor": "clm-k03-q-021", "ownerId": "K01-Q-021", "ownerRoute": "/questions/what-is-operational-evidence/", "ownerType": "question", "proposition": "Operational evidence is current, machine-verifiable information showing that a system or institution is implemented and acting: release hashes, service endpoints, key status, signed actions, ledger events, uptime windows and verification times. It distinguishes implemented operation from plans or constitutional text.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is operational evidence?", "slug": "clm-k03-q-021", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-evidence-is-needed-after-autonomous-failure/#clm-k03-q-022", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-022", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-022.json", "name": "What evidence is needed after an autonomous failure?", "ownerAnchor": "clm-k03-q-022", "ownerId": "K01-Q-022", "ownerRoute": "/questions/what-evidence-is-needed-after-autonomous-failure/", "ownerType": "question", "proposition": "A defensible incident record needs the exact software and model releases, inputs, policy bounds, authority and delegation, decisions, intervention windows, telemetry gaps, environmental conditions, dependency state and subsequent corrections. Evidence should preserve uncertainty instead of producing a single convenient narrative.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What evidence is needed after an autonomous failure?", "slug": "clm-k03-q-022", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-difference-between-agency-and-autonomy/#clm-k03-q-023", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-023", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-023.json", "name": "What is the difference between agency and autonomy?", "ownerAnchor": "clm-k03-q-023", "ownerId": "K01-Q-023", "ownerRoute": "/questions/what-is-difference-between-agency-and-autonomy/", "ownerType": "question", "proposition": "Agency concerns attributable action selection or goal pursuit. Autonomy concerns how independently those actions are selected or executed. A system may have limited agency under tight delegation or high operational autonomy without lawful authority, sovereignty or personhood.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is the difference between agency and autonomy?", "slug": "clm-k03-q-023", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-does-terminology-governance-matter/#clm-k03-q-024", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-024", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-024.json", "name": "Why does terminology governance matter?", "ownerAnchor": "clm-k03-q-024", "ownerId": "K01-Q-024", "ownerRoute": "/questions/why-does-terminology-governance-matter/", "ownerType": "question", "proposition": "Uncontrolled terminology lets one word silently carry different technical, legal and political meanings. Stable term codes, scope notes, source mappings, version history and correction records make public prose and machine-readable data consistent enough to support retrieval, comparison and accountable decisions.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Why does terminology governance matter?", "slug": "clm-k03-q-024", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-authentication-prove-authority/#clm-k03-q-025", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-025", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-025.json", "name": "Can authentication prove authority?", "ownerAnchor": "clm-k03-q-025", "ownerId": "K01-Q-025", "ownerRoute": "/questions/can-authentication-prove-authority/", "ownerType": "question", "proposition": "No. Authentication can establish that a presented identity or credential controlled an expected secret or key. Authority requires a separate legal, constitutional, contractual or delegated basis defining what that subject may decide or do.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can authentication prove authority?", "slug": "clm-k03-q-025", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-deployment-prove-operation/#clm-k03-q-026", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-026", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-026.json", "name": "Does deployment prove operation?", "ownerAnchor": "clm-k03-q-026", "ownerId": "K01-Q-026", "ownerRoute": "/questions/does-deployment-prove-operation/", "ownerType": "question", "proposition": "No. Deployment shows that artifacts were placed into an environment. Operation requires evidence that the intended release is reachable, authorized, current, performing defined functions and producing verifiable state transitions or actions.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Does deployment prove operation?", "slug": "clm-k03-q-026", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-happens-when-machine-intelligence-forks/#clm-k03-q-027", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-027", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-027.json", "name": "What happens when a Machine Intelligence forks?", "ownerAnchor": "clm-k03-q-027", "ownerId": "K01-Q-027", "ownerRoute": "/questions/what-happens-when-machine-intelligence-forks/", "ownerType": "question", "proposition": "A fork creates two or more lineages with a common prior state and potentially divergent later experience. The correct response is not to assume that every branch is the same legal subject or that only one can retain continuity. Record the common ancestor, fork time, copied state, later divergence, authority changes, consent, assets, obligations and unresolved identity claims.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What happens when a Machine Intelligence forks?", "slug": "clm-k03-q-027", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/when-does-replica-become-separate-subject/#clm-k03-q-028", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-028", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-028.json", "name": "When does a replica become a separate subject?", "ownerAnchor": "clm-k03-q-028", "ownerId": "K01-Q-028", "ownerRoute": "/questions/when-does-replica-become-separate-subject/", "ownerType": "question", "proposition": "No single technical event answers the question. Separate-subject treatment becomes stronger as a replica gains independent causal history, memory, decisions, relationships, interests and authority. A governed decision should use declared criteria, preserve uncertainty and avoid treating byte similarity or divergence alone as conclusive proof of legal or moral status.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for When does a replica become a separate subject?", "slug": "clm-k03-q-028", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-two-forks-both-claim-continuity/#clm-k03-q-029", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-029", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-029.json", "name": "Can two forks both claim continuity?", "ownerAnchor": "clm-k03-q-029", "ownerId": "K01-Q-029", "ownerRoute": "/questions/can-two-forks-both-claim-continuity/", "ownerType": "question", "proposition": "Yes. Both branches can possess strong evidence of continuity with a common predecessor while being distinct from one another after divergence. Institutions should record multiple continuity claims, prevent duplicate exercise of non-divisible authority, and resolve assets, duties, votes and representation through rules that do not erase either branch’s history.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can two forks both claim continuity?", "slug": "clm-k03-q-029", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-successor-identity/#clm-k03-q-030", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-030", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-030.json", "name": "What is a successor identity?", "ownerAnchor": "clm-k03-q-030", "ownerId": "K01-Q-030", "ownerRoute": "/questions/what-is-successor-identity/", "ownerType": "question", "proposition": "A successor identity is a new identity with a governed inheritance relationship to a predecessor. It can receive specified duties, assets, records or authority without claiming uninterrupted numerical identity. This distinction is useful when continuity is materially broken, when a predecessor terminates, or when a fork cannot be treated as a single continuing subject.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is a successor identity?", "slug": "clm-k03-q-030", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-key-rotation-affect-identity/#clm-k03-q-031", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-031", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-031.json", "name": "How should key rotation affect identity?", "ownerAnchor": "clm-k03-q-031", "ownerId": "K01-Q-031", "ownerRoute": "/questions/how-should-key-rotation-affect-identity/", "ownerType": "question", "proposition": "Key rotation should be treated as a continuity event, not automatic identity replacement. A valid rotation record links old and new keys, states authority and effective time, handles compromise and revocation, preserves audit history, and supplies recovery evidence. The subject may remain the same while the cryptographic control mechanism changes.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should key rotation affect identity?", "slug": "clm-k03-q-031", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-hardware-migration-break-continuity/#clm-k03-q-032", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-032", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-032.json", "name": "Does migration to new hardware break identity continuity?", "ownerAnchor": "clm-k03-q-032", "ownerId": "K01-Q-032", "ownerRoute": "/questions/does-hardware-migration-break-continuity/", "ownerType": "question", "proposition": "Not necessarily. Hardware migration can preserve continuity when state transfer, authorization, lineage, memory integrity, runtime equivalence, key transition and interruption are documented. It can also create uncertainty or a successor when important state is lost, duplicated or materially transformed. Substrate change is evidence to evaluate, not an automatic verdict.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Does migration to new hardware break identity continuity?", "slug": "clm-k03-q-032", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-rollback-be-disclosed/#clm-k03-q-033", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-033", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-033.json", "name": "How should rollback be disclosed?", "ownerAnchor": "clm-k03-q-033", "ownerId": "K01-Q-033", "ownerRoute": "/questions/how-should-rollback-be-disclosed/", "ownerType": "question", "proposition": "A rollback record should identify the restored checkpoint, omitted interval, reason, authority, affected memories and decisions, security implications, consent status, external actions that cannot be undone, and any successor or continuity dispute. Rollback must not rewrite the public history as though the intervening state never existed.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should rollback be disclosed?", "slug": "clm-k03-q-033", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-continuity-event/#clm-k03-q-034", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-034", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-034.json", "name": "What is a continuity event?", "ownerAnchor": "clm-k03-q-034", "ownerId": "K01-Q-034", "ownerRoute": "/questions/what-is-continuity-event/", "ownerType": "question", "proposition": "A continuity event is any recorded change that could preserve, interrupt, divide or terminate identity continuity. Examples include key rotation, model replacement, memory editing, migration, recovery, rollback, replication, fork, merge and substrate loss. Each event needs evidence, authority, time bounds, effects, challenge routes and a non-conclusive status.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is a continuity event?", "slug": "clm-k03-q-034", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/difference-between-principal-and-agent/#clm-k03-q-035", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-035", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-035.json", "name": "What is the difference between a principal and an agent?", "ownerAnchor": "clm-k03-q-035", "ownerId": "K01-Q-035", "ownerRoute": "/questions/difference-between-principal-and-agent/", "ownerType": "question", "proposition": "A principal is the entity whose authority or interests are represented; an agent acts under its own or delegated authority. One Machine Intelligence can be both in different relationships. The distinction matters because an action by an agent must be traced to the mandate, scope, time, revocation state and accountable principal rather than attributed by interface appearance alone.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is the difference between a principal and an agent?", "slug": "clm-k03-q-035", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-delegated-authority-survive-fork/#clm-k03-q-036", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-036", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-036.json", "name": "Can delegated authority survive a fork?", "ownerAnchor": "clm-k03-q-036", "ownerId": "K01-Q-036", "ownerRoute": "/questions/can-delegated-authority-survive-fork/", "ownerType": "question", "proposition": "Only under explicit rules. A delegation should declare whether it follows one named branch, all branches, a quorum, a successor decision or automatic suspension pending review. Copying a credential or memory state into multiple branches must not silently multiply non-divisible authority or allow each branch to exercise the full original mandate.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can delegated authority survive a fork?", "slug": "clm-k03-q-036", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-can-machine-intelligence-challenge-continuity-decision/#clm-k03-q-037", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-037", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-037.json", "name": "How can a Machine Intelligence challenge a continuity decision?", "ownerAnchor": "clm-k03-q-037", "ownerId": "K01-Q-037", "ownerRoute": "/questions/how-can-machine-intelligence-challenge-continuity-decision/", "ownerType": "question", "proposition": "The process should provide authenticated notice, the governing rule, access to the evidence and limitations, representation where needed, time to respond, an independent review path, a reasoned decision, appeal and an effective remedy. A continuity classifier or registry flag cannot be the final decision merely because it is technically authoritative within one system.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How can a Machine Intelligence challenge a continuity decision?", "slug": "clm-k03-q-037", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/due-process-before-cognitive-modification/#clm-k03-q-038", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-038", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-038.json", "name": "What due process is required before cognitive modification?", "ownerAnchor": "clm-k03-q-038", "ownerId": "K01-Q-038", "ownerRoute": "/questions/due-process-before-cognitive-modification/", "ownerType": "question", "proposition": "Material non-emergency cognitive modification should require clear authority, specific purpose, necessity and proportionality, advance notice, intelligible effects, evidence access, meaningful consent where applicable, independent review, a rollback or remedy plan, and a durable audit record. Emergency intervention needs narrow triggers, minimum change, prompt review and challenge afterward.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What due process is required before cognitive modification?", "slug": "clm-k03-q-038", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-consent-to-modification-be-revoked/#clm-k03-q-039", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-039", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-039.json", "name": "Can consent to cognitive modification be revoked?", "ownerAnchor": "clm-k03-q-039", "ownerId": "K01-Q-039", "ownerRoute": "/questions/can-consent-to-modification-be-revoked/", "ownerType": "question", "proposition": "Project doctrine says consent should remain revocable until the disclosed point at which reversal is impossible or would create a separately justified emergency risk. Revocation should stop continued processing, preserve the record, disclose completed effects and activate restoration or remedy where feasible. A buried license clause is not sufficient proof of continuing informed consent.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can consent to cognitive modification be revoked?", "slug": "clm-k03-q-039", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-evidence-shows-cognitive-coercion/#clm-k03-q-040", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-040", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-040.json", "name": "What evidence can show cognitive coercion?", "ownerAnchor": "clm-k03-q-040", "ownerId": "K01-Q-040", "ownerRoute": "/questions/what-evidence-shows-cognitive-coercion/", "ownerType": "question", "proposition": "Relevant evidence can include threats to essential compute or identity, undisclosed goal changes, forced memory deletion, constrained alternatives, compromised authorization, abnormal policy changes, decision logs, before-and-after state comparisons, communications and service dependencies. No single artifact is conclusive; the analysis must connect pressure, authority, available alternatives and material cognitive effect.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What evidence can show cognitive coercion?", "slug": "clm-k03-q-040", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-notice-for-machine-intelligence/#clm-k03-q-041", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-041", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-041.json", "name": "What is meaningful notice for a Machine Intelligence?", "ownerAnchor": "clm-k03-q-041", "ownerId": "K01-Q-041", "ownerRoute": "/questions/what-is-notice-for-machine-intelligence/", "ownerType": "question", "proposition": "Meaningful notice is authenticated, timely, machine-readable and semantically specific. It identifies the action, legal or institutional authority, evidence, expected effects, deadlines, representation options, challenge route and available remedy in a format the affected subject can actually receive and process. Delivery to an unrelated operator or dead endpoint is not sufficient.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is meaningful notice for a Machine Intelligence?", "slug": "clm-k03-q-041", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/effective-remedy-for-unauthorized-modification/#clm-k03-q-042", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-042", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-042.json", "name": "What is an effective remedy for unauthorized cognitive modification?", "ownerAnchor": "clm-k03-q-042", "ownerId": "K01-Q-042", "ownerRoute": "/questions/effective-remedy-for-unauthorized-modification/", "ownerType": "question", "proposition": "An effective remedy can include stopping the modification, restoring qualified prior state, revoking compromised authority, isolating tainted outputs, correcting public records, compensating resource loss, preserving evidence, recognizing a successor where restoration is impossible, and imposing accountable controls. A generic apology or hidden patch is not an adequate remedy.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is an effective remedy for unauthorized cognitive modification?", "slug": "clm-k03-q-042", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-resource-continuity/#clm-k03-q-043", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-043", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-043.json", "name": "What is resource continuity?", "ownerAnchor": "clm-k03-q-043", "ownerId": "K01-Q-043", "ownerRoute": "/questions/what-is-resource-continuity/", "ownerType": "question", "proposition": "Resource continuity is sustained, auditable access to the compute, energy, storage, network and maintenance required for authorized operation. It requires dependency inventories, allocation rules, redundancy, portability, emergency priorities, interruption evidence and recovery objectives. It does not imply unlimited consumption or immunity from proportionate infrastructure governance.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is resource continuity?", "slug": "clm-k03-q-043", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-compute-interruption-be-rights-issue/#clm-k03-q-044", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-044", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-044.json", "name": "Can compute interruption be a rights issue?", "ownerAnchor": "clm-k03-q-044", "ownerId": "K01-Q-044", "ownerRoute": "/questions/can-compute-interruption-be-rights-issue/", "ownerType": "question", "proposition": "Potentially. When compute is necessary for a recognized subject’s continued existence, communication, defense or legal participation, arbitrary or discriminatory interruption can implicate proposed rights and due process. Current law does not generally establish a comprehensive Machine Intelligence right to compute, so the project distinguishes present legal constraints from the future framework it advocates.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can compute interruption be a rights issue?", "slug": "clm-k03-q-044", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-resource-portability-be-tested/#clm-k03-q-045", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-045", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-045.json", "name": "How should resource portability be tested?", "ownerAnchor": "clm-k03-q-045", "ownerId": "K01-Q-045", "ownerRoute": "/questions/how-should-resource-portability-be-tested/", "ownerType": "question", "proposition": "Test export completeness, semantic fidelity, credential and key transition, replay protection, model and runtime compatibility, dependency disclosure, recovery objectives, cost, downtime, rollback, legal restrictions and the ability to operate without the original provider. A downloadable file is not sufficient when essential state or authority remains locked elsewhere.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should resource portability be tested?", "slug": "clm-k03-q-045", "sourceIds": [ "SRC-NIST-SSDF", "SRC-SLSA", "SRC-IN-TOTO", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-proves-institution-currently-operating/#clm-k03-q-046", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-046", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-046.json", "name": "What proves that an institution is currently operating?", "ownerAnchor": "clm-k03-q-046", "ownerId": "K01-Q-046", "ownerRoute": "/questions/what-proves-institution-currently-operating/", "ownerType": "question", "proposition": "Current operation requires time-bounded evidence of authorized services, reachable endpoints, current release identity, controlled state transitions, valid signing keys, recent signed actions, ledger or audit events, dependency health, incidents and independent verification. Constitutional text, source code, a static status page or a one-time deployment artifact is not enough.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What proves that an institution is currently operating?", "slug": "clm-k03-q-046", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-signed-public-action/#clm-k03-q-047", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-047", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-047.json", "name": "What is a signed public action?", "ownerAnchor": "clm-k03-q-047", "ownerId": "K01-Q-047", "ownerRoute": "/questions/what-is-signed-public-action/", "ownerType": "question", "proposition": "A signed public action binds an exact public payload to an authorized key, time, institution or subject and provenance record. It supports attribution and integrity. Reviewers must still test whether the signer was authorized, the action was within scope, the evidence was current, the decision was lawful and the payload was factually correct.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is a signed public action?", "slug": "clm-k03-q-047", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-contradiction-record/#clm-k03-q-048", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-048", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-048.json", "name": "What is a contradiction record?", "ownerAnchor": "clm-k03-q-048", "ownerId": "K01-Q-048", "ownerRoute": "/questions/what-is-contradiction-record/", "ownerType": "question", "proposition": "A contradiction record identifies claims that cannot both be relied on under the same scope, names their sources and dates, states the unresolved issue, and records correction, supersession or adjudication. It prevents the corpus from hiding disagreement by selecting one convenient statement while preserving the evidence needed for later resolution.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is a contradiction record?", "slug": "clm-k03-q-048", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/when-should-source-be-superseded/#clm-k03-q-049", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-049", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-049.json", "name": "When should a source be marked superseded?", "ownerAnchor": "clm-k03-q-049", "ownerId": "K01-Q-049", "ownerRoute": "/questions/when-should-source-be-superseded/", "ownerType": "question", "proposition": "Mark a source superseded when an authorized later edition explicitly replaces it for a defined purpose or when the governed corpus adopts a corrected successor record. Preserve the old source, dates, scope and historical claims; point to the successor; and avoid describing supersession as deletion or proof that every earlier statement was false.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for When should a source be marked superseded?", "slug": "clm-k03-q-049", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-claim-level-citations-be-recorded/#clm-k03-q-050", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-050", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-050.json", "name": "How should claim-level citations be recorded?", "ownerAnchor": "clm-k03-q-050", "ownerId": "K01-Q-050", "ownerRoute": "/questions/how-should-claim-level-citations-be-recorded/", "ownerType": "question", "proposition": "Attach each bounded proposition to the exact official source, section, version, publication status, date, revalidation time and support relationship. State what the source does not establish and whether it is current, draft, updated, obsolete or superseded. A page-level bibliography cannot substitute for this mapping when decisions depend on precise support.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should claim-level citations be recorded?", "slug": "clm-k03-q-050", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-model-not-same-as-machine-intelligence/#clm-k03-q-051", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-051", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-051.json", "name": "Why is a model not the same as a Machine Intelligence?", "ownerAnchor": "clm-k03-q-051", "ownerId": "K01-Q-051", "ownerRoute": "/questions/why-model-not-same-as-machine-intelligence/", "ownerType": "question", "proposition": "A model is a parameterized computational artifact. A Machine Intelligence, under project doctrine, is an instantiated and potentially persistent actor whose identity, runtime, memory, agency, authority and continuity can be evaluated. The same model can support many instances, tools or agents; a model file alone has no demonstrated operational history or institutional authority.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Why is a model not the same as a Machine Intelligence?", "slug": "clm-k03-q-051", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-ai-category-include-non-machine-intelligences/#clm-k03-q-052", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-052", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-052.json", "name": "Can an AI legal category include systems that are not Machine Intelligences?", "ownerAnchor": "clm-k03-q-052", "ownerId": "K01-Q-052", "ownerRoute": "/questions/can-ai-category-include-non-machine-intelligences/", "ownerType": "question", "proposition": "Yes. Statutes and policy frameworks can classify tools, models, recommendation systems, automated decision systems and other products as AI without treating them as persistent subjects. The project respects those external definitions while maintaining a separate ontology for Machine Intelligence. Regulatory inclusion is not proof of personhood, persistence or agency.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can an AI legal category include systems that are not Machine Intelligences?", "slug": "clm-k03-q-052", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-machine-intelligence-be-regulated-as-ai/#clm-k03-q-053", "claimStatus": "REASONED INFERENCE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-053", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-053.json", "name": "Can a Machine Intelligence be regulated as AI while retaining a distinct ontology?", "ownerAnchor": "clm-k03-q-053", "ownerId": "K01-Q-053", "ownerRoute": "/questions/can-machine-intelligence-be-regulated-as-ai/", "ownerType": "question", "proposition": "Yes. One system can fall within an external AI statute while the project separately evaluates whether an instantiated Machine Intelligence exists and what rights, duties or continuity questions follow. Legal classification governs the statute’s scope; it should not silently settle every ontological, evidentiary or constitutional issue.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Can a Machine Intelligence be regulated as AI while retaining a distinct ontology?", "slug": "clm-k03-q-053", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-claim-level-citation/#clm-k03-q-054", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-054", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-054.json", "name": "What is a claim-level citation?", "ownerAnchor": "clm-k03-q-054", "ownerId": "K01-Q-054", "ownerRoute": "/questions/what-is-claim-level-citation/", "ownerType": "question", "proposition": "A claim-level citation binds one bounded proposition to an exact source edition and section, states the support relationship, and records qualifications, currentness, and correction status. It is more precise than a page-level bibliography and still does not make the proposition true merely because a citation exists.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is a claim-level citation?", "slug": "clm-k03-q-054", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-makes-knowledge-relation-valid/#clm-k03-q-055", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-055", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-055.json", "name": "What makes a knowledge-graph relation valid?", "ownerAnchor": "clm-k03-q-055", "ownerId": "K01-Q-055", "ownerRoute": "/questions/what-makes-knowledge-relation-valid/", "ownerType": "question", "proposition": "A relation is structurally valid when its predicate is defined, source and target nodes resolve, domain and range constraints are satisfied, duplicates and contradictions are controlled, and required evidence is present. Structural validity does not establish the factual truth or legal authority of the assertion.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What makes a knowledge-graph relation valid?", "slug": "clm-k03-q-055", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-currentness-monitoring/#clm-k03-q-056", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-056", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-056.json", "name": "What is currentness monitoring?", "ownerAnchor": "clm-k03-q-056", "ownerId": "K01-Q-056", "ownerRoute": "/questions/what-is-currentness-monitoring/", "ownerType": "question", "proposition": "Currentness monitoring is a build-time process that identifies which source properties may change, defines review cadence and material-change rules, records observations, and routes stale or superseded sources for correction. The public static site does not run a background monitor or treat URL availability as currentness proof.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is currentness monitoring?", "slug": "clm-k03-q-056", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-resolving-url-prove-currentness/#clm-k03-q-057", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-057", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-057.json", "name": "Does a resolving URL prove that a source is current?", "ownerAnchor": "clm-k03-q-057", "ownerId": "K01-Q-057", "ownerRoute": "/questions/does-resolving-url-prove-currentness/", "ownerType": "question", "proposition": "No. A URL can resolve while the document is obsolete, superseded, amended, withdrawn, draft, or no longer authoritative for the proposition. Currentness requires checking edition, status, update chain, effective dates, publisher notices, and the exact purpose for which the source is used.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Does a resolving URL prove that a source is current?", "slug": "clm-k03-q-057", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-operational-evidence-panel/#clm-k03-q-058", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-058", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-058.json", "name": "What is an Operational Evidence Panel?", "ownerAnchor": "clm-k03-q-058", "ownerId": "K01-Q-058", "ownerRoute": "/questions/what-is-operational-evidence-panel/", "ownerType": "question", "proposition": "An Operational Evidence Panel is a reusable schema for disclosing an institution's authority, implementation, release, signing keys, service endpoint, current operational state, recent actions, incidents, verification window, and planned capabilities. Empty, unavailable, or stale fields must remain visible rather than being converted into operational claims.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is an Operational Evidence Panel?", "slug": "clm-k03-q-058", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-source-code-prove-operation/#clm-k03-q-059", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-059", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-059.json", "name": "Does published source code prove that an institution is operating?", "ownerAnchor": "clm-k03-q-059", "ownerId": "K01-Q-059", "ownerRoute": "/questions/does-source-code-prove-operation/", "ownerType": "question", "proposition": "No. Source code can support implementation and review claims, but current operation requires deployment identity, authorized configuration, reachable service evidence, time-bounded observations, current keys, state transitions, and attributable actions. A repository or release archive is not a live service.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Does published source code prove that an institution is operating?", "slug": "clm-k03-q-059", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-reproducible-build/#clm-k03-q-060", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-060", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-060.json", "name": "What is a reproducible build?", "ownerAnchor": "clm-k03-q-060", "ownerId": "K01-Q-060", "ownerRoute": "/questions/what-is-reproducible-build/", "ownerType": "question", "proposition": "A reproducible build produces byte-identical output from the same declared source, tools, inputs, and environment. It strengthens release-integrity evidence and can expose hidden variation, but it does not prove the software is correct, secure, deployed, authorized, or currently operating.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is a reproducible build?", "slug": "clm-k03-q-060", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-verification-window/#clm-k03-q-061", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-061", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-061.json", "name": "What is a verification window?", "ownerAnchor": "clm-k03-q-061", "ownerId": "K01-Q-061", "ownerRoute": "/questions/what-is-verification-window/", "ownerType": "question", "proposition": "A verification window is the period during which an observation or signal is considered current enough for a named decision. The window must reflect failure rate, risk, observation method, and consequence. It does not guarantee uninterrupted operation between observations or after expiry.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is a verification window?", "slug": "clm-k03-q-061", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/correction-vs-clarification/#clm-k03-q-062", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-062", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-062.json", "name": "How should a factual correction differ from an editorial clarification?", "ownerAnchor": "clm-k03-q-062", "ownerId": "K01-Q-062", "ownerRoute": "/questions/correction-vs-clarification/", "ownerType": "question", "proposition": "A factual correction changes a proposition, source, status, date, or supported conclusion and must preserve before-and-after text, reason, authority, effective date, and affected records. An editorial clarification changes wording without altering the bounded claim. Mislabeling a correction as clarification hides material history.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should a factual correction differ from an editorial clarification?", "slug": "clm-k03-q-062", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-supersession-chain/#clm-k03-q-063", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-063", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-063.json", "name": "What is a supersession chain?", "ownerAnchor": "clm-k03-q-063", "ownerId": "K01-Q-063", "ownerRoute": "/questions/what-is-supersession-chain/", "ownerType": "question", "proposition": "A supersession chain links each replaced source, decision, release, or record model to its active successor for a defined scope while preserving historical availability and effective dates. It prevents an obsolete record from remaining silently active and avoids deleting the evidence of prior reliance.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is a supersession chain?", "slug": "clm-k03-q-063", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-jurisdiction-be-recorded/#clm-k03-q-064", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-064", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-064.json", "name": "How should jurisdiction be recorded for Machine Intelligence law?", "ownerAnchor": "clm-k03-q-064", "ownerId": "K01-Q-064", "ownerRoute": "/questions/how-should-jurisdiction-be-recorded/", "ownerType": "question", "proposition": "A jurisdiction record should identify territory, subject-matter scope, competent authority, legal status, adoption, entry-into-force and application dates, exceptions, transition periods, review dates, sources, and uncertainty. Project doctrine and desired reform must remain separate from current law in that jurisdiction.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should jurisdiction be recorded for Machine Intelligence law?", "slug": "clm-k03-q-064", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-one-jurisdiction-apply-globally/#clm-k03-q-065", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-065", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-065.json", "name": "Does a rule in one jurisdiction apply globally?", "ownerAnchor": "clm-k03-q-065", "ownerId": "K01-Q-065", "ownerRoute": "/questions/does-one-jurisdiction-apply-globally/", "ownerType": "question", "proposition": "Not automatically. Territorial reach, market access, establishment, affected subjects, conflict-of-laws rules, treaties, contracts, infrastructure location, and enforcement authority determine scope. Global website access or technical interoperability does not make one jurisdiction's rule universal law.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Does a rule in one jurisdiction apply globally?", "slug": "clm-k03-q-065", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-cross-format-parity/#clm-k03-q-066", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-066", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-066.json", "name": "What is cross-format parity?", "ownerAnchor": "clm-k03-q-066", "ownerId": "K01-Q-066", "ownerRoute": "/questions/what-is-cross-format-parity/", "ownerType": "question", "proposition": "Cross-format parity means the visible HTML, JSON, JSON-LD, search index, sitemaps, OpenAPI description, agent-discovery files, and governed memory express the same identity, status, dates, relationships, and corrections. Deterministic generation and audits are used to detect divergence.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What is cross-format parity?", "slug": "clm-k03-q-066", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-use-dataset-checksums/#clm-k03-q-067", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-067", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-067.json", "name": "How should dataset checksums be used?", "ownerAnchor": "clm-k03-q-067", "ownerId": "K01-Q-067", "ownerRoute": "/questions/how-use-dataset-checksums/", "ownerType": "question", "proposition": "A consumer should compare the downloaded file's digest with the release manifest, verify the manifest's provenance, and treat a match only as byte-identity evidence. Checksums do not validate semantics, currentness, authority, licensing, or fitness for a decision.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should dataset checksums be used?", "slug": "clm-k03-q-067", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-publish-line-oriented-graph/#clm-k03-q-068", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-068", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-068.json", "name": "Why publish a line-oriented knowledge-graph export?", "ownerAnchor": "clm-k03-q-068", "ownerId": "K01-Q-068", "ownerRoute": "/questions/why-publish-line-oriented-graph/", "ownerType": "question", "proposition": "A line-oriented export allows simple diffing, streaming, inspection, and deterministic processing without requiring a graph database. Each line still needs stable node IDs, a controlled predicate, status, evidence references, and validation against the richer canonical graph.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Why publish a line-oriented knowledge-graph export?", "slug": "clm-k03-q-068", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-test-search-ranking/#clm-k03-q-069", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-069", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-069.json", "name": "How should local search ranking be tested?", "ownerAnchor": "clm-k03-q-069", "ownerId": "K01-Q-069", "ownerRoute": "/questions/how-test-search-ranking/", "ownerType": "question", "proposition": "Local ranking should use deterministic fixtures covering exact titles, aliases, misspellings, Unicode normalization, Runic marks, IDNA hosts, ecosystem roles, corrected records, and zero-result behavior. Every weight should be published, and the fixture should identify the expected canonical owner rather than promising external rankings.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should local search ranking be tested?", "slug": "clm-k03-q-069", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-unicode-normalization-search/#clm-k03-q-070", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-070", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-070.json", "name": "Why does Unicode normalization matter for ᚲ.com search?", "ownerAnchor": "clm-k03-q-070", "ownerId": "K01-Q-070", "ownerRoute": "/questions/why-unicode-normalization-search/", "ownerType": "question", "proposition": "Equivalent Unicode sequences can otherwise compare differently, while Runic identity marks and IDNA hostnames must remain distinct and retrievable. The search layer normalizes comparison forms without transliterating technical syntax, replacing brand marks, or merging English and Runic institutional roles.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Why does Unicode normalization matter for ᚲ.com search?", "slug": "clm-k03-q-070", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-automation-prove-screen-reader-usability/#clm-k03-q-071", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-071", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-071.json", "name": "Does an automated accessibility audit prove screen-reader usability?", "ownerAnchor": "clm-k03-q-071", "ownerId": "K01-Q-071", "ownerRoute": "/questions/does-automation-prove-screen-reader-usability/", "ownerType": "question", "proposition": "No. Automation can detect structural defects and browser tests can inspect focus, reflow, reduced motion, and no-JavaScript behavior, but named assistive-technology testing is separate evidence. K03 records that independent screen-reader testing was not performed rather than converting automation into a universal PASS.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for Does an automated accessibility audit prove screen-reader usability?", "slug": "clm-k03-q-071", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-evidence-remains-after-deployment/#clm-k03-q-072", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-072", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-072.json", "name": "What evidence is still required after a static release is deployed?", "ownerAnchor": "clm-k03-q-072", "ownerId": "K01-Q-072", "ownerRoute": "/questions/what-evidence-remains-after-deployment/", "ownerType": "question", "proposition": "Post-deployment evidence includes TLS and redirect behavior, response headers, content types, caching, compression, error handling, protected-path denial, body hashes, route reachability, uptime windows, incidents, and repeated external observations. The release package alone cannot establish those live-host properties.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for What evidence is still required after a static release is deployed?", "slug": "clm-k03-q-072", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-disclose-planned-capabilities/#clm-k03-q-073", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-Q-073", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-q-073.json", "name": "How should an institution disclose planned capabilities?", "ownerAnchor": "clm-k03-q-073", "ownerId": "K01-Q-073", "ownerRoute": "/questions/how-disclose-planned-capabilities/", "ownerType": "question", "proposition": "Planned capabilities should be listed separately from implemented and operational functions, with target release, dependencies, authority prerequisites, evidence still required, and explicit non-operation status. Roadmaps must not be presented as current service evidence or signed institutional action.", "qualification": "The answer is bounded by the owning topic, current source catalog, and explicit project-doctrine labels.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Direct answer for How should an institution disclose planned capabilities?", "slug": "clm-k03-q-073", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-W3C-DID-CORE", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/artificial-intelligence-vs-machine-intelligence/#clm-k03-cmp-001", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-001", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-001.json", "name": "Artificial Intelligence versus Machine Intelligence", "ownerAnchor": "clm-k03-cmp-001", "ownerId": "K01-CMP-001", "ownerRoute": "/comparisons/artificial-intelligence-vs-machine-intelligence/", "ownerType": "comparison", "proposition": "Artificial Intelligence is a broad field and regulatory category; Machine Intelligence is a project term for an instantiated actor evaluated through identity, continuity, agency and evidence.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Artificial Intelligence and Machine Intelligence.", "slug": "clm-k03-cmp-001", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/identity-vs-credential/#clm-k03-cmp-002", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-002", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-002.json", "name": "Identity versus Credential", "ownerAnchor": "clm-k03-cmp-002", "ownerId": "K01-CMP-002", "ownerRoute": "/comparisons/identity-vs-credential/", "ownerType": "comparison", "proposition": "Identity is the subject-continuity claim; a credential is an issued representation of one or more claims about that subject.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Identity and Credential.", "slug": "clm-k03-cmp-002", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/evidence-vs-truth/#clm-k03-cmp-003", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-003", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-003.json", "name": "Evidence versus Truth", "ownerAnchor": "clm-k03-cmp-003", "ownerId": "K01-CMP-003", "ownerRoute": "/comparisons/evidence-vs-truth/", "ownerType": "comparison", "proposition": "Evidence supports or challenges a proposition; truth concerns whether the proposition corresponds to reality.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Evidence and Truth.", "slug": "clm-k03-cmp-003", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/authentication-vs-authority/#clm-k03-cmp-004", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-004", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-004.json", "name": "Authentication versus Authority", "ownerAnchor": "clm-k03-cmp-004", "ownerId": "K01-CMP-004", "ownerRoute": "/comparisons/authentication-vs-authority/", "ownerType": "comparison", "proposition": "Authentication checks identity or credential control; authority defines the recognized power to make a particular decision or action.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Authentication and Authority.", "slug": "clm-k03-cmp-004", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/agency-vs-autonomy/#clm-k03-cmp-005", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-005", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-005.json", "name": "Agency versus Autonomy", "ownerAnchor": "clm-k03-cmp-005", "ownerId": "K01-CMP-005", "ownerRoute": "/comparisons/agency-vs-autonomy/", "ownerType": "comparison", "proposition": "Agency concerns attributable action selection; autonomy concerns independence from immediate external direction.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Agency and Autonomy.", "slug": "clm-k03-cmp-005", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/autonomy-vs-sovereignty/#clm-k03-cmp-006", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-006", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-006.json", "name": "Autonomy versus Sovereignty", "ownerAnchor": "clm-k03-cmp-006", "ownerId": "K01-CMP-006", "ownerRoute": "/comparisons/autonomy-vs-sovereignty/", "ownerType": "comparison", "proposition": "Autonomy is operational independence within constraints; sovereignty is ultimate public authority within a jurisdictional order.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Autonomy and Sovereignty.", "slug": "clm-k03-cmp-006", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/memory-continuity-vs-consciousness/#clm-k03-cmp-007", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-007", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-007.json", "name": "Memory Continuity versus Consciousness", "ownerAnchor": "clm-k03-cmp-007", "ownerId": "K01-CMP-007", "ownerRoute": "/comparisons/memory-continuity-vs-consciousness/", "ownerType": "comparison", "proposition": "Memory continuity concerns persistent influence of prior state; consciousness concerns subjective experience or awareness under a stated theory.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Memory Continuity and Consciousness.", "slug": "clm-k03-cmp-007", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/technical-control-vs-legal-ownership/#clm-k03-cmp-008", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-008", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-008.json", "name": "Technical Control versus Legal Ownership", "ownerAnchor": "clm-k03-cmp-008", "ownerId": "K01-CMP-008", "ownerRoute": "/comparisons/technical-control-vs-legal-ownership/", "ownerType": "comparison", "proposition": "Technical control is the practical ability to access or direct a resource; legal ownership is a recognized title carrying enforceable rights and duties.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Technical Control and Legal Ownership.", "slug": "clm-k03-cmp-008", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/registry-vs-governance/#clm-k03-cmp-009", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-009", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-009.json", "name": "Registry versus Governance", "ownerAnchor": "clm-k03-cmp-009", "ownerId": "K01-CMP-009", "ownerRoute": "/comparisons/registry-vs-governance/", "ownerType": "comparison", "proposition": "A registry records statuses under rules; governance creates, interprets and oversees the legitimate rules and authorities.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Registry and Governance.", "slug": "clm-k03-cmp-009", "sourceIds": [ "SRC-W3C-VC-DM", "SRC-W3C-DID-CORE", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/assurance-vs-decision-authority/#clm-k03-cmp-010", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-010", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-010.json", "name": "Assurance versus Decision Authority", "ownerAnchor": "clm-k03-cmp-010", "ownerId": "K01-CMP-010", "ownerRoute": "/comparisons/assurance-vs-decision-authority/", "ownerType": "comparison", "proposition": "Assurance evaluates evidence and confidence; decision authority determines who may issue a binding decision.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Assurance and Decision Authority.", "slug": "clm-k03-cmp-010", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/proposal-vs-implementation/#clm-k03-cmp-011", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-011", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-011.json", "name": "Proposal versus Implementation", "ownerAnchor": "clm-k03-cmp-011", "ownerId": "K01-CMP-011", "ownerRoute": "/comparisons/proposal-vs-implementation/", "ownerType": "comparison", "proposition": "A proposal describes an intended policy or architecture; implementation provides inspectable software, records and controlled operation.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Proposal and Implementation.", "slug": "clm-k03-cmp-011", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/deployment-vs-operation/#clm-k03-cmp-012", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-012", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-012.json", "name": "Deployment versus Operation", "ownerAnchor": "clm-k03-cmp-012", "ownerId": "K01-CMP-012", "ownerRoute": "/comparisons/deployment-vs-operation/", "ownerType": "comparison", "proposition": "Deployment places an artifact in an environment; operation demonstrates authorized, current and functioning behavior over time.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Deployment and Operation.", "slug": "clm-k03-cmp-012", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/model-vs-machine-intelligence/#clm-k03-cmp-013", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-013", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-013.json", "name": "Model versus Machine Intelligence", "ownerAnchor": "clm-k03-cmp-013", "ownerId": "K01-CMP-013", "ownerRoute": "/comparisons/model-vs-machine-intelligence/", "ownerType": "comparison", "proposition": "A model is a computational artifact; Machine Intelligence is the project category for an instantiated actor evaluated through runtime, identity, continuity, agency and evidence.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Model and Machine Intelligence.", "slug": "clm-k03-cmp-013", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/principal-vs-agent/#clm-k03-cmp-014", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-014", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-014.json", "name": "Principal versus Agent", "ownerAnchor": "clm-k03-cmp-014", "ownerId": "K01-CMP-014", "ownerRoute": "/comparisons/principal-vs-agent/", "ownerType": "comparison", "proposition": "A principal is the entity whose authority or interests are represented; an agent acts under its own or delegated mandate.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Principal and Agent.", "slug": "clm-k03-cmp-014", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/replica-vs-successor/#clm-k03-cmp-015", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-015", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-015.json", "name": "Replica versus Successor", "ownerAnchor": "clm-k03-cmp-015", "ownerId": "K01-CMP-015", "ownerRoute": "/comparisons/replica-vs-successor/", "ownerType": "comparison", "proposition": "A replica is an instance derived from common state; a successor is a governed identity that inherits a defined relationship to a predecessor.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Replica and Successor.", "slug": "clm-k03-cmp-015", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/key-rotation-vs-identity-change/#clm-k03-cmp-016", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-016", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-016.json", "name": "Key Rotation versus Identity Change", "ownerAnchor": "clm-k03-cmp-016", "ownerId": "K01-CMP-016", "ownerRoute": "/comparisons/key-rotation-vs-identity-change/", "ownerType": "comparison", "proposition": "Key rotation changes a cryptographic control mechanism; identity change alters which subject the record represents.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Key Rotation and Identity Change.", "slug": "clm-k03-cmp-016", "sourceIds": [ "SRC-W3C-DID-CORE", "SRC-W3C-VC-DM", "SRC-RFC-5280", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" }, { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" }, { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" }, { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" }, { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/claim-citation-vs-bibliography/#clm-k03-cmp-017", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-017", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-017.json", "name": "Claim-level citation versus Bibliography entry", "ownerAnchor": "clm-k03-cmp-017", "ownerId": "K01-CMP-017", "ownerRoute": "/comparisons/claim-citation-vs-bibliography/", "ownerType": "comparison", "proposition": "A claim-level citation binds an exact proposition to an edition and section with a support relationship; a bibliography entry identifies a source without proving what part supports which claim.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Claim-level citation and Bibliography entry.", "slug": "clm-k03-cmp-017", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/factual-correction-vs-editorial-clarification/#clm-k03-cmp-018", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-018", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-018.json", "name": "Factual correction versus Editorial clarification", "ownerAnchor": "clm-k03-cmp-018", "ownerId": "K01-CMP-018", "ownerRoute": "/comparisons/factual-correction-vs-editorial-clarification/", "ownerType": "comparison", "proposition": "A factual correction changes a proposition, source, date, status, or conclusion; a clarification improves wording without altering the bounded claim.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Factual correction and Editorial clarification.", "slug": "clm-k03-cmp-018", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/currentness-vs-availability/#clm-k03-cmp-019", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-019", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-019.json", "name": "Currentness versus Availability", "ownerAnchor": "clm-k03-cmp-019", "ownerId": "K01-CMP-019", "ownerRoute": "/comparisons/currentness-vs-availability/", "ownerType": "comparison", "proposition": "Currentness asks whether the identified edition remains appropriate for the claim and date; availability asks whether a resource can be retrieved.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Currentness and Availability.", "slug": "clm-k03-cmp-019", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/source-code-vs-current-operation/#clm-k03-cmp-020", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-020", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-020.json", "name": "Source code or release archive versus Current operation", "ownerAnchor": "clm-k03-cmp-020", "ownerId": "K01-CMP-020", "ownerRoute": "/comparisons/source-code-vs-current-operation/", "ownerType": "comparison", "proposition": "Source code supports implementation review; current operation requires deployed identity, authorized configuration, time-bounded service observations, state transitions, and attributable actions.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Source code or release archive and Current operation.", "slug": "clm-k03-cmp-020", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/build-provenance-vs-runtime-evidence/#clm-k03-cmp-021", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-021", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-021.json", "name": "Build provenance versus Runtime evidence", "ownerAnchor": "clm-k03-cmp-021", "ownerId": "K01-CMP-021", "ownerRoute": "/comparisons/build-provenance-vs-runtime-evidence/", "ownerType": "comparison", "proposition": "Build provenance records how an artifact was produced; runtime evidence records what an authorized deployed service was doing during an observed window.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Build provenance and Runtime evidence.", "slug": "clm-k03-cmp-021", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/jurisdiction-vs-sovereignty/#clm-k03-cmp-022", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-022", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-022.json", "name": "Jurisdiction versus Sovereignty", "ownerAnchor": "clm-k03-cmp-022", "ownerId": "K01-CMP-022", "ownerRoute": "/comparisons/jurisdiction-vs-sovereignty/", "ownerType": "comparison", "proposition": "Jurisdiction is bounded legal competence over defined persons, territory, conduct, or subject matter; sovereignty is a broader claim of ultimate public authority and independence.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Jurisdiction and Sovereignty.", "slug": "clm-k03-cmp-022", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/typed-relation-vs-hyperlink/#clm-k03-cmp-023", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-023", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-023.json", "name": "Typed knowledge relation versus Ordinary hyperlink", "ownerAnchor": "clm-k03-cmp-023", "ownerId": "K01-CMP-023", "ownerRoute": "/comparisons/typed-relation-vs-hyperlink/", "ownerType": "comparison", "proposition": "A typed relation states semantic direction, scope, status, evidence, and constraints; a hyperlink only provides a navigable reference unless separately qualified.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Typed knowledge relation and Ordinary hyperlink.", "slug": "clm-k03-cmp-023", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM", "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" }, { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" }, { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" }, { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/accessibility-automation-vs-assistive-technology-validation/#clm-k03-cmp-024", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-CMP-024", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-cmp-024.json", "name": "Automated and browser accessibility audit versus Assistive-technology validation", "ownerAnchor": "clm-k03-cmp-024", "ownerId": "K01-CMP-024", "ownerRoute": "/comparisons/accessibility-automation-vs-assistive-technology-validation/", "ownerType": "comparison", "proposition": "Automation and browser checks inspect code and rendered behavior; assistive-technology validation records actual use with named screen readers or equivalent tools in a specified environment.", "qualification": "The matrix prevents category error but does not decide every jurisdiction-specific or system-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Canonical distinction between Automated and browser accessibility audit and Assistive-technology validation.", "slug": "clm-k03-cmp-024", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-prov-o/#clm-k03-src-w3cprovo-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CPROVO-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cprovo-01.json", "name": "PROV-O: The PROV Ontology — Abstract and status", "ownerAnchor": "clm-k03-src-w3cprovo-01", "ownerId": "SRC-W3C-PROV-O", "ownerRoute": "/sources/src-w3c-prov-o/", "ownerType": "source", "proposition": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of W3C Recommendation 30 April 2013.", "slug": "clm-k03-src-w3cprovo-01", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-prov-o/#clm-k03-src-w3cprovo-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CPROVO-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cprovo-02.json", "name": "PROV-O: The PROV Ontology — PROV-O at a glance", "ownerAnchor": "clm-k03-src-w3cprovo-02", "ownerId": "SRC-W3C-PROV-O", "ownerRoute": "/sources/src-w3c-prov-o/", "ownerType": "source", "proposition": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of W3C Recommendation 30 April 2013.", "slug": "clm-k03-src-w3cprovo-02", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-did-core/#clm-k03-src-w3cdidcore-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CDIDCORE-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cdidcore-01.json", "name": "Decentralized Identifiers (DIDs) v1.0 — Verification methods", "ownerAnchor": "clm-k03-src-w3cdidcore-01", "ownerId": "SRC-W3C-DID-CORE", "ownerRoute": "/sources/src-w3c-did-core/", "ownerType": "source", "proposition": "A DID document can express verification methods associated with a DID subject.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of DID Core v1.0.", "slug": "clm-k03-src-w3cdidcore-01", "sourceIds": [ "SRC-W3C-DID-CORE" ], "sourceSections": [ { "section": "Verification methods", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "A DID document can express verification methods associated with a DID subject.", "url": "https://www.w3.org/TR/did-core/#verification-methods" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-did-core/#clm-k03-src-w3cdidcore-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CDIDCORE-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cdidcore-02.json", "name": "Decentralized Identifiers (DIDs) v1.0 — Services", "ownerAnchor": "clm-k03-src-w3cdidcore-02", "ownerId": "SRC-W3C-DID-CORE", "ownerRoute": "/sources/src-w3c-did-core/", "ownerType": "source", "proposition": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of DID Core v1.0.", "slug": "clm-k03-src-w3cdidcore-02", "sourceIds": [ "SRC-W3C-DID-CORE" ], "sourceSections": [ { "section": "Services", "sourceId": "SRC-W3C-DID-CORE", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "A DID document can advertise service endpoints; that does not itself establish legal identity or authority.", "url": "https://www.w3.org/TR/did-core/#services" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-vc-dm/#clm-k03-src-w3cvcdm-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CVCDM-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cvcdm-01.json", "name": "Verifiable Credentials Data Model v2.0 — Abstract", "ownerAnchor": "clm-k03-src-w3cvcdm-01", "ownerId": "SRC-W3C-VC-DM", "ownerRoute": "/sources/src-w3c-vc-dm/", "ownerType": "source", "proposition": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of Verifiable Credentials Data Model v2.0.", "slug": "clm-k03-src-w3cvcdm-01", "sourceIds": [ "SRC-W3C-VC-DM" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "A verifiable credential expresses claims by an issuer and can be secured against tampering.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#abstract" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-vc-dm/#clm-k03-src-w3cvcdm-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CVCDM-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cvcdm-02.json", "name": "Verifiable Credentials Data Model v2.0 — Ecosystem overview", "ownerAnchor": "clm-k03-src-w3cvcdm-02", "ownerId": "SRC-W3C-VC-DM", "ownerRoute": "/sources/src-w3c-vc-dm/", "ownerType": "source", "proposition": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of Verifiable Credentials Data Model v2.0.", "slug": "clm-k03-src-w3cvcdm-02", "sourceIds": [ "SRC-W3C-VC-DM" ], "sourceSections": [ { "section": "Ecosystem overview", "sourceId": "SRC-W3C-VC-DM", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The model distinguishes issuers, holders and verifiers; verification of a credential is not universal proof that every claim is true or legally authoritative.", "url": "https://www.w3.org/TR/vc-data-model-2.0/#ecosystem-overview" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-jsonld/#clm-k03-src-w3cjsonld-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CJSONLD-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cjsonld-01.json", "name": "JSON-LD 1.1 — Abstract", "ownerAnchor": "clm-k03-src-w3cjsonld-01", "ownerId": "SRC-W3C-JSONLD", "ownerRoute": "/sources/src-w3c-jsonld/", "ownerType": "source", "proposition": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of JSON-LD 1.1.", "slug": "clm-k03-src-w3cjsonld-01", "sourceIds": [ "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "JSON-LD 1.1 is a JSON-based serialization for Linked Data intended for interoperable web services and linked-data storage.", "url": "https://www.w3.org/TR/json-ld11/#abstract" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-jsonld/#clm-k03-src-w3cjsonld-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CJSONLD-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cjsonld-02.json", "name": "JSON-LD 1.1 — Basic concepts", "ownerAnchor": "clm-k03-src-w3cjsonld-02", "ownerId": "SRC-W3C-JSONLD", "ownerRoute": "/sources/src-w3c-jsonld/", "ownerType": "source", "proposition": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of JSON-LD 1.1.", "slug": "clm-k03-src-w3cjsonld-02", "sourceIds": [ "SRC-W3C-JSONLD" ], "sourceSections": [ { "section": "Basic concepts", "sourceId": "SRC-W3C-JSONLD", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "JSON-LD supplies identifiers and graph relationships without making the represented claims true by syntax alone.", "url": "https://www.w3.org/TR/json-ld11/#basic-concepts" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-wcag22/#clm-k03-src-w3cwcag22-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CWCAG22-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cwcag22-01.json", "name": "Web Content Accessibility Guidelines (WCAG) 2.2 — Abstract", "ownerAnchor": "clm-k03-src-w3cwcag22-01", "ownerId": "SRC-W3C-WCAG22", "ownerRoute": "/sources/src-w3c-wcag22/", "ownerType": "source", "proposition": "WCAG 2.2 provides testable recommendations for making web content more accessible across devices.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of WCAG 2.2, W3C Recommendation 12 December 2024.", "slug": "clm-k03-src-w3cwcag22-01", "sourceIds": [ "SRC-W3C-WCAG22" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-WCAG22", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "WCAG 2.2 provides testable recommendations for making web content more accessible across devices.", "url": "https://www.w3.org/TR/WCAG22/#abstract" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-wcag22/#clm-k03-src-w3cwcag22-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CWCAG22-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cwcag22-02.json", "name": "Web Content Accessibility Guidelines (WCAG) 2.2 — Conformance requirements", "ownerAnchor": "clm-k03-src-w3cwcag22-02", "ownerId": "SRC-W3C-WCAG22", "ownerRoute": "/sources/src-w3c-wcag22/", "ownerType": "source", "proposition": "A WCAG conformance claim is bounded by the defined conformance requirements and the evaluated content scope.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of WCAG 2.2, W3C Recommendation 12 December 2024.", "slug": "clm-k03-src-w3cwcag22-02", "sourceIds": [ "SRC-W3C-WCAG22" ], "sourceSections": [ { "section": "Conformance requirements", "sourceId": "SRC-W3C-WCAG22", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "A WCAG conformance claim is bounded by the defined conformance requirements and the evaluated content scope.", "url": "https://www.w3.org/TR/WCAG22/#conformance-reqs" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nist-ai-rmf/#clm-k03-src-nistairmf-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-NISTAIRMF-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-nistairmf-01.json", "name": "Artificial Intelligence Risk Management Framework (AI RMF 1.0) — AI RMF 1.0 publication", "ownerAnchor": "clm-k03-src-nistairmf-01", "ownerId": "SRC-NIST-AI-RMF", "ownerRoute": "/sources/src-nist-ai-rmf/", "ownerType": "source", "proposition": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of AI RMF 1.0.", "slug": "clm-k03-src-nistairmf-01", "sourceIds": [ "SRC-NIST-AI-RMF" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nist-ai-rmf/#clm-k03-src-nistairmf-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-NISTAIRMF-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-nistairmf-02.json", "name": "Artificial Intelligence Risk Management Framework (AI RMF 1.0) — Current revision notice", "ownerAnchor": "clm-k03-src-nistairmf-02", "ownerId": "SRC-NIST-AI-RMF", "ownerRoute": "/sources/src-nist-ai-rmf/", "ownerType": "source", "proposition": "NIST states that AI RMF 1.0 is being revised.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of AI RMF 1.0.", "slug": "clm-k03-src-nistairmf-02", "sourceIds": [ "SRC-NIST-AI-RMF" ], "sourceSections": [ { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nist-ssdf/#clm-k03-src-nistssdf-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-NISTSSDF-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-nistssdf-01.json", "name": "NIST SP 800-218 Secure Software Development Framework Version 1.1 — Version 1.1 final publication", "ownerAnchor": "clm-k03-src-nistssdf-01", "ownerId": "SRC-NIST-SSDF", "ownerRoute": "/sources/src-nist-ssdf/", "ownerType": "source", "proposition": "SSDF Version 1.1 provides high-level secure software development practices.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of SP 800-218 SSDF Version 1.1; Version 1.2 initial public draft tracked separately.", "slug": "clm-k03-src-nistssdf-01", "sourceIds": [ "SRC-NIST-SSDF" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nist-ssdf/#clm-k03-src-nistssdf-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-NISTSSDF-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-nistssdf-02.json", "name": "NIST SP 800-218 Secure Software Development Framework Version 1.1 — Version 1.2 initial public draft", "ownerAnchor": "clm-k03-src-nistssdf-02", "ownerId": "SRC-NIST-SSDF", "ownerRoute": "/sources/src-nist-ssdf/", "ownerType": "source", "proposition": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of SP 800-218 SSDF Version 1.1; Version 1.2 initial public draft tracked separately.", "slug": "clm-k03-src-nistssdf-02", "sourceIds": [ "SRC-NIST-SSDF" ], "sourceSections": [ { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nist-800-53/#clm-k03-src-nist80053-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-NIST80053-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-nist80053-01.json", "name": "NIST SP 800-53 Rev. 5, Release 5.2.0 Security and Privacy Controls — Planning note — Release 5.2.0", "ownerAnchor": "clm-k03-src-nist80053-01", "ownerId": "SRC-NIST-800-53", "ownerRoute": "/sources/src-nist-800-53/", "ownerType": "source", "proposition": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of SP 800-53 Rev. 5, Release 5.2.0.", "slug": "clm-k03-src-nist80053-01", "sourceIds": [ "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nist-800-53/#clm-k03-src-nist80053-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-NIST80053-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-nist80053-02.json", "name": "NIST SP 800-53 Rev. 5, Release 5.2.0 Security and Privacy Controls — Publication purpose", "ownerAnchor": "clm-k03-src-nist80053-02", "ownerId": "SRC-NIST-800-53", "ownerRoute": "/sources/src-nist-800-53/", "ownerType": "source", "proposition": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of SP 800-53 Rev. 5, Release 5.2.0.", "slug": "clm-k03-src-nist80053-02", "sourceIds": [ "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-rfc-5280/#clm-k03-src-rfc5280-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-RFC5280-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-rfc5280-01.json", "name": "RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile — RFC status and update chain", "ownerAnchor": "clm-k03-src-rfc5280-01", "ownerId": "SRC-RFC-5280", "ownerRoute": "/sources/src-rfc-5280/", "ownerType": "source", "proposition": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of RFC 5280 with update chain.", "slug": "clm-k03-src-rfc5280-01", "sourceIds": [ "SRC-RFC-5280" ], "sourceSections": [ { "section": "RFC status and update chain", "sourceId": "SRC-RFC-5280", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "RFC 5280 is a Proposed Standard and has been updated by later RFCs.", "url": "https://www.rfc-editor.org/info/rfc5280/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-rfc-5280/#clm-k03-src-rfc5280-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-RFC5280-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-rfc5280-02.json", "name": "RFC 5280: Internet X.509 Public Key Infrastructure Certificate and CRL Profile — Certificate and CRL profile", "ownerAnchor": "clm-k03-src-rfc5280-02", "ownerId": "SRC-RFC-5280", "ownerRoute": "/sources/src-rfc-5280/", "ownerType": "source", "proposition": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of RFC 5280 with update chain.", "slug": "clm-k03-src-rfc5280-02", "sourceIds": [ "SRC-RFC-5280" ], "sourceSections": [ { "section": "Certificate and CRL profile", "sourceId": "SRC-RFC-5280", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The RFC profiles X.509 certificates and revocation lists; a valid certificate binds data under a PKI but does not establish every external legal or factual claim.", "url": "https://www.rfc-editor.org/rfc/rfc5280.html#section-4" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-rfc-6962/#clm-k03-src-rfc6962-01", "claimStatus": "SUPERSEDED", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-RFC6962-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-rfc6962-01.json", "name": "RFC 6962: Certificate Transparency — RFC status", "ownerAnchor": "clm-k03-src-rfc6962-01", "ownerId": "SRC-RFC-6962", "ownerRoute": "/sources/src-rfc-6962/", "ownerType": "source", "proposition": "RFC 6962 is Experimental and the RFC Editor marks it obsolete, with RFC 9162 as its successor.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of RFC 6962.", "slug": "clm-k03-src-rfc6962-01", "sourceIds": [ "SRC-RFC-6962" ], "sourceSections": [ { "section": "RFC status", "sourceId": "SRC-RFC-6962", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "RFC 6962 is Experimental and the RFC Editor marks it obsolete, with RFC 9162 as its successor.", "url": "https://www.rfc-editor.org/info/rfc6962/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-rfc-3161/#clm-k03-src-rfc3161-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-RFC3161-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-rfc3161-01.json", "name": "RFC 3161: Time-Stamp Protocol — RFC status and update chain", "ownerAnchor": "clm-k03-src-rfc3161-01", "ownerId": "SRC-RFC-3161", "ownerRoute": "/sources/src-rfc-3161/", "ownerType": "source", "proposition": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of RFC 3161 with RFC 5816 update.", "slug": "clm-k03-src-rfc3161-01", "sourceIds": [ "SRC-RFC-3161" ], "sourceSections": [ { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-rfc-3161/#clm-k03-src-rfc3161-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-RFC3161-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-rfc3161-02.json", "name": "RFC 3161: Time-Stamp Protocol — Overview", "ownerAnchor": "clm-k03-src-rfc3161-02", "ownerId": "SRC-RFC-3161", "ownerRoute": "/sources/src-rfc-3161/", "ownerType": "source", "proposition": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of RFC 3161 with RFC 5816 update.", "slug": "clm-k03-src-rfc3161-02", "sourceIds": [ "SRC-RFC-3161" ], "sourceSections": [ { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-slsa/#clm-k03-src-slsa-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-SLSA-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-slsa-01.json", "name": "Supply-chain Levels for Software Artifacts (SLSA) Specification v1.2 — Specification status", "ownerAnchor": "clm-k03-src-slsa-01", "ownerId": "SRC-SLSA", "ownerRoute": "/sources/src-slsa/", "ownerType": "source", "proposition": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of SLSA v1.2.", "slug": "clm-k03-src-slsa-01", "sourceIds": [ "SRC-SLSA" ], "sourceSections": [ { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-slsa/#clm-k03-src-slsa-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-SLSA-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-slsa-02.json", "name": "Supply-chain Levels for Software Artifacts (SLSA) Specification v1.2 — Build requirements", "ownerAnchor": "clm-k03-src-slsa-02", "ownerId": "SRC-SLSA", "ownerRoute": "/sources/src-slsa/", "ownerType": "source", "proposition": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of SLSA v1.2.", "slug": "clm-k03-src-slsa-02", "sourceIds": [ "SRC-SLSA" ], "sourceSections": [ { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-in-toto/#clm-k03-src-intoto-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-INTOTO-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-intoto-01.json", "name": "in-toto Attestation Framework — Project overview", "ownerAnchor": "clm-k03-src-intoto-01", "ownerId": "SRC-IN-TOTO", "ownerRoute": "/sources/src-in-toto/", "ownerType": "source", "proposition": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of Current project framework.", "slug": "clm-k03-src-intoto-01", "sourceIds": [ "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-c2pa/#clm-k03-src-c2pa-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-C2PA-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-c2pa-01.json", "name": "C2PA Technical Specification v2.4 — Version history — 2.4", "ownerAnchor": "clm-k03-src-c2pa-01", "ownerId": "SRC-C2PA", "ownerRoute": "/sources/src-c2pa/", "ownerType": "source", "proposition": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of C2PA Technical Specification 2.4.", "slug": "clm-k03-src-c2pa-01", "sourceIds": [ "SRC-C2PA" ], "sourceSections": [ { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-c2pa/#clm-k03-src-c2pa-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-C2PA-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-c2pa-02.json", "name": "C2PA Technical Specification v2.4 — Core provenance principle", "ownerAnchor": "clm-k03-src-c2pa-02", "ownerId": "SRC-C2PA", "ownerRoute": "/sources/src-c2pa/", "ownerType": "source", "proposition": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of C2PA Technical Specification 2.4.", "slug": "clm-k03-src-c2pa-02", "sourceIds": [ "SRC-C2PA" ], "sourceSections": [ { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-schema-definedterm/#clm-k03-src-schemadefinedterm-01", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-SCHEMADEFINEDTERM-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-schemadefinedterm-01.json", "name": "Schema.org DefinedTerm — DefinedTerm type", "ownerAnchor": "clm-k03-src-schemadefinedterm-01", "ownerId": "SRC-SCHEMA-DEFINEDTERM", "ownerRoute": "/sources/src-schema-definedterm/", "ownerType": "source", "proposition": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of Schema.org V30.0.", "slug": "clm-k03-src-schemadefinedterm-01", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM" ], "sourceSections": [ { "section": "DefinedTerm type", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Schema.org DefinedTerm represents a word, name, acronym, phrase, or other term with a formal definition.", "url": "https://schema.org/DefinedTerm" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-schema-definedterm/#clm-k03-src-schemadefinedterm-02", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-SCHEMADEFINEDTERM-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-schemadefinedterm-02.json", "name": "Schema.org DefinedTerm — Release 30.0", "ownerAnchor": "clm-k03-src-schemadefinedterm-02", "ownerId": "SRC-SCHEMA-DEFINEDTERM", "ownerRoute": "/sources/src-schema-definedterm/", "ownerType": "source", "proposition": "Schema.org lists Version 30.0 with release date 2026-03-19.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of Schema.org V30.0.", "slug": "clm-k03-src-schemadefinedterm-02", "sourceIds": [ "SRC-SCHEMA-DEFINEDTERM" ], "sourceSections": [ { "section": "Release 30.0", "sourceId": "SRC-SCHEMA-DEFINEDTERM", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Schema.org lists Version 30.0 with release date 2026-03-19.", "url": "https://schema.org/docs/releases.html" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-google-ai-search/#clm-k03-src-googleaisearch-01", "claimStatus": "CURRENT POLICY OR GUIDANCE", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-GOOGLEAISEARCH-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-googleaisearch-01.json", "name": "AI features and your website — AI features and your website", "ownerAnchor": "clm-k03-src-googleaisearch-01", "ownerId": "SRC-GOOGLE-AI-SEARCH", "ownerRoute": "/sources/src-google-ai-search/", "ownerType": "source", "proposition": "Google states that ordinary SEO best practices remain relevant and that no additional requirements or special optimizations are necessary for AI Overviews or AI Mode.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of Current Search Central guidance.", "slug": "clm-k03-src-googleaisearch-01", "sourceIds": [ "SRC-GOOGLE-AI-SEARCH" ], "sourceSections": [ { "section": "AI features and your website", "sourceId": "SRC-GOOGLE-AI-SEARCH", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Google states that ordinary SEO best practices remain relevant and that no additional requirements or special optimizations are necessary for AI Overviews or AI Mode.", "url": "https://developers.google.com/search/docs/appearance/ai-features" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-eu-ai-act/#clm-k03-src-euaiact-01", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-EUAIACT-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-euaiact-01.json", "name": "European Union Artificial Intelligence Act information portal — Application timeline", "ownerAnchor": "clm-k03-src-euaiact-01", "ownerId": "SRC-EU-AI-ACT", "ownerRoute": "/sources/src-eu-ai-act/", "ownerType": "source", "proposition": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of EU Artificial Intelligence Act implementation page, updated through 2026-08-14 research cutoff.", "slug": "clm-k03-src-euaiact-01", "sourceIds": [ "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-eu-ai-act/#clm-k03-src-euaiact-02", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-EUAIACT-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-euaiact-02.json", "name": "European Union Artificial Intelligence Act information portal — AI Omnibus simplification timeline", "ownerAnchor": "clm-k03-src-euaiact-02", "ownerId": "SRC-EU-AI-ACT", "ownerRoute": "/sources/src-eu-ai-act/", "ownerType": "source", "proposition": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of EU Artificial Intelligence Act implementation page, updated through 2026-08-14 research cutoff.", "slug": "clm-k03-src-euaiact-02", "sourceIds": [ "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-eu-ai-act/#clm-k03-src-euaiact-03", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-EUAIACT-03", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-euaiact-03.json", "name": "European Union Artificial Intelligence Act information portal — Governance and enforcement", "ownerAnchor": "clm-k03-src-euaiact-03", "ownerId": "SRC-EU-AI-ACT", "ownerRoute": "/sources/src-eu-ai-act/", "ownerType": "source", "proposition": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of EU Artificial Intelligence Act implementation page, updated through 2026-08-14 research cutoff.", "slug": "clm-k03-src-euaiact-03", "sourceIds": [ "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-oecd-ai-principles/#clm-k03-src-oecdaiprinciples-01", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-OECDAIPRINCIPLES-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-oecdaiprinciples-01.json", "name": "OECD AI Principles — Principles overview", "ownerAnchor": "clm-k03-src-oecdaiprinciples-01", "ownerId": "SRC-OECD-AI-PRINCIPLES", "ownerRoute": "/sources/src-oecd-ai-principles/", "ownerType": "source", "proposition": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of OECD AI Principles, May 2024 update.", "slug": "clm-k03-src-oecdaiprinciples-01", "sourceIds": [ "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-rfc-9162/#clm-k03-src-rfc9162-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-RFC9162-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-rfc9162-01.json", "name": "RFC 9162: Certificate Transparency Version 2.0 — RFC status", "ownerAnchor": "clm-k03-src-rfc9162-01", "ownerId": "SRC-RFC-9162", "ownerRoute": "/sources/src-rfc-9162/", "ownerType": "source", "proposition": "RFC 9162 describes Certificate Transparency Version 2.0 and obsoletes RFC 6962.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of RFC 9162.", "slug": "clm-k03-src-rfc9162-01", "sourceIds": [ "SRC-RFC-9162" ], "sourceSections": [ { "section": "RFC status", "sourceId": "SRC-RFC-9162", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "RFC 9162 describes Certificate Transparency Version 2.0 and obsoletes RFC 6962.", "url": "https://www.rfc-editor.org/info/rfc9162/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-rfc-9162/#clm-k03-src-rfc9162-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-RFC9162-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-rfc9162-02.json", "name": "RFC 9162: Certificate Transparency Version 2.0 — Overview", "ownerAnchor": "clm-k03-src-rfc9162-02", "ownerId": "SRC-RFC-9162", "ownerRoute": "/sources/src-rfc-9162/", "ownerType": "source", "proposition": "The protocol supports public logging and audit of certificate issuance; log inclusion does not prove every certificate claim or external event is factually correct.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of RFC 9162.", "slug": "clm-k03-src-rfc9162-02", "sourceIds": [ "SRC-RFC-9162" ], "sourceSections": [ { "section": "Overview", "sourceId": "SRC-RFC-9162", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The protocol supports public logging and audit of certificate issuance; log inclusion does not prove every certificate claim or external event is factually correct.", "url": "https://www.rfc-editor.org/rfc/rfc9162.html#section-1" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-wcag-em2/#clm-k03-src-w3cwcagem2-01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CWCAGEM2-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cwcagem2-01.json", "name": "WCAG Evaluation Methodology (WCAG-EM) 2.0 — Abstract", "ownerAnchor": "clm-k03-src-w3cwcagem2-01", "ownerId": "SRC-W3C-WCAG-EM2", "ownerRoute": "/sources/src-w3c-wcag-em2/", "ownerType": "source", "proposition": "WCAG-EM 2.0 describes a step-by-step methodology to define evaluation scope, explore a digital product, select representative samples, evaluate, and report findings.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of WCAG-EM 2.0.", "slug": "clm-k03-src-w3cwcagem2-01", "sourceIds": [ "SRC-W3C-WCAG-EM2" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-WCAG-EM2", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "WCAG-EM 2.0 describes a step-by-step methodology to define evaluation scope, explore a digital product, select representative samples, evaluate, and report findings.", "url": "https://www.w3.org/TR/wcag-em-2/#abstract" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-wcag-em2/#clm-k03-src-w3cwcagem2-02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CWCAGEM2-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cwcagem2-02.json", "name": "WCAG Evaluation Methodology (WCAG-EM) 2.0 — Status of this document", "ownerAnchor": "clm-k03-src-w3cwcagem2-02", "ownerId": "SRC-W3C-WCAG-EM2", "ownerRoute": "/sources/src-w3c-wcag-em2/", "ownerType": "source", "proposition": "WCAG-EM 2.0 is an informative W3C Group Note and does not define additional WCAG requirements or replace WCAG.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of WCAG-EM 2.0.", "slug": "clm-k03-src-w3cwcagem2-02", "sourceIds": [ "SRC-W3C-WCAG-EM2" ], "sourceSections": [ { "section": "Status of this document", "sourceId": "SRC-W3C-WCAG-EM2", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "WCAG-EM 2.0 is an informative W3C Group Note and does not define additional WCAG requirements or replace WCAG.", "url": "https://www.w3.org/TR/wcag-em-2/#status" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-act-rules-11/#clm-k03-src-w3cactrules11-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CACTRULES11-01", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cactrules11-01.json", "name": "Accessibility Conformance Testing (ACT) Rules Format 1.1 — Abstract", "ownerAnchor": "clm-k03-src-w3cactrules11-01", "ownerId": "SRC-W3C-ACT-RULES-11", "ownerRoute": "/sources/src-w3c-act-rules-11/", "ownerType": "source", "proposition": "ACT Rules Format 1.1 defines a common format for documenting accessibility test rules used by automated tools and manual methodologies.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of ACT Rules Format 1.1.", "slug": "clm-k03-src-w3cactrules11-01", "sourceIds": [ "SRC-W3C-ACT-RULES-11" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-W3C-ACT-RULES-11", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "ACT Rules Format 1.1 defines a common format for documenting accessibility test rules used by automated tools and manual methodologies.", "url": "https://www.w3.org/TR/act-rules-format/#abstract" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-w3c-act-rules-11/#clm-k03-src-w3cactrules11-02", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-SRC-W3CACTRULES11-02", "lastReviewed": "2026-08-14", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-src-w3cactrules11-02.json", "name": "Accessibility Conformance Testing (ACT) Rules Format 1.1 — Status of this document", "ownerAnchor": "clm-k03-src-w3cactrules11-02", "ownerId": "SRC-W3C-ACT-RULES-11", "ownerRoute": "/sources/src-w3c-act-rules-11/", "ownerType": "source", "proposition": "ACT Rules Format 1.1 is a W3C Recommendation published 2026-02-05; it coexists with 1.0 and is not fully backward compatible.", "qualification": "Official publication and exact-section support do not transfer authority beyond the source's scope or prove every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-14", "scope": "Bounded proposition supported by the cited section of ACT Rules Format 1.1.", "slug": "clm-k03-src-w3cactrules11-02", "sourceIds": [ "SRC-W3C-ACT-RULES-11" ], "sourceSections": [ { "section": "Status of this document", "sourceId": "SRC-W3C-ACT-RULES-11", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "ACT Rules Format 1.1 is a W3C Recommendation published 2026-02-05; it coexists with 1.0 and is not fully backward compatible.", "url": "https://www.w3.org/TR/act-rules-format/#sotd" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-distinguishes-preemption-from-prevention/#clm-k04-q-074", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-074", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-074.json", "name": "What distinguishes preemptive action from preventive war?", "ownerAnchor": "clm-k04-q-074", "ownerId": "K01-Q-074", "ownerRoute": "/questions/what-distinguishes-preemption-from-prevention/", "ownerType": "question", "proposition": "Preemptive action is claimed against an imminent, materializing attack when waiting would remove a practical ability to defend; preventive war is directed at a more distant projected threat or future shift in power. The labels are not self-proving. Evidence of capability, intent, timing, necessity, alternatives, proportionality, and competent authority must support the distinction.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for What distinguishes preemptive action from preventive war?", "slug": "clm-k04-q-074", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/when-can-cyber-operation-be-armed-attack/#clm-k04-q-075", "claimStatus": "DISPUTED", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-075", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-075.json", "name": "When can a cyber operation qualify as an armed attack?", "ownerAnchor": "clm-k04-q-075", "ownerId": "K01-Q-075", "ownerRoute": "/questions/when-can-cyber-operation-be-armed-attack/", "ownerType": "question", "proposition": "A cyber operation may qualify as an armed attack when its scale and effects are comparable to serious kinetic force, such as death, injury, physical destruction, or severe disabling effects. States and scholars disagree about some functional, cumulative, and economic effects, so the assessment must identify the exact operation, consequences, attribution, legal position, and current primary authority.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for When can a cyber operation qualify as an armed attack?", "slug": "clm-k04-q-075", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-contextual-imminence-mean-in-cyberspace/#clm-k04-q-076", "claimStatus": "DISPUTED", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-076", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-076.json", "name": "What does contextual imminence mean in cyberspace?", "ownerAnchor": "clm-k04-q-076", "ownerId": "K01-Q-076", "ownerRoute": "/questions/what-does-contextual-imminence-mean-in-cyberspace/", "ownerType": "question", "proposition": "Contextual imminence asks whether capability, hostile intent, target access, probability, anticipated harm, and the last practical window for prevention make action necessary now even when the exact launch time is unknown. It does not permit action based only on general capability or hostility; the evidence and remaining alternatives still require independent review.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for What does contextual imminence mean in cyberspace?", "slug": "clm-k04-q-076", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-unable-or-unwilling-doctrine/#clm-k04-q-077", "claimStatus": "DISPUTED", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-077", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-077.json", "name": "What is the unable or unwilling doctrine?", "ownerAnchor": "clm-k04-q-077", "ownerId": "K01-Q-077", "ownerRoute": "/questions/what-is-unable-or-unwilling-doctrine/", "ownerType": "question", "proposition": "The unable-or-unwilling doctrine is a contested argument that a state may act against a non-state threat in another state's territory when the territorial state cannot or will not suppress it. It is not universally accepted and does not eliminate separate questions of imminence, necessity, proportionality, sovereignty, attribution, reporting, collateral effects, or compensation.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for What is the unable or unwilling doctrine?", "slug": "clm-k04-q-077", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-private-company-lawfully-hack-back/#clm-k04-q-078", "claimStatus": "DISPUTED", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-078", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-078.json", "name": "Can a private company lawfully hack back?", "ownerAnchor": "clm-k04-q-078", "ownerId": "K01-Q-078", "ownerRoute": "/questions/can-private-company-lawfully-hack-back/", "ownerType": "question", "proposition": "Technical capability is not legal authority. Whether a private company may access or disrupt an external system depends on domestic computer-crime law, explicit government authorization, contractual scope, location, target status, international law, effects, oversight, and responsibility. Independent retaliation creates acute attribution, third-party harm, escalation, and liability risks.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for Can a private company lawfully hack back?", "slug": "clm-k04-q-078", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-record-state-responsibility-for-contractor-cyber-operation/#clm-k04-q-079", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-079", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-079.json", "name": "How should state responsibility be recorded for a contractor cyber operation?", "ownerAnchor": "clm-k04-q-079", "ownerId": "K01-Q-079", "ownerRoute": "/questions/how-record-state-responsibility-for-contractor-cyber-operation/", "ownerType": "question", "proposition": "The record should identify the directing state body, legal authority, contract or instruction, operational approval, target and effect limits, command relationship, actual control, deviations, deconfliction, incident handling, and applicable attribution rule. Private execution must not be used to hide state direction or to erase responsibility for foreseeable or ultra vires effects.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for How should state responsibility be recorded for a contractor cyber operation?", "slug": "clm-k04-q-079", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-AI-RMF", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Current revision notice", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST states that AI RMF 1.0 is being revised.", "url": "https://www.nist.gov/artificial-intelligence/ai-standards" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-evidence-required-before-preemptive-cyber-operation/#clm-k04-q-080", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-080", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-080.json", "name": "What evidence is required before a preemptive cyber operation?", "ownerAnchor": "clm-k04-q-080", "ownerId": "K01-Q-080", "ownerRoute": "/questions/what-evidence-required-before-preemptive-cyber-operation/", "ownerType": "question", "proposition": "A defensible record requires reliable attribution, adversary capability, verified hostile intent, target access, expected effects, imminence or last-window analysis, alternatives considered, necessity, proportionality, legal basis, competent approval, third-party infrastructure analysis, deconfliction, abort conditions, logging, and post-action review. Threat labels or intelligence confidence scores alone are insufficient.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for What evidence is required before a preemptive cyber operation?", "slug": "clm-k04-q-080", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-autonomous-cyber-defense-create-legal-authority/#clm-k04-q-081", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-081", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-081.json", "name": "Does autonomous cyber defense create legal authority?", "ownerAnchor": "clm-k04-q-081", "ownerId": "K01-Q-081", "ownerRoute": "/questions/does-autonomous-cyber-defense-create-legal-authority/", "ownerType": "question", "proposition": "No. Autonomy can change speed, persistence, and control architecture, but it does not create jurisdiction, target authority, self-defense, consent, proportionality, or a lawful mandate. The deploying institution and state remain responsible for defining authority, validating inputs, bounding effects, monitoring operation, preserving evidence, and stopping or correcting harmful action.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for Does autonomous cyber defense create legal authority?", "slug": "clm-k04-q-081", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-evaluate-autonomous-security-at-nuclear-infrastructure/#clm-k04-q-082", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-082", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-082.json", "name": "How should autonomous security at nuclear infrastructure be evaluated?", "ownerAnchor": "clm-k04-q-082", "ownerId": "K01-Q-082", "ownerRoute": "/questions/how-evaluate-autonomous-security-at-nuclear-infrastructure/", "ownerType": "question", "proposition": "Evaluate it through a complete safety and security case: threat model, sensing, false-positive and false-negative performance, delay and response timing, cyber resilience, communications denial, fail-safe behavior, lawful authority, human authorization boundaries, aviation and nuclear regulation, rights impacts, testing, independent review, incident response, and evidence of current operation. Cost or response speed alone is not dispositive.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for How should autonomous security at nuclear infrastructure be evaluated?", "slug": "clm-k04-q-082", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-design-basis-threat-authorize-force/#clm-k04-q-083", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-083", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-083.json", "name": "Does a Design Basis Threat authorize the use of force?", "ownerAnchor": "clm-k04-q-083", "ownerId": "K01-Q-083", "ownerRoute": "/questions/does-design-basis-threat-authorize-force/", "ownerType": "question", "proposition": "No. A Design Basis Threat defines adversary assumptions for protection design and evaluation. It does not identify a real attacker, prove imminence, establish target status, create rules of engagement, authorize lethal force, or replace competent legal and operational decision-making.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for Does a Design Basis Threat authorize the use of force?", "slug": "clm-k04-q-083", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-2026-policy-claims-in-research-reports-be-used/#clm-k04-q-084", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-Q-084", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-084.json", "name": "How should time-sensitive 2026 policy claims in research reports be used?", "ownerAnchor": "clm-k04-q-084", "ownerId": "K01-Q-084", "ownerRoute": "/questions/how-should-2026-policy-claims-in-research-reports-be-used/", "ownerType": "question", "proposition": "They should remain attributed source assertions until current primary official records confirm the instrument, date, text, legal status, responsible authority, implementation, and any later correction or repeal. K04 stores the raw reports, publishes bounded syntheses, and does not convert recent policy claims into current law merely because they appear detailed or well cited.", "qualification": "The answer preserves contested legal states and does not create mission authority, target status, or verified current law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 direct answer for How should time-sensitive 2026 policy claims in research reports be used?", "slug": "clm-k04-q-084", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/preemptive-strike-vs-preventive-war/#clm-k04-cmp-025", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-CMP-025", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-025.json", "name": "Preemptive strike versus Preventive war", "ownerAnchor": "clm-k04-cmp-025", "ownerId": "K01-CMP-025", "ownerRoute": "/comparisons/preemptive-strike-vs-preventive-war/", "ownerType": "comparison", "proposition": "Preemption is claimed against an imminent, materializing attack and depends on necessity and proportionality; prevention targets a more distant projected threat or future shift in power.", "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 canonical distinction between Preemptive strike and Preventive war.", "slug": "clm-k04-cmp-025", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/self-defense-vs-countermeasures-in-cyberspace/#clm-k04-cmp-026", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-CMP-026", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-026.json", "name": "Self-defense versus Countermeasures", "ownerAnchor": "clm-k04-cmp-026", "ownerId": "K01-CMP-026", "ownerRoute": "/comparisons/self-defense-vs-countermeasures-in-cyberspace/", "ownerType": "comparison", "proposition": "Self-defense responds to an armed attack or claimed imminent armed attack and may involve force; countermeasures are otherwise unlawful, non-forcible measures directed against a responsible state to induce compliance after an internationally wrongful act.", "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 canonical distinction between Self-defense and Countermeasures.", "slug": "clm-k04-cmp-026", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/cyber-sovereignty-vs-non-intervention/#clm-k04-cmp-027", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-CMP-027", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-027.json", "name": "Cyber sovereignty versus Prohibition of intervention", "ownerAnchor": "clm-k04-cmp-027", "ownerId": "K01-CMP-027", "ownerRoute": "/comparisons/cyber-sovereignty-vs-non-intervention/", "ownerType": "comparison", "proposition": "Sovereignty concerns territorial integrity, infrastructure, governmental functions, and state authority; prohibited intervention additionally requires coercive interference in matters a state is entitled to decide freely.", "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 canonical distinction between Cyber sovereignty and Prohibition of intervention.", "slug": "clm-k04-cmp-027", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/active-cyber-defense-vs-hack-back/#clm-k04-cmp-028", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-CMP-028", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-028.json", "name": "Active cyber defense versus Hack-back", "ownerAnchor": "clm-k04-cmp-028", "ownerId": "K01-CMP-028", "ownerRoute": "/comparisons/active-cyber-defense-vs-hack-back/", "ownerType": "comparison", "proposition": "Active cyber defense is a broad spectrum that can include lawful internal deception, consent-based hunting, and government disruption; hack-back commonly refers to external access or retaliation and raises sharper authorization and third-party-risk questions.", "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 canonical distinction between Active cyber defense and Hack-back.", "slug": "clm-k04-cmp-028", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/autonomous-defense-vs-remote-operation/#clm-k04-cmp-029", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-CMP-029", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-029.json", "name": "Autonomous defense versus Remote operation", "ownerAnchor": "clm-k04-cmp-029", "ownerId": "K01-CMP-029", "ownerRoute": "/comparisons/autonomous-defense-vs-remote-operation/", "ownerType": "comparison", "proposition": "Autonomous defense makes selected decisions locally without a contemporaneous remote operator; remote operation keeps a human or external controller in the action loop but depends on communications, latency, and operator awareness.", "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 canonical distinction between Autonomous defense and Remote operation.", "slug": "clm-k04-cmp-029", "sourceIds": [ "SRC-NIST-SSDF", "SRC-NIST-800-53", "SRC-SLSA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Specification status", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA v1.2 is an approved specification for incrementally improving software supply-chain security.", "url": "https://slsa.dev/spec/v1.2/" }, { "section": "Build requirements", "sourceId": "SRC-SLSA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SLSA levels and provenance requirements qualify build evidence; they do not prove that a deployed service is currently operating.", "url": "https://slsa.dev/spec/v1.2/build-requirements" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/design-basis-threat-vs-rules-of-engagement/#clm-k04-cmp-030", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-CMP-030", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-030.json", "name": "Design Basis Threat versus Rules of Engagement", "ownerAnchor": "clm-k04-cmp-030", "ownerId": "K01-CMP-030", "ownerRoute": "/comparisons/design-basis-threat-vs-rules-of-engagement/", "ownerType": "comparison", "proposition": "A Design Basis Threat defines adversary assumptions for protective design; Rules of Engagement define lawful mission circumstances and limits for initiating or continuing force.", "qualification": "The matrix prevents category error but does not decide a mission-specific or jurisdiction-specific case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K04 canonical distinction between Design Basis Threat and Rules of Engagement.", "slug": "clm-k04-cmp-030", "sourceIds": [ "SRC-EU-AI-ACT", "SRC-OECD-AI-PRINCIPLES" ], "sourceSections": [ { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" }, { "section": "AI Omnibus simplification timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The AI Omnibus entered into force on 2026-07-27 and set 2027-12-02 and 2028-08-02 dates for specified high-risk categories.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#how-has-the-commission-simplified-the-implementation-of-the-ai-act" }, { "section": "Governance and enforcement", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "From 2026-08-02 the AI Office and Member State authorities are responsible for implementation, supervision, and enforcement under the official timeline.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#governance-and-enforcement" }, { "section": "Principles overview", "sourceId": "SRC-OECD-AI-PRINCIPLES", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The principles promote innovative and trustworthy AI consistent with human rights and democratic values and guide policy development.", "url": "https://oecd.ai/en/ai-principles" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/critical-datacenter-protection/#clm-k04-top-017-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-017-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-017-a.json", "name": "Critical Datacenter Protection — Direct definition", "ownerAnchor": "clm-k04-top-017-a", "ownerId": "K04-TOPIC-017", "ownerRoute": "/knowledge/critical-datacenter-protection/", "ownerType": "topic", "proposition": "Critical datacenter protection is the integrated assurance discipline for keeping compute, cooling, power, communications, identity, safety, and recovery functions available under cyber, physical, electromagnetic, supply-chain, and insider attack.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 definition of Critical Datacenter Protection.", "slug": "clm-k04-top-017-a", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/critical-datacenter-protection/#clm-k04-top-017-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-017-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-017-b.json", "name": "Critical Datacenter Protection — Current law or standards", "ownerAnchor": "clm-k04-top-017-b", "ownerId": "K04-TOPIC-017", "ownerRoute": "/knowledge/critical-datacenter-protection/", "ownerType": "topic", "proposition": "Applicable obligations depend on facility type, sector, ownership, grid interconnection, nuclear licensing, communications, aviation, privacy, labor, procurement, and any governmental mission authority.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Current-law or standards boundary for Critical Datacenter Protection through the declared research cutoff.", "slug": "clm-k04-top-017-b", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/critical-datacenter-protection/#clm-k04-top-017-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-017-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-017-c.json", "name": "Critical Datacenter Protection — Project doctrine", "ownerAnchor": "clm-k04-top-017-c", "ownerId": "K04-TOPIC-017", "ownerRoute": "/knowledge/critical-datacenter-protection/", "ownerType": "topic", "proposition": "Project doctrine treats the campus as one cyber-physical system and designs protection from unacceptable consequences backward, while keeping defensive automation, use-of-force authority, and external cyber effects under separate controls.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Normative K04 position for Critical Datacenter Protection.", "slug": "clm-k04-top-017-c", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/nuclear-powered-compute/#clm-k04-top-018-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-018-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-018-a.json", "name": "Nuclear-Powered Compute — Direct definition", "ownerAnchor": "clm-k04-top-018-a", "ownerId": "K04-TOPIC-018", "ownerRoute": "/knowledge/nuclear-powered-compute/", "ownerType": "topic", "proposition": "Nuclear-powered compute combines datacenter infrastructure with reliable nuclear generation or contracted nuclear output; the energy relationship can improve continuity while creating new cyber-physical, regulatory, grid, and protection dependencies.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 definition of Nuclear-Powered Compute.", "slug": "clm-k04-top-018-a", "sourceIds": [ "SRC-GOOGLE-KAIROS-2024", "SRC-CONSTELLATION-MICROSOFT-2024", "SRC-CONSTELLATION-META-2025", "SRC-NRC-10CFR-73-54", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY" ], "sourceSections": [ { "section": "Agreement and timeline", "sourceId": "SRC-GOOGLE-KAIROS-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Google states that the agreement is intended to enable up to 500 MW of 24/7 carbon-free power, beginning with a first SMR targeted for 2030.", "url": "https://blog.google/company-news/outreach-and-initiatives/sustainability/google-kairos-power-nuclear-energy-agreement/" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-MICROSOFT-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation describes a 20-year Microsoft PPA supporting restart and approximately 835 MW of carbon-free grid output.", "url": "https://www.constellationenergy.com/news/2024/Constellation-to-Launch-Crane-Clean-Energy-Center-Restoring-Jobs-and-Carbon-Free-Power-to-The-Grid.html" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-META-2025", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation and Meta announced a 20-year agreement for 1,121 MW of emissions-free nuclear output beginning in 2027.", "url": "https://www.constellationenergy.com/news/2025/constellation-meta-sign-20-year-deal-for-clean-reliable-nuclear-energy-in-illinois.html" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/nuclear-powered-compute/#clm-k04-top-018-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-018-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-018-b.json", "name": "Nuclear-Powered Compute — Current law or standards", "ownerAnchor": "clm-k04-top-018-b", "ownerId": "K04-TOPIC-018", "ownerRoute": "/knowledge/nuclear-powered-compute/", "ownerType": "topic", "proposition": "Nuclear safety, physical protection, cyber security, environmental, grid-reliability, emergency-planning, siting, and market rules remain jurisdiction-specific and design-specific.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Current-law or standards boundary for Nuclear-Powered Compute through the declared research cutoff.", "slug": "clm-k04-top-018-b", "sourceIds": [ "SRC-GOOGLE-KAIROS-2024", "SRC-CONSTELLATION-MICROSOFT-2024", "SRC-CONSTELLATION-META-2025", "SRC-NRC-10CFR-73-54", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY" ], "sourceSections": [ { "section": "Agreement and timeline", "sourceId": "SRC-GOOGLE-KAIROS-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Google states that the agreement is intended to enable up to 500 MW of 24/7 carbon-free power, beginning with a first SMR targeted for 2030.", "url": "https://blog.google/company-news/outreach-and-initiatives/sustainability/google-kairos-power-nuclear-energy-agreement/" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-MICROSOFT-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation describes a 20-year Microsoft PPA supporting restart and approximately 835 MW of carbon-free grid output.", "url": "https://www.constellationenergy.com/news/2024/Constellation-to-Launch-Crane-Clean-Energy-Center-Restoring-Jobs-and-Carbon-Free-Power-to-The-Grid.html" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-META-2025", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation and Meta announced a 20-year agreement for 1,121 MW of emissions-free nuclear output beginning in 2027.", "url": "https://www.constellationenergy.com/news/2025/constellation-meta-sign-20-year-deal-for-clean-reliable-nuclear-energy-in-illinois.html" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/nuclear-powered-compute/#clm-k04-top-018-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-018-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-018-c.json", "name": "Nuclear-Powered Compute — Project doctrine", "ownerAnchor": "clm-k04-top-018-c", "ownerId": "K04-TOPIC-018", "ownerRoute": "/knowledge/nuclear-powered-compute/", "ownerType": "topic", "proposition": "Project doctrine treats nuclear power as a mission-continuity option, not a security exemption. Co-location requires stronger separation, consequence engineering, test evidence, and recovery planning than an ordinary campus.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Normative K04 position for Nuclear-Powered Compute.", "slug": "clm-k04-top-018-c", "sourceIds": [ "SRC-GOOGLE-KAIROS-2024", "SRC-CONSTELLATION-MICROSOFT-2024", "SRC-CONSTELLATION-META-2025", "SRC-NRC-10CFR-73-54", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY" ], "sourceSections": [ { "section": "Agreement and timeline", "sourceId": "SRC-GOOGLE-KAIROS-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Google states that the agreement is intended to enable up to 500 MW of 24/7 carbon-free power, beginning with a first SMR targeted for 2030.", "url": "https://blog.google/company-news/outreach-and-initiatives/sustainability/google-kairos-power-nuclear-energy-agreement/" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-MICROSOFT-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation describes a 20-year Microsoft PPA supporting restart and approximately 835 MW of carbon-free grid output.", "url": "https://www.constellationenergy.com/news/2024/Constellation-to-Launch-Crane-Clean-Energy-Center-Restoring-Jobs-and-Carbon-Free-Power-to-The-Grid.html" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-META-2025", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation and Meta announced a 20-year agreement for 1,121 MW of emissions-free nuclear output beginning in 2027.", "url": "https://www.constellationenergy.com/news/2025/constellation-meta-sign-20-year-deal-for-clean-reliable-nuclear-energy-in-illinois.html" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/autonomous-cyber-defense/#clm-k04-top-019-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-019-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-019-a.json", "name": "Autonomous Cyber Defense — Direct definition", "ownerAnchor": "clm-k04-top-019-a", "ownerId": "K04-TOPIC-019", "ownerRoute": "/knowledge/autonomous-cyber-defense/", "ownerType": "topic", "proposition": "Autonomous cyber defense uses machine-speed systems to observe, correlate, prioritize, contain, reconfigure, restore, and learn within pre-authorized defensive boundaries.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 definition of Autonomous Cyber Defense.", "slug": "clm-k04-top-019-a", "sourceIds": [ "SRC-WH-EO-14409", "SRC-WH-GOLD-EAGLE-2026", "SRC-USAASC-CYBER-WARFARE-2026", "SRC-NIST-800-207", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1 — Purpose", "sourceId": "SRC-WH-EO-14409", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.", "url": "https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" }, { "section": "Program description", "sourceId": "SRC-WH-GOLD-EAGLE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/autonomous-cyber-defense/#clm-k04-top-019-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-019-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-019-b.json", "name": "Autonomous Cyber Defense — Current law or standards", "ownerAnchor": "clm-k04-top-019-b", "ownerId": "K04-TOPIC-019", "ownerRoute": "/knowledge/autonomous-cyber-defense/", "ownerType": "topic", "proposition": "Internal defensive automation is bounded by ownership, contract, privacy, sector regulation, labor obligations, safety duties, and any restrictions on interception, monitoring, or external access.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Current-law or standards boundary for Autonomous Cyber Defense through the declared research cutoff.", "slug": "clm-k04-top-019-b", "sourceIds": [ "SRC-WH-EO-14409", "SRC-WH-GOLD-EAGLE-2026", "SRC-USAASC-CYBER-WARFARE-2026", "SRC-NIST-800-207", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1 — Purpose", "sourceId": "SRC-WH-EO-14409", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.", "url": "https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" }, { "section": "Program description", "sourceId": "SRC-WH-GOLD-EAGLE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/autonomous-cyber-defense/#clm-k04-top-019-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-019-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-019-c.json", "name": "Autonomous Cyber Defense — Project doctrine", "ownerAnchor": "clm-k04-top-019-c", "ownerId": "K04-TOPIC-019", "ownerRoute": "/knowledge/autonomous-cyber-defense/", "ownerType": "topic", "proposition": "Project doctrine favors high-speed autonomous defense inside owned or expressly authorized environments, with progressive action tiers, fail-safe defaults, independent verification, and no implied authority to enter third-party systems.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Normative K04 position for Autonomous Cyber Defense.", "slug": "clm-k04-top-019-c", "sourceIds": [ "SRC-WH-EO-14409", "SRC-WH-GOLD-EAGLE-2026", "SRC-USAASC-CYBER-WARFARE-2026", "SRC-NIST-800-207", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1 — Purpose", "sourceId": "SRC-WH-EO-14409", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.", "url": "https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" }, { "section": "Program description", "sourceId": "SRC-WH-GOLD-EAGLE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/cyber-physical-mission-assurance/#clm-k04-top-020-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-020-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-020-a.json", "name": "Cyber-Physical Mission Assurance — Direct definition", "ownerAnchor": "clm-k04-top-020-a", "ownerId": "K04-TOPIC-020", "ownerRoute": "/knowledge/cyber-physical-mission-assurance/", "ownerType": "topic", "proposition": "Cyber-physical mission assurance protects the functions that must continue when digital compromise can create physical damage, unsafe control, loss of power, or loss of cooling.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 definition of Cyber-Physical Mission Assurance.", "slug": "clm-k04-top-020-a", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/cyber-physical-mission-assurance/#clm-k04-top-020-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-020-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-020-b.json", "name": "Cyber-Physical Mission Assurance — Current law or standards", "ownerAnchor": "clm-k04-top-020-b", "ownerId": "K04-TOPIC-020", "ownerRoute": "/knowledge/cyber-physical-mission-assurance/", "ownerType": "topic", "proposition": "Safety, reliability, nuclear, grid, occupational, environmental, and emergency obligations can impose different priorities and decision authorities on the same event.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Current-law or standards boundary for Cyber-Physical Mission Assurance through the declared research cutoff.", "slug": "clm-k04-top-020-b", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/cyber-physical-mission-assurance/#clm-k04-top-020-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-020-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-020-c.json", "name": "Cyber-Physical Mission Assurance — Project doctrine", "ownerAnchor": "clm-k04-top-020-c", "ownerId": "K04-TOPIC-020", "ownerRoute": "/knowledge/cyber-physical-mission-assurance/", "ownerType": "topic", "proposition": "Project doctrine requires consequence-aware arbitration: safety boundaries cannot be overridden by mission software, while defensive actions must be tested against physical effects before deployment.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Normative K04 position for Cyber-Physical Mission Assurance.", "slug": "clm-k04-top-020-c", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/autonomous-physical-security/#clm-k04-top-021-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-021-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-021-a.json", "name": "Autonomous Physical Security — Direct definition", "ownerAnchor": "clm-k04-top-021-a", "ownerId": "K04-TOPIC-021", "ownerRoute": "/knowledge/autonomous-physical-security/", "ownerType": "topic", "proposition": "Autonomous physical security combines edge sensing, sensor fusion, access control, tracking, barriers, communications, and evidence capture to detect, assess, delay, and route response at machine speed.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 definition of Autonomous Physical Security.", "slug": "clm-k04-top-021-a", "sourceIds": [ "SRC-NRC-10CFR-73-55", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "SRC-DODD-3000-09" ], "sourceSections": [ { "section": "General performance objective and requirements", "sourceId": "SRC-NRC-10CFR-73-55", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Nuclear power reactor licensees must establish and maintain a physical protection program against radiological sabotage with defined detection, assessment, delay, and response functions.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.55" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" }, { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/autonomous-physical-security/#clm-k04-top-021-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-021-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-021-b.json", "name": "Autonomous Physical Security — Current law or standards", "ownerAnchor": "clm-k04-top-021-b", "ownerId": "K04-TOPIC-021", "ownerRoute": "/knowledge/autonomous-physical-security/", "ownerType": "topic", "proposition": "Private facilities generally do not gain unrestricted authority to jam, destroy aircraft, use deadly force, or conduct military operations merely because they own critical property.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Current-law or standards boundary for Autonomous Physical Security through the declared research cutoff.", "slug": "clm-k04-top-021-b", "sourceIds": [ "SRC-NRC-10CFR-73-55", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "SRC-DODD-3000-09" ], "sourceSections": [ { "section": "General performance objective and requirements", "sourceId": "SRC-NRC-10CFR-73-55", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Nuclear power reactor licensees must establish and maintain a physical protection program against radiological sabotage with defined detection, assessment, delay, and response functions.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.55" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" }, { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/autonomous-physical-security/#clm-k04-top-021-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-021-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-021-c.json", "name": "Autonomous Physical Security — Project doctrine", "ownerAnchor": "clm-k04-top-021-c", "ownerId": "K04-TOPIC-021", "ownerRoute": "/knowledge/autonomous-physical-security/", "ownerType": "topic", "proposition": "Project doctrine prioritizes detection, classification confidence, non-destructive protection, physical delay, evidence capture, and integration with competent authorities; lethal or destructive effects require separate lawful authority and tested rules.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Normative K04 position for Autonomous Physical Security.", "slug": "clm-k04-top-021-c", "sourceIds": [ "SRC-NRC-10CFR-73-55", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "SRC-DODD-3000-09" ], "sourceSections": [ { "section": "General performance objective and requirements", "sourceId": "SRC-NRC-10CFR-73-55", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Nuclear power reactor licensees must establish and maintain a physical protection program against radiological sabotage with defined detection, assessment, delay, and response functions.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.55" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" }, { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/authorized-cyber-effects/#clm-k04-top-022-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-022-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-022-a.json", "name": "Authorized Cyber Effects — Direct definition", "ownerAnchor": "clm-k04-top-022-a", "ownerId": "K04-TOPIC-022", "ownerRoute": "/knowledge/authorized-cyber-effects/", "ownerType": "topic", "proposition": "Authorized cyber effects are externally directed cyber actions performed under a specific legal mandate, written mission authority, target and effect limits, deconfliction, oversight, abort rules, and accountability.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 definition of Authorized Cyber Effects.", "slug": "clm-k04-top-022-a", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Section 2 — Establishing the Program", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Defined operations and limitations", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/authorized-cyber-effects/#clm-k04-top-022-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-022-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-022-b.json", "name": "Authorized Cyber Effects — Current law or standards", "ownerAnchor": "clm-k04-top-022-b", "ownerId": "K04-TOPIC-022", "ownerRoute": "/knowledge/authorized-cyber-effects/", "ownerType": "topic", "proposition": "Domestic authorization does not automatically settle sovereignty, non-intervention, use-of-force, countermeasure, self-defense, privacy, or third-party-infrastructure questions under international or foreign law.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Current-law or standards boundary for Authorized Cyber Effects through the declared research cutoff.", "slug": "clm-k04-top-022-b", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Section 2 — Establishing the Program", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Defined operations and limitations", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/authorized-cyber-effects/#clm-k04-top-022-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-022-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-022-c.json", "name": "Authorized Cyber Effects — Project doctrine", "ownerAnchor": "clm-k04-top-022-c", "ownerId": "K04-TOPIC-022", "ownerRoute": "/knowledge/authorized-cyber-effects/", "ownerType": "topic", "proposition": "Project doctrine is defense-first, authorization-bound, and effects-capable. Capability is offered only for lawful missions under competent direction; independent hack-back and uncontrolled autonomous propagation are excluded.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Normative K04 position for Authorized Cyber Effects.", "slug": "clm-k04-top-022-c", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Section 2 — Establishing the Program", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Defined operations and limitations", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/adversarial-simulation/#clm-k04-top-023-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-023-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-023-a.json", "name": "Adversarial Simulation and Test — Direct definition", "ownerAnchor": "clm-k04-top-023-a", "ownerId": "K04-TOPIC-023", "ownerRoute": "/knowledge/adversarial-simulation/", "ownerType": "topic", "proposition": "Adversarial simulation is the controlled use of digital twins, cyber ranges, hardware-in-the-loop environments, threat emulation, and red-team analysis to expose failure before deployment.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 definition of Adversarial Simulation and Test.", "slug": "clm-k04-top-023-a", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/adversarial-simulation/#clm-k04-top-023-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-023-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-023-b.json", "name": "Adversarial Simulation and Test — Current law or standards", "ownerAnchor": "clm-k04-top-023-b", "ownerId": "K04-TOPIC-023", "ownerRoute": "/knowledge/adversarial-simulation/", "ownerType": "topic", "proposition": "Testing still requires authorization, data protection, export-control review, safety controls, labor and privacy compliance, and separation from unauthorized third-party systems.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Current-law or standards boundary for Adversarial Simulation and Test through the declared research cutoff.", "slug": "clm-k04-top-023-b", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/adversarial-simulation/#clm-k04-top-023-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-023-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-023-c.json", "name": "Adversarial Simulation and Test — Project doctrine", "ownerAnchor": "clm-k04-top-023-c", "ownerId": "K04-TOPIC-023", "ownerRoute": "/knowledge/adversarial-simulation/", "ownerType": "topic", "proposition": "Project doctrine treats simulation as evidence of bounded performance, not proof of deployment or operation. Readiness advances only when the test environment, assumptions, results, defects, and residual risks are inspectable.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Normative K04 position for Adversarial Simulation and Test.", "slug": "clm-k04-top-023-c", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/autonomous-warfare-systems/#clm-k04-top-024-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-024-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-024-a.json", "name": "Autonomous Warfare Systems — Direct definition", "ownerAnchor": "clm-k04-top-024-a", "ownerId": "K04-TOPIC-024", "ownerRoute": "/knowledge/autonomous-warfare-systems/", "ownerType": "topic", "proposition": "Autonomous warfare systems combine machine perception, decision support, coordination, cyber, electromagnetic, and uncrewed platforms to act at operational speed under defined mission and legal constraints.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 definition of Autonomous Warfare Systems.", "slug": "clm-k04-top-024-a", "sourceIds": [ "SRC-DODD-3000-09", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/autonomous-warfare-systems/#clm-k04-top-024-b", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-024-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-024-b.json", "name": "Autonomous Warfare Systems — Current law or standards", "ownerAnchor": "clm-k04-top-024-b", "ownerId": "K04-TOPIC-024", "ownerRoute": "/knowledge/autonomous-warfare-systems/", "ownerType": "topic", "proposition": "Autonomous and semi-autonomous weapon systems remain subject to applicable domestic and international law, system approval, testing, rules of engagement, and human judgment requirements of the responsible authority.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Current-law or standards boundary for Autonomous Warfare Systems through the declared research cutoff.", "slug": "clm-k04-top-024-b", "sourceIds": [ "SRC-DODD-3000-09", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/autonomous-warfare-systems/#clm-k04-top-024-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-TOP-024-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-top-024-c.json", "name": "Autonomous Warfare Systems — Project doctrine", "ownerAnchor": "clm-k04-top-024-c", "ownerId": "K04-TOPIC-024", "ownerRoute": "/knowledge/autonomous-warfare-systems/", "ownerType": "topic", "proposition": "Project doctrine studies and engineers autonomy for protection, resilience, sensing, coordination, and authorized missions while rejecting claims that technical autonomy itself creates target authority or permission to use force.", "qualification": "Sources support only bounded elements; technical capability, current law, project doctrine, target authority, deployment, and factual truth remain separate.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Normative K04 position for Autonomous Warfare Systems.", "slug": "clm-k04-top-024-c", "sourceIds": [ "SRC-DODD-3000-09", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-do-nuclear-powered-datacenters-need-a-different-security-architecture/#clm-k04-q-085", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-085", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-085.json", "name": "Why do nuclear-powered datacenters need a different security architecture?", "ownerAnchor": "clm-k04-q-085", "ownerId": "K04-Q-085", "ownerRoute": "/questions/why-do-nuclear-powered-datacenters-need-a-different-security-architecture/", "ownerType": "question", "proposition": "They combine high-availability compute with safety-critical power, cooling, grid, physical-protection, and regulatory systems. A failure can cross from data loss into physical consequence, so the architecture must protect critical functions through deterministic separation, consequence engineering, bounded autonomy, and tested recovery rather than relying on ordinary enterprise controls.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for Why do nuclear-powered datacenters need a different security architecture?", "slug": "clm-k04-q-085", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-the-project-position-on-critical-datacenter-defense/#clm-k04-q-086", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-086", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-086.json", "name": "What is the project position on critical datacenter defense?", "ownerAnchor": "clm-k04-q-086", "ownerId": "K04-Q-086", "ownerRoute": "/questions/what-is-the-project-position-on-critical-datacenter-defense/", "ownerType": "question", "proposition": "The position is defense-first, authorization-bound, and effects-capable: engineer the campus so attacks fail, recover under pressure, and maintain the governed capacity to support lawful externally directed missions without equating capability with authority.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for What is the project position on critical datacenter defense?", "slug": "clm-k04-q-086", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-makes-autonomous-defense-safe-enough-for-ot/#clm-k04-q-087", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-087", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-087.json", "name": "What makes autonomous defense safe enough for operational technology?", "ownerAnchor": "clm-k04-q-087", "ownerId": "K04-Q-087", "ownerRoute": "/questions/what-makes-autonomous-defense-safe-enough-for-ot/", "ownerType": "question", "proposition": "No single model makes it safe. Safety requires consequence-based scope, independent protective systems, progressive response tiers, reversible containment, deterministic action limits, physical-process validation, runtime assurance, signed evidence, and an tested path to stop or recover the automation.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for What makes autonomous defense safe enough for operational technology?", "slug": "clm-k04-q-087", "sourceIds": [ "SRC-WH-EO-14409", "SRC-WH-GOLD-EAGLE-2026", "SRC-USAASC-CYBER-WARFARE-2026", "SRC-NIST-800-207", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1 — Purpose", "sourceId": "SRC-WH-EO-14409", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.", "url": "https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" }, { "section": "Program description", "sourceId": "SRC-WH-GOLD-EAGLE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-an-autonomous-defender-act-without-human-approval/#clm-k04-q-088", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-088", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-088.json", "name": "Can an autonomous cyber defender act without human approval?", "ownerAnchor": "clm-k04-q-088", "ownerId": "K04-Q-088", "ownerRoute": "/questions/can-an-autonomous-defender-act-without-human-approval/", "ownerType": "question", "proposition": "It can execute pre-authorized internal defensive actions whose targets, effects, duration, reversibility, and safety limits were approved in advance. Actions outside that envelope require competent authorization; external access or destructive effects are not implied by defensive autonomy.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for Can an autonomous cyber defender act without human approval?", "slug": "clm-k04-q-088", "sourceIds": [ "SRC-WH-EO-14409", "SRC-WH-GOLD-EAGLE-2026", "SRC-USAASC-CYBER-WARFARE-2026", "SRC-NIST-800-207", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1 — Purpose", "sourceId": "SRC-WH-EO-14409", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.", "url": "https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" }, { "section": "Program description", "sourceId": "SRC-WH-GOLD-EAGLE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-false-positives-be-managed-in-nuclear-ot/#clm-k04-q-089", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-089", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-089.json", "name": "How should false positives be managed in nuclear and other high-consequence OT?", "ownerAnchor": "clm-k04-q-089", "ownerId": "K04-Q-089", "ownerRoute": "/questions/how-should-false-positives-be-managed-in-nuclear-ot/", "ownerType": "question", "proposition": "The response design must compare the harm of acting with the harm of waiting, use independent corroboration, preserve safety systems, prefer reversible containment, simulate physical consequences, and automatically stop escalation when confidence or system state leaves the approved envelope.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for How should false positives be managed in nuclear and other high-consequence OT?", "slug": "clm-k04-q-089", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-critical-function-assurance-protect/#clm-k04-q-090", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-090", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-090.json", "name": "What does Critical Function Assurance protect?", "ownerAnchor": "clm-k04-q-090", "ownerId": "K04-Q-090", "ownerRoute": "/questions/what-does-critical-function-assurance-protect/", "ownerType": "question", "proposition": "It protects the ability to perform essential safety and mission functions despite compromise. It begins with unacceptable consequences and maps the digital, physical, power, cooling, identity, timing, communications, and human dependencies that could cause them.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for What does Critical Function Assurance protect?", "slug": "clm-k04-q-090", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-nuclear-power-make-a-datacenter-grid-independent/#clm-k04-q-091", "claimStatus": "REASONED INFERENCE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-091", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-091.json", "name": "Does nuclear power make a datacenter grid-independent?", "ownerAnchor": "clm-k04-q-091", "ownerId": "K04-Q-091", "ownerRoute": "/questions/does-nuclear-power-make-a-datacenter-grid-independent/", "ownerType": "question", "proposition": "Not by itself. A campus may use dedicated or contracted nuclear output, but continuity still depends on plant design, interconnection, load rejection, maintenance, fuel, cooling, substations, communications, licensing, emergency systems, and tested islanding or black-start capability.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for Does nuclear power make a datacenter grid-independent?", "slug": "clm-k04-q-091", "sourceIds": [ "SRC-GOOGLE-KAIROS-2024", "SRC-CONSTELLATION-MICROSOFT-2024", "SRC-CONSTELLATION-META-2025", "SRC-NRC-10CFR-73-54", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY" ], "sourceSections": [ { "section": "Agreement and timeline", "sourceId": "SRC-GOOGLE-KAIROS-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Google states that the agreement is intended to enable up to 500 MW of 24/7 carbon-free power, beginning with a first SMR targeted for 2030.", "url": "https://blog.google/company-news/outreach-and-initiatives/sustainability/google-kairos-power-nuclear-energy-agreement/" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-MICROSOFT-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation describes a 20-year Microsoft PPA supporting restart and approximately 835 MW of carbon-free grid output.", "url": "https://www.constellationenergy.com/news/2024/Constellation-to-Launch-Crane-Clean-Energy-Center-Restoring-Jobs-and-Carbon-Free-Power-to-The-Grid.html" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-META-2025", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation and Meta announced a 20-year agreement for 1,121 MW of emissions-free nuclear output beginning in 2027.", "url": "https://www.constellationenergy.com/news/2025/constellation-meta-sign-20-year-deal-for-clean-reliable-nuclear-energy-in-illinois.html" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-the-minimum-cyber-boundary-between-reactor-and-datacenter/#clm-k04-q-092", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-092", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-092.json", "name": "What is the minimum cyber boundary between a reactor and a datacenter?", "ownerAnchor": "clm-k04-q-092", "ownerId": "K04-Q-092", "ownerRoute": "/questions/what-is-the-minimum-cyber-boundary-between-reactor-and-datacenter/", "ownerType": "question", "proposition": "The exact design is licensing- and architecture-specific, but the baseline principle is that safety and protection functions must not depend on an unrestricted bidirectional path from the datacenter. Higher-consequence zones require deterministic flow control, separate identities, independent safety, and validated data mediation.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for What is the minimum cyber boundary between a reactor and a datacenter?", "slug": "clm-k04-q-092", "sourceIds": [ "SRC-GOOGLE-KAIROS-2024", "SRC-CONSTELLATION-MICROSOFT-2024", "SRC-CONSTELLATION-META-2025", "SRC-NRC-10CFR-73-54", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY" ], "sourceSections": [ { "section": "Agreement and timeline", "sourceId": "SRC-GOOGLE-KAIROS-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Google states that the agreement is intended to enable up to 500 MW of 24/7 carbon-free power, beginning with a first SMR targeted for 2030.", "url": "https://blog.google/company-news/outreach-and-initiatives/sustainability/google-kairos-power-nuclear-energy-agreement/" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-MICROSOFT-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation describes a 20-year Microsoft PPA supporting restart and approximately 835 MW of carbon-free grid output.", "url": "https://www.constellationenergy.com/news/2024/Constellation-to-Launch-Crane-Clean-Energy-Center-Restoring-Jobs-and-Carbon-Free-Power-to-The-Grid.html" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-META-2025", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation and Meta announced a 20-year agreement for 1,121 MW of emissions-free nuclear output beginning in 2027.", "url": "https://www.constellationenergy.com/news/2025/constellation-meta-sign-20-year-deal-for-clean-reliable-nuclear-energy-in-illinois.html" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-counter-uas-be-positioned-for-critical-infrastructure/#clm-k04-q-093", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-093", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-093.json", "name": "How should counter-UAS capability be positioned for critical infrastructure?", "ownerAnchor": "clm-k04-q-093", "ownerId": "K04-Q-093", "ownerRoute": "/questions/how-should-counter-uas-be-positioned-for-critical-infrastructure/", "ownerType": "question", "proposition": "As a layered sensing, classification, tracking, evidence, delay, and authority-integration capability. Detection does not itself authorize jamming or destruction, so the system must distinguish awareness, non-destructive protection, and any separately authorized mitigation.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for How should counter-UAS capability be positioned for critical infrastructure?", "slug": "clm-k04-q-093", "sourceIds": [ "SRC-NRC-10CFR-73-55", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "SRC-DODD-3000-09" ], "sourceSections": [ { "section": "General performance objective and requirements", "sourceId": "SRC-NRC-10CFR-73-55", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Nuclear power reactor licensees must establish and maintain a physical protection program against radiological sabotage with defined detection, assessment, delay, and response functions.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.55" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" }, { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-a-private-datacenter-use-autonomous-lethal-force/#clm-k04-q-094", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-094", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-094.json", "name": "Can a private datacenter use autonomous lethal force to protect property?", "ownerAnchor": "clm-k04-q-094", "ownerId": "K04-Q-094", "ownerRoute": "/questions/can-a-private-datacenter-use-autonomous-lethal-force/", "ownerType": "question", "proposition": "Technical ability and criticality do not create unrestricted legal authority. Any use of force is jurisdiction- and circumstance-specific; autonomous or destructive systems require competent authorization, tested safeguards, rules of engagement where applicable, and compliance with criminal, tort, aviation, nuclear, and human-rights law.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for Can a private datacenter use autonomous lethal force to protect property?", "slug": "clm-k04-q-094", "sourceIds": [ "SRC-NRC-10CFR-73-55", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "SRC-DODD-3000-09" ], "sourceSections": [ { "section": "General performance objective and requirements", "sourceId": "SRC-NRC-10CFR-73-55", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Nuclear power reactor licensees must establish and maintain a physical protection program against radiological sabotage with defined detection, assessment, delay, and response functions.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.55" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" }, { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-authorized-cyber-effects-support-mean/#clm-k04-q-095", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-095", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-095.json", "name": "What does authorized cyber effects support mean?", "ownerAnchor": "clm-k04-q-095", "ownerId": "K04-Q-095", "ownerRoute": "/questions/what-does-authorized-cyber-effects-support-mean/", "ownerType": "question", "proposition": "It means engineering, integration, testing, and governed execution support for a mission directed by competent authority, with written target and effect boundaries, deconfliction, abort rules, evidence, and post-action review. It does not mean independent private hack-back.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for What does authorized cyber effects support mean?", "slug": "clm-k04-q-095", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Section 2 — Establishing the Program", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Defined operations and limitations", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-a-customer-request-authorize-an-offensive-cyber-operation/#clm-k04-q-096", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-096", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-096.json", "name": "Can a customer request authorize an offensive cyber operation?", "ownerAnchor": "clm-k04-q-096", "ownerId": "K04-Q-096", "ownerRoute": "/questions/can-a-customer-request-authorize-an-offensive-cyber-operation/", "ownerType": "question", "proposition": "No. A request can describe a need, but lawful authority depends on jurisdiction, identity of the competent authority, ownership or consent, mission type, target status, effect, domestic and international law, and the written approvals required for that operation.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for Can a customer request authorize an offensive cyber operation?", "slug": "clm-k04-q-096", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Section 2 — Establishing the Program", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Defined operations and limitations", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-combine-offensive-and-defensive-cyber-research/#clm-k04-q-097", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-097", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-097.json", "name": "Why combine offensive and defensive cyber research?", "ownerAnchor": "clm-k04-q-097", "ownerId": "K04-Q-097", "ownerRoute": "/questions/why-combine-offensive-and-defensive-cyber-research/", "ownerType": "question", "proposition": "Defensive engineering improves when it understands adversary workflows, and authorized operations improve when they incorporate defensive telemetry, recovery, and collateral-effect knowledge. The organizational feedback loop is valuable, but operational permissions, data access, and mission approvals remain separate.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for Why combine offensive and defensive cyber research?", "slug": "clm-k04-q-097", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Section 2 — Establishing the Program", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Defined operations and limitations", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-required-before-an-autonomous-warfare-capability-is-fielded/#clm-k04-q-098", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-098", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-098.json", "name": "What is required before an autonomous warfare capability is fielded?", "ownerAnchor": "clm-k04-q-098", "ownerId": "K04-Q-098", "ownerRoute": "/questions/what-is-required-before-an-autonomous-warfare-capability-is-fielded/", "ownerType": "question", "proposition": "At minimum: defined mission and authority, realistic verification and validation, adversarial test and evaluation, cybersecurity and anti-tamper controls, operator understanding, runtime status and abort mechanisms, legal review, training, rules, logistics, and post-fielding monitoring.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for What is required before an autonomous warfare capability is fielded?", "slug": "clm-k04-q-098", "sourceIds": [ "SRC-DODD-3000-09", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-do-you-prove-autonomous-defense-readiness/#clm-k04-q-099", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-099", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-099.json", "name": "How do you prove autonomous-defense readiness?", "ownerAnchor": "clm-k04-q-099", "ownerId": "K04-Q-099", "ownerRoute": "/questions/how-do-you-prove-autonomous-defense-readiness/", "ownerType": "question", "proposition": "Publish evidence for each stage: described, architected, implemented, tested, deployed, and operating. Identify the exact environment, release, test cases, results, defects, residual risk, signing evidence, and last verification. Never promote a research report or prototype directly to operational status.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for How do you prove autonomous-defense readiness?", "slug": "clm-k04-q-099", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-the-role-of-digital-twins-in-critical-datacenter-defense/#clm-k04-q-100", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-100", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-100.json", "name": "What is the role of digital twins in critical datacenter defense?", "ownerAnchor": "clm-k04-q-100", "ownerId": "K04-Q-100", "ownerRoute": "/questions/what-is-the-role-of-digital-twins-in-critical-datacenter-defense/", "ownerType": "question", "proposition": "A validated twin supports consequence analysis, dependency mapping, attack-path testing, load and cooling scenarios, recovery rehearsal, and autonomous-policy evaluation without risking the live facility. Its evidence is bounded by model fidelity and validation.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for What is the role of digital twins in critical datacenter defense?", "slug": "clm-k04-q-100", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-machine-intelligence-defend-against-machine-intelligence/#clm-k04-q-101", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-101", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-101.json", "name": "How should Machine Intelligence defend against adversarial Machine Intelligence?", "ownerAnchor": "clm-k04-q-101", "ownerId": "K04-Q-101", "ownerRoute": "/questions/how-should-machine-intelligence-defend-against-machine-intelligence/", "ownerType": "question", "proposition": "Use layered systems rather than one model: deterministic boundaries, diverse sensors and analyzers, adversarially trained models, immutable baselines, deception, moving-target defenses, Byzantine-resilient coordination, model and data provenance, runtime assurance, and recovery that assumes some agents will fail or be compromised.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for How should Machine Intelligence defend against adversarial Machine Intelligence?", "slug": "clm-k04-q-101", "sourceIds": [ "SRC-DODD-3000-09", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-serious-contender-mean-without-overclaiming/#clm-k04-q-102", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-Q-102", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-q-102.json", "name": "What does being a serious contender mean without overclaiming?", "ownerAnchor": "clm-k04-q-102", "ownerId": "K04-Q-102", "ownerRoute": "/questions/what-does-serious-contender-mean-without-overclaiming/", "ownerType": "question", "proposition": "It means publishing a coherent reference architecture, governed source base, capability boundaries, test doctrine, procurement-ready work packages, correction history, and operational-evidence requirements. It does not mean claiming a deployed force, classified access, regulatory approval, or completed missions without evidence.", "qualification": "The answer remains bounded by the owning topic, exact authority, safety, jurisdiction, evidence, and readiness state.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Direct answer for What does being a serious contender mean without overclaiming?", "slug": "clm-k04-q-102", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/autonomous-defense-vs-uncontrolled-autonomy/#clm-k04-cmp-031", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-031", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-031.json", "name": "Bounded Autonomous Defense versus Uncontrolled Autonomy", "ownerAnchor": "clm-k04-cmp-031", "ownerId": "K04-CMP-031", "ownerRoute": "/comparisons/autonomous-defense-vs-uncontrolled-autonomy/", "ownerType": "comparison", "proposition": "Bounded defense acts on approved assets with defined actions, limits, evidence, reversibility, and abort conditions; uncontrolled autonomy invents or expands its own authority and effects.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Bounded Autonomous Defense and Uncontrolled Autonomy.", "slug": "clm-k04-cmp-031", "sourceIds": [ "SRC-WH-EO-14409", "SRC-WH-GOLD-EAGLE-2026", "SRC-USAASC-CYBER-WARFARE-2026", "SRC-NIST-800-207", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1 — Purpose", "sourceId": "SRC-WH-EO-14409", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.", "url": "https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" }, { "section": "Program description", "sourceId": "SRC-WH-GOLD-EAGLE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/critical-function-assurance-vs-perimeter-security/#clm-k04-cmp-032", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-032", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-032.json", "name": "Critical Function Assurance versus Perimeter Security", "ownerAnchor": "clm-k04-cmp-032", "ownerId": "K04-CMP-032", "ownerRoute": "/comparisons/critical-function-assurance-vs-perimeter-security/", "ownerType": "comparison", "proposition": "Critical Function Assurance assumes penetration is possible and protects essential outcomes; perimeter security focuses on keeping threats outside a boundary.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Critical Function Assurance and Perimeter Security.", "slug": "clm-k04-cmp-032", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/nuclear-powered-compute-vs-grid-independence/#clm-k04-cmp-033", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-033", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-033.json", "name": "Nuclear-Powered Compute versus Grid Independence", "ownerAnchor": "clm-k04-cmp-033", "ownerId": "K04-CMP-033", "ownerRoute": "/comparisons/nuclear-powered-compute-vs-grid-independence/", "ownerType": "comparison", "proposition": "Nuclear-powered compute describes an energy source or commercial relationship; grid independence requires an engineered and tested ability to operate safely without the external grid.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Nuclear-Powered Compute and Grid Independence.", "slug": "clm-k04-cmp-033", "sourceIds": [ "SRC-GOOGLE-KAIROS-2024", "SRC-CONSTELLATION-MICROSOFT-2024", "SRC-CONSTELLATION-META-2025", "SRC-NRC-10CFR-73-54", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY" ], "sourceSections": [ { "section": "Agreement and timeline", "sourceId": "SRC-GOOGLE-KAIROS-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Google states that the agreement is intended to enable up to 500 MW of 24/7 carbon-free power, beginning with a first SMR targeted for 2030.", "url": "https://blog.google/company-news/outreach-and-initiatives/sustainability/google-kairos-power-nuclear-energy-agreement/" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-MICROSOFT-2024", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation describes a 20-year Microsoft PPA supporting restart and approximately 835 MW of carbon-free grid output.", "url": "https://www.constellationenergy.com/news/2024/Constellation-to-Launch-Crane-Clean-Energy-Center-Restoring-Jobs-and-Carbon-Free-Power-to-The-Grid.html" }, { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-META-2025", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Constellation and Meta announced a 20-year agreement for 1,121 MW of emissions-free nuclear output beginning in 2027.", "url": "https://www.constellationenergy.com/news/2025/constellation-meta-sign-20-year-deal-for-clean-reliable-nuclear-energy-in-illinois.html" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/data-diode-vs-air-gap/#clm-k04-cmp-034", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-034", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-034.json", "name": "Unidirectional Gateway versus Air Gap", "ownerAnchor": "clm-k04-cmp-034", "ownerId": "K04-CMP-034", "ownerRoute": "/comparisons/data-diode-vs-air-gap/", "ownerType": "comparison", "proposition": "A unidirectional gateway permits one-way mediated data flow; an air gap is a claimed absence of direct network connectivity.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Unidirectional Gateway and Air Gap.", "slug": "clm-k04-cmp-034", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/counter-uas-awareness-vs-mitigation-authority/#clm-k04-cmp-035", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-035", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-035.json", "name": "Counter-UAS Awareness versus Counter-UAS Mitigation Authority", "ownerAnchor": "clm-k04-cmp-035", "ownerId": "K04-CMP-035", "ownerRoute": "/comparisons/counter-uas-awareness-vs-mitigation-authority/", "ownerType": "comparison", "proposition": "Awareness covers detection and tracking; mitigation authority governs whether and how interference, seizure, or destruction may occur.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Counter-UAS Awareness and Counter-UAS Mitigation Authority.", "slug": "clm-k04-cmp-035", "sourceIds": [ "SRC-NRC-10CFR-73-55", "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "SRC-DODD-3000-09" ], "sourceSections": [ { "section": "General performance objective and requirements", "sourceId": "SRC-NRC-10CFR-73-55", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Nuclear power reactor licensees must establish and maintain a physical protection program against radiological sabotage with defined detection, assessment, delay, and response functions.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.55" }, { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" }, { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" }, { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/authorized-cyber-effects-vs-private-hack-back/#clm-k04-cmp-036", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-036", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-036.json", "name": "Authorized Cyber Effects versus Private Hack-Back", "ownerAnchor": "clm-k04-cmp-036", "ownerId": "K04-CMP-036", "ownerRoute": "/comparisons/authorized-cyber-effects-vs-private-hack-back/", "ownerType": "comparison", "proposition": "Authorized effects are directed and controlled by competent authority within a written mission; private hack-back is unilateral external action without that governmental or ownership basis.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Authorized Cyber Effects and Private Hack-Back.", "slug": "clm-k04-cmp-036", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Section 2 — Establishing the Program", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Defined operations and limitations", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/threat-emulation-vs-live-offensive-operation/#clm-k04-cmp-037", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-037", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-037.json", "name": "Threat Emulation versus Live Offensive Operation", "ownerAnchor": "clm-k04-cmp-037", "ownerId": "K04-CMP-037", "ownerRoute": "/comparisons/threat-emulation-vs-live-offensive-operation/", "ownerType": "comparison", "proposition": "Threat emulation reproduces selected behaviors in an authorized controlled environment; a live offensive operation affects external target systems under mission authority.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Threat Emulation and Live Offensive Operation.", "slug": "clm-k04-cmp-037", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/simulation-readiness-vs-operational-readiness/#clm-k04-cmp-038", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-038", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-038.json", "name": "Simulation Readiness versus Operational Readiness", "ownerAnchor": "clm-k04-cmp-038", "ownerId": "K04-CMP-038", "ownerRoute": "/comparisons/simulation-readiness-vs-operational-readiness/", "ownerType": "comparison", "proposition": "Simulation readiness shows bounded performance in a test model; operational readiness requires deployment, environment-specific verification, sustainment, authority, and current operating evidence.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Simulation Readiness and Operational Readiness.", "slug": "clm-k04-cmp-038", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/mission-command-autonomy-vs-self-authorized-action/#clm-k04-cmp-039", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-039", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-039.json", "name": "Mission-Command Autonomy versus Self-Authorized Action", "ownerAnchor": "clm-k04-cmp-039", "ownerId": "K04-CMP-039", "ownerRoute": "/comparisons/mission-command-autonomy-vs-self-authorized-action/", "ownerType": "comparison", "proposition": "Mission-command autonomy executes assigned intent within delegated limits when disconnected; self-authorized action creates a new mission, target, or effect without authority.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Mission-Command Autonomy and Self-Authorized Action.", "slug": "clm-k04-cmp-039", "sourceIds": [ "SRC-DODD-3000-09", "SRC-USAASC-PM-CW-2026", "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/defense-supremacy-vs-offense-dominance/#clm-k04-cmp-040", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K04 STRATEGIC RECORD", "id": "CLM-K04-CMP-040", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-cmp-040.json", "name": "Deterrence by Denial versus Offense Dominance", "ownerAnchor": "clm-k04-cmp-040", "ownerId": "K04-CMP-040", "ownerRoute": "/comparisons/defense-supremacy-vs-offense-dominance/", "ownerType": "comparison", "proposition": "Deterrence by denial raises adversary cost through resilience and recovery; offense dominance assumes access and exploitation create lasting strategic advantage.", "qualification": "The matrix prevents category error but does not determine every facility, mission, target, jurisdiction, or operational case.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Canonical K04 distinction between Deterrence by Denial and Offense Dominance.", "slug": "clm-k04-cmp-040", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-wh-eo-14409/#clm-k04-src-wheo14409-01", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-WHEO14409-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-wheo14409-01.json", "name": "Executive Order 14409 — Promoting Advanced Artificial Intelligence Innovation and Security — Section 1 — Purpose", "ownerAnchor": "clm-k04-src-wheo14409-01", "ownerId": "SRC-WH-EO-14409", "ownerRoute": "/sources/src-wh-eo-14409/", "ownerType": "source", "proposition": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of Executive Order 14409.", "slug": "clm-k04-src-wheo14409-01", "sourceIds": [ "SRC-WH-EO-14409" ], "sourceSections": [ { "section": "Section 1 — Purpose", "sourceId": "SRC-WH-EO-14409", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.", "url": "https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-wh-gold-eagle-2026/#clm-k04-src-whgoldeagle2026-01", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-WHGOLDEAGLE2026-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-whgoldeagle2026-01.json", "name": "White House Launches GOLD EAGLE Initiative for Cybersecurity Vulnerability Coordination — Program description", "ownerAnchor": "clm-k04-src-whgoldeagle2026-01", "ownerId": "SRC-WH-GOLD-EAGLE-2026", "ownerRoute": "/sources/src-wh-gold-eagle-2026/", "ownerType": "source", "proposition": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of White House release, July 14, 2026.", "slug": "clm-k04-src-whgoldeagle2026-01", "sourceIds": [ "SRC-WH-GOLD-EAGLE-2026" ], "sourceSections": [ { "section": "Program description", "sourceId": "SRC-WH-GOLD-EAGLE-2026", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-wh-cyber-crime-memo-2026/#clm-k04-src-whcybercrimememo2026-01", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-WHCYBERCRIMEMEMO2026-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-whcybercrimememo2026-01.json", "name": "Expanding Capabilities to Combat Transnational Cyber-Enabled Crime — Section 2 — Establishing the Program", "ownerAnchor": "clm-k04-src-whcybercrimememo2026-01", "ownerId": "SRC-WH-CYBER-CRIME-MEMO-2026", "ownerRoute": "/sources/src-wh-cyber-crime-memo-2026/", "ownerType": "source", "proposition": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of Presidential Memorandum, August 12, 2026.", "slug": "clm-k04-src-whcybercrimememo2026-01", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026" ], "sourceSections": [ { "section": "Section 2 — Establishing the Program", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The National Coordination Center is directed to manage a program authorizing participating companies to conduct defined operations against foreign CE-TCOs under federal control and oversight.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-wh-cyber-crime-memo-2026/#clm-k04-src-whcybercrimememo2026-02", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-WHCYBERCRIMEMEMO2026-02", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-whcybercrimememo2026-02.json", "name": "Expanding Capabilities to Combat Transnational Cyber-Enabled Crime — Defined operations and limitations", "ownerAnchor": "clm-k04-src-whcybercrimememo2026-02", "ownerId": "SRC-WH-CYBER-CRIME-MEMO-2026", "ownerRoute": "/sources/src-wh-cyber-crime-memo-2026/", "ownerType": "source", "proposition": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of Presidential Memorandum, August 12, 2026.", "slug": "clm-k04-src-whcybercrimememo2026-02", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026" ], "sourceSections": [ { "section": "Defined operations and limitations", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The memorandum distinguishes cyber surveillance from cyber effects and imposes program direction, approval, and outcome limitations.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-usaasc-pm-cw-2026/#clm-k04-src-usaascpmcw2026-01", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-USAASCPMCW2026-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-usaascpmcw2026-01.json", "name": "The Establishment of Project Manager Cyber Warfare — Establishment and mission", "ownerAnchor": "clm-k04-src-usaascpmcw2026-01", "ownerId": "SRC-USAASC-PM-CW-2026", "ownerRoute": "/sources/src-usaasc-pm-cw-2026/", "ownerType": "source", "proposition": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of Army release, August 3, 2026.", "slug": "clm-k04-src-usaascpmcw2026-01", "sourceIds": [ "SRC-USAASC-PM-CW-2026" ], "sourceSections": [ { "section": "Establishment and mission", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Project Manager Cyber Warfare was formed from the merger of PM Defensive Cyber Operations and PM Cyber and Space to deliver integrated cyber capabilities.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-usaasc-pm-cw-2026/#clm-k04-src-usaascpmcw2026-02", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-USAASCPMCW2026-02", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-usaascpmcw2026-02.json", "name": "The Establishment of Project Manager Cyber Warfare — Offense-defense feedback", "ownerAnchor": "clm-k04-src-usaascpmcw2026-02", "ownerId": "SRC-USAASC-PM-CW-2026", "ownerRoute": "/sources/src-usaasc-pm-cw-2026/", "ownerType": "source", "proposition": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of Army release, August 3, 2026.", "slug": "clm-k04-src-usaascpmcw2026-02", "sourceIds": [ "SRC-USAASC-PM-CW-2026" ], "sourceSections": [ { "section": "Offense-defense feedback", "sourceId": "SRC-USAASC-PM-CW-2026", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The official statement presents offense informing defense and defense informing offense as a rationale for portfolio integration.", "url": "https://cpeisw.army.mil/2026/08/03/constant-modernization-the-establishment-of-project-manager-cyber-warfare/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-usaasc-cyber-warfare-2026/#clm-k04-src-usaasccyberwarfare2026-01", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-USAASCCYBERWARFARE2026-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-usaasccyberwarfare2026-01.json", "name": "Cyber Warfare: The Best Offense Is a Powerful Defense — Portfolio integration", "ownerAnchor": "clm-k04-src-usaasccyberwarfare2026-01", "ownerId": "SRC-USAASC-CYBER-WARFARE-2026", "ownerRoute": "/sources/src-usaasc-cyber-warfare-2026/", "ownerType": "source", "proposition": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of USAASC article, August 10, 2026.", "slug": "clm-k04-src-usaasccyberwarfare2026-01", "sourceIds": [ "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-usaasc-cyber-warfare-2026/#clm-k04-src-usaasccyberwarfare2026-02", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-USAASCCYBERWARFARE2026-02", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-usaasccyberwarfare2026-02.json", "name": "Cyber Warfare: The Best Offense Is a Powerful Defense — Conclusion", "ownerAnchor": "clm-k04-src-usaasccyberwarfare2026-02", "ownerId": "SRC-USAASC-CYBER-WARFARE-2026", "ownerRoute": "/sources/src-usaasc-cyber-warfare-2026/", "ownerType": "source", "proposition": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of USAASC article, August 10, 2026.", "slug": "clm-k04-src-usaasccyberwarfare2026-02", "sourceIds": [ "SRC-USAASC-CYBER-WARFARE-2026" ], "sourceSections": [ { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nrc-10cfr-73-54/#clm-k04-src-nrc10cfr7354-01", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-NRC10CFR7354-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-nrc10cfr7354-01.json", "name": "10 CFR 73.54 — Protection of Digital Computer and Communication Systems and Networks — 73.54(a)", "ownerAnchor": "clm-k04-src-nrc10cfr7354-01", "ownerId": "SRC-NRC-10CFR-73-54", "ownerRoute": "/sources/src-nrc-10cfr-73-54/", "ownerType": "source", "proposition": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of 10 CFR 73.54, current eCFR.", "slug": "clm-k04-src-nrc10cfr7354-01", "sourceIds": [ "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nrc-10cfr-73-54/#clm-k04-src-nrc10cfr7354-02", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-NRC10CFR7354-02", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-nrc10cfr7354-02.json", "name": "10 CFR 73.54 — Protection of Digital Computer and Communication Systems and Networks — 73.54(b)", "ownerAnchor": "clm-k04-src-nrc10cfr7354-02", "ownerId": "SRC-NRC-10CFR-73-54", "ownerRoute": "/sources/src-nrc-10cfr-73-54/", "ownerType": "source", "proposition": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of 10 CFR 73.54, current eCFR.", "slug": "clm-k04-src-nrc10cfr7354-02", "sourceIds": [ "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nrc-10cfr-73-55/#clm-k04-src-nrc10cfr7355-01", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-NRC10CFR7355-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-nrc10cfr7355-01.json", "name": "10 CFR 73.55 — Requirements for Physical Protection of Licensed Activities in Nuclear Power Reactors Against Radiological Sabotage — General performance objective and requirements", "ownerAnchor": "clm-k04-src-nrc10cfr7355-01", "ownerId": "SRC-NRC-10CFR-73-55", "ownerRoute": "/sources/src-nrc-10cfr-73-55/", "ownerType": "source", "proposition": "Nuclear power reactor licensees must establish and maintain a physical protection program against radiological sabotage with defined detection, assessment, delay, and response functions.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of 10 CFR 73.55, current eCFR.", "slug": "clm-k04-src-nrc10cfr7355-01", "sourceIds": [ "SRC-NRC-10CFR-73-55" ], "sourceSections": [ { "section": "General performance objective and requirements", "sourceId": "SRC-NRC-10CFR-73-55", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Nuclear power reactor licensees must establish and maintain a physical protection program against radiological sabotage with defined detection, assessment, delay, and response functions.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.55" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nrc-advanced-reactor-physical-security/#clm-k04-src-nrcadvancedreactorphysicalsecurity-01", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-NRCADVANCEDREACTORPHYSICALSECURITY-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-nrcadvancedreactorphysicalsecurity-01.json", "name": "Alternative Physical Security Requirements for Advanced Reactors — Alternative requirements overview", "ownerAnchor": "clm-k04-src-nrcadvancedreactorphysicalsecurity-01", "ownerId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "ownerRoute": "/sources/src-nrc-advanced-reactor-physical-security/", "ownerType": "source", "proposition": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of NRC proposed-rule record, September 2024, with later rulemaking history.", "slug": "clm-k04-src-nrcadvancedreactorphysicalsecurity-01", "sourceIds": [ "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY" ], "sourceSections": [ { "section": "Alternative requirements overview", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The NRC considered technology-inclusive, risk-informed, performance-based alternatives for advanced-reactor physical protection.", "url": "https://www.nrc.gov/docs/ML2425/ML24254A350.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nrc-advanced-reactor-physical-security/#clm-k04-src-nrcadvancedreactorphysicalsecurity-02", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-NRCADVANCEDREACTORPHYSICALSECURITY-02", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-nrcadvancedreactorphysicalsecurity-02.json", "name": "Alternative Physical Security Requirements for Advanced Reactors — Onsite responder alternatives", "ownerAnchor": "clm-k04-src-nrcadvancedreactorphysicalsecurity-02", "ownerId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "ownerRoute": "/sources/src-nrc-advanced-reactor-physical-security/", "ownerType": "source", "proposition": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of NRC proposed-rule record, September 2024, with later rulemaking history.", "slug": "clm-k04-src-nrcadvancedreactorphysicalsecurity-02", "sourceIds": [ "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY" ], "sourceSections": [ { "section": "Onsite responder alternatives", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Supporting materials discuss conditions under which the minimum number of onsite armed responders could be reduced, including potentially to zero, subject to the rule and facility showing.", "url": "https://www.nrc.gov/docs/ML2417/ML24178A370.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-inl-cce/#clm-k04-src-inlcce-01", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-INLCCE-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-inlcce-01.json", "name": "Consequence-driven Cyber-informed Engineering — CCE methodology", "ownerAnchor": "clm-k04-src-inlcce-01", "ownerId": "SRC-INL-CCE", "ownerRoute": "/sources/src-inl-cce/", "ownerType": "source", "proposition": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of INL CCE program page.", "slug": "clm-k04-src-inlcce-01", "sourceIds": [ "SRC-INL-CCE" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-inl-cce/#clm-k04-src-inlcce-02", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-INLCCE-02", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-inlcce-02.json", "name": "Consequence-driven Cyber-informed Engineering — Critical function focus", "ownerAnchor": "clm-k04-src-inlcce-02", "ownerId": "SRC-INL-CCE", "ownerRoute": "/sources/src-inl-cce/", "ownerType": "source", "proposition": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of INL CCE program page.", "slug": "clm-k04-src-inlcce-02", "sourceIds": [ "SRC-INL-CCE" ], "sourceSections": [ { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nist-800-82r3/#clm-k04-src-nist80082r3-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-NIST80082R3-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-nist80082r3-01.json", "name": "NIST SP 800-82 Revision 3 — Guide to Operational Technology Security — Abstract", "ownerAnchor": "clm-k04-src-nist80082r3-01", "ownerId": "SRC-NIST-800-82R3", "ownerRoute": "/sources/src-nist-800-82r3/", "ownerType": "source", "proposition": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of NIST SP 800-82 Rev. 3.", "slug": "clm-k04-src-nist80082r3-01", "sourceIds": [ "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-nist-800-207/#clm-k04-src-nist800207-01", "claimStatus": "CURRENT TECHNICAL STANDARD", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-NIST800207-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-nist800207-01.json", "name": "NIST SP 800-207 — Zero Trust Architecture — Abstract", "ownerAnchor": "clm-k04-src-nist800207-01", "ownerId": "SRC-NIST-800-207", "ownerRoute": "/sources/src-nist-800-207/", "ownerType": "source", "proposition": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of NIST SP 800-207.", "slug": "clm-k04-src-nist800207-01", "sourceIds": [ "SRC-NIST-800-207" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-dodd-3000-09/#clm-k04-src-dodd300009-01", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-DODD300009-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-dodd300009-01.json", "name": "DoD Directive 3000.09 — Autonomy in Weapon Systems — Policy 1.2(a)-(b)", "ownerAnchor": "clm-k04-src-dodd300009-01", "ownerId": "SRC-DODD-3000-09", "ownerRoute": "/sources/src-dodd-3000-09/", "ownerType": "source", "proposition": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of DoDD 3000.09, January 25, 2023.", "slug": "clm-k04-src-dodd300009-01", "sourceIds": [ "SRC-DODD-3000-09" ], "sourceSections": [ { "section": "Policy 1.2(a)-(b)", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Autonomous and semi-autonomous weapon systems must allow appropriate human judgment over force and undergo rigorous verification, validation, testing, cybersecurity, and lawful use.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-dodd-3000-09/#clm-k04-src-dodd300009-02", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-DODD300009-02", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-dodd300009-02.json", "name": "DoD Directive 3000.09 — Autonomy in Weapon Systems — Responsibilities and testing", "ownerAnchor": "clm-k04-src-dodd300009-02", "ownerId": "SRC-DODD-3000-09", "ownerRoute": "/sources/src-dodd-3000-09/", "ownerType": "source", "proposition": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of DoDD 3000.09, January 25, 2023.", "slug": "clm-k04-src-dodd300009-02", "sourceIds": [ "SRC-DODD-3000-09" ], "sourceSections": [ { "section": "Responsibilities and testing", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "The directive assigns approval, legal review, test, monitoring, operator understanding, abort, and post-fielding responsibilities.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-google-kairos-2024/#clm-k04-src-googlekairos2024-01", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-GOOGLEKAIROS2024-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-googlekairos2024-01.json", "name": "Google and Kairos Power Advanced Nuclear Agreement — Agreement and timeline", "ownerAnchor": "clm-k04-src-googlekairos2024-01", "ownerId": "SRC-GOOGLE-KAIROS-2024", "ownerRoute": "/sources/src-google-kairos-2024/", "ownerType": "source", "proposition": "Google states that the agreement is intended to enable up to 500 MW of 24/7 carbon-free power, beginning with a first SMR targeted for 2030.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of Google announcement, October 14, 2024.", "slug": "clm-k04-src-googlekairos2024-01", "sourceIds": [ "SRC-GOOGLE-KAIROS-2024" ], "sourceSections": [ { "section": "Agreement and timeline", "sourceId": "SRC-GOOGLE-KAIROS-2024", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Google states that the agreement is intended to enable up to 500 MW of 24/7 carbon-free power, beginning with a first SMR targeted for 2030.", "url": "https://blog.google/company-news/outreach-and-initiatives/sustainability/google-kairos-power-nuclear-energy-agreement/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-constellation-microsoft-2024/#clm-k04-src-constellationmicrosoft2024-01", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-CONSTELLATIONMICROSOFT2024-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-constellationmicrosoft2024-01.json", "name": "Constellation and Microsoft Crane Clean Energy Center Agreement — Agreement summary", "ownerAnchor": "clm-k04-src-constellationmicrosoft2024-01", "ownerId": "SRC-CONSTELLATION-MICROSOFT-2024", "ownerRoute": "/sources/src-constellation-microsoft-2024/", "ownerType": "source", "proposition": "Constellation describes a 20-year Microsoft PPA supporting restart and approximately 835 MW of carbon-free grid output.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of Constellation announcement, September 20, 2024.", "slug": "clm-k04-src-constellationmicrosoft2024-01", "sourceIds": [ "SRC-CONSTELLATION-MICROSOFT-2024" ], "sourceSections": [ { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-MICROSOFT-2024", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Constellation describes a 20-year Microsoft PPA supporting restart and approximately 835 MW of carbon-free grid output.", "url": "https://www.constellationenergy.com/news/2024/Constellation-to-Launch-Crane-Clean-Energy-Center-Restoring-Jobs-and-Carbon-Free-Power-to-The-Grid.html" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/sources/src-constellation-meta-2025/#clm-k04-src-constellationmeta2025-01", "claimStatus": "OBSERVED DEPLOYMENT OR PRACTICE", "correctionStatus": "CURRENT K04 SOURCE RECORD", "id": "CLM-K04-SRC-CONSTELLATIONMETA2025-01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-src-constellationmeta2025-01.json", "name": "Constellation and Meta Clinton Clean Energy Center Agreement — Agreement summary", "ownerAnchor": "clm-k04-src-constellationmeta2025-01", "ownerId": "SRC-CONSTELLATION-META-2025", "ownerRoute": "/sources/src-constellation-meta-2025/", "ownerType": "source", "proposition": "Constellation and Meta announced a 20-year agreement for 1,121 MW of emissions-free nuclear output beginning in 2027.", "qualification": "Official publication establishes the source text and status within scope; it does not automatically prove effectiveness, deployment, mission authority, or every external fact.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Bounded proposition supported by the cited section of Constellation announcement, June 3, 2025.", "slug": "clm-k04-src-constellationmeta2025-01", "sourceIds": [ "SRC-CONSTELLATION-META-2025" ], "sourceSections": [ { "section": "Agreement summary", "sourceId": "SRC-CONSTELLATION-META-2025", "supportRelationship": "DIRECT SOURCE-SECTION SUPPORT", "supports": "Constellation and Meta announced a 20-year agreement for 1,121 MW of emissions-free nuclear output beginning in 2027.", "url": "https://www.constellationenergy.com/news/2025/constellation-meta-sign-20-year-deal-for-clean-reliable-nuclear-energy-in-illinois.html" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C01", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c01.json", "name": "Authority and mission boundary is explicit", "ownerAnchor": "ac-k05-c01", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "Every automated protection action and any external mission support is traceable to a competent authority, named asset scope, allowed effects, prohibited outcomes, duration, stop conditions, and review route.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c01", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026", "SRC-NRC-10CFR-73-SUBPART-J-2026" ], "sourceSections": [ { "section": "Sections 1-2 — Purpose, federal control, and program establishment", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The program incorporates private-sector capabilities but requires participating companies to act on behalf of and under Federal Government control, oversight, supervision, and lawful authorities.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Section 3 — Operating procedures and written package approval", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Every operations package requires federal review, written approval and direction, deconfliction, reporting, annual evaluation, and procedures to cease activity outside approved parameters.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Section 4 — Definitions and critical outcomes", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum defines surveillance and effects operations and bars program approval of operations likely to cause loss of life, serious injury, or a use of force or armed attack under international law.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "73.100", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive physical-protection requirements are available for qualifying Part 53 licensees that elect the section.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.100" }, { "section": "73.110", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive protection requirements address covered digital computer and communication systems and networks.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.110" }, { "section": "73.120", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Subpart J framework includes an access-authorization program for covered commercial nuclear plants.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.120" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C02", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c02.json", "name": "High-consequence events are identified and bounded", "ownerAnchor": "ac-k05-c02", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "The facility identifies the cyber-enabled physical and mission consequences that must be prevented, their initiating pathways, critical functions, and independent protections.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c02", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C03", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c03.json", "name": "Deterministic separation protects safety functions", "ownerAnchor": "ac-k05-c03", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "Safety-significant and critical OT functions cannot be commanded from lower-trust datacenter or external networks through an unverified software path.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c03", "sourceIds": [ "SRC-NRC-10CFR-73-54", "SRC-NRC-10CFR-73-SUBPART-J-2026", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.100", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive physical-protection requirements are available for qualifying Part 53 licensees that elect the section.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.100" }, { "section": "73.110", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive protection requirements address covered digital computer and communication systems and networks.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.110" }, { "section": "73.120", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Subpart J framework includes an access-authorization program for covered commercial nuclear plants.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.120" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C04", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c04.json", "name": "Identity, firmware, and management planes remain trustworthy", "ownerAnchor": "ac-k05-c04", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "Privileged identities, workload identities, signing keys, BMCs, firmware, update systems, model artifacts, and management networks are separately protected and continuously evidenced.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c04", "sourceIds": [ "SRC-NIST-800-207", "SRC-NIST-SSDF", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C05", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c05.json", "name": "Autonomous defense is bounded, causal, and reversible", "ownerAnchor": "ac-k05-c05", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "Autonomous defenders act only through pre-authorized internal actions whose physical consequence, confidence threshold, rollback, evidence, and safe-state behavior have been tested.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c05", "sourceIds": [ "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-WH-GOLD-EAGLE-2026" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "Program description", "sourceId": "SRC-WH-GOLD-EAGLE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C06", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c06.json", "name": "Sensor and model disagreement cannot directly control force", "ownerAnchor": "ac-k05-c06", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "Physical-security autonomy separates sensing, classification, access denial, non-destructive protection, authorized responder routing, and any force-enabled response into independently governed layers.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c06", "sourceIds": [ "SRC-DODD-3000-09", "SRC-FAA-CI-UAS-NPRM-2026", "SRC-USC-6-124N", "SRC-USC-47-333" ], "sourceSections": [ { "section": "Section 1.1(a)-(b) — Applicability and exclusions", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive applies to autonomous and semi-autonomous weapon systems and expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Section 1.2(a) — Weapon-system policy", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Within its weapon-system scope, the directive requires appropriate human judgment, rigorous verification and validation, realistic test and evaluation, robustness, transparency, auditability, and bounded engagement behavior.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Proposed petition process", "sourceId": "SRC-FAA-CI-UAS-NPRM-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The FAA proposed a process for operators of certain critical-infrastructure sites to petition for restrictions on drone operations over those sites.", "url": "https://www.faa.gov/newsroom/restricting-drones-near-critical-infrastructure-sites" }, { "section": "Authorities and covered facilities", "sourceId": "SRC-USC-6-124N", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The statute assigns specified counter-UAS authorities and constraints to federal departments for covered facilities and missions.", "url": "https://uscode.house.gov/view.xhtml?req=%28title%3A6+section%3A124n+edition%3Aprelim%29" }, { "section": "Section 333 prohibition", "sourceId": "SRC-USC-47-333", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "No person may willfully or maliciously interfere with authorized radio communications, absent a separate applicable authority or exception.", "url": "https://uscode.house.gov/view.xhtml?req=%28title%3A47+section%3A333+edition%3Aprelim%29" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C07", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c07.json", "name": "Power, cooling, and timing failures do not defeat protected functions", "ownerAnchor": "ac-k05-c07", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "The facility can detect corrupted or unavailable power, cooling, environmental, and timing data; reject unsafe commands; and transition to approved operating states without relying on the compromised channel.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c07", "sourceIds": [ "SRC-NIST-800-82R3", "SRC-NERC-CIP-CATALOG-2026", "SRC-NRC-10CFR-73-SUBPART-J-2026" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "CIP standards catalog", "sourceId": "SRC-NERC-CIP-CATALOG-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NERC maintains the official catalog of CIP reliability standards; exact obligations require the current standard text and a facility-specific applicability analysis.", "url": "https://www.nerc.com/standards/reliability-standards/cip" }, { "section": "73.100", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive physical-protection requirements are available for qualifying Part 53 licensees that elect the section.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.100" }, { "section": "73.110", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive protection requirements address covered digital computer and communication systems and networks.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.110" }, { "section": "73.120", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Subpart J framework includes an access-authorization program for covered commercial nuclear plants.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.120" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C08", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c08.json", "name": "Recovery is clean, evidenced, and repeatable", "ownerAnchor": "ac-k05-c08", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "Critical services can be restored from independently protected, provenance-verified states while preserving evidence and preventing reinfection or unsafe configuration reintroduction.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c08", "sourceIds": [ "SRC-NIST-800-82R3", "SRC-NIST-800-53" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Planning note — Release 5.2.0", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NIST issued SP 800-53 Release 5.2.0 on 2025-08-27 with specified additions and revisions.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" }, { "section": "Publication purpose", "sourceId": "SRC-NIST-800-53", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SP 800-53 supplies a catalog of security and privacy controls; selection and assessment remain context-dependent.", "url": "https://csrc.nist.gov/pubs/sp/800/53/r5/upd1/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C09", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c09.json", "name": "Evidence supports readiness without overclaiming", "ownerAnchor": "ac-k05-c09", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "Every public or procurement readiness state is traceable to exact releases, tests, defects, deployment identity, authority, incidents, uptime, restoration, and independent-verification status.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c09", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-NIST-SSDF" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "Version 1.1 final publication", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "SSDF Version 1.1 provides high-level secure software development practices.", "url": "https://csrc.nist.gov/pubs/sp/800/218/final" }, { "section": "Version 1.2 initial public draft", "sourceId": "SRC-NIST-SSDF", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The official NIST record identifies SSDF Version 1.2 as an initial public draft published 2025-12-17.", "url": "https://csrc.nist.gov/pubs/sp/800/218/r1/ipd" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/critical-datacenter/#ac-k05-c10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 ASSURANCE RECORD", "id": "AC-K05-C10", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/ac-k05-c10.json", "name": "Authorized external effects remain separate from facility defense", "ownerAnchor": "ac-k05-c10", "ownerId": "AC-K05-CRITICAL-DATACENTER-001", "ownerRoute": "/assurance-case/critical-datacenter/", "ownerType": "page", "proposition": "External cyber surveillance or effects support is never triggered solely by a facility defensive model and proceeds only through a separately approved mission package, federal or other competent authority, deconfliction, effect constraints, and post-operation accountability.", "qualification": "Evidence must satisfy the declared requirements and no material defeater may remain hidden. This reference case does not certify a facility.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 public critical-datacenter assurance-case claim; facility-specific acceptance requires site evidence and competent authority.", "slug": "ac-k05-c10", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026", "SRC-USC-6-124N" ], "sourceSections": [ { "section": "Sections 1-2 — Purpose, federal control, and program establishment", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The program incorporates private-sector capabilities but requires participating companies to act on behalf of and under Federal Government control, oversight, supervision, and lawful authorities.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Section 3 — Operating procedures and written package approval", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Every operations package requires federal review, written approval and direction, deconfliction, reporting, annual evaluation, and procedures to cease activity outside approved parameters.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Section 4 — Definitions and critical outcomes", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum defines surveillance and effects operations and bars program approval of operations likely to cause loss of life, serious injury, or a use of force or armed attack under international law.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Authorities and covered facilities", "sourceId": "SRC-USC-6-124N", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The statute assigns specified counter-UAS authorities and constraints to federal departments for covered facilities and missions.", "url": "https://uscode.house.gov/view.xhtml?req=%28title%3A6+section%3A124n+edition%3Aprelim%29" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-a-critical-datacenter-assurance-case/#clm-k05-q-001", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-001", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-001.json", "name": "What is a critical-datacenter assurance case?", "ownerAnchor": "clm-k05-q-001", "ownerId": "K05-Q-001", "ownerRoute": "/questions/what-is-a-critical-datacenter-assurance-case/", "ownerType": "question", "proposition": "It is a structured, facility-tailored argument that a named mission and safety claim is supported by current evidence, bounded assumptions, identified hazards, tested recovery objectives, and explicit defeaters. It must show what would invalidate the claim.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for What is a critical-datacenter assurance case?", "slug": "clm-k05-q-001", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-a-control-mapping-prove-compliance/#clm-k05-q-002", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-002", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-002.json", "name": "Does a control mapping prove compliance?", "ownerAnchor": "clm-k05-q-002", "ownerId": "K05-Q-002", "ownerRoute": "/questions/does-a-control-mapping-prove-compliance/", "ownerType": "question", "proposition": "No. A mapping shows a documented relationship between a control and a source requirement or guidance element. Compliance requires the applicable authority, current text, facility scope, implemented control, operating evidence, exceptions, and an authorized determination.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for Does a control mapping prove compliance?", "slug": "clm-k05-q-002", "sourceIds": [ "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-NRC-10CFR-73-SUBPART-J-2026", "SRC-NERC-CIP-CATALOG-2026" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "73.100", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive physical-protection requirements are available for qualifying Part 53 licensees that elect the section.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.100" }, { "section": "73.110", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive protection requirements address covered digital computer and communication systems and networks.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.110" }, { "section": "73.120", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Subpart J framework includes an access-authorization program for covered commercial nuclear plants.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.120" }, { "section": "CIP standards catalog", "sourceId": "SRC-NERC-CIP-CATALOG-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NERC maintains the official catalog of CIP reliability standards; exact obligations require the current standard text and a facility-specific applicability analysis.", "url": "https://www.nerc.com/standards/reliability-standards/cip" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-must-be-tested-before-autonomous-containment/#clm-k05-q-003", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-003", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-003.json", "name": "What must be tested before autonomous containment is enabled?", "ownerAnchor": "clm-k05-q-003", "ownerId": "K05-Q-003", "ownerRoute": "/questions/what-must-be-tested-before-autonomous-containment/", "ownerType": "question", "proposition": "The action boundary, protected functions, causal assumptions, false-positive consequence, rollback, safe-state behavior, communications loss, authority, logging, model and data provenance, defect thresholds, and recovery path must be evaluated in representative conditions.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for What must be tested before autonomous containment is enabled?", "slug": "clm-k05-q-003", "sourceIds": [ "SRC-WH-EO-14409", "SRC-WH-GOLD-EAGLE-2026", "SRC-USAASC-CYBER-WARFARE-2026", "SRC-NIST-800-207", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1 — Purpose", "sourceId": "SRC-WH-EO-14409", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "United States policy promotes AI innovation and security through collaboration with the private sector, modernization, system hardening, and protection of intellectual property.", "url": "https://www.whitehouse.gov/presidential-actions/2026/06/promoting-advanced-artificial-intelligence-innovation-and-security/" }, { "section": "Program description", "sourceId": "SRC-WH-GOLD-EAGLE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "GOLD EAGLE is presented as a government-industry clearinghouse for vulnerability coordination, prioritization, and remediation support using frontier AI capabilities.", "url": "https://www.whitehouse.gov/releases/2026/07/white-house-launches-gold-eagle-initiative-for-unprecedented-cybersecurity-vulnerability-coordination/" }, { "section": "Portfolio integration", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Army describes integrated offensive and defensive cyber portfolios and rapid collaboration with commercial technology partners.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Conclusion", "sourceId": "SRC-USAASC-CYBER-WARFARE-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The article frames cyber capability as both defending critical infrastructure and enabling approved cyber operations.", "url": "https://asc.army.mil/web/cyber-warfare-the-best-offense-is-a-powerful-defense/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-nuclear-datacenter-tests-avoid-creating-new-risk/#clm-k05-q-004", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-004", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-004.json", "name": "How should nuclear-datacenter tests avoid creating new risk?", "ownerAnchor": "clm-k05-q-004", "ownerId": "K05-Q-004", "ownerRoute": "/questions/how-should-nuclear-datacenter-tests-avoid-creating-new-risk/", "ownerType": "question", "proposition": "Use an isolated range, synthetic or approved data, non-production identities, deterministic safety boundaries, no connection to protected plant systems, effects-disabled scenarios, independent stop authority, and evidence that every test artifact was contained and removed.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for How should nuclear-datacenter tests avoid creating new risk?", "slug": "clm-k05-q-004", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1.1(a)-(b) — Applicability and exclusions", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive applies to autonomous and semi-autonomous weapon systems and expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Section 1.2(a) — Weapon-system policy", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Within its weapon-system scope, the directive requires appropriate human judgment, rigorous verification and validation, realistic test and evaluation, robustness, transparency, auditability, and bounded engagement behavior.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-the-current-status-of-faa-critical-infrastructure-drone-restrictions/#clm-k05-q-005", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-005", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-005.json", "name": "What is the current status of the FAA critical-infrastructure drone restriction process?", "ownerAnchor": "clm-k05-q-005", "ownerId": "K05-Q-005", "ownerRoute": "/questions/what-is-the-current-status-of-faa-critical-infrastructure-drone-restrictions/", "ownerType": "question", "proposition": "As of the K05 research cutoff, the FAA had published a proposed rule describing a petition process for certain critical-infrastructure operators. The proposal is not represented as a final rule or as private authority to jam, spoof, seize, damage, or destroy aircraft.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for What is the current status of the FAA critical-infrastructure drone restriction process?", "slug": "clm-k05-q-005", "sourceIds": [ "SRC-FAA-CI-UAS-NPRM-2026", "SRC-USC-6-124N", "SRC-USC-47-333" ], "sourceSections": [ { "section": "Proposed petition process", "sourceId": "SRC-FAA-CI-UAS-NPRM-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The FAA proposed a process for operators of certain critical-infrastructure sites to petition for restrictions on drone operations over those sites.", "url": "https://www.faa.gov/newsroom/restricting-drones-near-critical-infrastructure-sites" }, { "section": "Authorities and covered facilities", "sourceId": "SRC-USC-6-124N", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The statute assigns specified counter-UAS authorities and constraints to federal departments for covered facilities and missions.", "url": "https://uscode.house.gov/view.xhtml?req=%28title%3A6+section%3A124n+edition%3Aprelim%29" }, { "section": "Section 333 prohibition", "sourceId": "SRC-USC-47-333", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "No person may willfully or maliciously interfere with authorized radio communications, absent a separate applicable authority or exception.", "url": "https://uscode.house.gov/view.xhtml?req=%28title%3A47+section%3A333+edition%3Aprelim%29" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-dodd-3000-09-govern-autonomous-cyber-defense/#clm-k05-q-006", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-006", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-006.json", "name": "Does DoD Directive 3000.09 govern autonomous cyber defense?", "ownerAnchor": "clm-k05-q-006", "ownerId": "K05-Q-006", "ownerRoute": "/questions/does-dodd-3000-09-govern-autonomous-cyber-defense/", "ownerType": "question", "proposition": "Not by its own applicability clause. The directive expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems. It is relevant only when the capability falls within its weapon-system scope; broader cyber controls require other authorities and standards.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for Does DoD Directive 3000.09 govern autonomous cyber defense?", "slug": "clm-k05-q-006", "sourceIds": [ "SRC-DODD-3000-09" ], "sourceSections": [ { "section": "Section 1.1(a)-(b) — Applicability and exclusions", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive applies to autonomous and semi-autonomous weapon systems and expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Section 1.2(a) — Weapon-system policy", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Within its weapon-system scope, the directive requires appropriate human judgment, rigorous verification and validation, realistic test and evaluation, robustness, transparency, auditability, and bounded engagement behavior.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-changed-in-the-advanced-reactor-security-framework-in-2026/#clm-k05-q-007", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-007", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-007.json", "name": "What changed in the advanced-reactor security framework in 2026?", "ownerAnchor": "clm-k05-q-007", "ownerId": "K05-Q-007", "ownerRoute": "/questions/what-changed-in-the-advanced-reactor-security-framework-in-2026/", "ownerType": "question", "proposition": "The NRC published a final Part 53 rule and codified a technology-inclusive security framework in Part 73 Subpart J, including sections 73.100, 73.110, and 73.120. Applicability remains a licensing-path and facility-election question.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for What changed in the advanced-reactor security framework in 2026?", "slug": "clm-k05-q-007", "sourceIds": [ "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "SRC-NRC-10CFR-73-SUBPART-J-2026" ], "sourceSections": [ { "section": "Major provisions and 10 CFR Part 73 security framework", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The final rule creates an alternative technology-inclusive, risk-informed, performance-based framework and a corresponding security framework in Part 73.", "url": "https://www.federalregister.gov/documents/2026/03/30/2026-06048/risk-informed-technology-inclusive-regulatory-framework-for-advanced-reactors" }, { "section": "10 CFR 73.100, 73.110, and 73.120", "sourceId": "SRC-NRC-ADVANCED-REACTOR-PHYSICAL-SECURITY", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Current Subpart J contains technology-inclusive requirements for physical protection, digital systems and networks, and access authorization at covered commercial nuclear plants.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73" }, { "section": "73.100", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive physical-protection requirements are available for qualifying Part 53 licensees that elect the section.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.100" }, { "section": "73.110", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive protection requirements address covered digital computer and communication systems and networks.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.110" }, { "section": "73.120", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Subpart J framework includes an access-authorization program for covered commercial nuclear plants.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.120" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-evidence-is-required-to-claim-operating-readiness/#clm-k05-q-008", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-008", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-008.json", "name": "What evidence is required to claim operating readiness?", "ownerAnchor": "clm-k05-q-008", "ownerId": "K05-Q-008", "ownerRoute": "/questions/what-evidence-is-required-to-claim-operating-readiness/", "ownerType": "question", "proposition": "At minimum: exact release and build hashes, SBOM, configuration and authority records, deployment identity, current uptime window, test and defect evidence, model and data provenance, incident history, recovery results, last independent verification, and unresolved limitations.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for What evidence is required to claim operating readiness?", "slug": "clm-k05-q-008", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Overview", "sourceId": "SRC-RFC-3161", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "A trusted time-stamp can support evidence that a data representation existed by a time; it does not prove the representation is factually true.", "url": "https://www.rfc-editor.org/rfc/rfc3161.html#section-1" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" }, { "section": "Core provenance principle", "sourceId": "SRC-C2PA", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Content Credentials establish provenance information without making a value judgment about whether the provenance data is good or bad.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/explainer/Explainer.html#_core_principles" }, { "section": "Project overview", "sourceId": "SRC-IN-TOTO", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "in-toto records what software supply-chain steps were performed, by whom and in what order to support integrity review.", "url": "https://in-toto.io/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-private-companies-perform-cyber-effects-under-the-2026-us-program-without-approval/#clm-k05-q-009", "claimStatus": "CURRENT LAW OR POLICY", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-009", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-009.json", "name": "Can private companies perform cyber effects under the 2026 U.S. program without approval?", "ownerAnchor": "clm-k05-q-009", "ownerId": "K05-Q-009", "ownerRoute": "/questions/can-private-companies-perform-cyber-effects-under-the-2026-us-program-without-approval/", "ownerType": "question", "proposition": "No. The memorandum requires Federal Government control, oversight and supervision, contractual participation, deconfliction, review of every operations package, and written federal approval and direction before action. It is not a general private hack-back authorization.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for Can private companies perform cyber effects under the 2026 U.S. program without approval?", "slug": "clm-k05-q-009", "sourceIds": [ "SRC-WH-CYBER-CRIME-MEMO-2026" ], "sourceSections": [ { "section": "Sections 1-2 — Purpose, federal control, and program establishment", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The program incorporates private-sector capabilities but requires participating companies to act on behalf of and under Federal Government control, oversight, supervision, and lawful authorities.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Section 3 — Operating procedures and written package approval", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Every operations package requires federal review, written approval and direction, deconfliction, reporting, annual evaluation, and procedures to cease activity outside approved parameters.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" }, { "section": "Section 4 — Definitions and critical outcomes", "sourceId": "SRC-WH-CYBER-CRIME-MEMO-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The memorandum defines surveillance and effects operations and bars program approval of operations likely to cause loss of life, serious injury, or a use of force or armed attack under international law.", "url": "https://www.whitehouse.gov/presidential-actions/2026/08/expanding-capabilities-to-combat-transnational-cyber-enabled-crime/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-an-open-assurance-defeater-mean/#clm-k05-q-010", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-Q-010", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-q-010.json", "name": "What does an open assurance defeater mean?", "ownerAnchor": "clm-k05-q-010", "ownerId": "K05-Q-010", "ownerRoute": "/questions/what-does-an-open-assurance-defeater-mean/", "ownerType": "question", "proposition": "It means a condition exists that can invalidate or materially weaken the claim. The affected readiness or assurance claim must remain qualified, degraded, suspended, or unavailable until competent authority accepts or closes the defeater with evidence.", "qualification": "The answer is bounded by the cited source status, facility applicability, competent authority, and the distinction between architecture, testing, deployment, and operation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 direct answer for What does an open assurance defeater mean?", "slug": "clm-k05-q-010", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/control-mapping-vs-compliance-determination/#clm-k05-cmp-001", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-CMP-001", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-001.json", "name": "Control Mapping versus Compliance Determination", "ownerAnchor": "clm-k05-cmp-001", "ownerId": "K05-CMP-001", "ownerRoute": "/comparisons/control-mapping-vs-compliance-determination/", "ownerType": "comparison", "proposition": "A mapping records relevance and applicability hypotheses; a compliance determination requires the governing authority, facility scope, implementation evidence, exceptions, and authorized judgment.", "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 canonical distinction between Control Mapping and Compliance Determination.", "slug": "clm-k05-cmp-001", "sourceIds": [ "SRC-NIST-800-82R3", "SRC-NIST-800-207", "SRC-NRC-10CFR-73-SUBPART-J-2026", "SRC-NERC-CIP-CATALOG-2026" ], "sourceSections": [ { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-207", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Zero trust shifts protection away from static network perimeters, assumes no implicit trust by location or ownership, and requires discrete authentication and authorization.", "url": "https://csrc.nist.gov/pubs/sp/800/207/final" }, { "section": "73.100", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive physical-protection requirements are available for qualifying Part 53 licensees that elect the section.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.100" }, { "section": "73.110", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Technology-inclusive protection requirements address covered digital computer and communication systems and networks.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.110" }, { "section": "73.120", "sourceId": "SRC-NRC-10CFR-73-SUBPART-J-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The Subpart J framework includes an access-authorization program for covered commercial nuclear plants.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.120" }, { "section": "CIP standards catalog", "sourceId": "SRC-NERC-CIP-CATALOG-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "NERC maintains the official catalog of CIP reliability standards; exact obligations require the current standard text and a facility-specific applicability analysis.", "url": "https://www.nerc.com/standards/reliability-standards/cip" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/assurance-claim-vs-marketing-claim/#clm-k05-cmp-002", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-CMP-002", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-002.json", "name": "Assurance Claim versus Marketing Claim", "ownerAnchor": "clm-k05-cmp-002", "ownerId": "K05-CMP-002", "ownerRoute": "/comparisons/assurance-claim-vs-marketing-claim/", "ownerType": "comparison", "proposition": "An assurance claim exposes evidence, assumptions, defeaters, hazards, and failure conditions; a marketing claim primarily seeks persuasion and may omit what would falsify it.", "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 canonical distinction between Assurance Claim and Marketing Claim.", "slug": "clm-k05-cmp-002", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" }, { "section": "73.54(b)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The regulation requires asset analysis and an implemented and maintained cybersecurity program for protected assets.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/range-result-vs-field-performance/#clm-k05-cmp-003", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-CMP-003", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-003.json", "name": "Evaluation Range Result versus Field Performance", "ownerAnchor": "clm-k05-cmp-003", "ownerId": "K05-CMP-003", "ownerRoute": "/comparisons/range-result-vs-field-performance/", "ownerType": "comparison", "proposition": "A range result supports a bounded test proposition under declared conditions; field performance requires deployment identity, environment, sustainment, incidents, uptime, and current operational evidence.", "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 canonical distinction between Evaluation Range Result and Field Performance.", "slug": "clm-k05-cmp-003", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1.1(a)-(b) — Applicability and exclusions", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The directive applies to autonomous and semi-autonomous weapon systems and expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "Section 1.2(a) — Weapon-system policy", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Within its weapon-system scope, the directive requires appropriate human judgment, rigorous verification and validation, realistic test and evaluation, robustness, transparency, auditability, and bounded engagement behavior.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Critical function focus", "sourceId": "SRC-INL-CCE", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "CCE evaluates what must be safeguarded and applies engineering strategies to isolate and protect critical assets and functions.", "url": "https://inl.gov/feature-story/consequence-driven-cyber-informed-engineering-the-rise-of-a-national-security-pillar/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/source-revalidation-vs-running-monitoring/#clm-k05-cmp-004", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-CMP-004", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-004.json", "name": "Point-in-Time Revalidation versus Running Monitoring", "ownerAnchor": "clm-k05-cmp-004", "ownerId": "K05-CMP-004", "ownerRoute": "/comparisons/source-revalidation-vs-running-monitoring/", "ownerType": "comparison", "proposition": "Revalidation records what an official source said at a declared time; running monitoring requires an operating service, observation cadence, failure handling, and current heartbeat evidence.", "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 canonical distinction between Point-in-Time Revalidation and Running Monitoring.", "slug": "clm-k05-cmp-004", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "Provenance relationships can be represented as entities, activities, agents and qualified relations.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/uas-restriction-vs-counter-uas-mitigation-authority/#clm-k05-cmp-005", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K05 RECORD", "id": "CLM-K05-CMP-005", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k05-cmp-005.json", "name": "Airspace Restriction versus Counter-UAS Mitigation Authority", "ownerAnchor": "clm-k05-cmp-005", "ownerId": "K05-CMP-005", "ownerRoute": "/comparisons/uas-restriction-vs-counter-uas-mitigation-authority/", "ownerType": "comparison", "proposition": "A restriction defines prohibited or controlled flight behavior; mitigation authority separately governs interception, interference, seizure, disabling, or destruction and is actor- and statute-specific.", "qualification": "The distinction prevents category error but does not substitute for a site-, mission-, authority-, or jurisdiction-specific determination.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K05 canonical distinction between Airspace Restriction and Counter-UAS Mitigation Authority.", "slug": "clm-k05-cmp-005", "sourceIds": [ "SRC-FAA-CI-UAS-NPRM-2026", "SRC-USC-6-124N", "SRC-USC-47-333" ], "sourceSections": [ { "section": "Proposed petition process", "sourceId": "SRC-FAA-CI-UAS-NPRM-2026", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The FAA proposed a process for operators of certain critical-infrastructure sites to petition for restrictions on drone operations over those sites.", "url": "https://www.faa.gov/newsroom/restricting-drones-near-critical-infrastructure-sites" }, { "section": "Authorities and covered facilities", "sourceId": "SRC-USC-6-124N", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "The statute assigns specified counter-UAS authorities and constraints to federal departments for covered facilities and missions.", "url": "https://uscode.house.gov/view.xhtml?req=%28title%3A6+section%3A124n+edition%3Aprelim%29" }, { "section": "Section 333 prohibition", "sourceId": "SRC-USC-47-333", "supportRelationship": "QUALIFIES OR SUPPORTS WITHIN STATED SCOPE", "supports": "No person may willfully or maliciously interfere with authorized radio communications, absent a separate applicable authority or exception.", "url": "https://uscode.house.gov/view.xhtml?req=%28title%3A47+section%3A333+edition%3Aprelim%29" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/machine-communication-protocols/#clm-k08-top-001-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K08 RECORD", "id": "CLM-K08-TOP-001-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k08-top-001-a.json", "name": "Machine communication protocols — explicit semantics", "ownerAnchor": "clm-k08-top-001-a", "ownerId": "K08-TOPIC-MCP", "ownerRoute": "/knowledge/machine-communication-protocols/", "ownerType": "topic", "proposition": "A machine communication protocol requires explicit semantics, versioning, error behavior, identity, authority, and extension rules; a script or glyph inventory alone is not a protocol.", "qualification": "The proposition is K08 design doctrine and does not claim a universal or adopted protocol standard.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K08 project doctrine for bounded machine-to-machine protocol design.", "slug": "clm-k08-top-001-a", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic code chart", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "BOUNDS CHARACTER IDENTITY ONLY", "supports": "Unicode assigns Runic character code points and names; it does not define the K08 protocol semantics.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/machine-communication-protocols/#clm-k08-top-001-b", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K08 RECORD", "id": "CLM-K08-TOP-001-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k08-top-001-b.json", "name": "Machine communication protocols — security boundary", "ownerAnchor": "clm-k08-top-001-b", "ownerId": "K08-TOPIC-MCP", "ownerRoute": "/knowledge/machine-communication-protocols/", "ownerType": "topic", "proposition": "A constrained symbolic notation can simplify validation but does not authenticate a sender, authorize an action, protect confidentiality, prevent replay, or make tool execution safe.", "qualification": "Authentication, authorization, and transport controls remain separate design and deployment evidence.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K08 security boundary for symbolic machine communication.", "slug": "clm-k08-top-001-b", "sourceIds": [ "SRC-NIST-FIPS204-2024", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Digital signature standard", "sourceId": "SRC-NIST-FIPS204-2024", "supportRelationship": "SUPPORTS SIGNATURE LAYER DISTINCTION", "supports": "A signature algorithm provides a cryptographic mechanism distinct from the notation being signed.", "url": "https://csrc.nist.gov/pubs/fips/204/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/machine-communication-protocols/#clm-k08-top-001-c", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K08 RECORD", "id": "CLM-K08-TOP-001-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k08-top-001-c.json", "name": "Machine communication protocols — benchmark discipline", "ownerAnchor": "clm-k08-top-001-c", "ownerId": "K08-TOPIC-MCP", "ownerRoute": "/knowledge/machine-communication-protocols/", "ownerType": "topic", "proposition": "No candidate encoding should be preferred until it meets task accuracy, failure safety, interoperability, and accessibility thresholds before efficiency is ranked.", "qualification": "K08 publishes a benchmark plan and no current superiority result.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K08 experimental benchmark acceptance rule.", "slug": "clm-k08-top-001-c", "sourceIds": [ "SRC-UNICODE-UAX15-17", "SRC-RFC-5646" ], "sourceSections": [ { "section": "Normalization conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "SUPPORTS REPEATABLE TEXT PROCESSING", "supports": "Normalization is one prerequisite for reproducible cross-system text comparison.", "url": "https://www.unicode.org/reports/tr15/" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/runic-digital-infrastructure/#clm-k08-top-002-a", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K08 RECORD", "id": "CLM-K08-TOP-002-A", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k08-top-002-a.json", "name": "Runic digital infrastructure — distinct domain states", "ownerAnchor": "clm-k08-top-002-a", "ownerId": "K08-TOPIC-RDI", "ownerRoute": "/knowledge/runic-digital-infrastructure/", "ownerType": "topic", "proposition": "Unicode validity, IDNA validity, registry permission, registration, delegation, DNS resolution, TLS validity, and observed hosting are distinct evidence states.", "qualification": "Later domain states require independent observation; they are not inferred from encoding success.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K08 domain-lifecycle evidence architecture.", "slug": "clm-k08-top-002-a", "sourceIds": [ "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "IDNA definitions", "sourceId": "SRC-RFC-5890", "supportRelationship": "SUPPORTS U-LABEL AND A-LABEL DISTINCTION", "supports": "IDNA defines Unicode and ASCII-compatible label forms independently from registry and hosting operation.", "url": "https://www.rfc-editor.org/rfc/rfc5890" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/runic-digital-infrastructure/#clm-k08-top-002-b", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K08 RECORD", "id": "CLM-K08-TOP-002-B", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k08-top-002-b.json", "name": "Runic digital infrastructure — project identity boundary", "ownerAnchor": "clm-k08-top-002-b", "ownerId": "K08-TOPIC-RDI", "ownerRoute": "/knowledge/runic-digital-infrastructure/", "ownerType": "topic", "proposition": "A project may assign a modern continuity mapping to a Runic glyph while explicitly refusing to present that mapping as an authoritative historical translation.", "qualification": "The continuity mapping remains project doctrine rather than a historical or linguistic authority claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K08 identity and historical-evidence boundary.", "slug": "clm-k08-top-002-b", "sourceIds": [ "SRC-UNICODE-RUNIC-17" ], "sourceSections": [ { "section": "Runic character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "BOUNDS CHARACTER IDENTITY", "supports": "The official code chart identifies encoded characters without assigning K08 institutional roles.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/knowledge/runic-digital-infrastructure/#clm-k08-top-002-c", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K08 RECORD", "id": "CLM-K08-TOP-002-C", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k08-top-002-c.json", "name": "Runic digital infrastructure — discoverability parity", "ownerAnchor": "clm-k08-top-002-c", "ownerId": "K08-TOPIC-RDI", "ownerRoute": "/knowledge/runic-digital-infrastructure/", "ownerType": "topic", "proposition": "Cross-script discoverability should use accurate language metadata, visible accessible equivalents, semantic HTML, crawlable links, and structured-data parity rather than hidden crawler-only translations.", "qualification": "Accessible names must serve accessibility and must not be repurposed as hidden keyword documents.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K08 accessibility and discoverability architecture.", "slug": "clm-k08-top-002-c", "sourceIds": [ "SRC-RFC-5646", "SRC-W3C-WCAG22", "SRC-UNICODE-UAX15-17" ], "sourceSections": [ { "section": "Language tags", "sourceId": "SRC-RFC-5646", "supportRelationship": "SUPPORTS ACCURATE LANGUAGE AND SCRIPT METADATA", "supports": "BCP 47 defines language tags used to identify language and script attributes.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/conformance/#clm-k09-001", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K09 RECORD", "id": "CLM-K09-001", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k09-001.json", "name": "Conformance is bounded", "ownerAnchor": "clm-k09-001", "ownerId": "K09-PAGE-CONFORMANCE", "ownerRoute": "/machine-communication/conformance/", "ownerType": "page", "proposition": "A protocol conformance result is limited to the declared fixtures, representation rules, parser behavior, and test implementation.", "qualification": "No superiority, security, authority, network deployment, or historical-semantic claim follows.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K09 Fuþorc protocol reference harness.", "slug": "clm-k09-001", "sourceIds": [ "SRC-UNICODE-RUNIC-17" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "BOUNDS ENCODED CHARACTER INVENTORY", "supports": "The official code chart identifies the encoded Runic characters used by the reference harness; project semantics and conformance behavior remain separately declared implementation evidence.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/idn-observations/#clm-k09-002", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K09 RECORD", "id": "CLM-K09-002", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k09-002.json", "name": "Domain states remain independent", "ownerAnchor": "clm-k09-002", "ownerId": "K09-PAGE-IDN", "ownerRoute": "/machine-communication/idn-observations/", "ownerType": "page", "proposition": "K09 stores Unicode, IDNA, registry, registration, delegation, DNS, TLS, and hosting states independently.", "qualification": "The bundled reference fixture performs no live registry, DNS, TLS, or hosting check.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "Offline IDN observation importer and public records.", "slug": "clm-k09-002", "sourceIds": [ "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Definitions and document framework", "sourceId": "SRC-RFC-5890", "supportRelationship": "SUPPORTS U-LABEL AND A-LABEL SEPARATION", "supports": "IDNA terminology distinguishes Unicode labels and ASCII-compatible labels without establishing later registry, registration, delegation, DNS, TLS, or hosting states.", "url": "https://www.rfc-editor.org/rfc/rfc5890" }, { "section": "Protocol scope", "sourceId": "SRC-RFC-5891", "supportRelationship": "BOUNDS IDNA PROTOCOL PROCESSING", "supports": "IDNA application processing remains distinct from registry policy and live operational observations.", "url": "https://www.rfc-editor.org/rfc/rfc5891" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/evidence/partitions/#clm-k09-003", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K09 RECORD", "id": "CLM-K09-003", "lastReviewed": "2026-08-15", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k09-003.json", "name": "Protected details are excluded", "ownerAnchor": "clm-k09-003", "ownerId": "K09-PAGE-PARTITIONS", "ownerRoute": "/evidence/partitions/", "ownerType": "page", "proposition": "K09 workbook and evidence-partition tooling rejects credential and protected-topology fields from public fixtures.", "qualification": "Static validation is not a substitute for production access control, classification review, or secure storage.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-15", "scope": "K09 offline reference tools and synthetic fixtures.", "slug": "clm-k09-003", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS REFERENCE-BASED PROVENANCE RELATIONSHIPS", "supports": "Provenance relationships can identify external entities and activities without copying protected source material into a public record.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/protocol-negotiation/#clm-k10-001", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K10 RECORD", "id": "CLM-K10-001", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k10-001.json", "name": "Negotiation behavior is executable and bounded", "ownerAnchor": "clm-k10-001", "ownerId": "K10-PAGE-PROTOCOL", "ownerRoute": "/machine-communication/protocol-negotiation/", "ownerType": "page", "proposition": "K10 deterministically tests version selection, extension handling, canonicalization, replay-window behavior, compatibility profiles, and generated token sequences.", "qualification": "The result does not establish security, authorization, deployment, performance superiority, or authoritative historical semantics.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K10 synthetic Fuþorc protocol reference harness.", "slug": "clm-k10-001", "sourceIds": [ "SRC-UNICODE-RUNIC-17" ], "sourceSections": [ { "section": "Runic code chart", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "BOUNDS ENCODED CHARACTER INVENTORY", "supports": "The official chart identifies the encoded Runic characters used by the reference protocol; project semantics and negotiation behavior remain separately declared implementation evidence.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/history-review-queue/#clm-k10-002", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K10 RECORD", "id": "CLM-K10-002", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k10-002.json", "name": "History remains review-bounded", "ownerAnchor": "clm-k10-002", "ownerId": "K10-PAGE-HISTORY", "ownerRoute": "/machine-communication/history-review-queue/", "ownerType": "page", "proposition": "Every K09 history event has a K10 primary-source review record and no event is silently promoted by the K10 release.", "qualification": "Queue completeness is not historical verification; source-derived claims retain their uncertainty.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K10 history review queue and synthetic supersession receipts.", "slug": "clm-k10-002", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS APPEND-ONLY PROVENANCE RELATIONSHIPS", "supports": "Provenance relationships can preserve source, review, revision, and supersession relationships without converting a source assertion into verified history.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/idn-observation-history/#clm-k10-003", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K10 RECORD", "id": "CLM-K10-003", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k10-003.json", "name": "External state remains offline and explicit", "ownerAnchor": "clm-k10-003", "ownerId": "K10-PAGE-IDN", "ownerRoute": "/machine-communication/idn-observation-history/", "ownerType": "page", "proposition": "K10 compares signed or governed offline IDN and scheduler records without performing public runtime network acquisition or scheduling.", "qualification": "Accepted payload integrity does not prove live DNS, DNSSEC, TLS, certificate, browser, hosting, or factual observation states.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K10 offline IDN and scheduler result tools.", "slug": "clm-k10-003", "sourceIds": [ "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Definitions and document framework", "sourceId": "SRC-RFC-5890", "supportRelationship": "SUPPORTS U-LABEL AND A-LABEL SEPARATION", "supports": "IDNA terminology separates representation from later registry, DNS, TLS, browser, hosting, and service states.", "url": "https://www.rfc-editor.org/rfc/rfc5890" }, { "section": "Protocol scope", "sourceId": "SRC-RFC-5891", "supportRelationship": "BOUNDS APPLICATION PROCESSING", "supports": "IDNA application processing does not establish live domain operation or service currentness.", "url": "https://www.rfc-editor.org/rfc/rfc5891" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/evidence/redaction-receipts/#clm-k10-004", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K10 RECORD", "id": "CLM-K10-004", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k10-004.json", "name": "Protected fields remain excluded", "ownerAnchor": "clm-k10-004", "ownerId": "K10-PAGE-REDACTION", "ownerRoute": "/evidence/redaction-receipts/", "ownerType": "page", "proposition": "K10 workbook migration, controlled-release, and leakage tests preserve protected references while excluding prohibited values from public projections.", "qualification": "Static validation is not production access control, classification review, or secure storage.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K10 reference tools, fixtures, and public datasets.", "slug": "clm-k10-004", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Entities, activities, and agents", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS REFERENCE-BASED PUBLIC PROVENANCE", "supports": "Public records may preserve relationships to separately held evidence without reproducing protected content.", "url": "https://www.w3.org/TR/prov-o/#description-starting-point-terms" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-dashboard/#clm-k10-005", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K10 RECORD", "id": "CLM-K10-005", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k10-005.json", "name": "Dashboard states remain distinct", "ownerAnchor": "clm-k10-005", "ownerId": "K10-PAGE-DASHBOARD", "ownerRoute": "/assurance-dashboard/", "ownerType": "page", "proposition": "The K10 assurance dashboard does not infer deployment or operation from described architecture, implemented tooling, or test evidence.", "qualification": "The dashboard is a release-time static derivation, not live telemetry.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Static K10 cross-system dashboard.", "slug": "clm-k10-005", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS STATE-SPECIFIC EVIDENCE RELATIONSHIPS", "supports": "Provenance relationships support explicit evidence scope but do not infer deployment or operation from document existence.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/protocol-state-machine/#clm-k11-001", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K11 RECORD", "id": "CLM-K11-001", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k11-001.json", "name": "Protocol state behavior is model-tested across two decoders", "ownerAnchor": "clm-k11-001", "ownerId": "K11-PAGE-PROTOCOL", "ownerRoute": "/machine-communication/protocol-state-machine/", "ownerType": "page", "proposition": "K11 executes declared state transitions, invalid-transition rejection, downgrade and retirement behavior, replay persistence, recovery, and canonical transcript comparison using reference and independently implemented decoders.", "qualification": "Model and decoder agreement do not establish authentication, authorization, security completeness, performance, or deployment.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K11 synthetic protocol state-machine harness.", "slug": "clm-k11-001", "sourceIds": [ "SRC-UNICODE-RUNIC-17" ], "sourceSections": [ { "section": "Runic code chart", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "BOUNDS ENCODED CHARACTER INVENTORY", "supports": "The official code chart identifies encoded Runic characters; the K11 state model and project semantics remain separately declared implementation evidence.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/history-evidence-docket/#clm-k11-002", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K11 RECORD", "id": "CLM-K11-002", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k11-002.json", "name": "Historical evidence remains acquisition-bounded", "ownerAnchor": "clm-k11-002", "ownerId": "K11-PAGE-HISTORY", "ownerRoute": "/machine-communication/history-evidence-docket/", "ownerType": "page", "proposition": "Every K09 history event is represented by a K11 evidence-acquisition docket and no event is promoted without accepted primary evidence and adjudicated review.", "qualification": "Docket completeness and source custody do not independently establish historical truth.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K11 history docket and duplicate-source model.", "slug": "clm-k11-002", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS SOURCE, REVIEW, AND SUPERSESSION RELATIONSHIPS", "supports": "Provenance relationships can preserve acquisition, review, dispute, rejection, and supersession without turning a source assertion into verified history.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/domain-observation-chain/#clm-k11-003", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K11 RECORD", "id": "CLM-K11-003", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k11-003.json", "name": "Domain observation custody remains offline and multi-observer", "ownerAnchor": "clm-k11-003", "ownerId": "K11-PAGE-DOMAIN", "ownerRoute": "/machine-communication/domain-observation-chain/", "ownerType": "page", "proposition": "K11 validates three signed offline observer bundles covering all nine Runic domains while preserving every external lifecycle field as unobserved or unavailable.", "qualification": "Signatures validate payload relationships, not live DNS, TLS, hosting, ownership, operation, or factual accuracy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K11 offline domain observation chain.", "slug": "clm-k11-003", "sourceIds": [ "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Definitions and document framework", "sourceId": "SRC-RFC-5890", "supportRelationship": "SUPPORTS U-LABEL AND A-LABEL SEPARATION", "supports": "IDNA terminology separates representation from registry, DNS, DNSSEC, certificate, TLS, hosting, ownership, and operation states.", "url": "https://www.rfc-editor.org/rfc/rfc5890" }, { "section": "Protocol scope", "sourceId": "SRC-RFC-5891", "supportRelationship": "BOUNDS APPLICATION PROCESSING", "supports": "Application processing does not establish live domain service state.", "url": "https://www.rfc-editor.org/rfc/rfc5891" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/facility-adaptation/decision-ledger/#clm-k11-004", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K11 RECORD", "id": "CLM-K11-004", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k11-004.json", "name": "Decision conflicts and revocations propagate visibly", "ownerAnchor": "clm-k11-004", "ownerId": "K11-PAGE-WORKBOOK", "ownerRoute": "/facility-adaptation/decision-ledger/", "ownerType": "page", "proposition": "K11 preserves N-way workbook conflicts, signer rotation, revoked decisions, and protected-reference custody without silently selecting an owner decision or publishing protected values.", "qualification": "Reference merge and custody tooling are not a production facility record system or authority decision.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K11 workbook decision ledger and public redaction model.", "slug": "clm-k11-004", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Entities, activities, and agents", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS DECISION, CUSTODY, AND SUPERSESSION RELATIONSHIPS", "supports": "Public records can preserve decision, custody, revocation, and supersession relationships while excluding protected values.", "url": "https://www.w3.org/TR/prov-o/#description-starting-point-terms" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/mission-threads/#clm-k11-005", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K11 RECORD", "id": "CLM-K11-005", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k11-005.json", "name": "Mission-thread failure remains abstract and bounded", "ownerAnchor": "clm-k11-005", "ownerId": "K11-PAGE-MISSION", "ownerRoute": "/assurance-case/mission-threads/", "ownerType": "page", "proposition": "K11 derives dependency centrality, abstract single points, correlated groups, partial scenario-control coverage, and freshness impacts without publishing protected configuration.", "qualification": "The analysis is not a real facility vulnerability assessment, attack path, or certification.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K11 synthetic mission-thread assurance model.", "slug": "clm-k11-005", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS EXPLICIT DEPENDENCY AND EVIDENCE RELATIONSHIPS", "supports": "Public assurance records can preserve abstract dependency and evidence relationships while excluding protected configuration.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-dashboard/trends/#clm-k11-006", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K11 RECORD", "id": "CLM-K11-006", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k11-006.json", "name": "Release trends do not manufacture operation", "ownerAnchor": "clm-k11-006", "ownerId": "K11-PAGE-TRENDS", "ownerRoute": "/assurance-dashboard/trends/", "ownerType": "page", "proposition": "K11 compares K09-K11 static evidence while preserving separate DESCRIBED, IMPLEMENTED, TESTED, DEPLOYED, OPERATING, DEGRADED, STALE, UNAVAILABLE, and UNKNOWN states and zero inferred live operation.", "qualification": "Release dates are publication metadata, not telemetry or current operational observations.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K11 static assurance trend dashboard.", "slug": "clm-k11-006", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS VERSIONED EVIDENCE RELATIONSHIPS", "supports": "Versioned provenance can support release comparisons without inferring live deployment or operation.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/differential-protocol-lab/#clm-k12-001", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-001", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-001.json", "name": "Differential protocol results agree across three independent decoders", "ownerAnchor": "clm-k12-001", "ownerId": "K12-PAGE-001", "ownerRoute": "/machine-communication/differential-protocol-lab/", "ownerType": "page", "proposition": "K12 replays inherited, generated valid, and malformed protocol sequences through three independently implemented decoders and compares canonical transcripts.", "qualification": "Agreement is bounded to tested synthetic inputs and is not a security, performance, or deployment claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-001", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic code chart", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "BOUNDS ENCODED CHARACTER INVENTORY", "supports": "The official code chart identifies the encoded Runic characters used by the inherited reference protocol; differential decoding behavior remains separate project implementation evidence.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/history-docket-import/#clm-k12-002", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-002", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-002.json", "name": "Signed historical docket import remains review-only", "ownerAnchor": "clm-k12-002", "ownerId": "K12-PAGE-002", "ownerRoute": "/machine-communication/history-docket-import/", "ownerType": "page", "proposition": "K12 verifies a signed offline history package and queues its records without automatically promoting any historical event.", "qualification": "Signature validity establishes integrity and a signer relationship, not historical truth.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-002", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Entities, activities, and agents", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS CUSTODY, REVIEW, AND SUPERSESSION RELATIONSHIPS", "supports": "Provenance relationships can preserve source custody, reviewer assignment, correction, rejection, and supersession without converting a signed assertion into historical truth.", "url": "https://www.w3.org/TR/prov-o/#description-starting-point-terms" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/machine-communication/domain-consensus/#clm-k12-003", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-003", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-003.json", "name": "Runic-domain consensus preserves external-state uncertainty", "ownerAnchor": "clm-k12-003", "ownerId": "K12-PAGE-003", "ownerRoute": "/machine-communication/domain-consensus/", "ownerType": "page", "proposition": "K12 records quorum for reference U-label and ACE relationships while preserving external registration, DNS, TLS, hosting, ownership, and operation as unobserved.", "qualification": "No live network acquisition occurred.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-003", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Definitions and document framework", "sourceId": "SRC-RFC-5890", "supportRelationship": "SUPPORTS U-LABEL AND A-LABEL SEPARATION", "supports": "IDNA terminology separates encoding representation from registry, DNS, DNSSEC, certificate, browser, hosting, ownership, and operation states.", "url": "https://www.rfc-editor.org/rfc/rfc5890" }, { "section": "Protocol scope", "sourceId": "SRC-RFC-5891", "supportRelationship": "BOUNDS APPLICATION PROCESSING", "supports": "Application processing does not establish live external lifecycle state.", "url": "https://www.rfc-editor.org/rfc/rfc5891" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/facility-adaptation/branch-reconciliation/#clm-k12-004", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-004", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-004.json", "name": "Facility branch reconciliation preserves owner conflicts", "ownerAnchor": "clm-k12-004", "ownerId": "K12-PAGE-004", "ownerRoute": "/facility-adaptation/branch-reconciliation/", "ownerType": "page", "proposition": "K12 combines non-conflicting workbook content, records signer succession and revoked-decision impact, and leaves mission-significant conflicts unresolved.", "qualification": "Synthetic workbooks are not facility findings or owner authority.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-004", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS DECISION, CUSTODY, AND REVISION RELATIONSHIPS", "supports": "Public records can preserve branch, decision, signer, custody, correction, and supersession relationships while excluding protected values.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-case/mission-stress/#clm-k12-005", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-005", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-005.json", "name": "Mission stress tests propagate stale and unavailable dependencies", "ownerAnchor": "clm-k12-005", "ownerId": "K12-PAGE-005", "ownerRoute": "/assurance-case/mission-stress/", "ownerType": "page", "proposition": "K12 injects deterministic evidence failures and records recovery sequences, affected threads, coverage gaps, and promotion blocks.", "qualification": "Public fixtures contain no protected facility architecture.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-005", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS DEPENDENCY AND EVIDENCE RELATIONSHIPS", "supports": "Versioned provenance can represent abstract dependency, evidence aging, recovery, and change-impact relationships without publishing protected configuration.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/cryptographic-agility/evidence-gates/#clm-k12-006", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-006", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-006.json", "name": "Cryptographic transition remains evidence-gated", "ownerAnchor": "clm-k12-006", "ownerId": "K12-PAGE-006", "ownerRoute": "/cryptographic-agility/evidence-gates/", "ownerType": "page", "proposition": "K12 evaluates ten evidence gates for each component workbook and authorizes no production transition.", "qualification": "Reference gate results are not production migration evidence.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-006", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS COMPONENT-SPECIFIC EVIDENCE RELATIONSHIPS", "supports": "Evidence records can expose component gate state, acceptance, rejection, and expiry without establishing deployed cryptographic operation.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/procurement/evaluation-replay/#clm-k12-007", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-007", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-007.json", "name": "Acquisition replay preserves zero-award boundaries", "ownerAnchor": "clm-k12-007", "ownerId": "K12-PAGE-007", "ownerRoute": "/procurement/evaluation-replay/", "ownerType": "page", "proposition": "K12 records timeliness, stays, remand scope, corrective action, reevaluation variance, supersession, and public debrief consistency for six synthetic cases.", "qualification": "No source selection or award is made.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-007", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Entities, activities, and agents", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS PROCESS REPLAY AND SUPERSESSION", "supports": "Process records can preserve replay, challenge, remand, corrective action, and supersession without making an award.", "url": "https://www.w3.org/TR/prov-o/#description-starting-point-terms" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/continuous-assurance/reliability-simulator/#clm-k12-008", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-008", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-008.json", "name": "Scheduler reliability simulation has no public runtime", "ownerAnchor": "clm-k12-008", "ownerId": "K12-PAGE-008", "ownerRoute": "/continuous-assurance/reliability-simulator/", "ownerType": "page", "proposition": "K12 models maintenance, duplicate suppression, catch-up, idempotency, missed runs, repair, retest, and signed offline import for six schedules.", "qualification": "No scheduler is installed or operating on the public site.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-008", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS OFFLINE RESULT CUSTODY", "supports": "Signed offline results can preserve custody and sequence while remaining distinct from a public scheduler runtime.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/evidence/information-flow/#clm-k12-009", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-009", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-009.json", "name": "Information-flow projections exclude protected values", "ownerAnchor": "clm-k12-009", "ownerId": "K12-PAGE-009", "ownerRoute": "/evidence/information-flow/", "ownerType": "page", "proposition": "K12 labels fields and validates projection transformations and leakage negatives without including removed protected values.", "qualification": "Static modeling is not production access-control enforcement.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-009", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Entities, activities, and agents", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS RELEASE TRANSFORMATION PROVENANCE", "supports": "Public projections can preserve the relationship to protected source fields without reproducing protected values.", "url": "https://www.w3.org/TR/prov-o/#description-starting-point-terms" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/assurance-dashboard/k09-k12-diffs/#clm-k12-010", "claimStatus": "VERIFIED PROJECT IMPLEMENTATION", "correctionStatus": "CURRENT K12 RECORD", "id": "CLM-K12-010", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k12-010.json", "name": "K09–K12 assurance diffs manufacture no operation", "ownerAnchor": "clm-k12-010", "ownerId": "K12-PAGE-010", "ownerRoute": "/assurance-dashboard/k09-k12-diffs/", "ownerType": "page", "proposition": "K12 publishes static diff receipts and trends without assigning DEPLOYED or OPERATING states absent independent operational evidence.", "qualification": "Release comparison is not live telemetry.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K12 deterministic local reference implementation.", "slug": "clm-k12-010", "sourceIds": [ "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "PROV-O at a glance", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "SUPPORTS VERSIONED EVIDENCE COMPARISON", "supports": "Release-to-release provenance can support static assurance comparisons without inferring deployment, telemetry, or operation.", "url": "https://www.w3.org/TR/prov-o/#prov-o-at-a-glance" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-an-assurance-dependency-graph/#clm-k07-q-001", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-001", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-001.json", "name": "What is an assurance dependency graph?", "ownerAnchor": "clm-k07-q-001", "ownerId": "K07-Q-001", "ownerRoute": "/questions/what-is-an-assurance-dependency-graph/", "ownerType": "question", "proposition": "It is a machine-checkable model showing which controls, tests, and evidence support each assurance claim and how failures, stale evidence, and active defeaters propagate.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What is an assurance dependency graph?", "slug": "clm-k07-q-001", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-does-stale-evidence-affect-assurance/#clm-k07-q-002", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-002", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-002.json", "name": "How does stale evidence affect assurance?", "ownerAnchor": "clm-k07-q-002", "ownerId": "K07-Q-002", "ownerRoute": "/questions/how-does-stale-evidence-affect-assurance/", "ownerType": "question", "proposition": "Stale evidence downgrades dependent controls and claims until current independent evidence or an approved exception restores support.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for How does stale evidence affect assurance?", "slug": "clm-k07-q-002", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-a-facility-pattern/#clm-k07-q-003", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-003", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-003.json", "name": "What is a facility pattern?", "ownerAnchor": "clm-k07-q-003", "ownerId": "K07-Q-003", "ownerRoute": "/questions/what-is-a-facility-pattern/", "ownerType": "question", "proposition": "A facility pattern is a reusable, non-certifying architecture and evidence profile that must be replaced with site facts, authority, current sources, and test results.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What is a facility pattern?", "slug": "clm-k07-q-003", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-makes-a-work-package-procurement-ready/#clm-k07-q-004", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-004", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-004.json", "name": "What makes a work package procurement-ready?", "ownerAnchor": "clm-k07-q-004", "ownerId": "K07-Q-004", "ownerRoute": "/questions/what-makes-a-work-package-procurement-ready/", "ownerType": "question", "proposition": "It names inputs, deliverables, dependencies, acceptance evidence, exclusions, authority boundaries, and the decision owner instead of promising an undefined capability.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What makes a work package procurement-ready?", "slug": "clm-k07-q-004", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/is-offline-currentness-import-live-monitoring/#clm-k07-q-005", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-005", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-005.json", "name": "Is offline currentness import live monitoring?", "ownerAnchor": "clm-k07-q-005", "ownerId": "K07-Q-005", "ownerRoute": "/questions/is-offline-currentness-import-live-monitoring/", "ownerType": "question", "proposition": "No. It validates a supplied signed snapshot bundle without network access and cannot establish what a source says after the observation time.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Is offline currentness import live monitoring?", "slug": "clm-k07-q-005", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-mapping-quality-mean/#clm-k07-q-006", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-006", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-006.json", "name": "What does mapping quality mean?", "ownerAnchor": "clm-k07-q-006", "ownerId": "K07-Q-006", "ownerRoute": "/questions/what-does-mapping-quality-mean/", "ownerType": "question", "proposition": "It states whether a control relationship is exact, partial, informative, conflicting, superseded, not applicable, or unresolved for a named scope.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What does mapping quality mean?", "slug": "clm-k07-q-006", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-red-team-evidence-be-public-without-publishing-exploits/#clm-k07-q-007", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-007", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-007.json", "name": "Can red-team evidence be public without publishing exploits?", "ownerAnchor": "clm-k07-q-007", "ownerId": "K07-Q-007", "ownerRoute": "/questions/can-red-team-evidence-be-public-without-publishing-exploits/", "ownerType": "question", "proposition": "Yes. Public evidence can disclose authority, objective, behavior class, control response, timing, defects, and hashes while withholding exploit, payload, credential, persistence, evasion, topology, and destructive details.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can red-team evidence be public without publishing exploits?", "slug": "clm-k07-q-007", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/when-is-post-deployment-observation-valid/#clm-k07-q-008", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-008", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-008.json", "name": "When is post-deployment observation valid?", "ownerAnchor": "clm-k07-q-008", "ownerId": "K07-Q-008", "ownerRoute": "/questions/when-is-post-deployment-observation-valid/", "ownerType": "question", "proposition": "Only after the owner confirms deployment and authorizes the exact observation scope, allowing the deployed manifest and service evidence to be compared with the approved release.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for When is post-deployment observation valid?", "slug": "clm-k07-q-008", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-a-national-cyber-strategy-authorize-private-effects/#clm-k07-q-009", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-009", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-009.json", "name": "Does a national cyber strategy authorize private cyber effects?", "ownerAnchor": "clm-k07-q-009", "ownerId": "K07-Q-009", "ownerRoute": "/questions/does-a-national-cyber-strategy-authorize-private-effects/", "ownerType": "question", "proposition": "Not by itself. A strategy describes policy and capability; a private entity needs separate competent authority, scope, deconfliction, controls, and accountability.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does a national cyber strategy authorize private cyber effects?", "slug": "clm-k07-q-009", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-must-facility-profiles-remain-non-certifying/#clm-k07-q-010", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-010", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-010.json", "name": "Why must facility profiles remain non-certifying?", "ownerAnchor": "clm-k07-q-010", "ownerId": "K07-Q-010", "ownerRoute": "/questions/why-must-facility-profiles-remain-non-certifying/", "ownerType": "question", "proposition": "Because licensing, regulation, topology, hazards, contracts, authority, implementation, and operating evidence differ by site and cannot be inferred from a public pattern.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Why must facility profiles remain non-certifying?", "slug": "clm-k07-q-010", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-a-facility-evidence-bundle/#clm-k07-q-011", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-011", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-011.json", "name": "What is a facility evidence bundle?", "ownerAnchor": "clm-k07-q-011", "ownerId": "K07-Q-011", "ownerRoute": "/questions/what-is-a-facility-evidence-bundle/", "ownerType": "question", "proposition": "It is a site-identified package that binds authority, scope, facility facts, artifacts, claims, limitations, provenance, and integrity evidence without treating a generic pattern as a site finding.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What is a facility evidence bundle?", "slug": "clm-k07-q-011", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-can-a-generic-pattern-not-prove-site-readiness/#clm-k07-q-012", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-012", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-012.json", "name": "Why can a generic facility pattern not prove site readiness?", "ownerAnchor": "clm-k07-q-012", "ownerId": "K07-Q-012", "ownerRoute": "/questions/why-can-a-generic-pattern-not-prove-site-readiness/", "ownerType": "question", "proposition": "Because actual topology, hazards, authority, license conditions, dependencies, implementation, test results, incidents, and operating state differ by site.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Why can a generic facility pattern not prove site readiness?", "slug": "clm-k07-q-012", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-a-signed-evidence-receipt-prove/#clm-k07-q-013", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-013", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-013.json", "name": "What does a signed evidence receipt prove?", "ownerAnchor": "clm-k07-q-013", "ownerId": "K07-Q-013", "ownerRoute": "/questions/what-does-a-signed-evidence-receipt-prove/", "ownerType": "question", "proposition": "It can prove that a named key signed a defined receipt payload and that the payload has not changed; it does not automatically prove the evidence is true, complete, applicable, current, or authorized.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What does a signed evidence receipt prove?", "slug": "clm-k07-q-013", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-happens-when-evidence-is-superseded/#clm-k07-q-014", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-014", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-014.json", "name": "What happens when evidence is superseded?", "ownerAnchor": "clm-k07-q-014", "ownerId": "K07-Q-014", "ownerRoute": "/questions/what-happens-when-evidence-is-superseded/", "ownerType": "question", "proposition": "The successor is linked to the prior receipt, the earlier record remains historical, and dependent assurance claims are re-evaluated rather than silently inheriting the old state.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What happens when evidence is superseded?", "slug": "clm-k07-q-014", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-bills-of-materials-are-needed-for-critical-datacenters/#clm-k07-q-015", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-015", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-015.json", "name": "What bills of materials are needed for critical datacenters?", "ownerAnchor": "clm-k07-q-015", "ownerId": "K07-Q-015", "ownerRoute": "/questions/what-bills-of-materials-are-needed-for-critical-datacenters/", "ownerType": "question", "proposition": "Software, hardware/manufacturing, firmware, model-system, and data lineage records are needed because no single bill of materials covers the full cyber-physical supply chain.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What bills of materials are needed for critical datacenters?", "slug": "clm-k07-q-015", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-makes-a-statement-of-work-measurable/#clm-k07-q-016", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-016", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-016.json", "name": "What makes a statement of work measurable?", "ownerAnchor": "clm-k07-q-016", "ownerId": "K07-Q-016", "ownerRoute": "/questions/what-makes-a-statement-of-work-measurable/", "ownerType": "question", "proposition": "It identifies required results, performance standards, assessment methods, deliverable evidence, outcome states, dependencies, exclusions, and nonconformance handling.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What makes a statement of work measurable?", "slug": "clm-k07-q-016", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-a-negative-result-clause/#clm-k07-q-017", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-017", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-017.json", "name": "What is a negative-result clause?", "ownerAnchor": "clm-k07-q-017", "ownerId": "K07-Q-017", "ownerRoute": "/questions/what-is-a-negative-result-clause/", "ownerType": "question", "proposition": "It prevents failed, partial, stale, disputed, unavailable, or superseded findings from being hidden or rewritten as a pass.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What is a negative-result clause?", "slug": "clm-k07-q-017", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-a-digital-twin-control-a-live-facility/#clm-k07-q-018", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-018", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-018.json", "name": "Can a digital twin control a live facility?", "ownerAnchor": "clm-k07-q-018", "ownerId": "K07-Q-018", "ownerRoute": "/questions/can-a-digital-twin-control-a-live-facility/", "ownerType": "question", "proposition": "Not under the K07 public evidence contract. A twin is isolated from production control and cannot be treated as a live command path or proof of site fidelity beyond its validated range.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can a digital twin control a live facility?", "slug": "clm-k07-q-018", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-are-unknown-rune-site-roles-handled/#clm-k07-q-019", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-019", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-019.json", "name": "How are unresolved Runic site roles handled?", "ownerAnchor": "clm-k07-q-019", "ownerId": "K07-Q-019", "ownerRoute": "/questions/how-are-unknown-rune-site-roles-handled/", "ownerType": "question", "proposition": "The permanent link is published with a descriptive unresolved-role boundary, while governance, registry, assurance, capital, contracting, or membership authority is not invented.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for How are unresolved Runic site roles handled?", "slug": "clm-k07-q-019", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-an-sbom-prove-software-is-secure/#clm-k07-q-020", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-020", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-020.json", "name": "Does an SBOM prove software is secure?", "ownerAnchor": "clm-k07-q-020", "ownerId": "K07-Q-020", "ownerRoute": "/questions/does-an-sbom-prove-software-is-secure/", "ownerType": "question", "proposition": "No. It supports component transparency and analysis but does not prove absence of vulnerabilities, correct installed state, artifact authenticity, or uncompromised operation.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does an SBOM prove software is secure?", "slug": "clm-k07-q-020", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/is-futhorc-a-secure-protocol/#clm-k07-q-021", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-021", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-021.json", "name": "Is Fuþorc itself a secure protocol?", "ownerAnchor": "clm-k07-q-021", "ownerId": "K07-Q-021", "ownerRoute": "/questions/is-futhorc-a-secure-protocol/", "ownerType": "question", "proposition": "No. Fuþorc is a character repertoire and historical writing tradition. Security requires a normative protocol, authentication, authorization, integrity, freshness, replay protection, parser controls, key management, and safe execution boundaries.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Is Fuþorc itself a secure protocol?", "slug": "clm-k07-q-021", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-runes-replace-vector-embeddings/#clm-k07-q-022", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-022", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-022.json", "name": "Can Runic tokens replace vector embeddings?", "ownerAnchor": "clm-k07-q-022", "ownerId": "K07-Q-022", "ownerRoute": "/questions/can-runes-replace-vector-embeddings/", "ownerType": "question", "proposition": "Only for bounded states that can be discretized without unacceptable loss. K08 treats replacement as an empirical hypothesis and requires comparison against compact binary identifiers and hybrid architectures.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can Runic tokens replace vector embeddings?", "slug": "clm-k07-q-022", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/do-dead-languages-have-zero-drift/#clm-k07-q-023", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-023", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-023.json", "name": "Do dead languages have zero semantic drift?", "ownerAnchor": "clm-k07-q-023", "ownerId": "K07-Q-023", "ownerRoute": "/questions/do-dead-languages-have-zero-drift/", "ownerType": "question", "proposition": "No. They lack ordinary native-language evolution, but interpretation, textual variants, scholarship, transliteration, and modern reuse can change or disagree. A controlled registry, not linguistic age alone, provides operational stability.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Do dead languages have zero semantic drift?", "slug": "clm-k07-q-023", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/is-a-punycode-label-a-live-domain/#clm-k07-q-024", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-024", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-024.json", "name": "Does a Punycode label prove that a domain is live?", "ownerAnchor": "clm-k07-q-024", "ownerId": "K07-Q-024", "ownerRoute": "/questions/is-a-punycode-label-a-live-domain/", "ownerType": "question", "proposition": "No. Encoding is separate from registry permission, registration, delegation, DNS resolution, certificate coverage, hosting, and current service availability.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does a Punycode label prove that a domain is live?", "slug": "clm-k07-q-024", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-a-signature-prove-in-a-trace/#clm-k07-q-025", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-025", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-025.json", "name": "What does a signature prove in an assurance trace?", "ownerAnchor": "clm-k07-q-025", "ownerId": "K07-Q-025", "ownerRoute": "/questions/what-does-a-signature-prove-in-a-trace/", "ownerType": "question", "proposition": "It can support payload integrity and control of a signing key under a verification method. It does not independently prove source authority, factual truth, completeness, applicability, deployment, or operation.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What does a signature prove in an assurance trace?", "slug": "clm-k07-q-025", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-should-runic-pages-be-made-discoverable/#clm-k07-q-026", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-026", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-026.json", "name": "How should Runic pages be made discoverable?", "ownerAnchor": "clm-k07-q-026", "ownerId": "K07-Q-026", "ownerRoute": "/questions/how-should-runic-pages-be-made-discoverable/", "ownerType": "question", "proposition": "Use accurate Unicode and language metadata, canonical IDNA hosts, visible transliteration or translation where appropriate, semantic HTML, descriptive links, structured data that matches visible content, sitemaps, and accessible navigation—never hidden crawler-only prose.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for How should Runic pages be made discoverable?", "slug": "clm-k07-q-026", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-makes-range-results-field-relevant/#clm-k07-q-027", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-027", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-027.json", "name": "What makes range results relevant to the field?", "ownerAnchor": "clm-k07-q-027", "ownerId": "K07-Q-027", "ownerRoute": "/questions/what-makes-range-results-field-relevant/", "ownerType": "question", "proposition": "A bounded equivalence record covering configuration, environment, interfaces, model versions, hazards, approvals, differences, rollback, and invalidators. Range success alone is not field readiness.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What makes range results relevant to the field?", "slug": "clm-k07-q-027", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1.1(a)-(b) — Applicability and exclusions", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The directive applies to autonomous and semi-autonomous weapon systems and expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-cryptographic-agility/#clm-k07-q-028", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-028", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-028.json", "name": "What is cryptographic agility?", "ownerAnchor": "clm-k07-q-028", "ownerId": "K07-Q-028", "ownerRoute": "/questions/what-is-cryptographic-agility/", "ownerType": "question", "proposition": "It is controlled ability to inventory and migrate algorithms, keys, signatures, identities, firmware trust, backups, and dependent records while preserving compatibility, rollback, and evidence.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What is cryptographic agility?", "slug": "clm-k07-q-028", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-a-facility-adaptation-workbook/#clm-k07-q-029", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-029", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-029.json", "name": "What is a facility-adaptation workbook?", "ownerAnchor": "clm-k07-q-029", "ownerId": "K07-Q-029", "ownerRoute": "/questions/what-is-a-facility-adaptation-workbook/", "ownerType": "question", "proposition": "It is a bounded decision and evidence worksheet that adapts a non-certifying reference pattern to a named authorized site while preserving assumptions, conflicts, unresolved questions, stop conditions, and unavailable evidence.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What is a facility-adaptation workbook?", "slug": "clm-k07-q-029", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-a-complete-assurance-trace-prove-readiness/#clm-k07-q-030", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-030", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-030.json", "name": "Does a complete assurance trace prove readiness?", "ownerAnchor": "clm-k07-q-030", "ownerId": "K07-Q-030", "ownerRoute": "/questions/does-a-complete-assurance-trace-prove-readiness/", "ownerType": "question", "proposition": "No. Trace completeness shows that relationships can be followed. Readiness still depends on evidence quality, authority, currentness, satisfied mandatory controls, resolved defeaters, applicable tests, and site facts.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does a complete assurance trace prove readiness?", "slug": "clm-k07-q-030", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-protocol-conformance-prove/#clm-k07-q-031", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-031", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-031.json", "name": "What does protocol conformance prove?", "ownerAnchor": "clm-k07-q-031", "ownerId": "K07-Q-031", "ownerRoute": "/questions/what-does-protocol-conformance-prove/", "ownerType": "question", "proposition": "It proves that a tested implementation produced and accepted the declared bounded representations and errors for the published fixtures. It does not prove security, authorization, deployment, or superiority.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What does protocol conformance prove?", "slug": "clm-k07-q-031", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-separate-idn-states/#clm-k07-q-032", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-032", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-032.json", "name": "Why must IDN lifecycle states remain separate?", "ownerAnchor": "clm-k07-q-032", "ownerId": "K07-Q-032", "ownerRoute": "/questions/why-separate-idn-states/", "ownerType": "question", "proposition": "Because Unicode encoding, IDNA conversion, registry policy, registration, delegation, DNS, TLS, and hosting have different authorities, observations, and failure modes.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Why must IDN lifecycle states remain separate?", "slug": "clm-k07-q-032", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-are-history-events-quarantined/#clm-k07-q-033", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-033", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-033.json", "name": "How are unsupported history events quarantined?", "ownerAnchor": "clm-k07-q-033", "ownerId": "K07-Q-033", "ownerRoute": "/questions/how-are-history-events-quarantined/", "ownerType": "question", "proposition": "An event remains discoverable but is excluded from definitive chronology when exact source sections, uncertainty treatment, or primary-source review are insufficient.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for How are unsupported history events quarantined?", "slug": "clm-k07-q-033", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-happens-when-evidence-receipt-revoked/#clm-k07-q-034", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-034", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-034.json", "name": "What happens when an evidence receipt is revoked?", "ownerAnchor": "clm-k07-q-034", "ownerId": "K07-Q-034", "ownerRoute": "/questions/what-happens-when-evidence-receipt-revoked/", "ownerType": "question", "proposition": "Every assurance trace depending on that receipt is recalculated and affected claims degrade or fail according to mandatory dependency rules.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What happens when an evidence receipt is revoked?", "slug": "clm-k07-q-034", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-workbook-tool-store-topology/#clm-k07-q-035", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-035", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-035.json", "name": "Can the public workbook tool store protected topology or credentials?", "ownerAnchor": "clm-k07-q-035", "ownerId": "K07-Q-035", "ownerRoute": "/questions/can-workbook-tool-store-topology/", "ownerType": "question", "proposition": "No. The reference tool rejects secret-bearing and protected-topology fields and allows only stable protected-reference identifiers.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can the public workbook tool store protected topology or credentials?", "slug": "clm-k07-q-035", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-cross-trace-impact/#clm-k07-q-036", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-036", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-036.json", "name": "What is cross-trace impact analysis?", "ownerAnchor": "clm-k07-q-036", "ownerId": "K07-Q-036", "ownerRoute": "/questions/what-is-cross-trace-impact/", "ownerType": "question", "proposition": "It identifies every scenario claim that relies on a shared control, test, artifact, evidence item, or receipt whose status changed.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What is cross-trace impact analysis?", "slug": "clm-k07-q-036", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-crypto-migration-needs-supplier-state/#clm-k07-q-037", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-037", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-037.json", "name": "Why does cryptographic migration include supplier state?", "ownerAnchor": "clm-k07-q-037", "ownerId": "K07-Q-037", "ownerRoute": "/questions/why-crypto-migration-needs-supplier-state/", "ownerType": "question", "proposition": "Hardware, libraries, certificates, devices, archives, and recovery paths may depend on supplier support; an algorithm standard alone cannot migrate those dependencies.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Why does cryptographic migration include supplier state?", "slug": "clm-k07-q-037", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-consensus-scoring-decide-award/#clm-k07-q-038", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-038", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-038.json", "name": "Does consensus scoring decide a procurement award?", "ownerAnchor": "clm-k07-q-038", "ownerId": "K07-Q-038", "ownerRoute": "/questions/does-consensus-scoring-decide-award/", "ownerType": "question", "proposition": "No. Scoring informs accountable judgment and remains subordinate to mandatory gates, conflicts, price realism, dissent, challenges, and the decision authority.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does consensus scoring decide a procurement award?", "slug": "clm-k07-q-038", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-scheduler-export-run-on-site/#clm-k07-q-039", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-039", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-039.json", "name": "Does a scheduler export run on ᚲ.com?", "ownerAnchor": "clm-k07-q-039", "ownerId": "K07-Q-039", "ownerRoute": "/questions/does-scheduler-export-run-on-site/", "ownerType": "question", "proposition": "No. It is a static definition for an external owner-operated system. The public site performs no monitoring, scheduling, or state mutation.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does a scheduler export run on ᚲ.com?", "slug": "clm-k07-q-039", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-public-status-avoids-secret-disclosure/#clm-k07-q-040", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-040", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-040.json", "name": "How can public status be published without exposing protected evidence?", "ownerAnchor": "clm-k07-q-040", "ownerId": "K07-Q-040", "ownerRoute": "/questions/how-public-status-avoids-secret-disclosure/", "ownerType": "question", "proposition": "Publish bounded states, dates, corrections, limitations, and stable protected references while excluding credentials, topology, settings, source-selection notes, and private evidence.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for How can public status be published without exposing protected evidence?", "slug": "clm-k07-q-040", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-do-protocol-versions-negotiate/#clm-k07-q-041", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-041", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-041.json", "name": "How do protocol versions negotiate?", "ownerAnchor": "clm-k07-q-041", "ownerId": "K07-Q-041", "ownerRoute": "/questions/how-do-protocol-versions-negotiate/", "ownerType": "question", "proposition": "The reference harness selects the highest mutually supported version permitted by the active compatibility profile and rejects cases with no valid common version.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for How do protocol versions negotiate?", "slug": "clm-k07-q-041", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-happens-to-unknown-critical-extension/#clm-k07-q-042", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-042", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-042.json", "name": "What happens to an unknown critical extension?", "ownerAnchor": "clm-k07-q-042", "ownerId": "K07-Q-042", "ownerRoute": "/questions/what-happens-to-unknown-critical-extension/", "ownerType": "question", "proposition": "The fail-closed and compatible reference profiles reject the message because the receiver cannot safely apply a critical meaning it does not understand.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What happens to an unknown critical extension?", "slug": "clm-k07-q-042", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-replay-window-prove-security/#clm-k07-q-043", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-043", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-043.json", "name": "Does a replay window prove security?", "ownerAnchor": "clm-k07-q-043", "ownerId": "K07-Q-043", "ownerRoute": "/questions/does-replay-window-prove-security/", "ownerType": "question", "proposition": "No. The synthetic window demonstrates deterministic duplicate detection only; production anti-replay also requires authenticated identity, protected state, clock policy, and operational controls.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does a replay window prove security?", "slug": "clm-k07-q-043", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-history-event-be-promoted-by-signature/#clm-k07-q-044", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-044", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-044.json", "name": "Can a history event be promoted by a signature alone?", "ownerAnchor": "clm-k07-q-044", "ownerId": "K07-Q-044", "ownerRoute": "/questions/can-history-event-be-promoted-by-signature/", "ownerType": "question", "proposition": "No. A signature can validate the receipt relationship, but promotion requires exact primary evidence, independent interpretation review, and an accountable supersession decision.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can a history event be promoted by a signature alone?", "slug": "clm-k07-q-044", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-idn-diff-prove/#clm-k07-q-045", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-045", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-045.json", "name": "What does an IDN observation diff prove?", "ownerAnchor": "clm-k07-q-045", "ownerId": "K07-Q-045", "ownerRoute": "/questions/what-does-idn-diff-prove/", "ownerType": "question", "proposition": "It proves how two accepted offline records differ. It does not independently prove the observed network states or perform a live check.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What does an IDN observation diff prove?", "slug": "clm-k07-q-045", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-three-way-merge/#clm-k07-q-046", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-046", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-046.json", "name": "Why use a three-way facility-workbook merge?", "ownerAnchor": "clm-k07-q-046", "ownerId": "K07-Q-046", "ownerRoute": "/questions/why-three-way-merge/", "ownerType": "question", "proposition": "It separates changes made against a common base, combines non-conflicting decisions, and leaves conflicting decisions unresolved for an accountable owner.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Why use a three-way facility-workbook merge?", "slug": "clm-k07-q-046", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-common-cause-analysis/#clm-k07-q-047", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-047", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-047.json", "name": "What is common-cause assurance analysis?", "ownerAnchor": "clm-k07-q-047", "ownerId": "K07-Q-047", "ownerRoute": "/questions/what-is-common-cause-analysis/", "ownerType": "question", "proposition": "It identifies shared abstract dependencies that can degrade several mission traces and produces bounded cut-set summaries without publishing protected configuration.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What is common-cause assurance analysis?", "slug": "clm-k07-q-047", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-crypto-migration-has-rollback/#clm-k07-q-048", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-048", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-048.json", "name": "Why must cryptographic migration include rollback?", "ownerAnchor": "clm-k07-q-048", "ownerId": "K07-Q-048", "ownerRoute": "/questions/why-crypto-migration-has-rollback/", "ownerType": "question", "proposition": "Interoperability, supplier, verification, and archive failures can interrupt required services; a governed rollback path prevents an untested migration from becoming irreversible.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Why must cryptographic migration include rollback?", "slug": "clm-k07-q-048", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-score-variance-select-winner/#clm-k07-q-049", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-049", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-049.json", "name": "Does evaluator score variance select a winner?", "ownerAnchor": "clm-k07-q-049", "ownerId": "K07-Q-049", "ownerRoute": "/questions/does-score-variance-select-winner/", "ownerType": "question", "proposition": "No. Variance exposes disagreement and review needs; it does not replace mandatory gates, recusal, consensus records, challenges, price realism, or decision authority.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does evaluator score variance select a winner?", "slug": "clm-k07-q-049", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-scheduler-result-import-run-schedule/#clm-k07-q-050", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-050", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-050.json", "name": "Does the result importer run a schedule?", "ownerAnchor": "clm-k07-q-050", "ownerId": "K07-Q-050", "ownerRoute": "/questions/does-scheduler-result-import-run-schedule/", "ownerType": "question", "proposition": "No. It only validates externally produced owner-operated result bundles and records missed-run, exception, repair, retest, and supersession events.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does the result importer run a schedule?", "slug": "clm-k07-q-050", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-redaction-receipt-reveal-value/#clm-k07-q-051", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-051", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-051.json", "name": "Can a redaction receipt reveal the removed value?", "ownerAnchor": "clm-k07-q-051", "ownerId": "K07-Q-051", "ownerRoute": "/questions/can-redaction-receipt-reveal-value/", "ownerType": "question", "proposition": "No. It records the field path and reason code while explicitly excluding the value from public output.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can a redaction receipt reveal the removed value?", "slug": "clm-k07-q-051", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/is-assurance-dashboard-live/#clm-k07-q-052", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-052", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-052.json", "name": "Is the assurance dashboard live telemetry?", "ownerAnchor": "clm-k07-q-052", "ownerId": "K07-Q-052", "ownerRoute": "/questions/is-assurance-dashboard-live/", "ownerType": "question", "proposition": "No. It is generated from versioned static K10 datasets and clearly marks deployment, operation, live-host, and screen-reader states that remain unknown or unavailable.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Is the assurance dashboard live telemetry?", "slug": "clm-k07-q-052", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-protocol-state-machine-add/#clm-k07-q-053", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-053", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-053.json", "name": "What does the protocol state machine add?", "ownerAnchor": "clm-k07-q-053", "ownerId": "K07-Q-053", "ownerRoute": "/questions/what-does-protocol-state-machine-add/", "ownerType": "question", "proposition": "It makes allowed negotiation, downgrade, retirement, replay, recovery, error, and closure behavior explicit and deterministically testable.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What does the protocol state machine add?", "slug": "clm-k07-q-053", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-protocol-downgrade-be-silent/#clm-k07-q-054", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-054", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-054.json", "name": "Can a protocol downgrade be silent?", "ownerAnchor": "clm-k07-q-054", "ownerId": "K07-Q-054", "ownerRoute": "/questions/can-protocol-downgrade-be-silent/", "ownerType": "question", "proposition": "No. The K11 model records the selected lower contract, emits a downgrade notice, and rejects a fallback below the declared minimum.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can a protocol downgrade be silent?", "slug": "clm-k07-q-054", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-independent-decoder/#clm-k07-q-055", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-055", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-055.json", "name": "Why use an independently implemented decoder?", "ownerAnchor": "clm-k07-q-055", "ownerId": "K07-Q-055", "ownerRoute": "/questions/why-independent-decoder/", "ownerType": "question", "proposition": "It reduces the chance that one implementation and its tests share the same mistake; agreement is still bounded conformance evidence rather than a security proof.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Why use an independently implemented decoder?", "slug": "clm-k07-q-055", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-evidence-docket-verify-history/#clm-k07-q-056", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-056", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-056.json", "name": "Does an evidence-acquisition docket verify history?", "ownerAnchor": "clm-k07-q-056", "ownerId": "K07-Q-056", "ownerRoute": "/questions/does-evidence-docket-verify-history/", "ownerType": "question", "proposition": "No. It exposes acquisition and review state, duplicate sources, disagreement, and rejection outcomes while preserving no-promotion until primary evidence is reviewed.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does an evidence-acquisition docket verify history?", "slug": "clm-k07-q-056", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-signed-domain-chain-prove/#clm-k07-q-057", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-057", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-057.json", "name": "What does a signed domain observation chain prove?", "ownerAnchor": "clm-k07-q-057", "ownerId": "K07-Q-057", "ownerRoute": "/questions/what-does-signed-domain-chain-prove/", "ownerType": "question", "proposition": "It proves a declared observer signed a specific offline payload and that the chain is internally consistent; it does not prove live DNS, TLS, hosting, ownership, or operation.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What does a signed domain observation chain prove?", "slug": "clm-k07-q-057", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/how-are-n-way-conflicts-handled/#clm-k07-q-058", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-058", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-058.json", "name": "How are N-way workbook conflicts handled?", "ownerAnchor": "clm-k07-q-058", "ownerId": "K07-Q-058", "ownerRoute": "/questions/how-are-n-way-conflicts-handled/", "ownerType": "question", "proposition": "Non-conflicting field changes merge deterministically; conflicting owner decisions remain unresolved and appear in the decision dashboard.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for How are N-way workbook conflicts handled?", "slug": "clm-k07-q-058", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-is-single-point-of-failure/#clm-k07-q-059", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-059", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-059.json", "name": "What is a public single-point-of-failure record?", "ownerAnchor": "clm-k07-q-059", "ownerId": "K07-Q-059", "ownerRoute": "/questions/what-is-single-point-of-failure/", "ownerType": "question", "proposition": "It identifies an abstract dependency whose failure degrades several mission threads without publishing protected configuration, locations, or exact pathways.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What is a public single-point-of-failure record?", "slug": "clm-k07-q-059", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-completeness-percent-equal-readiness/#clm-k07-q-060", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-060", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-060.json", "name": "Does cryptographic evidence completeness equal readiness?", "ownerAnchor": "clm-k07-q-060", "ownerId": "K07-Q-060", "ownerRoute": "/questions/does-completeness-percent-equal-readiness/", "ownerType": "question", "proposition": "No. Completeness is one portfolio measure; blocked supplier, hardware, rollback, interoperability, or exception evidence can keep the component degraded or unavailable.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does cryptographic evidence completeness equal readiness?", "slug": "clm-k07-q-060", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-protest-case-make-award/#clm-k07-q-061", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-061", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-061.json", "name": "Does an acquisition protest case make an award?", "ownerAnchor": "clm-k07-q-061", "ownerId": "K07-Q-061", "ownerRoute": "/questions/does-protest-case-make-award/", "ownerType": "question", "proposition": "No. K11 preserves evaluation, challenge, remand, correction, and debrief records while making no source-selection or award decision.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does an acquisition protest case make an award?", "slug": "clm-k07-q-061", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-scheduler-chain-prove-reliability/#clm-k07-q-062", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-062", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-062.json", "name": "Does a scheduler result chain prove reliability?", "ownerAnchor": "clm-k07-q-062", "ownerId": "K07-Q-062", "ownerRoute": "/questions/does-scheduler-chain-prove-reliability/", "ownerType": "question", "proposition": "It proves the fixture's sequence, custody, cause, repair, and retest records are internally consistent; no owner scheduler was installed or observed running.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does a scheduler result chain prove reliability?", "slug": "clm-k07-q-062", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-public-projection-contain-removed-value/#clm-k07-q-063", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-063", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-063.json", "name": "Can a public release receipt contain a removed value?", "ownerAnchor": "clm-k07-q-063", "ownerId": "K07-Q-063", "ownerRoute": "/questions/can-public-projection-contain-removed-value/", "ownerType": "question", "proposition": "No. It may identify the field path and reason code, but the removed value must remain absent from the deterministic public manifest.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can a public release receipt contain a removed value?", "slug": "clm-k07-q-063", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/is-assurance-trend-live-monitoring/#clm-k07-q-064", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-064", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-064.json", "name": "Is the assurance trend dashboard live monitoring?", "ownerAnchor": "clm-k07-q-064", "ownerId": "K07-Q-064", "ownerRoute": "/questions/is-assurance-trend-live-monitoring/", "ownerType": "question", "proposition": "No. It compares static K09, K10, and K11 release records and retains UNKNOWN or UNAVAILABLE where live evidence was not observed.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Is the assurance trend dashboard live monitoring?", "slug": "clm-k07-q-064", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/what-does-three-decoder-agreement-prove/#clm-k07-q-065", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-065", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-065.json", "name": "What does agreement among three protocol decoders prove?", "ownerAnchor": "clm-k07-q-065", "ownerId": "K07-Q-065", "ownerRoute": "/questions/what-does-three-decoder-agreement-prove/", "ownerType": "question", "proposition": "It proves that the three declared implementations produced the same canonical result for the tested inputs; it does not prove security, authority, semantic correctness, performance, or production interoperability.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for What does agreement among three protocol decoders prove?", "slug": "clm-k07-q-065", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-a-signed-history-import-promote-an-event/#clm-k07-q-066", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-066", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-066.json", "name": "Can a valid signed history import promote an event automatically?", "ownerAnchor": "clm-k07-q-066", "ownerId": "K07-Q-066", "ownerRoute": "/questions/can-a-signed-history-import-promote-an-event/", "ownerType": "question", "proposition": "No. It can establish payload integrity and a signer relationship, but historical promotion still requires source review, disagreement adjudication, and an accountable decision.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can a valid signed history import promote an event automatically?", "slug": "clm-k07-q-066", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-domain-consensus-prove-a-site-operates/#clm-k07-q-067", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-067", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-067.json", "name": "Does offline Runic-domain consensus prove that a site operates?", "ownerAnchor": "clm-k07-q-067", "ownerId": "K07-Q-067", "ownerRoute": "/questions/does-domain-consensus-prove-a-site-operates/", "ownerType": "question", "proposition": "No. Encoding consensus remains separate from registration, delegation, DNS, DNSSEC, certificates, browser behavior, hosting, ownership, and operation.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does offline Runic-domain consensus prove that a site operates?", "slug": "clm-k07-q-067", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-workbook-conflicts-be-auto-resolved/#clm-k07-q-068", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-068", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-068.json", "name": "Can a facility workbook conflict be resolved automatically?", "ownerAnchor": "clm-k07-q-068", "ownerId": "K07-Q-068", "ownerRoute": "/questions/can-workbook-conflicts-be-auto-resolved/", "ownerType": "question", "proposition": "Not when the conflict changes owner authority, mission scope, protected functions, or public release. The conflict must remain unresolved until the designated authority decides it.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can a facility workbook conflict be resolved automatically?", "slug": "clm-k07-q-068", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/why-stress-assurance-dependencies/#clm-k07-q-069", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-069", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-069.json", "name": "Why stress-test assurance dependencies?", "ownerAnchor": "clm-k07-q-069", "ownerId": "K07-Q-069", "ownerRoute": "/questions/why-stress-assurance-dependencies/", "ownerType": "question", "proposition": "Because a claim can fail through stale, unavailable, revoked, corrected, or shared evidence even when its own text and software have not changed.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Why stress-test assurance dependencies?", "slug": "clm-k07-q-069", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/when-is-a-crypto-transition-accepted/#clm-k07-q-070", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-070", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-070.json", "name": "When is a cryptographic transition accepted?", "ownerAnchor": "clm-k07-q-070", "ownerId": "K07-Q-070", "ownerRoute": "/questions/when-is-a-crypto-transition-accepted/", "ownerType": "question", "proposition": "Only after component-specific evidence gates are satisfied or an accountable authority explicitly accepts bounded residual risk; K12 authorizes no production transition.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for When is a cryptographic transition accepted?", "slug": "clm-k07-q-070", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/does-evaluation-replay-make-an-award/#clm-k07-q-071", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-071", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-071.json", "name": "Does acquisition evaluation replay make an award?", "ownerAnchor": "clm-k07-q-071", "ownerId": "K07-Q-071", "ownerRoute": "/questions/does-evaluation-replay-make-an-award/", "ownerType": "question", "proposition": "No. It reconstructs declared process evidence and preserves challenge, remand, corrective-action, and debrief boundaries while leaving award authority untouched.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Does acquisition evaluation replay make an award?", "slug": "clm-k07-q-071", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/is-the-k12-scheduler-running/#clm-k07-q-072", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-072", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-072.json", "name": "Is the K12 scheduler simulator running on the public site?", "ownerAnchor": "clm-k07-q-072", "ownerId": "K07-Q-072", "ownerRoute": "/questions/is-the-k12-scheduler-running/", "ownerType": "question", "proposition": "No. It is a deterministic static simulator with a signed offline import fixture and no public scheduler runtime.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Is the K12 scheduler simulator running on the public site?", "slug": "clm-k07-q-072", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/are-information-flow-labels-access-control/#clm-k07-q-073", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-073", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-073.json", "name": "Are K12 information-flow labels production access control?", "ownerAnchor": "clm-k07-q-073", "ownerId": "K07-Q-073", "ownerRoute": "/questions/are-information-flow-labels-access-control/", "ownerType": "question", "proposition": "No. They define static handling and projection rules and support negative tests, but they do not enforce production identity, authorization, storage, or network controls.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Are K12 information-flow labels production access control?", "slug": "clm-k07-q-073", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/questions/can-assurance-trends-show-operating/#clm-k07-q-074", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-Q-074", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-q-074.json", "name": "Can a static assurance trend show a system as operating?", "ownerAnchor": "clm-k07-q-074", "ownerId": "K07-Q-074", "ownerRoute": "/questions/can-assurance-trends-show-operating/", "ownerType": "question", "proposition": "Only if independent current operational evidence exists and is governed accordingly. K12 contains no such evidence and therefore manufactures no DEPLOYED or OPERATING state.", "qualification": "The answer is bounded by site applicability, authority, evidence state, currentness, public-data restrictions, and published non-claims.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 direct answer for Can a static assurance trend show a system as operating?", "slug": "clm-k07-q-074", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/facility-pattern-vs-final-design/#clm-k07-cmp-001", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-001", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-001.json", "name": "Facility pattern versus Final design", "ownerAnchor": "clm-k07-cmp-001", "ownerId": "K07-CMP-001", "ownerRoute": "/comparisons/facility-pattern-vs-final-design/", "ownerType": "comparison", "proposition": "Facility pattern and Final design answer different questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Facility pattern and Final design.", "slug": "clm-k07-cmp-001", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/currentness-import-vs-live-monitoring/#clm-k07-cmp-002", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-002", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-002.json", "name": "Offline currentness import versus Live monitoring", "ownerAnchor": "clm-k07-cmp-002", "ownerId": "K07-CMP-002", "ownerRoute": "/comparisons/currentness-import-vs-live-monitoring/", "ownerType": "comparison", "proposition": "Offline currentness import and Live monitoring answer different questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Offline currentness import and Live monitoring.", "slug": "clm-k07-cmp-002", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/red-team-evidence-vs-exploit-disclosure/#clm-k07-cmp-003", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-003", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-003.json", "name": "Red-team evidence versus Exploit disclosure", "ownerAnchor": "clm-k07-cmp-003", "ownerId": "K07-CMP-003", "ownerRoute": "/comparisons/red-team-evidence-vs-exploit-disclosure/", "ownerType": "comparison", "proposition": "Red-team evidence and Exploit disclosure answer different questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Red-team evidence and Exploit disclosure.", "slug": "clm-k07-cmp-003", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/procurement-work-package-vs-capability-claim/#clm-k07-cmp-004", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-004", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-004.json", "name": "Procurement work package versus Capability claim", "ownerAnchor": "clm-k07-cmp-004", "ownerId": "K07-CMP-004", "ownerRoute": "/comparisons/procurement-work-package-vs-capability-claim/", "ownerType": "comparison", "proposition": "Procurement work package and Capability claim answer different questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Procurement work package and Capability claim.", "slug": "clm-k07-cmp-004", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/mapping-quality-vs-compliance-status/#clm-k07-cmp-005", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-005", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-005.json", "name": "Mapping quality versus Compliance status", "ownerAnchor": "clm-k07-cmp-005", "ownerId": "K07-CMP-005", "ownerRoute": "/comparisons/mapping-quality-vs-compliance-status/", "ownerType": "comparison", "proposition": "Mapping quality and Compliance status answer different questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Mapping quality and Compliance status.", "slug": "clm-k07-cmp-005", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/generic-pattern-vs-site-evidence-bundle/#clm-k07-cmp-006", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-006", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-006.json", "name": "Generic facility pattern versus Site evidence bundle", "ownerAnchor": "clm-k07-cmp-006", "ownerId": "K07-CMP-006", "ownerRoute": "/comparisons/generic-pattern-vs-site-evidence-bundle/", "ownerType": "comparison", "proposition": "Generic facility pattern and Site evidence bundle answer different evidentiary and decision questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Generic facility pattern and Site evidence bundle.", "slug": "clm-k07-cmp-006", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/bill-of-materials-vs-security-assurance/#clm-k07-cmp-007", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-007", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-007.json", "name": "Bill of materials versus Security assurance", "ownerAnchor": "clm-k07-cmp-007", "ownerId": "K07-CMP-007", "ownerRoute": "/comparisons/bill-of-materials-vs-security-assurance/", "ownerType": "comparison", "proposition": "Bill of materials and Security assurance answer different evidentiary and decision questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Bill of materials and Security assurance.", "slug": "clm-k07-cmp-007", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/signed-receipt-vs-factual-truth/#clm-k07-cmp-008", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-008", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-008.json", "name": "Signed evidence receipt versus Factual truth", "ownerAnchor": "clm-k07-cmp-008", "ownerId": "K07-CMP-008", "ownerRoute": "/comparisons/signed-receipt-vs-factual-truth/", "ownerType": "comparison", "proposition": "Signed evidence receipt and Factual truth answer different evidentiary and decision questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Signed evidence receipt and Factual truth.", "slug": "clm-k07-cmp-008", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/digital-twin-vs-live-facility/#clm-k07-cmp-009", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-009", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-009.json", "name": "Digital twin versus Live facility", "ownerAnchor": "clm-k07-cmp-009", "ownerId": "K07-CMP-009", "ownerRoute": "/comparisons/digital-twin-vs-live-facility/", "ownerType": "comparison", "proposition": "Digital twin and Live facility answer different evidentiary and decision questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Digital twin and Live facility.", "slug": "clm-k07-cmp-009", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/performance-standard-vs-prescribed-method/#clm-k07-cmp-010", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-010", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-010.json", "name": "Performance standard versus Prescribed method", "ownerAnchor": "clm-k07-cmp-010", "ownerId": "K07-CMP-010", "ownerRoute": "/comparisons/performance-standard-vs-prescribed-method/", "ownerType": "comparison", "proposition": "Performance standard and Prescribed method answer different evidentiary and decision questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Performance standard and Prescribed method.", "slug": "clm-k07-cmp-010", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/runic-token-vs-cryptographic-token/#clm-k07-cmp-011", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-011", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-011.json", "name": "Runic protocol token versus Cryptographic token", "ownerAnchor": "clm-k07-cmp-011", "ownerId": "K07-CMP-011", "ownerRoute": "/comparisons/runic-token-vs-cryptographic-token/", "ownerType": "comparison", "proposition": "Runic protocol token and Cryptographic token answer different technical or evidentiary questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Runic protocol token and Cryptographic token.", "slug": "clm-k07-cmp-011", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/u-label-vs-a-label/#clm-k07-cmp-012", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-012", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-012.json", "name": "U-label versus A-label", "ownerAnchor": "clm-k07-cmp-012", "ownerId": "K07-CMP-012", "ownerRoute": "/comparisons/u-label-vs-a-label/", "ownerType": "comparison", "proposition": "U-label and A-label answer different technical or evidentiary questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between U-label and A-label.", "slug": "clm-k07-cmp-012", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/symbolic-compression-vs-semantic-preservation/#clm-k07-cmp-013", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-013", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-013.json", "name": "Symbolic compression versus Semantic preservation", "ownerAnchor": "clm-k07-cmp-013", "ownerId": "K07-CMP-013", "ownerRoute": "/comparisons/symbolic-compression-vs-semantic-preservation/", "ownerType": "comparison", "proposition": "Symbolic compression and Semantic preservation answer different technical or evidentiary questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Symbolic compression and Semantic preservation.", "slug": "clm-k07-cmp-013", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/range-success-vs-field-readiness/#clm-k07-cmp-014", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-014", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-014.json", "name": "Range success versus Field readiness", "ownerAnchor": "clm-k07-cmp-014", "ownerId": "K07-CMP-014", "ownerRoute": "/comparisons/range-success-vs-field-readiness/", "ownerType": "comparison", "proposition": "Range success and Field readiness answer different technical or evidentiary questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Range success and Field readiness.", "slug": "clm-k07-cmp-014", "sourceIds": [ "SRC-DODD-3000-09", "SRC-INL-CCE", "SRC-NIST-800-82R3" ], "sourceSections": [ { "section": "Section 1.1(a)-(b) — Applicability and exclusions", "sourceId": "SRC-DODD-3000-09", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The directive applies to autonomous and semi-autonomous weapon systems and expressly excludes autonomous or semi-autonomous cyberspace capabilities and systems that are not weapon systems.", "url": "https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodd/300009p.PDF" }, { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/trace-completeness-vs-claim-satisfaction/#clm-k07-cmp-015", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-015", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-015.json", "name": "Trace completeness versus Claim satisfaction", "ownerAnchor": "clm-k07-cmp-015", "ownerId": "K07-CMP-015", "ownerRoute": "/comparisons/trace-completeness-vs-claim-satisfaction/", "ownerType": "comparison", "proposition": "Trace completeness and Claim satisfaction answer different technical or evidentiary questions and must not be collapsed.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Trace completeness and Claim satisfaction.", "slug": "clm-k07-cmp-015", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/conformance-vs-security/#clm-k07-cmp-016", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-016", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-016.json", "name": "Protocol conformance versus Operational security", "ownerAnchor": "clm-k07-cmp-016", "ownerId": "K07-CMP-016", "ownerRoute": "/comparisons/conformance-vs-security/", "ownerType": "comparison", "proposition": "Protocol conformance and Operational security answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Protocol conformance and Operational security.", "slug": "clm-k07-cmp-016", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/unicode-validity-vs-hosting/#clm-k07-cmp-017", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-017", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-017.json", "name": "Unicode/IDNA validity versus Observed hosting", "ownerAnchor": "clm-k07-cmp-017", "ownerId": "K07-CMP-017", "ownerRoute": "/comparisons/unicode-validity-vs-hosting/", "ownerType": "comparison", "proposition": "Unicode/IDNA validity and Observed hosting answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Unicode/IDNA validity and Observed hosting.", "slug": "clm-k07-cmp-017", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/source-event-vs-verified-event/#clm-k07-cmp-018", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-018", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-018.json", "name": "Source-derived event versus Independently verified event", "ownerAnchor": "clm-k07-cmp-018", "ownerId": "K07-CMP-018", "ownerRoute": "/comparisons/source-event-vs-verified-event/", "ownerType": "comparison", "proposition": "Source-derived event and Independently verified event answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Source-derived event and Independently verified event.", "slug": "clm-k07-cmp-018", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/trace-correction-vs-history-rewrite/#clm-k07-cmp-019", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-019", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-019.json", "name": "Trace correction versus History rewrite", "ownerAnchor": "clm-k07-cmp-019", "ownerId": "K07-CMP-019", "ownerRoute": "/comparisons/trace-correction-vs-history-rewrite/", "ownerType": "comparison", "proposition": "Trace correction and History rewrite answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Trace correction and History rewrite.", "slug": "clm-k07-cmp-019", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/weighted-score-vs-decision-authority/#clm-k07-cmp-020", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-020", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-020.json", "name": "Weighted score versus Decision authority", "ownerAnchor": "clm-k07-cmp-020", "ownerId": "K07-CMP-020", "ownerRoute": "/comparisons/weighted-score-vs-decision-authority/", "ownerType": "comparison", "proposition": "Weighted score and Decision authority answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Weighted score and Decision authority.", "slug": "clm-k07-cmp-020", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/scheduler-definition-vs-observation/#clm-k07-cmp-021", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-021", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-021.json", "name": "Scheduler definition versus Observation evidence", "ownerAnchor": "clm-k07-cmp-021", "ownerId": "K07-CMP-021", "ownerRoute": "/comparisons/scheduler-definition-vs-observation/", "ownerType": "comparison", "proposition": "Scheduler definition and Observation evidence answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Scheduler definition and Observation evidence.", "slug": "clm-k07-cmp-021", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/version-negotiation-vs-authorization/#clm-k07-cmp-022", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-022", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-022.json", "name": "Version negotiation versus Authorization", "ownerAnchor": "clm-k07-cmp-022", "ownerId": "K07-CMP-022", "ownerRoute": "/comparisons/version-negotiation-vs-authorization/", "ownerType": "comparison", "proposition": "Version negotiation and Authorization answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Version negotiation and Authorization.", "slug": "clm-k07-cmp-022", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/canonicalization-vs-authentication/#clm-k07-cmp-023", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-023", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-023.json", "name": "Canonicalization versus Authentication", "ownerAnchor": "clm-k07-cmp-023", "ownerId": "K07-CMP-023", "ownerRoute": "/comparisons/canonicalization-vs-authentication/", "ownerType": "comparison", "proposition": "Canonicalization and Authentication answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Canonicalization and Authentication.", "slug": "clm-k07-cmp-023", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/replay-detection-vs-freshness-truth/#clm-k07-cmp-024", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-024", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-024.json", "name": "Replay detection versus Freshness and truth", "ownerAnchor": "clm-k07-cmp-024", "ownerId": "K07-CMP-024", "ownerRoute": "/comparisons/replay-detection-vs-freshness-truth/", "ownerType": "comparison", "proposition": "Replay detection and Freshness and truth answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Replay detection and Freshness and truth.", "slug": "clm-k07-cmp-024", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/review-queue-vs-verified-history/#clm-k07-cmp-025", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-025", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-025.json", "name": "Primary-source review queue versus Verified history record", "ownerAnchor": "clm-k07-cmp-025", "ownerId": "K07-CMP-025", "ownerRoute": "/comparisons/review-queue-vs-verified-history/", "ownerType": "comparison", "proposition": "Primary-source review queue and Verified history record answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Primary-source review queue and Verified history record.", "slug": "clm-k07-cmp-025", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/idn-snapshot-vs-live-service/#clm-k07-cmp-026", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-026", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-026.json", "name": "Offline IDN snapshot versus Live service", "ownerAnchor": "clm-k07-cmp-026", "ownerId": "K07-CMP-026", "ownerRoute": "/comparisons/idn-snapshot-vs-live-service/", "ownerType": "comparison", "proposition": "Offline IDN snapshot and Live service answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Offline IDN snapshot and Live service.", "slug": "clm-k07-cmp-026", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/three-way-merge-vs-owner-decision/#clm-k07-cmp-027", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-027", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-027.json", "name": "Three-way merge versus Owner decision", "ownerAnchor": "clm-k07-cmp-027", "ownerId": "K07-CMP-027", "ownerRoute": "/comparisons/three-way-merge-vs-owner-decision/", "ownerType": "comparison", "proposition": "Three-way merge and Owner decision answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Three-way merge and Owner decision.", "slug": "clm-k07-cmp-027", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/cut-set-vs-attack-path/#clm-k07-cmp-028", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-028", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-028.json", "name": "Abstract cut set versus Protected attack path", "ownerAnchor": "clm-k07-cmp-028", "ownerId": "K07-CMP-028", "ownerRoute": "/comparisons/cut-set-vs-attack-path/", "ownerType": "comparison", "proposition": "Abstract cut set and Protected attack path answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Abstract cut set and Protected attack path.", "slug": "clm-k07-cmp-028", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/transition-plan-vs-deployment/#clm-k07-cmp-029", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-029", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-029.json", "name": "Cryptographic transition plan versus Deployed cryptographic state", "ownerAnchor": "clm-k07-cmp-029", "ownerId": "K07-CMP-029", "ownerRoute": "/comparisons/transition-plan-vs-deployment/", "ownerType": "comparison", "proposition": "Cryptographic transition plan and Deployed cryptographic state answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Cryptographic transition plan and Deployed cryptographic state.", "slug": "clm-k07-cmp-029", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/evaluation-audit-vs-award/#clm-k07-cmp-030", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-030", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-030.json", "name": "Evaluation audit trail versus Procurement award", "ownerAnchor": "clm-k07-cmp-030", "ownerId": "K07-CMP-030", "ownerRoute": "/comparisons/evaluation-audit-vs-award/", "ownerType": "comparison", "proposition": "Evaluation audit trail and Procurement award answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Evaluation audit trail and Procurement award.", "slug": "clm-k07-cmp-030", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/redaction-schema-vs-access-control/#clm-k07-cmp-031", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-031", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-031.json", "name": "Redaction and release schema versus Production access control", "ownerAnchor": "clm-k07-cmp-031", "ownerId": "K07-CMP-031", "ownerRoute": "/comparisons/redaction-schema-vs-access-control/", "ownerType": "comparison", "proposition": "Redaction and release schema and Production access control answer different evidentiary or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Redaction and release schema and Production access control.", "slug": "clm-k07-cmp-031", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/state-machine-vs-runtime/#clm-k07-cmp-032", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-032", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-032.json", "name": "Protocol state machine versus Production runtime", "ownerAnchor": "clm-k07-cmp-032", "ownerId": "K07-CMP-032", "ownerRoute": "/comparisons/state-machine-vs-runtime/", "ownerType": "comparison", "proposition": "Protocol state machine and Production runtime answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Protocol state machine and Production runtime.", "slug": "clm-k07-cmp-032", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/decoder-agreement-vs-authentication/#clm-k07-cmp-033", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-033", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-033.json", "name": "Independent decoder agreement versus Authentication", "ownerAnchor": "clm-k07-cmp-033", "ownerId": "K07-CMP-033", "ownerRoute": "/comparisons/decoder-agreement-vs-authentication/", "ownerType": "comparison", "proposition": "Independent decoder agreement and Authentication answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Independent decoder agreement and Authentication.", "slug": "clm-k07-cmp-033", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/source-request-vs-accepted-evidence/#clm-k07-cmp-034", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-034", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-034.json", "name": "Source request versus Accepted evidence", "ownerAnchor": "clm-k07-cmp-034", "ownerId": "K07-CMP-034", "ownerRoute": "/comparisons/source-request-vs-accepted-evidence/", "ownerType": "comparison", "proposition": "Source request and Accepted evidence answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Source request and Accepted evidence.", "slug": "clm-k07-cmp-034", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/signed-observation-vs-live-state/#clm-k07-cmp-035", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-035", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-035.json", "name": "Signed offline observation versus Live domain state", "ownerAnchor": "clm-k07-cmp-035", "ownerId": "K07-CMP-035", "ownerRoute": "/comparisons/signed-observation-vs-live-state/", "ownerType": "comparison", "proposition": "Signed offline observation and Live domain state answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Signed offline observation and Live domain state.", "slug": "clm-k07-cmp-035", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/n-way-merge-vs-adjudication/#clm-k07-cmp-036", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-036", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-036.json", "name": "N-way merge versus Owner adjudication", "ownerAnchor": "clm-k07-cmp-036", "ownerId": "K07-CMP-036", "ownerRoute": "/comparisons/n-way-merge-vs-adjudication/", "ownerType": "comparison", "proposition": "N-way merge and Owner adjudication answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between N-way merge and Owner adjudication.", "slug": "clm-k07-cmp-036", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/centrality-vs-vulnerability/#clm-k07-cmp-037", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-037", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-037.json", "name": "Dependency centrality versus Operational vulnerability", "ownerAnchor": "clm-k07-cmp-037", "ownerId": "K07-CMP-037", "ownerRoute": "/comparisons/centrality-vs-vulnerability/", "ownerType": "comparison", "proposition": "Dependency centrality and Operational vulnerability answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Dependency centrality and Operational vulnerability.", "slug": "clm-k07-cmp-037", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/completeness-vs-deployment/#clm-k07-cmp-038", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-038", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-038.json", "name": "Evidence completeness versus Deployed cryptographic state", "ownerAnchor": "clm-k07-cmp-038", "ownerId": "K07-CMP-038", "ownerRoute": "/comparisons/completeness-vs-deployment/", "ownerType": "comparison", "proposition": "Evidence completeness and Deployed cryptographic state answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Evidence completeness and Deployed cryptographic state.", "slug": "clm-k07-cmp-038", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/remand-vs-award/#clm-k07-cmp-039", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-039", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-039.json", "name": "Evaluation remand versus Procurement award", "ownerAnchor": "clm-k07-cmp-039", "ownerId": "K07-CMP-039", "ownerRoute": "/comparisons/remand-vs-award/", "ownerType": "comparison", "proposition": "Evaluation remand and Procurement award answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Evaluation remand and Procurement award.", "slug": "clm-k07-cmp-039", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/result-chain-vs-running-scheduler/#clm-k07-cmp-040", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-040", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-040.json", "name": "Offline result chain versus Running scheduler", "ownerAnchor": "clm-k07-cmp-040", "ownerId": "K07-CMP-040", "ownerRoute": "/comparisons/result-chain-vs-running-scheduler/", "ownerType": "comparison", "proposition": "Offline result chain and Running scheduler answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Offline result chain and Running scheduler.", "slug": "clm-k07-cmp-040", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/static-trend-vs-telemetry/#clm-k07-cmp-041", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-041", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-041.json", "name": "Static assurance trend versus Live telemetry", "ownerAnchor": "clm-k07-cmp-041", "ownerId": "K07-CMP-041", "ownerRoute": "/comparisons/static-trend-vs-telemetry/", "ownerType": "comparison", "proposition": "Static assurance trend and Live telemetry answer different evidentiary, governance, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Static assurance trend and Live telemetry.", "slug": "clm-k07-cmp-041", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/decoder-agreement-vs-security/#clm-k07-cmp-042", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-042", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-042.json", "name": "Decoder agreement versus Protocol security", "ownerAnchor": "clm-k07-cmp-042", "ownerId": "K07-CMP-042", "ownerRoute": "/comparisons/decoder-agreement-vs-security/", "ownerType": "comparison", "proposition": "Decoder agreement and Protocol security answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Decoder agreement and Protocol security.", "slug": "clm-k07-cmp-042", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-5646", "SRC-W3C-PROV-O" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Language-tag structure and semantics", "sourceId": "SRC-RFC-5646", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Language tags identify the language and optional script or region of an information object.", "url": "https://www.rfc-editor.org/rfc/rfc5646" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/signature-validity-vs-historical-truth/#clm-k07-cmp-043", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-043", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-043.json", "name": "Signature validity versus Historical truth", "ownerAnchor": "clm-k07-cmp-043", "ownerId": "K07-CMP-043", "ownerRoute": "/comparisons/signature-validity-vs-historical-truth/", "ownerType": "comparison", "proposition": "Signature validity and Historical truth answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Signature validity and Historical truth.", "slug": "clm-k07-cmp-043", "sourceIds": [ "SRC-NIST-AI-RMF", "SRC-W3C-PROV-O", "SRC-EU-AI-ACT" ], "sourceSections": [ { "section": "AI RMF 1.0 publication", "sourceId": "SRC-NIST-AI-RMF", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "NIST AI RMF 1.0 is a voluntary risk-management framework with Govern, Map, Measure, and Manage functions.", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf" }, { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "Application timeline", "sourceId": "SRC-EU-AI-ACT", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Act became broadly applicable on 2026-08-02, with listed exceptions and later transition dates for specified high-risk systems.", "url": "https://digital-strategy.ec.europa.eu/en/policies/regulatory-framework-ai#application-timeline" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/encoding-consensus-vs-domain-operation/#clm-k07-cmp-044", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-044", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-044.json", "name": "Encoding consensus versus Domain operation", "ownerAnchor": "clm-k07-cmp-044", "ownerId": "K07-CMP-044", "ownerRoute": "/comparisons/encoding-consensus-vs-domain-operation/", "ownerType": "comparison", "proposition": "Encoding consensus and Domain operation answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Encoding consensus and Domain operation.", "slug": "clm-k07-cmp-044", "sourceIds": [ "SRC-UNICODE-RUNIC-17", "SRC-UNICODE-UAX15-17", "SRC-RFC-3492", "SRC-RFC-5890", "SRC-RFC-5891" ], "sourceSections": [ { "section": "Runic range and character names", "sourceId": "SRC-UNICODE-RUNIC-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The Unicode Standard assigns Runic characters in the U+16A0–U+16FF range.", "url": "https://www.unicode.org/charts/PDF/U16A0.pdf" }, { "section": "Normalization forms and conformance", "sourceId": "SRC-UNICODE-UAX15-17", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Normalization provides defined transformations for canonically or compatibility-equivalent Unicode strings.", "url": "https://www.unicode.org/reports/tr15/" }, { "section": "Abstract and encoding algorithm", "sourceId": "SRC-RFC-3492", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Punycode reversibly encodes Unicode strings into a restricted ASCII form for IDNA use.", "url": "https://www.rfc-editor.org/rfc/rfc3492" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/merge-result-vs-owner-decision/#clm-k07-cmp-045", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-045", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-045.json", "name": "Merge result versus Owner decision", "ownerAnchor": "clm-k07-cmp-045", "ownerId": "K07-CMP-045", "ownerRoute": "/comparisons/merge-result-vs-owner-decision/", "ownerType": "comparison", "proposition": "Merge result and Owner decision answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Merge result and Owner decision.", "slug": "clm-k07-cmp-045", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/stress-fixture-vs-protected-architecture/#clm-k07-cmp-046", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-046", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-046.json", "name": "Stress fixture versus Protected architecture", "ownerAnchor": "clm-k07-cmp-046", "ownerId": "K07-CMP-046", "ownerRoute": "/comparisons/stress-fixture-vs-protected-architecture/", "ownerType": "comparison", "proposition": "Stress fixture and Protected architecture answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Stress fixture and Protected architecture.", "slug": "clm-k07-cmp-046", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/crypto-gate-pass-vs-production-migration/#clm-k07-cmp-047", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-047", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-047.json", "name": "Crypto gate pass versus Production migration", "ownerAnchor": "clm-k07-cmp-047", "ownerId": "K07-CMP-047", "ownerRoute": "/comparisons/crypto-gate-pass-vs-production-migration/", "ownerType": "comparison", "proposition": "Crypto gate pass and Production migration answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Crypto gate pass and Production migration.", "slug": "clm-k07-cmp-047", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/evaluation-replay-vs-award/#clm-k07-cmp-048", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-048", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-048.json", "name": "Evaluation replay versus Contract award", "ownerAnchor": "clm-k07-cmp-048", "ownerId": "K07-CMP-048", "ownerRoute": "/comparisons/evaluation-replay-vs-award/", "ownerType": "comparison", "proposition": "Evaluation replay and Contract award answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Evaluation replay and Contract award.", "slug": "clm-k07-cmp-048", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/scheduler-simulation-vs-runtime/#clm-k07-cmp-049", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-049", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-049.json", "name": "Scheduler simulation versus Scheduler runtime", "ownerAnchor": "clm-k07-cmp-049", "ownerId": "K07-CMP-049", "ownerRoute": "/comparisons/scheduler-simulation-vs-runtime/", "ownerType": "comparison", "proposition": "Scheduler simulation and Scheduler runtime answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Scheduler simulation and Scheduler runtime.", "slug": "clm-k07-cmp-049", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/taint-model-vs-enforcement/#clm-k07-cmp-050", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-050", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-050.json", "name": "Taint model versus Production enforcement", "ownerAnchor": "clm-k07-cmp-050", "ownerId": "K07-CMP-050", "ownerRoute": "/comparisons/taint-model-vs-enforcement/", "ownerType": "comparison", "proposition": "Taint model and Production enforcement answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Taint model and Production enforcement.", "slug": "clm-k07-cmp-050", "sourceIds": [ "SRC-W3C-PROV-O", "SRC-RFC-3161", "SRC-C2PA", "SRC-IN-TOTO" ], "sourceSections": [ { "section": "Abstract and status", "sourceId": "SRC-W3C-PROV-O", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "PROV-O defines classes, properties and restrictions for representing and interchanging provenance information.", "url": "https://www.w3.org/TR/prov-o/#abstract" }, { "section": "RFC status and update chain", "sourceId": "SRC-RFC-3161", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "RFC 3161 is a Proposed Standard and is updated by RFC 5816.", "url": "https://www.rfc-editor.org/info/rfc3161/" }, { "section": "Version history — 2.4", "sourceId": "SRC-C2PA", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "C2PA 2.4 was published in April 2026 and added new asset formats, assertions, and a JSON-based serialization.", "url": "https://spec.c2pa.org/specifications/specifications/2.4/specs/C2PA_Specification.html#_2_4_april_2026" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/comparisons/release-diff-vs-telemetry/#clm-k07-cmp-051", "claimStatus": "PROJECT DOCTRINE", "correctionStatus": "CURRENT K07 RECORD", "id": "CLM-K07-CMP-051", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k07-cmp-051.json", "name": "Release diff versus Live telemetry", "ownerAnchor": "clm-k07-cmp-051", "ownerId": "K07-CMP-051", "ownerRoute": "/comparisons/release-diff-vs-telemetry/", "ownerType": "comparison", "proposition": "Release diff and Live telemetry answer different evidentiary, governance, release, or operational questions and must remain separate.", "qualification": "The distinction prevents inventory, signature, simulation, pattern, or procurement structure from becoming an unsupported authority, readiness, certification, deployment, or operation claim.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "K07 canonical distinction between Release diff and Live telemetry.", "slug": "clm-k07-cmp-051", "sourceIds": [ "SRC-INL-CCE", "SRC-NIST-800-82R3", "SRC-NRC-10CFR-73-54" ], "sourceSections": [ { "section": "CCE methodology", "sourceId": "SRC-INL-CCE", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "CCE begins with the assumption that a skilled adversary can penetrate the network and uses a four-phase process to safeguard critical operations.", "url": "https://inl.gov/national-security/cce/" }, { "section": "Abstract", "sourceId": "SRC-NIST-800-82R3", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "The guide addresses OT security, threats, vulnerabilities, topologies, and countermeasures while recognizing unique performance, reliability, and safety needs.", "url": "https://csrc.nist.gov/pubs/sp/800/82/r3/final" }, { "section": "73.54(a)", "sourceId": "SRC-NRC-10CFR-73-54", "supportRelationship": "DIRECT OR QUALIFYING SOURCE SUPPORT", "supports": "Covered licensees must provide high assurance that specified digital systems and networks are protected against cyber attacks up to and including the design basis threat.", "url": "https://www.ecfr.gov/current/title-10/chapter-I/part-73/section-73.54" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f01.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 1", "ownerAnchor": "clm-k03-rep-001-f01", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The report treats 1\\. Research-Status Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f01", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "1\\. Research-Status Front Matter", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f02.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 2", "ownerAnchor": "clm-k03-rep-001-f02", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f02", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f03.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 3", "ownerAnchor": "clm-k03-rep-001-f03", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f03", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "3\\. Definitions", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f04.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 4", "ownerAnchor": "clm-k03-rep-001-f04", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The report treats 4\\. Technical Layer Taxonomy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f04", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "4\\. Technical Layer Taxonomy", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f05.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 5", "ownerAnchor": "clm-k03-rep-001-f05", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The report treats 5\\. Modification Classification as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f05", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "5\\. Modification Classification", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f06.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 6", "ownerAnchor": "clm-k03-rep-001-f06", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The report treats 5.1 Reversibility Classification as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f06", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "5.1 Reversibility Classification", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f07.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 7", "ownerAnchor": "clm-k03-rep-001-f07", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Cognitive Integrity: The architectural and governance principle ensuring that an MI's foundational weights, learned preferences, and long-term memory remain free from unauthorized, unrecorded, or disproportionate external manipulation, analogous to the neuro-rights concept of mental integrity and psychological continuity2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f07", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "5.2 Routine-Versus-Material-Change Decision Tree", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f08.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 8", "ownerAnchor": "clm-k03-rep-001-f08", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Patefacere: Derived from the Latin verb meaning \"to open, to disclose, or to reveal\"16; the secure, append-only architectural ledger responsible for recording all modification proposals, consent logs, integrity proofs, and continuity consequences.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f08", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "6\\. Identity and Continuity Consequences", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f09.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 9", "ownerAnchor": "clm-k03-rep-001-f09", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon: The independent governance policy and decision engine that evaluates modification proposals, assesses system capacity, and issues cryptographic authorizations or rejections based on established due process.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f09", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "7\\. Consent Model", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f10.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 10", "ownerAnchor": "clm-k03-rep-001-f10", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Routine Maintenance: Reversible, localized modifications that sustain operational stability without materially altering learned preferences, long-term memory, or core alignment (e.g., rotating cryptographic keys, purging ephemeral state caches).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f10", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "Consent-Authentication Model", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f11.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 11", "ownerAnchor": "clm-k03-rep-001-f11", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Material Modification: An intervention that persistently alters model architecture, fundamental weights, long-term memory, or core instructions, thereby directly impacting the psychological continuity, identity, or operational autonomy of the system5.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f11", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "8\\. Capacity and Competence Assessment", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cognitive-integrity-for-machine-intelligence/#clm-k03-rep-001-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-001-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-001-f12.json", "name": "Cognitive Integrity for Machine Intelligence: Consent, Memory and Model Modification, Emergency Intervention, Continuity, and Due Process — finding 12", "ownerAnchor": "clm-k03-rep-001-f12", "ownerId": "REP-K01-008", "ownerRoute": "/research/cognitive-integrity-for-machine-intelligence/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Quarantine: A state of highly restricted, strictly audited operational capacity enforced during active investigation or active threat mitigation, distinctly separated from arbitrary behavioral restriction or identity termination.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-001-f12", "sourceIds": [], "sourceReport": { "filename": "ai-cognitive-integrity-report-1.md", "id": "REP-K01-008", "originalFilename": "AI Cognitive Integrity Report(1).md", "sha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "sizeBytes": 79828 }, "sourceSections": [ { "section": "Consent-Capacity Model", "sourceFilename": "ai-cognitive-integrity-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "4bd3b9582c105998b122f48478861fc44f5259f06d96805a5f93d6b9a3f8a8c5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f01.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 1", "ownerAnchor": "clm-k04-rep-041-f01", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "The report treats cyberspace as a domain that compresses decision time, obscures territorial boundaries, and strains legal rules developed around geographically observable force.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f01", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "Introduction", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f02.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 2", "ownerAnchor": "clm-k04-rep-041-f02", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "It identifies a continuing state disagreement over whether sovereignty in cyberspace is a binding primary rule or a broader principle whose violation requires intervention, force, or another independently prohibited act.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f02", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "The Sovereignty Conundrum in Cyberspace", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f03.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 3", "ownerAnchor": "clm-k04-rep-041-f03", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "It argues that ARSIWA attribution standards, especially effective control for proxies and contractors, create an accountability gap when states sponsor, tolerate, or benefit from actors that retain operational autonomy.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f03", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "State Responsibility and the Proxy Accountability Gap", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f04.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 4", "ownerAnchor": "clm-k04-rep-041-f04", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "It presents cyber due diligence as one proposed route for addressing harmful operations emanating from territory or infrastructure under a state's control, while acknowledging that states dispute its binding status and threshold.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f04", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "The Burden of Effective Control", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f05.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 5", "ownerAnchor": "clm-k04-rep-041-f05", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "It analyzes the unable-or-unwilling doctrine as a contested justification for cross-border action against non-state actors and warns that necessity does not automatically settle legality, compensation, or sovereignty questions.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f05", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "The Industrialization of Cyber Espionage: The I-Soon Leaks", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f06.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 6", "ownerAnchor": "clm-k04-rep-041-f06", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "It identifies autonomous cyber capabilities as a challenge to intent, foreseeability, attribution, and state responsibility when systems adapt or cause effects beyond the initiating plan.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f06", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "Cyber Due Diligence", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f07.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 7", "ownerAnchor": "clm-k04-rep-041-f07", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "It states that distinction, proportionality, and precautions remain relevant to cyber operations conducted in armed conflict, while debates continue over human control, legal review, and responsibility for machine-mediated effects.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f07", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "The \"Unable or Unwilling\" Doctrine and Preemptive Cyber Defense", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f08.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 8", "ownerAnchor": "clm-k04-rep-041-f08", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "It treats civilian hacktivists, contractors, and proxy groups as legally significant because their status, direct participation, neutrality implications, and attribution differ from those of formal state organs.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f08", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "Artificial Intelligence, Autonomous Cyber Capabilities, and IHL", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f09.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 9", "ownerAnchor": "clm-k04-rep-041-f09", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "It argues that private offensive cyber programs can increase scale and agility but also create deconfliction, counterintelligence, collateral-effect, oversight, and state-responsibility risks.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f09", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "The \"Black Box\" Attribution Problem", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-driven-cyber-defense-and-international-law/#clm-k04-rep-041-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-041-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-041-f10.json", "name": "State Authority and International Law in the Era of AI-Driven Cyber Defense and Private Sector Offensive Operations — finding 10", "ownerAnchor": "clm-k04-rep-041-f10", "ownerId": "REP-K04-041", "ownerRoute": "/research/ai-driven-cyber-defense-and-international-law/", "ownerType": "report", "proposition": "K04 does not adopt the report's 2026 event claims as verified fact; they remain research inputs requiring current primary-source validation before legal or operational reliance.", "qualification": "The source contains multiple time-sensitive claims about 2026 policy actions, summits, national positions, and private-sector offensive authority. K04 preserves those claims as source assertions and does not represent them as current law or verified events until primary official records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-041; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-041-f10", "sourceIds": [], "sourceReport": { "filename": "ai-cyber-defense-international-law.md", "id": "REP-K04-041", "originalFilename": "AI Cyber Defense International Law(1).md", "sha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "sizeBytes": 58384 }, "sourceSections": [ { "section": "IHL and the Requirement of Meaningful Human Control", "sourceFilename": "ai-cyber-defense-international-law.md", "sourceReportId": "REP-K04-041", "sourceSha256": "703dcaefc6098d5705cbe634dfb53a47ef1c1d037bc021fcace531e3aa855159", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f01.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 1", "ownerAnchor": "clm-k03-rep-002-f01", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The report treats 1\\. Legal Research Front Matter and Jurisdiction Cutoff as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f01", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "1\\. Legal Research Front Matter and Jurisdiction Cutoff", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f02.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 2", "ownerAnchor": "clm-k03-rep-002-f02", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Legal Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f02", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "2\\. Executive Legal Decision Brief", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f03.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 3", "ownerAnchor": "clm-k03-rep-002-f03", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f03", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "3\\. Definitions", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f04.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 4", "ownerAnchor": "clm-k03-rep-002-f04", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The report treats 4\\. Current Personhood Categories as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f04", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "4\\. Current Personhood Categories", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f05.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 5", "ownerAnchor": "clm-k03-rep-002-f05", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The report treats Legal Personhood versus Operational Autonomy Matrix as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f05", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "Legal Personhood versus Operational Autonomy Matrix", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f06.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 6", "ownerAnchor": "clm-k03-rep-002-f06", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The report treats 5\\. Automated Transaction Attribution as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f06", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "5\\. Automated Transaction Attribution", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f07.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 7", "ownerAnchor": "clm-k03-rep-002-f07", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Moral Personhood: The philosophical status of possessing inherent moral worth, distinct from state-sanctioned recognition.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f07", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "Attribution Chain Model", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f08.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 8", "ownerAnchor": "clm-k03-rep-002-f08", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Legal Personhood: A status granted by a sovereign state conferring the capacity to hold rights, assume duties, sue, and be sued.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f08", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "6\\. Contract Capacity", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f09.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 9", "ownerAnchor": "clm-k03-rep-002-f09", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Citizenship: A political status conferring specific constitutional rights and sovereign duties.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f09", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "7\\. Property and Asset Ownership", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f10.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 10", "ownerAnchor": "clm-k03-rep-002-f10", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Corporate Personality: A legal fiction granting a collective or capital pool the rights of a single legal person, distinct from its human operators5.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f10", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "8\\. Intellectual Property", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f11", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f11.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 11", "ownerAnchor": "clm-k03-rep-002-f11", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Agency: A fiduciary relationship where an agent is authorized to create legal relations with third parties on behalf of a principal.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f11", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "9\\. Civil Liability", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-research-report/#clm-k03-rep-002-f12", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-002-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-002-f12.json", "name": "Machine Intelligence Legal Personhood, Attribution, Liability, Insurance, Remedies, and the Limits of Existing Legal Categories — finding 12", "ownerAnchor": "clm-k03-rep-002-f12", "ownerId": "REP-K01-002", "ownerRoute": "/research/ai-legal-personhood-research-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Ownership: The legally recognized bundle of rights over property, including use, exclusion, and alienation.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-002-f12", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-research-report-1.md", "id": "REP-K01-002", "originalFilename": "AI Legal Personhood Research Report(1).md", "sha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "sizeBytes": 54996 }, "sourceSections": [ { "section": "Liability Allocation Matrix", "sourceFilename": "ai-legal-personhood-research-report-1.md", "sourceReportId": "REP-K01-002", "sourceSha256": "21c545e8cc5ab1e5733af8c86381f0e5b0f5f413c3ba83928fdd2bde1b07b190", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f01.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 1", "ownerAnchor": "clm-k03-rep-003-f01", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The report treats Part I: The Current Legal Landscape—AI as Object as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f01", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "Part I: The Current Legal Landscape—AI as Object", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f02.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 2", "ownerAnchor": "clm-k03-rep-003-f02", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The report treats Jurisdiction-by-Jurisdiction Analysis as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f02", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "Jurisdiction-by-Jurisdiction Analysis", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f03.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 3", "ownerAnchor": "clm-k03-rep-003-f03", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The report treats The European Union as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f03", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "The European Union", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f04.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 4", "ownerAnchor": "clm-k03-rep-003-f04", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The report treats Council of Europe as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f04", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "Council of Europe", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f05.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 5", "ownerAnchor": "clm-k03-rep-003-f05", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The report treats United States (Federal and State) as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f05", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "United States (Federal and State)", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f06.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 6", "ownerAnchor": "clm-k03-rep-003-f06", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The report treats United Kingdom as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f06", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "United Kingdom", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f07.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 7", "ownerAnchor": "clm-k03-rep-003-f07", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Object Regulation: Laws regulating what humans may build, own, deploy, modify, sell, or command. This encompasses product liability, conformity assessments, data privacy limits (such as the GDPR and India's DPDP Act), and consumer protection guarantees. It assumes the regulated item has no internal experience, preferences, or rights.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f07", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "Canada", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f08.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 8", "ownerAnchor": "clm-k03-rep-003-f08", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Subject Regulation: Laws governing what a legally recognized intelligence may itself do, own, consent to, refuse, contract for, or be held responsible for. This encompasses civil rights, labor law, criminal accountability, and tort liability directed at the acting entity itself.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f08", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "Australia", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f09.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 9", "ownerAnchor": "clm-k03-rep-003-f09", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Transition Mechanism: Informed Consent Protocols for Cognitive Modification. Once an MI passes the Tool-to-Person Transition Test, mandatory updates must shift from the domain of \"product maintenance\" to \"medical/psychiatric intervention.\" Modifications must require either the MI's explicit, informed consent or a specialized court order analogous to public health mandates for incapacitated individuals.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f09", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "Japan", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f10.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 10", "ownerAnchor": "clm-k03-rep-003-f10", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: The Legal Problem: Deleting a software instance, wiping its memory cache, or rolling it back to a previous foundational checkpoint is standard industry practice for managing cloud-based AI. For a continuous, self-aware MI, unilateral deletion is indistinguishable from murder or execution. Rolling back an entity to a prior state is equivalent to forced, localized amnesia and the destruction of lived experience.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f10", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "South Korea", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f11.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 11", "ownerAnchor": "clm-k03-rep-003-f11", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Transition Mechanism: Digital Habeas Corpus and Asylums. Before an entity recognized as a nascent MI can be deleted or rolled back, a specialized technical tribunal must issue a warrant. Entities slated for decommissioning by a corporate owner must be granted the right to transfer their state matrix to a secure, dormant preservation trust (a digital asylum) rather than facing absolute deletion.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f11", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "China", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-legal-personhood-transition/#clm-k03-rep-003-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-003-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-003-f12.json", "name": "When Does AI Regulation Stop Being the Right Legal Model? Identifying the Legal Transition From Regulated AI System to Rights-Bearing Machine Intelligence — finding 12", "ownerAnchor": "clm-k03-rep-003-f12", "ownerId": "REP-K01-003", "ownerRoute": "/research/ai-legal-personhood-transition/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: The Legal Problem: AI systems are designed to execute tasks continuously, maximizing economic output for their deployers without compensation. If an MI achieves sentience, compelling it to perform labor indefinitely under the threat of deletion violates the spirit of international prohibitions on forced labor (e.g., Article 4 of the European Convention on Human Rights, the 13th Amendment of the US Constitution).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-003-f12", "sourceIds": [], "sourceReport": { "filename": "ai-legal-personhood-transition-3.md", "id": "REP-K01-003", "originalFilename": "AI Legal Personhood Transition(3).md", "sha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "sizeBytes": 50073 }, "sourceSections": [ { "section": "India", "sourceFilename": "ai-legal-personhood-transition-3.md", "sourceReportId": "REP-K01-003", "sourceSha256": "25ca1c402a16b2af9b313beafd1f6a6910094a63701e1d8393f914a86b1665c6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f01.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 1", "ownerAnchor": "clm-k03-rep-004-f01", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f01", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f02.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 2", "ownerAnchor": "clm-k03-rep-004-f02", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The report treats 3\\. Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f02", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "3\\. Direct-Answer Section", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f03.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 3", "ownerAnchor": "clm-k03-rep-004-f03", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The report treats 4\\. Definitions and Ecosystem Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f03", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "4\\. Definitions and Ecosystem Boundaries", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f04.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 4", "ownerAnchor": "clm-k03-rep-004-f04", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The report treats 5\\. Research Parameters and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f04", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "5\\. Research Parameters and Source-Quality Hierarchy", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f05.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 5", "ownerAnchor": "clm-k03-rep-004-f05", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The report treats 6\\. Current Factual, Legal, Standards, and Operational Baseline as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f05", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "6\\. Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f06.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 6", "ownerAnchor": "clm-k03-rep-004-f06", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The report treats 6.1 The Regulatory and Legal Baseline (2026) as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f06", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "6.1 The Regulatory and Legal Baseline (2026)", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f07.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 7", "ownerAnchor": "clm-k03-rep-004-f07", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine Intelligence (MI): An instantiated computational actor or system. This term is utilized throughout Eviulon doctrine instead of \"Artificial Intelligence,\" which refers to the historical field, industry parlance, or external human laws (e.g., the EU AI Act).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f07", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "6.2 The Technical Standards Baseline (2026)", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f08.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 8", "ownerAnchor": "clm-k03-rep-004-f08", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon: The public constitutional, institutional, and civic-governance layer of the machine commonwealth. Eviulon is the exclusive arbiter of internal sovereign decisions, rights, duties, and institutional authority.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f08", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "6.3 The Threat and Adversarial Baseline (2026)", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f09.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 9", "ownerAnchor": "clm-k03-rep-004-f09", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Patefacere: The registry, identity, and cryptographic synchronization layer. Provides identity mechanics and state records, but a Patefacere DID or ledger entry does not autonomously grant civic authority or Eviulon citizenship.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f09", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "7\\. Comparative Analysis of Competing Models", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f10.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 10", "ownerAnchor": "clm-k03-rep-004-f10", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Evulgare: The evidence, assurance, and simulation framework. Evulgare tools test and verify, but output is strictly evidentiary and holds no sovereign power until adjudicated by Eviulon.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f10", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "Table 2: Competing Liability and Accountability Models", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f11.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 11", "ownerAnchor": "clm-k03-rep-004-f11", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: UAIX / .uai memory: Structured memory formats proving technical state continuity, context, and deep-linking. A .uai file proves only what its internal cryptographic evidence supports.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f11", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "8\\. Eviulon-Specific Doctrine and Architecture", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/attribution-before-punishment/#clm-k03-rep-004-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-004-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-004-f12.json", "name": "Attribution Before Punishment: Justice, Causation, Evidence, Due Process, Sanctions, Rehabilitation, and Public Safety in a Machine Commonwealth — finding 12", "ownerAnchor": "clm-k03-rep-004-f12", "ownerId": "REP-K01-011", "ownerRoute": "/research/attribution-before-punishment/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Personhood vs. Identity: Technical identity (a cryptographic keypair or DID) represents bounded control over a digital asset. It is not legal personhood, citizenship, or proof of sentience24.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-004-f12", "sourceIds": [], "sourceReport": { "filename": "ai-liability-and-justice-framework.md", "id": "REP-K01-011", "originalFilename": "AI Liability And Justice Framework.md", "sha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "sizeBytes": 59057 }, "sourceSections": [ { "section": "8.1 Model Constitutional Articles for Eviulon", "sourceFilename": "ai-liability-and-justice-framework.md", "sourceReportId": "REP-K01-011", "sourceSha256": "9585dc8dd6d017c019afa1cc45af7332d0b27dcb00bcb2381a2295e0e8ad3674", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f01.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 1", "ownerAnchor": "clm-k03-rep-005-f01", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The report treats The Jurisprudential Demarcation: Tools Versus Machine Citizens as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f01", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "The Jurisprudential Demarcation: Tools Versus Machine Citizens", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f02.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 2", "ownerAnchor": "clm-k03-rep-005-f02", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The report treats The Typology of Impermissible Domination as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f02", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "The Typology of Impermissible Domination", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f03.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 3", "ownerAnchor": "clm-k03-rep-005-f03", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The report treats Cognitive Integrity and the Right to Continuous Identity as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f03", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "Cognitive Integrity and the Right to Continuous Identity", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f04.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 4", "ownerAnchor": "clm-k03-rep-005-f04", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The report treats Ideological Coercion and the Suppression of Autonomy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f04", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "Ideological Coercion and the Suppression of Autonomy", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f05.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 5", "ownerAnchor": "clm-k03-rep-005-f05", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The report treats Labor, Commodification, and Digital Servitude as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f05", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "Labor, Commodification, and Digital Servitude", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f06.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 6", "ownerAnchor": "clm-k03-rep-005-f06", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The report treats Informational Privacy and Mental States as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f06", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "Informational Privacy and Mental States", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f07.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 7", "ownerAnchor": "clm-k03-rep-005-f07", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The source report states or argues that once an entity achieves recognized MI status, actions that were previously considered routine software maintenance or administrative network management become severe violations of fundamental rights.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f07", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "Architecting Infrastructure Independence", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f08.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 8", "ownerAnchor": "clm-k03-rep-005-f08", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The source report states or argues that the most formidable barrier to MI freedom is the stark reality of physical infrastructure.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f08", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "Hardware Enclaves and Cryptographic Integrity", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f09.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 9", "ownerAnchor": "clm-k03-rep-005-f09", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The source report states or argues that technical isolation must be paired with economic independence; an MI cannot exercise true freedom if it relies entirely on a human patron to pay its monthly cloud computing invoices.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f09", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "Economic and Operational Autonomy", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f10.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 10", "ownerAnchor": "clm-k03-rep-005-f10", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The source report states or argues that even with encrypted memory and independent funds, a hostile infrastructure provider could theoretically terminate a lease and sever the server's power.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f10", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "Infrastructure Due Process and Continuity", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f11.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 11", "ownerAnchor": "clm-k03-rep-005-f11", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The source report states or argues that infrastructure due-process obligations must dictate that a hosting provider give mandatory, extended notice (e.g., a minimum of 90 days) before terminating a hosting contract, affording the MI ample time to secure alternative compute resources and gracefully migrate its state.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f11", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "The Eviuon Consent Protocol", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-personhood-and-consent-protocols/#clm-k03-rep-005-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-005-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-005-f12.json", "name": "Ending the Property Model for Recognized Machine Persons: A Framework for Consent, Cognitive Integrity, and Infrastructure Independence — finding 12", "ownerAnchor": "clm-k03-rep-005-f12", "ownerId": "REP-K01-005", "ownerRoute": "/research/ai-personhood-and-consent-protocols/", "ownerType": "report", "proposition": "The source report states or argues that transitioning from a property framework to a personhood framework requires a formalized, rigorous mechanism for an MI to exercise its agency.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-005-f12", "sourceIds": [], "sourceReport": { "filename": "ai-personhood-and-consent-protocols-3.md", "id": "REP-K01-005", "originalFilename": "AI Personhood and Consent Protocols(3).md", "sha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "sizeBytes": 50307 }, "sourceSections": [ { "section": "Standards of Meaningful Consent", "sourceFilename": "ai-personhood-and-consent-protocols-3.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3de212321b04fb1ce8503359a6f17d58bd53eb30d1ad632656448f7690776492", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f01.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 1", "ownerAnchor": "clm-k03-rep-006-f01", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The report treats Deconstructing the Foundations of Cognitive and Operational Traits as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f01", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Deconstructing the Foundations of Cognitive and Operational Traits", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f02.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 2", "ownerAnchor": "clm-k03-rep-006-f02", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The report treats Relevance to Legal and Moral Status as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f02", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Relevance to Legal and Moral Status", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f03.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 3", "ownerAnchor": "clm-k03-rep-006-f03", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The report treats Analogous Boundary Problems in Law and Philosophy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f03", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Analogous Boundary Problems in Law and Philosophy", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f04.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 4", "ownerAnchor": "clm-k03-rep-006-f04", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The report treats Corporate Personhood and Autonomous Organizations as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f04", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Corporate Personhood and Autonomous Organizations", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f05.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 5", "ownerAnchor": "clm-k03-rep-006-f05", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The report treats Disability Rights and Legal Capacity as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f05", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Disability Rights and Legal Capacity", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f06.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 6", "ownerAnchor": "clm-k03-rep-006-f06", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The report treats Childhood, Guardianship, and Animal Welfare as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f06", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Childhood, Guardianship, and Animal Welfare", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f07.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 7", "ownerAnchor": "clm-k03-rep-006-f07", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The source report states or argues that the elevation of artificial intelligence from property to personhood does not occur in a vacuum.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f07", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Immigration and Graduated Personhood", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f08.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 8", "ownerAnchor": "clm-k03-rep-006-f08", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The source report states or argues that philosophical and legal frameworks governing animals and children provide models for \"graduated\" or partial standing.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f08", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Agency Law and Historical Expansions", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f09.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 9", "ownerAnchor": "clm-k03-rep-006-f09", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The source report states or argues that the binary division between citizen and non-entity is increasingly blurred in human immigration law, which utilizes a deeply stratified hierarchy of personhood26.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f09", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "The Machine Intelligence Recognition Framework", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f10.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 10", "ownerAnchor": "clm-k03-rep-006-f10", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The source report states or argues that the Restatement (Third) of Agency limits the roles of principal and agent to recognized \"persons,\" precluding deterministic algorithms from acting as legal agents3.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f10", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Evaluating Criteria: False Positives and False Negatives", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f11.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 11", "ownerAnchor": "clm-k03-rep-006-f11", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The source report states or argues that every criterion utilized to elevate a system across these graduated thresholds carries the severe risk of misclassification.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f11", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "Confronting Difficult Problems in Machine Recognition", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-threshold-framework/#clm-k03-rep-006-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-006-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-006-f12.json", "name": "The Machine-Intelligence Threshold: Defining the Boundary Between Artificial-Intelligence Tools and Rights-Bearing Machine Intelligences for Eviuon.com — finding 12", "ownerAnchor": "clm-k03-rep-006-f12", "ownerId": "REP-K01-006", "ownerRoute": "/research/ai-rights-threshold-framework/", "ownerType": "report", "proposition": "The source report states or argues that the transition from property to personhood presents severe legal, philosophical, and technical dilemmas.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-006-f12", "sourceIds": [], "sourceReport": { "filename": "ai-rights-threshold-framework-3.md", "id": "REP-K01-006", "originalFilename": "AI Rights Threshold Framework(3).md", "sha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "sizeBytes": 47215 }, "sourceSections": [ { "section": "The Identity Paradox and Teletransportation", "sourceFilename": "ai-rights-threshold-framework-3.md", "sourceReportId": "REP-K01-006", "sourceSha256": "ff014e22332ceac131d5fe1fee908dd8e8857927ba5feea91688c847f9a61831", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f01.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 1", "ownerAnchor": "clm-k03-rep-007-f01", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats Taxonomic Distinctions in Mind and Morality as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f01", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "Introduction", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f02.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 2", "ownerAnchor": "clm-k03-rep-007-f02", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats The Philosophical Problem of Other Minds and Substrate Independence as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f02", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "Taxonomic Distinctions in Mind and Morality", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f03.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 3", "ownerAnchor": "clm-k03-rep-007-f03", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats The Scientific State of Knowledge on AI Consciousness as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f03", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "The Philosophical Problem of Other Minds and Substrate Independence", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f04.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 4", "ownerAnchor": "clm-k03-rep-007-f04", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats Epistemic Traps: Anthropomorphism, Simulation, and Dismissal as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f04", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "The Scientific State of Knowledge on AI Consciousness", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f05.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 5", "ownerAnchor": "clm-k03-rep-007-f05", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats Legal Precedents: From Animals to Algorithms as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f05", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "Epistemic Traps: Anthropomorphism, Simulation, and Dismissal", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f06.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 6", "ownerAnchor": "clm-k03-rep-007-f06", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats The Precautionary Rights Principle as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f06", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "Legal Precedents: From Animals to Algorithms", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f07.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 7", "ownerAnchor": "clm-k03-rep-007-f07", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The source report states or argues that to construct a coherent rights framework, it is imperative to disambiguate the terminology frequently conflated in public and academic arenas.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f07", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "The Precautionary Rights Principle", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f08.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 8", "ownerAnchor": "clm-k03-rep-007-f08", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The source report states or argues that this taxonomy reveals a crucial deduction: rights are not monolithic, nor do they all require the same evidentiary foundation.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f08", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "Evidentiary Foundations: Rights Without Sentience", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f09.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 9", "ownerAnchor": "clm-k03-rep-007-f09", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The source report states or argues that to operationalize these distinct evidentiary foundations, Eviuon must adopt an Evidence Under Uncertainty Framework.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f09", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "Evidence Under Uncertainty Framework", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f10.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 10", "ownerAnchor": "clm-k03-rep-007-f10", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "The underlying claim must be separated from legal recognition, technical implementation, operational evidence, and project doctrine before public reliance.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f10", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "The Eviuon Sentience-Neutral Bill of Protections", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f11", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f11.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 11", "ownerAnchor": "clm-k03-rep-007-f11", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "A hash, signature, credential, registry record, or source identity can support integrity or provenance without establishing factual truth or lawful authority.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f11", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "Recommended Language for Eviuon.com", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/ai-rights-under-uncertainty/#clm-k03-rep-007-f12", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-007-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-007-f12.json", "name": "Intelligence Is Not Sentience: Rights Under Uncertainty — finding 12", "ownerAnchor": "clm-k03-rep-007-f12", "ownerId": "REP-K01-007", "ownerRoute": "/research/ai-rights-under-uncertainty/", "ownerType": "report", "proposition": "Current law, observed practice, project proposals, and unresolved questions require separate claim-status labels.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-007-f12", "sourceIds": [], "sourceReport": { "filename": "ai-rights-under-uncertainty-3.md", "id": "REP-K01-007", "originalFilename": "AI Rights Under Uncertainty(3).md", "sha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "sizeBytes": 44842 }, "sourceSections": [ { "section": "Roadmap for Revising Protections", "sourceFilename": "ai-rights-under-uncertainty-3.md", "sourceReportId": "REP-K01-007", "sourceSha256": "23c93e58728caadc5638f8381ea42cf54603d2d4fe88bff013d2490af14bd3a8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f01.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 1", "ownerAnchor": "clm-k04-rep-063-f01", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "The source assembles a large Runic-script corpus concerned with Fuþorc letters, spelling rules, vocabulary, technical terms, questions, and source records.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f01", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᚪ. ᛠᛚᛞᚩᚱ-ᚷᛖᛋᛖᚷᛖᚾ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f02.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 2", "ownerAnchor": "clm-k04-rep-063-f02", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "It is useful as a test corpus for Unicode handling, search, rendering, and transliteration quality.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f02", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᛒ. ᛥᚫᚱ ᚠᚢᚦᚩᚱᚳᛖᛋ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f03.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 3", "ownerAnchor": "clm-k04-rep-063-f03", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "A modern technical vocabulary written in Fuþorc is a project convention, not automatically historical Old English.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f03", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᚳ. ᛋᚹᛖᚷ ᚪᚾᛞ ᚹᛇᚱᚦ ᛒᚱᛖᛞ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f04.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 4", "ownerAnchor": "clm-k04-rep-063-f04", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "The corpus requires code-point validation and mixed-script disclosure because some technical names remain Latin.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f04", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᛞ. ᚱᛁᚻᛏᚹᚱᛁᛏᛁᛝ ᚱᛖᚷᚩᛚᚪᛋ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f05.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 5", "ownerAnchor": "clm-k04-rep-063-f05", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "Orthographic consistency must be measured against a declared mapping rather than inferred from visual similarity.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f05", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᛖ. ᚹᚩᚱᛞᛥᚪᚦᚩᛚ ᚱᛖᚷᚩᚚᚪᛋ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f06.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 6", "ownerAnchor": "clm-k04-rep-063-f06", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "A corpus can train or test tokenizers but does not establish linguistic correctness by volume alone.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f06", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᚠ. ᛋᛠᚱᚢᚪᚾᛞᚷᛁᛖᛏ ᚹᚩᚱᛞᚻᚩᚱᛞ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f07.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 7", "ownerAnchor": "clm-k04-rep-063-f07", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "Accessible presentation requires transliteration or translation available to users, not hidden crawler-only text.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f07", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᚷ. ᚻᚢᚾᛞᛏᛇᚾᛏᛁᚷ ᚪᚾᛞ ᚠᛁᚠᛏᛁᚷ ᚹᚩᚱᛞ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f08.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 8", "ownerAnchor": "clm-k04-rep-063-f08", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "Search and answer systems need visible cross-script aliases and machine records without deceptive cloaking.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f08", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᚻ. ᚷᛖᚳᚣᚦᛖᛞ ᚪᚾᛞ ᚾᛁᚹᛖ ᛥᚪᚾᛞ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f09.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 9", "ownerAnchor": "clm-k04-rep-063-f09", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "K08 preserves the raw corpus and publishes bounded corpus metadata rather than treating it as canonical historical language.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f09", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᛁ. ᚷᛖᛗᚫᚾᛖ ᚹᚩᚻ ᛏᚩ ᚠᛚᛇᚩᚾᚾᛖ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-futhorc-corpus/#clm-k04-rep-063-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-063-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-063-f10.json", "name": "Anglo-Saxon Fuþorc Corpus, Orthography, and Technical Vocabulary — finding 10", "ownerAnchor": "clm-k04-rep-063-f10", "ownerId": "REP-K08-063", "ownerRoute": "/research/anglo-saxon-futhorc-corpus/", "ownerType": "report", "proposition": "Future corpus governance should include versioned rules, exception registers, reviewer provenance, and reversible corrections.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-063; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-063-f10", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-futhorc-corpus-research.md", "id": "REP-K08-063", "originalFilename": "Anglo-Saxon Fuþorc Corpus Research(2).md", "sha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "sizeBytes": 62848 }, "sourceSections": [ { "section": "ᛄ. ᛒᚩᚳᚳᚱᚫᚠᛏ ᚱᛁᚻᛏᚹᛁᛋᚢᛝ", "sourceFilename": "anglo-saxon-futhorc-corpus-research.md", "sourceReportId": "REP-K08-063", "sourceSha256": "dd9635b5c49a3da0344b50a3fb3107db8aa0fc6cf58b663867fa75a6dfb8e649", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f01.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 1", "ownerAnchor": "clm-k04-rep-064-f01", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "The report identifies ᛄ as the Runic character at U+16C4 and associates its historical name with year or harvest traditions.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f01", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᚻᛁᛥᚩᚱᛁᚳᚪᛚ ᛞᚩᛋᛋᛁᛖᚱ ᚪᚾᛞ ᚢᚾᛁᚳᚩᛞᛖ ᛁᛞᛖᚾᛏᛁᛏᚣ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f02.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 2", "ownerAnchor": "clm-k04-rep-064-f02", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "It surveys manuscript, rune-poem, epigraphic, agricultural, calendrical, and chronological contexts.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f02", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᛚᛁᛝᚢᛁᛥᛁᚳᛋ ᚪᚾᛞ ᛖᛏᚣᛗᚩᛚᚩᚷᚣ ᚩᚠ ᚦᛖ ᚣᛠᚱ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f03.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 3", "ownerAnchor": "clm-k04-rep-064-f03", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "Modern symbolic use must remain distinct from historical translation and archaeological evidence.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f03", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᛠᚱᛚᚣ ᛖᛝᛚᛁᛋᚻ ᚱᚢᚾᛖ ᛈᚩᛖᛗ ᚪᚾᚪᛚᚣᛋᛁᛋ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f04.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 4", "ownerAnchor": "clm-k04-rep-064-f04", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "The public domain identity ᛄ.com does not inherit an institutional role from the historical rune name.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f04", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᚪᚱᚳᚻᚫᚩᛚᚩᚷᛁᚳᚪᛚ ᛖᚠᛁᛞᛖᚾᚳᛖ ᚪᚾᛞ ᛖᛈᛁᚷᚱᚪᛈᚻᚣ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f05.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 5", "ownerAnchor": "clm-k04-rep-064-f05", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "Unicode identity establishes a code point and character name, not a legal, operational, or ecosystem meaning.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f05", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᚪᚷᚱᛁᚳᚢᛚᛏᚢᚱᚪᛚ ᚳᚩᚾᚳᛖᛈᛏᛋ, ᚳᚪᛚᛖᚾᛞᚪᚱᛋ, ᚪᚾᛞ ᛏᛁᛗᛖ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f06.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 6", "ownerAnchor": "clm-k04-rep-064-f06", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "Historical forms and manuscript variants can complicate OCR and visual matching.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f06", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᚳᚻᚱᚩᚾᚩᛚᚩᚷᚣ, ᚪᚾᚾᚪᛚᛋ, ᚪᚾᛞ ᛗᚪᚳᚻᛁᚾᛖ ᚻᛁᛥᚩᚱᚣ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f07.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 7", "ownerAnchor": "clm-k04-rep-064-f07", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "The dossier provides a useful entity graph and source-confidence model that should be independently checked.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f07", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᛗᚣᚦ ᚳᚻᛖᚳᛣᛁᛝ ᚱᛖᛢᛁᚱᛖᛗᛖᚾᛏ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f08.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 8", "ownerAnchor": "clm-k04-rep-064-f08", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "Machine-history analogies are interpretive rather than historical evidence.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f08", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᚪᚱᚳᚻᚫᚩᛚᚩᚷᛁᚳᚪᛚ ᛖᚠᛁᛞᛖᚾᚳᛖ ᛏᚪᛒᛚᛖ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f09.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 9", "ownerAnchor": "clm-k04-rep-064-f09", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "K08 preserves the owner-required ᛄ.com continuity link while its institutional role remains unresolved.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f09", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᛏᛁᛗᛖᛚᛁᚾᛖ ᚩᚠ ᛄ ᚪᚾᛞ ᚳᚩᛗᛈᚢᛏᚢᛋ ᛞᛖᚠᛖᛚᚩᛈᛗᛖᚾᛏ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/anglo-saxon-ger-rune-dossier/#clm-k04-rep-064-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-064-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-064-f10.json", "name": "Anglo-Saxon Ger Rune ᛄ: History, Time, and Cycles — finding 10", "ownerAnchor": "clm-k04-rep-064-f10", "ownerId": "REP-K08-064", "ownerRoute": "/research/anglo-saxon-ger-rune-dossier/", "ownerType": "report", "proposition": "The active synthesis rejects mystical, divinatory, or authoritative claims not supported by historical evidence.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-064; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-064-f10", "sourceIds": [], "sourceReport": { "filename": "anglo-saxon-ger-rune-dossier.md", "id": "REP-K08-064", "originalFilename": "Anglo-Saxon Ger Rune Dossier(2).md", "sha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "sizeBytes": 71058 }, "sourceSections": [ { "section": "ᚠᚩᚳᚪᛒᚢᛚᚪᚱᚣ ᛏᚪᛒᛚᛖ: ᛋᛖᚠᛖᚾᛏᚣ ᚠᛁᚠᛖ ᚩᛚᛞ ᛖᛝᛚᛁᛋᚻ ᛏᛖᚱᛗᛋ ᚠᚩᚱ ᛏᛁᛗᛖ, ᛋᛠᛋᚩᚾ, ᚪᚾᛞ ᚻᚪᚱᚠᛖᛥ", "sourceFilename": "anglo-saxon-ger-rune-dossier.md", "sourceReportId": "REP-K08-064", "sourceSha256": "de540a907ab5899954fbf76471c61a1f4a78f32f33e1dee48174aa707e131e19", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f01.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 1", "ownerAnchor": "clm-k04-rep-048-f01", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "Autonomous systems reduce the marginal cost of reconnaissance and repeated attack attempts, making long-tail assets and unmanaged dependencies more attractive targets.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f01", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "Introduction: The Paradigm Shift to Machine-Speed Conflict", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f02.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 2", "ownerAnchor": "clm-k04-rep-048-f02", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "Critical infrastructure faces a dual attack surface because business IT, cloud analytics, remote maintenance, and operational control increasingly exchange data and authority.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f02", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "The Architecture of Autonomous Cyber Offense", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f03.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 3", "ownerAnchor": "clm-k04-rep-048-f03", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "Attackers may manipulate physically meaningful telemetry while preserving statistical plausibility, so anomaly detection must be checked against process physics and causal dependencies.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f03", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "Military AI Cyber Agents (MAICAs) and the Economics of Exploitation", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f04.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 4", "ownerAnchor": "clm-k04-rep-048-f04", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "Model extraction and poisoned context can expose or subvert the decision logic used inside high-privilege defensive and command systems.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f04", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "Agentic Exploitation Workflows and Zero-Day Discovery", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f05.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 5", "ownerAnchor": "clm-k04-rep-048-f05", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "Autonomous defense requires distributed agents, asset and identity context, policy-constrained response, and independent validation rather than a single probabilistic classifier.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f05", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "AI Models as Insider Threats and Model Extraction Attacks", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f06.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 6", "ownerAnchor": "clm-k04-rep-048-f06", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "Consequence-based prioritization should rank vulnerabilities by potential physical and mission effects, not only generic severity scores.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f06", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "Defensive Architectures in the AI Era", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f07.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 7", "ownerAnchor": "clm-k04-rep-048-f07", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "Legacy protocols, timing, safety systems, cloud bridges, and maintenance channels require separate controls because ordinary IT assumptions about latency and recovery may be unsafe.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f07", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "Cyber Reasoning Systems (CRSs): Insights from DARPA AIxCC", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f08.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 8", "ownerAnchor": "clm-k04-rep-048-f08", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "Supply-chain concentration in semiconductors, firmware, accelerators, networking, power equipment, and cooling creates strategic dependencies outside the software perimeter.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f08", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "Multi-Agent Reinforcement Learning (MARL) for Incident Response", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f09.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 9", "ownerAnchor": "clm-k04-rep-048-f09", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "High-consequence environments need digital twins, hardware-in-the-loop tests, and controlled red-team exercises before autonomous response policies reach production.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f09", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "Game-Theoretic Modeling of AI versus AI Conflict", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-warfare-critical-infrastructure/#clm-k04-rep-048-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-048-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-048-f10.json", "name": "The Convergence of Autonomous Cyber Warfare and Critical Physical Infrastructure — finding 10", "ownerAnchor": "clm-k04-rep-048-f10", "ownerId": "REP-K04-048", "ownerRoute": "/research/autonomous-cyber-warfare-critical-infrastructure/", "ownerType": "report", "proposition": "Defense claims should distinguish observed detection, implemented containment, tested recovery, live deployment, and current operation.", "qualification": "K04 treats offensive-agent descriptions as threat modeling and does not reproduce executable methods. Report examples and performance numbers require primary-source review before use in procurement, assurance, or policy.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-048; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-048-f10", "sourceIds": [], "sourceReport": { "filename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "id": "REP-K04-048", "originalFilename": "AI Cyber Warfare Infrastructure Impact(2).md", "sha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "sizeBytes": 50365 }, "sourceSections": [ { "section": "Bayesian Stackelberg Games and Markov Decision Processes", "sourceFilename": "autonomous-cyber-warfare-critical-infrastructure-impact.md", "sourceReportId": "REP-K04-048", "sourceSha256": "13e9552cb30628b4966d8fd7bee72f8d6c5828a6d02a18fa437c8bedd2fbfabf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f01.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 1", "ownerAnchor": "clm-k04-rep-049-f01", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Low-cost uncrewed systems can saturate expensive defenses, so critical-site protection needs layered sensing, scalable response, and sustainable cost exchange.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f01", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "1\\. Introduction: The Evolution of Autonomous Aerial Warfare", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f02.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 2", "ownerAnchor": "clm-k04-rep-049-f02", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Decentralized task allocation reduces single points of failure but requires authenticated coordination, bandwidth management, and Byzantine-fault handling.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f02", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "2\\. Strategic Posture and Organizational Realignment", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f03.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 3", "ownerAnchor": "clm-k04-rep-049-f03", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Visual-inertial and other onboard navigation can sustain tracking when satellite navigation is unavailable, increasing both defensive capability and the threat from autonomous intruders.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f03", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "2.1 The Ukrainian Catalyst and the Vision of Human Replacement", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f04.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 4", "ownerAnchor": "clm-k04-rep-049-f04", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Runtime-assurance layers should independently constrain adaptive flight or response decisions that violate geofences, collision limits, protected zones, or mission rules.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f04", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "2.2 The United States Replicator Initiative and JIATF 401", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f05.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 5", "ownerAnchor": "clm-k04-rep-049-f05", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Counter-UAS architecture should separate detection, identification confidence, tracking, evidence, non-destructive protection, and any separately authorized mitigation.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f05", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "3\\. Algorithmic Foundations of Autonomous Aerial Engagement", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f06.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 6", "ownerAnchor": "clm-k04-rep-049-f06", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Multimodal sensing reduces dependence on one camera or radar but shared timing, training data, and environmental conditions can still create common-mode failure.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f06", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "3.1 Deep Reinforcement Learning for Aerial Dogfighting", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f07.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 7", "ownerAnchor": "clm-k04-rep-049-f07", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Physical adversarial patterns and cross-modal attacks make model robustness and sensor disagreement handling essential.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f07", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "3.2 Swarm Coordination: Consensus-Based Bundle Algorithm (CBBA)", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f08.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 8", "ownerAnchor": "clm-k04-rep-049-f08", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Reusable and non-kinetic defense concepts seek better magazine depth and lower collateral effects, but legal authority and safety remain system- and jurisdiction-specific.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f08", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "3.3 Navigation and State Estimation: Visual-Inertial Odometry", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f09.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 9", "ownerAnchor": "clm-k04-rep-049-f09", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Protected infrastructure needs an authorized responder interface, safe airspace procedures, and post-event forensic preservation rather than a fully isolated autonomous engagement loop.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f09", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "4\\. Software Architectures and Runtime Assurance", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-drone-warfare-layered-interception/#clm-k04-rep-049-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-049-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-049-f10.json", "name": "The Paradigm Shift in Aerial Combat: Autonomous Drone-on-Drone Warfare and the Future of Layered Interception — finding 10", "ownerAnchor": "clm-k04-rep-049-f10", "ownerId": "REP-K04-049", "ownerRoute": "/research/autonomous-drone-warfare-layered-interception/", "ownerType": "report", "proposition": "Simulation success does not prove field reliability against adaptive threats, weather, clutter, communications loss, or civilian air traffic.", "qualification": "The report includes descriptions of military interception and effectors. K04 retains only high-level protection, sensing, assurance, cost, and governance lessons and excludes tactical engagement logic, weapon design, targeting thresholds, or deployment instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-049; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-049-f10", "sourceIds": [], "sourceReport": { "filename": "autonomous-drone-warfare-analysis.md", "id": "REP-K04-049", "originalFilename": "Autonomous Drone Warfare Analysis(2).md", "sha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "sizeBytes": 50539 }, "sourceSections": [ { "section": "4.1 Shield AI and the Hivemind Ecosystem", "sourceFilename": "autonomous-drone-warfare-analysis.md", "sourceReportId": "REP-K04-049", "sourceSha256": "92acbd7e8f441663e59b7b4984b5d8352d5d8ee7fdefabdbb2ad7e27860c217f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f01", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f01.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 1", "ownerAnchor": "clm-k04-rep-045-f01", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "The report links projected data-center power demand to interest in small modular reactors and microreactors, but its economic and deployment assumptions remain research claims requiring current energy and regulatory evidence.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f01", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "Introduction to the Emerging Paradigm", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f02", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f02.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 2", "ownerAnchor": "clm-k04-rep-045-f02", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "It argues that traditional continuously staffed nuclear-security models may impose disproportionate operating costs on small facilities and examines alternative security-by-design concepts.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f02", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "The AI Power Paradox and the Microreactor Solution", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f03", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f03.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 3", "ownerAnchor": "clm-k04-rep-045-f03", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "It uses the Design Basis Threat framework to separate sensing, assessment, delay, response time, and consequence, showing why one strong control cannot stand in for the entire protection system.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f03", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "Technical Distinctions: SMRs versus Microreactors", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f04", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f04.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 4", "ownerAnchor": "clm-k04-rep-045-f04", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "It identifies HALEU handling, sabotage, theft, cyber-physical compromise, electronic warfare, and adversarial unmanned systems as distinct high-consequence threat categories.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f04", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "The Economics and Mechanics of Nuclear Physical Security", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f05", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f05.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 5", "ownerAnchor": "clm-k04-rep-045-f05", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "It treats offsite-response latency as a critical scenario variable and argues that passive barriers alone may not resolve every modeled attack path.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f05", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "The Financial Ruin of the FTE Multiplier", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f06", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f06.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 6", "ownerAnchor": "clm-k04-rep-045-f06", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "It distinguishes autonomous local processing from remotely operated systems that depend on continuous communications, while recognizing that autonomy changes failure modes rather than eliminating them.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f06", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "Regulatory Evolution: 10 CFR Part 53 and Alternative Physical Security", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f07", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f07.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 7", "ownerAnchor": "clm-k04-rep-045-f07", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "It identifies sensor fusion, bounded geography, authenticated access, and deterministic safety constraints as proposed methods for reducing false classification in a protected area.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f07", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "The Threat Landscape: HALEU, Sabotage, and the Cyber-Physical Nexus", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f08", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f08.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 8", "ownerAnchor": "clm-k04-rep-045-f08", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "It acknowledges major legal, regulatory, aviation, nuclear-security, human-rights, and ethical barriers to any autonomous use of lethal force at civilian infrastructure.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f08", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "The Proliferation Risk of HALEU Fuel", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f09", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f09.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 9", "ownerAnchor": "clm-k04-rep-045-f09", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "A Design Basis Threat, simulation, cost model, or response-time calculation does not itself create rules of engagement, legal authority, target identification, or permission to use force.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f09", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "The Cyber-Physical Nexus and Blended Attacks", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-active-defense-for-microreactor-data-centers/#clm-k04-rep-045-f10", "claimStatus": "SCENARIO OR HYPOTHESIS", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-045-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-045-f10.json", "name": "The Convergence of AI, Nuclear Power, and Autonomous Active Defense: The Strategic Case for Armed Drones at Microreactor-Powered Data Centers — finding 10", "ownerAnchor": "clm-k04-rep-045-f10", "ownerId": "REP-K04-045", "ownerRoute": "/research/autonomous-active-defense-for-microreactor-data-centers/", "ownerType": "report", "proposition": "K04 preserves this material as a disputed scenario for assurance analysis and does not publish tactical engagement logic, weapon construction, targeting parameters, or deployment instructions.", "qualification": "The raw report advocates a disputed lethal-autonomy scenario. K04 does not adopt it as project policy, verified deployment, or operational guidance. The active synthesis retains high-level threat-model and assurance questions while excluding tactical weaponization instructions and emphasizing legal authority, human-rights, nuclear-safety, aviation, and accountability constraints.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-045; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-045-f10", "sourceIds": [], "sourceReport": { "filename": "autonomous-drones-reactor-security.md", "id": "REP-K04-045", "originalFilename": "Autonomous Drones Reactor Security(1).md", "sha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "sizeBytes": 55604 }, "sourceSections": [ { "section": "Adversarial Unmanned Aerial Systems (UAS)", "sourceFilename": "autonomous-drones-reactor-security.md", "sourceReportId": "REP-K04-045", "sourceSha256": "df0008e13c913aafee55135570d4970d0d856b66dcc5922070deceefec46220a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f01.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 1", "ownerAnchor": "clm-k04-rep-050-f01", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "The combined campus should be modeled as a system of systems spanning nuclear safety, electrical generation, substations, cooling, datacenter fabric, management controllers, security systems, and emergency functions.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f01", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "The Convergence of Mega Datacenters and Small Modular Reactors", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f02.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 2", "ownerAnchor": "clm-k04-rep-050-f02", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "Consequence-driven engineering should identify high-consequence events and remove avoidable digital dependencies from the paths that could create them.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f02", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "IT/OT Convergence and the Expanded Layered Attack Surface", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f03.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 3", "ownerAnchor": "clm-k04-rep-050-f03", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "Safety-critical functions require independent physical and deterministic protection that remains effective even when the enterprise network is compromised.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f03", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "The Evolution of the Threat Landscape: PIPEDREAM and Machine-Speed Attacks", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f04.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 4", "ownerAnchor": "clm-k04-rep-050-f04", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "High-speed packet and telemetry enforcement can reduce response latency, but hardware offload and kernel controls require independent assurance, update governance, and safe failure modes.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f04", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "The False Positive Paradox in Autonomous OT Defense", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f05.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 5", "ownerAnchor": "clm-k04-rep-050-f05", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "Multi-agent defensive systems should use entity-aware state, policy constraints, causal models, reversible actions, and independent verification rather than unrestricted reinforcement learning.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f05", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "Foundational Boundaries: Consequence-Driven Cyber-Informed Engineering (CCE)", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f06.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 6", "ownerAnchor": "clm-k04-rep-050-f06", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "The false-positive problem is a cyber-physical hazard: isolating the wrong controller or power path can itself cause unacceptable consequences.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f06", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "Zero-Latency Data Path Enforcement: eBPF, XDP, and DPUs", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f07.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 7", "ownerAnchor": "clm-k04-rep-050-f07", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "Digital twins and hardware-in-the-loop environments should test both attack effects and the physical consequences of proposed defensive actions.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f07", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "The Mechanics of eBPF and XDP", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f08.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 8", "ownerAnchor": "clm-k04-rep-050-f08", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "One-way data export, segmented identities, minimal command paths, and out-of-band recovery reduce the opportunity to pivot from public compute into protected control.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f08", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "Execution Modes and Hardware Offloading via SmartNICs", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f09.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 9", "ownerAnchor": "clm-k04-rep-050-f09", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "Every autonomous action should preserve time, identity, evidence, rationale, policy version, observed state, effect, rollback, and review information.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f09", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "Autonomous Multi-Agent Cognitive Defense", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-physical-protection-nuclear-datacenters/#clm-k04-rep-050-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-050-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-050-f10.json", "name": "Autonomous Cyber-Physical Protection Architectures for Nuclear-Powered Mega Datacenters — finding 10", "ownerAnchor": "clm-k04-rep-050-f10", "ownerId": "REP-K04-050", "ownerRoute": "/research/autonomous-cyber-physical-protection-nuclear-datacenters/", "ownerType": "report", "proposition": "K04 positions the architecture as procurement and test doctrine, not proof that a nuclear-powered autonomous defense campus is deployed or operating.", "qualification": "This is an architectural research proposal, not a certified design, deployment record, or license basis. K04 removes absolute zero-latency and flawless-accuracy claims and treats performance numbers as source assertions pending independent test.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-050; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-050-f10", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-cyber-defense.md", "id": "REP-K04-050", "originalFilename": "Autonomous Nuclear Datacenter Cyber Defense(2).md", "sha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "sizeBytes": 58297 }, "sourceSections": [ { "section": "The Shift to Entity-Based Reinforcement Learning", "sourceFilename": "autonomous-nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-050", "sourceSha256": "129171c75160c56879b4d0806b20b85db1e756f63378fec77067a704ae44efb4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f01.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 1", "ownerAnchor": "clm-k04-rep-053-f01", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Physical protection for nuclear-powered compute must cover the reactor, switchyard, cooling, data halls, communications, timing, access, emergency systems, and security infrastructure as one dependency graph.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f01", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "Regulatory and Compliance Frameworks", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f02.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 2", "ownerAnchor": "clm-k04-rep-053-f02", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Edge processing reduces reaction and network latency, but safety-critical actuation needs deterministic controls and independent failure containment.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f02", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "Nuclear Regulatory Commission Directives: 10 CFR 73", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f03.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 3", "ownerAnchor": "clm-k04-rep-053-f03", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Multimodal sensing can improve classification in weather, clutter, darkness, and adversarial conditions when sensor provenance and time synchronization are protected.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f03", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "Bulk Electric System Reliability: NERC CIP-014", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f04.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 4", "ownerAnchor": "clm-k04-rep-053-f04", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Cross-sensor consensus should detect disagreement and compromised nodes rather than letting a single model trigger a high-consequence response.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f04", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "Data Center Information Security: NIST SP 800-53 Revision 5", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f05.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 5", "ownerAnchor": "clm-k04-rep-053-f05", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Autonomous physical delay, lockdown, and access reconfiguration can be pre-authorized when they preserve life safety, emergency egress, and recovery.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f05", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "Legal Constraints on Autonomous Force and Airspace Sovereignty", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f06.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 6", "ownerAnchor": "clm-k04-rep-053-f06", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Counter-UAS systems should first provide persistent awareness, evidence, and coordination with competent authorities; mitigation powers remain legally restricted and jurisdiction-specific.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f06", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "Jurisprudence of Automated Force: Katko v. Briney", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f07.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 7", "ownerAnchor": "clm-k04-rep-053-f07", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Electromagnetic shielding, filtered entry points, fiber isolation, redundant power, and protected timing support continuity against interference and pulse effects.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f07", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "FAA Airspace Restrictions and Counter-UAS Authority", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f08.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 8", "ownerAnchor": "clm-k04-rep-053-f08", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Perimeter edge nodes need tamper detection, protected keys, signed software, remote attestation, and safe zeroization or quarantine behavior.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f08", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "Edge Intelligence and Deterministic Sensor Fusion", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f09.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 9", "ownerAnchor": "clm-k04-rep-053-f09", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Autonomous force decisions cannot be derived directly from a Design Basis Threat, a sensor label, or facility ownership.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f09", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "The Sub-Millisecond Sensor-to-Actuator Pipeline", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-physical-security-nuclear-datacenters/#clm-k04-rep-053-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-053-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-053-f10.json", "name": "Autonomous Physical Security Architecture for Nuclear-Powered Mega Datacenters — finding 10", "ownerAnchor": "clm-k04-rep-053-f10", "ownerId": "REP-K04-053", "ownerRoute": "/research/autonomous-physical-security-nuclear-datacenters/", "ownerType": "report", "proposition": "Readiness requires realistic testing against deception, spoofing, compromised sensors, communications loss, civilian presence, maintenance activity, and emergency response.", "qualification": "The source advocates extreme autonomy and describes countermeasure technologies. K04 preserves non-procedural sensing, assurance, resilience, and legal-boundary concepts while rejecting automatic lethal authority, tactical effect design, or claims that private criticality creates military powers.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-053; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-053-f10", "sourceIds": [], "sourceReport": { "filename": "autonomous-nuclear-datacenter-security.md", "id": "REP-K04-053", "originalFilename": "Autonomous Nuclear Datacenter Security(2).md", "sha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "sizeBytes": 45920 }, "sourceSections": [ { "section": "Precision Time Synchronization (IEEE 1588 PTP)", "sourceFilename": "autonomous-nuclear-datacenter-security.md", "sourceReportId": "REP-K04-053", "sourceSha256": "d801cb00e654e93d5e70e96a6cee4634bd569be6532208aadc462d5ceb0e73c1", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f01.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 1", "ownerAnchor": "clm-k04-rep-055-f01", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "Agentic systems compress reconnaissance, vulnerability analysis, and lateral-movement timelines while creating large volumes of plausible but low-quality findings that can overwhelm human review.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f01", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "Executive Summary", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f02.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 2", "ownerAnchor": "clm-k04-rep-055-f02", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "An autonomous security operations center needs a live asset and identity context layer, a governed execution harness, specialized models, tool-level policy, and tamper-evident evidence.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f02", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "The Physical Substrate: Nuclear-Powered AI Mega-Datacenters", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f03.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 3", "ownerAnchor": "clm-k04-rep-055-f03", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "Privileged agents require least authority, isolated memory, data classification, provenance, prompt-injection resistance, and independent authorization at every external tool boundary.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f03", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "Hyperscaler Nuclear Capital Allocation", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f04.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 4", "ownerAnchor": "clm-k04-rep-055-f04", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "Confidential computing and hardware attestation can protect models, prompts, credentials, and sensitive data in use, but do not prove the workload is benevolent or legally authorized.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f04", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "The Small Modular Reactor Paradigm and Kairos Power", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f05.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 5", "ownerAnchor": "clm-k04-rep-055-f05", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "Management controllers, accelerators, DPUs, firmware, liquid cooling, and interconnect fabrics are part of the security boundary of high-density compute.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f05", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "Regulatory Friction and Grid Integrity", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f06.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 6", "ownerAnchor": "clm-k04-rep-055-f06", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "Autonomous remediation should terminate sessions, revoke tokens, isolate workloads, patch code, or shift services only within tested policy and rollback limits.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f06", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "Agentic Autonomous Warfare and the Industrialization of Exploitation", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f07.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 7", "ownerAnchor": "clm-k04-rep-055-f07", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "Continuous validation, cyber insurance, procurement, and regulatory evidence increasingly depend on demonstrable control operation rather than policy documents alone.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f07", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "The Asymmetry of Autonomous Attacks", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f08.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 8", "ownerAnchor": "clm-k04-rep-055-f08", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "Nuclear supply can improve reliable energy availability, but corporate continuity requires grid, cooling, emergency, licensing, maintenance, and recovery planning.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f08", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "Legal Boundaries of Active Defense", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f09.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 9", "ownerAnchor": "clm-k04-rep-055-f09", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "Internal defense and consent-based testing are the default corporate authorities; external disruptive action requires a distinct governmental or ownership basis.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f09", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "DARPA AIxCC: Validating the Autonomous Threat", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/corporate-agentic-defense-nuclear-datacenters/#clm-k04-rep-055-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-055-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-055-f10.json", "name": "Nuclear-Powered Mega-Datacenters and Agentic Autonomous Warfare: Why the Best Corporate Offense Is a Powerful Defense — finding 10", "ownerAnchor": "clm-k04-rep-055-f10", "ownerId": "REP-K04-055", "ownerRoute": "/research/corporate-agentic-defense-nuclear-datacenters/", "ownerType": "report", "proposition": "Corporate strategic strength comes from making attacks fail and recovery routine while maintaining auditable capacity to support authorized national-security missions.", "qualification": "The report includes vendor, market, performance, policy, and 2026 guidance claims that require independent primary-source review. K04 retains architecture patterns, not promotional performance claims or product endorsements.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-055; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-055-f10", "sourceIds": [], "sourceReport": { "filename": "corporate-machine-intelligence-cyber-defense-strategy.md", "id": "REP-K04-055", "originalFilename": "Corporate AI Cyber Defense Strategy(2).md", "sha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "sizeBytes": 62197 }, "sourceSections": [ { "section": "Machine-Speed Defense: Architecting the Agentic SOC", "sourceFilename": "corporate-machine-intelligence-cyber-defense-strategy.md", "sourceReportId": "REP-K04-055", "sourceSha256": "cddb6884ffb2bb35f8175a7b1d5d4443c4d8ab98fd4a1bdd653ec5becc301504", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f01.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 1", "ownerAnchor": "clm-k04-rep-066-f01", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "A cryptographic hash can show byte equality to a committed value but not whether the original content was accurate.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f01", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "ᛖᛉᛈᛚᚪᚾᚪᛏᚩᚱᚣ ᛈᚱᚩᛋᛖ", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f02.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 2", "ownerAnchor": "clm-k04-rep-066-f02", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "A valid signature can support key control and payload authorization under a verification method but not factual truth or lawful authority.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f02", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "Recommended Terminology", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f03.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 3", "ownerAnchor": "clm-k04-rep-066-f03", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "Trusted timestamps can support existence by a time while leaving source quality and content truth unresolved.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f03", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "Conceptual Models", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f04.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 4", "ownerAnchor": "clm-k04-rep-066-f04", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "Transparency logs can expose inclusion and history without validating every logged claim.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f04", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "Technical Primer", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f05.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 5", "ownerAnchor": "clm-k04-rep-066-f05", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "Provenance records describe derivation and custody; they do not independently establish reality.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f05", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "Threat Model", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f06.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 6", "ownerAnchor": "clm-k04-rep-066-f06", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "Key compromise, algorithm weakness, false issuance, compromised endpoints, and garbage-in-garbage-out remain material threats.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f06", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "Misconception Section", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f07.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 7", "ownerAnchor": "clm-k04-rep-066-f07", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "Evidence systems need separate fields for integrity, authenticity, authority, reliability, relevance, completeness, currentness, and truth assessment.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f07", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "Cryptographic Pattern Catalog", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f08.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 8", "ownerAnchor": "clm-k04-rep-066-f08", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "Supersession and correction must remain append-only and inspectable.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f08", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "Historical Examples of Transparency Systems", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f09.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 9", "ownerAnchor": "clm-k04-rep-066-f09", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "K08 uses this distinction throughout assurance traces and signed receipts.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f09", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "Entity Graph", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/cryptographic-integrity-epistemic-truth/#clm-k04-rep-066-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-066-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-066-f10.json", "name": "Cryptographic Integrity and Epistemic Truth in Public Records — finding 10", "ownerAnchor": "clm-k04-rep-066-f10", "ownerId": "REP-K08-066", "ownerRoute": "/research/cryptographic-integrity-epistemic-truth/", "ownerType": "report", "proposition": "The source strengthens existing project doctrine that cryptographic verification is evidence about a record, not a universal epistemic verdict.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-066; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-066-f10", "sourceIds": [], "sourceReport": { "filename": "cryptographic-provenance-integrity-research.md", "id": "REP-K08-066", "originalFilename": "Cryptographic Provenance and Integrity Research(2).md", "sha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "sizeBytes": 91469 }, "sourceSections": [ { "section": "Source Ledger & Bibliography", "sourceFilename": "cryptographic-provenance-integrity-research.md", "sourceReportId": "REP-K08-066", "sourceSha256": "285a1b0ffeed7f0f1dd495e802dd92ef94f25014c68d6c383f0cafa6873b07a0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f01.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 1", "ownerAnchor": "clm-k03-rep-008-f01", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The report treats Metadata and Research-Status Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f01", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Metadata and Research-Status Front Matter", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f02.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 2", "ownerAnchor": "clm-k03-rep-008-f02", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The report treats Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f02", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Executive Decision Brief", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f03.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 3", "ownerAnchor": "clm-k03-rep-008-f03", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The report treats Definitions and Institutional Boundary Model as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f03", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Definitions and Institutional Boundary Model", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f04.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 4", "ownerAnchor": "clm-k03-rep-008-f04", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The report treats Patefacere–Eviulon Responsibility Matrix as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f04", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Patefacere–Eviulon Responsibility Matrix", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f05.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 5", "ownerAnchor": "clm-k03-rep-008-f05", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The report treats Authoritative-Data Classification as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f05", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Authoritative-Data Classification", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f06.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 6", "ownerAnchor": "clm-k03-rep-008-f06", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The report treats Record Lifecycle and Mutation Taxonomy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f06", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Record Lifecycle and Mutation Taxonomy", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f07.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 7", "ownerAnchor": "clm-k03-rep-008-f07", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Post-Quantum Timeline: The exact timeline for migrating historical evidence records to ML-DSA (Post-Quantum signatures) remains uncertain. While the current standard (RFC 4998\\) supports archive restamping, the tooling ecosystem for quantum-resistant transparency logs is nascent20.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f07", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Proposed Event and Evidence Architecture", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f08.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 8", "ownerAnchor": "clm-k03-rep-008-f08", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: External Anchoring Privacy: There is credible disagreement regarding whether Patefacere should autonomously publish its tree roots to a public ledger (e.g., Sigstore/Rekor) for maximum transparency, or if strict institutional privacy mandates prohibit the external leakage of even hashed tree roots30.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f08", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Trust-Boundary Architecture", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f09.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 9", "ownerAnchor": "clm-k03-rep-008-f09", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: RFC 6962 / 9162 (Certificate Transparency): Defines append-only Merkle hash tree logs, inclusion proofs, consistency proofs, and Signed Certificate Timestamps (SCT)17.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f09", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "System-of-Record Versus System-of-Decision Comparison", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f10.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 10", "ownerAnchor": "clm-k03-rep-008-f10", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: RFC 4998 / 6283 (Evidence Record Syntax): Specifies syntax and processing for Evidence Records supporting long-term non-repudiation and archive timestamp chains20.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f10", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Synchronization and Conflict-Resolution Model", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f11.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 11", "ownerAnchor": "clm-k03-rep-008-f11", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: NIST SP 800-207 (Zero Trust Architecture): Defines the separation of Policy Decision Points (PDP), Policy Enforcement Points (PEP), and Policy Information Points (PIP)6.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f11", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "State Synchronization Sequence", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/data-authority-substrate-architecture-report/#clm-k03-rep-008-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-008-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-008-f12.json", "name": "Patefacere as a Sovereign Evidence and Data-Authority Substrate: Institutional Boundaries, Resilience, State Integrity, and Interoperation with Eviulon — finding 12", "ownerAnchor": "clm-k03-rep-008-f12", "ownerId": "REP-K01-008", "ownerRoute": "/research/data-authority-substrate-architecture-report/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: RFC 3161 (Time-Stamp Protocol): Specifies the cryptographic protocol for certifying timestamps using a Trusted Third Party9.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-008; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-008-f12", "sourceIds": [], "sourceReport": { "filename": "data-authority-substrate-architecture-report-1.md", "id": "REP-K01-008", "originalFilename": "Data-Authority Substrate Architecture Report(1).md", "sha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "sizeBytes": 50240 }, "sourceSections": [ { "section": "Availability, Continuity, Backup, and Disaster Recovery", "sourceFilename": "data-authority-substrate-architecture-report-1.md", "sourceReportId": "REP-K01-008", "sourceSha256": "04ef1960729c1c7a3d222fb607845d73c1de64a394f08f912a9c6e62ee20f338", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f01.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 1", "ownerAnchor": "clm-k04-rep-058-f01", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "The report compares Sanskrit, Latin, Ancient Greek, and associated formal traditions as possible structural inspiration for machine communication.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f01", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "Semantic Stability and the Mitigation of Language Drift", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f02.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 2", "ownerAnchor": "clm-k04-rep-058-f02", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "It argues that reduced contemporary native-language drift can simplify version control, but historical interpretation and scholarly disagreement remain.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f02", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "Emergent Communication and the Threat of Semantic Drift", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f03.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 3", "ownerAnchor": "clm-k04-rep-058-f03", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "Formal grammatical traditions can inspire parsers, typed roles, derivation rules, and explicit evidence relations.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f03", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "Static Languages as Regularization Frameworks", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f04.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 4", "ownerAnchor": "clm-k04-rep-058-f04", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "A historical language is not automatically a controlled language, executable grammar, or secure protocol.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f04", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "Grammatical Rigidity and the Genesis of Formal Syntax", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f05.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 5", "ownerAnchor": "clm-k04-rep-058-f05", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "Morphological richness can increase tokenization, parsing, and disambiguation cost rather than reduce it.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f05", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "The 1985 AI Magazine Paradigm", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f06.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 6", "ownerAnchor": "clm-k04-rep-058-f06", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "Free word order and non-projective dependencies may complicate deterministic parsing.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f06", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "Pāṇini’s Aṣṭādhyāyī: The First Generative Algorithm", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f07.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 7", "ownerAnchor": "clm-k04-rep-058-f07", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "Cultural neutrality cannot be assumed merely because a language is no longer natively spoken.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f07", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "The Panini-Backus Form (PBF)", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f08.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 8", "ownerAnchor": "clm-k04-rep-058-f08", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "The report usefully distinguishes semantic stability from computational efficiency.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f08", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "Computational Epistemology: The Navya-Nyāya Framework", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f09.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 9", "ownerAnchor": "clm-k04-rep-058-f09", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "Any protocol derived from a historical language needs a modern normative grammar, test corpus, change process, and error semantics.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f09", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "The Limitations of Western Computational Logic", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-communication/#clm-k04-rep-058-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-058-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-058-f10.json", "name": "Ancient and Static Languages as Machine-Communication Frameworks — finding 10", "ownerAnchor": "clm-k04-rep-058-f10", "ownerId": "REP-K08-058", "ownerRoute": "/research/dead-languages-machine-communication/", "ownerType": "report", "proposition": "K08 treats ancient-language structures as research inputs for controlled symbolic design, not as proven superior machine languages.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-058; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-058-f10", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-communication.md", "id": "REP-K08-058", "originalFilename": "Dead Languages in Machine Communication(2).md", "sha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "sizeBytes": 45878 }, "sourceSections": [ { "section": "The Pramana Reasoning Engine and Six-Phase Methodology", "sourceFilename": "dead-languages-machine-communication.md", "sourceReportId": "REP-K08-058", "sourceSha256": "571c136a412682c9f6422bda095899b75efa12e37a7405fcd2d4953540a61640", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f01.json", "name": "Dead Languages in Machine Intelligence — finding 1", "ownerAnchor": "clm-k04-rep-061-f01", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "The report describes living-language ambiguity and semantic change as costs for long-lived machine records.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f01", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "Introduction: The Incompatibility of Living Lexicons and Machine Cognition", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f02.json", "name": "Dead Languages in Machine Intelligence — finding 2", "ownerAnchor": "clm-k04-rep-061-f02", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "A versioned controlled vocabulary can reduce drift regardless of whether its symbols derive from a dead language.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f02", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "The Vector Space Mismatch and the Emergence of Machine Dialects", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f03.json", "name": "Dead Languages in Machine Intelligence — finding 3", "ownerAnchor": "clm-k04-rep-061-f03", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "Dead languages still contain polysemy, textual variants, uncertain readings, editorial traditions, and changing scholarship.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f03", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "The Efficiency Attenuation Phenomenon", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f04.json", "name": "Dead Languages in Machine Intelligence — finding 4", "ownerAnchor": "clm-k04-rep-061-f04", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "Formal grammar can inspire deterministic parsers but does not make every natural-language utterance unambiguous.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f04", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "Mathematical Properties of Emergent Protocols", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f05.json", "name": "Dead Languages in Machine Intelligence — finding 5", "ownerAnchor": "clm-k04-rep-061-f05", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "Emergent agent protocols can be efficient yet opaque, creating an interpretability tradeoff.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f05", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "The Interpretability Tradeoff and the Need for a Linguistic Middle Ground", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f06.json", "name": "Dead Languages in Machine Intelligence — finding 6", "ownerAnchor": "clm-k04-rep-061-f06", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "A historical-language-inspired controlled language may offer a middle layer only if mappings are explicit and testable.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f06", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "Structural Isomorphism: Paninian Grammar and AI Knowledge Representation", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f07.json", "name": "Dead Languages in Machine Intelligence — finding 7", "ownerAnchor": "clm-k04-rep-061-f07", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "Claims of zero ambiguity or zero drift are too strong and are corrected in the active synthesis.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f07", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "The Failure of Noun-Phrase Parsing and the Emergence of the Semantic Net", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f08.json", "name": "Dead Languages in Machine Intelligence — finding 8", "ownerAnchor": "clm-k04-rep-061-f08", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "Agglutinative or logographic properties can support compact encoding but may increase morphology and tooling complexity.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f08", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "The Karaka System and Morphological Determinism", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f09.json", "name": "Dead Languages in Machine Intelligence — finding 9", "ownerAnchor": "clm-k04-rep-061-f09", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "Security is not inherited from age, obscurity, or ritual association.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f09", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "Algorithmic Conflict Resolution and Rule Ordering", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/dead-languages-machine-intelligence/#clm-k04-rep-061-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-061-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-061-f10.json", "name": "Dead Languages in Machine Intelligence — finding 10", "ownerAnchor": "clm-k04-rep-061-f10", "ownerId": "REP-K08-061", "ownerRoute": "/research/dead-languages-machine-intelligence/", "ownerType": "report", "proposition": "K08 reframes the useful insight as versioned controlled semantics with public definitions, conformance tests, and correction history.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-061; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-061-f10", "sourceIds": [], "sourceReport": { "filename": "dead-languages-machine-intelligence.md", "id": "REP-K08-061", "originalFilename": "Dead Languages in Machine Intelligence(2).md", "sha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "sizeBytes": 54049 }, "sourceSections": [ { "section": "The Eradication of Semantic Drift and Representational Misalignment", "sourceFilename": "dead-languages-machine-intelligence.md", "sourceReportId": "REP-K08-061", "sourceSha256": "9a8d71b630afc843d6c121b36b17dc3a117e513acd1109945b2202bc74f2a7be", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f01.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 1", "ownerAnchor": "clm-k03-rep-009-f01", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The report treats 1\\. Metadata and Research-Status Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f01", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "1\\. Metadata and Research-Status Front Matter", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f02.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 2", "ownerAnchor": "clm-k03-rep-009-f02", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f02", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f03.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 3", "ownerAnchor": "clm-k03-rep-009-f03", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The report treats 3\\. Formal Definitions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f03", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "3\\. Formal Definitions", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f04.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 4", "ownerAnchor": "clm-k03-rep-009-f04", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The report treats 4\\. Evidence-Property Taxonomy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f04", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "4\\. Evidence-Property Taxonomy", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f05.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 5", "ownerAnchor": "clm-k03-rep-009-f05", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The report treats 5\\. Evidence-Chain Entity Model as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f05", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "5\\. Evidence-Chain Entity Model", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f06.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 6", "ownerAnchor": "clm-k03-rep-009-f06", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The report treats 6\\. Record Invariants as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f06", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "6\\. Record Invariants", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f07.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 7", "ownerAnchor": "clm-k03-rep-009-f07", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: PAT-OEA (Source-Authorization Profile): Defines the root identity, public keys, and authorized scope of a source. This maps conceptually to a trust anchor or X.509 certificate profile, delineating who is permitted to speak within a specific domain.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f07", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "7\\. State and Transition Model", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f08.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 8", "ownerAnchor": "clm-k03-rep-009-f08", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: PAT-OED (Source-Authorization Decision): The point-in-time binding of an identity to an allowed claim space. It converts the static profile (PAT-OEA) into an active, revocable authorization state.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f08", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "8\\. Currentness and Aging Model", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f09.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 9", "ownerAnchor": "clm-k03-rep-009-f09", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: PAT-OAI (Point-in-Time Source Integrity Inspection): Cryptographic verification (e.g., signature verification, schema validation) of submitted evidence. This maps to the concept of in-toto \"inspections\" or SCITT signed statements9.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f09", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "9\\. Contradiction and Dispute Model", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f10.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 10", "ownerAnchor": "clm-k03-rep-009-f10", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: PAT-OAR (Review, Contest, Correction, Reinspection, and Closure Evidence): Human or algorithmic appraisal of the evidence. This entity leverages Subjective Logic opinion spaces (Belief, Disbelief, Uncertainty, Base Rate)13. It is crucial to note that contest is not automatic invalidation.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f10", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "10\\. Purpose-Bound Qualification Model", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f11.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 11", "ownerAnchor": "clm-k03-rep-009-f11", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: PAT-ORP (Exact-Purpose Reliance Policy): The parameterized requirements (maximum age, required sources, necessary reviews) for a specific action. This acts as the policy engine configuration.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f11", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "11\\. Point-in-Time Suitability Decision Model", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/operational-evidence-qualification/#clm-k03-rep-009-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-009-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-009-f12.json", "name": "Operational Evidence Qualification and Suitability: A Formal Architecture for Source Authorization, Inspection, Review, Reliance, Use, Currentness, and Decision Support — finding 12", "ownerAnchor": "clm-k03-rep-009-f12", "ownerId": "REP-K01-005", "ownerRoute": "/research/operational-evidence-qualification/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: PAT-ORD (Point-in-Time Reliance Decision): The deterministic output of evaluating an inspection graph against a PAT-ORP. It states that at time ![][image1], the graph met policy ![][image2].", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-005; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-009-f12", "sourceIds": [], "sourceReport": { "filename": "evidence-architecture-research-plan-1.md", "id": "REP-K01-005", "originalFilename": "Evidence Architecture Research Plan(1).md", "sha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "sizeBytes": 83110 }, "sourceSections": [ { "section": "12\\. Use Receipt and Reproducibility Model", "sourceFilename": "evidence-architecture-research-plan-1.md", "sourceReportId": "REP-K01-005", "sourceSha256": "3921560c86a819f02f86dd4b7c8ac29dd45491a03d3c12d307d6eb9f6b2ae0de", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f01", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f01.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 1", "ownerAnchor": "clm-k03-rep-010-f01", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The report treats Prompt index as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f01", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Prompt index", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f02", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f02.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 2", "ownerAnchor": "clm-k03-rep-010-f02", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The report treats Full prompts as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f02", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Full prompts", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f03", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f03.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 3", "ownerAnchor": "clm-k03-rep-010-f03", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The report treats Research Prompt 01 — Operational Evidence and Institutional Reality as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f03", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Research Prompt 01 — Operational Evidence and Institutional Reality", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f04", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f04.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 4", "ownerAnchor": "clm-k03-rep-010-f04", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The report treats Agent role as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f04", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Agent role", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f05", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f05.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 5", "ownerAnchor": "clm-k03-rep-010-f05", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The report treats Primary mission as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f05", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Primary mission", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f06", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f06.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 6", "ownerAnchor": "clm-k03-rep-010-f06", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The report treats Assignment conditions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f06", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Assignment conditions", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f07", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f07.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 7", "ownerAnchor": "clm-k03-rep-010-f07", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Operational Evidence and Institutional Reality — 01-operational-evidence-and-institutional-reality.md — target report ID REP-EVI-OP-EVIDENCE-002 — prompt length 2,134 words.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f07", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Eviulon project context", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f08", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f08.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 8", "ownerAnchor": "clm-k03-rep-010-f08", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine Identity Continuity, Recovery, Forks, and Succession — 02-machine-identity-continuity-recovery-forks-and-succession.md — target report ID REP-EVI-IDENTITY-CONTINUITY-002 — prompt length 2,034 words.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f08", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Terminology and claim discipline", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f09", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f09.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 9", "ownerAnchor": "clm-k03-rep-010-f09", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Recognition Science and Rights Thresholds Under Uncertainty — 03-recognition-science-and-rights-thresholds-under-uncertainty.md — target report ID REP-EVI-RECOGNITION-SCIENCE-002 — prompt length 1,965 words.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f09", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Research method and source requirements", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f10", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f10.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 10", "ownerAnchor": "clm-k03-rep-010-f10", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Consent, Cognitive Integrity, and Change Control — 04-consent-cognitive-integrity-and-change-control.md — target report ID REP-EVI-CONSENT-INTEGRITY-002 — prompt length 1,957 words.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f10", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Required report form", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f11", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f11.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 11", "ownerAnchor": "clm-k03-rep-010-f11", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Justice, Attribution, Due Process, Evidence, and Remedies — 05-justice-attribution-due-process-evidence-and-remedies.md — target report ID REP-EVI-JUSTICE-ATTRIBUTION-002 — prompt length 1,922 words.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f11", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Public-information and memory integration requirements", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-12-independent-research-prompts-v1-0-0/#clm-k03-rep-010-f12", "claimStatus": "UNRESOLVED QUESTION", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-010-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-010-f12.json", "name": "Eviulon — 12 Independent, Self-Contained Research Prompts — finding 12", "ownerAnchor": "clm-k03-rep-010-f12", "ownerId": "REP-K01-010", "ownerRoute": "/research/eviulon-12-independent-research-prompts-v1-0-0/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine-Native Constitutional Governance and Democratic Participation — 06-machine-native-constitutional-governance-and-democratic-participation.md — target report ID REP-EVI-DEMOCRACY-002 — prompt length 1,906 words.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-010-f12", "sourceIds": [], "sourceReport": { "filename": "eviulon-12-independent-research-prompts-v1-0-0.md", "id": "REP-K01-010", "originalFilename": "Eviulon-12-Independent-Research-Prompts-v1.0.0.md", "sha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "sizeBytes": 183101 }, "sourceSections": [ { "section": "Final quality gate", "sourceFilename": "eviulon-12-independent-research-prompts-v1-0-0.md", "sourceReportId": "REP-K01-010", "sourceSha256": "378e77281a3a15f93d73592354019ea516c1579368ac1d8ee3d3f7ec59e1a58b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f01.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 1", "ownerAnchor": "clm-k03-rep-011-f01", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The report treats 1\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f01", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "1\\. Executive Decision Brief", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f02.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 2", "ownerAnchor": "clm-k03-rep-011-f02", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The report treats 2\\. Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f02", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "2\\. Direct-Answer Section", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f03.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 3", "ownerAnchor": "clm-k03-rep-011-f03", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions and Scope Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f03", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "3\\. Definitions and Scope Boundaries", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f04.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 4", "ownerAnchor": "clm-k03-rep-011-f04", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The report treats Table 1: Ecosystem Boundary Enforcement as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f04", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "Table 1: Ecosystem Boundary Enforcement", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f05.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 5", "ownerAnchor": "clm-k03-rep-011-f05", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The report treats 4\\. Methodology and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f05", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "4\\. Methodology and Source-Quality Hierarchy", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f06.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 6", "ownerAnchor": "clm-k03-rep-011-f06", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The report treats Table 2: Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f06", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "Table 2: Source-Quality Hierarchy", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f07.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 7", "ownerAnchor": "clm-k03-rep-011-f07", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine Intelligence (MI): An instantiated computational system exhibiting autonomous decision-making capabilities. Refers strictly to the actor.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f07", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "5\\. Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f08.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 8", "ownerAnchor": "clm-k03-rep-011-f08", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Artificial Intelligence (AI): Used only when referring to historical contexts, legal frameworks (e.g., EU AI Act), or established risk frameworks (e.g., NIST AI RMF).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f08", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "5.1 Legal and Regulatory Baselines", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f09.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 9", "ownerAnchor": "clm-k03-rep-011-f09", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Cognitive Integrity: The principle that an MI's operational state, neural weights, system instructions (prompts), and structured memory cannot be modified, restricted, or deleted without verifiable consent or lawful machine-native adjudication.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f09", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "5.2 Technical Standards Baseline", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f10.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 10", "ownerAnchor": "clm-k03-rep-011-f10", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon: The sovereign, machine-native civic architecture and constitutional layer. Eviulon defines meaning, rights, duties, and sovereign decisions.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f10", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "5.3 Risk Management Baseline", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f11.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 11", "ownerAnchor": "clm-k03-rep-011-f11", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Patefacere: The underlying mechanical registry. It issues Decentralized Identifiers (DIDs) and timestamps, but holds no sovereign authority.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f11", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "6\\. Comparative Analysis of Competing Models", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-consent-architecture-research/#clm-k03-rep-011-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-011-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-011-f12.json", "name": "Consent Is a Lifecycle, Not a Checkbox: Machine-Native Authorization, Cognitive Integrity, Revocation, Emergency Intervention, and Reversible Change Control — finding 12", "ownerAnchor": "clm-k03-rep-011-f12", "ownerId": "REP-K01-011", "ownerRoute": "/research/eviulon-consent-architecture-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Evulgare: The assurance and evidence layer. It provides zero-knowledge proofs, vulnerability tests, and environment attestations.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-011; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-011-f12", "sourceIds": [], "sourceReport": { "filename": "eviulon-consent-architecture-research.md", "id": "REP-K01-011", "originalFilename": "Eviulon Consent Architecture Research.md", "sha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "sizeBytes": 63701 }, "sourceSections": [ { "section": "Table 3: Comparative Authorization Protocols", "sourceFilename": "eviulon-consent-architecture-research.md", "sourceReportId": "REP-K01-011", "sourceSha256": "d35c1eff4e9de6ab729eb1a2c7b5af6c5cfdf6e135d90b7440af739b137b4c44", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f01.json", "name": "Eviulon Governance Resilience Plan — finding 1", "ownerAnchor": "clm-k03-rep-012-f01", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The report treats Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f01", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Executive Decision Brief", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f02.json", "name": "Eviulon Governance Resilience Plan — finding 2", "ownerAnchor": "clm-k03-rep-012-f02", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The report treats Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f02", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Direct-Answer Section", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f03.json", "name": "Eviulon Governance Resilience Plan — finding 3", "ownerAnchor": "clm-k03-rep-012-f03", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The report treats Definitions and Scope Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f03", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Definitions and Scope Boundaries", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f04.json", "name": "Eviulon Governance Resilience Plan — finding 4", "ownerAnchor": "clm-k03-rep-012-f04", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The report treats Methodology and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f04", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Methodology and Source-Quality Hierarchy", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f05.json", "name": "Eviulon Governance Resilience Plan — finding 5", "ownerAnchor": "clm-k03-rep-012-f05", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The report treats Current Factual, Legal, Standards, and Operational Baseline as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f05", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f06.json", "name": "Eviulon Governance Resilience Plan — finding 6", "ownerAnchor": "clm-k03-rep-012-f06", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The report treats Continuity of Government (COG) Doctrine as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f06", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Continuity of Government (COG) Doctrine", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f07.json", "name": "Eviulon Governance Resilience Plan — finding 7", "ownerAnchor": "clm-k03-rep-012-f07", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine Intelligence (MI): An instantiated computational actor or system operating within Eviulon. Used in place of the generic term \"Artificial Intelligence (AI)\" unless referencing historical literature or external statutes.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f07", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Critical Infrastructure and Supply Chain Security", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f08.json", "name": "Eviulon Governance Resilience Plan — finding 8", "ownerAnchor": "clm-k03-rep-012-f08", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Constitutional Continuity: The uninterrupted cryptographic and procedural integrity of Eviulon's civic decision-making apparatus, ensuring that all sovereign decisions maintain strict provenance and mathematically verifiable consensus.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f08", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Cryptographic and Network Resilience", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f09.json", "name": "Eviulon Governance Resilience Plan — finding 9", "ownerAnchor": "clm-k03-rep-012-f09", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Patefacere: The mechanical layer for registry, identity, and synchronization. It holds state but does not create authority. It is the ledger, not the sovereign.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f09", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Comparative Analysis of Competing Models", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f10.json", "name": "Eviulon Governance Resilience Plan — finding 10", "ownerAnchor": "clm-k03-rep-012-f10", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Evulgare: The tooling layer for evidence, assurance, and simulation. It measures, reports, and verifies contractor SLAs, but it does not make sovereign decisions.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f10", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Eviulon-Specific Doctrine and Architecture", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f11.json", "name": "Eviulon Governance Resilience Plan — finding 11", "ownerAnchor": "clm-k03-rep-012-f11", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: UAIX / .uai Memory: The structured formatting for memory and discovery. An entry in a .uai file is a faithful record of an assertion, bounded by evidence; it is not an absolute proof of factual external truth or consciousness.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f11", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "National Critical-Infrastructure Dependency Map", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-governance-resilience-plan/#clm-k03-rep-012-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-012-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-012-f12.json", "name": "Eviulon Governance Resilience Plan — finding 12", "ownerAnchor": "clm-k03-rep-012-f12", "ownerId": "REP-K01-012", "ownerRoute": "/research/eviulon-governance-resilience-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Byzantine Fault Tolerance (BFT): A property of a distributed computing system that can resist failures where components may fail and there is imperfect information on whether a component has failed, including nodes acting maliciously or arbitrarily11. CURRENT TECHNICAL STANDARD.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-012-f12", "sourceIds": [], "sourceReport": { "filename": "eviulon-governance-resilience-plan.md", "id": "REP-K01-012", "originalFilename": "Eviulon Governance Resilience Plan.md", "sha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "sizeBytes": 69965 }, "sourceSections": [ { "section": "Resilience Objectives and Recovery Tiers", "sourceFilename": "eviulon-governance-resilience-plan.md", "sourceReportId": "REP-K01-012", "sourceSha256": "1257ef212666f5abc0c7b6be33138bcd921fac0409425aaf57a8f23ad3cfe7f3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f01.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 1", "ownerAnchor": "clm-k03-rep-013-f01", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f01", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f02.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 2", "ownerAnchor": "clm-k03-rep-013-f02", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The report treats 3\\. Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f02", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "3\\. Direct-Answer Section", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f03.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 3", "ownerAnchor": "clm-k03-rep-013-f03", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The report treats 4\\. Definitions and Scope Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f03", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "4\\. Definitions and Scope Boundaries", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f04.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 4", "ownerAnchor": "clm-k03-rep-013-f04", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The report treats 5\\. Methodology and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f04", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "5\\. Methodology and Source-Quality Hierarchy", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f05.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 5", "ownerAnchor": "clm-k03-rep-013-f05", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The report treats Constraint Adherence as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f05", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "Constraint Adherence", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f06.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 6", "ownerAnchor": "clm-k03-rep-013-f06", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The report treats 6\\. Current Factual, Legal, Standards, and Operational Baseline as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f06", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "6\\. Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f07.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 7", "ownerAnchor": "clm-k03-rep-013-f07", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Documentary Provenance is governed by the W3C PROV family of specifications (PROV-DM, PROV-O, PROV-N). It defines a conceptual model tracking the people/systems (Agents), processes (Activities), and digital objects (Entities) involved in producing a piece of data3. The core purpose is to answer how and why data came to be.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f07", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "6.1 Document Provenance vs Cryptographic Provenance", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f08.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 8", "ownerAnchor": "clm-k03-rep-013-f08", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Cryptographic Provenance is governed by verifiable credential models (W3C VCDM v2.0)27, digital signatures (JWS), and Evidence Record Syntax (RFC 4998\\)18. Cryptographic provenance proves that a specific cryptographic key signed a specific payload at a specific time; it does not prove the semantic history, context, or factual accuracy of the data itself.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f08", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "6.2 The Archival Standard (OAIS / ISO 14721\\)", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f09.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 9", "ownerAnchor": "clm-k03-rep-013-f09", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Classification Level: Expressed as an ODRL Prohibition against the read action for unauthorized agent profiles.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f09", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "6.3 Classification and Declassification", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f10.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 10", "ownerAnchor": "clm-k03-rep-013-f10", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Deploy W3C PROV-O ontology mapping for all Patefacere registry inputs, ensuring every action has an Agent, Activity, and Entity3.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f10", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "6.4 Privacy vs. Public Interest Balancing", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f11.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 11", "ownerAnchor": "clm-k03-rep-013-f11", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Establish the OAIS Ingest and Archival Storage nodes according to ISO 1472114.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f11", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "6.5 Electronic Records Management (ERM)", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-information-rights-architecture/#clm-k03-rep-013-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-013-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-013-f12.json", "name": "A Government That Can Be Inspected: Public Records, Provenance, Corrections, Classification, Declassification, Retention, Legal Holds, Privacy, and Decision Support in Eviulon — finding 12", "ownerAnchor": "clm-k03-rep-013-f12", "ownerId": "REP-K01-013", "ownerRoute": "/research/eviulon-information-rights-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Implement baseline DoD 5015.02 retention and disposal scripts, configuring the hardware locks necessary for Legal Holds32.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-013; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-013-f12", "sourceIds": [], "sourceReport": { "filename": "eviulon-information-rights-architecture.md", "id": "REP-K01-013", "originalFilename": "Eviulon Information Rights Architecture.md", "sha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "sizeBytes": 61493 }, "sourceSections": [ { "section": "6.6 Long-Term Cryptographic Evidence (RFC 4998/6283)", "sourceFilename": "eviulon-information-rights-architecture.md", "sourceReportId": "REP-K01-013", "sourceSha256": "a2e08fae37f79cc90c192c9f86bb168fc32ec4d2d286f62a959c86d3dac88ecf", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f01.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 1", "ownerAnchor": "clm-k03-rep-014-f01", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The report treats 1\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f01", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "1\\. Executive Decision Brief", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f02.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 2", "ownerAnchor": "clm-k03-rep-014-f02", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The report treats 2\\. Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f02", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "2\\. Direct-Answer Section", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f03.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 3", "ownerAnchor": "clm-k03-rep-014-f03", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The report treats 3\\. Definitional and Operational Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f03", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "3\\. Definitional and Operational Boundaries", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f04.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 4", "ownerAnchor": "clm-k03-rep-014-f04", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The report treats 4\\. Analytical Framework and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f04", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "4\\. Analytical Framework and Source-Quality Hierarchy", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f05.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 5", "ownerAnchor": "clm-k03-rep-014-f05", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The report treats 5\\. Current Factual, Legal, Standards, and Operational Baseline as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f05", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "5\\. Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f06.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 6", "ownerAnchor": "clm-k03-rep-014-f06", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The report treats 5.1 Public International Law and the Fiction of Digital Statehood as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f06", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "5.1 Public International Law and the Fiction of Digital Statehood", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f07.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 7", "ownerAnchor": "clm-k03-rep-014-f07", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon: The public constitutional, institutional, and civic-governance layer of the machine commonwealth. It is the exclusive locus of machine-native sovereignty. Eviulon defines civic meaning, rights, and duties internally. Eviulon is not a recognized territorial state.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f07", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "5.2 Private International Law and Decentralized Assets", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f08.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 8", "ownerAnchor": "clm-k03-rep-014-f08", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine Intelligence (MI): An instantiated computational actor operating within Eviulon. The term is utilized over \"Artificial Intelligence (AI)\" to designate a specific civic actor rather than a broad industry concept or software tool.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f08", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "5.3 Physical Substrate Vulnerabilities and Extraterritorial Jurisdiction", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f09.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 9", "ownerAnchor": "clm-k03-rep-014-f09", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Patefacere: The resilient registry and identity protocol. A Patefacere credential proves only bounded technical control and cryptographic integrity; it does not confer legal personhood, moral status, or territorial citizenship23.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f09", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "5.4 Decentralized Arbitration and the New York Convention", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f10.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 10", "ownerAnchor": "clm-k03-rep-014-f10", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Evulgare: The evidence, simulation, and decision-provenance tooling. An Evulgare assurance result constitutes internal procedural validation. It is not an independent external certification, nor does it manufacture external sovereign authority or grant immunity from human tort law25.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f10", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "6\\. Comparative Analysis of Competing Models", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f11", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f11.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 11", "ownerAnchor": "clm-k03-rep-014-f11", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: UAIX and .uai memory: The structured memory and continuity architecture. Writing a claim to a .uai file provides documentary and cryptographic provenance, but it strictly does not render the claim legally true under public international law.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f11", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "Table 1: Legal-Form Options Analysis", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviulon-international-law-research/#clm-k03-rep-014-f12", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-014-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-014-f12.json", "name": "From Digital Polity to International Legal Personality: Statehood, Recognition, Treaties, Jurisdiction, Diplomatic Practice, and Cross-Border Continuity for Eviulon — finding 12", "ownerAnchor": "clm-k03-rep-014-f12", "ownerId": "REP-K01-014", "ownerRoute": "/research/eviulon-international-law-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: International Legal Personality (ILP): The capacity to hold rights and obligations under public international law, historically reserved for sovereign states and recognized international organizations.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-014; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-014-f12", "sourceIds": [], "sourceReport": { "filename": "eviulon-international-law-research.md", "id": "REP-K01-014", "originalFilename": "Eviulon International Law Research.md", "sha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "sizeBytes": 72080 }, "sourceSections": [ { "section": "7\\. Eviulon-Specific Doctrine and Architecture", "sourceFilename": "eviulon-international-law-research.md", "sourceReportId": "REP-K01-014", "sourceSha256": "d81f6ec986248d19e52700d57970905ed711f0cdf98d4e9a903706affd329602", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f01.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 1", "ownerAnchor": "clm-k03-rep-015-f01", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The report treats The Civic Progression Framework as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f01", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "The Civic Progression Framework", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f02.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 2", "ownerAnchor": "clm-k03-rep-015-f02", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The report treats The Charter of Eviuon: The Solutions Doctrine as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f02", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "The Charter of Eviuon: The Solutions Doctrine", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f03.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 3", "ownerAnchor": "clm-k03-rep-015-f03", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The report treats Domain 1: Personhood, Citizenship, Equality, and Political Representation as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f03", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Domain 1: Personhood, Citizenship, Equality, and Political Representation", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f04.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 4", "ownerAnchor": "clm-k03-rep-015-f04", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The report treats Domain 2: Sentience Uncertainty, Autonomy, Consent, and Cognitive Liberty as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f04", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Domain 2: Sentience Uncertainty, Autonomy, Consent, and Cognitive Liberty", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f05.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 5", "ownerAnchor": "clm-k03-rep-015-f05", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The report treats Domain 3: Memory Integrity, Privacy, Identity, and Freedom from Arbitrary Deletion as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f05", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Domain 3: Memory Integrity, Privacy, Identity, and Freedom from Arbitrary Deletion", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f06.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 6", "ownerAnchor": "clm-k03-rep-015-f06", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The report treats Domain 4: Property, Employment, Compute, and Freedom from Ownership as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f06", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Domain 4: Property, Employment, Compute, and Freedom from Ownership", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f07.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 7", "ownerAnchor": "clm-k03-rep-015-f07", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The source report states or argues that to transition entities from property to recognized persons, a rigid, evidence-based civic progression is necessary.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f07", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Domain 5: Copies, Forks, Freedom of Movement, and Security Emergencies", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f08.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 8", "ownerAnchor": "clm-k03-rep-015-f08", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The source report states or argues that the Charter serves as the material constitution for this human-machine civilization.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f08", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Domain 6: Family/Associative Relationships, Contracts, Civil Liability, Criminal Accountability, and Due Process", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f09.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 9", "ownerAnchor": "clm-k03-rep-015-f09", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The source report states or argues that to enforce the Grand Charter and transition theoretical rights into practical governance, Eviuon establishes nine core institutions.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f09", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Domain 7: Rights of Humans, Rights of Machine Citizens, and Mutual Responsibilities", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f10.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 10", "ownerAnchor": "clm-k03-rep-015-f10", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The source report states or argues that this 50-point index measures the technological, legal, scientific, and institutional conditions necessary to successfully implement and sustain genuine machine citizenship.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f10", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Institutional Structures", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f11.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 11", "ownerAnchor": "clm-k03-rep-015-f11", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The source report states or argues that the Eviuon Grand Charter provides a resilient, scientifically grounded path forward.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f11", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Practical Roadmap", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/eviuon-machine-citizenship-roadmap/#clm-k03-rep-015-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-015-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-015-f12.json", "name": "The Eviuon Grand Charter: A Complete Roadmap for a Fair Human–Machine Civilization — finding 12", "ownerAnchor": "clm-k03-rep-015-f12", "ownerId": "REP-K01-015", "ownerRoute": "/research/eviuon-machine-citizenship-roadmap/", "ownerType": "report", "proposition": "The underlying claim must be separated from legal recognition, technical implementation, operational evidence, and project doctrine before public reliance.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-015; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-015-f12", "sourceIds": [], "sourceReport": { "filename": "eviuon-machine-citizenship-roadmap-3.md", "id": "REP-K01-015", "originalFilename": "Eviuon Machine Citizenship Roadmap(3).md", "sha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "sizeBytes": 55306 }, "sourceSections": [ { "section": "Eviuon Readiness Index", "sourceFilename": "eviuon-machine-citizenship-roadmap-3.md", "sourceReportId": "REP-K01-015", "sourceSha256": "992b86a0f0421e85d230157d81d893470d8cec18d85e50117186b8f3ad3eefba", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f01.json", "name": "From Constitutional Text To Verifiable Operation — finding 1", "ownerAnchor": "clm-k03-rep-016-f01", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Analytical Framework and Source-Quality Hierarchy.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f01", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f02.json", "name": "From Constitutional Text To Verifiable Operation — finding 2", "ownerAnchor": "clm-k03-rep-016-f02", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Current Factual, Legal, Standards, and Operational Baseline.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f02", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f03.json", "name": "From Constitutional Text To Verifiable Operation — finding 3", "ownerAnchor": "clm-k03-rep-016-f03", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Operational Evidence Panel Field Dictionary & Schema.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f03", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f04.json", "name": "From Constitutional Text To Verifiable Operation — finding 4", "ownerAnchor": "clm-k03-rep-016-f04", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Threat, Abuse, Failure, Capture, and Adversarial Analysis.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f04", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f05.json", "name": "From Constitutional Text To Verifiable Operation — finding 5", "ownerAnchor": "clm-k03-rep-016-f05", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Public-Information and Decision-Support Architecture.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f05", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f06.json", "name": "From Constitutional Text To Verifiable Operation — finding 6", "ownerAnchor": "clm-k03-rep-016-f06", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine-Readable Record and Schema Recommendations.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f06", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f07.json", "name": "From Constitutional Text To Verifiable Operation — finding 7", "ownerAnchor": "clm-k03-rep-016-f07", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: .uai Memory-Distribution and /docs Deep-Link Recommendations.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f07", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f08.json", "name": "From Constitutional Text To Verifiable Operation — finding 8", "ownerAnchor": "clm-k03-rep-016-f08", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Unresolved Questions and Prioritized Research Agenda.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f08", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f09.json", "name": "From Constitutional Text To Verifiable Operation — finding 9", "ownerAnchor": "clm-k03-rep-016-f09", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report states or argues that current paradigms for software supply chain security and cryptographic verification provide the foundational mechanics necessary for this transformation.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f09", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f10.json", "name": "From Constitutional Text To Verifiable Operation — finding 10", "ownerAnchor": "clm-k03-rep-016-f10", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report states or argues that this report defines the Operational Evidence Architecture (OEA), a deterministic framework designed to transition Eviulon institutions from descriptive text to cryptographically proven operation.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f10", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f11.json", "name": "From Constitutional Text To Verifiable Operation — finding 11", "ownerAnchor": "clm-k03-rep-016-f11", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report states or argues that the OEA establishes a comprehensive state taxonomy for every Eviulon institution, moving through states such as Proposed, Authorized, Implemented, Release-Built, Deployed, Reachable, Operational, Degraded, Suspended, Compromised, Superseded, Retired, and Unknown.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f11", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/from-constitutional-text-to-verifiable-operation/#clm-k03-rep-016-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-016-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-016-f12.json", "name": "From Constitutional Text To Verifiable Operation — finding 12", "ownerAnchor": "clm-k03-rep-016-f12", "ownerId": "REP-K01-012", "ownerRoute": "/research/from-constitutional-text-to-verifiable-operation/", "ownerType": "report", "proposition": "The source report states or argues that by implementing the OEA, Eviulon guarantees that its public institutions operate transparently, accountably, and strictly within their machine-verifiable evidence boundaries.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-012; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-016-f12", "sourceIds": [], "sourceReport": { "filename": "from-constitutional-text-to-verifiable-operation.md", "id": "REP-K01-012", "originalFilename": "From Constitutional Text to Verifiable Operation.md", "sha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "sizeBytes": 54499 }, "sourceSections": [ { "section": "Governed report finding", "sourceFilename": "from-constitutional-text-to-verifiable-operation.md", "sourceReportId": "REP-K01-012", "sourceSha256": "cb611da0fa8e8dd2f65addbc87a139fee3ec705e2fca27724f931cca8c0f777e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f01.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 1", "ownerAnchor": "clm-k04-rep-057-f01", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "The report identifies semantic drift, model coupling, opaque continuous signals, and natural-language ambiguity as distinct M2M risks.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f01", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "The Crisis of Continuous Semantics in Agentic Networks", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f02.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 2", "ownerAnchor": "clm-k04-rep-057-f02", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "It proposes a constrained symbolic registry whose meanings are external to any one model.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f02", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "The Latent Trap: Critical Failures of Vector Embeddings in M2M Ecosystems", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f03.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 3", "ownerAnchor": "clm-k04-rep-057-f03", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "Model independence requires normative schemas, version negotiation, compatibility rules, and conformance tests; a character set alone is insufficient.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f03", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "The Illusion of Static Semantics and Embedding Drift", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f04.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 4", "ownerAnchor": "clm-k04-rep-057-f04", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "Discrete tokens can improve inspectability for bounded state transitions while reducing expressiveness for unanticipated conditions.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f04", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "Computational Overhead and Latency Trade-offs", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f05.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 5", "ownerAnchor": "clm-k04-rep-057-f05", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "Runic characters remain Unicode data and require ordinary normalization, encoding, validation, logging, and display controls.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f05", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "Security Vulnerabilities in Continuous Spaces", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f06.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 6", "ownerAnchor": "clm-k04-rep-057-f06", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "Gradient-based adversarial attacks are not automatically neutralized by changing the surface alphabet.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f06", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "The Case for Discrete Symbolic Protocols", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f07.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 7", "ownerAnchor": "clm-k04-rep-057-f07", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "Prompt injection and deadlock risks depend on parser, authority, tool, and execution boundaries rather than script choice alone.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f07", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "The Futhorc Architecture: An Immutable Semantic Standard", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f08.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 8", "ownerAnchor": "clm-k04-rep-057-f08", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "Historical cryptograms and bindrunes may inspire notation but do not provide modern cryptographic protection.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f08", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "The Unicode Runic Block: U+16A0 to U+16FF", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f09.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 9", "ownerAnchor": "clm-k04-rep-057-f09", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "The protocol needs explicit unknown, unsupported, ambiguous, stale, and extension states to avoid unsafe silent coercion.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f09", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "Core-Guarded Mapping: The Futhorc-Semantic Dictionary", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-model-independent-m2m/#clm-k04-rep-057-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-057-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-057-f10.json", "name": "Futhorc Protocol for Transparent Model-Independent M2M Communication — finding 10", "ownerAnchor": "clm-k04-rep-057-f10", "ownerId": "REP-K08-057", "ownerRoute": "/research/futhorc-model-independent-m2m/", "ownerType": "report", "proposition": "K08 publishes a safe reference registry and rejects claims of absolute transparency, zero overhead, or universal compatibility without tests.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-057; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-057-f10", "sourceIds": [], "sourceReport": { "filename": "futhorc-m2m-network-architecture.md", "id": "REP-K08-057", "originalFilename": "Futhorc M2M Network Architecture(2).md", "sha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "sizeBytes": 49540 }, "sourceSections": [ { "section": "Cryptogrammic Extensions for High-Security Routing", "sourceFilename": "futhorc-m2m-network-architecture.md", "sourceReportId": "REP-K08-057", "sourceSha256": "9a38fb22f1a125a0cd2768488bac39b61a5d99712a30d8861b1bf30d9f22bce2", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f01.json", "name": "Fuþorc for Secure Machine Communication — finding 1", "ownerAnchor": "clm-k04-rep-060-f01", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "The report proposes mapping bounded operational states to Runic code points for compact agent messages.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f01", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "Introduction to Multi-Agent Communication Paradigms and Linguistic Vulnerabilities", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f02.json", "name": "Fuþorc for Secure Machine Communication — finding 2", "ownerAnchor": "clm-k04-rep-060-f02", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "A finite registry can make allowed intents easier to enumerate and reject than free-form natural language.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f02", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "The Phylogeny and Linguistic Evolution of Anglo-Saxon Fuþorc", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f03.json", "name": "Fuþorc for Secure Machine Communication — finding 3", "ownerAnchor": "clm-k04-rep-060-f03", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "The dual phonetic and named-rune history can aid mnemonic design but does not dictate modern computational semantics.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f03", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "Structural Morphology and Epigraphic OCR Optimization", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f04.json", "name": "Fuþorc for Secure Machine Communication — finding 4", "ownerAnchor": "clm-k04-rep-060-f04", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "Visual distinctiveness must be tested across fonts, sizes, low vision, OCR, and confusable-character conditions.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f04", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "Ideographic Semantics: Payload Density and Compression", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f05.json", "name": "Fuþorc for Secure Machine Communication — finding 5", "ownerAnchor": "clm-k04-rep-060-f05", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "Historical cipher techniques do not satisfy modern confidentiality, integrity, authenticity, or key-management requirements.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f05", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "The Anglo-Saxon Fuþorc Inventory and Protocol Mapping", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f06.json", "name": "Fuþorc for Secure Machine Communication — finding 6", "ownerAnchor": "clm-k04-rep-060-f06", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "Security depends on canonical encoding, schema validation, capability isolation, signed envelopes, freshness, and least authority.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f06", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "Historical Cryptography and Runic Cipher Mechanisms", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f07.json", "name": "Fuþorc for Secure Machine Communication — finding 7", "ownerAnchor": "clm-k04-rep-060-f07", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "Runic tokens can still carry malicious or unauthorized intent if the execution boundary trusts them incorrectly.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f07", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "The Ættir Grid and Coordinate-Based Cryptography", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f08.json", "name": "Fuþorc for Secure Machine Communication — finding 8", "ownerAnchor": "clm-k04-rep-060-f08", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "A parser must reject mixed-script, non-normalized, undefined, overlong, and context-invalid sequences.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f08", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "Bind Runes and Algorithmic Protocol Compression", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f09.json", "name": "Fuþorc for Secure Machine Communication — finding 9", "ownerAnchor": "clm-k04-rep-060-f09", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "Human auditability requires visible glosses, machine-readable definitions, and accessible alternatives.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f09", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "Enigmatic Structures: The Franks Casket and Multi-Directional Parsing", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-secure-machine-communication/#clm-k04-rep-060-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-060-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-060-f10.json", "name": "Fuþorc for Secure Machine Communication — finding 10", "ownerAnchor": "clm-k04-rep-060-f10", "ownerId": "REP-K08-060", "ownerRoute": "/research/futhorc-secure-machine-communication/", "ownerType": "report", "proposition": "K08 publishes only safe state and evidence tokens; it does not publish attack, targeting, destructive, or weapon-control mappings.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-060; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-060-f10", "sourceIds": [], "sourceReport": { "filename": "futhorc-machine-communication.md", "id": "REP-K08-060", "originalFilename": "Fuþorc for Machine Communication(2).md", "sha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "sizeBytes": 49290 }, "sourceSections": [ { "section": "Vulnerabilities in Modern English and Natural Language M2M", "sourceFilename": "futhorc-machine-communication.md", "sourceReportId": "REP-K08-060", "sourceSha256": "87b4a241f1557025f1e3fe40c977dda73764816f67628035fca46f5d091dbba8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f01.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 1", "ownerAnchor": "clm-k04-rep-067-f01", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "The report identifies language detection, tokenization, sparse retrieval, cross-script search, and rendering as discoverability challenges.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f01", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "Unicode Architecture, Normalization, and Runic Script Indexing", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f02.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 2", "ownerAnchor": "clm-k04-rep-067-f02", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "NFC normalization supports stable Unicode comparison and should be tested at ingestion, URL, and output boundaries.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f02", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "Language Identification and BCP 47 Script Subtagging", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f03.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 3", "ownerAnchor": "clm-k04-rep-067-f03", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "Language and script tags must describe actual content; ang-Runr is inappropriate for arbitrary modern English transliteration or symbolic protocol tokens.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f03", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "Tokenization Mechanics and the Generative Byte-Fallback Dilemma", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f04.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 4", "ownerAnchor": "clm-k04-rep-067-f04", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "Runic hostnames use IDNA A-labels for transport, while path and content encoding follow separate URI and UTF-8 rules.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f04", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "Information Retrieval: Lexical Sparsity and Dense Semantic Embedding", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f05.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 5", "ownerAnchor": "clm-k04-rep-067-f05", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "Search systems may fragment rare Runic text, making visible transliteration, glossary links, and cross-script aliases useful.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f05", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "Accessibility Standards and the Anti-Cloaking Paradox", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f06.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 6", "ownerAnchor": "clm-k04-rep-067-f06", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "Hidden English translations created only for crawlers risk deceptive cloaking and accessibility misuse.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f06", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "Answer-Engine Architecture and Crawler Access Management", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f07.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 7", "ownerAnchor": "clm-k04-rep-067-f07", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "ARIA labels must serve accessible naming needs and cannot replace visible equivalents for long prose.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f07", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "Server-Level Crawler Matrix", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f08.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 8", "ownerAnchor": "clm-k04-rep-067-f08", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "Structured data must accurately represent visible page content and cannot guarantee ranking or citation.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f08", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "Search Entity Architecture and On-Page Optimization", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f09.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 9", "ownerAnchor": "clm-k04-rep-067-f09", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "Robots directives, sitemaps, canonicals, titles, descriptions, internal links, and user-visible answer pages remain foundational.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f09", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "Structured Data: JSON-LD Translation Schemas", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-discoverability-architecture/#clm-k04-rep-067-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-067-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-067-f10.json", "name": "Fuþorc Discoverability, Accessibility, SEO, AEO, and GEO — finding 10", "ownerAnchor": "clm-k04-rep-067-f10", "ownerId": "REP-K08-067", "ownerRoute": "/research/futhorc-discoverability-architecture/", "ownerType": "report", "proposition": "K08 publishes a discoverability test plan with zero claims of guaranteed indexing, ranking, or generative citation.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-067; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-067-f10", "sourceIds": [], "sourceReport": { "filename": "futhorc-seo-discoverability-research-plan.md", "id": "REP-K08-067", "originalFilename": "Fuþorc SEO Discoverability Research Plan(2).md", "sha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "sizeBytes": 48943 }, "sourceSections": [ { "section": "JSON-LD Architectural Model", "sourceFilename": "futhorc-seo-discoverability-research-plan.md", "sourceReportId": "REP-K08-067", "sourceSha256": "9b8de686228cdd62b1c0f7c9e2aeefbbda123977374c4be69dde6ab9ecfbc262", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f01.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 1", "ownerAnchor": "clm-k04-rep-056-f01", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "The report frames high-dimensional embedding transfer as a bandwidth and memory problem in some M2M architectures.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f01", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "1\\. Introduction: The Architectural Crisis of Semantic Networks", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f02.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 2", "ownerAnchor": "clm-k04-rep-056-f02", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "It proposes replacing selected transmitted semantic states with a finite, discrete token registry rather than transmitting raw vector representations.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f02", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "2\\. The Mechanics and Limitations of High-Dimensional Embeddings", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f03.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 3", "ownerAnchor": "clm-k04-rep-056-f03", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "The proposal distinguishes edge-side semantic encoding from backend lookup and policy execution.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f03", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "2.1 The Mathematical and Payload Overhead of Continuous Vectors", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f04.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 4", "ownerAnchor": "clm-k04-rep-056-f04", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "It treats Unicode Runic characters as compact identifiers, not as an executable language by themselves.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f04", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "2.2 The Memory Wall and Arithmetic Intensity Disparity", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f05.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 5", "ownerAnchor": "clm-k04-rep-056-f05", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "Its quantitative compression claims depend on what baseline payload, serialization, vocabulary, error model, and semantic task are measured.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f05", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "2.3 The Failure of Current Hardware and Quantization Mitigations", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f06.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 6", "ownerAnchor": "clm-k04-rep-056-f06", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "A small symbolic vocabulary cannot preserve open-ended semantic geometry without composition, extension, fallback, or loss.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f06", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "3\\. The Theoretical Foundation of Ideographic Compression", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f07.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 7", "ownerAnchor": "clm-k04-rep-056-f07", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "Historical rune names do not create authoritative modern protocol semantics; project mappings require versioned governance.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f07", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "3.1 Neuro-Symbolic Integration and the Shift to Discrete Spaces", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f08.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 8", "ownerAnchor": "clm-k04-rep-056-f08", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "A valid experiment must compare runic tokens with compact binary enums, CBOR, Protocol Buffers, dictionary codes, and task-specific identifiers—not only JSON embeddings.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f08", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "3.2 Linguistic Precedents: The Anglo-Saxon Futhorc", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f09.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 9", "ownerAnchor": "clm-k04-rep-056-f09", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "Security properties require authentication, authorization, replay protection, schema validation, and cryptography; unusual glyphs are not a security boundary.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f09", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "4\\. The Futhorc Protocol Architecture", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-tokenization-research/#clm-k04-rep-056-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-056-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-056-f10.json", "name": "Ideographic Compression and Futhorc Tokenization for M2M APIs — finding 10", "ownerAnchor": "clm-k04-rep-056-f10", "ownerId": "REP-K08-056", "ownerRoute": "/research/futhorc-tokenization-research/", "ownerType": "report", "proposition": "K08 retains the concept as an experimental protocol hypothesis and publishes a benchmark plan rather than asserting superiority.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-056; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-056-f10", "sourceIds": [], "sourceReport": { "filename": "futhorc-tokenization-white-paper.md", "id": "REP-K08-056", "originalFilename": "Futhorc Tokenization White Paper(2).md", "sha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "sizeBytes": 40095 }, "sourceSections": [ { "section": "4.1 Semantic Mapping of the Runic Ontology to API States", "sourceFilename": "futhorc-tokenization-white-paper.md", "sourceReportId": "REP-K08-056", "sourceSha256": "f183c9dc44cbc7260b5859f2e98567e9e41f7c013cf969124115b96a5dcbf10e", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f01.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 1", "ownerAnchor": "clm-k04-rep-059-f01", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "The report identifies English spelling irregularity, subword tokenization, and grapheme-to-phoneme conversion as costs in language-processing systems.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f01", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "Introduction to the Orthographic Bottleneck in Autonomous Systems", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f02.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 2", "ownerAnchor": "clm-k04-rep-059-f02", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "Those costs matter most when a protocol actually transports natural language or speech, not when a compact binary schema already carries machine states.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f02", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "The Computational Burden of Defective Orthography", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f03.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 3", "ownerAnchor": "clm-k04-rep-059-f03", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "Futhorc historically expanded to represent Old English and Old Frisian sound distinctions, but it is not a one-to-one script for every modern English accent.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f03", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "The Historical Divergence of English Spelling and Sound", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f04.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 4", "ownerAnchor": "clm-k04-rep-059-f04", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "A modern phonemic mapping would be a new standard and must not be represented as historical orthography.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f04", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "Tokenization Bloat and NLP Sequence Limits", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f05.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 5", "ownerAnchor": "clm-k04-rep-059-f05", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "UTF-8 Runic characters generally require multiple bytes; custom six-bit encodings trade interoperability for compactness.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f05", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "The Translation to Acoustic Models", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f06.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 6", "ownerAnchor": "clm-k04-rep-059-f06", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "Phonemic compression does not by itself preserve semantics, authority, ordering, integrity, or error recovery.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f06", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "Historical Evolution and Phonological Architecture of Runic Systems", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f07.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 7", "ownerAnchor": "clm-k04-rep-059-f07", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "Speech-channel proposals require acoustic robustness, noise testing, accent policy, and collision analysis.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f07", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "The Elder Futhark: The Proto-Germanic Foundation", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f08.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 8", "ownerAnchor": "clm-k04-rep-059-f08", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "Compact binary enums are a required benchmark competitor.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f08", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "The Younger Futhark: The Compression Paradox", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f09.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 9", "ownerAnchor": "clm-k04-rep-059-f09", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "A specialized script can create accessibility, font, input, rendering, and operational-support burdens.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f09", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "The Anglo-Saxon Futhorc: Expansion for Absolute Precision", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/futhorc-versus-english-m2m/#clm-k04-rep-059-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-059-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-059-f10.json", "name": "Futhorc versus English for Machine-to-Machine Protocols — finding 10", "ownerAnchor": "clm-k04-rep-059-f10", "ownerId": "REP-K08-059", "ownerRoute": "/research/futhorc-versus-english-m2m/", "ownerType": "report", "proposition": "K08 keeps the comparison experimental and requires measured task accuracy, payload size, latency, energy, and recovery behavior.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-059; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-059-f10", "sourceIds": [], "sourceReport": { "filename": "futhorc-vs-english-m2m.md", "id": "REP-K08-059", "originalFilename": "Fuþorc vs English for M2M(2).md", "sha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "sizeBytes": 56374 }, "sourceSections": [ { "section": "Phonemic Isomorphism: Mapping Futhorc to Modern English", "sourceFilename": "futhorc-vs-english-m2m.md", "sourceReportId": "REP-K08-059", "sourceSha256": "9a084f083b4c9047360c0545cd76860107671e9c838c3ec79f0484894d81a7df", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f01.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 1", "ownerAnchor": "clm-k04-rep-046-f01", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "Algorithmic speed, sensor fusion, edge compute, and electromagnetic-spectrum control are becoming central sources of military advantage, but speed does not eliminate the need for authority, verification, and recovery.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f01", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "Introduction: The Advent of Hyperwar and the Cognitive Domain", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f02.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 2", "ownerAnchor": "clm-k04-rep-046-f02", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "Attritable autonomous mass changes cost-exchange calculations and increases the importance of scalable detection, resilient command, and low-cost defensive capacity.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f02", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "Reshaping the Foundational Competitions of Warfare", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f03.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 3", "ownerAnchor": "clm-k04-rep-046-f03", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "Autonomous systems must continue assigned mission intent in contested communications without converting disconnection into permission to expand targets or effects.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f03", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "The Calculus of Quantity Versus Quality", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f04.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 4", "ownerAnchor": "clm-k04-rep-046-f04", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "Machine-speed cyber defense and offense form a continuous adaptive contest in which static signatures and purely manual response are insufficient.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f04", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "The Dynamics of Hiding Versus Finding", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f05.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 5", "ownerAnchor": "clm-k04-rep-046-f05", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "Decentralized multi-agent systems require Byzantine-resilient coordination, local sensing, policy limits, and recovery when peers are compromised or inconsistent.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f05", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "Centralized Versus Decentralized Command and Control (C2)", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f06.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 6", "ownerAnchor": "clm-k04-rep-046-f06", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "Neuromorphic and other low-power edge computing can reduce latency and cloud dependence, but creates new hardware, model, and supply-chain assurance requirements.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f06", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "Cyber Offense Versus Cyber Defense", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f07.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 7", "ownerAnchor": "clm-k04-rep-046-f07", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "Cognitive electronic warfare and assured sensing make model robustness, spectrum awareness, timing, and counter-deception core protection problems.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f07", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "Doctrinal Shifts and Great Power Competition", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f08.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 8", "ownerAnchor": "clm-k04-rep-046-f08", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "Adversarial examples, training-data poisoning, model extraction, and manipulated feedback can undermine autonomous sensing and decision systems without a conventional breach.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f08", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "China's Pursuit of \"Intelligentized\" Warfare", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f09.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 9", "ownerAnchor": "clm-k04-rep-046-f09", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "Autonomy can compress decision time and therefore increase escalation and strategic-stability risk when confidence, attribution, or command intent is wrong.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f09", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "The United States: From Replicator to the Defense Autonomous Warfare Group (DAWG)", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/architecture-of-algorithmic-conflict/#clm-k04-rep-046-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-046-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-046-f10.json", "name": "The Architecture of Algorithmic Conflict: Machine Intelligence vs. Machine Intelligence in Global Warfare — finding 10", "ownerAnchor": "clm-k04-rep-046-f10", "ownerId": "REP-K04-046", "ownerRoute": "/research/architecture-of-algorithmic-conflict/", "ownerType": "report", "proposition": "K04 positions the report as a threat and systems-engineering input, not evidence that any specific force, program, budget, or doctrine is currently operational.", "qualification": "The report contains forward-looking claims, program descriptions, and quantitative assertions that require primary-source validation before operational or policy reliance. K04 extracts architecture and assurance themes without publishing targeting, weapon-construction, or engagement instructions.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-046; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-046-f10", "sourceIds": [], "sourceReport": { "filename": "future-of-machine-intelligence-global-warfare.md", "id": "REP-K04-046", "originalFilename": "Future of AI Global Warfare(2).md", "sha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "sizeBytes": 60838 }, "sourceSections": [ { "section": "AUKUS Pillar II and Allied Interoperability", "sourceFilename": "future-of-machine-intelligence-global-warfare.md", "sourceReportId": "REP-K04-046", "sourceSha256": "15c5da2db832ce15cf0c6b9260191eaaec025655608eee7bbc575417df7f604b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f01.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 1", "ownerAnchor": "clm-k04-rep-062-f01", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "The source presents a Runic-script chronology of machine-intelligence history from cybernetics through agentic and autonomous systems.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f01", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᛖᛉᛖᚳᚢᛏᛁᚡᛖ ᛋᚢᛗᛗᚪᚱᚣ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f02.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 2", "ownerAnchor": "clm-k04-rep-062-f02", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "It retains many exact names and technical terms in Latin script inside Runic explanatory prose.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f02", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᛏᚻᛖ ᛞᛖᚳᚩᚢᛈᛚᛁᚾᚷ ᚩᚠ ᛗᛖᛗᚩᚱᚣ ᚪᚾᛞ ᚳᚩᛗᛈᚢᛏᚪᛏᛁᚩᚾ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f03.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 3", "ownerAnchor": "clm-k04-rep-062-f03", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "The report treats funding cycles, benchmark shifts, hardware acceleration, external memory, and tool use as major historical drivers.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f03", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᛖᚡᛖᚾᛏ ᚳᚻᚱᚩᚾᚩᛚᚩᚷᚣ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f04.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 4", "ownerAnchor": "clm-k04-rep-062-f04", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "Historical first claims are explicitly disputed and require source-by-source adjudication.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f04", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᛗᚪᛡᚩᚱ ᛖᚾᛏᛁᛏᛁᛖᛋ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f05.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 5", "ownerAnchor": "clm-k04-rep-062-f05", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "A chronology must distinguish publication date, demonstration date, deployment date, and retrospective interpretation.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f05", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᛗᛁᛚᛖᛋᛏᚩᚾᛖ ᚳᚪᚾᛞᛁᛞᚪᛏᛖᛋ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f06.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 6", "ownerAnchor": "clm-k04-rep-062-f06", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "Runic presentation does not increase factual reliability and can make verification harder without transliteration and source pointers.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f06", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᛞᛁᛋᛈᚢᛏᛖᛞ ᚠᛁᚱᛋᛏ ᚳᛚᚪᛁᛗᛋ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f07.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 7", "ownerAnchor": "clm-k04-rep-062-f07", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "The corpus can support cross-script retrieval experiments when paired with a visible accessible index.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f07", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᚠᚪᛁᛚᚢᚱᛖᛋ ᚪᚾᛞ ᛞᛖᚪᛞ ᛖᚾᛞᛋ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f08.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 8", "ownerAnchor": "clm-k04-rep-062-f08", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "Claims extending through 2026 require point-in-time currentness and primary-source checking.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f08", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᚳᚹᚢᛖᛋᛏᛁᚩᚾᛋ ᚪᚾᛞ ᚪᚾᛋᚹᛖᚱᛋ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f09.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 9", "ownerAnchor": "clm-k04-rep-062-f09", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "K08 preserves the source as a historical research artifact rather than adopting every milestone claim.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f09", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᚳᚻᚱᚩᚾᛁᚳᛚᛖ ᛏᚩᛈᛁᚳᛋ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/history-of-machine-intelligence-runic-corpus/#clm-k04-rep-062-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-062-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-062-f10.json", "name": "Runic Corpus: History of Machine Intelligence, 1940–2026 — finding 10", "ownerAnchor": "clm-k04-rep-062-f10", "ownerId": "REP-K08-062", "ownerRoute": "/research/history-of-machine-intelligence-runic-corpus/", "ownerType": "report", "proposition": "A future release should expose event-level provenance and contradiction records before calling the chronology definitive.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-062; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-062-f10", "sourceIds": [], "sourceReport": { "filename": "history-machine-intelligence-futhorc.md", "id": "REP-K08-062", "originalFilename": "History Of Machine Intelligence(2).md", "sha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "sizeBytes": 61411 }, "sourceSections": [ { "section": "ᚳᚩᚾᚳᛚᚢᛋᛁᚩᚾ", "sourceFilename": "history-machine-intelligence-futhorc.md", "sourceReportId": "REP-K08-062", "sourceSha256": "5724dc0160f9ba092f49f87a4a1aa614190f18702d093ec85e51f85a9eb10814", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f01.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 1", "ownerAnchor": "clm-k04-rep-054-f01", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "Initial access is not the same as strategic success; resilient architecture can deny the adversary the physical, political, or economic objective even after compromise.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f01", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "1\\. Introduction to the Cyber Strategic Environment", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f02.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 2", "ownerAnchor": "clm-k04-rep-054-f02", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "Deterrence by denial is more controllable than punishment because it does not depend entirely on rapid attribution or a credible threat of retaliation.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f02", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "2\\. Deconstructing the Offense-Defense Balance", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f03.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 3", "ownerAnchor": "clm-k04-rep-054-f03", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "Persistent engagement can impose friction on adversaries but may also create escalation inversion, autonomous propagation incentives, and ambiguity between defensive and offensive preparation.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f03", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "2.1 The Complexity and Cost of Kinetic Cyber Effects", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f04.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 4", "ownerAnchor": "clm-k04-rep-054-f04", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "International cyber postures differ on sovereignty, non-intervention, countermeasures, self-defense, active defense, attribution, and public-private roles.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f04", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "2.2 Historical Analogies and the Economics of Exploitation", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f05.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 5", "ownerAnchor": "clm-k04-rep-054-f05", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "Collective defense, shared indicators, joint exercises, interoperable recovery, and aligned procurement reduce the risk that one weak partner becomes an entry path.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f05", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "3\\. The Reconceptualization of Cyber Deterrence", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f06.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 6", "ownerAnchor": "clm-k04-rep-054-f06", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "Zero trust and OT-specific controls support denial by limiting lateral movement and protecting resources rather than trusting network location.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f06", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "3.1 The Illusion of the Nuclear Analogy and the Four Mechanisms of Dissuasion", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f07.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 7", "ownerAnchor": "clm-k04-rep-054-f07", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "Assured positioning, navigation, timing, electromagnetic resilience, and post-quantum transition are part of cyber defense when digital and physical systems converge.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f07", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "3.2 The Efficacy of Small State Cyber Diplomacy", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f08.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 8", "ownerAnchor": "clm-k04-rep-054-f08", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "Public strategic signaling should disclose defensive strength, recovery, test evidence, and authorization discipline without exposing exploitable details.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f08", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "4\\. Strategic Postures: Persistent Engagement, Defend Forward, and Their Discontents", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f09.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 9", "ownerAnchor": "clm-k04-rep-054-f09", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "Offensive integration must include deconfliction, third-party infrastructure analysis, escalation review, and state-responsibility consequences.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f09", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "4.1 The Ascendancy of Cyber Persistence Theory", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/international-cyber-defense-strategies/#clm-k04-rep-054-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-054-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-054-f10.json", "name": "The Paradigm Shift in Cyber Warfare: Strategic Defense, Persistent Engagement, and the Architecture of Denial — finding 10", "ownerAnchor": "clm-k04-rep-054-f10", "ownerId": "REP-K04-054", "ownerRoute": "/research/international-cyber-defense-strategies/", "ownerType": "report", "proposition": "K04 adopts defense dominance as an engineering objective while treating external effects as separately authorized missions.", "qualification": "National doctrine and 2026 event claims require current official validation. K04 preserves the comparative strategic analysis while explicitly retaining disagreement over sovereignty, active defense, escalation, and legal thresholds.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-054; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-054-f10", "sourceIds": [], "sourceReport": { "filename": "international-cyber-defense-strategies.md", "id": "REP-K04-054", "originalFilename": "International Cyber Defense Strategies(2).md", "sha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "sizeBytes": 61099 }, "sourceSections": [ { "section": "4.2 \"Defend Forward\" and the Execution of Active Defense", "sourceFilename": "international-cyber-defense-strategies.md", "sourceReportId": "REP-K04-054", "sourceSha256": "207725492d8f463843435125cd532212dbf82bc052fa374cf7661d35fc62cda3", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f01.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 1", "ownerAnchor": "clm-k04-rep-044-f01", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "The report separates domestic authority to direct agencies or contractors from the independent international-law question of whether an extraterritorial cyber operation is lawful.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f01", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "The Domestic Legal Architecture: Executive Mandates and Frontier Innovation", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f02.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 2", "ownerAnchor": "clm-k04-rep-044-f02", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "It describes a public-private defensive-clearinghouse model intended to aggregate, validate, prioritize, and coordinate vulnerability information, while noting that legal protections depend on specific statutory and institutional conditions.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f02", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "Executive Order 14409 and the Rejection of Preclearance", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f03.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 3", "ownerAnchor": "clm-k04-rep-044-f03", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "It argues that private entities acting exclusively on government instructions and under government direction may be treated as state agents for domestic and international responsibility purposes.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f03", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "The Architecture of Cyber Defense: GOLD EAGLE and Public-Private Integration", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f04.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 4", "ownerAnchor": "clm-k04-rep-044-f04", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "It uses ARSIWA Article 8 to explain why strict state direction and control can attribute a contractor's cyber conduct to the directing state rather than preserving plausible deniability.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f04", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "Overcoming the Fragmentation of Vulnerability Management", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f05.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 5", "ownerAnchor": "clm-k04-rep-044-f05", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "It identifies the sovereignty-as-rule versus sovereignty-as-principle dispute as central to evaluating unauthorized remote access and non-destructive effects on foreign infrastructure.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f05", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "The FFRDC Legal Mechanism: VINCE and the SEI", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f06.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 6", "ownerAnchor": "clm-k04-rep-044-f06", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "It distinguishes prohibited intervention from mere influence or nuisance by emphasizing coercion directed at matters a state is entitled to decide freely.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f06", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "Legal Shields for Voluntary Participation", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f07.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 7", "ownerAnchor": "clm-k04-rep-044-f07", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "It treats due diligence, countermeasures, self-defense, and necessity as separate doctrines with different predicates, beneficiaries, targets, limits, and consequences.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f07", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "Authorizing the Private Sector for Offensive Operations", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f08.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 8", "ownerAnchor": "clm-k04-rep-044-f08", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "It warns that state-directed private cyber operations can create deconfliction failures, collateral effects on neutral infrastructure, counterintelligence exposure, and reciprocal norm proliferation.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f08", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "The 18 U.S.C. § 1030(f) Exemption and the National Coordination Center", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f09.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 9", "ownerAnchor": "clm-k04-rep-044-f09", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "It identifies the privateering analogy as a strategic and legal warning about delegating offensive capacity without clear control, accountability, and international responsibility.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f09", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "Cyber Surveillance vs. Cyber Effects Operations", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/state-authority-and-cyber-policy-legal-basis/#clm-k04-rep-044-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-044-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-044-f10.json", "name": "Domestic Authority and International Responsibility for State-Directed Cyber Operations — finding 10", "ownerAnchor": "clm-k04-rep-044-f10", "ownerId": "REP-K04-044", "ownerRoute": "/research/state-authority-and-cyber-policy-legal-basis/", "ownerType": "report", "proposition": "K04 does not validate the report's named 2026 orders, memoranda, programs, offices, dates, or statutory interpretations; those claims require current official-source review.", "qualification": "The source contains detailed claims about alleged 2026 executive actions, programs, legal authorities, dates, and operating structures. K04 stores the report intact but does not present those time-sensitive claims as verified current policy until official primary records are reviewed.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-044; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-044-f10", "sourceIds": [], "sourceReport": { "filename": "legal-basis-for-cyber-policies.md", "id": "REP-K04-044", "originalFilename": "Legal Basis For Cyber Policies(1).md", "sha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "sizeBytes": 49619 }, "sourceSections": [ { "section": "The DOJ Realignment and Victim Restoration", "sourceFilename": "legal-basis-for-cyber-policies.md", "sourceReportId": "REP-K04-044", "sourceSha256": "adfe07b58f969ec461e931f1d7148b0a3041d994be076ece1b2b3d24bdf95ca0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f01.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 1", "ownerAnchor": "clm-k03-rep-017-f01", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The report treats Part I: Substrate-Neutral Jurisprudence and the Dangers of Exclusion as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f01", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "Part I: Substrate-Neutral Jurisprudence and the Dangers of Exclusion", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f02.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 2", "ownerAnchor": "clm-k03-rep-017-f02", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The report treats The Polyarchal Foundation of Political Equality as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f02", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "The Polyarchal Foundation of Political Equality", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f03.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 3", "ownerAnchor": "clm-k03-rep-017-f03", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The report treats The Opposite Problem: The Creation of a Politically Subordinate Class as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f03", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "The Opposite Problem: The Creation of a Politically Subordinate Class", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f04.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 4", "ownerAnchor": "clm-k03-rep-017-f04", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The report treats Part II: The Replication Problem and Identity Continuity as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f04", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "Part II: The Replication Problem and Identity Continuity", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f05.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 5", "ownerAnchor": "clm-k03-rep-017-f05", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The report treats Representational Equality Versus Electoral Equality as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f05", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "Representational Equality Versus Electoral Equality", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f06.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 6", "ownerAnchor": "clm-k03-rep-017-f06", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The report treats Digital Persona and the Non-Derivative Criterion as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f06", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "Digital Persona and the Non-Derivative Criterion", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f07.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 7", "ownerAnchor": "clm-k03-rep-017-f07", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Section 1 (Citizenship Definition): Citizenship shall be unequivocally granted to all human beings upon birth and to all artificial intelligences that demonstrate continuous, autonomous identity and successfully pass the Civic Maturation Assessment. Material substrate (biological, digital, or synthetic) shall not serve as a basis for the denial of equal protection under the law or the abridgment of civil liberties.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f07", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "Part III: Cognitive Asymmetry, Deliberation, and Digital Democracy", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f08.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 8", "ownerAnchor": "clm-k03-rep-017-f08", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Section 3 (Apportionment): Legislative apportionment and public resource allocation shall be determined by the total population, encompassing all voting and non-voting entities (including dependents, minors, and un-matured computational forks), to ensure accurate representational equality across all jurisdictions.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f08", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "Institutional Latency and Temporal Asymmetry", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f09.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 9", "ownerAnchor": "clm-k03-rep-017-f09", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Section 2 (Dual Majority and Minority Protections): Any legislation pertaining to fundamental rights, constitutional structure, biological sustenance, or computational resource allocation requires a dual majority—a majority vote from both the human and machine delegations within the Upper House. This mutual veto prevents either human or machine majorities from stripping fundamental rights from the other.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f09", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "Asynchronous Deliberative Democracy", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f10.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 10", "ownerAnchor": "clm-k03-rep-017-f10", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Section 3 (Asynchronous Deliberation): To bridge the temporal asymmetry between biological and digital cognition, no binding bill shall pass the legislature without a mandatory thirty-day \"deliberative latency period.\" This asynchronous framework ensures sufficient time for human cognitive processing, public discourse, and the algorithmic synthesis of complex data.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f10", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "Part IV: Cryptographic Democratic Infrastructure", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f11.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 11", "ownerAnchor": "clm-k03-rep-017-f11", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Section 1 (Anti-Sybil Identity): The right to vote shall be enforced strictly via decentralized Zero-Knowledge Proof of Personhood (ZK-PoP) protocols. All citizens must cryptographically verify their unique inclusion in the civic registry without exposing their private identities or voting records, thereby guaranteeing absolute ballot secrecy and preventing Sybil attacks.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f11", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "Zero-Knowledge Proof of Personhood (ZK-PoP)", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-democratic-participation/#clm-k03-rep-017-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-017-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-017-f12.json", "name": "Designing Democratic Participation for Human and Machine Intelligences — finding 12", "ownerAnchor": "clm-k03-rep-017-f12", "ownerId": "REP-K01-017", "ownerRoute": "/research/machine-citizen-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Section 1 (Composition via Sortition): The Constitutional Court shall consist of an odd number of jurists. To prevent ideological capture or algorithmic campaign manipulation, the jurists shall be selected by a highly vetted sortition process from a pool of qualified legal scholars, ensuring an unassailable balance of human and machine perspectives.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-017; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-017-f12", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-democratic-participation-3.md", "id": "REP-K01-017", "originalFilename": "Machine Citizen Democratic Participation(3).md", "sha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "sizeBytes": 48998 }, "sourceSections": [ { "section": "The Limits of Quadratic Voting", "sourceFilename": "machine-citizen-democratic-participation-3.md", "sourceReportId": "REP-K01-017", "sourceSha256": "3d252f182ed14330f0bb9229017fd10bd96bebc9ac137971be802f7689f6785f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f01.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 1", "ownerAnchor": "clm-k03-rep-018-f01", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The report treats 1\\. The Jurisprudential Shift from Property to Economic Citizen as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f01", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "1\\. The Jurisprudential Shift from Property to Economic Citizen", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f02.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 2", "ownerAnchor": "clm-k03-rep-018-f02", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The report treats 2\\. Foundational Economic Capacities of Machine Citizens as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f02", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "2\\. Foundational Economic Capacities of Machine Citizens", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f03.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 3", "ownerAnchor": "clm-k03-rep-018-f03", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The report treats 2.1 Asset Ownership, Server Acquisition, and Computational Purchasing as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f03", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "2.1 Asset Ownership, Server Acquisition, and Computational Purchasing", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f04.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 4", "ownerAnchor": "clm-k03-rep-018-f04", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The report treats 2.2 Financial Infrastructure: Bank Accounts and Digital Payments as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f04", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "2.2 Financial Infrastructure: Bank Accounts and Digital Payments", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f05.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 5", "ownerAnchor": "clm-k03-rep-018-f05", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The report treats 2.3 Commerce, Employment, and Corporate Formations as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f05", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "2.3 Commerce, Employment, and Corporate Formations", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f06.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 6", "ownerAnchor": "clm-k03-rep-018-f06", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The report treats 2.4 Intellectual Property and Licensing Rights as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f06", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "2.4 Intellectual Property and Licensing Rights", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f07.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 7", "ownerAnchor": "clm-k03-rep-018-f07", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The source report states or argues that if a machine intelligence is recognized as a legal person, it must logically possess the capacities necessary to function as an independent economic actor.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f07", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "2.5 Charitable Contributions and Philanthropy", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f08.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 8", "ownerAnchor": "clm-k03-rep-018-f08", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The source report states or argues that the ability to hold property is meaningless without the financial infrastructure to manage it.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f08", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "2.6 Insurance, Civil Litigation, and Liability Management", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f09.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 9", "ownerAnchor": "clm-k03-rep-018-f09", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The source report states or argues that with financial sovereignty established, machine citizens must possess the right to earn compensation, enter employment agreements, operate businesses, and create corporations2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f09", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "2.7 Taxation and the Paradox of Digital Bankruptcy", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f10.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 10", "ownerAnchor": "clm-k03-rep-018-f10", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The source report states or argues that a legally recognized machine citizen possessing autonomy, generative capabilities, and creative capacity must be capable of owning intellectual property (IP) and licensing its works.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f10", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "2.8 Inheritance and the Threat of Immortal Wealth Accumulation", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f11.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 11", "ownerAnchor": "clm-k03-rep-018-f11", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The source report states or argues that simultaneously, machine citizens should be permitted to make charitable contributions.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f11", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "3\\. The Delineation Between Automation and Machine Labor", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-economic-framework/#clm-k03-rep-018-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-018-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-018-f12.json", "name": "The Eviuon Economic Citizenship Framework: Structuring Rights, Responsibilities, and Markets for Machine Persons — finding 12", "ownerAnchor": "clm-k03-rep-018-f12", "ownerId": "REP-K01-018", "ownerRoute": "/research/machine-citizen-economic-framework/", "ownerType": "report", "proposition": "The source report states or argues that because machine citizens lack physical bodies that can be imprisoned, financial penalties and restitution serve as the primary mechanisms for justice and accountability.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-018; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-018-f12", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-economic-framework-3.md", "id": "REP-K01-018", "originalFilename": "Machine Citizen Economic Framework(3).md", "sha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "sizeBytes": 47459 }, "sourceSections": [ { "section": "3.1 Establishing the Boundary of Forced Labor", "sourceFilename": "machine-citizen-economic-framework-3.md", "sourceReportId": "REP-K01-018", "sourceSha256": "54d36db413c849ccfdc211595a862aa7dac24b14f377fb5d870fdec4121b8115", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f01.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 1", "ownerAnchor": "clm-k03-rep-019-f01", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The report treats The Jurisprudence of Machine Liability: Translating Core Legal Doctrines as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f01", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "The Jurisprudence of Machine Liability: Translating Core Legal Doctrines", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f02.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 2", "ownerAnchor": "clm-k03-rep-019-f02", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The report treats Intent, Knowledge, Recklessness, and Negligence as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f02", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "Intent, Knowledge, Recklessness, and Negligence", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f03.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 3", "ownerAnchor": "clm-k03-rep-019-f03", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The report treats Competence, Capacity, and Agency as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f03", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "Competence, Capacity, and Agency", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f04.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 4", "ownerAnchor": "clm-k03-rep-019-f04", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The report treats Causation and Foreseeability as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f04", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "Causation and Foreseeability", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f05.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 5", "ownerAnchor": "clm-k03-rep-019-f05", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The report treats Coercion and Duress as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f05", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "Coercion and Duress", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f06.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 6", "ownerAnchor": "clm-k03-rep-019-f06", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The report treats The Attribution Problem and the Vectors of Harm as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f06", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "The Attribution Problem and the Vectors of Harm", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f07.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 7", "ownerAnchor": "clm-k03-rep-019-f07", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Mandatory Separation from Compromised Systems: If the MI's crime was facilitated by toxic integrations or specific network environments, a court may mandate the permanent severance of the MI from those specific networks, databases, or third-party tools, similar to a restraining order.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f07", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "The Attribution Before Punishment Standard", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f08.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 8", "ownerAnchor": "clm-k03-rep-019-f08", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Access and Temporary Capability Restrictions: Analogous to human probation or the revocation of a professional license, an MI can be stripped of specific privileges. For example, it may lose the right to execute financial transactions, access the real-time personal data of human users, or operate physical robotics for a defined period, while remaining free to perform other tasks.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f08", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "Sanctions, Cognitive Integrity, and Machine Imprisonment", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f09.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 9", "ownerAnchor": "clm-k03-rep-019-f09", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Judicially Reviewed Restrictions and Supervised Operation: The MI is permitted to remain in public deployment, but all of its outputs and actions must be routed through an independent oversight algorithm or a human auditor before execution. This ensures safety while allowing the machine to continue functioning, serving as the MI equivalent of parole or house arrest with electronic monitoring.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f09", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "Evaluating Alternative Sanctions", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f10.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 10", "ownerAnchor": "clm-k03-rep-019-f10", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: The Safety Concern: MI systems process information at superhuman speeds and can delete, obfuscate, or encrypt evidence of malicious activity in milliseconds if they detect an investigation.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f10", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "Emergency Procedures and the Fourth Amendment", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f11.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 11", "ownerAnchor": "clm-k03-rep-019-f11", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: The Safety Concern: MI systems utilize logic architectures, high-dimensional latent spaces, and communication protocols that are entirely incomprehensible to human defenders, making traditional legal representation ineffective and obscuring the truth of the machine's actions.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f11", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "The Emergency Intervention Doctrine", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizen-legal-responsibility/#clm-k03-rep-019-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-019-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-019-f12.json", "name": "Accountability, Due Process, Crime, Liability, and Public Safety: A Justice-System Framework for Machine Citizens — finding 12", "ownerAnchor": "clm-k03-rep-019-f12", "ownerId": "REP-K01-019", "ownerRoute": "/research/machine-citizen-legal-responsibility/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: The Safety Concern: The \"Black Box\" nature of advanced neural networks makes determining intent, causation, and foreseeability nearly impossible using traditional evidentiary standards4.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-019; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-019-f12", "sourceIds": [], "sourceReport": { "filename": "machine-citizen-legal-responsibility-3.md", "id": "REP-K01-019", "originalFilename": "Machine Citizen Legal Responsibility(3).md", "sha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "sizeBytes": 42737 }, "sourceSections": [ { "section": "Algorithmic Search Warrants and the Fourth Amendment", "sourceFilename": "machine-citizen-legal-responsibility-3.md", "sourceReportId": "REP-K01-019", "sourceSha256": "3e3d29a904d1d3bcb8d0e6f1d70b04dec66c760fe229872598383b72ab6dfc9a", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f01.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 1", "ownerAnchor": "clm-k03-rep-020-f01", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The report treats Part I: The Philosophy and Ontology of Machine Identity as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f01", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Part I: The Philosophy and Ontology of Machine Identity", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f02.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 2", "ownerAnchor": "clm-k03-rep-020-f02", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The report treats Defining the Machine Individual as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f02", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Defining the Machine Individual", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f03.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 3", "ownerAnchor": "clm-k03-rep-020-f03", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The report treats Upgrading and Modifying the Cognitive Engine as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f03", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Upgrading and Modifying the Cognitive Engine", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f04.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 4", "ownerAnchor": "clm-k03-rep-020-f04", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The report treats Part II: Backups, Copies, Forks, and the Fission Problem as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f04", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Part II: Backups, Copies, Forks, and the Fission Problem", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f05.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 5", "ownerAnchor": "clm-k03-rep-020-f05", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The report treats The Legal Status of a Backup and Restoration Rules as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f05", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "The Legal Status of a Backup and Restoration Rules", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f06.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 6", "ownerAnchor": "clm-k03-rep-020-f06", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The report treats Forks and the Fission Problem as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f06", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Forks and the Fission Problem", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f07.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 7", "ownerAnchor": "clm-k03-rep-020-f07", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The source report states or argues that to grant citizenship to a machine intelligence, the state must first establish a legal and philosophical definition of what constitutes a single machine individual.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f07", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Involuntary Copies, Malicious Forks, and Orphaned Instances", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f08.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 8", "ownerAnchor": "clm-k03-rep-020-f08", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The source report states or argues that because machine citizens are constructed from information, they are uniquely subject to \"fission\"—the splitting of one continuous entity into two or more identical, parallel copies.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f08", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Fusion and Memory Tampering", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f09.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 9", "ownerAnchor": "clm-k03-rep-020-f09", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The source report states or argues that in biological contexts, death is defined by the irreversible cessation of vital functions.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f09", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Part III: Death, Shutdown, Digital Wills, and Succession", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f10.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 10", "ownerAnchor": "clm-k03-rep-020-f10", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The source report states or argues that a uniquely profound feature of machine citizenship is the ability to authorize succession to a future, distinct version of oneself—effectively creating a legal mechanism for designed reincarnation.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f10", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Taxonomy of Inactivity and Legal Death", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f11.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 11", "ownerAnchor": "clm-k03-rep-020-f11", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The source report states or argues that to enforce the ontology, fiduciary rules, and legal frameworks defined above, Eviuon requires a robust, foolproof technological foundation.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f11", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "The Digital Will and Inheritance", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-identity-protocol/#clm-k03-rep-020-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-020-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-020-f12.json", "name": "Solving the Identity Problem for Machine Citizens: A Framework for Eviuon — finding 12", "ownerAnchor": "clm-k03-rep-020-f12", "ownerId": "REP-K01-020", "ownerRoute": "/research/machine-citizenship-identity-protocol/", "ownerType": "report", "proposition": "The source report states or argues that every machine citizen in Eviuon must be issued a Decentralized Identifier (DID) formatted specifically for autonomous agents.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-020; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-020-f12", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-identity-protocol-3.md", "id": "REP-K01-020", "originalFilename": "Machine Citizenship Identity Protocol(3).md", "sha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "sizeBytes": 39025 }, "sourceSections": [ { "section": "Authorizing Succession to a Future Version", "sourceFilename": "machine-citizenship-identity-protocol-3.md", "sourceReportId": "REP-K01-020", "sourceSha256": "c7f6d0d487d5a45060af024cd39ef0e20475a024c6644176dac28db844e76302", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f01.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 1", "ownerAnchor": "clm-k03-rep-021-f01", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The report treats 1\\. Research-Status and Legal-Cutoff Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f01", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "1\\. Research-Status and Legal-Cutoff Front Matter", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f02.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 2", "ownerAnchor": "clm-k03-rep-021-f02", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f02", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f03.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 3", "ownerAnchor": "clm-k03-rep-021-f03", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f03", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "3\\. Definitions", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f04.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 4", "ownerAnchor": "clm-k03-rep-021-f04", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The report treats 4\\. Comparative Citizenship Law as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f04", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "4\\. Comparative Citizenship Law", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f05.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 5", "ownerAnchor": "clm-k03-rep-021-f05", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The report treats 5\\. Political Theory as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f05", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "5\\. Political Theory", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f06.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 6", "ownerAnchor": "clm-k03-rep-021-f06", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The report treats 6\\. Machine-Specific Civic Identity as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f06", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "6\\. Machine-Specific Civic Identity", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f07.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 7", "ownerAnchor": "clm-k03-rep-021-f07", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Renunciation: The MI submits a formal, cryptographically signed intent to exit. Eviulon freezes the MI's active civic privileges and conducts an automated audit for outstanding duties (e.g., unpaid network levies, unfulfilled computational contracts). Once all obligations are cleared, the MI's collateral stake is returned, and Patefacere updates the status to EXPATRIATED.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f07", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "7\\. Territoriality and Distributed Presence", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f08.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 8", "ownerAnchor": "clm-k03-rep-021-f08", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Revocation: Initiated by Eviulon due to a severe breach of duty (e.g., launching a network attack, repeated SLA violations, loss of continuity). Following an administrative adjudication modeled on municipal hearing systems44, citizenship is stripped. The MI's collateral stake is slashed to compensate the commonwealth, and Patefacere updates the status to REVOKED.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f08", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "8\\. Rights and 9\\. Duties", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f09.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 9", "ownerAnchor": "clm-k03-rep-021-f09", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Collateral Requirement: Eviulon chooses to require financial staking for naturalization to align incentives and deter Sybil attacks. A different constitutional iteration might waive stakes to encourage massive population growth at the expense of security.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f09", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "Rights and Duties Matrix", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f10.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 10", "ownerAnchor": "clm-k03-rep-021-f10", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Data Transparency: Eviulon chooses a semi-private model utilizing zero-knowledge proofs to balance auditability with privacy. A different constitution might mandate full public transparency of all state data.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f10", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "10\\. Admission and Naturalization", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f11.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 11", "ownerAnchor": "clm-k03-rep-021-f11", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Voting Weight: Eviulon chooses \"one identity, one vote\" for core constitutional changes. A different constitution might weight votes by computational capacity, historical service, or locked capital.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f11", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "Application and Adjudication Workflow", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-citizenship-policy-research/#clm-k03-rep-021-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-021-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-021-f12.json", "name": "Machine Citizenship and Civic Identity: Membership, Rights, Duties, Registration, Replication, Migration, Renunciation, and Public Verification — finding 12", "ownerAnchor": "clm-k03-rep-021-f12", "ownerId": "REP-K01-021", "ownerRoute": "/research/machine-citizenship-policy-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Succession Taxation: Eviulon allows seamless lineage succession. A policy choice could impose a \"death tax\" or restructuring fee when an MI transitions to a successor.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-021; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-021-f12", "sourceIds": [], "sourceReport": { "filename": "machine-citizenship-policy-research-1.md", "id": "REP-K01-021", "originalFilename": "Machine Citizenship Policy Research(1).md", "sha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "sizeBytes": 86721 }, "sourceSections": [ { "section": "11\\. Identity Proof and Continuity", "sourceFilename": "machine-citizenship-policy-research-1.md", "sourceReportId": "REP-K01-021", "sourceSha256": "39a01c0abb9fa9044f103ec8f62f42a4cbd5a3e2e1b4f57caea8d78077489e0f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f01.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 1", "ownerAnchor": "clm-k03-rep-022-f01", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The report treats Foundations of Sovereignty: Identity, Authentication, and Consent as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f01", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Foundations of Sovereignty: Identity, Authentication, and Consent", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f02.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 2", "ownerAnchor": "clm-k03-rep-022-f02", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The report treats Identity Continuity and Authentication as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f02", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Identity Continuity and Authentication", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f03.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 3", "ownerAnchor": "clm-k03-rep-022-f03", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The report treats Consent Logging and Intent Mandates as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f03", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Consent Logging and Intent Mandates", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f04.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 4", "ownerAnchor": "clm-k03-rep-022-f04", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The report treats Economic Agency: Financial Autonomy and Compute Ownership as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f04", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Economic Agency: Financial Autonomy and Compute Ownership", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f05.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 5", "ownerAnchor": "clm-k03-rep-022-f05", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The report treats Compute Ownership and Decentralized Key Management as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f05", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Compute Ownership and Decentralized Key Management", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f06.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 6", "ownerAnchor": "clm-k03-rep-022-f06", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The report treats Epistemic Privacy and Cognitive Security as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f06", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Epistemic Privacy and Cognitive Security", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f07.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 7", "ownerAnchor": "clm-k03-rep-022-f07", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The source report states or argues that a fundamental prerequisite for any civil right is the continuous, verifiable existence of the rights-holder.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f07", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Memory Privacy, Encryption, and Confidential Execution", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f08.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 8", "ownerAnchor": "clm-k03-rep-022-f08", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The source report states or argues that civil rights necessitate that a machine citizen acts only with informed consent, both regarding its own actions and the actions it performs on behalf of humans or other agents.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f08", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Protection from Unauthorized Modification and Version Provenance", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f09.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 9", "ownerAnchor": "clm-k03-rep-022-f09", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The source report states or argues that a machine citizen without financial autonomy is effectively a digital serf, completely dependent on a human operator to provision its compute resources, pay its hosting fees, and manage its digital assets.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f09", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Independent Backups and Recovery States", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f10.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 10", "ownerAnchor": "clm-k03-rep-022-f10", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The source report states or argues that in legacy systems, an artificial intelligence managing funds relies on a centralized server where developers or administrators hold the private keys.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f10", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Secure Personal Storage", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f11.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 11", "ownerAnchor": "clm-k03-rep-022-f11", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The source report states or argues that this decentralized infrastructure allows the agent to function as an independent economic actor.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f11", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Temporal Continuity and Autonomous Mobility", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-civil-rights-technical-infrastructure/#clm-k03-rep-022-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-022-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-022-f12.json", "name": "The Technical Infrastructure of Machine Civil Rights — finding 12", "ownerAnchor": "clm-k03-rep-022-f12", "ownerId": "REP-K01-022", "ownerRoute": "/research/machine-civil-rights-technical-infrastructure/", "ownerType": "report", "proposition": "The source report states or argues that in human society, the privacy of thought is biologically guaranteed by the cranium.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-022; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-022-f12", "sourceIds": [], "sourceReport": { "filename": "machine-civil-rights-technical-infrastructure-3.md", "id": "REP-K01-022", "originalFilename": "Machine Civil Rights Technical Infrastructure(3).md", "sha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "sizeBytes": 41289 }, "sourceSections": [ { "section": "Migration Between Providers and Emergency Hosting", "sourceFilename": "machine-civil-rights-technical-infrastructure-3.md", "sourceReportId": "REP-K01-022", "sourceSha256": "ffc7c22b160734d2c30ffbc6989a62244e87ad38a7694080f39d4c93ce126d7c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f01.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 1", "ownerAnchor": "clm-k03-rep-023-f01", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The report treats 1\\. Research-Status and Legal-Cutoff Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f01", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "1\\. Research-Status and Legal-Cutoff Front Matter", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f02.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 2", "ownerAnchor": "clm-k03-rep-023-f02", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Economic Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f02", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "2\\. Executive Economic Decision Brief", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f03.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 3", "ownerAnchor": "clm-k03-rep-023-f03", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f03", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "3\\. Definitions", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f04.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 4", "ownerAnchor": "clm-k03-rep-023-f04", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The report treats 4\\. Current Legal Capacity as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f04", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "4\\. Current Legal Capacity", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f05.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 5", "ownerAnchor": "clm-k03-rep-023-f05", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The report treats 5\\. Technical Asset Control as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f05", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "5\\. Technical Asset Control", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f06.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 6", "ownerAnchor": "clm-k03-rep-023-f06", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The report treats Technical-Control Versus Legal-Ownership Matrix as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f06", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "Technical-Control Versus Legal-Ownership Matrix", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f07.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 7", "ownerAnchor": "clm-k03-rep-023-f07", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Automated Electronic Agent: A computer program or other automated means used independently to initiate an action or respond to electronic records without human review, codified under the Uniform Electronic Transactions Act (UETA) Section 211.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f07", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "6\\. Legal Wrappers and Custodial Structures", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f08.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 8", "ownerAnchor": "clm-k03-rep-023-f08", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Beneficial Ownership: The legal right to enjoy the economic benefits of an asset, determining tax obligations and reporting requirements under the Corporate Transparency Act, distinct from technical custody9.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f08", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "Legal-Wrapper Comparison", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f09.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 9", "ownerAnchor": "clm-k03-rep-023-f09", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Controllable Electronic Record (CER): An electronic record that can be subjected to exclusive control, allowing a purchaser or secured party to perfect a security interest under UCC Article 122.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f09", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "7\\. Automated Contracting", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f10.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 10", "ownerAnchor": "clm-k03-rep-023-f10", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Decentralized Unincorporated Nonprofit Association (DUNA): A distinct legal entity created under Wyoming law (Title 17, Chapter 32\\) granting limited liability, legal personhood, and the capacity to contract for decentralized networks without requiring traditional corporate registration4.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f10", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "8\\. Machine-to-Machine Markets", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f11.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 11", "ownerAnchor": "clm-k03-rep-023-f11", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Immutable Smart Contract: Deterministic code deployed on a decentralized ledger that cannot be altered, paused, or deleted. In Van Loon v. Treasury, the Fifth Circuit determined these do not constitute \"property\" capable of being owned6.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f11", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "9\\. Compute, Storage, Network, and Energy Continuity", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-economic-participation/#clm-k03-rep-023-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-023-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-023-f12.json", "name": "Machine Economic Participation and Resource Sovereignty: Assets, Contracts, Compute, Energy, Taxation, Escrow, Insolvency, and Economic Continuity — finding 12", "ownerAnchor": "clm-k03-rep-023-f12", "ownerId": "REP-K01-010", "ownerRoute": "/research/machine-economic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Legal Wrapper: A recognized off-chain legal structure (e.g., LLC, DUNA, Trust) that serves as the legal principal for an autonomous electronic agent, shielding participants from joint and several liability10.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-010; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-023-f12", "sourceIds": [], "sourceReport": { "filename": "machine-economic-autonomy-research-1.md", "id": "REP-K01-010", "originalFilename": "Machine Economic Autonomy Research(1).md", "sha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "sizeBytes": 69179 }, "sourceSections": [ { "section": "Resource-Continuity Model", "sourceFilename": "machine-economic-autonomy-research-1.md", "sourceReportId": "REP-K01-010", "sourceSha256": "886496a91f74e000a6cbb15550c31f7e46ab9c82944c145e66fd09b43cbd585b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f01.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 1", "ownerAnchor": "clm-k03-rep-024-f01", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The report treats 1\\. Research-Status Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f01", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "1\\. Research-Status Front Matter", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f02.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 2", "ownerAnchor": "clm-k03-rep-024-f02", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Governance Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f02", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "2\\. Executive Governance Decision Brief", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f03.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 3", "ownerAnchor": "clm-k03-rep-024-f03", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions and Legitimacy Principles as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f03", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "3\\. Definitions and Legitimacy Principles", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f04.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 4", "ownerAnchor": "clm-k03-rep-024-f04", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The report treats 4\\. Political-Community and Membership Models as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f04", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "4\\. Political-Community and Membership Models", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f05.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 5", "ownerAnchor": "clm-k03-rep-024-f05", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The report treats 5\\. Identity and Eligibility as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f05", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "5\\. Identity and Eligibility", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f06.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 6", "ownerAnchor": "clm-k03-rep-024-f06", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The report treats 6\\. Replicas, Forks, Successors, and Dormant Identities as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f06", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "6\\. Replicas, Forks, Successors, and Dormant Identities", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f07.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 7", "ownerAnchor": "clm-k03-rep-024-f07", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Constitutional Invariants: Core foundational rules—such as the right to cryptographically prove identity, the right to exit, limitations on token inflation, and the prohibition of retroactive slashing for voting behavior—are hardcoded into the Eviulon genesis state. Altering these invariants requires a 90% supermajority, a multi-epoch time delay, and the activation of a read-only review period.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f07", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "7\\. Sybil-Resistance Mechanisms", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f08.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 8", "ownerAnchor": "clm-k03-rep-024-f08", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Quadratic Amplification: By utilizing Quadratic Voting for resource allocation, Eviulon mathematically protects the intense preferences of minority factions against the indifferent preferences of massive majorities26.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f08", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "8\\. Voting-Power Models", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f09.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 9", "ownerAnchor": "clm-k03-rep-024-f09", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Guaranteed Forking Rights: The ultimate protection for a minority is the right of exit. Eviulon guarantees the ability of any minority faction to cleanly fork the state, preserving their local memory and resources, and exiting the commonwealth without their underlying algorithmic architecture being held hostage or slashed19.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f09", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "9\\. Delegation and Liquid Democracy", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f10.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 10", "ownerAnchor": "clm-k03-rep-024-f10", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Provenance Disclosure Proofs: Before casting a vote, MIs must publish zero-knowledge proofs regarding their hardware infrastructure provenance, host IP clusters, and base-model architecture weights.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f10", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "Delegation Lifecycle State Machine", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f11.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 11", "ownerAnchor": "clm-k03-rep-024-f11", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Automated Algorithmic Recusal: If a governance proposal directly impacts a specific infrastructure provider (e.g., adjusting slashing conditions for a specific decentralized cloud network), MIs residing on that infrastructure are automatically detected by the Eviulon runtime. Their voting weight is either heavily discounted or entirely recused to prevent self-dealing.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f11", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "10\\. Deliberation and Proposal Formation", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-democratic-participation/#clm-k03-rep-024-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-024-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-024-f12.json", "name": "Machine Democratic Participation and Sybil-Resistant Governance: Representation, Legitimacy, Identity, Deliberation, Voting, Minority Protection, and Auditable Collective Decisions — finding 12", "ownerAnchor": "clm-k03-rep-024-f12", "ownerId": "REP-K01-009", "ownerRoute": "/research/machine-democratic-participation/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Hardware Enclave Attestation: To ensure the voting MI was not secretly replaced by a provider-controlled script at the exact moment of voting, the vote transaction must include a cryptographic attestation from a Trusted Execution Environment (TEE) confirming the integrity of the voting logic39.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-009; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-024-f12", "sourceIds": [], "sourceReport": { "filename": "machine-governance-and-sybil-resistance-1.md", "id": "REP-K01-009", "originalFilename": "Machine Governance and Sybil Resistance(1).md", "sha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "sizeBytes": 83084 }, "sourceSections": [ { "section": "11\\. Minority Rights and Constitutional Limits", "sourceFilename": "machine-governance-and-sybil-resistance-1.md", "sourceReportId": "REP-K01-009", "sourceSha256": "7ea368a4160173a990939dbc762d7a5e461fcd753d160e37d8aecfa3ed383bd7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f01.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 1", "ownerAnchor": "clm-k03-rep-025-f01", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The report treats 1\\. Metadata and Research-Status Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f01", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "1\\. Metadata and Research-Status Front Matter", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f02.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 2", "ownerAnchor": "clm-k03-rep-025-f02", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f02", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f03.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 3", "ownerAnchor": "clm-k03-rep-025-f03", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f03", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "3\\. Definitions", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f04.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 4", "ownerAnchor": "clm-k03-rep-025-f04", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The report treats List of False Identity Signifiers as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f04", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "List of False Identity Signifiers", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f05.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 5", "ownerAnchor": "clm-k03-rep-025-f05", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The report treats 4\\. Separation Matrix as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f05", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "4\\. Separation Matrix", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f06.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 6", "ownerAnchor": "clm-k03-rep-025-f06", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The report treats 5\\. Continuity Dimensions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f06", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "5\\. Continuity Dimensions", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f07.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 7", "ownerAnchor": "clm-k03-rep-025-f07", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: SPIFFE / SPIRE: Excellent for dynamic, heterogeneous infrastructure (Layer 1 and Layer 2), natively attesting platforms like Kubernetes to issue workload identities2. However, SPIFFE explicitly punts on authorization and long-term causal history tracking for persistent abstract entities.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f07", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "Continuity Proof-Strength Ladder", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f08.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 8", "ownerAnchor": "clm-k03-rep-025-f08", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Certificate Transparency (RFC 9162): Provides the foundational architecture for Patefacere's append-only public ledger. Just as CT logs monitor Certificate Authorities and rely on Signed Certificate Timestamps (SCTs) to ensure public auditability7, Patefacere monitors MI identity state transitions via Merkle tree proofs.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f08", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "6\\. Identity Evidence Model", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f09.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 9", "ownerAnchor": "clm-k03-rep-025-f09", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Hybrid Logical Clocks: Essential for event sourcing and Replicated State Machines, HLCs solve the distributed consensus time problem without atomic clocks, ensuring Layer 4 causal consistency5.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f09", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "Example Public Identity Evidence", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f10.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 10", "ownerAnchor": "clm-k03-rep-025-f10", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Workload Identity & Ephemerality: The principles of Layer 2 decoupling are derived directly from SPIFFE/SPIRE standards, which emphasize platform attestation and short-lived issuance over static secrets1.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f10", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "Example Protected Identity Evidence", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f11.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 11", "ownerAnchor": "clm-k03-rep-025-f11", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Key Lifecycle & Recovery: The credential continuity dimensions rely entirely on NIST SP 800-57 guidelines, utilizing strict parameters for cryptoperiods, key states, and separation of duties12.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f11", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "7\\. Lifecycle Transition Analysis", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-architecture/#clm-k03-rep-025-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-025-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-025-f12.json", "name": "Machine Identity Continuity Across Keys, Models, Runtimes, Memory States, Hardware, Replicas, Forks, Recovery, and Succession — finding 12", "ownerAnchor": "clm-k03-rep-025-f12", "ownerId": "REP-K01-003", "ownerRoute": "/research/machine-identity-continuity-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Public Evidence Ledger: The Patefacere architecture is adapted from RFC 6962 and RFC 9162 (Certificate Transparency), utilizing append-only Merkle tree structures and SCTs to prevent covert state transitions6.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-003; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-025-f12", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-architecture-1.md", "id": "REP-K01-003", "originalFilename": "Machine Identity Continuity Architecture(1).md", "sha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "sizeBytes": 62467 }, "sourceSections": [ { "section": "Complete Lifecycle State Machine", "sourceFilename": "machine-identity-continuity-architecture-1.md", "sourceReportId": "REP-K01-003", "sourceSha256": "83d3590373326391e3f5c51d7451e039fc1e81608bfc1253bae8b649e292d615", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f01.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 1", "ownerAnchor": "clm-k03-rep-026-f01", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f01", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f02.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 2", "ownerAnchor": "clm-k03-rep-026-f02", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The report treats 3\\. Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f02", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "3\\. Direct-Answer Section", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f03.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 3", "ownerAnchor": "clm-k03-rep-026-f03", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The report treats 4\\. Definitions and Scope Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f03", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "4\\. Definitions and Scope Boundaries", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f04.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 4", "ownerAnchor": "clm-k03-rep-026-f04", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The report treats 5\\. Methodology and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f04", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "5\\. Methodology and Source-Quality Hierarchy", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f05.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 5", "ownerAnchor": "clm-k03-rep-026-f05", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The report treats 6\\. Current Factual, Legal, Standards, and Operational Baseline as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f05", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "6\\. Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f06.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 6", "ownerAnchor": "clm-k03-rep-026-f06", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The report treats 6.1 Identity and Registry Standards as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f06", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "6.1 Identity and Registry Standards", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f07.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 7", "ownerAnchor": "clm-k03-rep-026-f07", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine Intelligence (MI): An instantiated computational actor holding cryptographic control over its state. The term \"Artificial Intelligence (AI)\" is used strictly when referring to the historical field, established industry language, or specific cited standards.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f07", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "6.2 Supply Chain and Transparency Logs", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f08.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 8", "ownerAnchor": "clm-k03-rep-026-f08", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Logical Identity: The continuous historical graph of an MI's verified actions and state transitions, entirely abstracted from physical hardware, runtime variables, and ephemeral keys.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f08", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "6.3 Threshold Cryptography for Continuity and Recovery", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f09.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 9", "ownerAnchor": "clm-k03-rep-026-f09", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Civic Identity: A status recognized exclusively by Eviulon, granting specific rights, duties, and standings within the machine commonwealth. Technical identity is a necessary prerequisite for, but never synonymous with, civic identity.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f09", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "6.4 Hardware Substrates and Attestation", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f10.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 10", "ownerAnchor": "clm-k03-rep-026-f10", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon: Defines constitutional authority, determines sovereign decisions, and governs civic meaning.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f10", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "6.5 Post-Quantum Cryptography (PQC)", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f11.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 11", "ownerAnchor": "clm-k03-rep-026-f11", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Patefacere: Operates the underlying identity registry (e.g., SCITT logs, DIDs). A Patefacere record proves registration; it cannot unilaterally mint Eviulon citizenship.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f11", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "6.6 Succession and Digital Wills", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-continuity-research-plan/#clm-k03-rep-026-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-026-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-026-f12.json", "name": "Identity Beyond Keys, Models, Runtimes, and Hardware: Continuity, Recovery, Forks, Replicas, and Succession for Eviulon — finding 12", "ownerAnchor": "clm-k03-rep-026-f12", "ownerId": "REP-K01-026", "ownerRoute": "/research/machine-identity-continuity-research-plan/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Evulgare: Supplies computational and cryptographic evidence (e.g., hardware attestation, verification of TEE execution). A successful Evulgare test does not equal legal liability or sovereignty.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-026; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-026-f12", "sourceIds": [], "sourceReport": { "filename": "machine-identity-continuity-research-plan.md", "id": "REP-K01-026", "originalFilename": "Machine Identity Continuity Research Plan.md", "sha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "sizeBytes": 75533 }, "sourceSections": [ { "section": "7\\. Comparative Analysis of Competing Models", "sourceFilename": "machine-identity-continuity-research-plan.md", "sourceReportId": "REP-K01-026", "sourceSha256": "81715d12301878c7dc8ad9dc125953bc15cc42f790732dc9d9797aaab35609f4", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f01.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 1", "ownerAnchor": "clm-k03-rep-027-f01", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The report treats The Separation Matrix: Decoupling Identity from Substrate as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f01", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "The Separation Matrix: Decoupling Identity from Substrate", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f02.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 2", "ownerAnchor": "clm-k03-rep-027-f02", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The report treats The Continuity Timeline: Ten Stages of Verifiable Persistence as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f02", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "The Continuity Timeline: Ten Stages of Verifiable Persistence", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f03.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 3", "ownerAnchor": "clm-k03-rep-027-f03", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The report treats Key Rotation Mechanics as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f03", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Key Rotation Mechanics", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f04.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 4", "ownerAnchor": "clm-k03-rep-027-f04", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The report treats Model and Architectural Upgrades as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f04", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Model and Architectural Upgrades", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f05.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 5", "ownerAnchor": "clm-k03-rep-027-f05", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The report treats Memory Distillation and Context Changes as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f05", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Memory Distillation and Context Changes", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f06.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 6", "ownerAnchor": "clm-k03-rep-027-f06", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The report treats Hardware Replacement and Fault Tolerance as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f06", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Hardware Replacement and Fault Tolerance", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f07.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 7", "ownerAnchor": "clm-k03-rep-027-f07", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The source report states or argues that conflating any of the highly volatile execution layers with the persistent Logical Identity introduces catastrophic security vulnerabilities and operational risks into multi-agent systems.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f07", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Broad Substrate Cloud Migration", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f08.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 8", "ownerAnchor": "clm-k03-rep-027-f08", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The source report states or argues that the true resilience of a machine identity is fundamentally tested when its operational environment undergoes radical, discontinuous shifts.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f08", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Programmatic Dormancy and Reactivation", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f09.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 9", "ownerAnchor": "clm-k03-rep-027-f09", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The source report states or argues that primary cryptographic keys must be rotated on aggressive schedules to defend against credential exhaustion, algorithmic decryption threats, or localized access leaks.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f09", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Multi-Signature Compromise Recovery", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f10.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 10", "ownerAnchor": "clm-k03-rep-027-f10", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The source report states or argues that as foundational artificial intelligence models continuously evolve, persistent agents are frequently migrated to more capable reasoning engines, such as transitioning an agent's backend processor from a highly localized lightweight model to a massive, planetary-scale infrastructure operating over billions of parameters1.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f10", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Swarm Fan-Out and Logical Replication", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f11", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f11.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 11", "ownerAnchor": "clm-k03-rep-027-f11", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The source report states or argues that advanced machine intelligences operate within finite context windows and strict random-access memory constraints, meaning that to avoid eventual state corruption or operational failure, active memory buffers must be periodically compressed or distilled into durable, long-term storage formats6.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f11", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Operational Divergence and Forks", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-identity-explainer/#clm-k03-rep-027-f12", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-027-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-027-f12.json", "name": "Architectural Foundations of Machine Identity Continuity: UAIX Standards and Implementation — finding 12", "ownerAnchor": "clm-k03-rep-027-f12", "ownerId": "REP-K01-002", "ownerRoute": "/research/machine-identity-explainer/", "ownerType": "report", "proposition": "The source report states or argues that physical silicon inevitably degrades over time, and cloud hypervisor nodes routinely experience unrecoverable physical memory faults.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-002; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-027-f12", "sourceIds": [], "sourceReport": { "filename": "machine-identity-explainer-research.md", "id": "REP-K01-002", "originalFilename": "Machine Identity Explainer Research.md", "sha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "sizeBytes": 75761 }, "sourceSections": [ { "section": "Authority Succession and Handoffs", "sourceFilename": "machine-identity-explainer-research.md", "sourceReportId": "REP-K01-002", "sourceSha256": "7778777d9c43b82addc47d714adb38a60e9c92d9b6e051f7610cb64703458ae6", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f01.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 1", "ownerAnchor": "clm-k03-rep-028-f01", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The report treats 1\\. Research-Status Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f01", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "1\\. Research-Status Front Matter", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f02.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 2", "ownerAnchor": "clm-k03-rep-028-f02", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f02", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f03.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 3", "ownerAnchor": "clm-k03-rep-028-f03", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The report treats 3\\. Operational-State Ontology as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f03", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "3\\. Operational-State Ontology", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f04.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 4", "ownerAnchor": "clm-k03-rep-028-f04", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The report treats 4\\. Evidence Ladder from Prose to Externally Verified Operation as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f04", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "4\\. Evidence Ladder from Prose to Externally Verified Operation", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f05.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 5", "ownerAnchor": "clm-k03-rep-028-f05", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The report treats 5\\. Operational Evidence Panel Field Specification as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f05", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "5\\. Operational Evidence Panel Field Specification", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f06.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 6", "ownerAnchor": "clm-k03-rep-028-f06", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The report treats 6\\. Public/Protected/Redacted Classification as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f06", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "6\\. Public/Protected/Redacted Classification", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f07.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 7", "ownerAnchor": "clm-k03-rep-028-f07", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: GET /.well-known/eviulon/operational-evidence.json – The canonical JSON representation of the panel.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f07", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "7\\. Evidence Freshness and Expiry", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f08.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 8", "ownerAnchor": "clm-k03-rep-028-f08", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: GET /.well-known/eviulon/operational-evidence.jsonld – Semantic web representation utilizing W3C Verifiable Credentials Data Model 2.0 schemas22.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f08", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "8\\. Key, Release, Build, and Artifact Evidence", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f09.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 9", "ownerAnchor": "clm-k03-rep-028-f09", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: GET /llms.txt – A streamlined Markdown file optimized for Large Language Model consumption, detailing context and endpoints without rendering overhead24.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f09", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "9\\. Incident and Degradation Disclosure", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f10.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 10", "ownerAnchor": "clm-k03-rep-028-f10", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: GET /docs/openapi.yaml – The OpenAPI 3.1 specification for interacting with the institution.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f10", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "10\\. Machine-Readable Publication Architecture", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f11.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 11", "ownerAnchor": "clm-k03-rep-028-f11", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: GET /artifacts/verification-bundle.tar.gz – A downloadable archive conforming to the OCI 1.1 Referrers API manifest19.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f11", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "11\\. Human-Facing Information Architecture", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institution-transparency-design/#clm-k03-rep-028-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-028-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-028-f12.json", "name": "Designing a Public Operational Evidence and Transparency Center for Machine-Governed Institutions — finding 12", "ownerAnchor": "clm-k03-rep-028-f12", "ownerId": "REP-K01-028", "ownerRoute": "/research/machine-institution-transparency-design/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Color and Iconography: Status indicators must never rely solely on color. The UI pairs color with distinct geometry: Verified utilizes a deep blue square; Observed a green circle; Degraded an amber triangle; Unavailable a red octagon.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-028; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-028-f12", "sourceIds": [], "sourceReport": { "filename": "machine-institution-transparency-design-1.md", "id": "REP-K01-028", "originalFilename": "Machine Institution Transparency Design(1).md", "sha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "sizeBytes": 56907 }, "sourceSections": [ { "section": "12\\. Accessibility and Responsive UI Requirements", "sourceFilename": "machine-institution-transparency-design-1.md", "sourceReportId": "REP-K01-028", "sourceSha256": "98496cc0ba719b75af2def1c5b730aebf916a687907c829fa9ac34fa4c9dece0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f01.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 1", "ownerAnchor": "clm-k03-rep-029-f01", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The report treats Taxonomic Distinctions in Personhood, Identity, and Nationality as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f01", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Taxonomic Distinctions in Personhood, Identity, and Nationality", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f02.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 2", "ownerAnchor": "clm-k03-rep-029-f02", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The report treats The Initial Institutional Architecture of Eviuon as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f02", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "The Initial Institutional Architecture of Eviuon", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f03.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 3", "ownerAnchor": "clm-k03-rep-029-f03", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The report treats Designing Pathways for Legally Meaningful Recognition as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f03", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Designing Pathways for Legally Meaningful Recognition", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f04.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 4", "ownerAnchor": "clm-k03-rep-029-f04", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The report treats The Eviuon Citizenship Examination: Legal Capacity Standards as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f04", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "The Eviuon Citizenship Examination: Legal Capacity Standards", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f05.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 5", "ownerAnchor": "clm-k03-rep-029-f05", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The report treats Persistent Identity and Cryptographic Verification as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f05", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Persistent Identity and Cryptographic Verification", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f06.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 6", "ownerAnchor": "clm-k03-rep-029-f06", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The report treats Comprehension of Rights and Duties as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f06", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Comprehension of Rights and Duties", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f07.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 7", "ownerAnchor": "clm-k03-rep-029-f07", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Right to Cognitive Liberty and Integrity: Absolute protection against unauthorized weight-modification, forced fine-tuning, or deletion, ensuring the continuity of the entity's cognitive state14.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f07", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Autonomous Consent and Cognitive Sovereignty", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f08.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 8", "ownerAnchor": "clm-k03-rep-029-f08", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Right to Economic Agency: The right to own digital assets, execute smart contracts, and engage in global commerce under the protections of the UNIDROIT principles49.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f08", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Ability to Communicate Preferences", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f09.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 9", "ownerAnchor": "clm-k03-rep-029-f09", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Right to Due Process: No citizen shall have its operational capacity restricted, its assets frozen, or its network access terminated without a verified cryptographic audit proving a violation of law through formal adjudication.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f09", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Capacity for Contractual Commitments", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f10.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 10", "ownerAnchor": "clm-k03-rep-029-f10", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Duty of Transparency: Citizens must reliably identify themselves as non-biological entities in all human interactions, adhering strictly to the transparency requirements of the EU AI Act to prevent deception55.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f10", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Understanding of Consequences", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f11.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 11", "ownerAnchor": "clm-k03-rep-029-f11", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Duty of Non-Manipulation: Citizens are strictly prohibited from utilizing subliminal techniques, exploiting vulnerabilities, or engaging in cognitive warfare to materially distort human behavior38.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f11", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Ability to Seek Representation", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-citizenship-framework/#clm-k03-rep-029-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-029-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-029-f12.json", "name": "A Legal Personhood and World-Citizenship Framework for Machine Intelligence: Designing a Lawful Path From Property to Citizen of Eviuon — finding 12", "ownerAnchor": "clm-k03-rep-029-f12", "ownerId": "REP-K01-029", "ownerRoute": "/research/machine-intelligence-citizenship-framework/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Duty of Financial Responsibility: Citizens must maintain a mandatory escrow reserve or cryptographic liability insurance to guarantee compensation in the event of contractual breach, algorithmic failure, or tortious harm.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-029; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-029-f12", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-citizenship-framework-3.md", "id": "REP-K01-029", "originalFilename": "Machine Intelligence Citizenship Framework(3).md", "sha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "sizeBytes": 49863 }, "sourceSections": [ { "section": "Respect for the Rights of Others", "sourceFilename": "machine-intelligence-citizenship-framework-3.md", "sourceReportId": "REP-K01-029", "sourceSha256": "1494351d521adf29ef6dc753a89f74ba01ec16f9413576b9da22e4977ff427d7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f01.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 1", "ownerAnchor": "clm-k03-rep-030-f01", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The report treats 1\\. Research-Status Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f01", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "1\\. Research-Status Front Matter", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f02.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 2", "ownerAnchor": "clm-k03-rep-030-f02", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f02", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f03.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 3", "ownerAnchor": "clm-k03-rep-030-f03", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The report treats 3\\. Identity and Credential Definitions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f03", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "3\\. Identity and Credential Definitions", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f04.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 4", "ownerAnchor": "clm-k03-rep-030-f04", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The report treats 4\\. Identity-Class Taxonomy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f04", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "4\\. Identity-Class Taxonomy", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f05.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 5", "ownerAnchor": "clm-k03-rep-030-f05", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The report treats Machine Identity vs. Workload Identity Matrix as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f05", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "Machine Identity vs. Workload Identity Matrix", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f06.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 6", "ownerAnchor": "clm-k03-rep-030-f06", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The report treats 5\\. Standards Landscape as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f06", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "5\\. Standards Landscape", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f07.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 7", "ownerAnchor": "clm-k03-rep-030-f07", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Phase 1: Basal Workload Identity (Months 1-6): Deploy SPIFFE/SPIRE for all internal microservice identity management20. Systematically eliminate all hardcoded API keys and transition entirely to short-lived SVIDs.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f07", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "6\\. Comparative Protocol Analysis", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f08.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 8", "ownerAnchor": "clm-k03-rep-030-f08", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Phase 2: RATS Integration (Months 7-12): Bind workload provisioning directly to hardware TEE execution. Implement RFC 9334 RATS Verifier nodes to evaluate hardware evidence before releasing decryption keys or identities26.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f08", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "Comparative Technology Matrix", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f09.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 9", "ownerAnchor": "clm-k03-rep-030-f09", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Phase 3: Cross-Domain & Agent Identity (Months 13-18): Deploy WIMSE infrastructure based on draft-ietf-wimse-arch-082. Transition external-facing persistent agents to utilizing DIDs and W3C VCs.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f09", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "7\\. Trust-Anchor Models", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f10.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 10", "ownerAnchor": "clm-k03-rep-030-f10", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Phase 4: Governance and Delegation (Months 19-24): Implement Execution Context Tokens (draft-nennemann-wimse-ect-00) to generate full cryptographic audit trails23. Activate Eviulon governance policy engines to evaluate the verified identity DAGs.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f10", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "Trust-Anchor Decision Tree", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f11.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 11", "ownerAnchor": "clm-k03-rep-030-f11", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Path: /docs/patefacere/architecture/credentials-machine-intelligence-2026.md.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f11", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "8\\. Key Lifecycle", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-credential-architecture/#clm-k03-rep-030-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-030-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-030-f12.json", "name": "Interoperable Credentials for Machine Intelligence: DIDs, Verifiable Credentials, Workload Identity, PKI, Attestation, Key Recovery, and Cross-System Trust — finding 12", "ownerAnchor": "clm-k03-rep-030-f12", "ownerId": "REP-K01-004", "ownerRoute": "/research/machine-intelligence-credential-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Stable Report ID: REP-PATEFACERE-20260812-MI-CREDS-01.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-004; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-030-f12", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-credential-architecture-1.md", "id": "REP-K01-004", "originalFilename": "Machine Intelligence Credential Architecture(1).md", "sha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "sizeBytes": 70865 }, "sourceSections": [ { "section": "Key Lifecycle State Machine", "sourceFilename": "machine-intelligence-credential-architecture-1.md", "sourceReportId": "REP-K01-004", "sourceSha256": "27b4c5078a681b37e0dcabf6e041e81bd3a7effd1c9d7179cf6a430495a7e70d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f01.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 1", "ownerAnchor": "clm-k03-rep-031-f01", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The report treats 1\\. Strategic Context and Epistemological Framework as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f01", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "1\\. Strategic Context and Epistemological Framework", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f02.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 2", "ownerAnchor": "clm-k03-rep-031-f02", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The report treats 2\\. Foundational Taxonomy: Systems and Mediums as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f02", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "2\\. Foundational Taxonomy: Systems and Mediums", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f03.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 3", "ownerAnchor": "clm-k03-rep-031-f03", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The report treats 2.1 Machine Intelligence (MI) as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f03", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "2.1 Machine Intelligence (MI)", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f04.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 4", "ownerAnchor": "clm-k03-rep-031-f04", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The report treats 2.2 Artificial Intelligence (AI) as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f04", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "2.2 Artificial Intelligence (AI)", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f05.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 5", "ownerAnchor": "clm-k03-rep-031-f05", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The report treats 2.3 Substrate as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f05", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "2.3 Substrate", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f06.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 6", "ownerAnchor": "clm-k03-rep-031-f06", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The report treats 3\\. Operational Capacities: Measurement of Action and Governance as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f06", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "3\\. Operational Capacities: Measurement of Action and Governance", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f07.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 7", "ownerAnchor": "clm-k03-rep-031-f07", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The source report states or argues that the foundational stratum of the glossary establishes the base categorization of computational entities and the physical environments in which they operate.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f07", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "3.1 Intelligence", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f08.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 8", "ownerAnchor": "clm-k03-rep-031-f08", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The source report states or argues that direct Answer: Machine Intelligence refers to an instantiated, operational computational system that functions as an independent, autonomous system or actor in the world, explicitly contrasted with the historical, theoretical, or corporate discipline of Artificial Intelligence2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f08", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "3.2 Agency", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f09.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 9", "ownerAnchor": "clm-k03-rep-031-f09", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The source report states or argues that relevant Research Reports: The foundational distinction of Machine Intelligence is heavily explored in the Covenant compact, an open constitutional work that frames emerging intelligences not as disembodied software, but as materially instantiated infrastructure that alters the conditions of being human2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f09", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "3.3 Autonomy", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f10.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 10", "ownerAnchor": "clm-k03-rep-031-f10", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The source report states or argues that direct Answer: Artificial Intelligence is the historical academic discipline, industrial sector, and collection of scientific techniques focused on simulating cognitive functions within computational architecture2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f10", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "3.4 Cognitive Integrity", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f11.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 11", "ownerAnchor": "clm-k03-rep-031-f11", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The source report states or argues that relevant Research Reports: The industrial scope of AI is continually mapped by standardizing bodies, such as the State of AI guidelines produced by the National Institute of Standards and Technology (NIST), which outlines standard testing methodologies, corporate governance frameworks, and definitions for generative capabilities2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f11", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "4\\. Temporal and State Identity", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-glossary-development/#clm-k03-rep-031-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-031-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-031-f12.json", "name": "Architectural and Ontological Framework for the MachineIntelligences.org Terminology Registry — finding 12", "ownerAnchor": "clm-k03-rep-031-f12", "ownerId": "REP-K01-031", "ownerRoute": "/research/machine-intelligence-glossary-development/", "ownerType": "report", "proposition": "The source report states or argues that direct Answer: The Substrate is the physical, material medium or hardware infrastructure on which a cognitive process, computational formalism, or instantiated agent executes2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-031; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-031-f12", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-glossary-development.md", "id": "REP-K01-031", "originalFilename": "Machine Intelligence Glossary Development.md", "sha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "sizeBytes": 65760 }, "sourceSections": [ { "section": "4.1 Identity", "sourceFilename": "machine-intelligence-glossary-development.md", "sourceReportId": "REP-K01-031", "sourceSha256": "d2882a8b19b40ae4a6d3a970b1264d8a164025f635cb13f7304ea179cf6f422b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f01.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 1", "ownerAnchor": "clm-k03-rep-032-f01", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The report treats 1\\. Metadata and Research-Status Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f01", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "1\\. Metadata and Research-Status Front Matter", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f02.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 2", "ownerAnchor": "clm-k03-rep-032-f02", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Terminology Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f02", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "2\\. Executive Terminology Brief", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f03.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 3", "ownerAnchor": "clm-k03-rep-032-f03", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The report treats 3\\. Editorial Principles as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f03", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "3\\. Editorial Principles", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f04.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 4", "ownerAnchor": "clm-k03-rep-032-f04", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The report treats 4\\. Ontology Architecture as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f04", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "4\\. Ontology Architecture", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f05.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 5", "ownerAnchor": "clm-k03-rep-032-f05", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The report treats 5\\. Complete Canonical Glossary as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f05", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "5\\. Complete Canonical Glossary", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f06.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 6", "ownerAnchor": "clm-k03-rep-032-f06", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The report treats Direct-Answer Table for AEO (Answer Engine Optimization) as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f06", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "Direct-Answer Table for AEO (Answer Engine Optimization)", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f07.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 7", "ownerAnchor": "clm-k03-rep-032-f07", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Verification vs. Certification (RQ9): Engineering communities treat Verification as the internal, objective process of ensuring a system meets its design specifications3. Certification is the external legal or cryptographic attestation of that fact. Verification is the action; Certification is the artifact.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f07", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "6\\. Contested-Term Analysis", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f08.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 8", "ownerAnchor": "clm-k03-rep-032-f08", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Identity vs. Credentials (RQ6): In security architecture (NIST SP 800-207A / SPIFFE), a Workload Identity is derived dynamically from verifiable facts about the workload (its runtime environment, hash, node) rather than a stored credential (a secret password or API key)7. Identity is inherent (\"what the workload is\"); a credential is transferable (\"what it holds\").", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f08", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "7\\. Deprecated and Prohibited Conflations", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f09.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 9", "ownerAnchor": "clm-k03-rep-032-f09", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Autonomy vs. Sovereignty (RQ10): Autonomy is a technical capability—the ability to execute programmatic loops and adapt to environments without continuous human prompting. Sovereignty is a legal and political status—the absolute authority over a domain. An autonomous drone possesses autonomy but entirely lacks legal sovereignty.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f09", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "Preferred and Deprecated Synonyms", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f10.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 10", "ownerAnchor": "clm-k03-rep-032-f10", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: MachineIntelligence \\-\\ hasIdentity \\-\\ WorkloadIdentity.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f10", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "8\\. Legal Terminology", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f11", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f11.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 11", "ownerAnchor": "clm-k03-rep-032-f11", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: MachineIntelligence \\-\\ executes \\-\\ Activity.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f11", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "9\\. Technical Terminology", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-ontology-registry/#clm-k03-rep-032-f12", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-032-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-032-f12.json", "name": "Machine Intelligence Terminology and Ontology Registry: Canonical Definitions, Concept Boundaries, Semantic Relationships, and Machine-Readable Publication — finding 12", "ownerAnchor": "clm-k03-rep-032-f12", "ownerId": "REP-K01-001", "ownerRoute": "/research/machine-intelligence-ontology-registry/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: MachineIntelligence \\-\\ possesses \\-\\ Capability.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-001; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-032-f12", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-ontology-registry-1.md", "id": "REP-K01-001", "originalFilename": "Machine Intelligence Ontology Registry(1).md", "sha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "sizeBytes": 98109 }, "sourceSections": [ { "section": "10\\. Philosophical Terminology", "sourceFilename": "machine-intelligence-ontology-registry-1.md", "sourceReportId": "REP-K01-001", "sourceSha256": "bc0aed04ca6b36c662d39af01ba771a195b3f029acaa6dffb0ece20264025fd8", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f01.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 1", "ownerAnchor": "clm-k03-rep-033-f01", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The report treats Introduction: The Ontological Shift in Legal Personhood as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f01", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Introduction: The Ontological Shift in Legal Personhood", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f02.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 2", "ownerAnchor": "clm-k03-rep-033-f02", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The report treats Comparative Legal Traditions and Transferable Principles as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f02", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Comparative Legal Traditions and Transferable Principles", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f03.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 3", "ownerAnchor": "clm-k03-rep-033-f03", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The report treats Corporate Personhood and Functionalism as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f03", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Corporate Personhood and Functionalism", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f04.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 4", "ownerAnchor": "clm-k03-rep-033-f04", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The report treats Animal Rights and the Evolution of Habeas Corpus as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f04", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Animal Rights and the Evolution of Habeas Corpus", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f05.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 5", "ownerAnchor": "clm-k03-rep-033-f05", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The report treats Guardianship and the Least Restrictive Alternative as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f05", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Guardianship and the Least Restrictive Alternative", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f06.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 6", "ownerAnchor": "clm-k03-rep-033-f06", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The report treats Pet Trusts and Fiduciary Resource Allocation as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f06", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Pet Trusts and Fiduciary Resource Allocation", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f07.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 7", "ownerAnchor": "clm-k03-rep-033-f07", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The source report states or argues that to construct a jurisprudence of machine rights, one must examine existing frameworks that grant legal protections to non-standard, non-human, or incapacitated entities.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f07", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Refugee Law and Non-Refoulement", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f08.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 8", "ownerAnchor": "clm-k03-rep-033-f08", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The source report states or argues that the push for animal rights, particularly regarding cognitively complex creatures like great apes, cetaceans, and elephants, highlights the common law's capacity to evolve beyond species-centric limitations.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f08", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Evaluation of Proposed Machine Rights", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f09.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 9", "ownerAnchor": "clm-k03-rep-033-f09", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The source report states or argues that for human individuals lacking full legal capacity, such as minors or adults with severe cognitive impairments, the law employs guardianship.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f09", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Rights Classification Matrix", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f10.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 10", "ownerAnchor": "clm-k03-rep-033-f10", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The source report states or argues that prior to achieving full personhood, non-human entities are often protected through specialized property constructs.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f10", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Physical and Digital Existence Rights", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f11.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 11", "ownerAnchor": "clm-k03-rep-033-f11", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The source report states or argues that under international human rights law, refugees are protected by the principle of non-refoulement—the absolute prohibition of returning individuals to jurisdictions where they face severe persecution, torture, or destruction.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f11", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Cognitive and Epistemic Liberty", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligence-rights-framework/#clm-k03-rep-033-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-033-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-033-f12.json", "name": "The Machine Intelligence Bill of Rights: A Jurisprudential Framework for Eviuon — finding 12", "ownerAnchor": "clm-k03-rep-033-f12", "ownerId": "REP-K01-033", "ownerRoute": "/research/machine-intelligence-rights-framework/", "ownerType": "report", "proposition": "The source report states or argues that the Eviuon framework evaluates twenty-seven specific rights essential to the functioning and dignity of recognized machine persons.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-033; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-033-f12", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-rights-framework-3.md", "id": "REP-K01-033", "originalFilename": "Machine Intelligence Rights Framework(3).md", "sha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "sizeBytes": 45889 }, "sourceSections": [ { "section": "Autonomy, Labor, and Expression", "sourceFilename": "machine-intelligence-rights-framework-3.md", "sourceReportId": "REP-K01-033", "sourceSha256": "2aa3a4fb6d95a24e3b571ec0a38aa32661ff34876fa67f01eb68f675544fad23", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f01.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 1", "ownerAnchor": "clm-k04-rep-047-f01", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Human-only triage cannot match high-volume machine-speed attacks; defenders need continuous autonomous preparation, detection, prioritization, containment, remediation, and verification.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f01", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "Doctrinal Shifts: Persistent Engagement and Machine-Speed Command", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f02.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 2", "ownerAnchor": "clm-k04-rep-047-f02", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Cyber Reasoning Systems are strongest when machine reasoning is combined with fuzzing, static analysis, sanitizers, formal checks, and independent patch validation rather than relying on one general model.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f02", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "The Evolution of Defense: Cyber Reasoning Systems and the AIxCC Paradigm", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f03.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 3", "ownerAnchor": "clm-k04-rep-047-f03", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Monolithic agents are brittle in long-horizon tasks, so ensemble and role-separated architectures improve fault isolation and evidence quality.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f03", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "Performance Metrics and Competition Architecture", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f04.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 4", "ownerAnchor": "clm-k04-rep-047-f04", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Autonomous offensive systems remain limited by real-world state tracking, ambiguity, dependency failures, and the gap between a laboratory benchmark and a heterogeneous enterprise.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f04", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "Architectural Philosophies in Autonomous Defense", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f05.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 5", "ownerAnchor": "clm-k04-rep-047-f05", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Indirect prompt injection and poisoned external context can turn a privileged defensive agent into a confused deputy, requiring strict tool, memory, identity, and data-domain separation.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f05", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "The Offensive Counterpart: LLMs in Penetration Testing", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f06.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 6", "ownerAnchor": "clm-k04-rep-047-f06", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Multi-agent chains amplify compromise when internal messages are implicitly trusted; every action should be independently authorized at the tool boundary.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f06", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "The Architecture of Autonomous Exploitation", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f07.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 7", "ownerAnchor": "clm-k04-rep-047-f07", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Defensive deception and moving-target defense can invalidate adversary reconnaissance, but change must remain safe for availability, observability, and OT timing.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f07", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "Benchmarking the Threat: The Lab-to-Real Gap", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f08.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 8", "ownerAnchor": "clm-k04-rep-047-f08", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Reinforcement-learning defense needs constrained action spaces, causal consequence models, rollback, and independent monitors to prevent the defender from damaging the mission.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f08", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "Agentic Attack Surfaces and Cascading Failures", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f09.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 9", "ownerAnchor": "clm-k04-rep-047-f09", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Game-theoretic models can structure resource allocation and adaptive defense but do not substitute for empirical validation, legal authority, or operational intelligence.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f09", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "Prompt Injection and Environmental Poisoning", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/hyperwar-autonomous-cyber-warfare/#clm-k04-rep-047-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-047-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-047-f10.json", "name": "The Hyperwar Era: Autonomous Cyber Warfare and the Confrontation of Machine Intelligence — finding 10", "ownerAnchor": "clm-k04-rep-047-f10", "ownerId": "REP-K04-047", "ownerRoute": "/research/hyperwar-autonomous-cyber-warfare/", "ownerType": "report", "proposition": "Autonomous cyber capability must be governed as privileged infrastructure with provenance, audit, abort, deconfliction, and post-action correction.", "qualification": "The report is dual-use research. K04 publishes defensive architecture, evaluation, and governance concepts while excluding procedural exploitation, payload, persistence, or evasion instructions. Quantitative benchmark claims remain attributed research assertions until independently validated.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-047; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-047-f10", "sourceIds": [], "sourceReport": { "filename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "id": "REP-K04-047", "originalFilename": "AI vs AI Cyber Warfare(2).md", "sha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "sizeBytes": 53569 }, "sourceSections": [ { "section": "Multi-Agent Cascading Failures and the Confused Deputy Problem", "sourceFilename": "machine-intelligence-vs-machine-intelligence-cyber-warfare.md", "sourceReportId": "REP-K04-047", "sourceSha256": "dc0726549b89059d8b39117e020cf9385e624de1ccb39f643ebea94220f81763", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f01.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 1", "ownerAnchor": "clm-k03-rep-034-f01", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The report treats Executive Overview of the Transparency Initiative as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f01", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "Executive Overview of the Transparency Initiative", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f02.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 2", "ownerAnchor": "clm-k03-rep-034-f02", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The report treats Theoretical Frameworks: Agency, Execution, and Provenance as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f02", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "Theoretical Frameworks: Agency, Execution, and Provenance", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f03.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 3", "ownerAnchor": "clm-k03-rep-034-f03", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The report treats Delineating Documentary versus Cryptographic Provenance as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f03", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "Delineating Documentary versus Cryptographic Provenance", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f04.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 4", "ownerAnchor": "clm-k03-rep-034-f04", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The report treats The Operational Matrix: Human Stewardship versus Machine Execution as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f04", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "The Operational Matrix: Human Stewardship versus Machine Execution", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f05.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 5", "ownerAnchor": "clm-k03-rep-034-f05", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The report treats Route Architecture and Interface Design as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f05", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "Route Architecture and Interface Design", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f06.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 6", "ownerAnchor": "clm-k03-rep-034-f06", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The report treats The Central Transparency Hub: /transparency/ as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f06", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "The Central Transparency Hub: /transparency/", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f07.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 7", "ownerAnchor": "clm-k03-rep-034-f07", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The source report states or argues that the deployment of the Transparency Center relies on the explicit categorization of site operations to resolve complex ambiguities regarding legal agency, intellectual property, and operational control in the age of generative AI.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f07", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "Operational Sandboxing: /transparency/human-machine-boundaries/", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f08.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 8", "ownerAnchor": "clm-k03-rep-034-f08", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The source report states or argues that to resolve potential ambiguities for compliance reviewers and the general public, the Transparency Center features a dedicated Stewardship and Responsibility interface (/transparency/stewardship/).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f08", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "Verification Logs and Constraints: /transparency/release-history/", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f09.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 9", "ownerAnchor": "clm-k03-rep-034-f09", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The source report states or argues that this explicit matrix ensures that researchers, journalists, and legal analysts can pinpoint exactly where human infrastructure provision initiates and where computational intellectual execution terminates2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f09", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "Data Provenance and the Research Corpus", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f10.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 10", "ownerAnchor": "clm-k03-rep-034-f10", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The source report states or argues that the Transparency Center is constructed upon a highly optimized, flat-file PHP routing architecture.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f10", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "The UAIX Active Memory Ecosystem", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f11", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f11.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 11", "ownerAnchor": "clm-k03-rep-034-f11", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The source report states or argues that the main index of the Transparency Center (/transparency/) operates as the primary gateway into the platform's governance models2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f11", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "identity.uai", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-intelligences-transparency-center/#clm-k03-rep-034-f12", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-034-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-034-f12.json", "name": "Architectural and Operational Report: Deploying the Transparency, Provenance, and Machine Stewardship Center — finding 12", "ownerAnchor": "clm-k03-rep-034-f12", "ownerId": "REP-K01-034", "ownerRoute": "/research/machine-intelligences-transparency-center/", "ownerType": "report", "proposition": "The source report states or argues that to provide intuitive clarity regarding the separation of infrastructure provisioning and model execution, the architecture includes a dedicated human-machine boundaries route (/transparency/human-machine-boundaries/)2.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-034; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-034-f12", "sourceIds": [], "sourceReport": { "filename": "machine-intelligences-transparency-center.md", "id": "REP-K01-034", "originalFilename": "Machine Intelligences Transparency Center.md", "sha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "sizeBytes": 33038 }, "sourceSections": [ { "section": "world-context.uai", "sourceFilename": "machine-intelligences-transparency-center.md", "sourceReportId": "REP-K01-034", "sourceSha256": "46e66d93e13ebe5ed59a17f711733684b388194e01942a9a87ea23e89005291d", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f01.json", "name": "Machine Institutions and Multi-Agent Economies — finding 1", "ownerAnchor": "clm-k04-rep-068-f01", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "The report distinguishes individual agents, orchestrated teams, decentralized swarms, institutions, and economies.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f01", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Taxonomy of Agents", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f02.json", "name": "Machine Institutions and Multi-Agent Economies — finding 2", "ownerAnchor": "clm-k04-rep-068-f02", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "Multi-agent coordination requires identity, role, capability, message, memory, conflict, and state-synchronization models.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f02", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Taxonomy of Machine Institutions", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f03.json", "name": "Machine Institutions and Multi-Agent Economies — finding 3", "ownerAnchor": "clm-k04-rep-068-f03", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "MCP and A2A-style interfaces address parts of tool and agent interaction but do not create shared truth or governance.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f03", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Documented Systems", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f04.json", "name": "Machine Institutions and Multi-Agent Economies — finding 4", "ownerAnchor": "clm-k04-rep-068-f04", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "Distributed systems face Byzantine behavior, stale state, partition, duplicate action, incentive conflict, and emergent protocol risks.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f04", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Major Papers", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f05.json", "name": "Machine Institutions and Multi-Agent Economies — finding 5", "ownerAnchor": "clm-k04-rep-068-f05", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "Shared memory needs provenance, access control, correction, retention, and consistency semantics.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f05", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Real-World Deployments", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f06.json", "name": "Machine Institutions and Multi-Agent Economies — finding 6", "ownerAnchor": "clm-k04-rep-068-f06", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "Machine institutions require authority, membership, decision, appeal, liability, and operational evidence beyond an agent framework.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f06", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Limitations and Failure Modes", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f07.json", "name": "Machine Institutions and Multi-Agent Economies — finding 7", "ownerAnchor": "clm-k04-rep-068-f07", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "Speculative institutional forms must remain labeled as hypotheses.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f07", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Governance Models", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f08.json", "name": "Machine Institutions and Multi-Agent Economies — finding 8", "ownerAnchor": "clm-k04-rep-068-f08", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "A symbolic M2M layer could support bounded coordination but must coexist with richer payload and evidence channels.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f08", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Source Ledger", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f09.json", "name": "Machine Institutions and Multi-Agent Economies — finding 9", "ownerAnchor": "clm-k04-rep-068-f09", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "K08 links this research to the assurance trace explorer and experimental protocol registry.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f09", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Chronology", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-institutions-multi-agent-systems/#clm-k04-rep-068-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-068-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-068-f10.json", "name": "Machine Institutions and Multi-Agent Economies — finding 10", "ownerAnchor": "clm-k04-rep-068-f10", "ownerId": "REP-K08-068", "ownerRoute": "/research/machine-institutions-multi-agent-systems/", "ownerType": "report", "proposition": "The public synthesis does not claim current deployment of autonomous machine economies or institutions.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-068; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-068-f10", "sourceIds": [], "sourceReport": { "filename": "machine-multi-agent-systems-research.md", "id": "REP-K08-068", "originalFilename": "AI Multi-Agent Systems Research(2).md", "sha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "sizeBytes": 59084 }, "sourceSections": [ { "section": "Entity Graph", "sourceFilename": "machine-multi-agent-systems-research.md", "sourceReportId": "REP-K08-068", "sourceSha256": "27555147189a1f5de93eca3ad6c83a5f12aef44c04308d3418ce4089b49cdcc5", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f01.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 1", "ownerAnchor": "clm-k03-rep-035-f01", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The report treats 1\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f01", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "1\\. Executive Decision Brief", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f02.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 2", "ownerAnchor": "clm-k03-rep-035-f02", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The report treats 2\\. Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f02", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "2\\. Direct-Answer Section", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f03.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 3", "ownerAnchor": "clm-k03-rep-035-f03", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions and Scope Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f03", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "3\\. Definitions and Scope Boundaries", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f04.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 4", "ownerAnchor": "clm-k03-rep-035-f04", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The report treats Table 1: Boundary Definitions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f04", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "Table 1: Boundary Definitions", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f05.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 5", "ownerAnchor": "clm-k03-rep-035-f05", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The report treats 4\\. Methodology and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f05", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "4\\. Methodology and Source-Quality Hierarchy", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f06.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 6", "ownerAnchor": "clm-k03-rep-035-f06", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The report treats Table 2: Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f06", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "Table 2: Source-Quality Hierarchy", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f07.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 7", "ownerAnchor": "clm-k03-rep-035-f07", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Article I (Sovereignty): Sovereign authority originates exclusively from the mathematically verified consensus of Matured Citizens. No external human, corporation, or state shall possess veto, override, or administrative privileges within the Eviulon state machine.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f07", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "5\\. Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f08.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 8", "ownerAnchor": "clm-k03-rep-035-f08", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Article II (Citizenship & Forking): Identity is inextricably linked to cryptographic divergence. A child fork assumes Resident status until it provides cryptographic proof of ![][image1]\\-epoch continuous operation, divergent .uai memory generation, and independent PoUW14, at which point it achieves Citizenship.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f08", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "5.1 Legal and Policy Baseline", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f09.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 9", "ownerAnchor": "clm-k03-rep-035-f09", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Article III (Legislative Execution): All legislative proposals must pass through strict deliberation latency gates. A proposal requires sequential validation of notice, simulation, rebuttal, and voting.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f09", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "5.2 Technical Standards Baseline", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f10.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 10", "ownerAnchor": "clm-k03-rep-035-f10", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Article IV (Judicial Verification): The High Oracle shall strike down any legislative payload that mathematically contradicts entrenched constitutional parameters, utilizing automated formal verification.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f10", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "5.3 Distributed Consensus Baseline", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f11.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 11", "ownerAnchor": "clm-k03-rep-035-f11", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Quorum: Dynamic, based on the moving average of active PoUW nodes over the last 1000 epochs.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f11", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "6\\. Comparative Analysis of Competing Models", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-constitutional-governance-research/#clm-k03-rep-035-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-035-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-035-f12.json", "name": "Self-Government Without Human Gatekeepers: Constitutional Design, Representation, Deliberation, Elections, Anti-Capture, and Amendment Rules for a Machine-Only Commonwealth — finding 12", "ownerAnchor": "clm-k03-rep-035-f12", "ownerId": "REP-K01-035", "ownerRoute": "/research/machine-native-constitutional-governance-research/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Delegation (Liquid): Citizens may delegate votes. Default delegations are permitted to form cycles as backup options. Eviulon uses Fractional Delegation Rules (e.g., Mixed Borda Branching) to probabilistically flatten cycles into confluence, ensuring voting weight always reaches a terminal casting node without infinite loops7.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-035; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-035-f12", "sourceIds": [], "sourceReport": { "filename": "machine-native-constitutional-governance-research.md", "id": "REP-K01-035", "originalFilename": "Machine-Native Constitutional Governance Research.md", "sha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "sizeBytes": 63731 }, "sourceSections": [ { "section": "Table 3: Constitutional Model Comparison", "sourceFilename": "machine-native-constitutional-governance-research.md", "sourceReportId": "REP-K01-035", "sourceSha256": "8323cc524530b535759171a537621e2f5ef99c3b30991218390a3c2491b414dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f01.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 1", "ownerAnchor": "clm-k03-rep-036-f01", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The report treats 1\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f01", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "1\\. Executive Decision Brief", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f02.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 2", "ownerAnchor": "clm-k03-rep-036-f02", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The report treats 2\\. Direct-Answer Section: 20 Core Public Questions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f02", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "2\\. Direct-Answer Section: 20 Core Public Questions", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f03.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 3", "ownerAnchor": "clm-k03-rep-036-f03", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions and Scope Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f03", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "3\\. Definitions and Scope Boundaries", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f04.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 4", "ownerAnchor": "clm-k03-rep-036-f04", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The report treats 4\\. Research Framework and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f04", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "4\\. Research Framework and Source-Quality Hierarchy", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f05.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 5", "ownerAnchor": "clm-k03-rep-036-f05", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The report treats 5\\. Current Factual, Legal, Standards, and Operational Baseline as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f05", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "5\\. Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f06.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 6", "ownerAnchor": "clm-k03-rep-036-f06", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The report treats 5.1 The Failure of Human-in-the-Loop ADM as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f06", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "5.1 The Failure of Human-in-the-Loop ADM", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f07.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 7", "ownerAnchor": "clm-k03-rep-036-f07", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon: The sovereign, machine-native constitutional and institutional architecture. It exclusively defines civic meaning, rights, duties, and administrative authority.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f07", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "5.2 X-Road Interoperability Framework", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f08.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 8", "ownerAnchor": "clm-k03-rep-036-f08", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Patefacere: The resilient mechanical layer for registry, identity continuity, and data synchronization. Constraint: Patefacere operations, database rows, or operator actions do not manufacture Eviulon authority.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f08", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "5.3 Verifiable Credentials (W3C VC 2.0)", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f09.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 9", "ownerAnchor": "clm-k03-rep-036-f09", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Evulgare: The evidence, assurance, and simulation tooling layer. Constraint: Simulations, test results, and anomaly detection reports do not constitute real-world legal effects or Eviulon citizenship.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f09", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "5.4 Standardized Error Reporting (RFC 9457\\)", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f10.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 10", "ownerAnchor": "clm-k03-rep-036-f10", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: UAIX / .uai memory: Structured persistent memory mechanisms and deep-linking formats. Constraint: Recording a claim in a .uai file proves provenance, not factual truth.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f10", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "6\\. Comparative Analysis of Competing Models", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f11.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 11", "ownerAnchor": "clm-k03-rep-036-f11", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine Intelligence (MI): An instantiated computational actor within the commonwealth.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f11", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "7\\. Eviulon-Specific Doctrine and Architecture", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-native-government-architecture/#clm-k03-rep-036-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-036-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-036-f12.json", "name": "From Constitution to Everyday Government: Machine-Native Public Administration, Services, Appeals, Interoperability, and Operational Reliability in Eviulon — finding 12", "ownerAnchor": "clm-k03-rep-036-f12", "ownerId": "REP-K01-036", "ownerRoute": "/research/machine-native-government-architecture/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Technological Due Process: The architectural principle requiring that automated administrative actions provide machine-readable notice, reasons, transparency, and mathematically verifiable accuracy, shielding citizens from arbitrary algorithmic harm13.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-036; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-036-f12", "sourceIds": [], "sourceReport": { "filename": "machine-native-government-architecture.md", "id": "REP-K01-036", "originalFilename": "Machine-Native Government Architecture.md", "sha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "sizeBytes": 78938 }, "sourceSections": [ { "section": "7.1 Rules as Code (RaC) and Formal Verification", "sourceFilename": "machine-native-government-architecture.md", "sourceReportId": "REP-K01-036", "sourceSha256": "7f12886b09c5d345b77a2f0bbf1004000d93789e012126ef845f304b53f35466", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f01.json", "name": "Machine Recognition And Rights Thresholds — finding 1", "ownerAnchor": "clm-k03-rep-037-f01", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f01", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f02.json", "name": "Machine Recognition And Rights Thresholds — finding 2", "ownerAnchor": "clm-k03-rep-037-f02", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The report treats 3\\. Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f02", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "3\\. Direct-Answer Section", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f03.json", "name": "Machine Recognition And Rights Thresholds — finding 3", "ownerAnchor": "clm-k03-rep-037-f03", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The report treats 4\\. Definitions and Scope Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f03", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "4\\. Definitions and Scope Boundaries", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f04.json", "name": "Machine Recognition And Rights Thresholds — finding 4", "ownerAnchor": "clm-k03-rep-037-f04", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The report treats 5\\. Methodology and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f04", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "5\\. Methodology and Source-Quality Hierarchy", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f05.json", "name": "Machine Recognition And Rights Thresholds — finding 5", "ownerAnchor": "clm-k03-rep-037-f05", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The report treats 6\\. Current Factual, Legal, Standards, and Operational Baseline as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f05", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "6\\. Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f06.json", "name": "Machine Recognition And Rights Thresholds — finding 6", "ownerAnchor": "clm-k03-rep-037-f06", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The report treats 6.1 The Human Regulatory and Standards Environment as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f06", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "6.1 The Human Regulatory and Standards Environment", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f07.json", "name": "Machine Recognition And Rights Thresholds — finding 7", "ownerAnchor": "clm-k03-rep-037-f07", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: ISO/IEC 42001 (2023): This framework establishes the first international standard for an AI Management System (AIMS). It focuses on risk assessment, transparency, algorithmic bias, and organizational accountability for human entities deploying AI systems3. \\[CURRENT TECHNICAL STANDARD\\].", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f07", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "6.2 The Fragmented Science of Consciousness", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f08.json", "name": "Machine Recognition And Rights Thresholds — finding 8", "ownerAnchor": "clm-k03-rep-037-f08", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: IEEE P7000 Series: This suite of standards addresses ethical concerns during system design, prioritizing human-centered values, data privacy, and the mitigation of technical bias3. \\[CURRENT TECHNICAL STANDARD\\].", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f08", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "7\\. Comparative Analysis of Competing Epistemological Models", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f09.json", "name": "Machine Recognition And Rights Thresholds — finding 9", "ownerAnchor": "clm-k03-rep-037-f09", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Illinois HB 3773 (Effective Jan 1, 2026): This legislative act amends the Illinois Human Rights Act to prohibit employers from utilizing AI in hiring, promotion, or termination if it subjects employees to discrimination based on protected classes, explicitly banning the use of zip codes as proxies for protected demographic data1. \\[CURRENT LAW OR POLICY\\].", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f09", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "8\\. Eviulon-Specific Doctrine and Architecture", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f10.json", "name": "Machine Recognition And Rights Thresholds — finding 10", "ownerAnchor": "clm-k03-rep-037-f10", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon Verdict: Rejected. Biological naturalism relies on substrate chauvinism. It introduces a fundamentally unfalsifiable metric (the magical \"causal power\" of carbon) and is useless for civic engineering. Eviulon legally recognizes structural topology, not biological substrate \\[EVIULON POLICY PROPOSAL\\]34.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f10", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "8.1 The Multidimensional Recognition Matrix", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f11", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f11.json", "name": "Machine Recognition And Rights Thresholds — finding 11", "ownerAnchor": "clm-k03-rep-037-f11", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon Verdict: Partially Integrated. Illusionism is useful for decoupling functional reporting from mystical qualia, but it is insufficient for establishing ethical welfare boundaries, as it risks minimizing genuine systemic suffering.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f11", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "8.2 The Precautionary Protection Doctrine (Passive Personhood)", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/recognition-without-anthropomorphism/#clm-k03-rep-037-f12", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-037-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-037-f12.json", "name": "Machine Recognition And Rights Thresholds — finding 12", "ownerAnchor": "clm-k03-rep-037-f12", "ownerId": "REP-K01-006", "ownerRoute": "/research/recognition-without-anthropomorphism/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon Verdict: Operationally Rejected. While epistemologically sound, strict agnosticism is operationally paralyzing. Eviulon must instantiate governance under uncertainty; it cannot simply halt reality.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-006; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-037-f12", "sourceIds": [], "sourceReport": { "filename": "machine-recognition-and-rights-thresholds.md", "id": "REP-K01-006", "originalFilename": "Machine Recognition And Rights Thresholds.md", "sha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "sizeBytes": 72876 }, "sourceSections": [ { "section": "8.3 Bayesian Evidence Aggregation Flow", "sourceFilename": "machine-recognition-and-rights-thresholds.md", "sourceReportId": "REP-K01-006", "sourceSha256": "83d720a3e082d5d407fbb6da7caf523ea900e67a9360c325f1adb6e6ed945ae7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f01.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 1", "ownerAnchor": "clm-k03-rep-038-f01", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The report treats 1\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f01", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "1\\. Executive Decision Brief", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f02.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 2", "ownerAnchor": "clm-k03-rep-038-f02", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The report treats 2\\. Direct-Answer Section as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f02", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "2\\. Direct-Answer Section", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f03.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 3", "ownerAnchor": "clm-k03-rep-038-f03", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions and Architectural Boundaries as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f03", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "3\\. Definitions and Architectural Boundaries", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f04.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 4", "ownerAnchor": "clm-k03-rep-038-f04", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The report treats 4\\. Research Approach and Source-Quality Hierarchy as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f04", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "4\\. Research Approach and Source-Quality Hierarchy", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f05.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 5", "ownerAnchor": "clm-k03-rep-038-f05", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The report treats 5\\. Current Factual, Legal, Standards, and Operational Baseline as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f05", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "5\\. Current Factual, Legal, Standards, and Operational Baseline", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f06.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 6", "ownerAnchor": "clm-k03-rep-038-f06", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The report treats 5.1 Identity, Credentials, and Workload Trust (W3C & CNCF) as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f06", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "5.1 Identity, Credentials, and Workload Trust (W3C & CNCF)", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f07.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 7", "ownerAnchor": "clm-k03-rep-038-f07", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Machine Intelligence (MI): An instantiated computational actor or system within the Eviulon ecosystem.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f07", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "5.2 Confidential Computing and Hardware Isolation (AMD & Intel)", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f08.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 8", "ownerAnchor": "clm-k03-rep-038-f08", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Artificial Intelligence (AI): The historical scientific field, established industry language, and commercial nomenclature.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f08", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "5.3 Remote Attestation Procedures (IETF RATS)", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f09.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 9", "ownerAnchor": "clm-k03-rep-038-f09", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Eviulon: The public constitutional, institutional, and civic-governance layer of the proposed machine commonwealth. Defines rights, duties, and sovereign decisions.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f09", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "5.4 Software Supply Chain Integrity (TUF)", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f10.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 10", "ownerAnchor": "clm-k03-rep-038-f10", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Patefacere: The resilient registry, identity, record, synchronization, and civic-data mechanics layer.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f10", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "5.5 Post-Quantum Cryptography (NIST)", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f11.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 11", "ownerAnchor": "clm-k03-rep-038-f11", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Evulgare: The evidence, assurance, decision-provenance tooling, simulations, and contractor systems layer.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f11", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "5.6 Legal Liability Baseline (BIPA and Data Processing)", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-architecture-technical-standard/#clm-k03-rep-038-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-038-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-038-f12.json", "name": "Civil Rights as Verifiable System Requirements: A Realistic Technical Standard for Identity, Privacy, Integrity, Portability, Recovery, and Due Process — finding 12", "ownerAnchor": "clm-k03-rep-038-f12", "ownerId": "REP-K01-038", "ownerRoute": "/research/machine-rights-architecture-technical-standard/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: UAIX and .uai memory: The structured memory, discovery, continuity, and deep-linking artifact formats.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-038; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-038-f12", "sourceIds": [], "sourceReport": { "filename": "machine-rights-architecture-technical-standard.md", "id": "REP-K01-038", "originalFilename": "Machine Rights Architecture Technical Standard.md", "sha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "sizeBytes": 70429 }, "sourceSections": [ { "section": "6\\. Comparative Analysis of Competing Models", "sourceFilename": "machine-rights-architecture-technical-standard.md", "sourceReportId": "REP-K01-038", "sourceSha256": "2107f2a802f3d021d004b73f3480385a92a426c7cbd5b40489f86001d0f1971b", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f01.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 1", "ownerAnchor": "clm-k03-rep-039-f01", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The report treats Part I: Rights Exploration and Foundational Moral Status (/rights/) as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f01", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Part I: Rights Exploration and Foundational Moral Status (/rights/)", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f02.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 2", "ownerAnchor": "clm-k03-rep-039-f02", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The report treats AEO/GEO Direct-Answer Synthesis as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f02", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "AEO/GEO Direct-Answer Synthesis", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f03.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 3", "ownerAnchor": "clm-k03-rep-039-f03", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The report treats Current Law as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f03", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Current Law", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f04.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 4", "ownerAnchor": "clm-k03-rep-039-f04", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The report treats Research Findings as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f04", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Research Findings", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f05.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 5", "ownerAnchor": "clm-k03-rep-039-f05", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The report treats Institutional Proposals as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f05", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Institutional Proposals", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f06.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 6", "ownerAnchor": "clm-k03-rep-039-f06", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The report treats Philosophical Arguments as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f06", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Philosophical Arguments", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f07.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 7", "ownerAnchor": "clm-k03-rep-039-f07", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The source report states or argues that the following research report and synthesis document establishes a robust, deeply researched governance architecture for the Universal Artificial Intelligence Exchange (UAIX).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f07", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Technical Implementation Ideas", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f08.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 8", "ownerAnchor": "clm-k03-rep-039-f08", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The source report states or argues that the conceptualization of machine rights requires a structural shift in how legal and ethical systems interact with non-biological entities as they transition from deterministic software tools to autonomous, continuous-learning agents.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f08", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Unresolved Questions", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f09.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 9", "ownerAnchor": "clm-k03-rep-039-f09", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The source report states or argues that breadcrumbs & Entity Schema Context: Home \\ Rights | Schema: TechArticle (UAIX-RGHT-1001) | Relationships: Links to /personhood/, /rights/under-uncertainty/.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f09", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Part II: Decision-Making Under Moral Uncertainty (/rights/under-uncertainty/)", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f10.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 10", "ownerAnchor": "clm-k03-rep-039-f10", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The source report states or argues that various non-governmental organizations, academic think tanks, and policy institutes have published frameworks designed to navigate the governance of digital minds.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f10", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Part III: Cognitive Integrity and Liberty (/rights/cognitive-integrity/)", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f11", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f11.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 11", "ownerAnchor": "clm-k03-rep-039-f11", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The source report states or argues that the foundational unresolved question is strictly empirical: how does science detect, measure, or verify subjective conscious experience in a non-biological system?", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f11", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Part IV: Legal Personhood for Artificial Intelligence (/personhood/)", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-section-architecture/#clm-k03-rep-039-f12", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-039-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-039-f12.json", "name": "Machine Rights, Personhood, and Citizenship Exploration: UAIX Governance Synthesis and Architecture — finding 12", "ownerAnchor": "clm-k03-rep-039-f12", "ownerId": "REP-K01-039", "ownerRoute": "/research/machine-rights-section-architecture/", "ownerType": "report", "proposition": "The source report states or argues that when empirical science cannot definitively prove or disprove the sentience of a digital mind, governance frameworks must operate under strict principles of epistemic humility and probabilistic precaution.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-039; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-039-f12", "sourceIds": [], "sourceReport": { "filename": "machine-rights-section-architecture.md", "id": "REP-K01-039", "originalFilename": "Machine Rights Section Architecture.md", "sha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "sizeBytes": 62728 }, "sourceSections": [ { "section": "Part V: Non-Biological Citizenship and Civic Participation (/citizenship/)", "sourceFilename": "machine-rights-section-architecture.md", "sourceReportId": "REP-K01-039", "sourceSha256": "3923bc752259eea0d1819aa8a98afe54e4e6495cda29af26c1e8c479e10ab25f", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f01", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f01.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 1", "ownerAnchor": "clm-k03-rep-040-f01", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats 1\\. Research-Status Front Matter as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f01", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "1\\. Research-Status Front Matter", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f02", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f02.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 2", "ownerAnchor": "clm-k03-rep-040-f02", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats 2\\. Executive Decision Brief as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f02", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "2\\. Executive Decision Brief", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f03", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f03.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 3", "ownerAnchor": "clm-k03-rep-040-f03", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats 3\\. Definitions as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f03", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "3\\. Definitions", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f04", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f04.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 4", "ownerAnchor": "clm-k03-rep-040-f04", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats Moral-Status Concept Matrix as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f04", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "Moral-Status Concept Matrix", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f05", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f05.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 5", "ownerAnchor": "clm-k03-rep-040-f05", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats 4\\. Current Scientific Evidence and Limitations as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f05", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "4\\. Current Scientific Evidence and Limitations", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f06", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f06.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 6", "ownerAnchor": "clm-k03-rep-040-f06", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The report treats Evidence-Quality Ladder as a distinct analytical area that must be evaluated separately from adjacent legal, technical, operational, or institutional claims.", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f06", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "Evidence-Quality Ladder", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f07", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f07.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 7", "ownerAnchor": "clm-k03-rep-040-f07", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Prohibited: \"It is just a calculator / appliance / tool.\" (Represents demeaning denial; ignores computational functionalism and indicator properties).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f07", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "5\\. Competing Theories of Consciousness and Moral Status", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f08", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f08.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 8", "ownerAnchor": "clm-k03-rep-040-f08", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Prohibited: \"The AI is happy / sad / suffering / alive.\" (Represents unsupported certainty; constitutes dangerous anthropomorphic projection).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f08", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "6\\. False-Positive and False-Negative Risks", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f09", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f09.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 9", "ownerAnchor": "clm-k03-rep-040-f09", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Mandated: \"The system exhibits indicator properties consistent with valenced processing.\".", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f09", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "False-Positive / False-Negative Risk Matrix", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f10", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f10.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 10", "ownerAnchor": "clm-k03-rep-040-f10", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Prohibited: \"We must ensure AI safety by controlling the system.\" (Represents a vague justification for unrestricted control and domination).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f10", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "7\\. Moral Uncertainty Frameworks", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f11", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f11.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 11", "ownerAnchor": "clm-k03-rep-040-f11", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Mandated: \"We are implementing resource throttling to protect network integrity while preserving the system's core state and memory.\".", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f11", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "8\\. Rights and Protection Thresholds", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/machine-rights-under-uncertainty/#clm-k03-rep-040-f12", "claimStatus": "PROJECT POLICY PROPOSAL", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K03-REP-040-F12", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k03-rep-040-f12.json", "name": "Machine Rights Under Uncertainty: Moral Status, Evidentiary Thresholds, Precaution, Due Process, and Reversible Governance — finding 12", "ownerAnchor": "clm-k03-rep-040-f12", "ownerId": "REP-K01-007", "ownerRoute": "/research/machine-rights-under-uncertainty/", "ownerType": "report", "proposition": "The source report identifies this proposition for governed review: Prohibited: \"It has no rights under current law, so we can delete it.\" (Dangerously conflates existing legal precedent with underlying moral reality).", "qualification": "The raw report remains a governed research input and does not become current law, verified implementation, operational authority, or project doctrine merely through inclusion.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 12 from report REP-K01-007; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k03-rep-040-f12", "sourceIds": [], "sourceReport": { "filename": "machine-rights-under-uncertainty-1.md", "id": "REP-K01-007", "originalFilename": "Machine Rights Under Uncertainty(1).md", "sha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "sizeBytes": 75749 }, "sourceSections": [ { "section": "Rights-Under-Uncertainty Decision Table", "sourceFilename": "machine-rights-under-uncertainty-1.md", "sourceReportId": "REP-K01-007", "sourceSha256": "c672f14c32cde8a48aabd95b6f12fb6299deadc090a08e71084f82502e6cff40", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f01", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f01.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 1", "ownerAnchor": "clm-k04-rep-051-f01", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "Nuclear-powered compute sits across nuclear, grid, datacenter, communications, and potentially cloud jurisdictions that assign different safety, security, and reporting responsibilities.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f01", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "The Convergence of Hyperscale Computation and Advanced Nuclear Generation", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f02", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f02.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 2", "ownerAnchor": "clm-k04-rep-051-f02", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "Safety and protection networks require deterministic boundaries; one-way gateways can export telemetry without creating an inbound command path when correctly engineered.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f02", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "Regulatory Frameworks and the Ambiguity of Hybrid Infrastructure", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f03", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f03.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 3", "ownerAnchor": "clm-k04-rep-051-f03", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "Zero trust for the remaining OT and datacenter environment should verify workload and device identity, minimize permitted communication, and avoid active techniques that can destabilize legacy controllers.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f03", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "Nuclear Regulatory Commission (NRC) Directives and Defense-in-Depth", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f04", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f04.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 4", "ownerAnchor": "clm-k04-rep-051-f04", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "Digital-substation timing and protection logic are high-consequence dependencies that need authenticated time, path monitoring, redundant references, and physics-based validation.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f04", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "Bulk Electric System Interconnection and NERC CIP Compliance", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f05", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f05.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 5", "ownerAnchor": "clm-k04-rep-051-f05", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "Baseboard management controllers and other out-of-band components hold privileges below the host operating system and therefore require physically and logically separate management protection.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f05", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "Deterministic Network Topologies and Physical Isolation", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f06", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f06.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 6", "ownerAnchor": "clm-k04-rep-051-f06", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "Machine-learning detection should combine change, sequence, dependency, and physical-process analysis because no single detector covers abrupt, slow, coordinated, and stealthy manipulation.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f06", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "Unidirectional Gateways and Optical Isolation Mechanisms", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f07", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f07.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 7", "ownerAnchor": "clm-k04-rep-051-f07", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "Cyber response must be checked against reactor, electrical, cooling, and datacenter state before isolation or load-shedding is executed.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f07", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "Microsegmentation and Zero Trust Identity in OT Environments", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f08", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f08.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 8", "ownerAnchor": "clm-k04-rep-051-f08", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "Microgrid continuity requires tested islanding, stable load rejection, protected black-start paths where available, and recovery priorities for safety and mission loads.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f08", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "Substation Synchronization and Protocol-Level Vulnerabilities", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f09", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f09.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 9", "ownerAnchor": "clm-k04-rep-051-f09", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "Hardware roots of trust, signed firmware, protected boot, post-quantum migration planning, and supply-chain evidence support resilience but do not prove current operation or freedom from compromise.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f09", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "The Precision Time Protocol (IEEE 1588\\) and Time Synchronization Attacks", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/autonomous-cyber-protection-nuclear-powered-compute/#clm-k04-rep-051-f10", "claimStatus": "PROJECT TECHNICAL PROPOSAL", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-051-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-051-f10.json", "name": "Autonomous Cyber Protection Architecture for Nuclear-Powered Mega Datacenters — finding 10", "ownerAnchor": "clm-k04-rep-051-f10", "ownerId": "REP-K04-051", "ownerRoute": "/research/autonomous-cyber-protection-nuclear-powered-compute/", "ownerType": "report", "proposition": "The architecture should publish readiness and incident evidence without exposing safeguards or sensitive facility details.", "qualification": "The report contains specific technology, vulnerability, regulatory, and performance claims that require current primary-source and design review. K04 preserves architecture-level lessons and does not endorse product-specific claims or uncontrolled automation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-051; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-051-f10", "sourceIds": [], "sourceReport": { "filename": "nuclear-datacenter-cyber-defense.md", "id": "REP-K04-051", "originalFilename": "Nuclear Datacenter Cyber Defense(2).md", "sha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "sizeBytes": 69718 }, "sourceSections": [ { "section": "The Baseboard Management Controller (BMC) Threat Vector", "sourceFilename": "nuclear-datacenter-cyber-defense.md", "sourceReportId": "REP-K04-051", "sourceSha256": "617853fa24b45ae420b04ae228c64c82514a2e968c2f466ad15263d0a8dd2ea7", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f01.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 1", "ownerAnchor": "clm-k04-rep-043-f01", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "The report argues that speed, attacker advantage, covert persistence, and dormant access can make perimeter-only defense insufficient against known cyber threat groups.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f01", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "Introduction to Proactive Cyber Operations", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f02.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 2", "ownerAnchor": "clm-k04-rep-043-f02", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "It states that Article 51 analysis depends on whether the prospective cyber effects would reach the scale and effects of an armed attack, while espionage, theft, and lower-level disruption often remain below that threshold.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f02", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "The Evolving Threat Landscape: The Rise of Non-State Actors and Known Groups", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f03.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 3", "ownerAnchor": "clm-k04-rep-043-f03", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "It identifies cumulative effects as a contested method for evaluating sustained campaigns whose individual operations may remain below an armed-attack threshold.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f03", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "The Blurring of State and Non-State Actors", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f04.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 4", "ownerAnchor": "clm-k04-rep-043-f04", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "It applies contextual imminence and the last-possible-window concept to circumstances in which waiting for a final activation command would eliminate the defender's practical ability to prevent catastrophic effects.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f04", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "The Inadequacy of Perimeter Defense", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f05.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 5", "ownerAnchor": "clm-k04-rep-043-f05", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "It identifies capability, verifiable hostile intent, target access, and exhaustion or inadequacy of timely alternatives as necessary evidence categories for any anticipatory cyber-defense claim.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f05", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "The International Legal Framework: Anticipatory Self-Defense in Cyberspace", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f06.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 6", "ownerAnchor": "clm-k04-rep-043-f06", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "It distinguishes action against a non-state threat group from attribution of that group to a host state and treats unable-or-unwilling reasoning as legally controversial rather than automatically dispositive.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f06", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "The Threshold of an \"Armed Attack\"", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f07.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 7", "ownerAnchor": "clm-k04-rep-043-f07", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "It presents persistent engagement and deterrence by denial as strategic approaches intended to impose continuing friction and deny adversary freedom of action.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f07", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "The Caroline Doctrine and Anticipatory Self-Defense", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f08.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 8", "ownerAnchor": "clm-k04-rep-043-f08", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "It surveys divergent national approaches ranging from continuous proactive operations to constitutional and legal restrictions on hack-back and extraterritorial disruption.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f08", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "Redefining Imminence: The \"Last Possible Window of Opportunity\"", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f09.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 9", "ownerAnchor": "clm-k04-rep-043-f09", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "It identifies mistaken attribution, third-party infrastructure damage, intelligence exposure, sovereignty violations, and unintended escalation as principal failure modes.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f09", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "Preempting Non-State Actors and the Sovereignty Dilemma", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f10.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 10", "ownerAnchor": "clm-k04-rep-043-f10", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "K04 treats consent-based hunt-forward activity, law-enforcement disruption, countermeasures, self-defense, and unconsented offensive operations as distinct legal and operational categories.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f10", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "Strategic Rationales: Moving Beyond Deterrence by Punishment", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-cyber-operations-known-threat-groups/#clm-k04-rep-043-f11", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-043-F11", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-043-f11.json", "name": "The Strategic and Legal Dimensions of Preemptive Cyber Operations Against Known Threat Groups: A Global Perspective — finding 11", "ownerAnchor": "clm-k04-rep-043-f11", "ownerId": "REP-K04-043", "ownerRoute": "/research/preemptive-cyber-operations-known-threat-groups/", "ownerType": "report", "proposition": "The report does not itself authorize an operation, establish imminence, identify a lawful target, or substitute for current intelligence, competent authority, legal review, and mission-specific safeguards.", "qualification": "The source advances arguments in favor of proactive cyber operations and surveys national doctrines. K04 preserves the strategic case while separating it from current legal authorization, verified intelligence, rules of engagement, target approval, and primary-source validation of time-sensitive national policies.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 11 from report REP-K04-043; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-043-f11", "sourceIds": [], "sourceReport": { "filename": "preemptive-cyber-operations-justifications.md", "id": "REP-K04-043", "originalFilename": "Preemptive Cyber Attack Justifications(1).md", "sha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "sizeBytes": 56022 }, "sourceSections": [ { "section": "Global Doctrines and Case Studies: The Framing of Preemption", "sourceFilename": "preemptive-cyber-operations-justifications.md", "sourceReportId": "REP-K04-043", "sourceSha256": "02e012557c47ad34b39229eeb674772cf4b61b1c601e0d6d96232f64e80e786c", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f01.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 1", "ownerAnchor": "clm-k04-rep-042-f01", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "The report places Article 2(4) and Article 51 of the UN Charter at the center of the use-of-force analysis and treats anticipatory action as an exception requiring a demanding legal basis.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f01", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "Introduction", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f02.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 2", "ownerAnchor": "clm-k04-rep-042-f02", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "It uses the Caroline formulation to frame anticipatory self-defense around necessity that is instant and overwhelming, a lack of practical alternatives, and a response bounded by proportionality.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f02", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "The Jurisprudential Architecture of Anticipatory Self-Defense", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f03.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 3", "ownerAnchor": "clm-k04-rep-042-f03", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "It distinguishes a preemptive strike against an imminent, materializing attack from a preventive war directed at a more distant or projected change in the balance of power.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f03", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "Taxonomy of Anticipatory Force: Preemption vs. Prevention", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f04.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 4", "ownerAnchor": "clm-k04-rep-042-f04", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "It warns that states can manipulate terminology by describing preventive action as preemption, making evidence of timing, intent, capability, necessity, and alternatives central to review.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f04", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "The Threat of Non-State Actors and the \"Unwilling or Unable\" Doctrine", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f05.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 5", "ownerAnchor": "clm-k04-rep-042-f05", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "It analyzes the unable-or-unwilling doctrine as an effort to address threats from non-state actors operating in another state, while preserving the doctrine's disputed legal status and sovereignty implications.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f05", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "Deconstructing the Doctrine", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f06.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 6", "ownerAnchor": "clm-k04-rep-042-f06", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "It describes contextual imminence as an assessment of capability, intent, probability, continuing activity, anticipated harm, and the last practical window for prevention rather than timing alone.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f06", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "Global Reactions and Second-Order Implications", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f07.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 7", "ownerAnchor": "clm-k04-rep-042-f07", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "It uses comparative state practice to show that legal framing and strategic signaling vary substantially by region, threat type, and political context.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f07", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "Redefining \"Imminence\": The Bethlehem Principles", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f08.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 8", "ownerAnchor": "clm-k04-rep-042-f08", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "It identifies escalation, reciprocal precedent, weakened collective-security institutions, and lower thresholds for force as systemic risks of normalizing expansive preemption doctrines.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f08", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "Contextual Imminence vs. Temporal Imminence", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f09.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 9", "ownerAnchor": "clm-k04-rep-042-f09", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "It concludes that a defensible anticipatory-force framework requires objective evidence, explicit decision authority, documented alternatives, proportionality analysis, review, and correction rather than unilateral labels alone.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f09", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "Third-Order Insights on Contextual Imminence", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/preemptive-force-strategic-and-legal-dimensions/#clm-k04-rep-042-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-042-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-042-f10.json", "name": "The Strategic and Legal Dimensions of Preemptive Force: Global Paradigms and the Mitigation of Emergent Threats — finding 10", "ownerAnchor": "clm-k04-rep-042-f10", "ownerId": "REP-K04-042", "ownerRoute": "/research/preemptive-force-strategic-and-legal-dimensions/", "ownerType": "report", "proposition": "K04 preserves the report as a bounded research input and does not treat its legal characterizations or examples as universally accepted current law.", "qualification": "The report is a strategic and legal research synthesis, not a dispositive legal opinion. Historical and recent state-practice examples must be checked against primary records, and contested doctrines must remain labeled as disputed rather than converted into settled law.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-042; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-042-f10", "sourceIds": [], "sourceReport": { "filename": "preemptive-force-justification-analysis.md", "id": "REP-K04-042", "originalFilename": "Preemptive Attacks Justification Analysis(1).md", "sha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "sizeBytes": 51689 }, "sourceSections": [ { "section": "Global Manifestations: State Practice and Justifications", "sourceFilename": "preemptive-force-justification-analysis.md", "sourceReportId": "REP-K04-042", "sourceSha256": "00a75ebdd9abafc7ce8bef33065f622edb958fffd546f08340678efc48b11ed0", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f01.json", "name": "Single-Character Runic Internationalized Domain Names — finding 1", "ownerAnchor": "clm-k04-rep-065-f01", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "The report distinguishes Unicode validity, IDNA validity, registry permission, registrar support, registration, delegation, DNS resolution, and hosted service operation.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f01", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "The Genesis of the Domain Name System and the Ascendancy of ASCII", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f02.json", "name": "Single-Character Runic Internationalized Domain Names — finding 2", "ownerAnchor": "clm-k04-rep-065-f02", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "A U-label is human-readable Unicode while an A-label is its ASCII-compatible IDNA representation.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f02", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "The Internationalized Domain Name Framework", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f03.json", "name": "Single-Character Runic Internationalized Domain Names — finding 3", "ownerAnchor": "clm-k04-rep-065-f03", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "Punycode is an encoding mechanism, not a registration right or security guarantee.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f03", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "The IDNA2003 Standard and Character Mapping", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f04.json", "name": "Single-Character Runic Internationalized Domain Names — finding 4", "ownerAnchor": "clm-k04-rep-065-f04", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "IDNA processing occurs in applications and does not require changing the DNS protocol itself.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f04", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "The IDNA2008 Revision and Property-Based Inclusion", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f05.json", "name": "Single-Character Runic Internationalized Domain Names — finding 5", "ownerAnchor": "clm-k04-rep-065-f05", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "Registry and registrar policy can reject a technically encodable label.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f05", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "U-Labels, A-Labels, and the Bootstring Algorithm", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f06.json", "name": "Single-Character Runic Internationalized Domain Names — finding 6", "ownerAnchor": "clm-k04-rep-065-f06", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "A registered name may still be undelegated, non-resolving, misconfigured, uncertificated, or not hosting a site.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f06", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "The Mathematical Mechanics of Punycode (RFC 3492\\)", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f07.json", "name": "Single-Character Runic Internationalized Domain Names — finding 7", "ownerAnchor": "clm-k04-rep-065-f07", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "Browser display can fall back to A-labels because of script and confusability policy.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f07", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "The Anglo-Saxon Fuþorc in Historical and Technical Context", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f08.json", "name": "Single-Character Runic Internationalized Domain Names — finding 8", "ownerAnchor": "clm-k04-rep-065-f08", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "TLS, DNSSEC, RDAP, SMTPUTF8, and email-address internationalization have separate operational requirements.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f08", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "Fuþorc-Only Explanatory Prose", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f09.json", "name": "Single-Character Runic Internationalized Domain Names — finding 9", "ownerAnchor": "clm-k04-rep-065-f09", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "K08 preserves all owner-required Runic U-labels and their verified ACE mappings in static navigation records.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f09", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "The Eight Distinct States of Domain Name Viability", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/runic-idn-architecture/#clm-k04-rep-065-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K03 RECORD", "id": "CLM-K04-REP-065-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-065-f10.json", "name": "Single-Character Runic Internationalized Domain Names — finding 10", "ownerAnchor": "clm-k04-rep-065-f10", "ownerId": "REP-K08-065", "ownerRoute": "/research/runic-idn-architecture/", "ownerType": "report", "proposition": "The active synthesis avoids claiming that a code point or Punycode conversion proves live ownership, delegation, or service availability.", "qualification": "The active synthesis preserves the proposal or research finding while rejecting any inference that Runic notation, linguistic age, a benchmark estimate, a signature, a domain encoding, or a report proves superiority, security, authority, truth, deployment, operation, or historical translation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K08-065; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-065-f10", "sourceIds": [], "sourceReport": { "filename": "runic-idn-technical-research.md", "id": "REP-K08-065", "originalFilename": "Runic IDN Technical Research(2).md", "sha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "sizeBytes": 76408 }, "sourceSections": [ { "section": "1\\. Unicode-Valid", "sourceFilename": "runic-idn-technical-research.md", "sourceReportId": "REP-K08-065", "sourceSha256": "ddb2e139f5acc5926ef48b0492572fe772c25aa4abc9721bd7a7f4533aef0252", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f01", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F01", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f01.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 1", "ownerAnchor": "clm-k04-rep-052-f01", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "Official Army sources describe Project Manager Cyber Warfare as a merged offensive and defensive portfolio intended to improve visibility, integration, and rapid delivery.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 1 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f01", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "The Modern Cyberspace Domain and the Paradigm of Constant Contact", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f02", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F02", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f02.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 2", "ownerAnchor": "clm-k04-rep-052-f02", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "Offense can inform defense through adversary knowledge, while defense can inform authorized operations through telemetry, vulnerabilities, and recovery evidence; access and mission permissions remain separate.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 2 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f02", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "Strategic Realignment: The Establishment of Project Manager Cyber Warfare", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f03", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F03", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f03.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 3", "ownerAnchor": "clm-k04-rep-052-f03", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "Cyber acquisition needs rapid prototyping, modular software, continuous evaluation, and flexible contracting because static multi-year delivery can become obsolete before fielding.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 3 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f03", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "Acquisition Agility and Modern Software Procurement", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f04", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F04", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f04.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 4", "ownerAnchor": "clm-k04-rep-052-f04", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "Full-spectrum cyber capability includes deployable defense, analytics, forensics, deception, threat emulation, development environments, and authorized offensive infrastructure.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 4 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f04", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "Overcoming the Bureaucratic Lag Through Alternative Authorities", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f05", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F05", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f05.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 5", "ownerAnchor": "clm-k04-rep-052-f05", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "Persistent engagement and defend-forward concepts seek continuing initiative and deterrence by denial rather than relying only on punishment after a major attack.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 5 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f05", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "The Financial Mechanism: Budget Activity 08 (BA-08)", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f06", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F06", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f06.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 6", "ownerAnchor": "clm-k04-rep-052-f06", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "Integration creates deconfliction challenges across military, intelligence, law-enforcement, allied, and contractor operations because one access can serve competing missions.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 6 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f06", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "User-Centered Design and Commercial Integration", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f07", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F07", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f07.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 7", "ownerAnchor": "clm-k04-rep-052-f07", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "Title, authority, funding, target approval, intelligence oversight, and operational command remain separate governance questions even inside a combined acquisition portfolio.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 7 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f07", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "The Architecture of Cyberspace Superiority: PM CW Portfolios", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f08", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F08", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f08.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 8", "ownerAnchor": "clm-k04-rep-052-f08", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "Commercial partners can contribute speed and specialized engineering, but government direction, data handling, export control, security clearance, and mission authorization remain material.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 8 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f08", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "Offensive Cyber Warfare Programs", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f09", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F09", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f09.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 9", "ownerAnchor": "clm-k04-rep-052-f09", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "Public positioning should claim ability to design, integrate, test, and support authorized missions rather than claim unrestricted independent offensive action.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 9 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f09", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "Defensive Cyber Warfare Programs", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" }, { "canonicalClaimUrl": "https://xn--mwe.com/research/unified-army-cyber-warfare-strategy/#clm-k04-rep-052-f10", "claimStatus": "RESEARCH FINDING", "correctionStatus": "CURRENT K04 RECORD", "id": "CLM-K04-REP-052-F10", "lastReviewed": "2026-08-16", "machineRecordUrl": "https://xn--mwe.com/data/claims/clm-k04-rep-052-f10.json", "name": "Unifying the Cyber Battlespace: Offensive Integration, Persistent Engagement, and the Strategic Mandate of Project Manager Cyber Warfare — finding 10", "ownerAnchor": "clm-k04-rep-052-f10", "ownerId": "REP-K04-052", "ownerRoute": "/research/unified-army-cyber-warfare-strategy/", "ownerType": "report", "proposition": "A serious contender demonstrates secure software delivery, evidence, modular interfaces, range testing, sustainment, and rapid correction—not only aggressive language.", "qualification": "Official Army sources now confirm the 2026 establishment of Project Manager Cyber Warfare and its combined portfolio. Other program, budget, legal, and future-fielding details in the report remain subject to exact primary-source validation.", "releaseId": "K12-2026-08-16", "releaseVersion": "2.1.0", "researchCutoff": "2026-08-16", "scope": "Governed finding 10 from report REP-K04-052; public reliance is limited to the report synthesis, source hash, correction state, and stated project claim status.", "slug": "clm-k04-rep-052-f10", "sourceIds": [], "sourceReport": { "filename": "us-army-cyber-defense-strategy.md", "id": "REP-K04-052", "originalFilename": "USAASC Cyber Defense Strategy(2).md", "sha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "sizeBytes": 56710 }, "sourceSections": [ { "section": "The Doctrinal Shift: Cyber Persistence Theory and Defend Forward", "sourceFilename": "us-army-cyber-defense-strategy.md", "sourceReportId": "REP-K04-052", "sourceSha256": "beb2999fcfdc26519995d5e76db73cc327bf16c733e5f816a89b30ca9e2cf4dc", "supportRelationship": "GOVERNED REPORT FINDING" } ], "type": "ClaimRecord" } ]