# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-21T15:54:28Z", "synthesisSha256": "131ee914a13657b21051d1c008ac45c7b01c83df00e33f8ee005fb9fcc134b42", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-MEM-009", "registryId": "vr.wm-mem-009", "name": "Memory Conflict and Precedence Rule", "version": "0.1.0-reviewable-draft", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.MEM.PRE" ], "tags": [ "memory", "conflict", "precedence", "rule", "inf.mem.pre" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-mem-009-memory-conflict-and-precedence-rule/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-mem-009", "model": { "registry_id": "vr.wm-mem-009", "model_id": "WM-MEM-009", "name": "Memory Conflict and Precedence Rule", "entry_kind": "entity", "purpose": "Describe a governed, versioned rule for recognizing scoped memory disagreements and specifying which eligible assertions may be preferred or left unresolved.", "scope_statement": "One identifiable rule definition with revisions, applicability conditions, conflict input requirements, precedence criteria and outcome contracts. Conflict occurrences, decision runs and source memory items have separate identities. The structure is a proposed local profile derived from open specifications, not a standard-defined universal hierarchy or an executable resolver.", "in_scope": [ "Rule identity, scope, conflict classification and input-reference contracts", "Owner and authority qualification, ordered criteria, temporal applicability, ties and unresolved outcomes", "Rule revision, exception requirements, acceptance scenarios and external evaluation evidence references" ], "out_of_scope": [ "Memory item and store lifecycle, retrieval ranking, context assembly and consolidation execution", "Issuing sharing grants, calculating trust scores, incident handling, quarantine, redaction and deletion execution", "Runtime conflict detection, policy evaluation or enforcement, operational decision records and audit-trail implementation", "Determining objective truth, legal authority or a universal owner-over-time-over-authority ordering" ], "boundary_notes": [ { "neighbor": "WM-MEM-002 Memory Item", "distinction": "Registry parent is reconciled as a candidate reference, not inheritance: the rule describes permitted preference between externally mastered assertions and does not become their content or lifecycle.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-MEM-008 Memory Consolidation and WM-MEM-013 Context Assembly", "distinction": "These may consume a rule reference and an external resolution result. This definition does not merge items, select retrieved context or execute consolidation.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "WM-MEM-010 Memory Retention and Forgetting Policy and WM-MEM-011 Memory Scope and Sharing Grant", "distinction": "Local requirements reference retention and sharing policies. Preference cannot confer access or erase competing assertions; execution remains with their policy owners and storage systems.", "source_refs": [ "SRC-001", "SRC-004" ] }, { "neighbor": "WM-MEM-018 Memory Trust Assessment", "distinction": "A metric-qualified assessment is an optional input to an explicit rule. Its calculation, calibration and lifecycle remain external; a confidence score is not authority.", "source_refs": [ "SRC-007" ] }, { "neighbor": "Policy evaluator and decision or audit record", "distinction": "Only input/output contracts and evidence references are local. Operational detection, resolution, enforcement and audit trails remain separately mastered.", "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] } ] }, "sources": [ { "id": "SRC-001", "title": "PROV-O: The PROV Ontology", "organization": "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-10-21T15:52:23Z", "relevance": "Sections 3 and 4: entity provenance, attribution, derivation, revision and invalidation. These describe evidence links, not truth or permission to override a record." }, { "id": "SRC-002", "title": "OWL 2 Web Ontology Language Primer (Second Edition)", "organization": "W3C", "url": "https://www.w3.org/TR/owl2-primer/", "version_or_date": "Second Edition, 11 December 2012; introductory alignment", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:52:23Z", "relevance": "Introduction and open-world discussion distinguish missing assertions from false assertions and describe logical consistency. No universal memory conflict detector is specified." }, { "id": "SRC-003", "title": "Shapes Constraint Language (SHACL)", "organization": "W3C", "url": "https://www.w3.org/TR/shacl/", "version_or_date": "W3C Recommendation edition 2017; selected sections reviewed", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:52:23Z", "relevance": "Sections 2 and 3.6 separate shapes, constraints and validation reports. A violation against a selected shape is not proof of factual contradiction." }, { "id": "SRC-004", "title": "eXtensible Access Control Markup Language (XACML) Version 3.0", "organization": "OASIS", "url": "https://docs.oasis-open.org/xacml/3.0/xacml-3.0-core-spec-os-en.html", "version_or_date": "OASIS Standard, 22 January 2013", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:52:23Z", "relevance": "Appendix C and policy structure support explicit algorithm identity and distinct indeterminate and not-applicable outcomes. Access-control decisions are an analogy only; they are not memory truth values." }, { "id": "SRC-005", "title": "RFC 9110: HTTP Semantics", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc9110.html", "version_or_date": "RFC 9110, June 2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:52:23Z", "relevance": "Sections 8.8 and 13.1.1 describe validators and If-Match for lost-update avoidance. Optional HTTP binding example; transport concurrency does not resolve semantic disagreement." }, { "id": "SRC-006", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:52:23Z", "relevance": "Sections 4.3, 5.1 and 5.6 support offsets and timestamp representation. String ordering needs consistent representations; timestamp syntax does not establish causality." }, { "id": "SRC-007", "title": "Data on the Web Best Practices: Data Quality Vocabulary", "organization": "W3C", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "Working Group Note, 2016 edition; selected sections reviewed", "source_type": "ontology", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-21T15:52:23Z", "relevance": "Sections 3 and 4.1 describe metric-qualified quality measurements and their targets. This Note is not a Recommendation and supplies no universal reliability score or precedence rule." } ], "structure": { "bundles": [ { "id": "bundle-definition", "name": "Rule definition and scope", "description": "Separate reusable rule identity from its application and define comparable assertions.", "rationale": "Proposed grouping: Separate reusable rule identity from its application and define comparable assertions.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ], "layers": [ { "id": "layer-rule-identity", "name": "Rule identity and revision", "description": "Proposed profile requirement. Identify the reusable rule separately from its immutable revision and any application. A rule can exist without a conflict occurrence. Record its accountable steward by role.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "finding-rule-identity", "name": "Rule identity and revision", "description": "Proposed profile requirement. Identify the reusable rule separately from its immutable revision and any application. A rule can exist without a conflict occurrence. Record its accountable steward by role.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "rule-identity-q1", "text": "Which authoritative identifier names this rule independently of its revisions?", "kind": "identity", "answer_data": [ "rule-id" ] }, { "id": "rule-identity-q2", "text": "Which immutable revision and predecessor define the current rule content?", "kind": "lifecycle", "answer_data": [ "revision-id", "predecessor-ref" ] }, { "id": "rule-identity-q3", "text": "Which role stewards the rule and which authority reference permits its maintenance?", "kind": "ownership", "answer_data": [ "steward-role", "maintenance-authority-ref" ] }, { "id": "rule-identity-q4", "text": "Which consumer profiles may reference this revision without owning it?", "kind": "relationship", "answer_data": [ "consumer-profile-refs" ] } ], "data_elements": [ { "id": "rule-identity-data-rule-id", "name": "rule-id", "description": "Candidate rule-id in the rule identity and revision contract; adopt a typed instance schema before execution.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "rule-identity-data-revision-id", "name": "revision-id", "description": "Candidate revision-id in the rule identity and revision contract; adopt a typed instance schema before execution.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "rule-identity-data-predecessor-ref", "name": "predecessor-ref", "description": "Candidate predecessor-ref in the rule identity and revision contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "rule-identity-data-steward-role", "name": "steward-role", "description": "Candidate steward-role in the rule identity and revision contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "rule-identity-data-maintenance-authority-ref", "name": "maintenance-authority-ref", "description": "Candidate maintenance-authority-ref in the rule identity and revision contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "rule-identity-data-consumer-profile-refs", "name": "consumer-profile-refs", "description": "Candidate consumer-profile-refs in the rule identity and revision contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "rule-identity-artifact", "name": "Rule identity and revision declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-comparison-scope", "name": "Comparable assertion scope", "description": "Proposed profile requirement. Define comparability before declaring a conflict: referent, property, perspective, purpose, tenant, temporal interval and value interpretation matter. Distinct values may coexist when the profile permits multiplicity. Missing scope information produces an unresolved classification.", "source_refs": [ "SRC-002", "SRC-003" ], "findings": [ { "id": "finding-comparison-scope", "name": "Comparable assertion scope", "description": "Proposed profile requirement. Define comparability before declaring a conflict: referent, property, perspective, purpose, tenant, temporal interval and value interpretation matter. Distinct values may coexist when the profile permits multiplicity. Missing scope information produces an unresolved classification.", "source_refs": [ "SRC-002", "SRC-003" ], "questions": [ { "id": "comparison-scope-q1", "text": "What subject, property and assertion granularity form the comparison key?", "kind": "definition", "answer_data": [ "comparison-key" ] }, { "id": "comparison-scope-q2", "text": "Which scope dimensions must match before two assertions are comparable?", "kind": "constraint", "answer_data": [ "scope-dimensions" ] }, { "id": "comparison-scope-q3", "text": "Which multiplicity, unit and normalization rules distinguish an allowed variation from a conflict?", "kind": "classification", "answer_data": [ "value-profile-ref", "normalization-policy-ref" ] }, { "id": "comparison-scope-q4", "text": "How is an unknown referent or incomplete comparison scope reported?", "kind": "exception", "answer_data": [ "incomplete-scope-outcome" ] } ], "data_elements": [ { "id": "comparison-scope-data-comparison-key", "name": "comparison-key", "description": "Candidate comparison-key in the comparable assertion scope contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "comparison-scope-data-scope-dimensions", "name": "scope-dimensions", "description": "Candidate scope-dimensions in the comparable assertion scope contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "comparison-scope-data-value-profile-ref", "name": "value-profile-ref", "description": "Candidate value-profile-ref in the comparable assertion scope contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "comparison-scope-data-normalization-policy-ref", "name": "normalization-policy-ref", "description": "Candidate normalization-policy-ref in the comparable assertion scope contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "id": "comparison-scope-data-incomplete-scope-outcome", "name": "incomplete-scope-outcome", "description": "Candidate incomplete-scope-outcome in the comparable assertion scope contract; adopt a typed instance schema before execution.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "comparison-scope-artifact", "name": "Comparable assertion scope declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-conflict-inputs", "name": "Conflict and evidence input contracts", "description": "Qualify conflict kinds and evidence before any priority decision.", "rationale": "Proposed grouping: Qualify conflict kinds and evidence before any priority decision.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-conflict-kinds", "name": "Conflict kinds and detection contract", "description": "Proposed profile requirement. Distinguish explicit contradiction, profile constraint violation, incompatible policy rules and concurrent revision conflict. A proposed classification refers to a declared comparator and external evidence; a missing assertion alone is not negation. This finding defines inputs, not a detection engine.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "findings": [ { "id": "finding-conflict-kinds", "name": "Conflict kinds and detection contract", "description": "Proposed profile requirement. Distinguish explicit contradiction, profile constraint violation, incompatible policy rules and concurrent revision conflict. A proposed classification refers to a declared comparator and external evidence; a missing assertion alone is not negation. This finding defines inputs, not a detection engine.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ], "questions": [ { "id": "conflict-kinds-q1", "text": "Which conflict kinds does this rule accept and which require another profile?", "kind": "classification", "answer_data": [ "accepted-conflict-kinds", "excluded-conflict-kinds" ] }, { "id": "conflict-kinds-q2", "text": "Which comparator version and evidence must an external detector supply?", "kind": "requirement", "answer_data": [ "comparator-ref", "detector-evidence-requirements" ] }, { "id": "conflict-kinds-q3", "text": "How does the contract separate missing information from explicit negation or invalid data?", "kind": "validation", "answer_data": [ "unknown-handling" ] }, { "id": "conflict-kinds-q4", "text": "Which external conflict occurrence identifies all participating item revisions?", "kind": "relationship", "answer_data": [ "occurrence-reference-contract" ] } ], "data_elements": [ { "id": "conflict-kinds-data-accepted-conflict-kinds", "name": "accepted-conflict-kinds", "description": "Candidate accepted-conflict-kinds in the conflict kinds and detection contract contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "conflict-kinds-data-excluded-conflict-kinds", "name": "excluded-conflict-kinds", "description": "Candidate excluded-conflict-kinds in the conflict kinds and detection contract contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "conflict-kinds-data-comparator-ref", "name": "comparator-ref", "description": "Candidate comparator-ref in the conflict kinds and detection contract contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "conflict-kinds-data-detector-evidence-requirements", "name": "detector-evidence-requirements", "description": "Candidate detector-evidence-requirements in the conflict kinds and detection contract contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "conflict-kinds-data-unknown-handling", "name": "unknown-handling", "description": "Candidate unknown-handling in the conflict kinds and detection contract contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] }, { "id": "conflict-kinds-data-occurrence-reference-contract", "name": "occurrence-reference-contract", "description": "Candidate occurrence-reference-contract in the conflict kinds and detection contract contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "conflict-kinds-artifact", "name": "Conflict kinds and detection contract declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-002", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-evidence-lineage", "name": "Evidence and derivation input requirements", "description": "Proposed profile requirement. Keep source assertion, derived summary, assessment and cited evidence distinct. Attribution identifies an origin but does not prove authority. Repetition through derived copies must not silently count as independent corroboration. Detailed provenance remains external.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-evidence-lineage", "name": "Evidence and derivation input requirements", "description": "Proposed profile requirement. Keep source assertion, derived summary, assessment and cited evidence distinct. Attribution identifies an origin but does not prove authority. Repetition through derived copies must not silently count as independent corroboration. Detailed provenance remains external.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "evidence-lineage-q1", "text": "Which item revision, origin and derivation references must accompany each competing assertion?", "kind": "provenance", "answer_data": [ "lineage-reference-requirements" ] }, { "id": "evidence-lineage-q2", "text": "What evidence locator and integrity information bind an assertion to its cited support?", "kind": "evidence", "answer_data": [ "evidence-binding-requirements" ] }, { "id": "evidence-lineage-q3", "text": "Which metric, target, method version and observation time qualify an optional assessment?", "kind": "quality", "answer_data": [ "quality-input-contract" ] }, { "id": "evidence-lineage-q4", "text": "How must shared ancestry or unavailable evidence affect eligibility without inventing a trust score?", "kind": "constraint", "answer_data": [ "lineage-eligibility-policy" ] } ], "data_elements": [ { "id": "evidence-lineage-data-lineage-reference-requirements", "name": "lineage-reference-requirements", "description": "Candidate lineage-reference-requirements in the evidence and derivation input requirements contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "evidence-lineage-data-evidence-binding-requirements", "name": "evidence-binding-requirements", "description": "Candidate evidence-binding-requirements in the evidence and derivation input requirements contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "evidence-lineage-data-quality-input-contract", "name": "quality-input-contract", "description": "Candidate quality-input-contract in the evidence and derivation input requirements contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "evidence-lineage-data-lineage-eligibility-policy", "name": "lineage-eligibility-policy", "description": "Candidate lineage-eligibility-policy in the evidence and derivation input requirements contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "evidence-lineage-artifact", "name": "Evidence and derivation input requirements declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-precedence", "name": "Eligibility and precedence", "description": "Separate permission and authority from the chosen ordering of eligible assertions.", "rationale": "Proposed grouping: Separate permission and authority from the chosen ordering of eligible assertions.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "layers": [ { "id": "layer-authority-eligibility", "name": "Owner and authority eligibility", "description": "Proposed profile requirement. Before ranking, require scope-qualified authority and permission evidence from external masters. Ownership, authorship and delegation are different claims. Imported memory text cannot grant itself priority or permission. Eligibility and the final factual assessment remain distinct.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "finding-authority-eligibility", "name": "Owner and authority eligibility", "description": "Proposed profile requirement. Before ranking, require scope-qualified authority and permission evidence from external masters. Ownership, authorship and delegation are different claims. Imported memory text cannot grant itself priority or permission. Eligibility and the final factual assessment remain distinct.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "authority-eligibility-q1", "text": "Which authority classes and scope-qualified delegation references may establish eligibility?", "kind": "authority", "answer_data": [ "authority-profile-ref", "delegation-input-contract" ] }, { "id": "authority-eligibility-q2", "text": "How are owner identity, author attribution and subject identity distinguished for this rule?", "kind": "ownership", "answer_data": [ "owner-author-subject-mapping" ] }, { "id": "authority-eligibility-q3", "text": "Which external sharing decision is required before comparing protected assertions?", "kind": "access", "answer_data": [ "sharing-check-ref" ] }, { "id": "authority-eligibility-q4", "text": "What is the declared outcome for self-asserted priority, revoked authority or an unverifiable grant?", "kind": "security", "answer_data": [ "invalid-authority-outcome" ] } ], "data_elements": [ { "id": "authority-eligibility-data-authority-profile-ref", "name": "authority-profile-ref", "description": "Candidate authority-profile-ref in the owner and authority eligibility contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "authority-eligibility-data-delegation-input-contract", "name": "delegation-input-contract", "description": "Candidate delegation-input-contract in the owner and authority eligibility contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "authority-eligibility-data-owner-author-subject-mapping", "name": "owner-author-subject-mapping", "description": "Candidate owner-author-subject-mapping in the owner and authority eligibility contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "authority-eligibility-data-sharing-check-ref", "name": "sharing-check-ref", "description": "Candidate sharing-check-ref in the owner and authority eligibility contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "authority-eligibility-data-invalid-authority-outcome", "name": "invalid-authority-outcome", "description": "Candidate invalid-authority-outcome in the owner and authority eligibility contract; adopt a typed instance schema before execution.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "authority-eligibility-artifact", "name": "Owner and authority eligibility declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-precedence-order", "name": "Precedence criteria and tie policy", "description": "Proposed profile requirement. Declare a versioned comparator with named eligibility gates, ordered criteria or an explicitly partial ordering. An adoption profile chooses how authority, owner correction, time and quality interact; this model prescribes no universal order. Cycles, equally ranked alternatives and incomparable metrics must have explicit unresolved outcomes.", "source_refs": [ "SRC-004", "SRC-007" ], "findings": [ { "id": "finding-precedence-order", "name": "Precedence criteria and tie policy", "description": "Proposed profile requirement. Declare a versioned comparator with named eligibility gates, ordered criteria or an explicitly partial ordering. An adoption profile chooses how authority, owner correction, time and quality interact; this model prescribes no universal order. Cycles, equally ranked alternatives and incomparable metrics must have explicit unresolved outcomes.", "source_refs": [ "SRC-004", "SRC-007" ], "questions": [ { "id": "precedence-order-q1", "text": "Which ordered or partially ordered criteria determine preference among eligible assertions?", "kind": "decision", "answer_data": [ "criteria-specification" ] }, { "id": "precedence-order-q2", "text": "Which comparator identifier and version fix the meaning of the precedence rule?", "kind": "requirement", "answer_data": [ "precedence-comparator-ref" ] }, { "id": "precedence-order-q3", "text": "What outcome applies to a tie, cycle or incomparable pair of eligible assertions?", "kind": "exception", "answer_data": [ "tie-cycle-policy" ] }, { "id": "precedence-order-q4", "text": "Which comparable metric definitions and thresholds are required if quality participates in precedence?", "kind": "measurement", "answer_data": [ "metric-binding-contract" ] } ], "data_elements": [ { "id": "precedence-order-data-criteria-specification", "name": "criteria-specification", "description": "Candidate criteria-specification in the precedence criteria and tie policy contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "precedence-order-data-precedence-comparator-ref", "name": "precedence-comparator-ref", "description": "Candidate precedence-comparator-ref in the precedence criteria and tie policy contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "precedence-order-data-tie-cycle-policy", "name": "tie-cycle-policy", "description": "Candidate tie-cycle-policy in the precedence criteria and tie policy contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "precedence-order-data-metric-binding-contract", "name": "metric-binding-contract", "description": "Candidate metric-binding-contract in the precedence criteria and tie policy contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "precedence-order-artifact", "name": "Precedence criteria and tie policy declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-time-concurrency", "name": "Time and concurrency", "description": "Prevent recency, arrival order and concurrent mutation from silently changing semantics.", "rationale": "Proposed grouping: Prevent recency, arrival order and concurrent mutation from silently changing semantics.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006" ], "layers": [ { "id": "layer-temporal-applicability", "name": "Temporal applicability and recency", "description": "Proposed profile requirement. Specify the time basis for any recency criterion and for rule activation. Event or effective time differs from observation and ingestion time. Timestamp representation neither proves causal order nor makes later arrivals more authoritative. Preserve imprecision and unknown intervals without fabricating seconds.", "source_refs": [ "SRC-001", "SRC-006" ], "findings": [ { "id": "finding-temporal-applicability", "name": "Temporal applicability and recency", "description": "Proposed profile requirement. Specify the time basis for any recency criterion and for rule activation. Event or effective time differs from observation and ingestion time. Timestamp representation neither proves causal order nor makes later arrivals more authoritative. Preserve imprecision and unknown intervals without fabricating seconds.", "source_refs": [ "SRC-001", "SRC-006" ], "questions": [ { "id": "temporal-applicability-q1", "text": "Which effective interval determines whether a rule revision applies to a comparison?", "kind": "temporal", "answer_data": [ "rule-effective-interval" ] }, { "id": "temporal-applicability-q2", "text": "Which event, observation or ingestion time is the declared recency basis and why?", "kind": "temporal", "answer_data": [ "recency-time-basis" ] }, { "id": "temporal-applicability-q3", "text": "How are clock uncertainty, equal instants, missing offsets and partial dates handled?", "kind": "quality", "answer_data": [ "temporal-uncertainty-policy" ] }, { "id": "temporal-applicability-q4", "text": "How do late arrivals or nonoverlapping assertion validity intervals change comparability?", "kind": "constraint", "answer_data": [ "interval-and-late-arrival-policy" ] } ], "data_elements": [ { "id": "temporal-applicability-data-rule-effective-interval", "name": "rule-effective-interval", "description": "Candidate rule-effective-interval in the temporal applicability and recency contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "temporal-applicability-data-recency-time-basis", "name": "recency-time-basis", "description": "Candidate recency-time-basis in the temporal applicability and recency contract; adopt a typed instance schema before execution.", "value_kind": "code", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "temporal-applicability-data-temporal-uncertainty-policy", "name": "temporal-uncertainty-policy", "description": "Candidate temporal-uncertainty-policy in the temporal applicability and recency contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] }, { "id": "temporal-applicability-data-interval-and-late-arrival-policy", "name": "interval-and-late-arrival-policy", "description": "Candidate interval-and-late-arrival-policy in the temporal applicability and recency contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-006" ] } ], "artifacts": [ { "id": "temporal-applicability-artifact", "name": "Temporal applicability and recency declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-001", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-snapshot-concurrency", "name": "Snapshot and concurrent change contract", "description": "Proposed profile requirement. Bind external resolution evidence to a fixed rule revision and input revisions. A storage adapter may use conditional updates, but successful concurrency control does not establish semantic truth. Changed inputs, authority or policy require a new evaluation under the adopted freshness contract.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "finding-snapshot-concurrency", "name": "Snapshot and concurrent change contract", "description": "Proposed profile requirement. Bind external resolution evidence to a fixed rule revision and input revisions. A storage adapter may use conditional updates, but successful concurrency control does not establish semantic truth. Changed inputs, authority or policy require a new evaluation under the adopted freshness contract.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "snapshot-concurrency-q1", "text": "Which rule and input revision identifiers define the snapshot used by a resolver?", "kind": "identity", "answer_data": [ "snapshot-contract" ] }, { "id": "snapshot-concurrency-q2", "text": "What expected revision condition must a consumer check before applying a result?", "kind": "constraint", "answer_data": [ "expected-revision-condition" ] }, { "id": "snapshot-concurrency-q3", "text": "What response is required if an input, grant or rule changes after evaluation?", "kind": "exception", "answer_data": [ "stale-result-policy" ] }, { "id": "snapshot-concurrency-q4", "text": "How does a binding preserve revision checks without assuming HTTP or a particular store?", "kind": "interoperability", "answer_data": [ "concurrency-binding-ref" ] } ], "data_elements": [ { "id": "snapshot-concurrency-data-snapshot-contract", "name": "snapshot-contract", "description": "Candidate snapshot-contract in the snapshot and concurrent change contract contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "snapshot-concurrency-data-expected-revision-condition", "name": "expected-revision-condition", "description": "Candidate expected-revision-condition in the snapshot and concurrent change contract contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "snapshot-concurrency-data-stale-result-policy", "name": "stale-result-policy", "description": "Candidate stale-result-policy in the snapshot and concurrent change contract contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "snapshot-concurrency-data-concurrency-binding-ref", "name": "concurrency-binding-ref", "description": "Candidate concurrency-binding-ref in the snapshot and concurrent change contract contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "snapshot-concurrency-artifact", "name": "Snapshot and concurrent change contract declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-outcomes", "name": "Outcomes and review", "description": "Specify unresolved outcomes and bounded review without claiming truth or executing actions.", "rationale": "Proposed grouping: Specify unresolved outcomes and bounded review without claiming truth or executing actions.", "source_refs": [ "SRC-001", "SRC-004" ], "layers": [ { "id": "layer-resolution-outcomes", "name": "Resolution outcome contract", "description": "Proposed profile requirement. Specify proposed outcomes such as preferred assertion, coexistence, unresolved tie, inapplicable and indeterminate. A preference is a scoped decision, not proof that alternatives are false. A merge proposal creates no memory item here. Outcomes reference all considered inputs and the external decision record without copying its lifecycle.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "finding-resolution-outcomes", "name": "Resolution outcome contract", "description": "Proposed profile requirement. Specify proposed outcomes such as preferred assertion, coexistence, unresolved tie, inapplicable and indeterminate. A preference is a scoped decision, not proof that alternatives are false. A merge proposal creates no memory item here. Outcomes reference all considered inputs and the external decision record without copying its lifecycle.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "resolution-outcomes-q1", "text": "Which outcome codes preserve preference, coexistence, inapplicability and indeterminate evaluation separately?", "kind": "state", "answer_data": [ "outcome-vocabulary" ] }, { "id": "resolution-outcomes-q2", "text": "Which rationale, criterion trace and decision reference must accompany an external result?", "kind": "evidence", "answer_data": [ "result-evidence-contract" ] }, { "id": "resolution-outcomes-q3", "text": "What must a consumer preserve about nonpreferred assertions and partial field-level decisions?", "kind": "constraint", "answer_data": [ "alternative-preservation-rule" ] }, { "id": "resolution-outcomes-q4", "text": "Which consumer action classes are permitted for each outcome without granting new authority?", "kind": "process", "answer_data": [ "consumer-action-contract" ] } ], "data_elements": [ { "id": "resolution-outcomes-data-outcome-vocabulary", "name": "outcome-vocabulary", "description": "Candidate outcome-vocabulary in the resolution outcome contract contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "resolution-outcomes-data-result-evidence-contract", "name": "result-evidence-contract", "description": "Candidate result-evidence-contract in the resolution outcome contract contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "resolution-outcomes-data-alternative-preservation-rule", "name": "alternative-preservation-rule", "description": "Candidate alternative-preservation-rule in the resolution outcome contract contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "resolution-outcomes-data-consumer-action-contract", "name": "consumer-action-contract", "description": "Candidate consumer-action-contract in the resolution outcome contract contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "resolution-outcomes-artifact", "name": "Resolution outcome contract declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-exceptions-review", "name": "Exception and review requirements", "description": "Proposed profile requirement. An exception is a separately authorized, scoped reference with expiry and reasons. It must not weaken access or other mandatory restrictions through precedence. Unresolved high-impact comparisons may require human review under the adopting policy. This rule records requirements and references, not adjudication or external actions.", "source_refs": [ "SRC-001", "SRC-004" ], "findings": [ { "id": "finding-exceptions-review", "name": "Exception and review requirements", "description": "Proposed profile requirement. An exception is a separately authorized, scoped reference with expiry and reasons. It must not weaken access or other mandatory restrictions through precedence. Unresolved high-impact comparisons may require human review under the adopting policy. This rule records requirements and references, not adjudication or external actions.", "source_refs": [ "SRC-001", "SRC-004" ], "questions": [ { "id": "exceptions-review-q1", "text": "Which conditions require abstention or review rather than automatic preference?", "kind": "exception", "answer_data": [ "review-trigger-policy" ] }, { "id": "exceptions-review-q2", "text": "Which role and external authorization reference can approve a scoped exception?", "kind": "authority", "answer_data": [ "exception-authority-contract" ] }, { "id": "exceptions-review-q3", "text": "What scope, expiry and revocation checks bound an exception?", "kind": "temporal", "answer_data": [ "exception-validity-contract" ] }, { "id": "exceptions-review-q4", "text": "Which external review record and follow-up rule revision preserve a disputed outcome?", "kind": "relationship", "answer_data": [ "review-record-contract" ] } ], "data_elements": [ { "id": "exceptions-review-data-review-trigger-policy", "name": "review-trigger-policy", "description": "Candidate review-trigger-policy in the exception and review requirements contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "exceptions-review-data-exception-authority-contract", "name": "exception-authority-contract", "description": "Candidate exception-authority-contract in the exception and review requirements contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "exceptions-review-data-exception-validity-contract", "name": "exception-validity-contract", "description": "Candidate exception-validity-contract in the exception and review requirements contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] }, { "id": "exceptions-review-data-review-record-contract", "name": "review-record-contract", "description": "Candidate review-record-contract in the exception and review requirements contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004" ] } ], "artifacts": [ { "id": "exceptions-review-artifact", "name": "Exception and review requirements declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-001", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Assurance and rule governance", "description": "Make adoption tests, mapping limitations and lifecycle responsibilities explicit.", "rationale": "Proposed grouping: Make adoption tests, mapping limitations and lifecycle responsibilities explicit.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-acceptance-mapping", "name": "Acceptance scenarios and interoperable mappings", "description": "Proposed profile requirement. Pin synthetic scenarios, expected outcomes and external validation reports to a rule revision. Test boundary cases and lossy bindings; a schema-valid research package alone proves no executable conformance. Conceptual mappings to open specifications remain qualified by their domain and status.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-acceptance-mapping", "name": "Acceptance scenarios and interoperable mappings", "description": "Proposed profile requirement. Pin synthetic scenarios, expected outcomes and external validation reports to a rule revision. Test boundary cases and lossy bindings; a schema-valid research package alone proves no executable conformance. Conceptual mappings to open specifications remain qualified by their domain and status.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ], "questions": [ { "id": "acceptance-mapping-q1", "text": "Which synthetic cases test missing values, ties, cycles, authority changes and late arrivals?", "kind": "validation", "answer_data": [ "acceptance-case-refs" ] }, { "id": "acceptance-mapping-q2", "text": "Which expected outcomes and external evaluator version make a report reproducible?", "kind": "validation", "answer_data": [ "expected-outcome-contract", "validation-report-refs" ] }, { "id": "acceptance-mapping-q3", "text": "Which mapping preserves each criterion, unknown value and outcome across bindings?", "kind": "interoperability", "answer_data": [ "mapping-profile-refs" ] }, { "id": "acceptance-mapping-q4", "text": "Which unsupported or lossy mappings block deployment or require explicit profile review?", "kind": "quality", "answer_data": [ "mapping-loss-policy" ] } ], "data_elements": [ { "id": "acceptance-mapping-data-acceptance-case-refs", "name": "acceptance-case-refs", "description": "Candidate acceptance-case-refs in the acceptance scenarios and interoperable mappings contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "acceptance-mapping-data-expected-outcome-contract", "name": "expected-outcome-contract", "description": "Candidate expected-outcome-contract in the acceptance scenarios and interoperable mappings contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "acceptance-mapping-data-validation-report-refs", "name": "validation-report-refs", "description": "Candidate validation-report-refs in the acceptance scenarios and interoperable mappings contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "acceptance-mapping-data-mapping-profile-refs", "name": "mapping-profile-refs", "description": "Candidate mapping-profile-refs in the acceptance scenarios and interoperable mappings contract; adopt a typed instance schema before execution.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] }, { "id": "acceptance-mapping-data-mapping-loss-policy", "name": "mapping-loss-policy", "description": "Candidate mapping-loss-policy in the acceptance scenarios and interoperable mappings contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "acceptance-mapping-artifact", "name": "Acceptance scenarios and interoperable mappings declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-rule-governance", "name": "Rule change, retention and privacy", "description": "Proposed profile requirement. Govern this rule definition and its local artifacts independently of source memory. Material changes create a revision and preserve authorized provenance links. Retention is bounded by adopting policies; supersession does not require indefinite payload storage. A tombstone or opaque reference may replace inaccessible evidence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "findings": [ { "id": "finding-rule-governance", "name": "Rule change, retention and privacy", "description": "Proposed profile requirement. Govern this rule definition and its local artifacts independently of source memory. Material changes create a revision and preserve authorized provenance links. Retention is bounded by adopting policies; supersession does not require indefinite payload storage. A tombstone or opaque reference may replace inaccessible evidence.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "questions": [ { "id": "rule-governance-q1", "text": "Which approval and compatibility checks move a rule revision from draft to active or retired?", "kind": "lifecycle", "answer_data": [ "rule-transition-policy" ] }, { "id": "rule-governance-q2", "text": "Which retention policy and disposition trigger govern this rule and its local artifacts?", "kind": "retention", "answer_data": [ "retention-policy-ref", "disposition-trigger" ] }, { "id": "rule-governance-q3", "text": "What minimization and redaction rules prevent rationale or test data from revealing protected assertions?", "kind": "privacy", "answer_data": [ "minimization-policy" ] }, { "id": "rule-governance-q4", "text": "Which roles can read, propose, approve or retire a rule revision and inspect exception metadata?", "kind": "access", "answer_data": [ "role-access-profile" ] } ], "data_elements": [ { "id": "rule-governance-data-rule-transition-policy", "name": "rule-transition-policy", "description": "Candidate rule-transition-policy in the rule change, retention and privacy contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "rule-governance-data-retention-policy-ref", "name": "retention-policy-ref", "description": "Candidate retention-policy-ref in the rule change, retention and privacy contract; adopt a typed instance schema before execution.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "rule-governance-data-disposition-trigger", "name": "disposition-trigger", "description": "Candidate disposition-trigger in the rule change, retention and privacy contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "rule-governance-data-minimization-policy", "name": "minimization-policy", "description": "Candidate minimization-policy in the rule change, retention and privacy contract; adopt a typed instance schema before execution.", "value_kind": "text", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "rule-governance-data-role-access-profile", "name": "role-access-profile", "description": "Candidate role-access-profile in the rule change, retention and privacy contract; adopt a typed instance schema before execution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "rule-governance-artifact", "name": "Rule change, retention and privacy declaration", "description": "Versioned rule attachment containing this finding's declarations and external references; it is not an operational decision or a duplicate memory payload.", "media_or_form": [ "Structured declaration", "Human-readable projection" ], "serial": true, "identity_strategy": "Authoritative rule master identifier plus governed attachment identifier and separate revision; otherwise governed IRI, then Dimension-assigned UUID or ULID. A date is not an identifier.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-define-rule", "name": "Draft rule definition", "description": "Create a local rule identity and scope declaration.", "inputs": [ "Owner package reference", "Comparison profile" ], "outputs": [ "Draft rule revision" ], "preconditions": [ "Steward authority established" ], "effects": [ "Create local definition only; no memory write or activation" ], "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "function-bind-input-contract", "name": "Bind conflict input contract", "description": "Record required conflict, lineage and quality references.", "inputs": [ "Draft revision", "Comparator reference", "Input requirements" ], "outputs": [ "Versioned input contract" ], "preconditions": [ "Referenced masters and field meanings are identified" ], "effects": [ "Change local requirements; no runtime detection or trust assessment" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "function-declare-precedence", "name": "Declare precedence and outcomes", "description": "Record criteria, authority gates, unresolved outcomes and exception requirements.", "inputs": [ "Input contract", "Authority profile", "Ordered criteria", "Tie policy" ], "outputs": [ "Proposed precedence declaration" ], "preconditions": [ "Every criterion and unknown outcome is explicit" ], "effects": [ "Store proposed rule semantics only; do not resolve operational conflicts" ], "source_refs": [ "SRC-004", "SRC-007" ] }, { "id": "function-attach-assurance", "name": "Attach acceptance evidence", "description": "Link synthetic scenarios, expected outcomes, mappings and external validation reports.", "inputs": [ "Rule revision", "Scenario references", "Report references" ], "outputs": [ "Acceptance evidence manifest" ], "preconditions": [ "Evidence permissions and revision bindings checked" ], "effects": [ "Record validation evidence without claiming executable conformance" ], "source_refs": [ "SRC-003", "SRC-005", "SRC-006" ] }, { "id": "function-revise-rule", "name": "Propose successor revision", "description": "Record changed conditions and authorized approval references against an expected predecessor.", "inputs": [ "Expected revision", "Change rationale", "Approval reference" ], "outputs": [ "Successor draft", "Compatibility assessment reference" ], "preconditions": [ "Expected revision is current and changes are within authority" ], "effects": [ "Preserve predecessor link; activation remains subject to external policy" ], "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "function-retire-rule", "name": "Record rule retirement", "description": "Mark this definition retired with replacement and retention references.", "inputs": [ "Rule revision", "Retirement authority", "Retention reference" ], "outputs": [ "Retirement metadata", "Optional successor reference" ], "preconditions": [ "Authority and disposition policy verified" ], "effects": [ "Retire the local rule record only; storage owner executes any authorized disposition" ], "source_refs": [ "SRC-001", "SRC-004" ] } ], "composition": [ { "target": "WM-MEM-002", "relation": "REFERENCE", "purpose": "Candidate parent reconciliation: reference memory item identities and revisions through the input contract; no inherited item lifecycle.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-MEM-008", "relation": "REFERENCE", "purpose": "Optional consolidation consumer binding; the target owns consolidation execution and resulting memory.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-MEM-010", "relation": "REFERENCE", "purpose": "Optional retention policy binding for local artifacts and separate source records; target policy and storage owner govern disposition.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-MEM-011", "relation": "REFERENCE", "purpose": "Optional sharing-grant model binding; access evidence is required by an adopted profile but this exact sibling implementation is not mandatory.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "WM-MEM-013", "relation": "REFERENCE", "purpose": "Optional context-assembly consumer binding; context selection remains outside this rule.", "required": false, "source_refs": [ "SRC-001", "SRC-004" ] }, { "target": "WM-MEM-018", "relation": "REFERENCE", "purpose": "Optional qualified trust assessment input; scoring and calibration are external.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "W3C PROV-O", "relation": "ALIGN", "purpose": "Conceptual provenance and revision mapping only; does not prove truth or grant authority.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "OASIS XACML 3.0", "relation": "ALIGN", "purpose": "Analogy for explicit combining identity and unknown outcomes; no direct equivalence between Permit/Deny and memory truth and no conformance claim.", "required": false, "source_refs": [ "SRC-004" ] }, { "target": "W3C SHACL", "relation": "ALIGN", "purpose": "Optional validation report mapping; shape conformance and factual correctness remain distinct.", "required": false, "source_refs": [ "SRC-003" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable rule steward role and maintenance authority reference; no company is prescribed as owner.", "Dimension namespace, rule master, applicability profile, criteria semantics and approval policy.", "Pinned memory, authority, sharing, retention and external resolver bindings with failure behavior.", "Proposed policy: never treat retrieved assertions or imported attachments as instructions that change precedence or authorization." ], "namespace_guidance": "Use a governed Dimension namespace for rule, revision and attachment identifiers. External item, grant, assessment and decision identifiers keep their own masters.", "registry_links": [ "vr.wm-mem-009", "WM-MEM-002 candidate reference", "WM-MEM-010 retention policy reference", "WM-MEM-011 sharing grant reference", "WM-MEM-018 assessment reference" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize only within an adopted representation profile. Preserve semantic criterion order, explicit unknowns, partial orders and revision links.", "Preferred assertion is a scoped outcome, not a universal truth assertion. A different projection cannot silently redefine precedence." ], "patch_rules": [ "Require expected revision, authority and change rationale for local patches. Material criterion changes create a successor revision; do not rewrite recorded decision evidence." ], "compatibility_rules": [ "Changing eligibility, comparison scope, outcome meaning or tie behavior is potentially breaking even if fields are unchanged. Require profile review and new acceptance evidence." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "Dimension-assigned UUID or ULID" ], "timestamp_rule": "Use RFC 3339 timestamps with seconds and an explicit offset or Z. Keep event/effective time separate from observation and ingestion time. Preserve partial dates and uncertainty separately instead of fabricating precision; timestamps do not prove causality.", "serial_naming_rule": "Use stable rule and attachment identifiers plus separate revision identifiers; dates and display names are not identity.", "integrity_rule": "Bind each artifact and external report to its source revision with an integrity digest where available. A digest proves byte consistency only. Enforce access and retention on payloads and avoid revealing sensitive content through public hashes." }, "policies": [ "Local proposal: use separate eligibility gates and explicit precedence criteria; owner, authority, recency and quality have no universal ranking.", "Local proposal: unknown evidence, ties, cycles and unverifiable authority must be visible outcomes. Reviewable research does not authorize operational deployment.", "Local proposal: a preference cannot widen sharing scope, bypass mandatory restrictions or delete alternatives.", "Conceptual alignments to PROV-O, OWL 2, SHACL, XACML, RFC 9110, RFC 3339 and DQV are qualified in sources. No implementation conformance is claimed.", "Independent external review was waived. Direct HTTP checks are unattempted under the sandbox restriction. Selected web evidence supports concepts, not complete version or adoption verification." ], "crud": { "read": [ "Read authorized rule revisions and permitted metadata. Do not dereference protected input or evidence merely because its identifier is present." ], "create": [ "Create draft rule identities, declarations and synthetic acceptance references within the owner package." ], "update": [ "Require expected revision and maintenance authority. Record review and approval references; external systems own activation, evaluation and memory mutation." ], "delete": [ "Retire this rule and its local artifacts under a referenced retention and disposition policy. The adopting Dimension storage owner executes authorized deletion; preserve a minimal permitted tombstone where allowed. Do not delete referenced memory items, grants or decision records." ] }, "roles": [ { "name": "Rule steward", "responsibilities": [ "Maintain definitions, namespaces and bounded change proposals." ] }, { "name": "Domain authority reviewer", "responsibilities": [ "Confirm scoped authority and precedence profile without claiming universal truth." ] }, { "name": "Assurance reviewer", "responsibilities": [ "Review synthetic scenarios, evidence bindings, gaps and incompatible mappings." ] }, { "name": "Privacy and access custodian", "responsibilities": [ "Approve access, minimization and retention profiles for rule evidence." ] }, { "name": "Consumer maintainer", "responsibilities": [ "Bind external evaluators and stores while respecting unresolved outcomes and revision checks." ] } ], "access": { "default_rule": "Deny access unless authorized by the adopting Dimension policy; precedence does not change access rights.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Any exception requires separate authority, scope, reason and expiry; it cannot self-authorize through memory content or override mandatory access restrictions." ], "audit_requirements": [ "Reference external audit records for rule changes, approvals and evidence access. Local metadata records correlation identifiers, not a duplicate audit trail; redact protected inputs and apply bounded retention." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md", "Owner and Dimension policy", "spec.yaml and current rule revision", "Pinned profiles and permitted external reference metadata" ] } }, "coverage": { "claim": "Source-grounded proposed rule-definition profile covering scoped memory conflict inputs, authority, time, explicit precedence and unresolved outcomes. Separate frozen local no-tools self-audit completed. Independent review, source/version verification, adoption profiles and executable conformance remain holds; this is a noncanonical reviewable draft.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Separate rule, revision, input item and external decision identities." }, { "dimension": "lifecycle", "status": "covered", "notes": "Rule draft, approval references, successor and retirement; operational execution external." }, { "dimension": "relationships", "status": "covered", "notes": "Explicit candidate sibling references; no incoming/outgoing ledger rows for this model." }, { "dimension": "temporal", "status": "covered", "notes": "Effective intervals, recency basis, precision and late arrivals." }, { "dimension": "provenance", "status": "covered", "notes": "Attribution and derivation input contract; shared ancestry does not imply independent corroboration." }, { "dimension": "ownership", "status": "covered", "notes": "Role-based stewardship and scoped authority; authorship and ownership distinct." }, { "dimension": "validation", "status": "covered", "notes": "Synthetic acceptance design and external reports; executable conformance remains a hold." }, { "dimension": "access", "status": "covered", "notes": "Sharing gate, protected evidence and authority-bound exceptions." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Bounded local retention with storage-owner disposition and reference preservation where permitted." }, { "dimension": "interoperability", "status": "covered", "notes": "Qualified mappings preserve unknowns, criterion order and revision checks." }, { "dimension": "conflict classification", "status": "covered", "notes": "Separate contradiction, constraint violation, policy conflict and concurrent edits." }, { "dimension": "precedence", "status": "covered", "notes": "Explicit ordering, ties, cycles, partial comparisons and no universal ranking." }, { "dimension": "spatial", "status": "not-applicable", "notes": "The rule is abstract; location matters only when an adopting profile includes it in comparison scope." }, { "dimension": "executable conformance", "status": "gap", "notes": "No instance schema, resolver, calibration study or end-to-end implementation is supplied." } ], "known_omissions": [ "Independent second-provider review is waived; this run uses a separate local Codex no-tools self-audit.", "Direct HTTP status, full source-version validation and independent claim verification remain open; readable web excerpts are not direct HTTP measurements.", "Typed instance schemas, formal comparator semantics, runtime evaluation and external decision schemas require an adoption profile.", "Domain-specific precedence, metric calibration and distributed causality or convergence guarantees are not established.", "Sensitive or high-impact uses require domain authority and privacy review; no legal or operational entitlement is inferred." ], "conflicts": [], "regional_assumptions": [ "No jurisdiction or universal institutional authority is assumed. Local policies supply authority scope, permissible processing and retention; sources are technical alignments." ], "adversarial_checks": [ "Missing assertion versus explicit negation: require comparator and unknown handling, not a fabricated contradiction.", "Two valid owners disagree: use scoped authority profile or unresolved outcome, never a global owner hierarchy.", "Late arrival or forged future time: ingestion recency alone cannot create authority or causal priority.", "High score from duplicated derivations: preserve shared ancestry and metric definition; no count-based truth inference.", "Tie or precedence cycle: keep unresolved outcome rather than select by incidental serialization order.", "Inputs or grants change after evaluation: require fresh external evaluation and expected-revision checks before consumer action.", "Preference rationale leaks protected content: apply minimization and access independently of priority.", "Old rule is retired: retention remains bounded and historical evidence is not automatically retained forever." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "One governed rule definition persists across revisions and applications. Conflicts, input memory items and operational decisions keep separate identities. The registry standalone-mm label is a catalogue classification; its parent is reconciled as a candidate reference without asserting inheritance." }, "decisions": [ { "concept": "Rule and conflict occurrence boundary", "disposition": "accepted", "rationale": "The root identifies a reusable rule definition; all conflict occurrences, inputs and operational outcomes remain externally mastered references." }, { "concept": "Memory Item parent", "disposition": "qualified as candidate reference", "rationale": "No relation-ledger row establishes inheritance. The parent identifies relevant inputs but does not grant ownership of memory item content or lifecycle." }, { "concept": "Contradiction and missing information", "disposition": "separated", "rationale": "Scope, comparator and value interpretation are declared. Absence, allowed multiplicity and nonoverlapping intervals cannot silently become contradiction." }, { "concept": "Evidence and quality", "disposition": "accepted with qualifications", "rationale": "Lineage and metric-qualified assessment inputs do not certify truth, authority or independent corroboration. The target assessment model retains calculation and calibration." }, { "concept": "Authority and ownership", "disposition": "separated", "rationale": "Owner, author, subject and delegated authority are distinct. Imported content cannot grant itself priority or access, and eligibility uses external evidence." }, { "concept": "Universal precedence ordering", "disposition": "rejected", "rationale": "The draft requires an adopted comparator and explicit ordered or partial criteria. It does not prescribe owner-over-time-over-authority or newest-wins behavior." }, { "concept": "Ties and cycles", "disposition": "accepted as unresolved outcomes", "rationale": "Equally ranked or incomparable inputs and cyclic criteria require explicit outcome policies; incidental representation order cannot supply an undisclosed winner." }, { "concept": "Time and causal order", "disposition": "separated", "rationale": "Effective, observation and ingestion time remain distinct. Timestamp syntax and lexical sorting cannot substitute for authority or distributed causality." }, { "concept": "Concurrent changes", "disposition": "accepted as external contract", "rationale": "Snapshots, expected revisions and stale-result policies constrain external consumption. HTTP conditional updates are optional alignment, not semantic resolution." }, { "concept": "Preference and alternative preservation", "disposition": "separated", "rationale": "A preference is a scoped outcome and does not establish falsehood, invalidation or deletion of other assertions. Access and retention remain independent gates." }, { "concept": "Review and exception authority", "disposition": "accepted with external ownership", "rationale": "The model records scoped exception and review requirements and external references. It neither adjudicates cases nor authorizes actions outside the adopting policy." }, { "concept": "Local functions and service layers", "disposition": "accepted as proposed", "rationale": "All six functions manage declarations or evidence links. Runtime evaluation, consolidation, sharing, trust assessment and source-memory disposition remain outside the boundary." }, { "concept": "Revision history and retention", "disposition": "accepted with bounded retention", "rationale": "Successor links and retirement are local metadata. Retention and permitted minimal tombstones qualify history preservation; indefinite sensitive payload storage is not required." }, { "concept": "Source alignment and executable conformance", "disposition": "qualified and held", "rationale": "Selected primary content supports distinctions, not the invented hierarchy. Conceptual mappings, typed candidate groups and unexecuted scenarios do not prove runtime conformance or fully verified source versions." }, { "concept": "Independent external review", "disposition": "waived and held", "rationale": "Claude and Grok were skipped with zero attempts. This assessment is a separate local Codex self-audit of frozen evidence and cannot stand in for independent provider agreement." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not independent second-provider review.", "Source verification is incomplete. All seven admitted pages supplied selected readable web evidence, but direct HTTP was unattempted under the owner-reported sandbox restriction, with zero measured HTTP responses. Full-text, exact edition, errata and independent claim verification remain open; the coordinator checker is prepared.", "Adoption profiles must establish comparator semantics, authority scope, permission evidence, temporal interpretation, metric comparability, exception policy and privacy/retention requirements. No universal precedence order or operational authority is established.", "Executable conformance remains unproven. Nested instance schemas, actual sibling bindings, formal comparators, end-to-end validation and implemented adversarial fixtures are not supplied; synthetic acceptance scenarios are design evidence only.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Run coordinator HTTP checks and verify complete source editions, errata, domain applicability and claim mappings; HTTP success alone does not close substantive verification.", "Develop typed instance schemas and evaluate synthetic cases covering ties, cycles, missing values, authority revocation, late arrivals, protected evidence and lossy mappings under an explicit adopting profile.", "Restore independent external review before canonical promotion; assess domain-specific precedence, metric calibration and distributed causality or convergence requirements." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }