{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-mem-001","code":"wm-mem-001-memory-store","url":"https://ver.cy/models/wm-mem-001-memory-store/","name":"Memory Store","alternateNames":[],"kind":"world-model","status":"published","version":"0.1.0-reviewable-draft","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"entity","plane":"","domain":["INF.MEM.STO"],"industry":["Cross-industry"],"navPath":"NAV.INF.MEM.STO","tags":["memory","store","inf.mem.sto"],"facets":{}},"whatItIs":"A persistent identity for a logical memory store, including stores configured for temporary contents. The root is independent of physical storage, item identities, retrieval indexes and consuming agents. This is a proposed research model with local operation contracts, not an implemented storage system or a claim of cognitive memory.","purpose":"Describe one governed logical store of agent memory with explicit identity, custody, scope, tenancy, release and retention obligations.","scope":{"in":["Stable store identity, admitted memory classes, custody, purpose and tenant boundaries","Membership references, admission evidence, grants, release eligibility and revision control","Store lifecycle, observed service properties, retention bindings, disposal progress, portability and assurance"],"out":["Memory item content schemas, learned procedures, model weights, biological memory and hardware memory","Retrieval ranking algorithms, embedding implementation, truth adjudication, context assembly and autonomous agent execution","Physical backend implementation, cryptographic key material, legal determinations and operational security attack procedures"],"boundaries":[{"neighbor":"WM-DAT-001 Dataset","distinction":"Registry parent is qualified ALIGN only. A managed store is not identical to a catalogued dataset, service, distribution or physical database."},{"neighbor":"WM-MEM-002 Memory Item","distinction":"Items retain distinct identity, content, validity and provenance. Store membership is a reference with its own revision, not ownership of the item master."},{"neighbor":"WM-MEM-006 Memory Formation Event; WM-MEM-008 Memory Consolidation","distinction":"Formation and consolidation events explain membership or derived items; their event and transformation details remain external."},{"neighbor":"WM-MEM-007 Memory Recall Event; WM-MEM-013 Context Assembly","distinction":"Recall and context assembly record retrieval and downstream use; store release eligibility alone cannot establish either event."},{"neighbor":"WM-MEM-010 Memory Retention and Forgetting Policy; WM-MEM-011 Memory Scope and Sharing Grant","distinction":"Store-level bindings apply externally mastered policy and grant revisions. Their full lifecycles are not redefined here."},{"neighbor":"WM-MEM-012 Memory Portability Package; WM-MEM-014 Retrieval Index","distinction":"Packages and indexes are derivative resources with distinct identities, revisions and disposal obligations; neither is the store master."},{"neighbor":"WM-MEM-009 Memory Conflict and Precedence Rule; WM-MEM-017 Context Policy","distinction":"Content conflict resolution and context precedence are external. This store controls policy admission and release without declaring which stored assertion is true."},{"neighbor":"WM-MEM-018 Memory Trust Assessment; WM-MEM-019 Memory Poisoning Incident; WM-MEM-020 Memory Quarantine and Redaction","distinction":"Trust, incident and quarantine masters remain external. Only eligibility decisions, restricted references and policy-level obligations belong here."}]},"distinguishingFeatures":["Unlike WM-DAT-001 Dataset: Registry parent is qualified ALIGN only. A managed store is not identical to a catalogued dataset, service, distribution or physical database.","Unlike WM-MEM-002 Memory Item: Items retain distinct identity, content, validity and provenance. Store membership is a reference with its own revision, not ownership of the item master.","Unlike WM-MEM-006 Memory Formation Event; WM-MEM-008 Memory Consolidation: Formation and consolidation events explain membership or derived items; their event and transformation details remain external.","Unlike WM-MEM-007 Memory Recall Event; WM-MEM-013 Context Assembly: Recall and context assembly record retrieval and downstream use; store release eligibility alone cannot establish either event.","Unlike WM-MEM-010 Memory Retention and Forgetting Policy; WM-MEM-011 Memory Scope and Sharing Grant: Store-level bindings apply externally mastered policy and grant revisions. Their full lifecycles are not redefined here.","Unlike WM-MEM-012 Memory Portability Package; WM-MEM-014 Retrieval Index: Packages and indexes are derivative resources with distinct identities, revisions and disposal obligations; neither is the store master.","Unlike WM-MEM-009 Memory Conflict and Precedence Rule; WM-MEM-017 Context Policy: Content conflict resolution and context precedence are external. This store controls policy admission and release without declaring which stored assertion is true.","Unlike WM-MEM-018 Memory Trust Assessment; WM-MEM-019 Memory Poisoning Incident; WM-MEM-020 Memory Quarantine and Redaction: Trust, incident and quarantine masters remain external. Only eligibility decisions, restricted references and policy-level obligations belong here."],"structure":{"bundles":[{"id":"bundle-identity-governance","name":"Identity and governance","description":"Identify the logical resource and its accountable scope.","layers":[{"id":"layer-identity","name":"Store identity and classification","description":"Proposed root: one governed logical store with a stable master identity, independent of endpoint, physical backend, index or snapshot. A store may be empty and may hold multiple memory classes. Catalog metadata can describe its corpus and service separately.","findings":[{"id":"finding-identity","name":"Logical store identity","description":"Proposed root: one governed logical store with a stable master identity, independent of endpoint, physical backend, index or snapshot. A store may be empty and may hold multiple memory classes. Catalog metadata can describe its corpus and service separately.","questions":[{"text":"Which master identifier and namespace distinguish this store from its endpoints and snapshots?","id":"finding-identity-q1","kind":"identity"},{"text":"Which memory classes and persistence profile does the store admit?","id":"finding-identity-q2","kind":"classification"},{"text":"How is the store related to catalogued datasets without equating the store to a distribution?","id":"finding-identity-q3","kind":"relationship"},{"text":"When does a split or merger create a new store identity instead of a revision?","id":"finding-identity-q4","kind":"exception"}]}]},{"id":"layer-custody","name":"Accountability and operational scope","description":"Proposed responsibilities separate accountable steward, storage custodian, delegated agent and data subject. Control of infrastructure does not confer ownership of every memory. Scope can be personal, session, project or shared, with explicit purpose and tenancy boundaries.","findings":[{"id":"finding-custody","name":"Custody and purpose boundary","description":"Proposed responsibilities separate accountable steward, storage custodian, delegated agent and data subject. Control of infrastructure does not confer ownership of every memory. Scope can be personal, session, project or shared, with explicit purpose and tenancy boundaries.","questions":[{"text":"Who is accountable for this store and which custodians have only delegated operational duties?","id":"finding-custody-q1","kind":"ownership"},{"text":"Which purposes and scope classes justify persistence in this store?","id":"finding-custody-q2","kind":"definition"},{"text":"Which residency and tenant boundaries apply to payloads and derived copies?","id":"finding-custody-q3","kind":"constraint"},{"text":"What evidence permits a transfer of custody without silently expanding access?","id":"finding-custody-q4","kind":"authority"}]}]}]},{"id":"bundle-membership-admission","name":"Membership and admission","description":"Describe what belongs to the store and how admission is governed.","layers":[{"id":"layer-membership","name":"Membership and lineage","description":"Proposed membership records bind a store revision to separately identified memory items and their revisions. Membership does not transfer the item master or imply its factual correctness. Removal from this store is distinct from erasing every copy elsewhere.","findings":[{"id":"finding-membership","name":"Referenced membership revisions","description":"Proposed membership records bind a store revision to separately identified memory items and their revisions. Membership does not transfer the item master or imply its factual correctness. Removal from this store is distinct from erasing every copy elsewhere.","questions":[{"text":"Which item identities and revisions belong to the declared store view?","id":"finding-membership-q1","kind":"composition"},{"text":"Which times describe membership validity and which describe recording or observation?","id":"finding-membership-q2","kind":"temporal"},{"text":"What formation or import evidence explains each membership addition?","id":"finding-membership-q3","kind":"provenance"},{"text":"How are empty membership and an incompletely enumerated membership distinguished?","id":"finding-membership-q4","kind":"quality"}]}]},{"id":"layer-admission","name":"Admission and trust boundary","description":"Proposed admission checks validate the declared item profile, provenance and authority before membership is accepted. Untrusted memory content is data and cannot modify control policy. Quarantine and trust assessments retain external identities; a failed check does not imply that a claim is false.","findings":[{"id":"finding-admission","name":"Admission and quarantine routing","description":"Proposed admission checks validate the declared item profile, provenance and authority before membership is accepted. Untrusted memory content is data and cannot modify control policy. Quarantine and trust assessments retain external identities; a failed check does not imply that a claim is false.","questions":[{"text":"Which schema and provenance checks are required before an item is admitted?","id":"finding-admission-q1","kind":"validation"},{"text":"How are untrusted instructions prevented from becoming store control policy?","id":"finding-admission-q2","kind":"security"},{"text":"Which admission states distinguish pending review from accepted or rejected membership?","id":"finding-admission-q3","kind":"state"},{"text":"Which quarantine and trust assessment references govern reconsideration?","id":"finding-admission-q4","kind":"relationship"}]}]}]},{"id":"bundle-access-release","name":"Access and release","description":"Bind access decisions and release obligations to current policy.","layers":[{"id":"layer-grants","name":"Access and sharing","description":"Proposed access evaluates tenant, authenticated subject, purpose, resource scope, action, current grant version and item restrictions. Store membership never grants access by itself. Policy conflicts or unavailable authority evidence produce a denied or indeterminate decision, with no release until resolved.","findings":[{"id":"finding-grants","name":"Effective grant evaluation","description":"Proposed access evaluates tenant, authenticated subject, purpose, resource scope, action, current grant version and item restrictions. Store membership never grants access by itself. Policy conflicts or unavailable authority evidence produce a denied or indeterminate decision, with no release until resolved.","questions":[{"text":"Which current grants authorize a particular subject and action in this tenant?","id":"finding-grants-q1","kind":"access"},{"text":"How do store restrictions and item restrictions combine for a requested view?","id":"finding-grants-q2","kind":"constraint"},{"text":"What is returned when grants conflict or the policy service is unavailable?","id":"finding-grants-q3","kind":"exception"},{"text":"How are existence clues in identifiers and membership counts limited for unauthorized readers?","id":"finding-grants-q4","kind":"privacy"}]}]},{"id":"layer-recall","name":"Recall and derived views","description":"Proposed store release checks current eligibility even when a candidate was found through a stale index or cache. Retrieval, ranking, recall events and context assembly remain external. An authorized read does not authorize later sharing; revocation obligations and their completion evidence are tracked separately.","findings":[{"id":"finding-recall","name":"Release eligibility and revocation","description":"Proposed store release checks current eligibility even when a candidate was found through a stale index or cache. Retrieval, ranking, recall events and context assembly remain external. An authorized read does not authorize later sharing; revocation obligations and their completion evidence are tracked separately.","questions":[{"text":"At which boundary is current eligibility checked before a candidate leaves the store?","id":"finding-recall-q1","kind":"process"},{"text":"Which index and recall references identify a derived retrieval path without becoming the master?","id":"finding-recall-q2","kind":"relationship"},{"text":"How does revocation reach cached views and outstanding release requests?","id":"finding-recall-q3","kind":"lifecycle"},{"text":"What distinguishes a candidate match from an item actually released or used in a context?","id":"finding-recall-q4","kind":"evidence"}]}]}]},{"id":"bundle-change-continuity","name":"Change and continuity","description":"Distinguish revision, state, observation and recovery evidence.","layers":[{"id":"layer-revision","name":"Mutation and revision control","description":"Proposed configuration and membership mutations require a current revision precondition and an authorized actor. Repeated requests have explicit outcome records. HTTP If-Match is one possible representation binding; it is neither a global lock nor a universal transaction protocol.","findings":[{"id":"finding-revision","name":"Conditional configuration mutation","description":"Proposed configuration and membership mutations require a current revision precondition and an authorized actor. Repeated requests have explicit outcome records. HTTP If-Match is one possible representation binding; it is neither a global lock nor a universal transaction protocol.","questions":[{"text":"Which revision and authority must a mutation present before it can be accepted?","id":"finding-revision-q1","kind":"requirement"},{"text":"How is an accepted mutation distinguished from a rejected or uncertain request?","id":"finding-revision-q2","kind":"event"},{"text":"How are concurrent conflicting updates and repeated request identifiers handled?","id":"finding-revision-q3","kind":"exception"},{"text":"Which evidence links a new revision to its predecessor and responsible operation?","id":"finding-revision-q4","kind":"provenance"}]}]},{"id":"layer-lifecycle","name":"Availability and continuity","description":"Proposed lifecycle states distinguish planned, active, read-only, suspended, retiring and retired stores; the state list is local. Health observations and recovery objectives are distinct from measured recovery outcomes. Restores must reconcile later erasures and revoked grants before any release resumes.","findings":[{"id":"finding-lifecycle","name":"Store state and recovery evidence","description":"Proposed lifecycle states distinguish planned, active, read-only, suspended, retiring and retired stores; the state list is local. Health observations and recovery objectives are distinct from measured recovery outcomes. Restores must reconcile later erasures and revoked grants before any release resumes.","questions":[{"text":"Which transitions are authorized from the current store state and who may approve them?","id":"finding-lifecycle-q1","kind":"lifecycle"},{"text":"Which observation supports the reported capacity and availability at a given time?","id":"finding-lifecycle-q2","kind":"measurement"},{"text":"Which recovery point and recovery time objectives have tested evidence?","id":"finding-lifecycle-q3","kind":"requirement"},{"text":"How does a restored snapshot reconcile later deletions and revocations before reopening?","id":"finding-lifecycle-q4","kind":"security"}]}]}]},{"id":"bundle-retention-disposal","name":"Retention and disposal","description":"Separate retention authority from proof of bounded disposal.","layers":[{"id":"layer-retention","name":"Retention and forgetting","description":"Proposed store configuration binds versioned external retention policies and determines which item classes they govern. Expiry, exclusion from recall, erasure request and completed disposal are distinct states. Holds need scope, authority, expiry or review date; they do not authorize ordinary use of retained payloads.","findings":[{"id":"finding-retention","name":"Retention obligations and exceptions","description":"Proposed store configuration binds versioned external retention policies and determines which item classes they govern. Expiry, exclusion from recall, erasure request and completed disposal are distinct states. Holds need scope, authority, expiry or review date; they do not authorize ordinary use of retained payloads.","questions":[{"text":"Which retention policy revision applies to each membership class and copy category?","id":"finding-retention-q1","kind":"retention"},{"text":"What event starts the retention period and how is an unknown start handled?","id":"finding-retention-q2","kind":"temporal"},{"text":"Which authority can impose or release a scoped retention hold?","id":"finding-retention-q3","kind":"authority"},{"text":"How are conflicting retention and erasure requirements referred for resolution?","id":"finding-retention-q4","kind":"exception"}]}]},{"id":"layer-disposal","name":"Disposal and propagation","description":"Proposed disposal tracks the declared copy inventory, including derived indexes, summaries, replicas and backups. A tombstone or missing search result is not proof of erasure. Minimal lawful evidence may survive under its own policy, while payload history remains subject to disposal. Unreachable copies keep the result incomplete.","findings":[{"id":"finding-disposal","name":"Evidence of bounded erasure","description":"Proposed disposal tracks the declared copy inventory, including derived indexes, summaries, replicas and backups. A tombstone or missing search result is not proof of erasure. Minimal lawful evidence may survive under its own policy, while payload history remains subject to disposal. Unreachable copies keep the result incomplete.","questions":[{"text":"Which payloads and derived copies are included in a disposal request?","id":"finding-disposal-q1","kind":"retention"},{"text":"What evidence demonstrates completion for each in-scope copy category?","id":"finding-disposal-q2","kind":"evidence"},{"text":"How are unreachable replicas and unexpired backup schedules reported?","id":"finding-disposal-q3","kind":"exception"},{"text":"What minimal tombstone may remain without retaining erased content or unnecessary identifiers?","id":"finding-disposal-q4","kind":"privacy"}]}]}]},{"id":"bundle-exchange-assurance","name":"Exchange and assurance","description":"Describe portability, explicit losses and scoped assurance.","layers":[{"id":"layer-portability","name":"Portability and storage bindings","description":"Proposed store metadata binds versioned interfaces and optional export packages without selecting a commercial backend. Transfer records preserve source identity, provenance, policy obligations and migration losses. Checksums establish byte consistency only; imports require semantic and authority review before admission.","findings":[{"id":"finding-portability","name":"Transfer and migration boundaries","description":"Proposed store metadata binds versioned interfaces and optional export packages without selecting a commercial backend. Transfer records preserve source identity, provenance, policy obligations and migration losses. Checksums establish byte consistency only; imports require semantic and authority review before admission.","questions":[{"text":"Which versioned schema and interface bindings support a portable store view?","id":"finding-portability-q1","kind":"interoperability"},{"text":"Which portability package represents the selected revision and permitted export scope?","id":"finding-portability-q2","kind":"composition"},{"text":"Which checks separate byte integrity from identity mapping and policy compatibility?","id":"finding-portability-q3","kind":"validation"},{"text":"Which migration losses or inaccessible references prevent automatic import?","id":"finding-portability-q4","kind":"exception"}]}]},{"id":"layer-assurance","name":"Assurance and evidence","description":"Proposed assurance claims name the assessed store revision, tenant scope, test method and unresolved failures. Audit references protect sensitive payloads through minimized records and separate access. No assertion of correct recall, universal memory quality or compliance follows from a structurally valid catalog package.","findings":[{"id":"finding-assurance","name":"Scoped audit and acceptance claims","description":"Proposed assurance claims name the assessed store revision, tenant scope, test method and unresolved failures. Audit references protect sensitive payloads through minimized records and separate access. No assertion of correct recall, universal memory quality or compliance follows from a structurally valid catalog package.","questions":[{"text":"Which revision and tenant scope does an assurance statement actually cover?","id":"finding-assurance-q1","kind":"evidence"},{"text":"Which acceptance cases test empty stores, revoked grants and incomplete erasure?","id":"finding-assurance-q2","kind":"validation"},{"text":"Who can inspect or administer audit evidence independently of store payload access?","id":"finding-assurance-q3","kind":"access"},{"text":"Which uncertainties limit any claim that the store is ready for operational use?","id":"finding-assurance-q4","kind":"quality"}]}]}]}]},"agentConduct":{"may":["Register a store description: Proposed, unimplemented operation. Create a proposed local store record without provisioning storage.","Assess a membership proposal: Proposed, unimplemented operation. Produce a local admission assessment for a separately mastered item.","Evaluate a release request: Proposed, unimplemented operation. Evaluate the current permitted projection before any downstream release.","Record a conditional metadata mutation: Proposed, unimplemented operation. Propose a revision change with explicit concurrency and retry outcomes.","Assess disposal completion: Proposed, unimplemented operation. Reconcile external disposal receipts against a declared copy inventory.","Assess transfer compatibility: Proposed, unimplemented operation. Assess an optional portability package before a separately authorized import."],"mustNot":["Default deny when tenant, purpose, grant or policy applicability is unresolved.","Memory content cannot alter these controls.","Deny by default across tenant and purpose boundaries; an indeterminate policy decision releases nothing."],"requiresHuman":[]},"ethics":{"considerations":["No jurisdiction-specific privacy or retention determination, legal deadlines or compliance certification."],"affectedParties":[]},"owners":{"steward":"Name an accountable steward by role or local identity, not a brand owner.","roles":[{"name":"Accountable steward","responsibilities":["Approve scope, policy bindings and custody transitions; resolve responsibilities without claiming ownership of all content."]},{"name":"Storage custodian","responsibilities":["Maintain declared storage bindings, copy inventory and continuity evidence under delegated authority."]},{"name":"Memory curator","responsibilities":["Propose admission, correction and quarantine referrals with provenance; cannot grant itself access."]},{"name":"Policy administrator","responsibilities":["Manage authorized grants and retention bindings, separate from ordinary payload use."]},{"name":"Authorized consumer","responsibilities":["Request only permitted projections for an approved purpose; respect downstream limits."]},{"name":"Assurance reviewer","responsibilities":["Inspect scoped evidence and unresolved failures under separately granted audit access."]}],"masterSystems":[]},"relations":[{"target":"WM-DAT-001","type":"aligned","note":"Candidate catalog alignment from registry parent; no inherited schema or runtime dependency. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-002","type":"references","note":"Optional zero-to-many membership; item identities and content remain external. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-006","type":"references","note":"Optional formation evidence for admissions. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-008","type":"references","note":"Optional consolidation lineage for derived members. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-007","type":"references","note":"Optional recall event evidence; release is not equivalent to recall or use. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-010","type":"references","note":"Candidate retention policy model binding; an effective retention policy is required but adoption of this registry model is not. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-011","type":"references","note":"Candidate sharing grant binding; no grant and no authority means no access. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-012","type":"references","note":"Optional portability package with its own identity and lifecycle. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-014","type":"references","note":"Optional derived index; current item and policy masters remain authoritative. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-013","type":"references","note":"Optional downstream context assembly evidence, not store containment. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-018","type":"references","note":"Optional externally mastered trust assessments. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-MEM-020","type":"references","note":"Optional quarantine and redaction evidence without duplicating the workflow. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance."},{"target":"WM-DAT-001 Dataset","type":"neighbor","note":"Registry parent is qualified ALIGN only. A managed store is not identical to a catalogued dataset, service, distribution or physical database."},{"target":"WM-MEM-002 Memory Item","type":"neighbor","note":"Items retain distinct identity, content, validity and provenance. Store membership is a reference with its own revision, not ownership of the item master."},{"target":"WM-MEM-006 Memory Formation Event; WM-MEM-008 Memory Consolidation","type":"neighbor","note":"Formation and consolidation events explain membership or derived items; their event and transformation details remain external."},{"target":"WM-MEM-007 Memory Recall Event; WM-MEM-013 Context Assembly","type":"neighbor","note":"Recall and context assembly record retrieval and downstream use; store release eligibility alone cannot establish either event."},{"target":"WM-MEM-010 Memory Retention and Forgetting Policy; WM-MEM-011 Memory Scope and Sharing Grant","type":"neighbor","note":"Store-level bindings apply externally mastered policy and grant revisions. Their full lifecycles are not redefined here."},{"target":"WM-MEM-012 Memory Portability Package; WM-MEM-014 Retrieval Index","type":"neighbor","note":"Packages and indexes are derivative resources with distinct identities, revisions and disposal obligations; neither is the store master."},{"target":"WM-MEM-009 Memory Conflict and Precedence Rule; WM-MEM-017 Context Policy","type":"neighbor","note":"Content conflict resolution and context precedence are external. This store controls policy admission and release without declaring which stored assertion is true."},{"target":"WM-MEM-018 Memory Trust Assessment; WM-MEM-019 Memory Poisoning Incident; WM-MEM-020 Memory Quarantine and Redaction","type":"neighbor","note":"Trust, incident and quarantine masters remain external. Only eligibility decisions, restricted references and policy-level obligations belong here."},{"target":"WM-DAT-001","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier plus revision","Namespace-qualified stable local identifier plus revision when no master exists","Digest of a declared byte representation as integrity evidence only"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":[]},"capabilities":{"applicability":"required","items":["Register a store description: Proposed, unimplemented operation. Create a proposed local store record without provisioning storage.","Assess a membership proposal: Proposed, unimplemented operation. Produce a local admission assessment for a separately mastered item.","Evaluate a release request: Proposed, unimplemented operation. Evaluate the current permitted projection before any downstream release.","Record a conditional metadata mutation: Proposed, unimplemented operation. Propose a revision change with explicit concurrency and retry outcomes.","Assess disposal completion: Proposed, unimplemented operation. Reconcile external disposal receipts against a declared copy inventory.","Assess transfer compatibility: Proposed, unimplemented operation. Assess an optional portability package before a separately authorized import."]},"hazards":{"applicability":"optional","items":[]},"interfaces":{"applicability":"required","items":["Data Catalog Vocabulary (DCAT) - Version 3","PROV-O: The PROV Ontology","NIST SP 800-53 Revision 5: Security and Privacy Controls for Information Systems and Organizations","RFC 9110: HTTP Semantics","RFC 8493: The BagIt File Packaging Format (V1.0)","RFC 3339: Date and Time on the Internet: Timestamps"]},"context":{"applicability":"required","items":["No jurisdiction is selected. The cited NIST publication supplies adaptable control concepts, not a universal legal obligation.","Residency, rights, retention, disclosure and emergency-access authority require qualified local profiles."]}},"sources":[{"title":"Data Catalog Vocabulary (DCAT) - Version 3","url":"https://www.w3.org/TR/vocab-dcat-3/","note":"W3C"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"W3C"},{"title":"ODRL Information Model 2.2","url":"https://www.w3.org/TR/odrl-model/","note":"W3C"},{"title":"NIST SP 800-53 Revision 5: Security and Privacy Controls for Information Systems and Organizations","url":"https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf","note":"NIST"},{"title":"RFC 9110: HTTP Semantics","url":"https://www.rfc-editor.org/rfc/rfc9110.html","note":"IETF"},{"title":"RFC 8493: The BagIt File Packaging Format (V1.0)","url":"https://www.rfc-editor.org/rfc/rfc8493.html","note":"RFC Editor Independent Submission"},{"title":"RFC 3339: Date and Time on the Internet: Timestamps","url":"https://www.rfc-editor.org/rfc/rfc3339.html","note":"IETF"}],"openQuestions":["Restore independent external review before canonical or publishable-draft promotion.","Run the coordinator source checker and verify applicable versions, errata, selected claims and source licensing separately from HTTP success.","Develop qualified adoption profiles and nested schemas, then execute the scoped acceptance cases for revocation, tenant isolation, mutation races, erasure propagation, restore and migration losses.","No formal agent-memory ontology or cognitive equivalence claim.","Nested schemas, code lists, tenant partition proofs, distributed consistency, replication and recovery implementations are not provided.","No claim of universal erasure across uncontrolled downstream systems; copy scope and residuals must be declared.","No jurisdiction-specific privacy or retention determination, legal deadlines or compliance certification.","Independent external review and full source/version/errata verification remain outstanding.","Operational tests for stale indexes, revocation races, cross-tenant metadata leakage, replay, restore-after-erasure and lossy migration remain to be executed."],"resources":{"spec":"/models/wm-mem-001-memory-store/spec.yaml","agents":"/models/wm-mem-001-memory-store/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-mem-001"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-mem-001-memory-store/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-21T15:46:50Z","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}}