{"schema":"https://ver.cy/schemas/card/1.0.0","id":"vr.wm-mem-014","code":"wm-mem-014-retrieval-index","url":"https://ver.cy/models/wm-mem-014-retrieval-index/","name":"Retrieval Index","alternateNames":[],"kind":"world-model","status":"published","version":"0.1.0","language":"en","classifiers":{"family":"World Models","category":"Information and virtual systems","entryKind":"entity","plane":"","domain":["INF.MEM.IDX"],"industry":["Cross-industry"],"navPath":"NAV.INF.MEM.IDX","tags":["retrieval","index","inf.mem.idx"],"facets":{}},"whatItIs":"A persistent derived index entity with revisioned definitions and addressable generations. Lexical, vector and hybrid profiles are conditional. This research proposes context and local evidence-record operations, not an implemented search engine.","purpose":"Describe one governed retrieval index over a declared corpus, its representations, generation lineage, refresh evidence and serving constraints.","scope":{"in":["Logical index and generation identity; corpus membership and source revision references","Segmentation recipe and passage bindings; lexical analysis and conditional embedding compatibility","Refresh coverage, release receipts, access bindings, disposal evidence and evaluation references"],"out":["Source document, dataset and passage master lifecycles","Encoder training, embedding execution, search execution and distributed storage implementation","Recall-event history, context assembly, answer generation and grounding judgments","Policy authorship, access decision execution, incident handling and physical erasure execution","Universal chunk sizes, metric thresholds, conformance certification or production readiness"],"boundaries":[{"neighbor":"WM-DAT-001","distinction":"Registry parent is Dataset. Align catalog identity and distributions; the index specializes a derived resource and does not duplicate corpus ownership or dataset lifecycle."},{"neighbor":"WM-MEM-001","distinction":"Optional store and tenancy binding. Store operations, capacity and general retention are outside the index record."},{"neighbor":"WM-MEM-015","distinction":"Passage revisions remain independently mastered; index membership and locator references do not create a second passage lifecycle."},{"neighbor":"WM-MEM-007","distinction":"Recall-event owner records actual queries, rankings and use. This index supplies generation and capability references only."},{"neighbor":"WM-MEM-013","distinction":"Context assembly owns selected context and budgets; index configuration does not assert what was placed in a context."},{"neighbor":"WM-MEM-010","distinction":"Retention and forgetting policy owns disposition rules; index records affected derivatives and external execution receipts."},{"neighbor":"WM-MEM-011","distinction":"Scope and sharing grant owns authorization policy. Index labels and filters are projections, not grants."},{"neighbor":"WM-MEM-020","distinction":"Quarantine and redaction owner decides source restrictions; index binds suppression status without adjudicating the underlying incident."},{"neighbor":"WM-MEM-016","distinction":"Answer grounding owns claim-to-evidence support. Retrieval similarity is not a grounding verdict."},{"neighbor":"Encoder and storage bindings","distinction":"Embedding model revisions and backend formats are referenced. This index does not own model training or storage-service lifecycle."}]},"distinguishingFeatures":["Unlike WM-DAT-001: Registry parent is Dataset. Align catalog identity and distributions; the index specializes a derived resource and does not duplicate corpus ownership or dataset lifecycle.","Unlike WM-MEM-001: Optional store and tenancy binding. Store operations, capacity and general retention are outside the index record.","Unlike WM-MEM-015: Passage revisions remain independently mastered; index membership and locator references do not create a second passage lifecycle.","Unlike WM-MEM-007: Recall-event owner records actual queries, rankings and use. This index supplies generation and capability references only.","Unlike WM-MEM-013: Context assembly owns selected context and budgets; index configuration does not assert what was placed in a context.","Unlike WM-MEM-010: Retention and forgetting policy owns disposition rules; index records affected derivatives and external execution receipts.","Unlike WM-MEM-011: Scope and sharing grant owns authorization policy. Index labels and filters are projections, not grants.","Unlike WM-MEM-020: Quarantine and redaction owner decides source restrictions; index binds suppression status without adjudicating the underlying incident.","Unlike WM-MEM-016: Answer grounding owns claim-to-evidence support. Retrieval similarity is not a grounding verdict.","Unlike Encoder and storage bindings: Embedding model revisions and backend formats are referenced. This index does not own model training or storage-service lifecycle."],"structure":{"bundles":[{"id":"bundle-identity-corpus","name":"Identity and corpus","description":"Identify the derived resource and its declared source membership.","layers":[{"id":"layer-identity","name":"Index identity","description":"Index-specific context for logical index and generation identity.","findings":[{"id":"finding-identity","name":"Logical index and generation identity","description":"Proposed index identity persists across rebuilds; generation IDs identify frozen serving contents. Backend addresses, aliases and document ordinals are bindings, not authoritative identities.","questions":[{"text":"Which authoritative identifier names the logical index independently of its endpoint and active generation?","id":"finding-identity-q-1","kind":"identity"},{"text":"Which retrieval families and modalities does this index profile explicitly support?","id":"finding-identity-q-2","kind":"classification"},{"text":"Which generation is declared active and which generations are staged, superseded, failed or retired?","id":"finding-identity-q-3","kind":"lifecycle"},{"text":"Which accountable roles may change the index definition and authorize a generation transition?","id":"finding-identity-q-4","kind":"ownership"}]}]},{"id":"layer-corpus","name":"Corpus membership","description":"Index-specific context for versioned corpus selection.","findings":[{"id":"finding-corpus","name":"Versioned corpus selection","description":"Proposed manifest references eligible source revisions and explicit exclusions. The index is a derived access structure; source dataset ownership and source record lifecycles stay external. Empty approved corpora are valid.","questions":[{"text":"Which dataset revisions and source selection rules define this generation including an intentionally empty corpus?","id":"finding-corpus-q-1","kind":"composition"},{"text":"Which language, modality, licensing or collection restrictions exclude material from indexing?","id":"finding-corpus-q-2","kind":"constraint"},{"text":"How does each indexed member resolve to its source revision and ingestion evidence?","id":"finding-corpus-q-3","kind":"provenance"},{"text":"How are expected, included, excluded and failed members reconciled without claiming total corpus coverage?","id":"finding-corpus-q-4","kind":"quality"}]}]}]},{"id":"bundle-representation","name":"Passage and lexical representation","description":"Bind indexed units to source revisions and describe lexical analysis.","layers":[{"id":"layer-passages","name":"Passage bindings","description":"Index-specific context for segmentation and locator contract.","findings":[{"id":"finding-passages","name":"Segmentation and locator contract","description":"Proposed segmentation settings and membership references bind externally mastered passages to source representations. Whole-document indexing is allowed. Chunk IDs and source offsets must not be substituted for stable source identity.","questions":[{"text":"Which segmentation recipe or whole-document rule produced the indexed units?","id":"finding-passages-q-1","kind":"process"},{"text":"Which passage revision and source representation are bound to each indexed unit?","id":"finding-passages-q-2","kind":"relationship"},{"text":"Which locator convention distinguishes characters, bytes, tokens and timed media positions?","id":"finding-passages-q-3","kind":"interoperability"},{"text":"How are ambiguous locators, changed source text and overlapping or duplicate passages handled?","id":"finding-passages-q-4","kind":"exception"}]}]},{"id":"layer-lexical","name":"Lexical representation","description":"Index-specific context for field and analysis profile.","findings":[{"id":"finding-lexical","name":"Field and analysis profile","description":"Proposed field schema records analysis, normalization and index/storage choices. Lexical-only profiles need no embedding. Unsupported languages or field types are declared rather than silently treated as equivalent.","questions":[{"text":"Which fields are indexed, stored, filterable or excluded and with which data types?","id":"finding-lexical-q-1","kind":"definition"},{"text":"Which tokenizer, normalization, language and analysis versions are used for each lexical field?","id":"finding-lexical-q-2","kind":"process"},{"text":"Which query transformations must be compatible with the indexed lexical representation?","id":"finding-lexical-q-3","kind":"constraint"},{"text":"What happens when a field schema or analysis change invalidates existing postings?","id":"finding-lexical-q-4","kind":"validation"}]}]}]},{"id":"bundle-retrieval","name":"Vector and query compatibility","description":"Declare vector spaces and retrieval capabilities without owning recall events.","layers":[{"id":"layer-vectors","name":"Vector representation","description":"Index-specific context for embedding space compatibility.","findings":[{"id":"finding-vectors","name":"Embedding space compatibility","description":"Proposed vector profile pins document and query encoder revisions, preprocessing and space identifiers. Equal dimensions alone do not prove compatible meaning. This is a design inference, not an embedding interchange standard.","questions":[{"text":"Which immutable encoder and preprocessing revisions identify each document and query embedding space?","id":"finding-vectors-q-1","kind":"identity"},{"text":"Which vector dimensions, numeric encoding, distance metric and normalization apply per field?","id":"finding-vectors-q-2","kind":"measurement"},{"text":"Which evidence permits query vectors and stored vectors to be compared in the same space?","id":"finding-vectors-q-3","kind":"validation"},{"text":"How are absent, invalid, truncated or incompatible embeddings represented without hiding lexical fallback?","id":"finding-vectors-q-4","kind":"exception"}]}]},{"id":"layer-query","name":"Retrieval capability","description":"Index-specific context for query and result binding.","findings":[{"id":"finding-query","name":"Query and result binding","description":"Proposed capability metadata describes supported query routes, filtering, ranking configuration and result references. Actual recall events and downstream answer support remain external. A similarity score does not establish truth.","questions":[{"text":"Which lexical, vector or hybrid query capabilities and filter operators are supported by this generation?","id":"finding-query-q-1","kind":"requirement"},{"text":"Which candidate limits, approximation settings and score combination rules constrain a query route?","id":"finding-query-q-2","kind":"constraint"},{"text":"Which generation and configuration references accompany a result handed to the recall-event owner?","id":"finding-query-q-3","kind":"evidence"},{"text":"How are zero hits, time limits, partial shard results and unavailable fields distinguished?","id":"finding-query-q-4","kind":"exception"}]}]}]},{"id":"bundle-generation","name":"Refresh and serving generations","description":"Account for change coverage, release evidence and recovery limits.","layers":[{"id":"layer-refresh","name":"Refresh evidence","description":"Index-specific context for change coverage and freshness.","findings":[{"id":"finding-refresh","name":"Change coverage and freshness","description":"Proposed refresh receipts distinguish source change time, observation, ingestion and reader visibility. Per-source watermarks and failures qualify freshness. Successful job completion alone does not show every eligible change is visible.","questions":[{"text":"Which source revisions or change watermarks are included in the currently visible generation?","id":"finding-refresh-q-1","kind":"temporal"},{"text":"Which change, schedule or repair trigger requests incremental refresh or complete rebuilding?","id":"finding-refresh-q-2","kind":"process"},{"text":"Which receipt separates source change, observation, ingestion, commit and reader-visible times?","id":"finding-refresh-q-3","kind":"event"},{"text":"How are duplicated, late, out-of-order or failed updates reconciled before freshness is declared?","id":"finding-refresh-q-4","kind":"exception"}]}]},{"id":"layer-release","name":"Generation release","description":"Index-specific context for publication and recovery evidence.","findings":[{"id":"finding-release","name":"Publication and recovery evidence","description":"Proposed generation transitions bind manifests and external release receipts. Atomicity, durability and reader visibility must be stated per binding; no universal distributed transaction guarantee is inferred. Older generations cannot bypass current denials.","questions":[{"text":"Which readiness conditions distinguish a staged generation from one eligible for serving?","id":"finding-release-q-1","kind":"state"},{"text":"Which approved receipt binds the serving alias to an exact generation and prior binding revision?","id":"finding-release-q-2","kind":"authority"},{"text":"Which consistency and recovery guarantees apply across shards, replicas and reader snapshots?","id":"finding-release-q-3","kind":"constraint"},{"text":"Under which evidence may a previous generation be restored without reviving withdrawn material?","id":"finding-release-q-4","kind":"lifecycle"}]}]}]},{"id":"bundle-governance","name":"Access and disposition","description":"Bind external policy to disclosure and derivative disposal evidence.","layers":[{"id":"layer-authorization","name":"Access bindings","description":"Index-specific context for policy and tenancy projection.","findings":[{"id":"finding-authorization","name":"Policy and tenancy projection","description":"Proposed bindings connect index metadata and result disclosure to externally governed access decisions. Query filtering is not authorization proof. Missing or stale authorization evidence requires denial, including for counts, snippets and cached results.","questions":[{"text":"Which tenant, subject, resource and operation attributes are required before index data may be disclosed?","id":"finding-authorization-q-1","kind":"access"},{"text":"Which external authorization decision must be enforced before returning hits, snippets, scores or counts?","id":"finding-authorization-q-2","kind":"security"},{"text":"How are policy changes and revoked grants reflected in index generations and result caches?","id":"finding-authorization-q-3","kind":"temporal"},{"text":"What is the deny behavior when labels conflict or the authorization service is unavailable?","id":"finding-authorization-q-4","kind":"exception"}]}]},{"id":"layer-disposition","name":"Withdrawal and disposal","description":"Index-specific context for suppression and erasure evidence.","findings":[{"id":"finding-disposition","name":"Suppression and erasure evidence","description":"Proposed disposition records separate prompt suppression from verified physical removal. Retention and forgetting policy is externally mastered. Embeddings, copied fields, snapshots and caches are included in the affected-resource inventory; no erasure completion is inferred from a tombstone.","questions":[{"text":"Which policy references determine retention and disposal of this index and its derived representations?","id":"finding-disposition-q-1","kind":"retention"},{"text":"Which source withdrawal or quarantine reference requires suppression across current and prior generations?","id":"finding-disposition-q-2","kind":"process"},{"text":"Which external receipts demonstrate removal from serving copies, retained snapshots, caches and backups?","id":"finding-disposition-q-3","kind":"evidence"},{"text":"How is a retention hold reconciled with denial of ordinary retrieval and eventual disposal?","id":"finding-disposition-q-4","kind":"exception"}]}]}]},{"id":"bundle-assurance","name":"Evaluation and interchange","description":"Qualify quality claims and portable descriptions with remaining holds.","layers":[{"id":"layer-evaluation","name":"Quality evidence","description":"Index-specific context for generation evaluation binding.","findings":[{"id":"finding-evaluation","name":"Generation evaluation binding","description":"Proposed evidence references bind an external evaluation to corpus, queries, judgments, configuration and generation. Retrieval relevance, approximate-neighbor accuracy and end-answer correctness are separate claims. Thresholds are adopted per use case, not universal.","questions":[{"text":"Which task, query set, judgments and eligible corpus define the retrieval quality claim?","id":"finding-evaluation-q-1","kind":"measurement"},{"text":"Which relevance, approximation, latency and coverage metrics are reported with definitions and uncertainty?","id":"finding-evaluation-q-2","kind":"quality"},{"text":"Which generation and query configuration were evaluated and which acceptance thresholds were approved?","id":"finding-evaluation-q-3","kind":"validation"},{"text":"Which language, tenant, sparse-result and unjudged-document gaps limit generalization of the evaluation?","id":"finding-evaluation-q-4","kind":"exception"}]}]},{"id":"layer-exchange","name":"Interchange and assurance","description":"Index-specific context for portable description and unresolved bindings.","findings":[{"id":"finding-exchange","name":"Portable description and unresolved bindings","description":"Proposed interchange description separates portable metadata from backend-specific physical bytes. Conceptual alignment is not executable conformance. Migration may require rebuilding and fresh evaluation rather than copying an index file.","questions":[{"text":"Which metadata and artifact bindings can another implementation interpret without hidden runtime assumptions?","id":"finding-exchange-q-1","kind":"interoperability"},{"text":"Which recipe, source and encoder references plus integrity evidence permit reconstruction of a generation?","id":"finding-exchange-q-2","kind":"provenance"},{"text":"Which format, algorithm or policy changes require migration, rebuilding or separate compatibility review?","id":"finding-exchange-q-3","kind":"constraint"},{"text":"Which independent review, source verification and executable fixture gaps remain before operational adoption?","id":"finding-exchange-q-4","kind":"validation"}]}]}]}]},"agentConduct":{"may":["Register an index definition: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Bind a generation manifest: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Record representation compatibility: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Record refresh coverage: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Record serving transition evidence: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Record suppression and disposal evidence: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict."],"mustNot":["Read recorded state with evidence age and gaps; never infer actual live serving state from an unverified receipt.","Deny until subject, resource, tenant, operation and current policy evidence permit the specific disclosure.","An index filter is never sufficient authority by itself."],"requiresHuman":[]},"ethics":{"considerations":["Format-neutral technical profile; source rights, privacy, residency and retention rules depend on the adopting jurisdiction and corpus."],"affectedParties":[]},"owners":{"steward":"Accountable index owner role and delegated custodian, with tenant scope and approval authority","roles":[{"name":"Index owner","responsibilities":["Approve scope, profiles and adoption gates."]},{"name":"Index custodian","responsibilities":["Maintain generation and refresh evidence without changing source masters."]},{"name":"Policy authority","responsibilities":["Own access and retention decisions referenced by the index."]},{"name":"Assurance reviewer","responsibilities":["Assess provenance, compatibility and evaluation limitations."]},{"name":"Consumer agent","responsibilities":["Read authorized metadata and preserve generation references in downstream records."]}],"masterSystems":[]},"relations":[{"target":"WM-DAT-001","type":"aligned","note":"Registry parent is Dataset. Align catalog identity and distributions; the index specializes a derived resource and does not duplicate corpus ownership or dataset lifecycle."},{"target":"WM-MEM-001","type":"references","note":"Optional store and tenancy binding. Store operations, capacity and general retention are outside the index record."},{"target":"WM-MEM-015","type":"references","note":"Passage revisions remain independently mastered; index membership and locator references do not create a second passage lifecycle."},{"target":"WM-MEM-007","type":"references","note":"Recall-event owner records actual queries, rankings and use. This index supplies generation and capability references only."},{"target":"WM-MEM-013","type":"references","note":"Context assembly owns selected context and budgets; index configuration does not assert what was placed in a context."},{"target":"WM-MEM-010","type":"references","note":"Retention and forgetting policy owns disposition rules; index records affected derivatives and external execution receipts."},{"target":"WM-MEM-011","type":"references","note":"Scope and sharing grant owns authorization policy. Index labels and filters are projections, not grants."},{"target":"WM-MEM-020","type":"references","note":"Quarantine and redaction owner decides source restrictions; index binds suppression status without adjudicating the underlying incident."},{"target":"WM-MEM-016","type":"references","note":"Answer grounding owns claim-to-evidence support. Retrieval similarity is not a grounding verdict."},{"target":"WM-DAT-001","type":"neighbor","note":"Registry parent is Dataset. Align catalog identity and distributions; the index specializes a derived resource and does not duplicate corpus ownership or dataset lifecycle."},{"target":"WM-MEM-001","type":"neighbor","note":"Optional store and tenancy binding. Store operations, capacity and general retention are outside the index record."},{"target":"WM-MEM-015","type":"neighbor","note":"Passage revisions remain independently mastered; index membership and locator references do not create a second passage lifecycle."},{"target":"WM-MEM-007","type":"neighbor","note":"Recall-event owner records actual queries, rankings and use. This index supplies generation and capability references only."},{"target":"WM-MEM-013","type":"neighbor","note":"Context assembly owns selected context and budgets; index configuration does not assert what was placed in a context."},{"target":"WM-MEM-010","type":"neighbor","note":"Retention and forgetting policy owns disposition rules; index records affected derivatives and external execution receipts."},{"target":"WM-MEM-011","type":"neighbor","note":"Scope and sharing grant owns authorization policy. Index labels and filters are projections, not grants."},{"target":"WM-MEM-020","type":"neighbor","note":"Quarantine and redaction owner decides source restrictions; index binds suppression status without adjudicating the underlying incident."},{"target":"WM-MEM-016","type":"neighbor","note":"Answer grounding owns claim-to-evidence support. Retrieval similarity is not a grounding verdict."},{"target":"Encoder and storage bindings","type":"neighbor","note":"Embedding model revisions and backend formats are referenced. This index does not own model training or storage-service lifecycle."},{"target":"WM-DAT-001","type":"parent"}],"interaction":{"identity":{"applicability":"required","items":["Authoritative master-system identifier","Governed global identifier or IRI","UUID or ULID assigned by the adopting Dimension"]},"properties":{"applicability":"not-applicable","items":[]},"recognition":{"applicability":"optional","items":[]},"capabilities":{"applicability":"required","items":["Register an index definition: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Bind a generation manifest: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Record representation compatibility: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Record refresh coverage: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Record serving transition evidence: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict.","Record suppression and disposal evidence: Proposed local metadata operation; unimplemented. Refuse unauthorized, stale-revision or unresolved-evidence writes. Repeated identical receipts are idempotent; contradictory receipts become a review conflict."]},"hazards":{"applicability":"optional","items":[]},"interfaces":{"applicability":"required","items":["PROV-O: The PROV Ontology","Data Catalog Vocabulary (DCAT) - Version 3"]},"context":{"applicability":"required","items":["Format-neutral technical profile; source rights, privacy, residency and retention rules depend on the adopting jurisdiction and corpus.","NIST material is used for conceptual alignment, not universal legal authority."]}},"sources":[{"title":"Apache Lucene IndexWriter API","url":"https://lucene.apache.org/core/10_3_1/core/org/apache/lucene/index/IndexWriter.html","note":"Apache Software Foundation"},{"title":"Apache Lucene KnnFloatVectorField API","url":"https://lucene.apache.org/core/10_3_1/core/org/apache/lucene/document/KnnFloatVectorField.html","note":"Apache Software Foundation"},{"title":"PROV-O: The PROV Ontology","url":"https://www.w3.org/TR/prov-o/","note":"W3C"},{"title":"Data Catalog Vocabulary (DCAT) - Version 3","url":"https://www.w3.org/TR/vocab-dcat-3/","note":"W3C"},{"title":"Web Annotation Data Model","url":"https://www.w3.org/TR/annotation-model/","note":"W3C"},{"title":"Text REtrieval Conference (TREC) Overview","url":"https://trec.nist.gov/overview.html","note":"NIST"},{"title":"Guide to Attribute Based Access Control (ABAC) Definition and Considerations","url":"https://csrc.nist.gov/pubs/sp/800/162/upd2/final","note":"NIST"},{"title":"Apache Lucene Analyzer API","url":"https://lucene.apache.org/core/10_3_1/core/org/apache/lucene/analysis/Analyzer.html","note":"Apache Software Foundation"},{"title":"Apache Lucene KnnFloatVectorQuery API","url":"https://lucene.apache.org/core/10_3_1/core/org/apache/lucene/search/KnnFloatVectorQuery.html","note":"Apache Software Foundation"}],"openQuestions":["Have the coordinator verify all source URLs, editions, redirects and body integrity; review full access-control guidance and relevant errata.","Develop typed instance bindings and fixtures for empty and lexical-only indexes, source edits, incompatible encoders, partial refresh, stale policies, revocation during rollback and disposal with retained copies.","Validate profile-specific multilingual segmentation, hybrid ranking, approximation quality, distributed visibility and applicable rights and retention rules.","Restore independent external review before any canonical or publishable-draft promotion.","Independent second-provider review is absent; local self-audit is not independent review.","Direct HTTP checks are unattempted under the owner-reported sandbox restriction. Browser service content access does not measure HTTP status, byte integrity or current source version.","Candidate data groups are not executable nested instance schemas; binding mappings and adversarial fixtures remain to be implemented.","Embedding compatibility, hybrid fusion, distributed visibility, multilingual segmentation and tenant isolation require profile-specific evidence.","No full NIST SP 800-162 reading, legal applicability review, implementation test or benchmark run was performed."],"resources":{"spec":"/models/wm-mem-014-retrieval-index/spec.yaml","agents":"/models/wm-mem-014-retrieval-index/AGENTS.md","source":"https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-mem-014"},"provenance":{"origin":"world-models research","builtFrom":["models/wm-mem-014-retrieval-index/spec.yaml"],"providers":["Codex"],"researchStatus":"reviewable-draft","generatedAt":"2026-10-21T17:29:15Z","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}}