{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-mem-008","code":"wm-mem-008-memory-consolidation","url":"https://ver.cy/models/wm-mem-008-memory-consolidation/","name":"Memory Consolidation","alternateNames":[],"kind":"world-model","status":"published","version":"0.1.0-reviewable-draft","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"event","plane":"","domain":["INF.MEM.CNS"],"industry":["Cross-industry"],"navPath":"NAV.INF.MEM.CNS","tags":["memory","consolidation","inf.mem.cns"],"facets":{}},"whatItIs":"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.","purpose":"Describe a bounded attempt to merge duplicate memory records, produce a summary or request retirement, with traceable inputs, decisions and observed outcomes.","scope":{"in":["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":["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."],"boundaries":[{"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."},{"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."},{"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."},{"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."},{"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."},{"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."},{"neighbor":"WM-MEM-014 Retrieval Index","distinction":"Record required refresh and invalidation receipt references only; the external index owns update, caching and recall visibility."},{"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."}]},"distinguishingFeatures":["Unlike WM-MEM-002 Memory Item: 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.","Unlike WM-MEM-001 Memory Store: The store owns transactional mutation and authoritative receipts. This record tracks proposals and outcomes without claiming to execute store operations.","Unlike WM-MEM-006 Memory Formation Event: 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.","Unlike WM-MEM-009 Memory Conflict and Precedence Rule: Record unresolved conflict and a pinned external ruling; do not invent precedence or use recency alone to resolve truth.","Unlike WM-MEM-010 Memory Retention and Forgetting Policy: Bind policy and receipt references. Retirement from active use, deletion of payload and expiry of local evidence are separate decisions.","Unlike WM-MEM-011 Memory Scope and Sharing Grant: Reference permission decisions for each input and derived output. Reading two inputs does not authorize sharing their combination.","Unlike WM-MEM-014 Retrieval Index: Record required refresh and invalidation receipt references only; the external index owns update, caching and recall visibility.","Unlike WM-MEM-018 Memory Trust Assessment and WM-MEM-020 Memory Quarantine and Redaction: Treat risk assessments and quarantine/redaction decisions as external bindings. Consolidation cannot upgrade trust by repeating or compressing a claim."],"structure":{"bundles":[{"id":"intent-inputs","name":"Intent and inputs","description":"Bind an attempt to its purpose and exact candidate revisions.","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.","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.","questions":[{"text":"Which master identifier distinguishes this attempt from its request and any retry?","id":"run-identity-q1","kind":"identity"},{"text":"Which operation is proposed: duplicate merge, summary, retirement, or an explicit combination?","id":"run-identity-q2","kind":"classification"},{"text":"Which role owns the consolidation record and its allowed namespace?","id":"run-identity-q3","kind":"ownership"},{"text":"What are the recorded start, end and observation times, including unknown values?","id":"run-identity-q4","kind":"temporal"}]}]},{"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.","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.","questions":[{"text":"Which item revisions are included and which candidates were excluded?","id":"input-snapshot-q1","kind":"composition"},{"text":"How was the candidate set selected and at which source snapshot?","id":"input-snapshot-q2","kind":"provenance"},{"text":"What must happen if an input revision changes or becomes unavailable before application?","id":"input-snapshot-q3","kind":"constraint"},{"text":"Which representation and digest support each snapshot without equating content with identity?","id":"input-snapshot-q4","kind":"evidence"}]}]}]},{"id":"merge-decisions","name":"Merge decisions","description":"Make duplicate and contradiction decisions inspectable.","layers":[{"id":"duplicate-basis-layer","name":"Duplicate equivalence assessment context","description":"Local research context for duplicate equivalence assessment; external masters retain delegated operations.","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.","questions":[{"text":"What equivalence criterion is used for this candidate duplicate set?","id":"duplicate-basis-q1","kind":"definition"},{"text":"How were similarity or equality results measured and qualified?","id":"duplicate-basis-q2","kind":"measurement"},{"text":"Which contextual differences prevent these records from being merged?","id":"duplicate-basis-q3","kind":"exception"},{"text":"Who accepted, rejected or deferred the equivalence proposal and why?","id":"duplicate-basis-q4","kind":"decision"}]}]},{"id":"conflict-routing-layer","name":"Contradiction and precedence binding context","description":"Local research context for contradiction and precedence binding; external masters retain delegated operations.","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.","questions":[{"text":"Which input assertions conflict and which external rule owns their resolution?","id":"conflict-routing-q1","kind":"relationship"},{"text":"What external decision permits a preferred assertion in this specific scope?","id":"conflict-routing-q2","kind":"authority"},{"text":"Which disputed values remain unresolved in the proposed result?","id":"conflict-routing-q3","kind":"state"},{"text":"How is dissent preserved when a proposal proceeds on uncontested inputs?","id":"conflict-routing-q4","kind":"constraint"}]}]}]},{"id":"derived-content","name":"Derived content and lineage","description":"Describe a proposed summary and its derivation.","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.","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.","questions":[{"text":"Which method, instruction revision and parameters produced the summary proposal?","id":"summary-fidelity-q1","kind":"process"},{"text":"Which input spans support each retained summary assertion?","id":"summary-fidelity-q2","kind":"evidence"},{"text":"What information was omitted or distorted relative to the stated purpose?","id":"summary-fidelity-q3","kind":"quality"},{"text":"What evidence permits approval or requires rejection of the summary?","id":"summary-fidelity-q4","kind":"validation"}]}]},{"id":"lineage-map-layer","name":"Derivation and identity continuity context","description":"Local research context for derivation and identity continuity; external masters retain delegated operations.","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.","questions":[{"text":"Which input-to-output edges explain the transformation and responsible agent?","id":"lineage-map-q1","kind":"provenance"},{"text":"Which output identity is new, retained or an authorized alias of an existing item?","id":"lineage-map-q2","kind":"identity"},{"text":"Does the mapped lineage satisfy the applicable usage, generation and invalidation ordering?","id":"lineage-map-q3","kind":"temporal"},{"text":"What mapping and loss report accompany a PROV-O projection?","id":"lineage-map-q4","kind":"interoperability"}]}]}]},{"id":"controlled-application","name":"Controlled application","description":"Capture authority and externally evidenced change outcomes.","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.","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.","questions":[{"text":"Which principals may read each input and the derived output for this purpose?","id":"approval-gate-q1","kind":"access"},{"text":"Which role may approve the proposal and what separation of duties applies?","id":"approval-gate-q2","kind":"authority"},{"text":"What sensitive information or inference requires redaction or a narrower output scope?","id":"approval-gate-q3","kind":"privacy"},{"text":"How are embedded instructions and quarantined inputs treated during consolidation review?","id":"approval-gate-q4","kind":"security"}]}]},{"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.","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.","questions":[{"text":"Which external store operation is bound to the approved proposal revision?","id":"application-receipts-q1","kind":"process"},{"text":"What conditional-write and atomicity contract applies to this change set?","id":"application-receipts-q2","kind":"constraint"},{"text":"Which authoritative receipts identify applied, refused or unknown item outcomes?","id":"application-receipts-q3","kind":"event"},{"text":"How are retries and partial application reconciled without duplicate outputs?","id":"application-receipts-q4","kind":"exception"}]}]}]},{"id":"disposition-impact","name":"Disposition and downstream impact","description":"Track retirement requests and dependent visibility.","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.","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.","questions":[{"text":"Which source items are proposed for retirement and what replacement references remain?","id":"retirement-disposition-q1","kind":"lifecycle"},{"text":"Which policy revision and applicable hold govern each proposed disposition?","id":"retirement-disposition-q2","kind":"retention"},{"text":"What external receipt distinguishes retirement, redaction and completed deletion?","id":"retirement-disposition-q3","kind":"evidence"},{"text":"What local lineage metadata may be retained after payload erasure?","id":"retirement-disposition-q4","kind":"privacy"}]}]},{"id":"downstream-effects-layer","name":"Dependent copies and visibility context","description":"Local research context for dependent copies and visibility; external masters retain delegated operations.","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.","questions":[{"text":"Which dependent records and retrieval surfaces reference affected item revisions?","id":"downstream-effects-q1","kind":"relationship"},{"text":"Which refresh or restriction acknowledgments are required before declaring the run reconciled?","id":"downstream-effects-q2","kind":"requirement"},{"text":"Which downstream surfaces remain stale or have unknown disposition?","id":"downstream-effects-q3","kind":"state"},{"text":"How are inaccessible or offline dependencies reported without claiming global completion?","id":"downstream-effects-q4","kind":"exception"}]}]}]},{"id":"recovery-assurance","name":"Recovery and assurance","description":"Record correction proposals and acceptance evidence.","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.","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.","questions":[{"text":"What defect or later evidence triggered correction of a completed consolidation?","id":"correction-recovery-q1","kind":"event"},{"text":"Which compensating proposal addresses the defect under current authority?","id":"correction-recovery-q2","kind":"process"},{"text":"Which effects are reversible and which cannot be restored?","id":"correction-recovery-q3","kind":"constraint"},{"text":"What external evidence confirms corrected lineage and downstream reconciliation?","id":"correction-recovery-q4","kind":"validation"}]}]},{"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.","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.","questions":[{"text":"Which metrics and denominators measure consolidation quality for this profile?","id":"evaluation-evidence-q1","kind":"measurement"},{"text":"Which edge cases were assessed and what limitations remain?","id":"evaluation-evidence-q2","kind":"quality"},{"text":"What profile thresholds and reviewer evidence justify accepting this run?","id":"evaluation-evidence-q3","kind":"decision"},{"text":"Which schema and reference checks must an adopting implementation demonstrate?","id":"evaluation-evidence-q4","kind":"interoperability"}]}]}]}]},"agentConduct":{"may":["Register consolidation attempt: Create a local declaration and input manifest without executing any store mutation. Proposed local operation only; no implementation is supplied.","Record duplicate assessment: Store a reviewer-supported equivalence proposal; this operation is not an equivalence or trust engine. Proposed local operation only; no implementation is supplied.","Record summary proposal: 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.","Record release decision: Record approval or rejection for an exact proposal and output audience. Proposed local operation only; no implementation is supplied.","Reconcile external outcomes: Record authenticated external receipts and classify the local activity outcome. Proposed local operation only; no implementation is supplied.","Record correction proposal: Link a new proposed compensating activity and later evidence to a defective run. Proposed local operation only; no implementation is supplied."],"mustNot":["Never treat compression, repetition, confidence scores or provenance presence as proof of a claim.","Referenced item retirement or deletion is executed by the external store under WM-MEM-010 policy, never by deletion of this event record.","Deny by default."],"requiresHuman":[]},"ethics":{"considerations":["Dangerous content remains at policy level; this model records controls and decisions, not operational harmful instructions."],"affectedParties":[]},"owners":{"steward":"An accountable memory operator role owns the namespace and declares processing purposes.","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."]}],"masterSystems":[]},"relations":[{"target":"WM-MEM-001","type":"references","note":"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."},{"target":"WM-MEM-002","type":"references","note":"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."},{"target":"WM-MEM-006","type":"references","note":"Link output formation events where separately recorded. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted."},{"target":"WM-MEM-009","type":"references","note":"Bind a scope-specific conflict ruling without authoring precedence. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted."},{"target":"WM-MEM-010","type":"references","note":"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."},{"target":"WM-MEM-011","type":"references","note":"Bind processing and output sharing decisions without minting grants. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted."},{"target":"WM-MEM-014","type":"references","note":"Reference index refresh and invalidation receipts without implementing retrieval. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted."},{"target":"WM-MEM-018","type":"references","note":"Reference source trust assessment without upgrading trust through consolidation. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted."},{"target":"WM-MEM-020","type":"references","note":"Reference quarantine and redaction decisions; processing remains policy limited. Candidate binding requiring an adoption profile and version pin; no mandatory co-instantiation is asserted."},{"target":"https://www.w3.org/TR/prov-o/","type":"aligned","note":"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."},{"target":"https://www.w3.org/TR/vocab-dqv/","type":"aligned","note":"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."},{"target":"WM-MEM-002 Memory Item","type":"neighbor","note":"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."},{"target":"WM-MEM-001 Memory Store","type":"neighbor","note":"The store owns transactional mutation and authoritative receipts. This record tracks proposals and outcomes without claiming to execute store operations."},{"target":"WM-MEM-006 Memory Formation Event","type":"neighbor","note":"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."},{"target":"WM-MEM-009 Memory Conflict and Precedence Rule","type":"neighbor","note":"Record unresolved conflict and a pinned external ruling; do not invent precedence or use recency alone to resolve truth."},{"target":"WM-MEM-010 Memory Retention and Forgetting Policy","type":"neighbor","note":"Bind policy and receipt references. Retirement from active use, deletion of payload and expiry of local evidence are separate decisions."},{"target":"WM-MEM-011 Memory Scope and Sharing Grant","type":"neighbor","note":"Reference permission decisions for each input and derived output. Reading two inputs does not authorize sharing their combination."},{"target":"WM-MEM-014 Retrieval Index","type":"neighbor","note":"Record required refresh and invalidation receipt references only; the external index owns update, caching and recall visibility."},{"target":"WM-MEM-018 Memory Trust Assessment and WM-MEM-020 Memory Quarantine and Redaction","type":"neighbor","note":"Treat risk assessments and quarantine/redaction decisions as external bindings. Consolidation cannot upgrade trust by repeating or compressing a claim."},{"target":"WM-MEM-002","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier","Governed global identifier or IRI","Dimension-assigned UUID or ULID"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":[]},"capabilities":{"applicability":"required","items":["Register consolidation attempt: Create a local declaration and input manifest without executing any store mutation. Proposed local operation only; no implementation is supplied.","Record duplicate assessment: Store a reviewer-supported equivalence proposal; this operation is not an equivalence or trust engine. Proposed local operation only; no implementation is supplied.","Record summary proposal: 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.","Record release decision: Record approval or rejection for an exact proposal and output audience. Proposed local operation only; no implementation is supplied.","Reconcile external outcomes: Record authenticated external receipts and classify the local activity outcome. Proposed local operation only; no implementation is supplied.","Record correction proposal: Link a new proposed compensating activity and later evidence to a defective run. Proposed local operation only; no implementation is supplied."]},"hazards":{"applicability":"optional","items":[]},"interfaces":{"applicability":"required","items":["PROV-O: The PROV Ontology","Constraints of the PROV Data Model","NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0"]},"context":{"applicability":"required","items":["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."]}},"sources":[{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"W3C"},{"title":"Constraints of the PROV Data Model","url":"https://www.w3.org/TR/prov-constraints/","note":"W3C"},{"title":"Data on the Web Best Practices: Data Quality Vocabulary","url":"https://www.w3.org/TR/vocab-dqv/","note":"W3C"},{"title":"JSON Canonicalization Scheme (JCS)","url":"https://www.rfc-editor.org/rfc/rfc8785","note":"RFC Editor"},{"title":"HTTP Semantics","url":"https://www.rfc-editor.org/rfc/rfc9110.html","note":"RFC Editor"},{"title":"Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile","url":"https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.600-1.pdf","note":"NIST"},{"title":"NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0","url":"https://nvlpubs.nist.gov/nistpubs/CSWP/NIST.CSWP.01162020.pdf","note":"NIST"},{"title":"Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"RFC Editor"}],"openQuestions":["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.","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."],"resources":{"spec":"/models/wm-mem-008-memory-consolidation/spec.yaml","agents":"/models/wm-mem-008-memory-consolidation/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-mem-008"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-mem-008-memory-consolidation/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-21T17:20:23Z","builder":"tools/build_cards.py@1.0.0"},"completeness":{"sections":{"classifiers":"filled","whatItIs":"filled","purpose":"filled","distinguishingFeatures":"derived","structure":"filled","agentConduct":"derived","ethics":"derived","owners":"filled","relations":"filled","interaction.identity":"filled","interaction.properties":"not-applicable","interaction.recognition":"missing","interaction.capabilities":"filled","interaction.hazards":"missing","interaction.interfaces":"derived","interaction.context":"filled","sources":"filled"},"notes":{"distinguishingFeatures":"Derived from boundary notes against neighbouring models.","agentConduct":"Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.","ethics":"Sentences mentioning harm, privacy, consent or similar, collected from the specification.","interaction.properties":"Institutional or informational subject: no invented physical properties."},"score":0.75}}