{ "checkedAt": "2026-09-21T18:19:12.097426+00:00", "models": [ { "id": "WM-XCT-012", "version": "0.3.0-research.1", "url": "https://ver.cy/models/wm-xct-012-provenance/", "files": [ { "name": "spec.yaml", "sha256": "aa6155354c55a87ab837ec9bd47f796ca582309fe383f1afffb802dafff7ecb5", "bytes": 271531, "publicMatchesLocal": true }, { "name": "AGENTS.md", "sha256": "a036444b2ea477073a32e1c8aa10ec14b4b35f953c98af029e29ea40e65fa9bb", "bytes": 904, "publicMatchesLocal": true }, { "name": "publication.json", "sha256": "a050d44bcdf079f5f02ae682c60722d2c3065bdf49581afbf988f3612451ca87", "bytes": 1181, "publicMatchesLocal": true } ], "model": { "registry_id": "vr.wm-xct-012", "model_id": "WM-XCT-012", "name": "Provenance", "entry_kind": "mixin", "purpose": "Provide a format-neutral, attachable provenance dimension that lets an agent state, verify and govern where a subject came from, what acted on it, who is responsible, in what custody it has been, and how strongly each of those statements is evidenced.", "scope_statement": "Provenance is modelled as a mix-in applied to a host subject (digital asset, dataset, record, software artifact, physical item, statement or agent output). It covers the origin, derivation graph, responsible agents, activities and plans, custody history, temporal and spatial context, integrity and attestation evidence, verification outcome and confidence, regulatory disclosure, discovery/access, redaction and retention of provenance itself. It does not define the subject's own domain semantics, nor does it re-define agents, rights, retention schedules, access policy or data-quality metrics that belong to composable sibling models; it references them. The model is storage- and interface-neutral: JSON, YAML, Markdown, RDF, JUMBF, Git, MCP and MongoDB are projections of these semantics, not the semantics.", "in_scope": [ "Origination: the activity, agent, instrument, place and time at which the subject first came into being, including capture context and whether the account is first-hand or reconstructed.", "Derivation and lineage: entity-to-entity relations (derivation, revision, quotation, primary source, ingredient, aggregation, transformation) and the traversable ancestor/descendant graph.", "Activities, process steps, plans, algorithms, build definitions and their parameters and resolved dependencies.", "Agents, agent types (person, organisation, software agent, mechanism, device), qualified roles, delegation and on-behalf-of responsibility.", "Chain of custody: successive holders, accession and transfer events, and changes in ownership or control significant to authenticity.", "Time semantics: separation of event/occurrence time from record/observation time, intervals, ordering constraints, invalidation and trusted timestamping.", "Integrity evidence: fixity digests, integrity methods, hard content bindings, soft bindings (watermark/fingerprint), signatures and seals.", "Attestation layer: who asserts the provenance, the signed envelope, trust anchors, credential status, revocation and validation outcome.", "Confidence, completeness, unknown provenance, inferred versus asserted statements, and reconciliation of conflicting provenance claims.", "Regulatory disclosure duties attached to provenance: machine-readable marking of synthetic content, training-data lineage summaries, source-of-personal-data disclosure.", "Discovery of and access to provenance records, provenance-of-provenance bundling, redaction, minimisation and selective disclosure.", "Retention, disposition and deletion of provenance records considered independently of the subject's own retention." ], "out_of_scope": [ "The host subject's substantive content model, schema or domain semantics (supplied by the host model into which this mix-in is composed).", "Rights, licence terms and permissions adjudication; provenance references a rights statement but does not define rights semantics.", "The authoritative registry and resolution of agent, organisation and person identity; provenance references governed agent identifiers.", "Access-control policy definition and enforcement; provenance records that an access decision occurred as evidence, it is not the policy engine.", "Definition of data-quality metrics and thresholds; provenance supplies evidence that quality assessment consumes.", "Retention schedules and disposition authorities as legal instruments; provenance cites the applicable schedule identifier.", "Cryptographic algorithm registries, key management, PKI and trust-list operation; provenance references keys, certificates and trust lists as external artefacts.", "Storage-layer mechanics of versioning systems, object stores, ledgers or content-addressed file layouts; these are projections.", "Business-process semantics of supply-chain steps, clinical workflows or build systems beyond the provenance facts they emit.", "Physical measurement and sensor semantics; provenance records the observation act, not the observable property model." ], "boundary_notes": [ { "neighbor": "Audit log / AuditEvent model", "distinction": "Provenance describes how an entity came to be and who is responsible for it; audit logging describes who accessed or attempted an operation on a system. FHIR draws the same line: Provenance is generation-focused while AuditEvent covers usage and other activity. Read events belong to the audit sibling unless they generated a new entity.", "source_refs": [ "SRC-010", "SRC-001" ] }, { "neighbor": "Version control / revision history model", "distinction": "A revision chain is one derivation relation (prov:wasRevisionOf, dcterms:isVersionOf) among many. Commit graphs, branches and merges are a storage projection; this model captures the derivation and responsibility facts that survive migration off any given VCS.", "source_refs": [ "SRC-001", "SRC-008" ] }, { "neighbor": "Rights and licensing model", "distinction": "dcterms:provenance covers changes in ownership and custody significant to authenticity, integrity and interpretation; it is not the licence. Rights holders and licence documents are referenced as external agents and documents.", "source_refs": [ "SRC-008", "SRC-017" ] }, { "neighbor": "Archival description model (fonds / respect des fonds)", "distinction": "In archival practice 'provenance' primarily denotes the creator and the accumulating body of a fonds; here that sense is carried by origination agent plus custody history, while the transformation graph is modelled separately. The homonym must be disambiguated when mapping to RiC-CM.", "source_refs": [ "SRC-016", "SRC-017" ] }, { "neighbor": "Software bill of materials (SBOM) model", "distinction": "An SBOM enumerates composition at a point in time; provenance states how that composition was produced and by whom. SPDX Element creation information and in-toto/SLSA build predicates are alignments, not the SBOM inventory itself.", "source_refs": [ "SRC-015", "SRC-006", "SRC-007" ] }, { "neighbor": "Supply-chain traceability event model (EPCIS)", "distinction": "EPCIS what/when/where/why events are an authoritative source of physical-object provenance, but the business-step and disposition vocabularies remain in the traceability sibling; this model consumes the events as origination, transfer and transformation facts.", "source_refs": [ "SRC-014" ] }, { "neighbor": "Geospatial lineage metadata", "distinction": "ISO 19115 lineage (statement, process step, source) is a domain projection of the same activity/entity structure; the geospatial resolution, reference system and citation fields stay with the geospatial metadata sibling.", "source_refs": [ "SRC-013" ] }, { "neighbor": "Content authenticity manifest (C2PA)", "distinction": "A C2PA manifest is a signed transport of provenance bound to a media asset. This model treats manifests, claims, assertions and ingredients as artefacts and evidence; JUMBF embedding, codec-specific box hashing and trust-list operation stay outside.", "source_refs": [ "SRC-005" ] }, { "neighbor": "Data quality model", "distinction": "Provenance is evidence for quality judgements (FAIR R1.2 requires detailed provenance) but does not define accuracy, completeness or fitness metrics; a quality assessment is itself an activity with its own provenance.", "source_refs": [ "SRC-018", "SRC-013" ] }, { "neighbor": "Records retention and disposition model", "distinction": "Disposition authorities, schedules and approval flows belong to the records sibling; provenance records the disposition event and retains the evidence that it happened, and may itself be subject to a different retention period than the subject.", "source_refs": [ "SRC-019", "SRC-011" ] } ] }, "composition": [ { "target": "Agent and Party model (person, organisation, position, software agent)", "relation": "REFERENCE", "purpose": "Provenance names responsible agents and their types and roles but must not maintain its own agent registry; agent identity, deduplication and organisational hierarchy are resolved externally.", "required": true, "source_refs": [ "SRC-001", "SRC-017", "SRC-016", "SRC-010" ] }, { "target": "Event and Activity model", "relation": "COMPOSE", "purpose": "Origination, transformation, transfer, disposition and verification acts are events; the provenance mix-in composes the shared event structure and adds provenance-specific roles for used, generated and invalidated entities.", "required": true, "source_refs": [ "SRC-001", "SRC-013", "SRC-014" ] }, { "target": "Identifier and Identity Scheme model", "relation": "REFERENCE", "purpose": "Supplies the identifier tiers and resolution behaviour that the identity priority rule depends on, including external identifier retention alongside locally minted identifiers.", "required": true, "source_refs": [ "SRC-015", "SRC-007" ] }, { "target": "Temporal model (instants, intervals, calendars, offsets)", "relation": "ALIGN", "purpose": "Provenance depends on a shared time representation with explicit offsets and separable occurrence and record axes; the temporal model owns calendar and interval semantics, provenance owns which axis means what.", "required": true, "source_refs": [ "SRC-010", "SRC-014", "SRC-002" ] }, { "target": "Place and Jurisdiction model", "relation": "REFERENCE", "purpose": "Activity location, read point, business location and governing jurisdiction are resolved against an external gazetteer and legal-order registry rather than defined here.", "required": false, "source_refs": [ "SRC-002", "SRC-014", "SRC-011" ] }, { "target": "Rights and Licensing model", "relation": "REFERENCE", "purpose": "Provenance records custody and ownership changes and points at rights statements and licences; the terms, permissions and obligations themselves are owned by the rights model.", "required": false, "source_refs": [ "SRC-008", "SRC-017" ] }, { "target": "Trust, Keys and Credentials model", "relation": "REFERENCE", "purpose": "Signer credentials, trust lists, revocation status and time authorities are external objects whose lifecycle provenance consumes but does not govern.", "required": true, "source_refs": [ "SRC-005", "SRC-006" ] }, { "target": "Records Retention and Disposition model", "relation": "REFERENCE", "purpose": "Retention schedules, disposition authorities and legal holds are defined externally; provenance cites the schedule and records the disposition event and its evidence.", "required": true, "source_refs": [ "SRC-019", "SRC-011" ] }, { "target": "Access and Authorization model", "relation": "REFERENCE", "purpose": "Visibility classes and audience views on provenance are enforced by the access model; provenance records the decision as evidence and does not implement policy.", "required": true, "source_refs": [ "SRC-004", "SRC-012" ] }, { "target": "Data Quality and Assessment model", "relation": "EXTEND", "purpose": "Quality assessment consumes provenance as evidence and, being itself an activity, generates provenance; the two models extend each other without either owning the other's vocabulary.", "required": false, "source_refs": [ "SRC-018", "SRC-013" ] }, { "target": "Content Asset and Dataset models (host subjects)", "relation": "MIX-IN", "purpose": "This model is applied to host entity models as a dimension; the host supplies the subject, its identifier stability and its version boundaries, and accepts the provenance application profile.", "required": true, "source_refs": [ "SRC-015", "SRC-009", "SRC-018" ] }, { "target": "W3C PROV family (PROV-DM, PROV-O, PROV-CONSTRAINTS, PROV-AQ)", "relation": "ALIGN", "purpose": "Primary external alignment for entity/activity/agent structure, qualified influence, validity constraints and discovery; alignment is recorded in the crosswalk and no conformance is claimed without validation evidence.", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ] }, { "target": "PREMIS Data Dictionary and archival description (RiC-CM)", "relation": "ALIGN", "purpose": "Alignment for preservation events, object granularity, fixity and for the creator/custody sense of provenance; the homonym between archival provenance and derivation lineage is recorded as a mapping caution.", "required": false, "source_refs": [ "SRC-017", "SRC-016" ] }, { "target": "Content authenticity and software supply-chain attestation (C2PA, in-toto/SLSA, SPDX)", "relation": "ALIGN", "purpose": "Alignment for signed transport, subject binding by digest, build provenance predicates and element-level creation information; these are evidence carriers, not replacements for the semantic model.", "required": false, "source_refs": [ "SRC-005", "SRC-006", "SRC-007", "SRC-015" ] }, { "target": "Traceability event exchange (GS1 EPCIS) and geospatial lineage (ISO 19115 MRL)", "relation": "ALIGN", "purpose": "Domain projections that supply authoritative origination, transfer and process-step facts; their business-step, disposition and geospatial vocabularies remain with those siblings.", "required": false, "source_refs": [ "SRC-014", "SRC-013" ] }, { "target": "Clinical provenance and audit (HL7 FHIR Provenance and AuditEvent)", "relation": "ALIGN", "purpose": "Alignment for the occurred-versus-recorded distinction, entity roles and the generation-versus-usage boundary that separates provenance from audit logging.", "required": false, "source_refs": [ "SRC-010" ] } ], "holds": [ "Verify live availability, version pins and exact claim support for every source accepted into the synthesis.", "Create and test sector profiles for archival records, geospatial data, clinical records, software supply chains and media authenticity before promoting a universal completeness claim." ], "scope": "Full specification recursively inventoried and compared to public bytes; prior source holds not discharged." }, { "id": "WM-XCT-026", "version": "0.3.0-research.1", "url": "https://ver.cy/models/wm-xct-026-quality-confidence/", "files": [ { "name": "spec.yaml", "sha256": "efd72d845af742b7aa7d7592e5f6087ef034145f468a799927163cd6eb599ee5", "bytes": 262013, "publicMatchesLocal": true }, { "name": "AGENTS.md", "sha256": "b9273d197400bacda57f1469b660a581c29e970cd2bf9cfb618632720e8c0f94", "bytes": 940, "publicMatchesLocal": true }, { "name": "publication.json", "sha256": "4bc65c29070931eea776f3dbf2f5e2dce930cf056832a456f2d676b297b3c28a", "bytes": 2850, "publicMatchesLocal": true } ], "model": { "registry_id": "vr.wm-xct-026", "model_id": "WM-XCT-026", "name": "Quality / Confidence", "entry_kind": "mixin", "purpose": "Provide a format-neutral, attachable structure for asserting, computing, evidencing and governing quality dimensions, measures, scores, assessment methods, uncertainty and confidence about any subject, so that an agent can decide whether the subject is fit for a stated purpose and can defend that decision with evidence.", "scope_statement": "WM-XCT-026 models the quality/confidence ASSERTION as a first-class, separately identified, attributable and time-stamped record about some other subject. It covers: what is assessed and at what granularity; which dimension and which registered measure are used; the method, sampling and reference basis; the result value, its scale and its uncertainty; a confidence statement about the assertion itself, its declared scale and its evidential basis; conformance against a stated requirement; declared fitness for purpose and limitations; validity in time; lifecycle and supersession; attribution and provenance; comparability, disagreement, access and retention. It does NOT model the subject's own semantics, nor units, provenance graphs, identifier minting, constraint languages, risk of harm or agent trust, all of which belong to composable sibling models. Storage and interface (JSON, YAML, Markdown, RDF, Git, MCP, MongoDB) are projections of this structure, never its semantics. W3C DQV is used as the primary structural anchor precisely because it deliberately refuses to prescribe a single definition of quality and instead standardises the shape of comparable assessments.", "in_scope": [ "Quality assertions attached to any host entity, event, dataset, model output, artifact or process step", "Dimension/category vocabularies and registered quality measures with parameters, value type and value structure", "Assessment method: procedure, evaluation environment, full inspection versus sampling, reference/ground-truth basis", "Result expression: value, scale type, value structure, unit reference, aggregation and composite scores", "Measurement uncertainty and error models, including coverage interval, coverage probability and coverage factor", "Confidence as an explicit statement about the assertion, with a declared scale, evidential basis and calibration claim", "Requirements, acceptance thresholds, decision rules, conformance verdicts and severity", "Declared intended use, fitness-for-purpose judgement and explicit limitations, caveats and known defects", "Temporal validity, currency, re-assessment cadence, lifecycle states, supersession and retraction", "Attribution, competence, independence of the assessor, and provenance/lineage of derived assertions", "Comparability rules, competing assessments, disagreement and rectification", "Access classification, disclosure, retention and deletion of quality statements and their evidence" ], "out_of_scope": [ "The subject's own domain semantics, payload or business rules", "Definition of units, quantity kinds and unit conversion (Measurement & Units sibling model)", "General provenance graph semantics and activity modelling (Provenance & Attribution sibling model)", "Identifier minting policy and identifier scheme registration (Identifier sibling model)", "Constraint/shape languages and the authoring of validation rules (Validation & Constraint sibling model)", "Risk, hazard and likelihood of harm; confidence in an assertion is not a risk score (Risk sibling model)", "Trust, reputation and accreditation of agents as standalone subjects (Agent/Party and Certification sibling models)", "Statistical and machine-learning method definitions themselves (Method/Analysis sibling model)", "Licensing, rights and terms of use of the subject", "Orchestration of monitoring pipelines and job scheduling (Process sibling model)", "Sensitive-data classification schemes as such; this model only carries the classification assigned to a quality statement" ], "boundary_notes": [ { "neighbor": "Validation & Conformance (SHACL-style constraint checking)", "distinction": "SHACL yields binary conformance: a focus node either conforms or produces results, and sh:resultSeverity (Violation/Warning/Info) is organisational rather than a graded score. WM-XCT-026 carries graded, scaled and uncertain assessments. A validation report is therefore an INPUT artifact to a quality assertion, not a substitute for it; conversely a quality score must never be presented as conformance without an explicit requirement and decision rule.", "source_refs": [ "SRC-007", "SRC-003" ] }, { "neighbor": "Provenance & Attribution", "distinction": "DQV itself reuses PROV for who produced a quality statement, when, and from what. This model references prov:wasAttributedTo / prov:wasGeneratedBy / prov:wasDerivedFrom rather than redefining provenance; it owns only the quality-specific slots (assessor competence, independence, method, evidence).", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "Measurement & Units", "distinction": "Uncertainty semantics (standard/expanded uncertainty, coverage interval, coverage probability, coverage factor, metrological traceability) are consumed from JCGM GUM/VIM; unit identifiers are referenced (DQV recommends sdmx-attribute:unitMeasure with dereferenceable unit definitions) and never minted here.", "source_refs": [ "SRC-004", "SRC-005", "SRC-001" ] }, { "neighbor": "Risk & Harm", "distinction": "Confidence is a statement about the strength of an assessment, not a probability of harm and not an expected loss. Frameworks that grade certainty of evidence (GRADE) keep the certainty rating strictly separate from the effect estimate; this model preserves that separation and forbids arithmetic between confidence grades and risk scores.", "source_refs": [ "SRC-015", "SRC-017" ] }, { "neighbor": "Evidence & Attestation / Verifiable Credentials", "distinction": "A signed attestation carries issuer, proof, status and an evidence property, but W3C VC Data Model 2.0 defines no confidence property; assurance is derived by the verifier from issuer, proof, evidence and status. This model supplies the confidence semantics and treats the credential as a transport and integrity wrapper.", "source_refs": [ "SRC-018" ] }, { "neighbor": "Sensing systems and system capability (SSN/SOSA)", "distinction": "ssn-system states device capabilities (Accuracy, Precision, Resolution, Drift, Latency) qualified by Condition, i.e. quality of an instrument under stated conditions. That is a capability declaration about a system, not an assessment of a produced result. WM-XCT-026 may cite such a capability as method context but keeps assertion-level results separate.", "source_refs": [ "SRC-008" ] }, { "neighbor": "Catalogue/Dataset description (DCAT-style records)", "distinction": "A catalogue record describes availability and access; quality metadata is attached to it via a quality-metadata container rather than embedded as descriptive fields, so that quality statements can carry their own provenance, validity and access rules.", "source_refs": [ "SRC-001", "SRC-019" ] } ] }, "composition": [ { "target": "Any host world-model entry that requires quality or confidence qualification", "relation": "MIX-IN", "purpose": "Attach quality assertions to any subject through a quality-metadata container and a subject reference, without modifying or duplicating the host's own semantics. DQV's pattern of linking quality statements to an assessed resource is the template.", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "Provenance & Attribution mixin (sibling; identifier to be assigned by the registry)", "relation": "REFERENCE", "purpose": "Resolve who generated a quality assertion, from what, and when. DQV itself delegates this to PROV rather than restating it, so this model references generation, attribution and derivation instead of redefining them.", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "Measurement, Units & Quantity Kinds model (sibling)", "relation": "REFERENCE", "purpose": "Resolve dereferenceable unit identifiers and quantity kinds for quantitative results; DQV recommends a dereferenceable unit reference rather than a unit string, and VIM supplies the metrological vocabulary.", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "Validation & Constraint results model (sibling)", "relation": "COMPOSE", "purpose": "Consume binary conformance results with focus node, source shape, constraint component and severity as evidence inputs to graded quality assertions, keeping validation authoring out of this model.", "required": false, "source_refs": [ "SRC-007", "SRC-003" ] }, { "target": "Agent / Party & Role model (sibling)", "relation": "REFERENCE", "purpose": "Resolve assessor identity, role, accreditation and organisational affiliation used for attribution, competence and independence classification.", "required": true, "source_refs": [ "SRC-006", "SRC-016" ] }, { "target": "Evidence & Attestation model (sibling)", "relation": "COMPOSE", "purpose": "Carry issued quality certificates and attestations with issuer, securing mechanism, status and evidence, providing tamper-evidence and revocation that this model does not define.", "required": false, "source_refs": [ "SRC-018", "SRC-001" ] }, { "target": "Quality measure register (nested registry within this model's governance scope)", "relation": "CHILD", "purpose": "Hold registered measure items with identifier, version, status and supersession, maintained under registration procedures; nested rather than sibling because measure semantics are inseparable from result semantics.", "required": true, "source_refs": [ "SRC-012", "SRC-020", "SRC-003" ] }, { "target": "Sampling & Statistical Population model (sibling)", "relation": "REFERENCE", "purpose": "Resolve frames, sampling designs, achieved samples and representativeness claims that determine whether a measured value generalises to the declared scope.", "required": false, "source_refs": [ "SRC-003", "SRC-011" ] }, { "target": "Risk & Harm model (sibling)", "relation": "ALIGN", "purpose": "Align confidence and quality inputs to risk assessment without merging them: measurement and evidence assessment is a distinct governed activity from risk treatment, and confidence grades must not be arithmetically combined with risk scores.", "required": false, "source_refs": [ "SRC-017", "SRC-015" ] }, { "target": "Access & Disclosure Policy model (sibling)", "relation": "REFERENCE", "purpose": "Resolve classification schemes, redaction profiles and authorisation decisions applied to quality statements and evidence packages, which this model classifies but does not define.", "required": true, "source_refs": [ "SRC-014", "SRC-013" ] }, { "target": "Records Retention & Disposition model (sibling)", "relation": "REFERENCE", "purpose": "Resolve retention classes, schedules, legal holds and disposition actions covering assertions and evidence under conflicting retention and erasure duties.", "required": true, "source_refs": [ "SRC-013", "SRC-014" ] }, { "target": "ISO/IEC 25012 and ISO/IEC 5259-2 data quality dimension vocabularies", "relation": "ALIGN", "purpose": "Bind dimension terms from published vocabularies rather than embedding a proprietary list; alignment strength is recorded per term and conformance is not claimed without test evidence.", "required": false, "source_refs": [ "SRC-002", "SRC-010", "SRC-001" ] }, { "target": "ISO 19157-1 data quality measure component structure", "relation": "ALIGN", "purpose": "Align the measure definition slots (identifier, name, definition, parameters, value type, value structure, source reference) and the scope/evaluation/reporting separation to a published component structure.", "required": false, "source_refs": [ "SRC-003", "SRC-020" ] }, { "target": "Sensing System Capability model (sibling, SSN/SOSA-aligned)", "relation": "ALIGN", "purpose": "Reference declared instrument capabilities qualified by operating conditions as method context, while keeping capability declarations distinct from assessments of produced results.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "Dataset / Catalogue record model (sibling)", "relation": "EXTEND", "purpose": "Extend catalogue records with attached quality metadata containers so that quality carries its own provenance, validity and access rules instead of becoming inert descriptive fields.", "required": false, "source_refs": [ "SRC-001", "SRC-019" ] } ], "holds": [ "Source verification is incomplete: normalise the base's ISO citations from the unusual committee.iso.org/es/sites/... paths to canonical iso.org/standard/NNNNN.html forms as used by the source provider, re-resolve every one of the twenty base URLs live, and re-pin access dates before publication.", "Verify the JCGM version pins actually asserted by the base (JCGM 100:2008 with Amendment 1:2026, GUM-1:2023, GUM-5:2026, GUM-6:2020, JCGM 106:2012). The base states it read the publications index and the annotated VIM but not the full text of JCGM 100 or 106, so all clause-level claims about decision rules and guard bands remain unverified and must not be published as normative guidance.", "Recheck the publication status of ISO/FDIS 19157-3, the strongest available anchor for measure-register governance, which the base records as still at final-draft stage. Until it is published, measure-register governance must remain marked as a defensible pattern rather than a normative requirement.", "Reconcile the authority tier assigned to W3C DQV. It is a Working Group Note, not a Recommendation; the base treats it as tier-1 and its primary structural anchor while the source provider assigns tier 2. Either downgrade the tier or state explicitly why a non-normative Note is load-bearing for the model's shape.", "Multi-profile validation is not complete. The model has been reasoned over data, geospatial and ML/analytics hosts only; the base records a robotics factor of zero and supplies no bindings for images, audio, code, physical goods or sensing. Validate against at least three concrete domain profiles before publication and state the untested profiles explicitly.", "Verify the ISO/IEC 25012 fifteen-characteristic set and the ISO 19157-1 element set from licensed normative text before publishing any bound vocabulary profile derived from them; both providers relied on catalogue records for these enumerations." ], "scope": "Full specification recursively inventoried and compared to public bytes; prior source holds not discharged." }, { "id": "WM-XCT-028", "version": "0.3.0-research.1", "url": "https://ver.cy/models/wm-xct-028-evidence-rationale/", "files": [ { "name": "spec.yaml", "sha256": "3aab7ecb4ba7d4e56d650060b982058c4253e5bcbd621e2784480e8cc4f3d636", "bytes": 318948, "publicMatchesLocal": true }, { "name": "AGENTS.md", "sha256": "b1d33b77202844436e0e63052562a6b4e81ab510a610daa37e03202de8ab63e0", "bytes": 940, "publicMatchesLocal": true }, { "name": "publication.json", "sha256": "bf54ee49b104d11fc7334e00f317b589c3d10ac82d42bbc37828009f6b71aa6f", "bytes": 2793, "publicMatchesLocal": true } ], "model": { "registry_id": "vr.wm-xct-028", "model_id": "WM-XCT-028", "name": "Evidence / Rationale", "entry_kind": "mixin", "purpose": "Provide a format-neutral, attachable structure that records traceable support for a claim or decision: what supports it, by what reasoning, on whose authority, with what integrity, how strong the support is, and how it can be re-checked, contested, retained or withdrawn.", "scope_statement": "This mixin is attached to a host record that already asserts something (a claim, decision, classification, requirement or measurement held in a sibling model). It supplies the support apparatus around that assertion: typed support relations to evidence items, the inference/warrant and assumptions that license the conclusion, counter-evidence and its resolution, evidence identity, anchoring into sources, acquisition and custody, provenance and time, cryptographic integrity and verification, quality appraisal and sufficiency, and the governance surface (authority, rights, access, retention, lifecycle, interoperability). It never carries the propositional content of the claim itself and never duplicates the bibliographic record of a source, the agent registry or the audit-log infrastructure.", "in_scope": [ "Typed support and counter-support relations between evidence items and a supported claim or decision", "Reasoning apparatus: warrant/inference, argumentation scheme, assumptions, scope conditions, alternatives considered and rejected", "Evidence item identity, form/modality, anchoring into a source location and state, and excerpt fidelity", "Acquisition method, instrument, and chain of custody including auditability, repeatability and reproducibility", "Provenance, attribution, independence/conflict of interest, and separated event/observation/record/assertion times", "Cryptographic content binding, signatures/attestations, trusted timestamps and verification events", "Certainty grading against a declared scheme, bias and limitations, sufficiency thresholds and corroboration", "Governance of the support record: ownership, approving authority, rights, access classification, redaction, retention, legal hold, lifecycle states and retraction", "Declared alignments and exchange packaging to external provenance, assurance-case, credential and attestation models" ], "out_of_scope": [ "The propositional content, truth value or semantics of the supported claim itself (belongs to the parent knowledge/claim model)", "The full bibliographic or catalogue record of a source document, dataset or publication (sibling source/citation model)", "The agent, organisation and role registry that identifiers here resolve into (sibling agent/party model)", "General-purpose provenance/lineage of arbitrary artefacts not offered in support of a claim (sibling provenance model)", "Audit-log and telemetry infrastructure design, log shipping and SIEM operation", "Legal case management, court procedure, disclosure workflow and forensic investigation case files", "Evidence synthesis statistics: meta-analysis, pooling, effect-size estimation and study design", "Dialogue and argumentation protocols (turn taking, burden shifting in dialogue games)", "Trust or reputation scoring of agents and sources as a standalone scored model", "Cryptographic key management, PKI operation and trust-list curation" ], "boundary_notes": [ { "neighbor": "WM-KNW-008 (parent knowledge/claim model)", "distinction": "The parent holds the assertion; this mixin holds why the assertion is held. An assurance case separates the top-level claim from the structured argumentation and the evidence and assumptions underlying it, so the claim must remain addressable independently of its support.", "source_refs": [ "SRC-006", "SRC-005" ] }, { "neighbor": "Source / citation / bibliographic model", "distinction": "This model references a source by identifier and adds a locator, selector and captured state; it does not carry title, authorship, edition or catalogue metadata. Web Annotation separates the Target resource from the Specific Resource plus Selector used to address part of it.", "source_refs": [ "SRC-004", "SRC-013" ] }, { "neighbor": "Provenance / lineage model", "distinction": "PROV describes generation, derivation and attribution for any entity. This mixin uses that vocabulary only for entities offered in support of a claim, and additionally records the assertion of support itself, which PROV does not model.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "Attestation / verifiable credential model", "distinction": "A verifiable credential is itself a signed claim container whose optional evidence property describes how the issuer verified claims before issuance. A credential may be an evidence item here, but credential issuance, holding and presentation are governed elsewhere.", "source_refs": [ "SRC-003" ] }, { "neighbor": "Audit trail / event log model", "distinction": "Automatically generated logs are a source of evidence items and are separately mandated with their own retention floors; the logging subsystem, its content requirements and its retention schedule belong to the log model, not to this mixin.", "source_refs": [ "SRC-015", "SRC-018" ] }, { "neighbor": "Digital forensic case model", "distinction": "ISO/IEC 27037 governs identification, collection, acquisition and preservation of potential digital evidence by designated roles. This mixin records the custody and integrity facts needed to reason about admissibility, not the forensic process, tooling competence regime or investigation case file.", "source_refs": [ "SRC-008" ] }, { "neighbor": "Decision record model", "distinction": "The decision, its options and its outcome live in the decision model. This mixin supplies the rationale, alternatives-rejected reasons and supporting evidence attached to that decision, in the same way an architecture description carries rationale separately from the architecture it describes.", "source_refs": [ "SRC-007" ] }, { "neighbor": "Measurement / observation model", "distinction": "An observation's method, unit, uncertainty and sensor semantics belong to the measurement model. Here an observation is treated as an evidence item with an acquisition record and an appraisal, not re-specified.", "source_refs": [ "SRC-014", "SRC-008" ] } ] }, "composition": [ { "target": "WM-KNW-008 (parent knowledge/claim model)", "relation": "CHILD", "purpose": "This mixin is a child of the knowledge model and attaches to the assertion it holds; the claim remains addressable and meaningful without support, and the support is meaningless without the claim.", "required": true, "source_refs": [ "SRC-006", "SRC-005" ] }, { "target": "Decision record model (decision, options, outcome)", "relation": "MIX-IN", "purpose": "Supplies rationale, alternatives-rejected reasons, assumptions and supporting evidence to a recorded decision, in the same way rationale is recorded as description content separate from the thing described.", "required": false, "source_refs": [ "SRC-007", "SRC-006" ] }, { "target": "Source / citation / bibliographic model", "relation": "REFERENCE", "purpose": "Resolves source-ref to a described source; this model contributes only the locator, selector, captured state and citation intent, never the bibliographic description.", "required": true, "source_refs": [ "SRC-004", "SRC-013" ] }, { "target": "Agent / party / organisation registry", "relation": "REFERENCE", "purpose": "Resolves every agent reference \u2014 asserter, custodian, signer, grader, approver, adjudicator \u2014 to a governed party record with roles and delegation.", "required": true, "source_refs": [ "SRC-002", "SRC-001" ] }, { "target": "Provenance / lineage model", "relation": "COMPOSE", "purpose": "Composes entity, activity and agent lineage with derivation, generation and attribution relations for evidence items, and treats the provenance bundle as itself an attributable entity.", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "Access classification and authorisation model", "relation": "REFERENCE", "purpose": "Resolves classification codes and access conditions; this model contributes only evidence-specific exceptions such as privilege claims and redaction maps.", "required": true, "source_refs": [ "SRC-018", "SRC-016" ] }, { "target": "Records retention and disposition model", "relation": "REFERENCE", "purpose": "Resolves retention-rule-ref to a schedule with legal bases, floors and caps; disposition execution and certification are performed here against that schedule.", "required": true, "source_refs": [ "SRC-016", "SRC-015" ] }, { "target": "Measurement / observation model", "relation": "REFERENCE", "purpose": "Resolves observational evidence items to their measurement semantics, units and uncertainty rather than restating instrument and method semantics in this model.", "required": false, "source_refs": [ "SRC-014", "SRC-008" ] }, { "target": "W3C PROV-O / PROV-DM", "relation": "ALIGN", "purpose": "Alignment target for derivation, primary source, quotation, revision, attribution, delegation, invalidation and bundle-level provenance-of-provenance. Alignment only; no conformance is claimed.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "OMG SACM 2.3 and ISO/IEC/IEEE 15026-2:2022", "relation": "ALIGN", "purpose": "Alignment target for the claim/argumentation/evidence separation, inference as a reasoning step under a specified context, explicit assumptions and justification, and auditability of the case.", "required": false, "source_refs": [ "SRC-005", "SRC-006" ] }, { "target": "W3C Verifiable Credentials Data Model 2.0", "relation": "ALIGN", "purpose": "Alignment target for issuer, evidence, proof, validFrom/validUntil and credentialStatus, and for the separation of credential verification from evaluation of claim truth.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "C2PA Technical Specification 2.2 and in-toto Attestation Framework", "relation": "ALIGN", "purpose": "Alignment targets for digest-based subject identity, hard bindings, hashed URIs, created versus gathered assertions, ingredient provenance and signed statement envelopes.", "required": false, "source_refs": [ "SRC-011", "SRC-012" ] }, { "target": "W3C Web Annotation Data Model and CiTO", "relation": "ALIGN", "purpose": "Alignment targets for selector-based anchoring with source state, and for the governed vocabulary of support, authority, agreement and refutation relations with factual/rhetorical polarity.", "required": false, "source_refs": [ "SRC-004", "SRC-013" ] }, { "target": "ISO/IEC 27037:2012 digital evidence handling", "relation": "ALIGN", "purpose": "Alignment target for the identification/collection/acquisition/preservation processes, the auditability, repeatability and reproducibility principles, and unbroken chain of custody across physical, logical and documentary modes.", "required": false, "source_refs": [ "SRC-008" ] }, { "target": "GRADE certainty-of-evidence approach", "relation": "ALIGN", "purpose": "Alignment target for scheme-declared certainty levels, rating-down and rating-up domains, and separation of evidence certainty from recommendation strength and direction.", "required": false, "source_refs": [ "SRC-014" ] }, { "target": "Regulatory logging and technical documentation obligations (EU AI Act, NIST SP 800-53 AU family)", "relation": "EXTEND", "purpose": "Extends the model with mandated machine-generated evidence, minimum log content for defined system classes, and audit-record governance including retention floors, without absorbing the logging subsystem itself.", "required": false, "source_refs": [ "SRC-015", "SRC-018", "SRC-019" ] } ], "holds": [ "Source verification incomplete: re-resolve every accepted source URL and pin its live version before publication, including the C2PA divergence (base cites 2.2, the accepted grok findings sit alongside a 2.4 citation), the CiTO version-versus-modified date, and the two newly relied-on grok sources (FHIR R5 Evidence, FRE 401).", "Paywalled and unretrieved normative texts: ISO/IEC/IEEE 15026-2:2022, ISO/IEC/IEEE 42010:2022 and ISO/IEC 27037:2012 were read from catalogue abstracts, and the OMG SACM 2.3 normative PDF was never retrieved. Publish alignment language only; no clause numbers, no metamodel class names and no conformance claims until the normative texts are confirmed.", "EU AI Act Article 19 six-month log-retention floor was read from a secondary rendering (Future of Life Institute AI Act Explorer). Re-verify against the Official Journal text of Regulation (EU) 2024/1689 before the floor is stated as a requirement.", "Multi-profile validation not complete: the model must be exercised against at least the legal-evidence profile (US FRE 401/901, jurisdiction-qualified), the health/guideline profile (GRADE plus FHIR Evidence statistics), the engineering-assurance profile (SACM, 15026-2) and the content-provenance profile (C2PA, in-toto). GRADE categories and FRE tests must not travel as global defaults.", "The accepted quantitative-statistic finding must be reconciled with the sibling Quantity/Unit and Measurement models before operational use, so that unit, interval and uncertainty semantics are stated once and referenced, not duplicated inside the support record.", "Confirm that the accepted authentication-foundation finding does not silently import US admissibility doctrine: authentication must remain a recorded foundation, never a ruling, and the exclusionary bars (hearsay, privilege, prejudice) stay with the legal sibling model." ], "scope": "Full specification recursively inventoried and compared to public bytes; prior source holds not discharged." } ] }