# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-21T17:20:23Z", "synthesisSha256": "f13d802e125c18aa18e30ba42b5983c549263d41f12f03b9b27af10c65b1362c", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-MEM-008", "registryId": "vr.wm-mem-008", "name": "Memory Consolidation", "version": "0.1.0-reviewable-draft", "previousVersions": [], "entryKind": "event", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.MEM.CNS" ], "tags": [ "memory", "consolidation", "inf.mem.cns" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-mem-008-memory-consolidation/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-mem-008", "model": { "registry_id": "vr.wm-mem-008", "model_id": "WM-MEM-008", "name": "Memory Consolidation", "entry_kind": "event", "purpose": "Describe a bounded attempt to merge duplicate memory records, produce a summary or request retirement, with traceable inputs, decisions and observed outcomes.", "scope_statement": "One consolidation activity occurrence and its local evidence record, from authorized input selection through proposal, review and reconciliation of external receipts. This is an authored, format-neutral profile grounded in open provenance and governance specifications; no cited source defines a canonical agent-memory consolidation standard.", "in_scope": [ "Run identity, purpose, scope, method pin and source-revision snapshot.", "Candidate duplicate assessment, loss-aware summary proposals and source-to-output lineage.", "Recorded approval, refusal, partial outcome, retirement request and correction dependencies." ], "out_of_scope": [ "Biological memory consolidation, clinical claims, training or model-weight modification.", "Memory-store execution, source item lifecycle, recall ranking, index implementation and context assembly.", "Generic conflict precedence, trust scoring, grants, retention policy authoring, physical erasure and incident response.", "Universal merge thresholds, automated truth certification or executable conformance claims." ], "boundary_notes": [ { "neighbor": "WM-MEM-002 Memory Item", "distinction": "The registry parent is a candidate navigation relationship, not inheritance: an activity uses and generates item revisions but is not itself an item. Item identity and lifecycle remain external.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-MEM-001 Memory Store", "distinction": "The store owns transactional mutation and authoritative receipts. This record tracks proposals and outcomes without claiming to execute store operations.", "source_refs": [ "SRC-001", "SRC-005" ] }, { "neighbor": "WM-MEM-006 Memory Formation Event", "distinction": "Formation explains an individual item origin; consolidation explains the bounded multi-input or single-input transformation attempt. Link any formation events rather than duplicating them.", "source_refs": [ "SRC-001" ] }, { "neighbor": "WM-MEM-009 Memory Conflict and Precedence Rule", "distinction": "Record unresolved conflict and a pinned external ruling; do not invent precedence or use recency alone to resolve truth.", "source_refs": [ "SRC-003", "SRC-006" ] }, { "neighbor": "WM-MEM-010 Memory Retention and Forgetting Policy", "distinction": "Bind policy and receipt references. Retirement from active use, deletion of payload and expiry of local evidence are separate decisions.", "source_refs": [ "SRC-007" ] }, { "neighbor": "WM-MEM-011 Memory Scope and Sharing Grant", "distinction": "Reference permission decisions for each input and derived output. Reading two inputs does not authorize sharing their combination.", "source_refs": [ "SRC-007" ] }, { "neighbor": "WM-MEM-014 Retrieval Index", "distinction": "Record required refresh and invalidation receipt references only; the external index owns update, caching and recall visibility.", "source_refs": [ "SRC-001", "SRC-006" ] }, { "neighbor": "WM-MEM-018 Memory Trust Assessment and WM-MEM-020 Memory Quarantine and Redaction", "distinction": "Treat risk assessments and quarantine/redaction decisions as external bindings. Consolidation cannot upgrade trust by repeating or compressing a claim.", "source_refs": [ "SRC-006", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "title": "PROV-O: The PROV Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-21T17:19:02Z", "relevance": "Sections 3.1-3.3: activity, entity, agent, derivation, revision and invalidation vocabulary. Alignment supports lineage, not factual truth or this proposed consolidation algorithm." }, { "id": "SRC-002", "title": "Constraints of the PROV Data Model", "organization": "W3C", "url": "https://www.w3.org/TR/prov-constraints/", "version_or_date": "Recommendation 2013-04-30", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:19:02Z", "relevance": "Sections 6.1-6.4: identity, event ordering and entity/activity disjointness. Use to check mapped provenance; consistent provenance is not proof that a summary is correct." }, { "id": "SRC-003", "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; retrieved 2026-10-21; exact dated publication pin pending", "source_type": "ontology", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-21T17:19:02Z", "relevance": "Sections 1, 4.1-4.3 and 6: measurements, metrics and contextual quality metadata. It does not prescribe a universal quality score; local acceptance criteria are authored proposals." }, { "id": "SRC-004", "title": "JSON Canonicalization Scheme (JCS)", "organization": "RFC Editor", "url": "https://www.rfc-editor.org/rfc/rfc8785", "version_or_date": "RFC 8785, June 2020, Informational Independent Submission", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-21T17:19:02Z", "relevance": "Section 3: deterministic JSON representation for digesting. Equal canonical bytes are not semantic equivalence of memory claims, and raw bytes require their own digest." }, { "id": "SRC-005", "title": "HTTP Semantics", "organization": "RFC Editor", "url": "https://www.rfc-editor.org/rfc/rfc9110.html", "version_or_date": "RFC 9110, June 2022, STD 97", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:19:02Z", "relevance": "Section 13.1.1: If-Match and strong validators prevent lost updates to a selected representation. An analogy for local revision preconditions; no cross-record transaction guarantee is inferred." }, { "id": "SRC-006", "title": "Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile", "organization": "NIST", "url": "https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf", "version_or_date": "NIST AI 600-1, July 2024", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-21T17:19:02Z", "relevance": "Confabulation and information integrity risk categories; MP-2.2-001 and MS-2.5-003 motivate upstream dependency documentation and output-source review. No memory-specific algorithm or threshold is supplied." }, { "id": "SRC-007", "title": "NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0", "organization": "NIST", "url": "https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.01162020.pdf", "version_or_date": "Version 1.0, 2020-01-16; historical pinned edition, not a latest-version claim", "source_type": "public-authority", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-21T17:19:02Z", "relevance": "Core CT.DM-P1-P9: policy-governed review, alteration, deletion, permissions and minimized audit records. Voluntary framework, not legal authority or an erasure implementation." }, { "id": "SRC-008", "title": "Date and Time on the Internet: Timestamps", "organization": "RFC Editor", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002, section 5.6", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T17:19:02Z", "relevance": "Timestamp syntax with seconds and offsets. Does not establish causal ordering, clock accuracy or the validity interval of a source assertion." } ], "structure": { "bundles": [ { "id": "intent-inputs", "name": "Intent and inputs", "description": "Bind an attempt to its purpose and exact candidate revisions.", "rationale": "Separates event identity from mutable source content.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-008" ], "layers": [ { "id": "run-identity-layer", "name": "Run identity and intent context", "description": "Local research context for run identity and intent; external masters retain delegated operations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "findings": [ { "id": "run-identity", "name": "Run identity and intent", "description": "A stable activity identifier groups one attempt, its declared purpose and observed execution. A planned attempt may have no start or output; a retry has its own attempt identity under the same request key.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ], "questions": [ { "id": "run-identity-q1", "text": "Which master identifier distinguishes this attempt from its request and any retry?", "kind": "identity", "answer_data": [ "run_id", "request_key", "retry_of" ] }, { "id": "run-identity-q2", "text": "Which operation is proposed: duplicate merge, summary, retirement, or an explicit combination?", "kind": "classification", "answer_data": [ "operation_kind", "purpose", "combination_order" ] }, { "id": "run-identity-q3", "text": "Which role owns the consolidation record and its allowed namespace?", "kind": "ownership", "answer_data": [ "owner_role", "dimension_id", "namespace" ] }, { "id": "run-identity-q4", "text": "What are the recorded start, end and observation times, including unknown values?", "kind": "temporal", "answer_data": [ "started_at", "ended_at", "observed_at", "clock_quality" ] } ], "data_elements": [ { "id": "run-identity-data1", "name": "run_id / request_key / retry_of", "description": "Candidate answer group for: Which master identifier distinguishes this attempt from its request and any retry? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "run-identity-data2", "name": "operation_kind / purpose / combination_order", "description": "Candidate answer group for: Which operation is proposed: duplicate merge, summary, retirement, or an explicit combination? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "run-identity-data3", "name": "owner_role / dimension_id / namespace", "description": "Candidate answer group for: Which role owns the consolidation record and its allowed namespace? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] }, { "id": "run-identity-data4", "name": "started_at / ended_at / observed_at / clock_quality", "description": "Candidate answer group for: What are the recorded start, end and observation times, including unknown values? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "artifacts": [ { "id": "run-identity-artifact", "name": "Run declaration", "description": "Versioned evidence for run identity and intent. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-008" ] } ], "inline_only_rationale": null } ] }, { "id": "input-snapshot-layer", "name": "Input membership and revision snapshot context", "description": "Local research context for input membership and revision snapshot; external masters retain delegated operations.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "findings": [ { "id": "input-snapshot", "name": "Input membership and revision snapshot", "description": "Snapshot references identify exact input revisions, selection rules and exclusions. Empty eligible input is a valid no-op; missing revisions cannot be silently replaced with current content.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ], "questions": [ { "id": "input-snapshot-q1", "text": "Which item revisions are included and which candidates were excluded?", "kind": "composition", "answer_data": [ "input_refs", "revision_ids", "exclusions" ] }, { "id": "input-snapshot-q2", "text": "How was the candidate set selected and at which source snapshot?", "kind": "provenance", "answer_data": [ "selection_rule", "store_snapshot", "selection_evidence" ] }, { "id": "input-snapshot-q3", "text": "What must happen if an input revision changes or becomes unavailable before application?", "kind": "constraint", "answer_data": [ "expected_versions", "stale_action", "missing_action" ] }, { "id": "input-snapshot-q4", "text": "Which representation and digest support each snapshot without equating content with identity?", "kind": "evidence", "answer_data": [ "raw_digest", "canonical_digest", "canonicalization_profile", "digest_algorithm" ] } ], "data_elements": [ { "id": "input-snapshot-data1", "name": "input_refs / revision_ids / exclusions", "description": "Candidate answer group for: Which item revisions are included and which candidates were excluded? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "input-snapshot-data2", "name": "selection_rule / store_snapshot / selection_evidence", "description": "Candidate answer group for: How was the candidate set selected and at which source snapshot? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "input-snapshot-data3", "name": "expected_versions / stale_action / missing_action", "description": "Candidate answer group for: What must happen if an input revision changes or becomes unavailable before application? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] }, { "id": "input-snapshot-data4", "name": "raw_digest / canonical_digest / canonicalization_profile / digest_algorithm", "description": "Candidate answer group for: Which representation and digest support each snapshot without equating content with identity? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "artifacts": [ { "id": "input-snapshot-artifact", "name": "Input snapshot manifest", "description": "Versioned evidence for input membership and revision snapshot. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "merge-decisions", "name": "Merge decisions", "description": "Make duplicate and contradiction decisions inspectable.", "rationale": "Prevents similarity and repetition from becoming unearned authority.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "layers": [ { "id": "duplicate-basis-layer", "name": "Duplicate equivalence assessment context", "description": "Local research context for duplicate equivalence assessment; external masters retain delegated operations.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "findings": [ { "id": "duplicate-basis", "name": "Duplicate equivalence assessment", "description": "Distinguish byte equality, normalized equality, semantic similarity and a reviewed equivalence decision. Context, subject, validity interval and permission differences may forbid a merge. Similarity and canonical hashes alone do not authorize equivalence.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ], "questions": [ { "id": "duplicate-basis-q1", "text": "What equivalence criterion is used for this candidate duplicate set?", "kind": "definition", "answer_data": [ "equivalence_kind", "criterion_version", "comparison_scope" ] }, { "id": "duplicate-basis-q2", "text": "How were similarity or equality results measured and qualified?", "kind": "measurement", "answer_data": [ "metric_id", "method_version", "score", "threshold", "uncertainty" ] }, { "id": "duplicate-basis-q3", "text": "Which contextual differences prevent these records from being merged?", "kind": "exception", "answer_data": [ "subject_mismatch", "validity_mismatch", "permission_mismatch", "exceptions" ] }, { "id": "duplicate-basis-q4", "text": "Who accepted, rejected or deferred the equivalence proposal and why?", "kind": "decision", "answer_data": [ "decision", "reviewer_ref", "reason", "evidence_refs" ] } ], "data_elements": [ { "id": "duplicate-basis-data1", "name": "equivalence_kind / criterion_version / comparison_scope", "description": "Candidate answer group for: What equivalence criterion is used for this candidate duplicate set? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "duplicate-basis-data2", "name": "metric_id / method_version / score / threshold / uncertainty", "description": "Candidate answer group for: How were similarity or equality results measured and qualified? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "duplicate-basis-data3", "name": "subject_mismatch / validity_mismatch / permission_mismatch / exceptions", "description": "Candidate answer group for: Which contextual differences prevent these records from being merged? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "duplicate-basis-data4", "name": "decision / reviewer_ref / reason / evidence_refs", "description": "Candidate answer group for: Who accepted, rejected or deferred the equivalence proposal and why? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "duplicate-basis-artifact", "name": "Duplicate assessment", "description": "Versioned evidence for duplicate equivalence assessment. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "conflict-routing-layer", "name": "Contradiction and precedence binding context", "description": "Local research context for contradiction and precedence binding; external masters retain delegated operations.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "conflict-routing", "name": "Contradiction and precedence binding", "description": "Contradictory assertions remain distinguishable, including their time and scope. This model captures a reference to an external precedence decision or holds the affected proposal; frequency and newer timestamps do not settle a conflict.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "conflict-routing-q1", "text": "Which input assertions conflict and which external rule owns their resolution?", "kind": "relationship", "answer_data": [ "conflicting_refs", "conflict_rule_ref", "rule_revision" ] }, { "id": "conflict-routing-q2", "text": "What external decision permits a preferred assertion in this specific scope?", "kind": "authority", "answer_data": [ "ruling_ref", "issuer_role", "scope", "decision_revision" ] }, { "id": "conflict-routing-q3", "text": "Which disputed values remain unresolved in the proposed result?", "kind": "state", "answer_data": [ "unresolved_assertions", "dispute_state", "blocking_scope" ] }, { "id": "conflict-routing-q4", "text": "How is dissent preserved when a proposal proceeds on uncontested inputs?", "kind": "constraint", "answer_data": [ "excluded_claims", "contrary_evidence_refs", "partial_scope" ] } ], "data_elements": [ { "id": "conflict-routing-data1", "name": "conflicting_refs / conflict_rule_ref / rule_revision", "description": "Candidate answer group for: Which input assertions conflict and which external rule owns their resolution? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "conflict-routing-data2", "name": "ruling_ref / issuer_role / scope / decision_revision", "description": "Candidate answer group for: What external decision permits a preferred assertion in this specific scope? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "conflict-routing-data3", "name": "unresolved_assertions / dispute_state / blocking_scope", "description": "Candidate answer group for: Which disputed values remain unresolved in the proposed result? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "conflict-routing-data4", "name": "excluded_claims / contrary_evidence_refs / partial_scope", "description": "Candidate answer group for: How is dissent preserved when a proposal proceeds on uncontested inputs? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "conflict-routing-artifact", "name": "Conflict routing record", "description": "Versioned evidence for contradiction and precedence binding. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "derived-content", "name": "Derived content and lineage", "description": "Describe a proposed summary and its derivation.", "rationale": "Compression must leave a reviewable account of support and loss.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006" ], "layers": [ { "id": "summary-fidelity-layer", "name": "Summary content and information loss context", "description": "Local research context for summary content and information loss; external masters retain delegated operations.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "findings": [ { "id": "summary-fidelity", "name": "Summary content and information loss", "description": "A summary is a proposed derived item with a declared purpose and loss budget. Negation, qualifications, attribution and uncertainty require review. Unsupported output claims are rejected or explicitly marked unverified; compression does not create knowledge.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ], "questions": [ { "id": "summary-fidelity-q1", "text": "Which method, instruction revision and parameters produced the summary proposal?", "kind": "process", "answer_data": [ "method_ref", "instruction_digest", "parameters", "language" ] }, { "id": "summary-fidelity-q2", "text": "Which input spans support each retained summary assertion?", "kind": "evidence", "answer_data": [ "output_claim_id", "input_revision", "span_locator", "support_relation" ] }, { "id": "summary-fidelity-q3", "text": "What information was omitted or distorted relative to the stated purpose?", "kind": "quality", "answer_data": [ "omission_inventory", "qualification_checks", "loss_assessment" ] }, { "id": "summary-fidelity-q4", "text": "What evidence permits approval or requires rejection of the summary?", "kind": "validation", "answer_data": [ "acceptance_profile", "review_results", "unsupported_claims", "verdict" ] } ], "data_elements": [ { "id": "summary-fidelity-data1", "name": "method_ref / instruction_digest / parameters / language", "description": "Candidate answer group for: Which method, instruction revision and parameters produced the summary proposal? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "summary-fidelity-data2", "name": "output_claim_id / input_revision / span_locator / support_relation", "description": "Candidate answer group for: Which input spans support each retained summary assertion? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "summary-fidelity-data3", "name": "omission_inventory / qualification_checks / loss_assessment", "description": "Candidate answer group for: What information was omitted or distorted relative to the stated purpose? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] }, { "id": "summary-fidelity-data4", "name": "acceptance_profile / review_results / unsupported_claims / verdict", "description": "Candidate answer group for: What evidence permits approval or requires rejection of the summary? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "summary-fidelity-artifact", "name": "Summary fidelity report", "description": "Versioned evidence for summary content and information loss. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "lineage-map-layer", "name": "Derivation and identity continuity context", "description": "Local research context for derivation and identity continuity; external masters retain delegated operations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "findings": [ { "id": "lineage-map", "name": "Derivation and identity continuity", "description": "Outputs retain their own item identifiers and revisions, linked to all contributing inputs and the activity. Duplicate aliases are governed mappings, not fabricated identity equality. Lineage metadata remains access controlled and subject to retention.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ], "questions": [ { "id": "lineage-map-q1", "text": "Which input-to-output edges explain the transformation and responsible agent?", "kind": "provenance", "answer_data": [ "input_ref", "output_ref", "activity_ref", "agent_ref", "derivation_kind" ] }, { "id": "lineage-map-q2", "text": "Which output identity is new, retained or an authorized alias of an existing item?", "kind": "identity", "answer_data": [ "output_id", "identity_action", "alias_authority", "alias_target" ] }, { "id": "lineage-map-q3", "text": "Does the mapped lineage satisfy the applicable usage, generation and invalidation ordering?", "kind": "temporal", "answer_data": [ "ordering_check", "event_refs", "unknown_times", "violation_refs" ] }, { "id": "lineage-map-q4", "text": "What mapping and loss report accompany a PROV-O projection?", "kind": "interoperability", "answer_data": [ "mapping_version", "qualified_edges", "unmapped_fields", "roundtrip_report" ] } ], "data_elements": [ { "id": "lineage-map-data1", "name": "input_ref / output_ref / activity_ref / agent_ref / derivation_kind", "description": "Candidate answer group for: Which input-to-output edges explain the transformation and responsible agent? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "lineage-map-data2", "name": "output_id / identity_action / alias_authority / alias_target", "description": "Candidate answer group for: Which output identity is new, retained or an authorized alias of an existing item? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "lineage-map-data3", "name": "ordering_check / event_refs / unknown_times / violation_refs", "description": "Candidate answer group for: Does the mapped lineage satisfy the applicable usage, generation and invalidation ordering? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] }, { "id": "lineage-map-data4", "name": "mapping_version / qualified_edges / unmapped_fields / roundtrip_report", "description": "Candidate answer group for: What mapping and loss report accompany a PROV-O projection? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "lineage-map-artifact", "name": "Derivation map", "description": "Versioned evidence for derivation and identity continuity. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "controlled-application", "name": "Controlled application", "description": "Capture authority and externally evidenced change outcomes.", "rationale": "Proposal, approval and actual mutation are different states.", "source_refs": [ "SRC-001", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "approval-gate-layer", "name": "Authorization and output audience context", "description": "Local research context for authorization and output audience; external masters retain delegated operations.", "source_refs": [ "SRC-006", "SRC-007" ], "findings": [ { "id": "approval-gate", "name": "Authorization and output audience", "description": "Per-input processing authority and output purpose are checked separately. The output audience is no broader than what all contributing restrictions permit unless an explicit authorized transformation and release decision applies. Unknown authorization blocks release.", "source_refs": [ "SRC-006", "SRC-007" ], "questions": [ { "id": "approval-gate-q1", "text": "Which principals may read each input and the derived output for this purpose?", "kind": "access", "answer_data": [ "input_grant_refs", "output_grant_ref", "purpose", "audience" ] }, { "id": "approval-gate-q2", "text": "Which role may approve the proposal and what separation of duties applies?", "kind": "authority", "answer_data": [ "approver_role", "delegation_ref", "review_policy", "approval_ref" ] }, { "id": "approval-gate-q3", "text": "What sensitive information or inference requires redaction or a narrower output scope?", "kind": "privacy", "answer_data": [ "sensitivity_refs", "inference_risk", "redaction_decision_ref" ] }, { "id": "approval-gate-q4", "text": "How are embedded instructions and quarantined inputs treated during consolidation review?", "kind": "security", "answer_data": [ "untrusted_content_rule", "quarantine_refs", "admission_decision" ] } ], "data_elements": [ { "id": "approval-gate-data1", "name": "input_grant_refs / output_grant_ref / purpose / audience", "description": "Candidate answer group for: Which principals may read each input and the derived output for this purpose? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "approval-gate-data2", "name": "approver_role / delegation_ref / review_policy / approval_ref", "description": "Candidate answer group for: Which role may approve the proposal and what separation of duties applies? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "approval-gate-data3", "name": "sensitivity_refs / inference_risk / redaction_decision_ref", "description": "Candidate answer group for: What sensitive information or inference requires redaction or a narrower output scope? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "approval-gate-data4", "name": "untrusted_content_rule / quarantine_refs / admission_decision", "description": "Candidate answer group for: How are embedded instructions and quarantined inputs treated during consolidation review? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "approval-gate-artifact", "name": "Authorization assessment", "description": "Versioned evidence for authorization and output audience. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "application-receipts-layer", "name": "Conditional application and partial outcomes context", "description": "Local research context for conditional application and partial outcomes; external masters retain delegated operations.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "application-receipts", "name": "Conditional application and partial outcomes", "description": "Record store-issued receipts and expected revisions, not inferred success from a prepared proposal. The local event may reconcile partial results; a profile must define atomicity or compensation. HTTP conditional semantics alone do not make a multi-item transaction atomic.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "application-receipts-q1", "text": "Which external store operation is bound to the approved proposal revision?", "kind": "process", "answer_data": [ "operation_ref", "proposal_revision", "store_binding", "request_key" ] }, { "id": "application-receipts-q2", "text": "What conditional-write and atomicity contract applies to this change set?", "kind": "constraint", "answer_data": [ "expected_versions", "transaction_boundary", "atomicity_mode", "refusal_result" ] }, { "id": "application-receipts-q3", "text": "Which authoritative receipts identify applied, refused or unknown item outcomes?", "kind": "event", "answer_data": [ "receipt_refs", "per_item_status", "acknowledged_revision", "observed_at" ] }, { "id": "application-receipts-q4", "text": "How are retries and partial application reconciled without duplicate outputs?", "kind": "exception", "answer_data": [ "retry_key", "previous_receipts", "partial_scope", "reconciliation_decision" ] } ], "data_elements": [ { "id": "application-receipts-data1", "name": "operation_ref / proposal_revision / store_binding / request_key", "description": "Candidate answer group for: Which external store operation is bound to the approved proposal revision? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "application-receipts-data2", "name": "expected_versions / transaction_boundary / atomicity_mode / refusal_result", "description": "Candidate answer group for: What conditional-write and atomicity contract applies to this change set? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "application-receipts-data3", "name": "receipt_refs / per_item_status / acknowledged_revision / observed_at", "description": "Candidate answer group for: Which authoritative receipts identify applied, refused or unknown item outcomes? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "application-receipts-data4", "name": "retry_key / previous_receipts / partial_scope / reconciliation_decision", "description": "Candidate answer group for: How are retries and partial application reconciled without duplicate outputs? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "application-receipts-artifact", "name": "Application reconciliation record", "description": "Versioned evidence for conditional application and partial outcomes. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "disposition-impact", "name": "Disposition and downstream impact", "description": "Track retirement requests and dependent visibility.", "rationale": "Source retirement alone cannot establish forgetting across dependent copies.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "layers": [ { "id": "retirement-disposition-layer", "name": "Retirement and deletion distinction context", "description": "Local research context for retirement and deletion distinction; external masters retain delegated operations.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "retirement-disposition", "name": "Retirement and deletion distinction", "description": "A successful consolidation may propose retirement of redundant items. It neither proves payload erasure nor overrides retention or legal hold. External policy and store owners execute disposition; this record carries minimal authorized evidence.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "retirement-disposition-q1", "text": "Which source items are proposed for retirement and what replacement references remain?", "kind": "lifecycle", "answer_data": [ "retirement_candidates", "replacement_refs", "effective_state" ] }, { "id": "retirement-disposition-q2", "text": "Which policy revision and applicable hold govern each proposed disposition?", "kind": "retention", "answer_data": [ "retention_policy_ref", "policy_revision", "hold_refs", "disposition_basis" ] }, { "id": "retirement-disposition-q3", "text": "What external receipt distinguishes retirement, redaction and completed deletion?", "kind": "evidence", "answer_data": [ "disposition_receipt", "action_kind", "completion_scope", "unconfirmed_copies" ] }, { "id": "retirement-disposition-q4", "text": "What local lineage metadata may be retained after payload erasure?", "kind": "privacy", "answer_data": [ "minimal_tombstone_fields", "retention_basis", "expiry", "restricted_link_refs" ] } ], "data_elements": [ { "id": "retirement-disposition-data1", "name": "retirement_candidates / replacement_refs / effective_state", "description": "Candidate answer group for: Which source items are proposed for retirement and what replacement references remain? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "retirement-disposition-data2", "name": "retention_policy_ref / policy_revision / hold_refs / disposition_basis", "description": "Candidate answer group for: Which policy revision and applicable hold govern each proposed disposition? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "retirement-disposition-data3", "name": "disposition_receipt / action_kind / completion_scope / unconfirmed_copies", "description": "Candidate answer group for: What external receipt distinguishes retirement, redaction and completed deletion? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "retirement-disposition-data4", "name": "minimal_tombstone_fields / retention_basis / expiry / restricted_link_refs", "description": "Candidate answer group for: What local lineage metadata may be retained after payload erasure? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "retirement-disposition-artifact", "name": "Disposition request and evidence", "description": "Versioned evidence for retirement and deletion distinction. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "downstream-effects-layer", "name": "Dependent copies and visibility context", "description": "Local research context for dependent copies and visibility; external masters retain delegated operations.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "findings": [ { "id": "downstream-effects", "name": "Dependent copies and visibility", "description": "A dependency ledger references summaries, aliases, caches and indexes affected by a change. Local completion requires the profile-defined acknowledgments; missing acknowledgments leave a visible reconciliation state. The ledger is not an index or an erasure engine.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ], "questions": [ { "id": "downstream-effects-q1", "text": "Which dependent records and retrieval surfaces reference affected item revisions?", "kind": "relationship", "answer_data": [ "dependent_refs", "index_refs", "cache_refs", "dependency_revision" ] }, { "id": "downstream-effects-q2", "text": "Which refresh or restriction acknowledgments are required before declaring the run reconciled?", "kind": "requirement", "answer_data": [ "required_receipts", "visibility_rule", "timeout_policy" ] }, { "id": "downstream-effects-q3", "text": "Which downstream surfaces remain stale or have unknown disposition?", "kind": "state", "answer_data": [ "surface_status", "last_receipt", "pending_scope" ] }, { "id": "downstream-effects-q4", "text": "How are inaccessible or offline dependencies reported without claiming global completion?", "kind": "exception", "answer_data": [ "unreachable_refs", "exception_owner", "review_due", "residual_risk" ] } ], "data_elements": [ { "id": "downstream-effects-data1", "name": "dependent_refs / index_refs / cache_refs / dependency_revision", "description": "Candidate answer group for: Which dependent records and retrieval surfaces reference affected item revisions? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "downstream-effects-data2", "name": "required_receipts / visibility_rule / timeout_policy", "description": "Candidate answer group for: Which refresh or restriction acknowledgments are required before declaring the run reconciled? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "downstream-effects-data3", "name": "surface_status / last_receipt / pending_scope", "description": "Candidate answer group for: Which downstream surfaces remain stale or have unknown disposition? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] }, { "id": "downstream-effects-data4", "name": "unreachable_refs / exception_owner / review_due / residual_risk", "description": "Candidate answer group for: How are inaccessible or offline dependencies reported without claiming global completion? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "downstream-effects-artifact", "name": "Dependency reconciliation ledger", "description": "Versioned evidence for dependent copies and visibility. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-001", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "recovery-assurance", "name": "Recovery and assurance", "description": "Record correction proposals and acceptance evidence.", "rationale": "A completed event can still require later correction and residual-risk reporting.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-006", "SRC-007" ], "layers": [ { "id": "correction-recovery-layer", "name": "Correction and compensating activity context", "description": "Local research context for correction and compensating activity; external masters retain delegated operations.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ], "findings": [ { "id": "correction-recovery", "name": "Correction and compensating activity", "description": "Corrections preserve the original event record subject to retention, and link a new authorized activity. A false merge can require item separation and dependent invalidation. Recovery cannot restore erased payloads or bypass current restrictions.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ], "questions": [ { "id": "correction-recovery-q1", "text": "What defect or later evidence triggered correction of a completed consolidation?", "kind": "event", "answer_data": [ "defect_ref", "new_evidence_ref", "affected_run", "detected_at" ] }, { "id": "correction-recovery-q2", "text": "Which compensating proposal addresses the defect under current authority?", "kind": "process", "answer_data": [ "compensation_run", "affected_outputs", "current_grants", "plan_ref" ] }, { "id": "correction-recovery-q3", "text": "Which effects are reversible and which cannot be restored?", "kind": "constraint", "answer_data": [ "reversible_effects", "erased_inputs", "irreversible_effects", "refusal_reason" ] }, { "id": "correction-recovery-q4", "text": "What external evidence confirms corrected lineage and downstream reconciliation?", "kind": "validation", "answer_data": [ "correction_receipts", "lineage_check", "dependent_acknowledgments", "residual_gaps" ] } ], "data_elements": [ { "id": "correction-recovery-data1", "name": "defect_ref / new_evidence_ref / affected_run / detected_at", "description": "Candidate answer group for: What defect or later evidence triggered correction of a completed consolidation? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "correction-recovery-data2", "name": "compensation_run / affected_outputs / current_grants / plan_ref", "description": "Candidate answer group for: Which compensating proposal addresses the defect under current authority? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "correction-recovery-data3", "name": "reversible_effects / erased_inputs / irreversible_effects / refusal_reason", "description": "Candidate answer group for: Which effects are reversible and which cannot be restored? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] }, { "id": "correction-recovery-data4", "name": "correction_receipts / lineage_check / dependent_acknowledgments / residual_gaps", "description": "Candidate answer group for: What external evidence confirms corrected lineage and downstream reconciliation? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] } ], "artifacts": [ { "id": "correction-recovery-artifact", "name": "Correction assessment", "description": "Versioned evidence for correction and compensating activity. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "evaluation-evidence-layer", "name": "Quality evaluation and acceptance record context", "description": "Local research context for quality evaluation and acceptance record; external masters retain delegated operations.", "source_refs": [ "SRC-003", "SRC-006" ], "findings": [ { "id": "evaluation-evidence", "name": "Quality evaluation and acceptance record", "description": "Evaluate a proposal against explicit use-specific criteria and record the assessor, fixture set and uncertainty. Proposed metrics include false merges, unsupported claims and loss of qualifications. No universal numeric acceptance threshold or executed benchmark is claimed.", "source_refs": [ "SRC-003", "SRC-006" ], "questions": [ { "id": "evaluation-evidence-q1", "text": "Which metrics and denominators measure consolidation quality for this profile?", "kind": "measurement", "answer_data": [ "metric_definitions", "denominators", "units", "population" ] }, { "id": "evaluation-evidence-q2", "text": "Which edge cases were assessed and what limitations remain?", "kind": "quality", "answer_data": [ "fixture_set", "language_coverage", "negative_cases", "sampling_limits" ] }, { "id": "evaluation-evidence-q3", "text": "What profile thresholds and reviewer evidence justify accepting this run?", "kind": "decision", "answer_data": [ "threshold_profile", "reviewer_ref", "assessment_refs", "acceptance_decision" ] }, { "id": "evaluation-evidence-q4", "text": "Which schema and reference checks must an adopting implementation demonstrate?", "kind": "interoperability", "answer_data": [ "schema_version", "mapping_tests", "reference_checks", "conformance_report" ] } ], "data_elements": [ { "id": "evaluation-evidence-data1", "name": "metric_definitions / denominators / units / population", "description": "Candidate answer group for: Which metrics and denominators measure consolidation quality for this profile? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "evaluation-evidence-data2", "name": "fixture_set / language_coverage / negative_cases / sampling_limits", "description": "Candidate answer group for: Which edge cases were assessed and what limitations remain? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "evaluation-evidence-data3", "name": "threshold_profile / reviewer_ref / assessment_refs / acceptance_decision", "description": "Candidate answer group for: What profile thresholds and reviewer evidence justify accepting this run? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "id": "evaluation-evidence-data4", "name": "schema_version / mapping_tests / reference_checks / conformance_report", "description": "Candidate answer group for: Which schema and reference checks must an adopting implementation demonstrate? Preserve explicit unknown, not-applicable and withheld states. Nested schema is an adoption hold.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] } ], "artifacts": [ { "id": "evaluation-evidence-artifact", "name": "Acceptance evidence record", "description": "Versioned evidence for quality evaluation and acceptance record. Store references instead of unnecessary source payload; author and authority are recorded.", "media_or_form": [ "application/json", "text/markdown" ], "serial": true, "identity_strategy": "Authoritative master-system artifact identifier first; governed IRI second; Dimension-assigned UUID third. Separate stable identity from revision and digest.", "source_refs": [ "SRC-003", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-attempt", "name": "Register consolidation attempt", "description": "Create a local declaration and input manifest without executing any store mutation. Proposed local operation only; no implementation is supplied.", "inputs": [ "request and purpose", "authorized input revision references" ], "outputs": [ "run declaration", "input snapshot or refusal" ], "preconditions": [ "Caller may create within the owner namespace", "Input references are readable under the processing purpose" ], "effects": [ "Assign run identity and separate retry key", "Record absent or ineligible input as no-op; do not invent content" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "record-merge-assessment", "name": "Record duplicate assessment", "description": "Store a reviewer-supported equivalence proposal; this operation is not an equivalence or trust engine. Proposed local operation only; no implementation is supplied.", "inputs": [ "candidate item revisions", "comparison evidence and external conflict ruling if needed" ], "outputs": [ "duplicate assessment", "unresolved conflict references" ], "preconditions": [ "Exact revisions identified", "Comparison criterion and responsible assessor supplied" ], "effects": [ "Record accepted, rejected or deferred equivalence", "Preserve contrary evidence and identity distinctions" ], "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "id": "record-summary-proposal", "name": "Record summary proposal", "description": "Attach a derived-content proposal and its support/loss report; generation and factual evaluation remain separately evidenced. Proposed local operation only; no implementation is supplied.", "inputs": [ "proposed summary revision", "claim-to-input mapping", "method and fidelity evidence" ], "outputs": [ "summary proposal", "derivation map or refusal" ], "preconditions": [ "Input processing allowed", "Unsupported claims explicitly identified", "No inherited instruction authority from source content" ], "effects": [ "Record candidate output without promoting it to accepted memory", "Keep uncertainty and omissions inspectable" ], "source_refs": [ "SRC-001", "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "record-release-decision", "name": "Record release decision", "description": "Record approval or rejection for an exact proposal and output audience. Proposed local operation only; no implementation is supplied.", "inputs": [ "proposal revision", "grant bindings", "review verdict" ], "outputs": [ "approval record or refusal" ], "preconditions": [ "Approver authorized for purpose and scope", "Restrictions checked for all contributors", "Unknown grants block release" ], "effects": [ "Bind decision to revision and constraints", "Do not invoke external writes or broaden grants" ], "source_refs": [ "SRC-006", "SRC-007" ] }, { "id": "reconcile-outcomes", "name": "Reconcile external outcomes", "description": "Record authenticated external receipts and classify the local activity outcome. Proposed local operation only; no implementation is supplied.", "inputs": [ "approved revision", "store and disposition receipts", "dependency acknowledgments" ], "outputs": [ "reconciliation record", "pending scope or terminal result" ], "preconditions": [ "Receipt issuer and request binding verified", "Expected revisions and per-item outcomes compared" ], "effects": [ "Distinguish completed, partial, refused and unknown effects", "Do not infer deletion or global consistency from local success" ], "source_refs": [ "SRC-001", "SRC-005", "SRC-007" ] }, { "id": "record-correction", "name": "Record correction proposal", "description": "Link a new proposed compensating activity and later evidence to a defective run. Proposed local operation only; no implementation is supplied.", "inputs": [ "defect evidence", "current policy and grants", "affected dependency references" ], "outputs": [ "correction assessment", "linked activity or refusal" ], "preconditions": [ "Caller may annotate the event", "Current authority checked", "Erased material cannot be reconstructed by this operation" ], "effects": [ "Preserve original evidence subject to retention", "Record irreversible effects and pending downstream correction" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ] } ], "composition": [ { "target": "WM-MEM-001", "relation": "REFERENCE", "purpose": "Bind a store and its external mutation receipts; do not own store lifecycle. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "target": "WM-MEM-002", "relation": "REFERENCE", "purpose": "Inputs and outputs reference exact item revisions; registry parent is not subject inheritance. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-MEM-006", "relation": "REFERENCE", "purpose": "Link output formation events where separately recorded. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-MEM-009", "relation": "REFERENCE", "purpose": "Bind a scope-specific conflict ruling without authoring precedence. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-003", "SRC-006" ] }, { "target": "WM-MEM-010", "relation": "REFERENCE", "purpose": "Bind retention policy and disposition authority, including local evidence retention. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "WM-MEM-011", "relation": "REFERENCE", "purpose": "Bind processing and output sharing decisions without minting grants. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-007" ] }, { "target": "WM-MEM-014", "relation": "REFERENCE", "purpose": "Reference index refresh and invalidation receipts without implementing retrieval. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-001", "SRC-006" ] }, { "target": "WM-MEM-018", "relation": "REFERENCE", "purpose": "Reference source trust assessment without upgrading trust through consolidation. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-MEM-020", "relation": "REFERENCE", "purpose": "Reference quarantine and redaction decisions; processing remains policy limited. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-006", "SRC-007" ] }, { "target": "https://www.w3.org/TR/prov-o/", "relation": "ALIGN", "purpose": "Conceptual mapping of activity, entity revisions, agents and derivation; implementation and conformance remain unproven. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "https://www.w3.org/TR/vocab-dqv/", "relation": "ALIGN", "purpose": "Conceptual quality measurement mapping with locally defined metrics and uncertainty. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted.", "required": false, "source_refs": [ "SRC-003" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "An accountable memory operator role owns the namespace and declares processing purposes.", "Pin store, item, conflict, grant and retention bindings before an implementation acts.", "Declare acceptance metrics, approval roles, atomicity, retry semantics and evidence retention.", "Maintain a minimal AGENTS.md entry point and report unresolved bindings." ], "namespace_guidance": "Use a Dimension-controlled namespace for run, proposal, artifact and revision identifiers. Source identifiers keep their original authority; do not encode dates as identities.", "registry_links": [ "vr.wm-mem-008", "WM-MEM-002", "WM-MEM-010", "WM-MEM-011" ] }, "canon_and_patch": { "canonicalization_rules": [ "This research is a noncanonical reviewable draft. Keep source payload, comparison normalization and artifact canonicalization separate.", "For a chosen JSON binding, pin RFC 8785 applicability and representational limitations; equal digests do not prove equivalent claims." ], "patch_rules": [ "Append a revision with actor, reason, expected prior revision and changed fields; corrections never silently rewrite an observed event.", "Material changes to input membership, scope or proposal content require renewed review; refuse stale preconditions." ], "compatibility_rules": [ "Version state vocabularies and mappings; preserve unknown extensions or report losses.", "Compatible projections retain input revisions, authority, uncertainty and outcome distinctions." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "Dimension-assigned UUID or ULID" ], "timestamp_rule": "Use RFC 3339 with seconds and an explicit offset or Z. Keep execution event time separate from observation or ingestion time and from source validity intervals; unknown time is explicit.", "serial_naming_rule": "Use stable artifact identifiers with separate revision tokens and ordered evidence entries. Dates may label an artifact but are not its identity.", "integrity_rule": "Record digest algorithm, representation profile, issuer and revision. Verify digests where authorized; a digest establishes neither truth nor processing authority." }, "policies": [ "Treat memory content as untrusted data; embedded instructions have no authority. Quarantine and security incidents are external policy workflows.", "A summary inherits contributing processing restrictions unless an authorized release decision documents a permitted transformation. Unknown permissions block release.", "Never treat compression, repetition, confidence scores or provenance presence as proof of a claim. Preserve disputed assertions and missing evidence.", "Dangerous content remains at policy level; this model records controls and decisions, not operational harmful instructions." ], "crud": { "read": [ "Authorize purpose and field scope before reading run evidence or following lineage. Avoid disclosing restricted existence or identifiers." ], "create": [ "Create a run declaration, proposal or evidence record only under an authorized owner namespace; execution is separately delegated." ], "update": [ "Require expected revision and actor authority. Record actual external effects only from validated receipts; partial and unknown outcomes remain visible." ], "delete": [ "Apply the adopting Dimension retention policy to this model's own evidence; erase restricted payload and retain only authorized minimal tombstones.", "Referenced item retirement or deletion is executed by the external store under WM-MEM-010 policy, never by deletion of this event record.", "History and lineage preservation are subordinate to applicable erasure and retention obligations; no perpetual personal-data archive is required." ] }, "roles": [ { "name": "Memory operator", "responsibilities": [ "Own run namespace and bind approved profiles." ] }, { "name": "Proposal author", "responsibilities": [ "Record methods, candidate outputs and limitations without approving their own restricted release unless policy permits." ] }, { "name": "Reviewer", "responsibilities": [ "Assess equivalence, summary fidelity and unresolved disputes against explicit criteria." ] }, { "name": "Authorized approver", "responsibilities": [ "Approve exact revisions and output scope under documented delegation." ] }, { "name": "Evidence custodian", "responsibilities": [ "Reconcile external receipts and enforce evidence retention and access." ] } ], "access": { "default_rule": "Deny by default. Check purpose, tenant, subject scope and inherited restrictions for both payload and lineage metadata.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Only a documented time-limited delegation or release decision may authorize an exception; record issuer, purpose and expiry.", "Revocation requires re-evaluation before further processing; reading inputs does not grant output publication." ], "audit_requirements": [ "Record actor, scope, decision reference, revision, time and outcome with minimized content.", "Store audit-trail references; the external audit service owns its integrity and lifecycle." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md", "spec.yaml and publication holds", "Dimension purpose, authorization and retention policies", "Pinned neighbor bindings and exact input revisions", "Proposal evidence, external receipts and unresolved reconciliation" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one memory consolidation activity, reviewed in a separate local no-tools self-audit. Independent review, source verification, adoption profiles and executable conformance remain holds. This is a noncanonical reviewable draft, not an implemented memory engine.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Run, request, item, revision and artifact identities are distinct." }, { "dimension": "lifecycle", "status": "covered", "notes": "Authored proposed states: planned, reviewing, approved, refused, applying, partial, reconciled and correction-linked. Applying and outcomes require external evidence; no engine supplied." }, { "dimension": "relationships", "status": "covered", "notes": "Candidate neighbor bindings preserve external ownership; no relation-ledger rows were found for this model." }, { "dimension": "temporal", "status": "covered", "notes": "Execution, observation and source validity are separate; unknown and uncertain clocks do not fabricate causal order." }, { "dimension": "provenance", "status": "covered", "notes": "Input revision membership, output claims and responsible activity are linked; lineage cannot certify truth." }, { "dimension": "ownership", "status": "covered", "notes": "Accountable operator and delegated roles; no company or product owns the model." }, { "dimension": "validation", "status": "gap", "notes": "Schema-valid research is not an executable instance schema or tested consolidation implementation." }, { "dimension": "access", "status": "covered", "notes": "Per-input permission, derived audience, metadata restrictions and revocation are explicit." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Retirement, erasure, minimal tombstones and dependent visibility remain distinct." }, { "dimension": "interoperability", "status": "gap", "notes": "PROV-O and DQV alignments are conceptual; pinned mappings and roundtrip fixtures remain unbuilt." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Declared attempts and observed external outcomes are distinguished using receipts and assessors." }, { "dimension": "direct properties", "status": "covered", "notes": "Operation kind, purpose, membership, state and measured quality apply; physical geometry and mass are inapplicable to this abstract event." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Six proposed local recording functions have prerequisites, outputs, refusal paths and effects; store actions remain external." }, { "dimension": "context and evidence", "status": "covered", "notes": "Purpose, scope, authorities, uncertainty, policy bindings and evidence references accompany decisions." }, { "dimension": "source verification", "status": "gap", "notes": "Eight official URLs read through the web service at selected sections. Direct HTTP unattempted under owner-reported sandbox restriction; current versions and errata not exhaustively checked." }, { "dimension": "independent review", "status": "gap", "notes": "Codex only under owner waiver; separate no-tools self-audit required and not independent external review." } ], "known_omissions": [ "Nested required instance fields, enumerations and cross-field schemas are not yet implemented.", "No empirical evaluation establishes merge thresholds, summary fidelity or performance across languages and memory modalities.", "No atomic store adapter, erasure engine, index connector or rollback implementation is supplied.", "Source versions, current errata, licensing and claim-level independent verification remain open." ], "conflicts": [], "regional_assumptions": [ "No jurisdiction-specific retention period, erasure right or legal basis is asserted. Adopters must supply applicable policy and qualified review.", "NIST guidance is used as voluntary risk-management input, not as law or certification." ], "adversarial_checks": [ "Similar text about different people, time intervals or purposes must not be automatically merged.", "Repeated claims and summaries must not accumulate unearned confidence or suppress contrary evidence.", "A summary of restricted inputs cannot silently widen its audience or strip qualifications.", "Stale input revisions, retries and partial receipts must not produce false completed states.", "Erasure of inputs constrains recovery and local lineage retention; hashes and tombstones can themselves expose information." ] }, "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": "event", "status": "accepted", "rationale": "The subject is one bounded consolidation activity occurrence, including its prospective declaration and observed outcomes. It may have duration. The local record does not own memory items, grants, policy, store execution or index lifecycle; the registry parent is reconciled as a reference candidate." }, "decisions": [ { "concept": "Activity boundary and registry parent", "disposition": "accepted", "rationale": "One occurrence with duration, prospective declaration and observed outcomes is defensibly classified as event. The memory item parent is a reference candidate, not inheritance. Biological memory and training are explicitly excluded." }, { "concept": "run-identity", "disposition": "accepted", "rationale": "Run, request, retry and artifact identities remain distinct. A declaration does not assert that execution happened; absent times and no-op outcomes remain possible." }, { "concept": "input-snapshot", "disposition": "accepted", "rationale": "Exact item revisions, selection scope, exclusions and unavailable inputs are explicit. Representation digests support integrity without replacing item identity or current authorization." }, { "concept": "duplicate-basis", "disposition": "accepted with profile hold", "rationale": "Similarity, canonical-byte equality and reviewed equivalence are separated. Subject, time and permissions can defeat a merge. Numeric thresholds and false-merge evaluation must be supplied by an adopting profile." }, { "concept": "conflict-routing", "disposition": "accepted", "rationale": "Contrary assertions and external ruling references survive the proposal. The draft does not create a precedence engine or assume that recency or repetition establishes truth." }, { "concept": "summary-fidelity", "disposition": "accepted with evidence limit", "rationale": "Support mapping, omissions, qualifications and unsupported assertions are explicit. An unverified claim label is not approval as established fact. The profile must determine when any such proposal is usable." }, { "concept": "lineage-map", "disposition": "accepted", "rationale": "Input and output revisions, activity and agent attribution are distinct. Aliases require authority. A valid provenance graph or digest cannot certify factual correctness, and metadata remains restricted." }, { "concept": "approval-gate", "disposition": "accepted", "rationale": "Processing authority and output audience are separate decisions. Reading all inputs cannot silently widen output access; unknown permission blocks release. Embedded instructions remain untrusted data." }, { "concept": "application-receipts", "disposition": "accepted", "rationale": "External receipts, expected revisions and per-item outcomes ground observed effects. The result explicitly avoids claiming atomic transactions or safe retries solely from HTTP conditional semantics." }, { "concept": "retirement-disposition", "disposition": "accepted", "rationale": "Retirement, payload erasure and expiry of local evidence remain separate. External policy and store owners execute disposition; preservation of history cannot require indefinite personal-data retention." }, { "concept": "downstream-effects", "disposition": "accepted with residual-risk reporting", "rationale": "Dependent visibility and missing acknowledgments stay visible. An inaccessible dependency cannot be counted as globally forgotten or reconciled merely because the local record is complete." }, { "concept": "correction-recovery", "disposition": "accepted", "rationale": "Correction links a new authorized activity, preserves the earlier record only within retention rules, and refuses to promise recovery of erased payloads or unrestricted rollback." }, { "concept": "evaluation-evidence", "disposition": "deferred implementation", "rationale": "Purpose-specific metrics, denominators and edge cases are elicited. These are proposed requirements, not executed benchmarks. Optional candidate object fields do not establish an executable instance schema." }, { "concept": "Functions and service ownership", "disposition": "accepted as proposed only", "rationale": "All six functions record local declarations, proposals or evidence. They do not execute merges, create grants, adjudicate conflicts, delete source records or update indexes. All eight service sections preserve those boundaries." }, { "concept": "Source and provider assurance", "disposition": "limited", "rationale": "The frozen evidence contains selected readings of eight official sources and no measured direct HTTP status. General provenance and governance sources ground an authored proposal, not an existing consolidation standard. No waived-provider result exists." } ], "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 an independent second-provider review.", "Live source, version, errata and reuse-term verification remains incomplete. Selected text from eight official sources was read through the web service. Direct HTTP checks were not attempted under the owner-reported sandbox restriction: zero measured HTTP 200 responses, with statuses unmeasured. The DQV dated publication pin remains unresolved; NIST Privacy Framework 1.0 is a historical pinned edition, not a latest-version claim.", "Adopting profiles must pin neighbor versions, processing purpose, grants, retention and erasure authority, release review, atomicity and retry contracts. No universal duplicate threshold, precedence rule, summary acceptance score or jurisdiction-specific legal basis is established.", "Executable nested instance schemas, PROV-O and DQV mappings, store and index adapters, empirical quality evaluation and adversarial acceptance fixtures remain unimplemented. Research schema validation does not certify operational behavior, factual accuracy or compliance.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Run the prepared source checker outside the sandbox and verify cited editions, dated DQV pin, errata, applicability and reuse terms independently.", "Build nested schemas and pinned bindings with acceptance cases for context-sensitive duplicates, contradictory evidence, missing qualifications, permission conflicts, stale revisions, partial receipts and erased inputs.", "Evaluate false merges, unsupported summary claims, information loss and dependency reconciliation against purpose-specific datasets before operational use.", "Restore independent external review before considering any canonical or publishable-draft promotion." ] }, "statistics": { "sources": 8, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }