# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-21T15:46:50Z", "synthesisSha256": "8472f8070e490e66be2050ef315eb00e88be984acafc1176291026de5d5161ca", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-MEM-001", "registryId": "vr.wm-mem-001", "name": "Memory Store", "version": "0.1.0-reviewable-draft", "previousVersions": [], "entryKind": "entity", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.MEM.STO" ], "tags": [ "memory", "store", "inf.mem.sto" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-mem-001-memory-store/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-mem-001", "model": { "registry_id": "vr.wm-mem-001", "model_id": "WM-MEM-001", "name": "Memory Store", "entry_kind": "entity", "purpose": "Describe one governed logical store of agent memory with explicit identity, custody, scope, tenancy, release and retention obligations.", "scope_statement": "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.", "in_scope": [ "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_of_scope": [ "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" ], "boundary_notes": [ { "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.", "source_refs": [ "SRC-001" ] }, { "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.", "source_refs": [ "SRC-002" ] }, { "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.", "source_refs": [ "SRC-002" ] }, { "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.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "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.", "source_refs": [ "SRC-003", "SRC-004" ] }, { "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "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.", "source_refs": [ "SRC-002", "SRC-003" ] }, { "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.", "source_refs": [ "SRC-002", "SRC-004" ] } ] }, "sources": [ { "id": "SRC-001", "title": "Data Catalog Vocabulary (DCAT) - Version 3", "organization": "W3C", "url": "https://www.w3.org/TR/vocab-dcat-3/", "version_or_date": "Recommendation, 2024-08-22", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:45:28Z", "relevance": "Dataset, distribution and service distinctions; catalog alignment and version metadata. Does not specify memory-store runtime behavior." }, { "id": "SRC-002", "title": "PROV-O: The PROV Ontology", "organization": "W3C", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "Recommendation, 2013-04-30", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:45:28Z", "relevance": "Entity, collection, membership, derivation, attribution and invalidation vocabulary; provenance does not certify truth." }, { "id": "SRC-003", "title": "ODRL Information Model 2.2", "organization": "W3C", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "Recommendation, 2018-02-15", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:45:28Z", "relevance": "Policies, parties, assets, constraints and policy conflict strategies; expression is distinct from enforcement." }, { "id": "SRC-004", "title": "NIST SP 800-53 Revision 5: Security and Privacy Controls for Information Systems and Organizations", "organization": "NIST", "url": "https://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r5.pdf", "version_or_date": "September 2020, includes updates as of 2020-12-10; later catalog releases not reconciled", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:45:28Z", "relevance": "Selected AC-3, AU-9, CP-9, SI-10, SI-11 and SI-12 controls inform local access, audit, continuity, admission and retention questions. Tailoring is required; no certification claimed." }, { "id": "SRC-005", "title": "RFC 9110: HTTP Semantics", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc9110.html", "version_or_date": "June 2022, STD 97", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:45:28Z", "relevance": "Sections 8.8 and 13.1.1 support representation validators and conditional mutation. An optional HTTP binding does not establish distributed transactions." }, { "id": "SRC-006", "title": "RFC 8493: The BagIt File Packaging Format (V1.0)", "organization": "RFC Editor Independent Submission", "url": "https://www.rfc-editor.org/rfc/rfc8493.html", "version_or_date": "October 2018, Informational, BagIt 1.0", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 2, "accessed_at": "2026-10-21T15:45:28Z", "relevance": "Payload manifests and completeness/checksum validation inform optional transfer receipts. The format does not establish semantic compatibility, authenticity or access rights." }, { "id": "SRC-007", "title": "RFC 3339: Date and Time on the Internet: Timestamps", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "July 2002, Standards Track; later updates not reconciled", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:45:28Z", "relevance": "Section 5.6 timestamp syntax and explicit offsets support recorded operational instants. Logical ordering, uncertain times and durations need separate fields." } ], "structure": { "bundles": [ { "id": "bundle-identity-governance", "name": "Identity and governance", "description": "Identify the logical resource and its accountable scope.", "rationale": "Proposed grouping of distinct store-level questions; cited specifications support component concepts, not this exact hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-001", "SRC-002" ], "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.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "finding-identity-q1", "kind": "identity", "text": "Which master identifier and namespace distinguish this store from its endpoints and snapshots?", "answer_data": [ "master_id", "namespace", "endpoint_refs", "snapshot_refs" ] }, { "id": "finding-identity-q2", "kind": "classification", "text": "Which memory classes and persistence profile does the store admit?", "answer_data": [ "class_scheme", "scheme_version", "admitted_classes", "persistence_profile" ] }, { "id": "finding-identity-q3", "kind": "relationship", "text": "How is the store related to catalogued datasets without equating the store to a distribution?", "answer_data": [ "dataset_refs", "service_refs", "mapping_version", "distinction" ] }, { "id": "finding-identity-q4", "kind": "exception", "text": "When does a split or merger create a new store identity instead of a revision?", "answer_data": [ "continuity_rule", "predecessor_refs", "successor_refs", "decision_evidence" ] } ], "data_elements": [ { "id": "data-identity-master-id", "name": "Master identifier", "description": "Candidate master identifier field for logical store identity; nested schemas and code lists require a pinned adoption profile.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-identity-namespace", "name": "Store namespace", "description": "Candidate store namespace field for logical store identity; nested schemas and code lists require a pinned adoption profile.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-identity-classification", "name": "Classification profile", "description": "Candidate classification profile field for logical store identity; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-identity-catalog-links", "name": "Catalog links", "description": "Candidate catalog links field for logical store identity; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "artifact-identity", "name": "Store identity record", "description": "Versioned evidence for logical store identity, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "finding-custody-q1", "kind": "ownership", "text": "Who is accountable for this store and which custodians have only delegated operational duties?", "answer_data": [ "steward_ref", "custodian_refs", "delegation_refs", "responsibility_limits" ] }, { "id": "finding-custody-q2", "kind": "definition", "text": "Which purposes and scope classes justify persistence in this store?", "answer_data": [ "purpose_codes", "scope_class", "scope_ref", "prohibited_uses" ] }, { "id": "finding-custody-q3", "kind": "constraint", "text": "Which residency and tenant boundaries apply to payloads and derived copies?", "answer_data": [ "tenant_ref", "residency_profile", "replica_locations", "exceptions" ] }, { "id": "finding-custody-q4", "kind": "authority", "text": "What evidence permits a transfer of custody without silently expanding access?", "answer_data": [ "transfer_authority", "receiving_custodian", "policy_revision", "approval_ref" ] } ], "data_elements": [ { "id": "data-custody-steward", "name": "Accountable steward", "description": "Candidate accountable steward field for custody and purpose boundary; nested schemas and code lists require a pinned adoption profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-custody-scope", "name": "Scope and purpose", "description": "Candidate scope and purpose field for custody and purpose boundary; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-custody-custody", "name": "Custody assignments", "description": "Candidate custody assignments field for custody and purpose boundary; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-custody-residency", "name": "Residency profile", "description": "Candidate residency profile field for custody and purpose boundary; nested schemas and code lists require a pinned adoption profile.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-custody", "name": "Custody and scope declaration", "description": "Versioned evidence for custody and purpose boundary, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-membership-admission", "name": "Membership and admission", "description": "Describe what belongs to the store and how admission is governed.", "rationale": "Proposed grouping of distinct store-level questions; cited specifications support component concepts, not this exact hierarchy.", "source_refs": [ "SRC-002", "SRC-004", "SRC-007" ], "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.", "source_refs": [ "SRC-002", "SRC-007" ], "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.", "source_refs": [ "SRC-002", "SRC-007" ], "questions": [ { "id": "finding-membership-q1", "kind": "composition", "text": "Which item identities and revisions belong to the declared store view?", "answer_data": [ "item_refs", "revision_refs", "membership_revision", "view_scope" ] }, { "id": "finding-membership-q2", "kind": "temporal", "text": "Which times describe membership validity and which describe recording or observation?", "answer_data": [ "valid_from", "valid_until", "recorded_at", "observed_at", "unknown_time_reason" ] }, { "id": "finding-membership-q3", "kind": "provenance", "text": "What formation or import evidence explains each membership addition?", "answer_data": [ "formation_refs", "import_refs", "asserting_actor", "evidence_refs" ] }, { "id": "finding-membership-q4", "kind": "quality", "text": "How are empty membership and an incompletely enumerated membership distinguished?", "answer_data": [ "enumeration_state", "completeness_scope", "count_observed", "observed_at" ] } ], "data_elements": [ { "id": "data-membership-members", "name": "Member references", "description": "Candidate member references field for referenced membership revisions; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] }, { "id": "data-membership-membership-revision", "name": "Membership revision", "description": "Candidate membership revision field for referenced membership revisions; nested schemas and code lists require a pinned adoption profile.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-007" ] }, { "id": "data-membership-enumeration", "name": "Enumeration status", "description": "Candidate enumeration status field for referenced membership revisions; nested schemas and code lists require a pinned adoption profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-007" ] }, { "id": "data-membership-membership-times", "name": "Membership time assertions", "description": "Candidate membership time assertions field for referenced membership revisions; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-membership", "name": "Membership manifest", "description": "Versioned evidence for referenced membership revisions, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-002", "SRC-004" ], "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.", "source_refs": [ "SRC-002", "SRC-004" ], "questions": [ { "id": "finding-admission-q1", "kind": "validation", "text": "Which schema and provenance checks are required before an item is admitted?", "answer_data": [ "item_profile_version", "check_results", "provenance_refs", "unresolved_fields" ] }, { "id": "finding-admission-q2", "kind": "security", "text": "How are untrusted instructions prevented from becoming store control policy?", "answer_data": [ "data_control_boundary", "enforcement_ref", "rejection_rule", "review_role" ] }, { "id": "finding-admission-q3", "kind": "state", "text": "Which admission states distinguish pending review from accepted or rejected membership?", "answer_data": [ "admission_state", "reason_codes", "decision_ref", "effective_revision" ] }, { "id": "finding-admission-q4", "kind": "relationship", "text": "Which quarantine and trust assessment references govern reconsideration?", "answer_data": [ "quarantine_refs", "trust_assessment_refs", "reviewer_ref", "reconsideration_basis" ] } ], "data_elements": [ { "id": "data-admission-admission-profile", "name": "Admission profile", "description": "Candidate admission profile field for admission and quarantine routing; nested schemas and code lists require a pinned adoption profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "data-admission-admission-result", "name": "Admission decision", "description": "Candidate admission decision field for admission and quarantine routing; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "data-admission-review-links", "name": "Quarantine and trust links", "description": "Candidate quarantine and trust links field for admission and quarantine routing; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-admission", "name": "Admission decision receipt", "description": "Versioned evidence for admission and quarantine routing, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-access-release", "name": "Access and release", "description": "Bind access decisions and release obligations to current policy.", "rationale": "Proposed grouping of distinct store-level questions; cited specifications support component concepts, not this exact hierarchy.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-003", "SRC-004" ], "questions": [ { "id": "finding-grants-q1", "kind": "access", "text": "Which current grants authorize a particular subject and action in this tenant?", "answer_data": [ "subject_ref", "tenant_ref", "grant_refs", "action", "evaluated_at" ] }, { "id": "finding-grants-q2", "kind": "constraint", "text": "How do store restrictions and item restrictions combine for a requested view?", "answer_data": [ "store_policy_version", "item_policy_versions", "combination_rule", "decision" ] }, { "id": "finding-grants-q3", "kind": "exception", "text": "What is returned when grants conflict or the policy service is unavailable?", "answer_data": [ "conflict_class", "unavailable_dependency", "deny_or_indeterminate", "retry_rule" ] }, { "id": "finding-grants-q4", "kind": "privacy", "text": "How are existence clues in identifiers and membership counts limited for unauthorized readers?", "answer_data": [ "disclosure_profile", "filtered_fields", "count_policy", "audit_ref" ] } ], "data_elements": [ { "id": "data-grants-policy-binding", "name": "Policy bindings", "description": "Candidate policy bindings field for effective grant evaluation; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-grants-grant-binding", "name": "Grant references", "description": "Candidate grant references field for effective grant evaluation; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "data-grants-decision-context", "name": "Evaluation context", "description": "Candidate evaluation context field for effective grant evaluation; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-grants", "name": "Access evaluation receipt", "description": "Versioned evidence for effective grant evaluation, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "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.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ], "questions": [ { "id": "finding-recall-q1", "kind": "process", "text": "At which boundary is current eligibility checked before a candidate leaves the store?", "answer_data": [ "release_boundary", "checked_item_revision", "grant_revision", "decision_ref" ] }, { "id": "finding-recall-q2", "kind": "relationship", "text": "Which index and recall references identify a derived retrieval path without becoming the master?", "answer_data": [ "index_refs", "index_revision", "recall_event_ref", "authoritative_item_ref" ] }, { "id": "finding-recall-q3", "kind": "lifecycle", "text": "How does revocation reach cached views and outstanding release requests?", "answer_data": [ "revocation_ref", "affected_views", "propagation_state", "pending_release_rule" ] }, { "id": "finding-recall-q4", "kind": "evidence", "text": "What distinguishes a candidate match from an item actually released or used in a context?", "answer_data": [ "candidate_refs", "released_refs", "context_assembly_ref", "outcome_status" ] } ], "data_elements": [ { "id": "data-recall-release-profile", "name": "Release profile", "description": "Candidate release profile field for release eligibility and revocation; nested schemas and code lists require a pinned adoption profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "data-recall-derived-views", "name": "Derived view references", "description": "Candidate derived view references field for release eligibility and revocation; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] }, { "id": "data-recall-revocation-state", "name": "Revocation propagation", "description": "Candidate revocation propagation field for release eligibility and revocation; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-recall", "name": "Release eligibility receipt", "description": "Versioned evidence for release eligibility and revocation, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-change-continuity", "name": "Change and continuity", "description": "Distinguish revision, state, observation and recovery evidence.", "rationale": "Proposed grouping of distinct store-level questions; cited specifications support component concepts, not this exact hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-005", "SRC-007" ], "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.", "source_refs": [ "SRC-002", "SRC-005" ], "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.", "source_refs": [ "SRC-002", "SRC-005" ], "questions": [ { "id": "finding-revision-q1", "kind": "requirement", "text": "Which revision and authority must a mutation present before it can be accepted?", "answer_data": [ "expected_revision", "actor_ref", "authorization_ref", "change_scope" ] }, { "id": "finding-revision-q2", "kind": "event", "text": "How is an accepted mutation distinguished from a rejected or uncertain request?", "answer_data": [ "request_id", "outcome", "prior_revision", "resulting_revision", "rejection_reason" ] }, { "id": "finding-revision-q3", "kind": "exception", "text": "How are concurrent conflicting updates and repeated request identifiers handled?", "answer_data": [ "conflict_rule", "request_fingerprint", "prior_outcome", "retry_decision" ] }, { "id": "finding-revision-q4", "kind": "provenance", "text": "Which evidence links a new revision to its predecessor and responsible operation?", "answer_data": [ "predecessor_revision", "operation_ref", "actor_ref", "evidence_digest" ] } ], "data_elements": [ { "id": "data-revision-revision-token", "name": "Current revision token", "description": "Candidate current revision token field for conditional configuration mutation; nested schemas and code lists require a pinned adoption profile.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "data-revision-change-set", "name": "Proposed change set", "description": "Candidate proposed change set field for conditional configuration mutation; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "data-revision-mutation-outcome", "name": "Mutation outcome", "description": "Candidate mutation outcome field for conditional configuration mutation; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-revision", "name": "Mutation receipt", "description": "Versioned evidence for conditional configuration mutation, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-002", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ], "questions": [ { "id": "finding-lifecycle-q1", "kind": "lifecycle", "text": "Which transitions are authorized from the current store state and who may approve them?", "answer_data": [ "current_state", "proposed_state", "transition_rule", "approving_role" ] }, { "id": "finding-lifecycle-q2", "kind": "measurement", "text": "Which observation supports the reported capacity and availability at a given time?", "answer_data": [ "metric_name", "value", "unit", "method", "observed_at", "uncertainty" ] }, { "id": "finding-lifecycle-q3", "kind": "requirement", "text": "Which recovery point and recovery time objectives have tested evidence?", "answer_data": [ "objective_profile", "test_ref", "actual_loss_interval", "actual_recovery_duration" ] }, { "id": "finding-lifecycle-q4", "kind": "security", "text": "How does a restored snapshot reconcile later deletions and revocations before reopening?", "answer_data": [ "snapshot_revision", "erasure_watermark", "grant_watermark", "reconciliation_status" ] } ], "data_elements": [ { "id": "data-lifecycle-store-state", "name": "Store lifecycle state", "description": "Candidate store lifecycle state field for store state and recovery evidence; nested schemas and code lists require a pinned adoption profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "data-lifecycle-health", "name": "Health observations", "description": "Candidate health observations field for store state and recovery evidence; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] }, { "id": "data-lifecycle-recovery", "name": "Recovery assurance", "description": "Candidate recovery assurance field for store state and recovery evidence; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-lifecycle", "name": "Continuity assessment", "description": "Versioned evidence for store state and recovery evidence, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-retention-disposal", "name": "Retention and disposal", "description": "Separate retention authority from proof of bounded disposal.", "rationale": "Proposed grouping of distinct store-level questions; cited specifications support component concepts, not this exact hierarchy.", "source_refs": [ "SRC-002", "SRC-003", "SRC-004", "SRC-007" ], "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.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "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.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ], "questions": [ { "id": "finding-retention-q1", "kind": "retention", "text": "Which retention policy revision applies to each membership class and copy category?", "answer_data": [ "policy_ref", "policy_revision", "member_class", "copy_category", "applicability" ] }, { "id": "finding-retention-q2", "kind": "temporal", "text": "What event starts the retention period and how is an unknown start handled?", "answer_data": [ "trigger_type", "trigger_ref", "start_time", "duration", "unknown_handling" ] }, { "id": "finding-retention-q3", "kind": "authority", "text": "Which authority can impose or release a scoped retention hold?", "answer_data": [ "hold_ref", "authority_ref", "covered_items", "review_due", "release_basis" ] }, { "id": "finding-retention-q4", "kind": "exception", "text": "How are conflicting retention and erasure requirements referred for resolution?", "answer_data": [ "conflicting_policy_refs", "applicable_profile", "responsible_reviewer", "interim_access_rule" ] } ], "data_elements": [ { "id": "data-retention-retention-bindings", "name": "Retention policy bindings", "description": "Candidate retention policy bindings field for retention obligations and exceptions; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-retention-holds", "name": "Scoped hold references", "description": "Candidate scoped hold references field for retention obligations and exceptions; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] }, { "id": "data-retention-retention-evaluation", "name": "Retention evaluation", "description": "Candidate retention evaluation field for retention obligations and exceptions; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-retention", "name": "Retention applicability assessment", "description": "Versioned evidence for retention obligations and exceptions, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-003", "SRC-004", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-002", "SRC-004" ], "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.", "source_refs": [ "SRC-002", "SRC-004" ], "questions": [ { "id": "finding-disposal-q1", "kind": "retention", "text": "Which payloads and derived copies are included in a disposal request?", "answer_data": [ "request_ref", "member_refs", "copy_inventory", "derived_refs", "exclusions" ] }, { "id": "finding-disposal-q2", "kind": "evidence", "text": "What evidence demonstrates completion for each in-scope copy category?", "answer_data": [ "copy_ref", "disposal_method_ref", "completion_receipt", "verification_state" ] }, { "id": "finding-disposal-q3", "kind": "exception", "text": "How are unreachable replicas and unexpired backup schedules reported?", "answer_data": [ "pending_copy_refs", "expected_expiry", "retry_owner", "residual_risk" ] }, { "id": "finding-disposal-q4", "kind": "privacy", "text": "What minimal tombstone may remain without retaining erased content or unnecessary identifiers?", "answer_data": [ "tombstone_fields", "necessity_basis", "retention_limit", "access_scope" ] } ], "data_elements": [ { "id": "data-disposal-disposal-request", "name": "Disposal request reference", "description": "Candidate disposal request reference field for evidence of bounded erasure; nested schemas and code lists require a pinned adoption profile.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "data-disposal-copy-dispositions", "name": "Copy dispositions", "description": "Candidate copy dispositions field for evidence of bounded erasure; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "data-disposal-completion", "name": "Bounded completion state", "description": "Candidate bounded completion state field for evidence of bounded erasure; nested schemas and code lists require a pinned adoption profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004" ] } ], "artifacts": [ { "id": "artifact-disposal", "name": "Disposal propagation report", "description": "Versioned evidence for evidence of bounded erasure, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-002", "SRC-004" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-exchange-assurance", "name": "Exchange and assurance", "description": "Describe portability, explicit losses and scoped assurance.", "rationale": "Proposed grouping of distinct store-level questions; cited specifications support component concepts, not this exact hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-004", "SRC-006" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ], "questions": [ { "id": "finding-portability-q1", "kind": "interoperability", "text": "Which versioned schema and interface bindings support a portable store view?", "answer_data": [ "schema_uri", "schema_version", "interface_uri", "supported_operations", "limitations" ] }, { "id": "finding-portability-q2", "kind": "composition", "text": "Which portability package represents the selected revision and permitted export scope?", "answer_data": [ "package_ref", "store_revision", "export_scope", "excluded_items", "destination_ref" ] }, { "id": "finding-portability-q3", "kind": "validation", "text": "Which checks separate byte integrity from identity mapping and policy compatibility?", "answer_data": [ "checksum_result", "identity_map", "policy_mapping", "semantic_validation", "unresolved_losses" ] }, { "id": "finding-portability-q4", "kind": "exception", "text": "Which migration losses or inaccessible references prevent automatic import?", "answer_data": [ "loss_report", "unresolved_refs", "admission_state", "human_review_ref" ] } ], "data_elements": [ { "id": "data-portability-bindings", "name": "Versioned storage and interface bindings", "description": "Candidate versioned storage and interface bindings field for transfer and migration boundaries; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "data-portability-transfer", "name": "Transfer assessment", "description": "Candidate transfer assessment field for transfer and migration boundaries; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] }, { "id": "data-portability-package-links", "name": "Portability package references", "description": "Candidate portability package references field for transfer and migration boundaries; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-portability", "name": "Transfer compatibility report", "description": "Versioned evidence for transfer and migration boundaries, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "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.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "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.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ], "questions": [ { "id": "finding-assurance-q1", "kind": "evidence", "text": "Which revision and tenant scope does an assurance statement actually cover?", "answer_data": [ "assessed_revision", "tenant_scope", "observation_window", "evidence_refs" ] }, { "id": "finding-assurance-q2", "kind": "validation", "text": "Which acceptance cases test empty stores, revoked grants and incomplete erasure?", "answer_data": [ "case_refs", "expected_outcomes", "actual_results", "unresolved_failures" ] }, { "id": "finding-assurance-q3", "kind": "access", "text": "Who can inspect or administer audit evidence independently of store payload access?", "answer_data": [ "auditor_roles", "audit_admin_roles", "access_policy", "separation_rule" ] }, { "id": "finding-assurance-q4", "kind": "quality", "text": "Which uncertainties limit any claim that the store is ready for operational use?", "answer_data": [ "open_findings", "untested_bindings", "source_limits", "independent_review_status" ] } ], "data_elements": [ { "id": "data-assurance-assurance", "name": "Assurance statement", "description": "Candidate assurance statement field for scoped audit and acceptance claims; nested schemas and code lists require a pinned adoption profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "data-assurance-audit-links", "name": "Audit evidence references", "description": "Candidate audit evidence references field for scoped audit and acceptance claims; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] }, { "id": "data-assurance-limitations", "name": "Open limitations", "description": "Candidate open limitations field for scoped audit and acceptance claims; nested schemas and code lists require a pinned adoption profile.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-assurance", "name": "Store assurance report", "description": "Versioned evidence for scoped audit and acceptance claims, with store revision, scope, responsible role, uncertainty and restricted evidence references. Payload inclusion follows the applicable access and retention policy.", "media_or_form": [ "application/json", "human-readable report" ], "serial": true, "identity_strategy": "Use the authoritative master-system artifact identifier first; otherwise allocate a namespace-qualified stable identifier plus revision. A content digest checks bytes and never substitutes for semantic identity. Never encode a timestamp as the sole identity.", "source_refs": [ "SRC-002", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-register-store", "name": "Register a store description", "description": "Proposed, unimplemented operation. Create a proposed local store record without provisioning storage.", "inputs": [ "master identity", "namespace", "steward and scope", "policy bindings" ], "preconditions": [ "identity unique within namespace", "accountable steward authorized", "required scope and profile resolved" ], "outputs": [ "new description revision or refusal", "provenance receipt" ], "effects": [ "Creates local metadata only; no endpoint or grant is created." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "function-assess-admission", "name": "Assess a membership proposal", "description": "Proposed, unimplemented operation. Produce a local admission assessment for a separately mastered item.", "inputs": [ "item revision reference", "formation evidence", "admission profile", "expected membership revision" ], "preconditions": [ "authorized writer", "schema and provenance evidence available", "store accepts admissions" ], "outputs": [ "accepted proposal, quarantine referral or refusal", "check receipt" ], "effects": [ "Records an assessment only; actual membership mutation requires the conditional mutation contract." ], "source_refs": [ "SRC-002", "SRC-004", "SRC-005" ] }, { "id": "function-evaluate-release", "name": "Evaluate a release request", "description": "Proposed, unimplemented operation. Evaluate the current permitted projection before any downstream release.", "inputs": [ "subject and tenant", "purpose and action", "item revisions", "current grants and policies" ], "preconditions": [ "authenticated caller", "current policy evidence", "store permits reads", "no unresolved revocation affecting release" ], "outputs": [ "permitted projection descriptor or denial/indeterminate", "evaluation receipt" ], "effects": [ "Records local eligibility; this research function does not retrieve or transmit payloads or assemble model context." ], "source_refs": [ "SRC-003", "SRC-004" ] }, { "id": "function-record-mutation", "name": "Record a conditional metadata mutation", "description": "Proposed, unimplemented operation. Propose a revision change with explicit concurrency and retry outcomes.", "inputs": [ "change set", "expected revision", "request identifier and fingerprint", "authorization evidence" ], "preconditions": [ "current revision matches atomically in an implementing binding", "request identity is unambiguous", "mutation scope authorized" ], "outputs": [ "new revision receipt, conflict, prior outcome or refusal" ], "effects": [ "Changes local metadata only after preconditions; a mismatch has no mutation effect. Distributed behavior requires separate conformance." ], "source_refs": [ "SRC-002", "SRC-005" ] }, { "id": "function-assess-disposal", "name": "Assess disposal completion", "description": "Proposed, unimplemented operation. Reconcile external disposal receipts against a declared copy inventory.", "inputs": [ "disposal request", "retention and hold references", "copy inventory", "completion evidence" ], "preconditions": [ "authorized reviewer", "hold conflicts resolved or recorded as blocking", "copy inventory scope declared" ], "outputs": [ "complete within declared scope, incomplete or blocked", "residual copy report" ], "effects": [ "Records bounded evidence only; does not erase payloads or assert recall exclusion is physical erasure." ], "source_refs": [ "SRC-002", "SRC-004" ] }, { "id": "function-assess-transfer", "name": "Assess transfer compatibility", "description": "Proposed, unimplemented operation. Assess an optional portability package before a separately authorized import.", "inputs": [ "package reference", "source store revision", "destination profile", "manifest and policy mappings" ], "preconditions": [ "authorized export/import purpose", "integrity evidence available", "identity and scope mappings declared" ], "outputs": [ "compatible proposal, loss report or refusal", "migration assessment receipt" ], "effects": [ "Records assessment only; does not export, import, execute embedded content or fetch referenced remote payloads." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-006" ] } ], "composition": [ { "target": "WM-DAT-001", "relation": "ALIGN", "purpose": "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.", "required": false, "source_refs": [ "SRC-001" ] }, { "target": "WM-MEM-002", "relation": "REFERENCE", "purpose": "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.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-MEM-006", "relation": "REFERENCE", "purpose": "Optional formation evidence for admissions. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-MEM-008", "relation": "REFERENCE", "purpose": "Optional consolidation lineage for derived members. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-MEM-007", "relation": "REFERENCE", "purpose": "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.", "required": false, "source_refs": [ "SRC-002" ] }, { "target": "WM-MEM-010", "relation": "REFERENCE", "purpose": "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.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "WM-MEM-011", "relation": "REFERENCE", "purpose": "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.", "required": false, "source_refs": [ "SRC-003", "SRC-004" ] }, { "target": "WM-MEM-012", "relation": "REFERENCE", "purpose": "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.", "required": false, "source_refs": [ "SRC-006" ] }, { "target": "WM-MEM-014", "relation": "REFERENCE", "purpose": "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.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-MEM-013", "relation": "REFERENCE", "purpose": "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.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "WM-MEM-018", "relation": "REFERENCE", "purpose": "Optional externally mastered trust assessments. Target version and compatibility must be pinned before implementation; the citation supports the concept, not registry-model conformance.", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] }, { "target": "WM-MEM-020", "relation": "REFERENCE", "purpose": "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.", "required": false, "source_refs": [ "SRC-002", "SRC-004" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Name an accountable steward by role or local identity, not a brand owner.", "Declare master namespace, store identity, tenant scope and permitted purposes.", "Bind versioned policy, item profile, retention schedule, interface and audit locations.", "Do not store credentials or secret key material in the model package." ], "namespace_guidance": "Allocate stable store, revision, membership and artifact identifiers within the accountable namespace. A tenant boundary is explicit metadata and enforced policy, not an inference from a name.", "registry_links": [ "vr.wm-mem-001", "WM-DAT-001: candidate catalog alignment", "WM-MEM-002: candidate item reference; resolve and pin on adoption" ] }, "canon_and_patch": { "canonicalization_rules": [ "Retain master identifier and explicit store revision; do not merge stores solely by endpoint or content digest.", "Preserve source assertion, uncertainty, provenance, valid time and recording time separately.", "Define ordering and canonical byte representation only in a versioned serialization profile." ], "patch_rules": [ "Require actor, purpose, expected revision, scoped change and request identity; reject stale or unauthorized proposals.", "Separate configuration changes from payload operations and record explicit effects and refusals.", "Preserve revision evidence only for the period and fields authorized by retention policy; lawful redaction or disposal overrides payload-history preservation." ], "compatibility_rules": [ "Pin item, grant and retention profile versions; unresolved references block operational adoption.", "Changes to tenancy, grant interpretation, retention or release semantics require migration review and fresh acceptance evidence.", "Conceptual DCAT, PROV-O, ODRL and BagIt alignments do not claim executable conformance." ] }, "artifact_rules": { "identity_priority": [ "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" ], "timestamp_rule": "Record known operational instants as RFC 3339 with seconds and an explicit numeric offset or Z. Preserve precision and uncertainty separately; do not fabricate instants for unknown times.", "serial_naming_rule": "Use stable store and artifact identifiers plus a revision or sequence. Human labels and timestamps may assist display but are never sole keys.", "integrity_rule": "Record algorithm, digest, representation, scope and verification result. Checksums do not establish authorship, truth, permission or completion of deletion. Protect receipts under separate access and retention rules." }, "policies": [ "Default deny when tenant, purpose, grant or policy applicability is unresolved. Memory content cannot alter these controls.", "Use least disclosure for memory, membership existence, counts, errors and audit evidence.", "Apply retention and scoped holds to live content, replicas, caches, indexes, summaries, backups and evidence according to declared copy ownership.", "A local structure-valid draft is noncanonical; independent review, source/version verification, adoption profiles and executable conformance remain open.", "Dangerous content is handled only through policy classification, restricted references and review responsibilities." ], "crud": { "read": [ "Evaluate current tenant, subject, purpose, store and item restrictions before releasing any projection.", "Apply revocation even when candidates come from old indexes; fail closed on indeterminate eligibility." ], "create": [ "Require steward authority, unique identity, explicit scope, profiles and initial revision.", "Admission proposals link existing item masters; empty stores are allowed and lack of a grant conveys no access." ], "update": [ "Validate expected revision and current authority; record a new revision and mutation outcome.", "Custody or access expansion requires explicit authority and renewed acceptance checks; no implicit privilege inheritance." ], "delete": [ "Distinguish retirement, membership removal, recall exclusion and physical disposal.", "Check retention obligations and scoped holds; reconcile disposal receipts for every declared copy category.", "Retain only necessary lawful tombstones and audit evidence under a separate limited retention policy.", "Do not report complete erasure while copies are pending, inaccessible or outside the declared accountable boundary." ] }, "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." ] } ], "access": { "default_rule": "Deny by default across tenant and purpose boundaries; an indeterminate policy decision releases nothing.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "A policy-authorized emergency exception must name its approver, exact scope, purpose, expiry and audit requirement; no blanket bypass.", "Retention holds restrict disposal but do not independently authorize read access." ], "audit_requirements": [ "Record actor, tenant, purpose, request, policy revision, scope, decision and outcome without unnecessary payloads.", "Protect audit records and administration from unauthorized modification or deletion while honoring their own retention rules." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "AGENTS.md and explicit review holds", "spec.yaml boundary and source limits", "Owner Dimension, current grants and retention policies", "Pinned item and interface profiles before any instance action" ] } }, "coverage": { "claim": "Source-grounded proposed structure for one governed logical agent-memory store, assessed in a separate local no-tools self-audit. Component specifications inform local design choices, not a complete memory standard. This noncanonical reviewable draft retains independent-review, source/version, adoption-profile and executable-conformance holds.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Stable logical store identity, separate revisions and backend references." }, { "dimension": "classification", "status": "covered", "notes": "Memory class and persistence profiles are declared; no biological-memory claim." }, { "dimension": "direct properties", "status": "covered", "notes": "Scope, tenant, policies and lifecycle state; operational measurements require units, method and time. Physical dimensions are inapplicable to this abstract root." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Master resolution, scope checks and timestamped health evidence distinguish a store from an index or endpoint." }, { "dimension": "capabilities and actions", "status": "covered", "notes": "Six proposed local operations with preconditions, outputs and effects; runtime implementation remains absent." }, { "dimension": "lifecycle", "status": "covered", "notes": "Local state transitions and disposal stages are distinct." }, { "dimension": "relationships", "status": "covered", "notes": "Separate item, policy, grant, recall, index and package masters; candidate bindings require version pins." }, { "dimension": "temporal", "status": "covered", "notes": "Membership validity, recording, policy effectiveness and observation time remain separate." }, { "dimension": "provenance", "status": "covered", "notes": "Formation, derivation and mutation receipts do not certify factual truth." }, { "dimension": "ownership", "status": "covered", "notes": "Steward, custodian and consumer responsibilities do not imply ownership of memory subjects." }, { "dimension": "validation", "status": "gap", "notes": "Research schema validation is available; nested instance schemas and executable conformance fixtures are deferred." }, { "dimension": "access", "status": "covered", "notes": "Tenant and purpose checks, current restrictions and revocation before release." }, { "dimension": "interoperability", "status": "gap", "notes": "Conceptual open-specification alignments only; migration mappings and loss tests require implementation." }, { "dimension": "retention", "status": "covered", "notes": "Copy inventory, holds, expiry and bounded erasure completion are explicit." }, { "dimension": "source verification", "status": "gap", "notes": "Selected web-service content reviewed; direct HTTP unattempted and version/errata review incomplete." }, { "dimension": "independent review", "status": "gap", "notes": "Claude and Grok skipped under waiver; later local no-tools self-audit is not independent external review." } ], "known_omissions": [ "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." ], "conflicts": [], "regional_assumptions": [ "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." ], "adversarial_checks": [ "An empty store must be expressible without inventing memory items or measured completeness.", "A stale index candidate or revoked sharing grant must never bypass current eligibility checks.", "A checksum-valid export must not be treated as authorized, semantically compatible or authentic by default.", "A tombstone, expired item or retired store must not be reported as complete erasure.", "Restoring an older snapshot must not silently restore revoked access or erased payloads.", "A memory containing instructions must not promote itself into control policy." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "entity", "status": "accepted", "rationale": "One logical store preserves master identity across membership, configuration, custody and backend changes, including an empty store or a temporary-content profile. The registry standalone-mm value classifies the record plane. Dataset is a qualified catalog alignment, while items, indexes, snapshots and consuming agents retain separate identities." }, "decisions": [ { "concept": "Logical store root", "disposition": "accepted", "rationale": "Persistent identity and changing membership support entity. Empty stores and temporary-content profiles do not require invented members or a different root kind." }, { "concept": "Dataset parent inheritance", "disposition": "qualified", "rationale": "The registry parent is retained as candidate catalog alignment; the draft separates dataset, distribution, service and managed store without imposing an inherited runtime schema." }, { "concept": "Membership ownership", "disposition": "rejected", "rationale": "Membership references neither transfer item mastery nor certify truth. Enumeration completeness, membership revision and item revision remain separate." }, { "concept": "Custody and tenant authority", "disposition": "accepted with limits", "rationale": "Accountability, custody and consumption are separate roles. Purpose and tenant boundaries apply independently of infrastructure control and do not imply ownership of memory subjects." }, { "concept": "Optional neighbor bindings", "disposition": "qualified", "rationale": "Registry-model adoption is optional, while effective authorization and retention policy remain required. Candidate links need version pins before use and do not amend shared relationships." }, { "concept": "Memory as control instructions", "disposition": "rejected", "rationale": "Admission treats untrusted content as data; a memory cannot grant itself authority or replace policy. Quarantine and trust masters remain external." }, { "concept": "Policy expression and release enforcement", "disposition": "separated", "rationale": "ODRL informs expression, while fail-closed conflict handling is a local proposal. Stale index candidates still require current eligibility; atomic revocation and release binding remain implementation work." }, { "concept": "Conditional mutation guarantees", "disposition": "qualified", "rationale": "Revision preconditions and explicit replay outcomes are proposed contracts. HTTP validators support one binding but do not prove distributed transactions or multi-resource atomicity." }, { "concept": "Local function authority", "disposition": "accepted as proposed only", "rationale": "Six operations disclose unimplemented local effects and refusal outcomes. Assessments do not provision storage, release payloads, grant external rights or perform disposal." }, { "concept": "Retention and evidence history", "disposition": "accepted with profile dependency", "rationale": "Expiry, holds, exclusion and disposal are distinct. Revision and audit evidence are limited by their own retention rules; history is not a justification for perpetual payload retention." }, { "concept": "Erasure and recovery claims", "disposition": "bounded", "rationale": "A tombstone or absent retrieval result is insufficient evidence. Completion is limited to the declared copy scope, residuals remain visible, and restore requires later erasure and grant reconciliation." }, { "concept": "Artifact identity and time", "disposition": "accepted", "rationale": "Master identity and revision take priority over digests and timestamps. Known instants, uncertain time, observation and membership validity remain distinct, without invented physical dimensions." }, { "concept": "Portability and conformance", "disposition": "deferred in part", "rationale": "Checksum validity does not establish authorization, authenticity or semantic compatibility. Nested schemas, neighbor pins, policy mappings and executable acceptance fixtures remain incomplete." }, { "concept": "Source support and freshness", "disposition": "limited", "rationale": "Seven primary documents support selected component concepts; the hierarchy and memory-specific safeguards are local proposals. Web-service readings are not direct HTTP measurements, and later versions and errata remain unreconciled." }, { "concept": "Legacy and registry provenance", "disposition": "reconciled", "rationale": "No legacy alias, specification reference or matching supplement is present. Historical provider attribution on the registry row is not evidence of an independent pass on this run." }, { "concept": "Independent review", "disposition": "waived and held", "rationale": "Claude and Grok were skipped with zero attempts under the owner override. This separate Codex no-tools phase is a self-audit, cannot add waived-provider facts and cannot support canonical promotion." } ], "publicationHolds": [ "Independent external review is absent under the owner-authorized single-provider waiver. Claude and Grok were skipped with zero attempts; the separate local Codex no-tools self-audit is not a second-provider review.", "Live source and version verification remains incomplete. Seven admitted URLs supplied selected readable web-service evidence, but direct HTTP checks were not attempted under the owner-reported sandbox restriction and no HTTP status was measured. Current versions, errata and claim support need coordinator review; check_sources.py is prepared.", "Qualified adoption profiles must determine tenancy, purpose, residency, legal authority, retention, holds, disposal scope and emergency access. No universal legal applicability, memory ontology or compliance certification is claimed.", "Nested instance schemas, pinned neighbor bindings, policy and portability mappings, concurrency and revocation enforcement, and executable acceptance cases remain incomplete. Research validation does not prove runtime isolation, retrieval quality, recovery safety or complete erasure.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }