# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-02T17:11:50Z", "synthesisSha256": "d89a44c97beeaee6e820433cd7bec6e92579da36180ef8fec4152b8fc95c6da8", "providerMode": "single-provider-waiver", "providers": [ "Claude" ], "waivedProviders": [ "Grok" ] }, "metaModel": { "id": "WM-KNW-008", "registryId": "vr.wm-knw-008", "name": "Evidence / Citation", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "relationship", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.KNW.EVD" ], "tags": [ "evidence", "citation", "inf.knw.evd" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-knw-008-evidence-citation/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-knw-008", "model": { "registry_id": "vr.wm-knw-008", "model_id": "WM-KNW-008", "name": "Evidence / Citation", "entry_kind": "relationship", "purpose": "Model the reified evidential citation: a directed, typed, attributable link from a citing context to a cited source, plus the locator needed to retrieve and re-verify the exact cited material.", "scope_statement": "Defines the evidential citation as an independently identifiable relationship record. Covers citing-context binding, evidential stance (support, challenge, qualification, neutral mention), evidence type and assertion method, the source locator (preferred citation identifier, access URI, in-resource anchor, consulted representation state), integrity and provenance of the citation act, binding of an external certainty scheme, record lifecycle and supersession, and interoperability profiles. Storage- and interface-neutral: JSON, RDF, Markdown, Git, MCP and document stores are projections. It masters neither endpoint: the citing claim or decision, and the cited work, are governed elsewhere.", "in_scope": [ "Reified citation record identity, deduplication and the directed citing-context to cited-source link", "Typed evidential stance and rhetorical intent, with polarity and direction", "Evidence type and assertion method, including human curation versus automated or model-derived extraction", "Source locator: preferred citation identifier distinguished from access URI, with scheme normalization", "In-resource anchoring by selector chains, plus excerpt, quotation context and transformation status", "Consulted representation state: access datetime, version identifier, archived snapshot and request conditions", "Locator resolution health, link rot and content drift detection", "Binding of an externally governed certainty rating scheme and its per-domain limitation results", "Provenance of the citation act, with event, observation and ingestion times kept separate", "Fixity of excerpts and captures, and references to signed media provenance manifests", "Citation record lifecycle states, supersession and versioning", "Dated observations of the cited source's status such as retraction or expression of concern", "Alignment declarations, exchange profiles and sensitivity classification of the record and its excerpt" ], "out_of_scope": [ "Claim wording, decomposition, truth status and lifecycle, which belong to WM-KNW-007", "Decision options, criteria, deliberation and decision lifecycle, which belong to WM-KNW-010", "Aggregation of multiple evidence items into a verdict, belief revision, or argument-scheme structure", "Canonical bibliographic description and the publication lifecycle of the cited work", "Web archive capture scheduling, storage and preservation execution", "Rendering of style-specific formatted reference strings and bibliographies", "Runtime access evaluation, enforcement and audit-trail records", "Execution of retention schedules, erasure and legal-hold determination", "Publisher or author trust and reputation scoring as a managed registry", "Signing and cryptographic validation of media provenance manifests", "Bibliometric citation counting and impact analytics" ], "boundary_notes": [ { "neighbor": "WM-KNW-007 Claim / Assertion", "distinction": "The claim model owns claim identity, text, decomposition, status and lifecycle. This model holds only a resolving reference to the claim and a locus within it, and never mirrors or versions claim status.", "source_refs": [ "SRC-003", "SRC-012" ] }, { "neighbor": "WM-KNW-010 Decision rationale", "distinction": "The decision model owns options, criteria, rationale structure and decision lifecycle. This model supplies citation records that a rationale step points at; it models no deliberation and reaches no conclusion.", "source_refs": [ "SRC-008", "SRC-002" ] }, { "neighbor": "Bibliographic source-work registry (DataCite, Crossref or equivalent)", "distinction": "Registries master full bibliographic metadata and identifier authority. This model holds a cached, explicitly non-authoritative minimal descriptor with a refresh timestamp, sufficient to make a citation intelligible without dereferencing.", "source_refs": [ "SRC-007", "SRC-005" ] }, { "neighbor": "Web archiving and preservation service", "distinction": "This model records memento and timegate URIs, archive datetimes and digests. Capture scheduling, storage tiers and preservation actions are external.", "source_refs": [ "SRC-006" ] }, { "neighbor": "General provenance graph (PROV-O)", "distinction": "Provenance patterns are used for the citation act only. A whole-of-knowledge-base activity and agent graph is a separate concern and is not constructed here.", "source_refs": [ "SRC-002" ] }, { "neighbor": "Argumentation and inference model", "distinction": "This model records one typed evidential link with stance and certainty. Multi-premise schemes, defeaters, weighting and aggregation are not modelled.", "source_refs": [ "SRC-003", "SRC-010" ] }, { "neighbor": "Adopting-Dimension access policy and audit service", "distinction": "Only sensitivity labels and policy references are held here. Evaluation of a request, enforcement and the audit trail are owned entirely by that service; referencing an audit event grants no ownership of audit semantics.", "source_refs": [ "SRC-008", "SRC-001" ] }, { "neighbor": "Media provenance system (C2PA)", "distinction": "Signed manifests and hard or soft bindings are referenced as integrity evidence for media excerpts. Signing, certificate handling and validation are performed by that system.", "source_refs": [ "SRC-011" ] }, { "neighbor": "Records retention and disposition service", "distinction": "This model records a retention class reference, disposition state and tombstone stub. Schedule ownership, legal-hold determination and erasure execution stay with the adopting Dimension.", "source_refs": [ "SRC-013", "SRC-008" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Web Annotation Data Model", "organization": "World Wide Web Consortium (W3C)", "url": "https://www.w3.org/TR/annotation-model/", "version_or_date": "W3C Recommendation, 23 February 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-02T09:10:00Z", "relevance": "Normative selector types (Fragment, CSS, XPath, TextQuote, TextPosition, DataPosition, SVG, Range), refinedBy chains, TimeState and HttpRequestState, and creator/created/generator/via/canonical properties for anchoring and representation state." }, { "id": "SRC-002", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium (W3C)", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-02T09:12:00Z", "relevance": "Entity, Activity and Agent pattern with wasGeneratedBy, used, wasAttributedTo and delegation, used to model the citation act, its actor and its accountability chain." }, { "id": "SRC-003", "title": "CiTO, the Citation Typing Ontology", "organization": "SPAR Ontologies (Silvio Peroni and David Shotton)", "url": "https://sparontologies.github.io/cito/current/cito.html", "version_or_date": "Version 2.8.2, namespace http://purl.org/spar/cito/", "source_type": "ontology", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-02T09:14:00Z", "relevance": "Reified cito:Citation class with hasCitingEntity, hasCitedEntity and hasCitationCharacterization, plus supporting intents (citesAsEvidence, citesAsAuthority, confirms, supports) and challenging intents (disputes, critiques, refutes, disagreesWith, qualifies)." }, { "id": "SRC-004", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "Standards Track, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-02T09:16:00Z", "relevance": "Required timestamp profile: full date-time with a seconds component and an explicit numeric offset or Z, with -00:00 signalling unknown local offset; basis for the model's timestamp rule." }, { "id": "SRC-005", "title": "RFC 8574: cite-as: A Link Relation to Convey a Preferred URI for Referencing", "organization": "IETF / RFC Editor (Independent Submission)", "url": "https://www.rfc-editor.org/rfc/rfc8574.html", "version_or_date": "Informational, April 2019", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-02T09:18:00Z", "relevance": "Normative separation of the access URI from the reference URI preferred for permanent citation, and the discovery mechanism for a preferred citation identifier." }, { "id": "SRC-006", "title": "RFC 7089: HTTP Framework for Time-Based Access to Resource States -- Memento", "organization": "Internet Engineering Task Force (IETF)", "url": "https://www.rfc-editor.org/rfc/rfc7089.html", "version_or_date": "Informational, December 2013", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-02T09:20:00Z", "relevance": "Original Resource, Memento, TimeGate and TimeMap roles with Accept-Datetime and Memento-Datetime headers, supporting the consulted-representation state and archived snapshot elements." }, { "id": "SRC-007", "title": "DataCite Metadata Schema 4.6, Appendix relationType", "organization": "DataCite", "url": "https://datacite-metadata-schema.readthedocs.io/en/4.6/appendices/appendix-1/relationType/", "version_or_date": "Schema version 4.6", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-02T09:22:00Z", "relevance": "Governed relation vocabulary (Cites, IsCitedBy, References, Reviews, IsVersionOf, IsNewVersionOf, IsObsoletedBy, IsIdenticalTo, HasPart) and relatedIdentifierType values (DOI, Handle, URL, URN, ISBN, PMID, arXiv) for identifier scheme and relation alignment." }, { "id": "SRC-008", "title": "Verifiable Credentials Data Model v2.0", "organization": "World Wide Web Consortium (W3C)", "url": "https://www.w3.org/TR/vc-data-model-2.0/", "version_or_date": "W3C Recommendation, 15 May 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-02T09:24:00Z", "relevance": "The evidence property as documentary basis distinct from cryptographic proof, plus validFrom/validUntil validity intervals and credentialStatus for revocation, informing verification, validity and lifecycle semantics." }, { "id": "SRC-009", "title": "Evidence and Conclusion Ontology (ECO)", "organization": "OBO Foundry / Evidence Ontology project", "url": "https://obofoundry.org/ontology/eco.html", "version_or_date": "OBO Foundry registry entry, CC0 1.0; release date not stated on the registry page (accessed 2026-09-02)", "source_type": "ontology", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-02T09:26:00Z", "relevance": "Separates evidence type from assertion method, and distinguishes manual curation from automatic assertion, supplying the evidence-type and assertion-method vocabulary pattern." }, { "id": "SRC-010", "title": "GRADE Handbook for grading the quality of evidence and the strength of recommendations", "organization": "GRADE Working Group", "url": "https://gdt.gradepro.org/app/handbook/handbook.html", "version_or_date": "Updated October 2013", "source_type": "scientific", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-02T09:28:00Z", "relevance": "Four certainty levels (high, moderate, low, very low), five rate-down domains (risk of bias, imprecision, inconsistency, indirectness, publication bias) and three rate-up domains, used as an externally governed certainty scheme this model binds rather than redefines." }, { "id": "SRC-011", "title": "Content Credentials: C2PA Technical Specification", "organization": "Coalition for Content Provenance and Authenticity (C2PA)", "url": "https://spec.c2pa.org/specifications/specifications/2.2/specs/C2PA_Specification.html", "version_or_date": "Version 2.2, May 2025", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-02T09:30:00Z", "relevance": "Manifest, claim, claim signature, assertions, ingredients, hard bindings by content hash and soft bindings by fingerprint or watermark, referenced as integrity evidence for media excerpts and their regions." }, { "id": "SRC-012", "title": "ClaimReview (schema.org type)", "organization": "schema.org", "url": "https://schema.org/ClaimReview", "version_or_date": "schema.org version 30.0, 19 March 2026", "source_type": "schema", "primary_source": true, "authority_tier": 3, "accessed_at": "2026-09-02T09:32:00Z", "relevance": "claimReviewed, itemReviewed, reviewRating, author and associatedClaimReview show a widely deployed model where the review verdict sits outside the claim, marking a mapping decision this model must make explicit." }, { "id": "SRC-013", "title": "NISO RP-45-2024, Communication of Retractions, Removals, and Expressions of Concern (CREC)", "organization": "National Information Standards Organization (NISO)", "url": "https://www.niso.org/publications/rp-45-2024-crec", "version_or_date": "Recommended Practice, published 27 June 2024, DOI 10.3789/niso-rp-45-2024", "source_type": "standard", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-09-02T09:34:00Z", "relevance": "Metadata elements for retraction notices, machine-readable retraction status, persistent identifiers for notices, and propagation of status to citing works and downstream systems." } ], "structure": { "bundles": [ { "id": "evidential-link", "name": "Evidential Link Identity and Typing", "description": "The citation as a reified, independently identifiable relationship, what it attaches to, and how its evidential character is typed.", "rationale": "CiTO reifies a citation as a directed link with its own characterization, and the Web Annotation model reifies an annotation with its own identity; both require the link to be addressable independently of its endpoints so that stance, provenance and lifecycle can attach to it.", "source_refs": [ "SRC-003", "SRC-001" ], "layers": [ { "id": "citation-record-core", "name": "Citation Record Core", "description": "Identity of the citation record and its binding to the citing context.", "source_refs": [ "SRC-003", "SRC-001" ], "findings": [ { "id": "citation-record-identity", "name": "Citation record identity and deduplication", "description": "The evidential citation is a first-class record with its own identifier, distinguishable from any other link between the same two endpoints.", "source_refs": [ "SRC-003", "SRC-007", "SRC-001" ], "questions": [ { "id": "q-cri-identity", "text": "Which identifier authoritatively identifies this citation record, and which system masters it?", "kind": "identity", "answer_data": [ "Master-system identifier value and issuing system reference", "Identifier scheme code", "Fallback UUID or ULID assigned by the adopting Dimension" ] }, { "id": "q-cri-definition", "text": "What distinguishes a genuinely new citation record from a duplicate of an existing citing-context-to-source link?", "kind": "definition", "answer_data": [ "Deduplication key composed of citing-context reference, source identifier, anchor and stance", "Collision and merge policy" ] }, { "id": "q-cri-composition", "text": "Which sub-structures are embedded components of this record rather than separately identified records?", "kind": "composition", "answer_data": [ "Component inventory with embedded or referenced flag", "Cardinality per component" ] }, { "id": "q-cri-interop", "text": "Which external citation identifiers may be recorded as equivalents of this record?", "kind": "interoperability", "answer_data": [ "External identifier scheme and value", "Basis on which equivalence is asserted" ] } ], "data_elements": [ { "id": "de-cri-record-id", "name": "citation-record-identifier", "description": "Primary identifier of the reified citation record.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "de-cri-scheme", "name": "identifier-scheme", "description": "Scheme that governs the primary identifier.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-cri-dedup-key", "name": "deduplication-key", "description": "Normalized composite key used to detect duplicate links.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-cri-equivalent", "name": "equivalent-identifier", "description": "External identifier asserted to denote the same citation.", "value_kind": "identifier", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007", "SRC-003" ] } ], "artifacts": [], "inline_only_rationale": "Record identity is pure structured reference data resolved through identifier registries. Materialising it as a separate file would create a second identity surface competing with the master system, which the identity priority explicitly forbids." }, { "id": "citing-context-binding", "name": "Citing-context binding and locus", "description": "What is doing the citing (claim, decision rationale, document passage or data field) and where inside it the citation applies, held as a reference only.", "source_refs": [ "SRC-003", "SRC-001", "SRC-012" ], "questions": [ { "id": "q-ccb-relationship", "text": "Which citing context does this record attach to, and through what stable reference into its owning model?", "kind": "relationship", "answer_data": [ "Citing-context reference and owning model identifier", "Citing-context kind code" ] }, { "id": "q-ccb-composition", "text": "Where inside the citing context does the citation apply, and how is that position expressed?", "kind": "composition", "answer_data": [ "Locus expression such as passage, field path or rationale step", "Locus expression scheme" ] }, { "id": "q-ccb-constraint", "text": "May one record serve several citing contexts, and what eligibility rules restrict permitted endpoints?", "kind": "constraint", "answer_data": [ "Cardinality rule for citing contexts", "Permitted citing-context kinds declared by the owning package" ] }, { "id": "q-ccb-authority", "text": "Which model owns the citing context's own status so that this record never mirrors it?", "kind": "authority", "answer_data": [ "Owning model identifier for citing-context status", "Declared prohibition on caching that status here" ] } ], "data_elements": [ { "id": "de-ccb-context-ref", "name": "citing-context-reference", "description": "Resolving reference to the claim, rationale step or passage that cites.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "de-ccb-context-kind", "name": "citing-context-kind", "description": "Classification of the citing endpoint.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-012" ] }, { "id": "de-ccb-locus", "name": "citing-locus", "description": "Position inside the citing context to which the citation applies.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-ccb-role", "name": "citation-role", "description": "Role the citation plays in the citing context, such as primary support or background.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [], "inline_only_rationale": "The binding is a pointer plus a locus expression. Producing an artifact here would duplicate content owned by WM-KNW-007 or WM-KNW-010 and create a second, drifting copy of the citing text." } ] }, { "id": "evidential-typing", "name": "Evidential Typing", "description": "Stance, intent, evidence type and the method by which the evidential assertion was produced.", "source_refs": [ "SRC-003", "SRC-009" ], "findings": [ { "id": "stance-and-intent", "name": "Evidential stance and citation intent", "description": "The controlled value characterising whether the cited material supports, challenges, qualifies or merely mentions the citing context, with polarity and direction.", "source_refs": [ "SRC-003", "SRC-007", "SRC-012" ], "questions": [ { "id": "q-sai-classification", "text": "Which controlled stance value characterises this link?", "kind": "classification", "answer_data": [ "Stance code and its polarity", "Reference and version of the stance vocabulary" ] }, { "id": "q-sai-relationship", "text": "Is the inverse assertion also recorded, and who may assert it?", "kind": "relationship", "answer_data": [ "Inverse-asserted flag", "Agent permitted to assert the inverse" ] }, { "id": "q-sai-constraint", "text": "May conflicting stance values coexist on a single record, and how are they disambiguated?", "kind": "constraint", "answer_data": [ "Multiplicity rule for stance values", "Disambiguation or split rule" ] }, { "id": "q-sai-interop", "text": "How does each local stance term map to CiTO properties and DataCite relation types, and where does the mapping fail?", "kind": "interoperability", "answer_data": [ "Per-term mapping with strength", "Terms with no defensible external equivalent" ] } ], "data_elements": [ { "id": "de-sai-stance", "name": "stance-code", "description": "Controlled value for the evidential stance.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "de-sai-polarity", "name": "stance-polarity", "description": "Supporting, challenging, qualifying or neutral polarity derived from the stance.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "de-sai-vocab", "name": "stance-vocabulary-reference", "description": "Version-bound reference to the governing stance vocabulary.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-sai-inverse", "name": "inverse-asserted", "description": "Whether the reciprocal link is also asserted.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [], "inline_only_rationale": "Stance is a single controlled value plus vocabulary binding. It is consumed by machines as a code, and rendering it as a document would obscure the version binding that makes it interpretable." }, { "id": "evidence-type-and-method", "name": "Evidence type and assertion method", "description": "What kind of evidence the cited material constitutes, and by what method the evidential link was produced: human curation, automated extraction or model inference.", "source_refs": [ "SRC-009", "SRC-002", "SRC-003" ], "questions": [ { "id": "q-etm-classification", "text": "Which evidence-type class describes the cited material?", "kind": "classification", "answer_data": [ "Evidence-type code", "Version-bound evidence-type vocabulary reference" ] }, { "id": "q-etm-process", "text": "By what assertion method was this evidential link produced?", "kind": "process", "answer_data": [ "Assertion method code such as manual curation or automatic assertion", "Pipeline or configuration reference" ] }, { "id": "q-etm-provenance", "text": "If the link was produced automatically, which tool and model version generated it and with what reported confidence?", "kind": "provenance", "answer_data": [ "Tool identifier and version", "Model identifier and version", "Reported machine confidence value and its scale" ] }, { "id": "q-etm-quality", "text": "What minimum evidence-type granularity must be reached before the record may leave draft state?", "kind": "quality", "answer_data": [ "Minimum granularity rule", "Exception conditions" ] } ], "data_elements": [ { "id": "de-etm-type", "name": "evidence-type-code", "description": "Class of evidence the cited material provides.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "de-etm-method", "name": "assertion-method-code", "description": "Method by which the evidential assertion was made.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-009" ] }, { "id": "de-etm-tool", "name": "extraction-tool-reference", "description": "Software agent, model and version that produced an automated assertion.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-etm-confidence", "name": "machine-confidence", "description": "Confidence value reported by an automated extractor, with declared scale.", "value_kind": "number", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-009" ] } ], "artifacts": [], "inline_only_rationale": "These are coded classifications and tool references. The pipeline configuration they point at is owned and versioned by the tooling package, so copying it here would fork a second configuration of record." } ] } ] }, { "id": "source-locator", "name": "Cited Source Locator", "description": "Everything required to identify, retrieve, anchor and re-retrieve the exact cited material.", "rationale": "RFC 8574 separates the URI used for access from the URI preferred for citation, Memento provides time-based access to prior states, and the Web Annotation model supplies selector and state patterns; together these define what a durable source locator must carry.", "source_refs": [ "SRC-005", "SRC-006", "SRC-001" ], "layers": [ { "id": "source-identification", "name": "Source Identification", "description": "Which source is cited, by which identifier, and what minimal description travels with it.", "source_refs": [ "SRC-005", "SRC-007" ], "findings": [ { "id": "preferred-citation-identifier", "name": "Preferred citation identifier and scheme normalization", "description": "The identifier that should be used to cite the source, kept distinct from the URI used to access it, with accepted schemes, precedence and normalization rules.", "source_refs": [ "SRC-005", "SRC-007", "SRC-006" ], "questions": [ { "id": "q-pci-identity", "text": "Which persistent identifier is preferred for citing this source, and how was it discovered?", "kind": "identity", "answer_data": [ "Persistent identifier value and scheme", "Discovery method such as a cite-as link relation, registry lookup or manual entry" ] }, { "id": "q-pci-classification", "text": "Which identifier schemes are accepted and in what precedence order when several exist?", "kind": "classification", "answer_data": [ "Accepted scheme list", "Precedence ordering rule" ] }, { "id": "q-pci-constraint", "text": "What normalization must be applied before identifiers are compared or deduplicated?", "kind": "constraint", "answer_data": [ "Normalization profile covering case, prefix form, resolver host and percent-encoding", "Raw and normalized identifier forms" ] }, { "id": "q-pci-exception", "text": "What is recorded when the cited source has no persistent identifier at all?", "kind": "exception", "answer_data": [ "No-identifier reason code", "Substitute locator such as access URI, archived snapshot or descriptor-only record" ] }, { "id": "q-pci-interop", "text": "How is the access URI kept distinct from the reference URI when the record is exchanged?", "kind": "interoperability", "answer_data": [ "Separate elements for access URI and reference URI", "Export rule preventing conflation" ] } ], "data_elements": [ { "id": "de-pci-preferred", "name": "preferred-citation-identifier", "description": "Identifier preferred for permanent citation of the source.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "de-pci-scheme", "name": "source-identifier-scheme", "description": "Scheme of the preferred citation identifier.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-pci-access-uri", "name": "access-uri", "description": "URI actually used to retrieve a representation of the source.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "de-pci-normalized", "name": "normalized-identifier", "description": "Identifier after the declared normalization profile, used for comparison.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-pci-discovery", "name": "identifier-discovery-method", "description": "How the preferred identifier was obtained.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] } ], "artifacts": [], "inline_only_rationale": "Identifiers and their normalized forms are atomic reference values that must stay comparable byte for byte. An artifact would add an indirection that defeats the deduplication and resolution rules built on them." }, { "id": "source-minimal-descriptor", "name": "Minimal source descriptor and its non-authority", "description": "The smallest description held locally so a citation is intelligible without dereferencing, explicitly marked as a cache rather than the master record.", "source_refs": [ "SRC-007", "SRC-012", "SRC-003" ], "questions": [ { "id": "q-smd-definition", "text": "What is the minimum descriptor set required for a citation to be intelligible without dereferencing the source?", "kind": "definition", "answer_data": [ "Minimum element set", "Conditions under which additional elements become mandatory" ] }, { "id": "q-smd-ownership", "text": "Which registry masters the full bibliographic description, and how is the local copy marked as non-authoritative?", "kind": "ownership", "answer_data": [ "Mastering registry reference", "Descriptor authority flag distinguishing cache from master" ] }, { "id": "q-smd-temporal", "text": "When was the cached descriptor last refreshed from its mastering registry, and what staleness is tolerated?", "kind": "temporal", "answer_data": [ "Descriptor refresh timestamp", "Staleness tolerance and refresh trigger" ] }, { "id": "q-smd-classification", "text": "Which source category applies, such as peer-reviewed article, dataset, statute, standard, web page, personal communication or model output?", "kind": "classification", "answer_data": [ "Source category code", "Category-specific mandatory descriptor elements" ] } ], "data_elements": [ { "id": "de-smd-category", "name": "source-category", "description": "Category of the cited source.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-smd-title", "name": "source-title", "description": "Cached title or designation of the source.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-smd-party", "name": "responsible-party-reference", "description": "Reference to the author, issuing body or publisher, resolved through the party model.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-smd-issued", "name": "source-issued-date", "description": "Publication or issue date of the cited source as cached.", "value_kind": "date", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-smd-authority", "name": "descriptor-authority", "description": "Flag declaring the descriptor a non-authoritative cache and naming its master.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-smd-refreshed", "name": "descriptor-refreshed-at", "description": "Time the cached descriptor was last refreshed from the mastering registry.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [], "inline_only_rationale": "The descriptor exists only to make a reference legible in place; it is a bounded cache of registry-mastered fields. Emitting it as an artifact would encourage its reuse as a bibliographic record and turn this model into a shadow registry." } ] }, { "id": "in-resource-anchoring", "name": "In-Resource Anchoring", "description": "Precise location of the cited portion inside the source, and the excerpt reproduced from it.", "source_refs": [ "SRC-001", "SRC-011" ], "findings": [ { "id": "anchor-selectors", "name": "Anchor selectors and granularity", "description": "One or more selectors, optionally refined in a chain, that locate the cited portion within the retrieved representation, including non-textual regions.", "source_refs": [ "SRC-001", "SRC-011", "SRC-003" ], "questions": [ { "id": "q-ans-composition", "text": "Which selector types anchor the cited portion, and in what refinement order?", "kind": "composition", "answer_data": [ "Selector list with type per selector", "Refinement chain ordering" ] }, { "id": "q-ans-spatial", "text": "For non-textual sources, how is the cited region expressed?", "kind": "spatial", "answer_data": [ "Region expression such as page box, SVG shape, media time interval, byte range or cell range", "Coordinate or timing reference frame" ] }, { "id": "q-ans-constraint", "text": "How many independent redundant selectors are required so the anchor survives reformatting of the source?", "kind": "constraint", "answer_data": [ "Minimum redundancy rule by source category", "Permitted selector combinations" ] }, { "id": "q-ans-validation", "text": "How is a selector validated against a retrieved representation, and what counts as a successful re-anchor?", "kind": "validation", "answer_data": [ "Match procedure per selector type", "Success, partial-match and failure criteria" ] }, { "id": "q-ans-exception", "text": "What is recorded when the source cannot be anchored more precisely than the whole resource?", "kind": "exception", "answer_data": [ "Whole-resource granularity flag and reason", "Legacy human-readable locator text such as a page or section reference" ] } ], "data_elements": [ { "id": "de-ans-selector", "name": "selector", "description": "Structured selector locating the cited portion.", "value_kind": "object", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001" ] }, { "id": "de-ans-selector-type", "name": "selector-type", "description": "Type of each selector, such as fragment, text quote, text position, data position, SVG or range.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001" ] }, { "id": "de-ans-refined-by", "name": "refined-by-reference", "description": "Selector or state that refines another selector.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-ans-granularity", "name": "anchor-granularity", "description": "Achieved granularity, from whole resource down to a character or sample range.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001" ] }, { "id": "de-ans-legacy-locator", "name": "legacy-locator-text", "description": "Human-readable locator such as a page, clause or timecode reference.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003" ] } ], "artifacts": [], "inline_only_rationale": "Selectors are machine-evaluable expressions that must be applied against a representation at verification time. Freezing them into an artifact would separate them from the record whose re-anchoring they govern." }, { "id": "excerpt-and-quotation", "name": "Excerpt, quotation context and transformation", "description": "The material actually reproduced from the source, with surrounding context, language, transformation status and reproduction limits.", "source_refs": [ "SRC-001", "SRC-011", "SRC-003" ], "questions": [ { "id": "q-exq-evidence", "text": "What exact excerpt is reproduced as the evidential material, and with what surrounding context?", "kind": "evidence", "answer_data": [ "Excerpt content", "Prefix and suffix context", "Context window size rule" ] }, { "id": "q-exq-constraint", "text": "What length and licence limits constrain reproducing this excerpt in the record?", "kind": "constraint", "answer_data": [ "Maximum permitted excerpt extent", "Licence or fair-dealing basis reference" ] }, { "id": "q-exq-quality", "text": "Is the excerpt verbatim, normalized, translated or paraphrased, and how is that transformation declared?", "kind": "quality", "answer_data": [ "Transformation code", "Language tag of the excerpt and of the original", "Transformation agent reference" ] }, { "id": "q-exq-privacy", "text": "Does the excerpt contain personal or special-category data requiring masking before storage or export?", "kind": "privacy", "answer_data": [ "Personal-data presence flag and category", "Masking rule and masked rendition reference" ] } ], "data_elements": [ { "id": "de-exq-text", "name": "excerpt-text", "description": "Reproduced text of the cited portion.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-exq-prefix", "name": "excerpt-prefix", "description": "Text immediately preceding the excerpt, used for disambiguation and re-anchoring.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-exq-suffix", "name": "excerpt-suffix", "description": "Text immediately following the excerpt.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-exq-transformation", "name": "excerpt-transformation", "description": "Declared transformation applied to the excerpt relative to the source.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001" ] }, { "id": "de-exq-language", "name": "excerpt-language", "description": "Language tag of the stored excerpt.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-exq-rights", "name": "reproduction-rights-reference", "description": "Reference to the licence or permission under which the excerpt is held.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [ { "id": "cited-excerpt-capture", "name": "Cited excerpt capture", "description": "A stored rendition of the cited portion, preserving what was actually read: a text snippet, a cropped page image, a clipped media segment or a tabular extract.", "media_or_form": [ "plain text snippet", "cropped page image", "clipped audio or video segment", "tabular extract" ], "serial": true, "identity_strategy": "Citation record identifier plus a zero-padded, never-reused capture ordinal. The content digest is recorded for equality comparison but is never used as the primary key, and the capture datetime is an attribute rather than part of the name.", "source_refs": [ "SRC-001", "SRC-011" ] } ], "inline_only_rationale": null } ] }, { "id": "resource-state", "name": "Consulted Representation State and Retrievability", "description": "Which representation of the source was consulted, and whether the locator still resolves to equivalent content.", "source_refs": [ "SRC-006", "SRC-001" ], "findings": [ { "id": "resource-state-binding", "name": "Consulted representation state", "description": "Binding of the citation to the specific representation consulted: access datetime, version, archived snapshot and the request conditions that produced it.", "source_refs": [ "SRC-006", "SRC-001", "SRC-004" ], "questions": [ { "id": "q-rsb-temporal", "text": "At what instant was the cited representation retrieved, expressed with an explicit offset?", "kind": "temporal", "answer_data": [ "Access timestamp in RFC 3339 form", "Clock source and precision" ] }, { "id": "q-rsb-state", "text": "Which representation state was consulted: live current, a named version, or an archived snapshot?", "kind": "state", "answer_data": [ "State kind code", "Version identifier or archive datetime as applicable" ] }, { "id": "q-rsb-provenance", "text": "Which request conditions were needed to obtain that representation?", "kind": "provenance", "answer_data": [ "Request headers including content negotiation and datetime negotiation", "Credential class required, without the credential itself" ] }, { "id": "q-rsb-relationship", "text": "Which archived snapshot and time gate correspond to the consulted state?", "kind": "relationship", "answer_data": [ "Memento URI and its archive datetime", "Time gate or time map URI" ] }, { "id": "q-rsb-retention", "text": "How long must the captured representation be retained for the citation to stay re-verifiable?", "kind": "retention", "answer_data": [ "Retention class reference for the capture", "Minimum retention interval tied to the citing context's own retention" ] } ], "data_elements": [ { "id": "de-rsb-accessed-at", "name": "accessed-at", "description": "Instant the representation was retrieved.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-rsb-version", "name": "source-version-identifier", "description": "Version, edition or revision identifier of the consulted representation.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-rsb-memento", "name": "memento-uri", "description": "URI of an archived snapshot of the consulted state.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "de-rsb-memento-datetime", "name": "memento-datetime", "description": "Archive datetime of the snapshot, stored in the model's canonical timestamp form.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-004" ] }, { "id": "de-rsb-request-state", "name": "request-state", "description": "Request conditions, such as headers and negotiated media type, needed to reproduce the retrieval.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [ { "id": "consulted-representation-capture", "name": "Consulted representation capture", "description": "A point-in-time capture of the representation actually consulted, so a later reader can see what the citer saw: a web archive record, a rendered document, a serialized payload or a screenshot.", "media_or_form": [ "web archive record", "rendered document", "serialized payload", "screenshot" ], "serial": true, "identity_strategy": "Citation record identifier plus a zero-padded capture ordinal. Capture datetime, archive URI and content digest are attributes; the digest is never promoted to primary key because the same content may be captured on several occasions.", "source_refs": [ "SRC-006", "SRC-001" ] } ], "inline_only_rationale": null }, { "id": "locator-resolution-health", "name": "Locator resolution health and content drift", "description": "Whether the identifier still resolves, whether the anchored content is still present and unchanged, and how link rot and drift are recorded.", "source_refs": [ "SRC-005", "SRC-006", "SRC-001" ], "questions": [ { "id": "q-lrh-measurement", "text": "What resolution and re-anchor outcome was observed at the most recent check?", "kind": "measurement", "answer_data": [ "Resolution status code and redirect chain", "Anchor match result and similarity measure" ] }, { "id": "q-lrh-temporal", "text": "How often is resolution re-checked and when is the next check due?", "kind": "temporal", "answer_data": [ "Check interval by source category", "Last checked and next due timestamps" ] }, { "id": "q-lrh-exception", "text": "Which fallback locators apply when the primary identifier fails to resolve?", "kind": "exception", "answer_data": [ "Ordered fallback locator list", "Escalation rule when all fallbacks fail" ] }, { "id": "q-lrh-state", "text": "Which health state is currently asserted for this locator?", "kind": "state", "answer_data": [ "Health state code such as resolvable, redirected, moved, unresolvable or content-drifted", "Evidence reference supporting the state" ] } ], "data_elements": [ { "id": "de-lrh-checked-at", "name": "last-checked-at", "description": "Instant of the most recent resolution check.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-lrh-status", "name": "resolution-status", "description": "Outcome of the most recent resolution attempt.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-005" ] }, { "id": "de-lrh-anchor-match", "name": "anchor-match-result", "description": "Whether the recorded selectors still match the current representation.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-lrh-fallback", "name": "fallback-locator", "description": "Alternative locator used when the primary fails.", "value_kind": "identifier", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-006" ] }, { "id": "de-lrh-interval", "name": "check-interval", "description": "Declared interval between scheduled resolution checks.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006" ] } ], "artifacts": [ { "id": "locator-check-report", "name": "Locator resolution check report", "description": "Machine-readable report of a single resolution and re-anchor check, recording outcome codes, observed redirects and any detected content drift.", "media_or_form": [ "structured check report", "log record" ], "serial": true, "identity_strategy": "Citation record identifier plus a monotonically increasing check ordinal. The check timestamp is an attribute of the report and is never part of its identifier.", "source_refs": [ "SRC-005", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "evidential-assessment", "name": "Evidential Assessment and Contest", "description": "How much confidence the cited material can carry, what limits it, and how contradiction and adverse source status are recorded without adjudicating.", "rationale": "GRADE defines an externally governed certainty scheme with explicit rate-down domains, and NISO CREC requires retraction status to propagate to citing works; both are properties the citation must carry, while the verdict remains with the citing model.", "source_refs": [ "SRC-010", "SRC-013" ], "layers": [ { "id": "certainty-assessment", "name": "Certainty and Limitations", "description": "Binding of an external rating scheme and recording of assessed limitations.", "source_refs": [ "SRC-010", "SRC-009" ], "findings": [ { "id": "certainty-and-limitations", "name": "Certainty rating binding and limitation domains", "description": "How much confidence the cited material provides for this citing context, expressed on an externally governed scheme with per-domain limitation results.", "source_refs": [ "SRC-010", "SRC-009", "SRC-008" ], "questions": [ { "id": "q-cal-measurement", "text": "Which rating scheme and scale value express the certainty this evidence provides for the citing context?", "kind": "measurement", "answer_data": [ "Certainty value and its ordinal scale", "Scheme identifier and bound version" ] }, { "id": "q-cal-authority", "text": "Which body owns the rating scheme definition, and which version is bound here?", "kind": "authority", "answer_data": [ "Scheme-owning organisation reference", "Bound scheme version and binding date" ] }, { "id": "q-cal-quality", "text": "Which limitation domains were assessed and with what result?", "kind": "quality", "answer_data": [ "Per-domain judgement covering rate-down domains such as risk of bias, imprecision, inconsistency, indirectness and publication bias", "Any rate-up factors applied" ] }, { "id": "q-cal-constraint", "text": "Under what conditions may a certainty value be asserted without a completed limitation assessment?", "kind": "constraint", "answer_data": [ "Provisional assessment rule and required disclosure", "Expiry of a provisional value" ] }, { "id": "q-cal-provenance", "text": "Who performed the assessment, when, and was the assessor independent of the citing author?", "kind": "provenance", "answer_data": [ "Assessor reference and role", "Assessment timestamp", "Independence declaration" ] } ], "data_elements": [ { "id": "de-cal-scheme", "name": "certainty-scheme-reference", "description": "Version-bound reference to the external certainty or quality rating scheme.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-010" ] }, { "id": "de-cal-value", "name": "certainty-value", "description": "Value on the bound scheme's scale.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-010" ] }, { "id": "de-cal-domain-result", "name": "limitation-domain-result", "description": "Judgement recorded for one limitation domain of the bound scheme.", "value_kind": "object", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-010" ] }, { "id": "de-cal-assessor", "name": "assessment-agent-reference", "description": "Agent that performed the assessment.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-cal-assessed-at", "name": "assessed-at", "description": "Instant the assessment was made.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [ { "id": "evidence-assessment-record", "name": "Evidence assessment record", "description": "A structured assessment sheet recording the bound rating scheme, the per-domain judgements, any rate-up factors and the narrative justification for the resulting certainty value.", "media_or_form": [ "structured assessment record", "tabular evidence profile", "narrative justification note" ], "serial": false, "identity_strategy": "Citation record identifier plus the bound scheme identifier and scheme version. A new scheme version yields a new assessment record; superseded assessments are versioned and retained, never renamed in place.", "source_refs": [ "SRC-010", "SRC-009" ] } ], "inline_only_rationale": null } ] }, { "id": "contest-and-status", "name": "Contest and Cited-Source Status", "description": "Cross-references to opposing evidence, and dated observations about the cited source's editorial status.", "source_refs": [ "SRC-013", "SRC-003" ], "findings": [ { "id": "contested-and-counter-evidence", "name": "Contested flag and counter-evidence references", "description": "Recording that other citation records address the same citing context with an opposing stance, without weighing them or reaching a conclusion.", "source_refs": [ "SRC-003", "SRC-012", "SRC-007" ], "questions": [ { "id": "q-cce-relationship", "text": "Which other citation records address the same citing context with an opposing stance?", "kind": "relationship", "answer_data": [ "Opposing citation record references", "Shared citing-context reference establishing the comparison" ] }, { "id": "q-cce-constraint", "text": "What may this record assert about a contradiction, and what conclusion-drawing is deferred to the citing model?", "kind": "constraint", "answer_data": [ "Permitted assertions limited to reference and flag", "Explicit list of deferred judgements and the model that owns them" ] }, { "id": "q-cce-state", "text": "Is this record currently flagged as contested, and what triggered the flag?", "kind": "state", "answer_data": [ "Contested flag and reason code", "Trigger event reference and raise timestamp" ] }, { "id": "q-cce-process", "text": "What procedure raises, reviews and clears a contested flag, and who may run it?", "kind": "process", "answer_data": [ "Raise, review and clear steps", "Roles permitted at each step" ] } ], "data_elements": [ { "id": "de-cce-opposing", "name": "opposing-record-reference", "description": "Reference to a citation record with an opposing stance on the same citing context.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003" ] }, { "id": "de-cce-flag", "name": "contested-flag", "description": "Whether the record is currently marked contested.", "value_kind": "boolean", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "de-cce-reason", "name": "contest-reason", "description": "Reason code for the contested state.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-012" ] }, { "id": "de-cce-raised-at", "name": "contest-raised-at", "description": "Instant the contested flag was raised.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] } ], "artifacts": [], "inline_only_rationale": "This finding holds only cross-references and a flag. The evaluation that weighs opposing evidence and reaches a verdict belongs to the claim and decision models, so producing a local adjudication artifact would create a rival source of truth for a judgement this model does not own." }, { "id": "cited-source-status-observation", "name": "Cited-source status observation", "description": "Dated observations that the cited source has been retracted, withdrawn, corrected, flagged with an expression of concern or superseded, recorded as observations rather than as ownership of the source's lifecycle.", "source_refs": [ "SRC-013", "SRC-007", "SRC-012" ], "questions": [ { "id": "q-csso-event", "text": "Which status event about the cited source has been observed?", "kind": "event", "answer_data": [ "Status code such as retraction, removal, expression of concern, correction or superseded version", "Scope of the event, whether whole work or a part" ] }, { "id": "q-csso-temporal", "text": "When did the status event occur at the source, and when was it observed here?", "kind": "temporal", "answer_data": [ "Event time at the source", "Observation time in this store", "Reason for any gap between them" ] }, { "id": "q-csso-provenance", "text": "From which authority or feed was the status observation obtained, and what identifier does the notice carry?", "kind": "provenance", "answer_data": [ "Status authority or feed reference", "Persistent identifier of the notice", "Retrieval method" ] }, { "id": "q-csso-process", "text": "What action does an adverse status observation trigger for this record and for the citing context?", "kind": "process", "answer_data": [ "Trigger rule such as raising a review flag or notifying the citing model", "Notification target and its owning model" ] } ], "data_elements": [ { "id": "de-csso-status", "name": "source-status-code", "description": "Observed editorial or technical status of the cited source.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "de-csso-event-at", "name": "status-event-at", "description": "Time the status event occurred at the source.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013", "SRC-004" ] }, { "id": "de-csso-observed-at", "name": "status-observed-at", "description": "Time the status was observed and recorded here.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-csso-notice", "name": "status-notice-identifier", "description": "Persistent identifier of the retraction or concern notice.", "value_kind": "identifier", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "de-csso-authority", "name": "status-source-authority", "description": "Authority or feed from which the observation was obtained.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] } ], "artifacts": [], "inline_only_rationale": "Status is a dated observation about a source whose lifecycle is governed by its publisher. The notice itself is published and persistently identified elsewhere, so this model stores the reference and the two timestamps rather than copying, re-issuing or re-asserting the notice." } ] } ] }, { "id": "provenance-and-integrity", "name": "Provenance and Integrity of the Citation Act", "description": "Who asserted the citation, when, with what tooling, and how the stored evidence is kept tamper-evident and independently verifiable.", "rationale": "PROV-O supplies the entity, activity and agent pattern for attributing an assertion; the Verifiable Credentials model separates documentary evidence from cryptographic proof; C2PA supplies content bindings for media integrity.", "source_refs": [ "SRC-002", "SRC-008", "SRC-011" ], "layers": [ { "id": "citation-act-provenance", "name": "Citation Act Provenance", "description": "Attribution of the assertion and the distinct times that describe it.", "source_refs": [ "SRC-002", "SRC-004" ], "findings": [ { "id": "asserting-agent-and-activity", "name": "Asserting agent, accountability and activity", "description": "Who or what asserted the evidential link, under which role, through which activity, and which organisation is accountable.", "source_refs": [ "SRC-002", "SRC-009", "SRC-008" ], "questions": [ { "id": "q-aaa-provenance", "text": "Which agent asserted this evidential link and through which activity?", "kind": "provenance", "answer_data": [ "Asserting agent reference", "Activity reference and its start and end times" ] }, { "id": "q-aaa-ownership", "text": "Which organisation is accountable for the assertion, as distinct from the individual or software that made it?", "kind": "ownership", "answer_data": [ "Accountable organisation reference", "Delegation chain from organisation to acting agent" ] }, { "id": "q-aaa-authority", "text": "On what declared basis was the asserting agent entitled to make this assertion?", "kind": "authority", "answer_data": [ "Authority basis reference held outside this model", "Permitted action codes for the agent" ] }, { "id": "q-aaa-classification", "text": "Is the asserting agent human, organisational or software, and how is that recorded?", "kind": "classification", "answer_data": [ "Agent kind code", "Software agent version and configuration reference where applicable" ] } ], "data_elements": [ { "id": "de-aaa-agent", "name": "asserting-agent-reference", "description": "Agent that asserted the citation, resolved through the party model.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-002" ] }, { "id": "de-aaa-kind", "name": "agent-kind", "description": "Whether the agent is a person, organisation or software.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-002" ] }, { "id": "de-aaa-org", "name": "accountable-organisation-reference", "description": "Organisation accountable for the assertion.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-aaa-activity", "name": "assertion-activity-reference", "description": "Activity during which the citation was asserted.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-aaa-delegation", "name": "delegation-chain", "description": "Ordered chain of delegation from the accountable organisation to the acting agent.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] } ], "artifacts": [], "inline_only_rationale": "Agents and activities are resolved through the party and provenance models. Holding an artifact here would duplicate identity records that those models master and would drift from them as roles change." }, { "id": "citation-time-model", "name": "Time model: event, observation and ingestion", "description": "The distinct time points a citation record must keep apart, their required form, and the validity interval of the assertion.", "source_refs": [ "SRC-004", "SRC-002", "SRC-008" ], "questions": [ { "id": "q-ctm-temporal", "text": "Which distinct timestamps must be recorded, and how do event time, observation time and ingestion time differ on this record?", "kind": "temporal", "answer_data": [ "Enumeration of required timestamps and their definitions", "Rule forbidding one from being copied into another when unknown" ] }, { "id": "q-ctm-constraint", "text": "What format, precision and offset rules apply to every timestamp in this model?", "kind": "constraint", "answer_data": [ "Canonical timestamp profile with seconds and explicit offset", "Handling of unknown local offset", "Conversion rule at protocol boundaries that use other formats" ] }, { "id": "q-ctm-lifecycle", "text": "Over what interval is the evidential assertion held valid, and what ends that interval?", "kind": "lifecycle", "answer_data": [ "Valid-from and valid-until values", "Events that terminate validity, such as supersession or adverse source status" ] }, { "id": "q-ctm-validation", "text": "How are implausible or out-of-order timestamps detected and rejected?", "kind": "validation", "answer_data": [ "Ordering constraints between timestamps", "Rejection and correction procedure" ] } ], "data_elements": [ { "id": "de-ctm-asserted-at", "name": "asserted-at", "description": "Event time at which the evidential assertion was made.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] }, { "id": "de-ctm-recorded-at", "name": "recorded-at", "description": "Ingestion time at which the record entered this store, set by the receiving system.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] }, { "id": "de-ctm-valid-from", "name": "valid-from", "description": "Start of the interval over which the assertion is held valid.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-ctm-valid-until", "name": "valid-until", "description": "End of the validity interval, where one is known.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [], "inline_only_rationale": "Timestamps are atomic values that must remain directly comparable and sortable within the record. Externalising them into an artifact would break the ordering constraints that validation depends on." } ] }, { "id": "integrity-and-verification", "name": "Integrity and Verification", "description": "Tamper-evidence over stored evidence, and independent confirmation that the citation still holds.", "source_refs": [ "SRC-011", "SRC-008" ], "findings": [ { "id": "excerpt-fixity-and-media-binding", "name": "Fixity of excerpt and capture, and media provenance binding", "description": "Digests over the excerpt and the consulted representation computed after a declared canonicalization, plus references to signed media provenance manifests where the cited material is a media asset.", "source_refs": [ "SRC-011", "SRC-008", "SRC-001" ], "questions": [ { "id": "q-efm-security", "text": "Which digest algorithm and values fix the excerpt and the consulted representation?", "kind": "security", "answer_data": [ "Named digest algorithm", "Digest value for the excerpt and for the representation", "Byte size and media type" ] }, { "id": "q-efm-constraint", "text": "What canonicalization is applied before digesting so that logically equal content yields equal digests?", "kind": "constraint", "answer_data": [ "Canonicalization profile identifier and version", "Whether prefix and suffix context are included in the digest input" ] }, { "id": "q-efm-evidence", "text": "Where the cited material is a media asset, which provenance manifest and binding are referenced as integrity evidence?", "kind": "evidence", "answer_data": [ "Manifest reference and its issuing system", "Binding kind, whether hard content hash or soft fingerprint or watermark" ] }, { "id": "q-efm-validation", "text": "What outcome is recorded when a recomputed digest no longer matches the stored value?", "kind": "validation", "answer_data": [ "Integrity-failed state and its effect on dependent verifications", "Retention rule for the mismatching artifact and its original digest" ] } ], "data_elements": [ { "id": "de-efm-algorithm", "name": "digest-algorithm", "description": "Named algorithm used to compute stored digests.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "de-efm-excerpt-digest", "name": "excerpt-digest", "description": "Digest of the canonicalized excerpt.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "de-efm-representation-digest", "name": "representation-digest", "description": "Digest of the consulted representation as captured.", "value_kind": "text", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "de-efm-canonicalization", "name": "canonicalization-profile", "description": "Profile applied before digesting.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-efm-manifest", "name": "media-manifest-reference", "description": "Reference to a signed media provenance manifest covering the cited asset.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] }, { "id": "de-efm-binding-kind", "name": "binding-kind", "description": "Whether the manifest binding is a hard content hash or a soft fingerprint or watermark.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-011" ] } ], "artifacts": [], "inline_only_rationale": "Digests, canonicalization profile identifiers and manifest references are compact structured values attached to the artifacts they protect. The signed manifest itself is produced, signed and validated by the media provenance system, so this model references it and never reproduces or re-issues it." }, { "id": "verification-record", "name": "Independent verification of the citation", "description": "Confirmation that the citation still resolves, still anchors and still bears the stance asserted, kept distinct from cryptographic proof and from the original assertion.", "source_refs": [ "SRC-008", "SRC-002", "SRC-010" ], "questions": [ { "id": "q-ver-validation", "text": "What verification was performed, by whom, and with what outcome?", "kind": "validation", "answer_data": [ "Verification outcome code", "Verifier reference and independence declaration", "Verification timestamp" ] }, { "id": "q-ver-process", "text": "Which verification depth was applied, from identifier resolution through anchor match to confirmation that the excerpt bears the asserted stance?", "kind": "process", "answer_data": [ "Depth code and per-step results", "Tooling used at each step" ] }, { "id": "q-ver-ownership", "text": "Who is accountable for a failed verification and what remediation is expected?", "kind": "ownership", "answer_data": [ "Accountable role", "Remediation action and due interval" ] }, { "id": "q-ver-temporal", "text": "How long does a verification remain valid before re-verification is required?", "kind": "temporal", "answer_data": [ "Verification validity interval by source category", "Expiry timestamp" ] } ], "data_elements": [ { "id": "de-ver-outcome", "name": "verification-outcome", "description": "Result of the verification pass.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-ver-depth", "name": "verification-depth", "description": "How deep the verification went.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-ver-verifier", "name": "verifier-reference", "description": "Agent that performed the verification.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-ver-verified-at", "name": "verified-at", "description": "Instant the verification was completed.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-ver-expires-at", "name": "verification-expires-at", "description": "Instant after which the verification is treated as stale.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [ { "id": "citation-verification-report", "name": "Citation verification report", "description": "A dated report of one verification pass covering resolution, re-anchoring, digest comparison and stance confirmation, with per-step outcomes and any drift findings.", "media_or_form": [ "structured verification report", "human-readable review note" ], "serial": true, "identity_strategy": "Citation record identifier plus a never-reused verification ordinal. Verifier identity and completion datetime are attributes of the report, not components of its identifier.", "source_refs": [ "SRC-008", "SRC-002" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "lifecycle-and-governance", "name": "Record Lifecycle and Governance", "description": "States and transitions of the citation record itself, its versioning, its stewardship, and its disposition.", "rationale": "The Verifiable Credentials model treats status and validity as first-class, DataCite governs versioning and obsolescence relations, and NISO CREC requires status change to propagate; a citation record therefore needs its own lifecycle distinct from either endpoint.", "source_refs": [ "SRC-008", "SRC-007", "SRC-013" ], "layers": [ { "id": "record-lifecycle", "name": "Record Lifecycle", "description": "Permitted states, transitions, versioning and supersession of the citation record.", "source_refs": [ "SRC-008", "SRC-007" ], "findings": [ { "id": "lifecycle-states", "name": "Citation record states and transitions", "description": "The states a citation record may occupy, the permitted transitions between them, and what becomes immutable on assertion.", "source_refs": [ "SRC-008", "SRC-002", "SRC-013" ], "questions": [ { "id": "q-lcs-lifecycle", "text": "Which states may a citation record occupy and which transitions between them are permitted?", "kind": "lifecycle", "answer_data": [ "State enumeration such as proposed, asserted, verified, contested, superseded, withdrawn and disposed", "Permitted transition matrix" ] }, { "id": "q-lcs-state", "text": "What is the current state, and which reason code and actor produced the last transition?", "kind": "state", "answer_data": [ "Current state and entry timestamp", "Transition reason code and acting agent reference" ] }, { "id": "q-lcs-constraint", "text": "Which fields become immutable once the record reaches the asserted state?", "kind": "constraint", "answer_data": [ "Immutable field set", "Escape route requiring a new version rather than an edit" ] }, { "id": "q-lcs-exception", "text": "How is a record handled when its cited source becomes permanently unavailable?", "kind": "exception", "answer_data": [ "Permitted state for an unresolvable source", "Requirement to retain excerpt, digest and capture as surviving evidence" ] } ], "data_elements": [ { "id": "de-lcs-state", "name": "record-state", "description": "Current lifecycle state of the citation record.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-008" ] }, { "id": "de-lcs-entered-at", "name": "state-entered-at", "description": "Instant the current state was entered.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] }, { "id": "de-lcs-reason", "name": "transition-reason", "description": "Reason code for the most recent transition.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "de-lcs-actor", "name": "transition-actor-reference", "description": "Agent that performed the transition.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-lcs-immutable", "name": "immutable-field-set", "description": "Fields frozen once the record is asserted.", "value_kind": "collection", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [], "inline_only_rationale": "States and transitions are coded values evaluated in place on the record. Externalising them would separate the state from the data it constrains and invite the two to diverge." }, { "id": "supersession-and-versioning", "name": "Versioning and supersession", "description": "How corrections produce new versions, how predecessors stay resolvable, and how change is attributed.", "source_refs": [ "SRC-007", "SRC-002", "SRC-008" ], "questions": [ { "id": "q-sav-lifecycle", "text": "Is a correction expressed as an in-place update or as a new version that supersedes the prior record?", "kind": "lifecycle", "answer_data": [ "Change classification rule by field", "Version increment policy" ] }, { "id": "q-sav-relationship", "text": "Which record supersedes this one and which does this one supersede?", "kind": "relationship", "answer_data": [ "Supersedes and superseded-by references", "Relation vocabulary term used for the link" ] }, { "id": "q-sav-provenance", "text": "What change reason, actor and timestamp are recorded for each version?", "kind": "provenance", "answer_data": [ "Change reason code", "Acting agent reference", "Version creation timestamp" ] }, { "id": "q-sav-constraint", "text": "Must a superseded record remain resolvable, and for how long?", "kind": "constraint", "answer_data": [ "Resolvability obligation for predecessors", "Minimum retention interval tied to the citing context" ] } ], "data_elements": [ { "id": "de-sav-version", "name": "record-version", "description": "Version designation of this citation record.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-sav-supersedes", "name": "supersedes-reference", "description": "Prior record versions that this one replaces.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-sav-superseded-by", "name": "superseded-by-reference", "description": "Successor record that replaces this one.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-007" ] }, { "id": "de-sav-change-reason", "name": "change-reason", "description": "Reason the new version was created.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-sav-created-at", "name": "version-created-at", "description": "Instant this version was created.", "value_kind": "timestamp", "cardinality": "1", "required": true, "source_refs": [ "SRC-004" ] } ], "artifacts": [], "inline_only_rationale": "Version links are reference values that must resolve through the same identifier service as the records themselves. A separate artifact would introduce a second, weaker path to the version graph." } ] }, { "id": "governance-and-disposition", "name": "Governance and Disposition", "description": "Stewardship, declared authority, retention class binding and the surviving stub after disposition.", "source_refs": [ "SRC-013", "SRC-008" ], "findings": [ { "id": "stewardship-and-authority", "name": "Ownership, stewardship and declared authority basis", "description": "Which parties own and maintain the record, and on what externally held basis actions on it are permitted. Declaration only, never enforcement.", "source_refs": [ "SRC-002", "SRC-008", "SRC-013" ], "questions": [ { "id": "q-saa-ownership", "text": "Which party owns this citation record and which party maintains it operationally?", "kind": "ownership", "answer_data": [ "Owner reference", "Steward or maintainer reference", "Handover procedure reference" ] }, { "id": "q-saa-authority", "text": "Which declared authority basis permits assertion, verification, supersession and withdrawal, and where is that basis held?", "kind": "authority", "answer_data": [ "Authority basis reference resolved outside this model", "Permitted action codes per role" ] }, { "id": "q-saa-decision", "text": "Who resolves a dispute between the asserting agent and a reviewer over a citation's stance?", "kind": "decision", "answer_data": [ "Escalation path and deciding role", "Recording rule for the outcome as a state change plus reason" ] }, { "id": "q-saa-constraint", "text": "What review cadence and reviewer independence are required for high-consequence citations?", "kind": "constraint", "answer_data": [ "Consequence classification and its cadence", "Independence criteria for reviewers" ] } ], "data_elements": [ { "id": "de-saa-owner", "name": "owner-reference", "description": "Party accountable for the record.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-002" ] }, { "id": "de-saa-steward", "name": "steward-reference", "description": "Party that maintains the record operationally.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002" ] }, { "id": "de-saa-authority", "name": "authority-basis-reference", "description": "Reference to the externally held basis on which actions are permitted.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-saa-permitted", "name": "permitted-action", "description": "Action codes declared permissible for a role on this record.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-saa-cadence", "name": "review-cadence", "description": "Declared interval between reviews.", "value_kind": "duration", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] } ], "artifacts": [], "inline_only_rationale": "These are declarative pointers to parties and to an externally held authority basis. The runtime evaluation of whether an actor may act, the enforcement point that stops them, and the log of what they did are owned by the adopting Dimension's policy and audit services, so no local governance artifact is issued." }, { "id": "retention-and-disposition", "name": "Retention class, disposition state and surviving stub", "description": "How long the record, excerpt and captures are kept and how removal is expressed without breaking citing contexts or destroying re-verifiability.", "source_refs": [ "SRC-013", "SRC-008", "SRC-001" ], "questions": [ { "id": "q-rad-retention", "text": "Which retention class applies to the record, the excerpt and the capture, and who owns that schedule?", "kind": "retention", "answer_data": [ "Retention class reference per component", "Owning retention service reference" ] }, { "id": "q-rad-exception", "text": "How is a takedown, licence expiry or legal hold expressed on this record?", "kind": "exception", "answer_data": [ "Disposition state and reason code", "Legal hold reference and its owning service" ] }, { "id": "q-rad-constraint", "text": "What minimum stub must survive disposition so that citing contexts do not become dangling references?", "kind": "constraint", "answer_data": [ "Stub element set including identifier, state, reason, timestamp and successor link", "Resolution behaviour for a stub" ] }, { "id": "q-rad-privacy", "text": "Which parts of the record may be redacted while the locator and fixity values are preserved?", "kind": "privacy", "answer_data": [ "Redactable element list", "Elements that must survive redaction to keep the citation re-verifiable" ] } ], "data_elements": [ { "id": "de-rad-class", "name": "retention-class-reference", "description": "Reference to the retention class assigned by the owning records service.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "de-rad-state", "name": "disposition-state", "description": "Current disposition state such as active, redacted, tombstoned or disposed.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "de-rad-stub", "name": "tombstone-stub", "description": "Minimal surviving record retained after disposition.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-rad-hold", "name": "legal-hold-reference", "description": "Reference to a hold asserted by the owning retention service.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-013" ] }, { "id": "de-rad-redaction", "name": "redaction-marker", "description": "Marker recording that a named element was redacted and on what basis.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] } ], "artifacts": [], "inline_only_rationale": "Retention schedules and their execution belong to the adopting Dimension's records service. This model records only the class reference, hold reference, disposition state and surviving stub, so issuing a disposition certificate here would claim an authority the model does not hold." } ] } ] }, { "id": "interoperability", "name": "Interoperability, Exchange and Access", "description": "How citation records map to external vocabularies, how they are exchanged, and how sensitivity is declared.", "rationale": "DataCite, CiTO, the Web Annotation model and schema.org each govern part of the citation surface and disagree in places; a conservative model must record mappings with evidence and refuse unevidenced conformance claims.", "source_refs": [ "SRC-007", "SRC-003", "SRC-001", "SRC-012" ], "layers": [ { "id": "vocabulary-alignment", "name": "Vocabulary Alignment", "description": "Declared mappings to external standards with strength, evidence and recorded conflicts.", "source_refs": [ "SRC-003", "SRC-007" ], "findings": [ { "id": "external-vocabulary-alignment", "name": "External vocabulary alignment and conformance evidence", "description": "Term-by-term mappings from local stance, evidence-type and relation vocabularies to external standards, with mapping strength, supporting evidence and known conflicts.", "source_refs": [ "SRC-003", "SRC-007", "SRC-012", "SRC-009" ], "questions": [ { "id": "q-eva-interop", "text": "Which external terms does each local term map to, and with what mapping strength?", "kind": "interoperability", "answer_data": [ "Local term and target term pairs", "Mapping strength such as exact, broader, narrower or related", "Target vocabulary version" ] }, { "id": "q-eva-evidence", "text": "What evidence supports each conformance or alignment claim, and against which target version was it tested?", "kind": "evidence", "answer_data": [ "Test result or registration reference", "Target version tested and test date" ] }, { "id": "q-eva-constraint", "text": "Which local terms have no defensible external equivalent and must remain local?", "kind": "constraint", "answer_data": [ "Unmapped local term list with justification", "Loss statement for round-trips through each target" ] }, { "id": "q-eva-provenance", "text": "Who authored and last reviewed the alignment, and when?", "kind": "provenance", "answer_data": [ "Alignment author and reviewer references", "Last review timestamp and next review due" ] } ], "data_elements": [ { "id": "de-eva-local-term", "name": "local-term", "description": "Local controlled value being mapped.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003" ] }, { "id": "de-eva-target", "name": "target-vocabulary-reference", "description": "Version-bound reference to the external vocabulary and term.", "value_kind": "reference", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-eva-strength", "name": "mapping-strength", "description": "Strength of the mapping between local and target term.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-eva-evidence", "name": "alignment-evidence-reference", "description": "Reference to the test result or registration supporting a conformance claim.", "value_kind": "reference", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-eva-conflict", "name": "known-conflict", "description": "Recorded conflict or loss when mapping to a target vocabulary.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-012" ] } ], "artifacts": [ { "id": "vocabulary-crosswalk", "name": "Vocabulary crosswalk", "description": "A term-by-term crosswalk mapping local stance, evidence-type and relation values to named external vocabulary terms, with mapping strength, loss notes and supporting test references.", "media_or_form": [ "tabular crosswalk", "machine-readable mapping set" ], "serial": false, "identity_strategy": "Model identifier plus the target vocabulary identifier and that target's own version string. A new target version produces a new crosswalk rather than an in-place edit, so historical mappings stay auditable.", "source_refs": [ "SRC-003", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "exchange-and-access", "name": "Exchange and Access", "description": "Profile obligations for exchanging records, and the sensitivity declarations that travel with them.", "source_refs": [ "SRC-007", "SRC-001", "SRC-008" ], "findings": [ { "id": "exchange-profile", "name": "Exchange profile obligations and extension rules", "description": "Which elements are mandatory, conditional or optional for interoperable exchange, how extensions are carried, and what test establishes conformance, independent of serialization.", "source_refs": [ "SRC-007", "SRC-001", "SRC-008" ], "questions": [ { "id": "q-exp-requirement", "text": "Which elements are mandatory, conditional or optional in an interoperable citation record?", "kind": "requirement", "answer_data": [ "Element obligation table", "Conditions that promote a conditional element to mandatory" ] }, { "id": "q-exp-interop", "text": "Which profile constraints must every serialization projection satisfy?", "kind": "interoperability", "answer_data": [ "Serialization-independent constraint list", "Mapping of each constraint to its check in a given projection" ] }, { "id": "q-exp-constraint", "text": "How are vendor or unknown extensions carried without breaking consumers?", "kind": "constraint", "answer_data": [ "Extension namespace rule", "Consumer behaviour for unrecognised elements" ] }, { "id": "q-exp-validation", "text": "What conformance test determines that an exchanged record satisfies the profile?", "kind": "validation", "answer_data": [ "Conformance test reference and pass criteria", "Result record and its validity period" ] } ], "data_elements": [ { "id": "de-exp-profile", "name": "profile-reference", "description": "Version-bound reference to the exchange profile in force.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-exp-obligation", "name": "element-obligation", "description": "Obligation level assigned to an element by the profile.", "value_kind": "code", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-007" ] }, { "id": "de-exp-extension", "name": "extension-namespace", "description": "Namespace under which local extensions are carried.", "value_kind": "text", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-exp-test", "name": "conformance-test-reference", "description": "Reference to the test whose result substantiates a conformance claim.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [ { "id": "exchange-profile-specification", "name": "Exchange profile specification", "description": "A written application profile listing element obligations, controlled-value bindings, extension rules and conformance tests, expressed independently of any serialization format.", "media_or_form": [ "application profile document", "machine-readable profile constraints" ], "serial": false, "identity_strategy": "Model identifier plus profile name and semantic version. Profile versions are additive; a published version is never silently redefined, and breaking changes force a new major version.", "source_refs": [ "SRC-007", "SRC-001" ] } ], "inline_only_rationale": null }, { "id": "access-and-confidentiality", "name": "Sensitivity, embargo and disclosure scope", "description": "Classification of the record, its excerpt and its captures, together with embargo and licence conditions restricting disclosure. Labels and references only.", "source_refs": [ "SRC-001", "SRC-008", "SRC-011" ], "questions": [ { "id": "q-aac-access", "text": "What sensitivity classification applies to the record, the excerpt and the capture, and who may read each?", "kind": "access", "answer_data": [ "Sensitivity class per component", "Disclosure scope codes", "Reference to the policy that will be evaluated elsewhere" ] }, { "id": "q-aac-privacy", "text": "Which excerpt content must be masked or withheld when the record leaves its origin?", "kind": "privacy", "answer_data": [ "Masking rule per data category", "Masked rendition reference" ] }, { "id": "q-aac-exception", "text": "Which embargo, licence or confidentiality condition temporarily restricts disclosure, and when does it lapse?", "kind": "exception", "answer_data": [ "Embargo expiry timestamp", "Licence or confidentiality reference and its terms location" ] }, { "id": "q-aac-constraint", "text": "May a locator be disclosed when the excerpt may not, and how is that partial disclosure expressed?", "kind": "constraint", "answer_data": [ "Component-level disclosure matrix", "Marker indicating suppressed components in an export" ] } ], "data_elements": [ { "id": "de-aac-sensitivity", "name": "sensitivity-class", "description": "Classification governing disclosure of the record or one of its components.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-008" ] }, { "id": "de-aac-scope", "name": "disclosure-scope", "description": "Scope within which a component may be disclosed.", "value_kind": "code", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-008" ] }, { "id": "de-aac-embargo", "name": "embargo-until", "description": "Instant at which an embargo lapses.", "value_kind": "timestamp", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004" ] }, { "id": "de-aac-licence", "name": "licence-reference", "description": "Reference to the licence governing reuse of the excerpt or capture.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001" ] }, { "id": "de-aac-policy", "name": "access-policy-reference", "description": "Reference to the externally held policy that an enforcement point will evaluate.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-008" ] } ], "artifacts": [], "inline_only_rationale": "Only classification labels and pointers to externally held policies and licences live here. The decision engine that evaluates a request, the enforcement point that applies the outcome, and the access log are owned by the adopting Dimension, so this model deliberately produces no access artifact." } ] } ] } ] }, "functions": [ { "id": "mint-citation-record", "name": "Mint citation record", "description": "Create a reified citation record linking a citing context to a cited source with a typed stance.", "inputs": [ "Citing-context reference", "Cited source identifier or access URI", "Stance code and bound vocabulary version", "Asserting agent reference" ], "outputs": [ "Citation record identifier", "Initial record state", "Recorded-at and asserted-at timestamps" ], "preconditions": [ "The citing-context reference resolves in its owning model", "The stance vocabulary version is bound", "The asserting agent is identified and its kind declared", "Deduplication key computed and checked" ], "effects": [ "Creates a citation record in the proposed state", "Links to an existing record instead of minting a duplicate when the deduplication key matches", "Leaves the citing context and the cited source unmodified" ], "source_refs": [ "SRC-003", "SRC-001", "SRC-002" ] }, { "id": "resolve-source-locator", "name": "Resolve source locator", "description": "Resolve a preferred citation identifier or access URI to a retrievable representation, optionally at a target datetime.", "inputs": [ "Preferred citation identifier or access URI", "Optional target datetime for time-based access" ], "outputs": [ "Resolved representation reference", "Resolution status and redirect chain", "Discovered preferred citation identifier where advertised" ], "preconditions": [ "At least one identifier or URI is present", "Resolver and time gate endpoints are reachable or their failure is recordable" ], "effects": [ "Records the resolution outcome and any redirect chain", "Populates the preferred citation identifier when a preferred-reference link is advertised by the source", "Sets locator health state" ], "source_refs": [ "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "anchor-cited-excerpt", "name": "Anchor cited excerpt", "description": "Attach selectors and an excerpt locating the cited portion within a retrieved representation.", "inputs": [ "Resolved representation", "Requested anchor granularity", "Canonicalization profile" ], "outputs": [ "Selector set with refinement chain", "Excerpt with prefix and suffix context", "Excerpt digest" ], "preconditions": [ "A representation has been retrieved", "A canonicalization profile is declared", "Licence and privacy limits on excerpting have been checked" ], "effects": [ "Attaches selectors and the excerpt to the record", "Flags whole-resource granularity with a reason when finer anchoring is impossible", "Suppresses excerpt text where reproduction is not permitted while retaining selectors and digest" ], "source_refs": [ "SRC-001", "SRC-011", "SRC-003" ] }, { "id": "capture-representation-state", "name": "Capture representation state", "description": "Record the state of the representation consulted, including access datetime, version, archived snapshot and fixity.", "inputs": [ "Resolved representation", "Request conditions", "Archive or time gate endpoint where available" ], "outputs": [ "Consulted representation capture", "Access timestamp and any archive datetime", "Representation digest" ], "preconditions": [ "The retention class permits storing a capture", "The licence permits retaining a copy of the representation" ], "effects": [ "Stores a point-in-time capture with its digest and media type", "Records the archived snapshot and time gate references", "Does not schedule or perform ongoing archiving, which remains with the archiving service" ], "source_refs": [ "SRC-006", "SRC-001", "SRC-004" ] }, { "id": "classify-evidential-link", "name": "Classify evidential link", "description": "Assign stance, evidence type and assertion method to the citation record.", "inputs": [ "Excerpt or whole-resource anchor", "Stance vocabulary and evidence-type vocabulary with versions", "Assertion method context" ], "outputs": [ "Stance code and polarity", "Evidence-type code", "Assertion method code and machine confidence where automated" ], "preconditions": [ "An anchor exists at some granularity", "Both vocabularies and their versions are declared by the owning package" ], "effects": [ "Sets the typed classification on the record", "Records tool and model version when the classification was produced automatically", "Blocks promotion beyond draft when the minimum granularity rule is unmet" ], "source_refs": [ "SRC-003", "SRC-009", "SRC-002" ] }, { "id": "assess-evidential-certainty", "name": "Assess evidential certainty", "description": "Bind an external certainty scheme and record a certainty value with its per-domain limitation results.", "inputs": [ "Citation record", "Selected rating scheme and version", "Per-domain limitation judgements", "Assessor reference" ], "outputs": [ "Certainty value", "Per-domain results and rate-up factors", "Evidence assessment record" ], "preconditions": [ "The scheme is externally defined and version-bound", "The assessor is identified and independence is declared" ], "effects": [ "Attaches a new assessment or supersedes a prior one for the same scheme", "Never redefines or extends the external scheme's own definitions", "Marks the assessment provisional when domain judgements are incomplete" ], "source_refs": [ "SRC-010", "SRC-009", "SRC-008" ] }, { "id": "reverify-citation", "name": "Re-verify citation and detect drift", "description": "Re-resolve the locator, re-apply selectors, recompute digests and confirm the asserted stance still holds.", "inputs": [ "Citation record", "Requested verification depth", "Prior digests and excerpt" ], "outputs": [ "Verification outcome and per-step results", "Recomputed digests and anchor match result", "Drift findings" ], "preconditions": [ "A locator is present", "Prior digests or an excerpt exist for comparison", "The verifier is identified" ], "effects": [ "Appends a verification report and sets verification validity", "Sets locator health and may raise a content-drifted or contested flag", "Never modifies the citing context, whose own status remains with its owning model" ], "source_refs": [ "SRC-008", "SRC-001", "SRC-006" ] }, { "id": "record-source-status-observation", "name": "Record cited-source status observation", "description": "Record a dated observation that the cited source has been retracted, corrected, removed, flagged or superseded.", "inputs": [ "Cited source identifier", "Status authority or feed response", "Notice identifier where published" ], "outputs": [ "Status code", "Event time at the source and observation time here", "Notice reference" ], "preconditions": [ "A status authority or feed for the source is identified", "The event time and observation time can be distinguished or the gap explained" ], "effects": [ "Appends a dated observation to the record", "May raise a review flag and notify the citing model through its own interface", "Does not assert, execute or publish the source's retraction, which belongs to the source's publisher" ], "source_refs": [ "SRC-013", "SRC-007", "SRC-012" ] }, { "id": "supersede-citation-record", "name": "Supersede or withdraw citation record", "description": "Create a successor version or withdraw a record, preserving resolvability of the predecessor.", "inputs": [ "Current record", "Change reason code", "Replacement content or withdrawal instruction", "Acting agent reference" ], "outputs": [ "New record version or withdrawn state", "Supersedes and superseded-by links", "Transition timestamp" ], "preconditions": [ "The acting agent holds a declared permitted action for supersession or withdrawal", "No legal hold forbids the change", "Immutable fields are respected" ], "effects": [ "Creates a successor version and marks the predecessor superseded while keeping it resolvable", "Records reason, actor and timestamp on both versions", "Leaves the citing context to decide what its own status becomes" ], "source_refs": [ "SRC-007", "SRC-002", "SRC-008" ] }, { "id": "project-to-exchange-profile", "name": "Project record to an exchange profile", "description": "Produce a profile-conformant projection of a citation record for exchange with another system.", "inputs": [ "Citation record", "Target profile and version", "Vocabulary crosswalk for the target" ], "outputs": [ "Profile-conformant projection", "Unmapped element and loss report", "Conformance claim status" ], "preconditions": [ "A crosswalk exists for the target vocabulary version", "Profile obligations are declared", "Disclosure scope permits export of each included component" ], "effects": [ "Emits the projection with suppressed components marked rather than silently dropped", "Records unmapped local terms and round-trip loss", "Asserts conformance only where a valid conformance test result exists" ], "source_refs": [ "SRC-007", "SRC-001", "SRC-003" ] }, { "id": "mark-record-disposition", "name": "Mark record disposition", "description": "Apply a disposition state, redaction markers and tombstone stub on instruction from the owning retention service.", "inputs": [ "Retention class decision from the adopting Dimension", "Disposition instruction", "Legal hold status from the owning service" ], "outputs": [ "Disposition state", "Tombstone stub", "Redaction markers" ], "preconditions": [ "The retention class reference resolves", "Legal hold status has been checked with its owning service", "The surviving stub element set is declared" ], "effects": [ "Sets disposition state and reduces the record to a resolvable stub", "Redacts or purges excerpts and captures while retaining selectors, digests and identifiers", "Leaves schedule ownership, erasure execution and hold determination with the adopting Dimension's records service" ], "source_refs": [ "SRC-013", "SRC-008", "SRC-001" ] } ], "composition": [ { "target": "WM-KNW-007 Claim / Assertion", "relation": "REFERENCE", "purpose": "Carry a resolving reference to the claim that is supported or challenged, plus the locus within it. Claim wording, decomposition, truth status and lifecycle stay in the claim model and are never mirrored here.", "required": false, "source_refs": [ "SRC-003", "SRC-012" ] }, { "target": "WM-KNW-010 Decision rationale", "relation": "REFERENCE", "purpose": "Let a rationale step point at citation records for explainability. Options, criteria, deliberation and decision lifecycle remain owned by the decision model.", "required": false, "source_refs": [ "SRC-008", "SRC-002" ] }, { "target": "Party / Agent model", "relation": "REFERENCE", "purpose": "Resolve asserting agents, verifiers, accountable organisations and responsible parties instead of mastering person or organisation records in this model.", "required": true, "source_refs": [ "SRC-002", "SRC-008" ] }, { "target": "Bibliographic source-work registry (DataCite, Crossref or equivalent)", "relation": "REFERENCE", "purpose": "Dereference full bibliographic metadata and identifier authority for the cited work. Only a non-authoritative minimal descriptor with a refresh timestamp is cached locally.", "required": false, "source_refs": [ "SRC-007", "SRC-005" ] }, { "target": "Web archiving service conforming to the Memento framework", "relation": "REFERENCE", "purpose": "Record archived snapshot and time gate URIs with archive datetimes. Capture scheduling, storage and preservation actions remain with the archiving service.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "Adopting-Dimension access policy and audit service", "relation": "REFERENCE", "purpose": "Hold sensitivity labels and policy references only. Request evaluation, enforcement and audit-trail records are owned entirely by that service; referencing an audit event confers no ownership of audit semantics.", "required": true, "source_refs": [ "SRC-008", "SRC-001" ] }, { "target": "Adopting-Dimension records retention and disposition service", "relation": "REFERENCE", "purpose": "Bind a retention class, receive disposition instructions and read legal-hold status. Schedule ownership, hold determination and erasure execution stay outside this model.", "required": true, "source_refs": [ "SRC-013", "SRC-008" ] }, { "target": "CiTO, the Citation Typing Ontology", "relation": "ALIGN", "purpose": "Map local stance values onto CiTO citation properties and adopt its reified citation pattern. Alignment only, with conflicts and unmapped terms recorded.", "required": false, "source_refs": [ "SRC-003" ] }, { "target": "W3C PROV-O", "relation": "ALIGN", "purpose": "Express the citation act as entity, activity and agent for provenance interchange, without importing a general provenance graph for the wider knowledge base.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "W3C Web Annotation Data Model", "relation": "ALIGN", "purpose": "Adopt the selector, refinement and state patterns for in-resource anchoring and consulted-representation binding, normalising timestamps at the boundary.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "DataCite Metadata Schema relationType vocabulary", "relation": "ALIGN", "purpose": "Map citation direction, versioning and obsolescence relations onto a governed relation vocabulary for scholarly exchange, recording the loss where challenge stances have no equivalent.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "Evidence and Conclusion Ontology (ECO)", "relation": "ALIGN", "purpose": "Bind evidence-type and assertion-method values, declaring local extension terms explicitly where the target's biomedical scope does not reach.", "required": false, "source_refs": [ "SRC-009" ] }, { "target": "GRADE certainty-of-evidence framework", "relation": "ALIGN", "purpose": "Bind an externally governed certainty scale and its rate-down and rate-up domains as an assessment scheme, without redefining or extending the scheme itself.", "required": false, "source_refs": [ "SRC-010" ] }, { "target": "C2PA Content Credentials", "relation": "ALIGN", "purpose": "Reference signed media provenance manifests and their hard or soft bindings as integrity evidence for media excerpts. Signing, certificate handling and validation are performed by that system.", "required": false, "source_refs": [ "SRC-011" ] }, { "target": "NISO RP-45-2024 CREC", "relation": "ALIGN", "purpose": "Align cited-source status observations with the recommended retraction, removal and expression-of-concern metadata and its propagation to citing works.", "required": false, "source_refs": [ "SRC-013" ] }, { "target": "schema.org ClaimReview", "relation": "ALIGN", "purpose": "Map web-publication fact-check linkage, making explicit that the verdict rating sits with the citing claim model while only stance is carried here.", "required": false, "source_refs": [ "SRC-012" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "The owning package must declare the stance, evidence-type and certainty vocabularies it binds, each with a resolvable reference and an explicit version.", "The owning package must name the master system for citation record identifiers and the fallback identifier scheme it mints when no master system exists.", "The owning package must name the retention and disposition service, the access policy and audit service, and the party model it delegates to, since this model owns none of them.", "The owning package must declare which citing-context models are permitted endpoints and how their references resolve." ], "namespace_guidance": "Local record identifiers and local controlled values are minted in a Dimension-scoped namespace and never inside an external standard's namespace. External terms are referenced by their governing IRI together with the version in force. Local extensions to an aligned vocabulary live under a clearly separated local extension path so that a consumer can distinguish standard terms from local ones without a lookup.", "registry_links": [ "DataCite Metadata Schema relationType as the governed vocabulary for citation direction, versioning and obsolescence relations.", "SPAR CiTO property set as the governed citation-intent vocabulary for supporting and challenging stances.", "The cite-as link relation as the governed mechanism for discovering a source's preferred citation identifier.", "Evidence and Conclusion Ontology as the governed evidence-type and assertion-method vocabulary where scientific evidence is cited.", "The GRADE certainty framework as a bindable external certainty scheme." ] }, "canon_and_patch": { "canonicalization_rules": [ "Declare a canonicalization profile before digesting any excerpt: a fixed Unicode normalization form, defined whitespace folding, a defined line-ending form, and explicit inclusion or exclusion of prefix and suffix context in the digest input.", "Normalize identifiers before comparison or deduplication: consistent case for scheme and prefix, resolver host removed, percent-encoding normalized; retain both the raw and normalized forms so the original is never lost.", "Serialize all timestamps in the canonical form and sort repeated elements by a declared stable key before digesting, so that logically equal records produce equal digests across projections." ], "patch_rules": [ "Patches address individual elements by stable path and never reorder or renumber collections as a side effect of an unrelated change.", "Any patch that alters stance, locator, anchor, excerpt, fixity or certainty on an asserted record produces a new record version rather than an in-place edit.", "Every patch carries a change reason code, the acting agent reference and an ingestion timestamp; a patch without a reason code is rejected.", "A patch may not write a value into an element owned by a referenced model, such as claim status or audit outcome; such a patch is rejected at the boundary." ], "compatibility_rules": [ "Adding an optional element or a new controlled value is a minor change. Removing an element, narrowing cardinality or retiring a controlled value is breaking and requires a new profile major version.", "Retired controlled values remain resolvable and carry a mapping to their replacement rather than being deleted.", "A conformance claim against an external vocabulary version is invalidated when that version changes and must be re-tested before it is restated." ] }, "artifact_rules": { "identity_priority": [ "The authoritative master-system identifier issued by the system of record for the citation, such as the curation platform's citation record key, is used first and is never re-minted locally.", "Where no master-system identifier exists, a governed global identifier or IRI such as a DOI, Handle or registered persistent IRI, resolvable through its own registry, is used.", "Only when neither exists does the adopting Dimension assign a UUID or ULID in its own namespace. A date, a URL that may change, and a content digest are never used as the primary identifier." ], "timestamp_rule": "All time values are recorded in RFC 3339 form with an explicit seconds component and an explicit offset or Z, for example 2026-09-02T14:03:07Z or 2026-09-02T16:03:07+02:00, using -00:00 only to signal a known UTC instant whose local offset is unknown. Event time (when the assertion was made, when the cited source was published, changed or retracted) is recorded separately from observation or ingestion time (when the representation was accessed, when the status was observed, when the record entered this store); where only one is known the other is left empty rather than copied across. Protocol formats that use another representation, such as the RFC 1123 datetimes carried in time-based access headers, are converted to this form on storage.", "serial_naming_rule": "Serial artifacts, namely excerpt captures, consulted-representation captures, locator check reports and verification reports, are named as the citation record identifier plus a zero-padded ordinal that increases monotonically and is never reused, even after a member is deleted. Capture datetimes, verifier names and digests are attributes of the artifact and never form part of its name.", "integrity_rule": "Every stored artifact carries a named digest algorithm, a digest value computed after the declared canonicalization profile, a byte size and a media type. A recomputation mismatch sets the artifact to an integrity-failed state and marks dependent verification results stale; the artifact and its original digest are retained as evidence of the mismatch rather than silently replaced." }, "policies": [ "Conformance to an external standard is asserted only where a dated test result or authoritative registration is recorded. Otherwise the relationship is recorded as an alignment with its known conflicts and round-trip losses.", "A citation record never restates, caches as authoritative, or version-controls the content or status of the citing claim or decision it points at; those remain mastered by their owning models.", "Automatically generated citations are marked with their assertion method, tool and model version, and may not enter a verified state without a recorded independent verification pass.", "Excerpts are stored only within licence and privacy limits. Where reproduction is not permitted, the locator, selectors and digests are retained without the excerpt text, so the citation stays re-verifiable at the source.", "This model records references to policy, hold and audit artefacts but never evaluates, enforces or writes them." ], "crud": { "read": [ "Reading a record returns identity, locator, stance, provenance and current state. Excerpts and captures are returned only where the requester's disclosure scope permits, with suppressed components explicitly marked.", "Superseded, withdrawn and tombstoned records remain readable by identifier, returning state, reason and successor link so that historical citing contexts never dangle.", "A read may specify a target datetime to obtain the record version that was current at that instant, distinguishing what was asserted then from what is asserted now." ], "create": [ "A record may be created only with a resolving citing-context reference, at least one source identifier or access URI, a stance value drawn from a version-bound vocabulary, and an identified asserting agent.", "Creation sets ingestion time from the receiving system clock and assertion time from the assertion event; the two are stored separately and never conflated.", "Duplicate detection runs on the normalized deduplication key before minting; a match returns a link to the existing record rather than creating a second one." ], "update": [ "Non-evidential fields such as notes, review cadence and the cached source descriptor may be updated in place with a change reason and acting agent.", "Changes to stance, locator, anchor, excerpt, fixity or certainty on an asserted record produce a new version with supersession links; the prior version becomes immutable.", "State transitions follow only the declared permitted transitions and always record reason, actor and timestamp.", "Elements owned by referenced models, including claim status, decision outcome, hold determination and audit entries, are never written by this model." ], "delete": [ "Hard deletion is not performed by this model. A record leaving service is set to withdrawn or disposed and reduced to a tombstone stub retaining the record identifier, final state, disposition reason, disposition timestamp and successor link, so that citing contexts resolve rather than break.", "Excerpts, representation captures and any personal data inside them may be redacted or purged ahead of the record itself. Selectors, digests and identifiers survive redaction so the citation remains re-verifiable against the original source, and each redaction is marked with its basis.", "The retention class, the disposition schedule, the legal-hold determination and the authority to order erasure are owned by the adopting Dimension's records retention and disposition service. This model records only the class reference, the hold reference, the disposition state and the resulting stub, and executes disposition markers on that service's instruction.", "Where a takedown obliges removal of cited content, this model removes only its own copies and observations. Removal at the source is executed by the source's publisher, repository or archiving service and is never performed or claimed here." ] }, "roles": [ { "name": "Citation asserter", "responsibilities": [ "Create citation records with a resolving citing-context reference, a stance value and a locator", "Declare the assertion method and, for automated assertion, the tool and model version", "Capture the excerpt within licence and privacy limits, or record why it was suppressed" ] }, { "name": "Evidence verifier", "responsibilities": [ "Re-resolve locators, re-apply selectors and compare digests", "Confirm or reject the asserted stance and record a dated verification report", "Raise contested and drift flags without altering the citing context" ] }, { "name": "Vocabulary and alignment steward", "responsibilities": [ "Maintain the bound stance, evidence-type and certainty vocabularies and their versions", "Own the crosswalks to external vocabularies and record conflicts and round-trip losses", "Re-test conformance claims whenever a target vocabulary version changes" ] }, { "name": "Record owner", "responsibilities": [ "Accept accountability for the record, its review cadence and its disposition state", "Approve supersession and withdrawal", "Resolve disputes over stance through the declared escalation path" ] }, { "name": "Locator custodian", "responsibilities": [ "Schedule and interpret resolution health checks", "Register fallback locators and archived snapshot references", "Escalate link rot and content drift to the record owner" ] } ], "access": { "default_rule": "A citation record defaults to the more restrictive of the citing context's sensitivity and the cited source's disclosure terms. Identity, locator and stance metadata are readable at the citing context's scope, while excerpts and stored captures default to origin-only disclosure until a broader scope is explicitly granted by the adopting Dimension's policy service.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Embargoed source: locator and stance remain readable while the excerpt and captures stay withheld until the embargo timestamp lapses.", "Personal or special-category data in an excerpt: the excerpt is masked or withheld while selectors and digests remain readable so re-verification is still possible.", "Licence-restricted reproduction: excerpt text is suppressed on export outside the origin while the citation record itself is exported with a suppression marker.", "Legal hold: disposition actions are blocked even after the retention class has expired, on instruction from the owning retention service.", "Contested or integrity-failed records: readable with their flag visible; the flag may not be stripped on export." ], "audit_requirements": [ "Every state transition, supersession, verification and disposition action records the acting agent, reason code and an RFC 3339 timestamp on the record itself.", "Disclosure of an excerpt or capture outside its default scope is recorded as an event by the adopting Dimension's audit service; this model stores only a reference to that event and never the audit trail.", "Automated assertion and automated verification passes are attributable to a named tool and version so that a later reviewer can reproduce them.", "Alignment and conformance claims record who authored them, against which target version they were tested, and when they were last reviewed." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL", "Bound vocabularies with versions", "Delegation targets for party, retention, access and audit" ], "read_order": [ "AGENTS.md for the model name, type and the four mandatory URLs", "Specification URL for scope, boundaries, exclusions and the bundle, layer and finding structure", "Storage type URL for the projection in force and its canonicalization profile", "Interface URL for read, create, update and disposition operations and their preconditions", "Processes URL for the assertion, verification, supersession and disposition procedures", "Composition links to the citing-context, party, retention, access and audit services before any write is attempted" ] } }, "coverage": { "claim": "Within its 13 cited sources the draft covers the reified evidential citation: record identity and deduplication, stance and evidence typing, preferred-citation-identifier versus access-URI separation, in-resource anchoring and excerpt handling, consulted-representation state and drift detection, citation-act provenance and fixity, binding of an external certainty scheme, lifecycle and supersession, and declaration-level access, retention and exchange. Coverage is single-provider and uncorroborated. Aggregation, adjudication, bibliographic mastering and runtime enforcement are excluded by design; legal admissibility and sub-sentence multilingual alignment remain declared gaps. No claim of completeness for evidence semantics generally.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Reified citation record with its own identifier, master-system-first identity priority, deduplication key and equivalence to external citation identifiers. Grounded in the reified citation pattern in CiTO and the identified annotation in the Web Annotation model." }, { "dimension": "lifecycle", "status": "covered", "notes": "State enumeration, permitted transitions, immutability on assertion, versioning and supersession, and disposition states. Validity intervals follow the Verifiable Credentials pattern; the citing context's own lifecycle is explicitly excluded." }, { "dimension": "relationships", "status": "covered", "notes": "Citing-context binding with locus, directed stance link with optional inverse, supersession links, opposing-record references and alignment to a governed relation vocabulary." }, { "dimension": "temporal", "status": "covered", "notes": "Assertion, ingestion, access, archive, status-event, status-observation, assessment, verification and embargo times are modelled separately under a single RFC 3339 profile with an explicit seconds component and offset." }, { "dimension": "provenance", "status": "covered", "notes": "Asserting agent, accountable organisation, delegation chain and activity follow the PROV entity-activity-agent pattern; tool and model version are required for automated assertion." }, { "dimension": "ownership", "status": "covered", "notes": "Record owner, steward, accountable organisation and the mastering registry for bibliographic metadata are all named, with an explicit non-authority flag on the cached descriptor." }, { "dimension": "validation", "status": "covered", "notes": "Selector re-anchoring, digest recomputation, timestamp ordering checks, stance confirmation and profile conformance tests, with an explicit rule that unevidenced conformance is recorded only as alignment." }, { "dimension": "access", "status": "covered", "notes": "Sensitivity classes, component-level disclosure scopes, embargo and licence references are modelled as declarations. Evaluation, enforcement and the access log are referenced and explicitly disclaimed." }, { "dimension": "retention and deletion", "status": "covered", "notes": "No hard delete: withdrawal and disposition produce a resolvable tombstone stub; excerpts and captures may be redacted ahead of the record. Schedule ownership, hold determination and erasure execution belong to the adopting Dimension's records service." }, { "dimension": "interoperability", "status": "covered", "notes": "Term-level crosswalks with mapping strength and recorded loss, an exchange profile with obligations and extension rules, and explicit conversion of protocol-format timestamps at the boundary." }, { "dimension": "source locator durability", "status": "covered", "notes": "Preferred citation identifier separated from access URI, archived snapshot and time gate references, fallback locators, scheduled resolution checks and content drift detection." }, { "dimension": "evidence quality and certainty", "status": "covered", "notes": "An external certainty scheme is bound by version with per-domain limitation results; the scheme itself is never redefined, and no local scale is invented." }, { "dimension": "integrity and fixity", "status": "covered", "notes": "Canonicalization before digesting, digests over excerpt and representation, integrity-failed state, and references to signed media provenance manifests for media excerpts." }, { "dimension": "evidence aggregation and adjudication", "status": "not-applicable", "notes": "Weighing multiple evidence items into a verdict belongs to the claim and decision models. Only opposing-record references and a contested flag are held here, by design." }, { "dimension": "bibliometrics", "status": "not-applicable", "notes": "Citation counting, co-citation and impact analytics are downstream computations over these records rather than evidential context, and are excluded to keep the record semantically neutral." }, { "dimension": "legal admissibility and chain of custody", "status": "gap", "notes": "Jurisdiction-specific custody, sealing, disclosure and admissibility duties are not modelled. No cited authority in this source set governs them, so the structure would be unsupported." }, { "dimension": "multilingual handling", "status": "gap", "notes": "Language tagging and a translation flag are present, but transliteration schemes, script variants and sub-sentence alignment between an original and its translation are not modelled." } ], "known_omissions": [ "No model of citation counting or bibliometric aggregation; these are downstream analytics over citation records, not evidential context.", "No jurisdiction-specific chain-of-custody or admissibility model for legal or forensic evidence, which would impose custody, sealing and disclosure duties this model does not express.", "Multilingual coverage stops at language tagging and a transformation flag; transliteration, script variants and original-to-translation alignment below sentence level are absent.", "Citations to inherently non-retrievable sources such as personal communications, oral testimony and embargoed internal documents are supported only at whole-resource granularity with a descriptor and no persistent identifier.", "Rights and licensing of the cited source are referenced but not modelled; machine-enforceable reuse terms would require a separate rights model.", "Confidence values reported by automated extractors are stored as opaque numbers with a declared scale but no governed calibration methodology.", "No model of evidence sampling or corpus construction, so systematic selection bias across a set of citations cannot be detected from these records alone." ], "conflicts": [ "CiTO version is reported as 2.8.2 in the current SPAR documentation build while other SPAR pages and secondary indexes cite 2.8.1 dated 16 February 2018. Any binding must pin the version explicitly and re-check it before a conformance claim is restated.", "The Memento framework mandates RFC 1123 datetimes in its Accept-Datetime and Memento-Datetime headers, whereas this model requires RFC 3339 for stored values. Implementations must convert at the protocol boundary and store the RFC 3339 form, keeping the original header value only as provenance.", "The Web Annotation Data Model requires created and modified timestamps expressed in UTC with a trailing Z, while RFC 3339 permits non-zero offsets. Export to Web Annotation normalises to UTC and loses the original local offset unless it is retained in a separate element.", "CiTO citation intents and DataCite relationTypes overlap only partially: DataCite offers Cites, IsCitedBy and Reviews but no equivalent of refutes, disputes or qualifies, so challenge stances cannot round-trip through DataCite without loss.", "schema.org ClaimReview places the verdict rating on the review, while this model keeps the verdict with the citing claim model and carries only stance. A mapping must decide explicitly which side holds the rating, and the decision must be recorded in the crosswalk.", "ECO was developed for biological assertions and its assertion-method branch does not fully cover legal, journalistic or engineering evidence; local extension terms are required and must be declared as local rather than presented as ECO terms.", "GRADE certainty levels are defined for effect estimates in health evidence. Applying them to documentary, testimonial or engineering evidence is an extension beyond the handbook's stated scope and must be declared as such rather than claimed as GRADE conformance." ], "regional_assumptions": [ "Assumes no single jurisdiction's law of evidence applies. Where the adopting Dimension operates under a specific regime, such as a national records act or a regional data protection law, its retention, redaction and disclosure obligations override the defaults stated here.", "Assumes scholarly identifier infrastructure such as DOI, Handle and PMID is reachable. Where it is not, the governed-global-identifier tier of the identity priority collapses to Dimension-assigned identifiers and the locator becomes correspondingly weaker.", "Assumes that retaining an archived copy of the cited representation is lawful and permitted by licence. Some publishers and some jurisdictions restrict archival copies, which forces locator-only citations without a capture.", "Assumes excerpts are stored in the source's original language by default. Localised deployments must declare their own default language and translation policy.", "Assumes the adopting Dimension operates a party model, a retention service and an access policy service; where any is absent, the corresponding references become unresolvable and the model degrades to declarations without delegation targets." ], "adversarial_checks": [ "Boundary test against WM-KNW-007: no bundle, layer, finding or function stores claim text, claim decomposition, claim truth status or claim lifecycle. The model carries only a citing-context reference and locus, and the contested flag deliberately stops short of adjudication, which is stated as an explicit deferred judgement.", "Boundary test against WM-KNW-010: nothing here models options, criteria, deliberation or decision outcome. The decision model consumes citation records and retains its own rationale lifecycle; no function writes back into it.", "Runtime-ownership test: sensitivity classes, retention classes, legal holds and audit events appear only as references. No finding or function defines an evaluation engine, an enforcement point or an audit trail, and the delete rules name the adopting Dimension as the executor of erasure and hold determination.", "Counterexample test on non-retrievable sources: personal communications and oral testimony have no resolvable identifier, so identifier elements are optional, an explicit no-identifier exception question exists, and whole-resource anchor granularity is a first-class recorded outcome rather than a failure.", "Counterexample test on sources that change after citation: drift is detectable only if a digest and a capture existed at assertion time, so fixity and consulted-representation capture are modelled as first-class rather than optional convenience, and integrity failure is a retained state rather than a silent overwrite.", "Duplication test against bibliographic registries: source metadata appears only as an explicitly non-authoritative cache with a refresh timestamp and a named master, preventing this model from becoming a shadow bibliographic registry.", "Unsupported-structure test: a publisher or author trust-score layer was considered and rejected because no source in this set defines a governed trust vocabulary; certainty is bound to an external, version-pinned scheme instead, and no local scale was invented.", "Format-neutrality test: no finding names a serialization. Selectors, states, digests and profiles are described as semantics, with JSON, RDF, Markdown, Git, MCP and document stores treated as projections governed by the canonicalization rules." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "claude" ], "waivedProviders": [ "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-08-29T09:06:27Z", "scope": "Queued subject-model research from WM-XCT-013 onward", "active_providers": [ "claude" ], "waived_providers": [ { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-08-29T09:06:27Z", "reason": "The repository owner explicitly instructed the research queue to continue without Grok after repeated structured-output failures." } ], "review_rule": "Claude-only results require a separate no-tools adversarial audit and remain reviewable drafts with a visible single-provider hold." }, "boundaryDecision": { "entry_kind": "relationship", "status": "accepted", "rationale": "Two axes must be kept apart. The frozen registry value standalone-mm classifies the record plane (a world-model record carried standalone in the registry, per record_plane world-model) and is not a member of the subject-model enum, so it cannot be adopted here. On the subject-model axis the defining semantic is a directed, typed, attributable link from a citing context to a cited source that masters neither endpoint: both contract edges (WM-KNW-007 and WM-KNW-010) are inbound REFERENCE, contains_ids and composition_role are empty, and every boundary note reasserts non-ownership of both ends. 'relationship' is therefore the most defensible schema kind. 'aggregate' was considered because the record has independent identity, lifecycle, supersession and four identity-dependent serial artifacts keyed on the record identifier; that behaviour is a consequence of reification, not a change of kind, and 'entity' was rejected because the record has no meaning detached from its two endpoints." }, "decisions": [ { "concept": "Aggregate root identification: citation record as root of captures, check reports and verification reports", "disposition": "accepted", "rationale": "All four serial artifacts key on the citation record identifier plus a never-reused zero-padded ordinal, matching serial_naming_rule exactly; no member carries independent identity, so the root is unambiguous and no member can be orphaned or re-parented." }, { "concept": "Deduplication key composition versus the identity finding's distinguishability claim", "disposition": "accepted with binding condition", "rationale": "The create rule collapses a mint onto an existing record when a normalized key matches, but the key's composition is left entirely to open question q-cri-definition. Unless the key includes locus, stance and asserting agent, it contradicts the identity finding's own claim that a record is distinguishable from any other link between the same two endpoints." }, { "concept": "Evidence assessment record identity (record id + scheme id + scheme version, serial:false)", "disposition": "rejected as sufficient", "rationale": "q-cal-provenance requires recording assessor independence and q-saa-constraint requires a review cadence for high-consequence citations, so two independent assessments under one scheme version are expected; the declared key collides on them. A never-reused occurrence component is needed without promoting datetime or digest to the key." }, { "concept": "Vocabulary crosswalk identity keyed on the target vocabulary's own version string", "disposition": "deferred", "rationale": "SRC-009 records no ECO release version on the registry page and SRC-010 carries only 'Updated October 2013', so the declared key is unsatisfiable for two of the five registry_links vocabularies. A declared surrogate version token with its derivation rule is required before the identity strategy is published as normative." }, { "concept": "GRADE certainty binding applied at single-citation granularity", "disposition": "accepted with declared scope extension", "rationale": "GRADE rates certainty for a body of evidence per outcome, while this model excludes aggregation entirely; the conflicts list acknowledges the domain extension but not the unit-of-assessment mismatch. The binding must record the scheme's own unit of assessment alongside the version pin." }, { "concept": "Fixity values and selectors surviving redaction of personal-data excerpts", "disposition": "accepted for draft, held for privacy review", "rationale": "The delete rule states unconditionally that selectors and digests survive redaction so re-verification stays possible. Over a short special-category excerpt a retained digest remains a checkable value, and regional_assumptions only defer generically to overriding regimes rather than qualifying this specific rule." }, { "concept": "Access scope enumeration (bundle, layer, finding, artifact) versus record, excerpt and capture disclosure rules", "disposition": "reclassified as annotation-required", "rationale": "The enumerated scopes are documentation-structure levels while the default rule, exceptions and q-aac-access all govern instance components. Only 'artifact' maps cleanly to a capture; the mismatch must be annotated in the draft rather than published as a coherent scope vocabulary." }, { "concept": "Contested-flag procedure with a role responsibility and a question but no function", "disposition": "deferred", "rationale": "The Evidence verifier role must raise contested and drift flags and q-cce-process asks who runs the raise, review and clear procedure, yet none of the 11 functions covers it. Single-provider mode forbids adding a function, so this is recorded as an open structural gap rather than invented." }, { "concept": "Alignment authoring and conformance re-test with no covering function", "disposition": "deferred", "rationale": "The compatibility rule invalidates a conformance claim when a target version changes and the steward role must re-test it, but the function set only projects a record to an exchange profile. The maintenance path for the crosswalk artifact is therefore unexecutable as specified." }, { "concept": "Registry parent_ids WM-KNW-007 versus the REFERENCE-only relationship contract", "disposition": "accepted as navigational, not compositional", "rationale": "contains_ids, composition_role and default_link_type are empty and both contract edges point inward as REFERENCE. A compositional reading of parent_ids would contradict the model's independent identity, lifecycle and supersession, so it must be read as taxonomy placement under NAV.INF.KNW.EVD." }, { "concept": "Checklist rows 'access' and 'retention and deletion' marked covered", "disposition": "reclassified as covered-by-declaration", "rationale": "The model explicitly disclaims request evaluation, enforcement, the audit trail, schedule ownership, hold determination and erasure execution. An unqualified 'covered' overstates what the record supplies and invites an adopter to assume delegation targets exist." }, { "concept": "Cited-source arity of a single citation record", "disposition": "deferred", "rationale": "q-ccb-constraint governs whether one record may serve several citing contexts, but nothing constrains the cited-source side. With aggregation and argument schemes out of scope, one cited source per record should be stated explicitly rather than left inferable." }, { "concept": "SRC-012 schema.org ClaimReview as the sole tier-3 mapping target", "disposition": "accepted with pinned-version caveat", "rationale": "It carries a fast-moving version string (30.0, 19 March 2026) and drives the declared conflict over whether the verdict rating sits on the review or with the citing claim model; that crosswalk decision cannot be restated without re-verifying the pinned version." }, { "concept": "Rejection of a local publisher or author trust-score layer", "disposition": "accepted", "rationale": "The unsupported-structure adversarial check is sound: no source in the set defines a governed trust vocabulary, and binding certainty to an external version-pinned scheme instead of inventing a local scale is the correct discipline for a source-grounded model." } ], "publicationHolds": [ "Live source and version verification is outstanding for all 13 sources. SRC-003 (CiTO 2.8.2 versus the 2.8.1 dated 2018 cited elsewhere), SRC-009 (ECO, no release version recorded at all), SRC-010 (GRADE handbook, 'Updated October 2013' only), SRC-011 (C2PA 2.2), SRC-012 (schema.org 30.0) and SRC-008 (VC Data Model 2.0) must each be re-resolved and re-pinned before any alignment or conformance claim is restated in a published artifact.", "Independent second-provider review is absent by explicit owner authorization: Grok was waived by the repository owner at 2026-08-29T09:06:27Z after repeated structured-output failures. Every publication artifact must carry a visible single-provider hold, name the waived provider and the authorizing party, and the result remains a reviewable draft rather than an adjudicated model.", "Registry status candidate and review_state boundary-review-required must remain in force until the parent_ids link to WM-KNW-007 is confirmed as navigational placement rather than composition, since a compositional reading would invalidate the accepted relationship entry kind.", "The normalized deduplication key composition must be bound (locus, stance and asserting agent at minimum) before any implementation or interface guidance is published, because the create rule as written can silently merge legitimately distinct assertions.", "The evidence-assessment-record identity strategy must gain a never-reused occurrence component before the artifact identity rules are published as normative, otherwise an independent re-assessment under the same scheme version is unrepresentable.", "Independent second-provider review was explicitly waived by the repository owner; this Claude-only result remains a reviewable draft." ], "deferredResearch": [ "Pin a resolvable ECO release IRI or dated version for SRC-009 and record the derivation rule for the surrogate version token used in the crosswalk artifact key.", "Resolve the CiTO version discrepancy (2.8.2 in the current SPAR build versus 2.8.1 dated 16 February 2018 in secondary indexes) against the namespace itself and record which build the stance mapping was tested against.", "Verify whether any later IETF specification updates or profiles RFC 3339 in a way that affects the declared timestamp rule, particularly the -00:00 convention and the RFC 1123 conversion at the Memento protocol boundary.", "Define the normalized deduplication key and its interaction with q-cri-definition, then re-test it against the case of two opposing-stance records over the same citing context.", "Determine how the unconditional survival of excerpt digests through redaction interacts with erasure obligations over short special-category excerpts, and whether a salted or truncated fixity form preserves re-verifiability without preserving a checkable value.", "Assign ownership and a procedure for raising, reviewing and clearing the contested flag, and reconcile it with the Evidence verifier role responsibilities before any function is added in a future multi-provider pass.", "Specify the alignment authoring and conformance re-test path required by the compatibility rule and the Vocabulary and alignment steward role, which currently has no covering function.", "Identify an authoritative source for jurisdiction-neutral chain-of-custody and admissibility duties, or confirm the gap is unclosable from any defensible source set, before the legal-admissibility checklist row is revisited.", "Establish whether the schema.org ClaimReview verdict rating sits with the review or with the citing claim model, and record the decision explicitly in the crosswalk as the conflicts list requires." ] }, "statistics": { "sources": 13, "bundles": 6, "layers": 13, "findings": 24, "questions": 100, "artifacts": 7, "functions": 11 } }