# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-10-21T16:49:40Z", "synthesisSha256": "a0feca1c6bf3f9bcd34ff17610e9e2f75db6d78489714efe2e55e3443fadc965", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-MEM-011", "registryId": "vr.wm-mem-011", "name": "Memory Scope and Sharing Grant", "version": "0.1.0", "previousVersions": [], "entryKind": "relationship", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.MEM.SHR" ], "tags": [ "memory", "scope", "sharing", "grant", "inf.mem.shr" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-mem-011-memory-scope-and-sharing-grant/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-mem-011", "model": { "registry_id": "vr.wm-mem-011", "model_id": "WM-MEM-011", "name": "Memory Scope and Sharing Grant", "entry_kind": "relationship", "purpose": "Describe who may perform which operations on a bounded memory scope, under whose authority and conditions, including sharing among agents.", "scope_statement": "One identifiable, versioned authorization relationship linking an issuing authority, an authorized principal or governed principal set, and explicitly selected memory resources. Scope is a component of the grant, not a second store master. Proposed research structure is format-neutral; a recorded grant is neither a credential nor an executed access decision.", "in_scope": [ "Grant identity, issuer authority references, subject and actor bindings, resource selectors and permitted action tuples", "Conditions, delegation limits, effective intervals, revision and withdrawal assertions", "References to enforcement observations, derivative-sharing restrictions, retention dependencies and mapping evidence" ], "out_of_scope": [ "Memory payloads, store administration, identity and credential masters", "Runtime access evaluation, token issuance or revocation, copying memory, executing recall or writes, and deleting memory", "Universal legal consent, privacy compliance certification, memory truth ranking, and automatic safety or trust approval" ], "boundary_notes": [ { "neighbor": "WM-XCT-002 Access Contract / Consent", "distinction": "Registry parent is a candidate conceptual specialization. This model adds memory resource and action bindings; generic consent and authority records remain referenced. Read permission alone cannot establish write permission or lawful processing.", "source_refs": [ "SRC-001", "SRC-002" ] }, { "neighbor": "WM-MEM-001 Memory Store and WM-MEM-002 Memory Item", "distinction": "Resources remain externally mastered. Store, tenant, item and revision references delimit the grant without copying payload or store lifecycle.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "neighbor": "WM-MEM-007 Memory Recall Event and WM-MEM-013 Context Assembly", "distinction": "Grant references may accompany recall and context assembly; this model does not retrieve, rank, assemble or observe those activities by itself.", "source_refs": [ "SRC-003", "SRC-007" ] }, { "neighbor": "WM-MEM-010 Memory Retention and Forgetting Policy", "distinction": "Withdrawal blocks prospective authority as defined by the adopting profile; erasure obligations and execution remain separately governed. Already disclosed content is not recalled by editing a grant.", "source_refs": [ "SRC-004", "SRC-007" ] }, { "neighbor": "WM-MEM-012 Memory Portability Package and WM-MEM-014 Retrieval Index", "distinction": "Export and index-derived access need explicit scope treatment. A package or index is not an independent permission source.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "neighbor": "WM-MEM-017 Context Policy, WM-MEM-018 Memory Trust Assessment and WM-MEM-020 Memory Quarantine and Redaction", "distinction": "Context constraints, trust and quarantine are external policy inputs. A sharing grant cannot override them; authorization does not certify memory reliability.", "source_refs": [ "SRC-001", "SRC-003", "SRC-007" ] } ] }, "sources": [ { "id": "SRC-001", "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:59:26Z", "relevance": "Sections 2.1-2.6, 2.10 and 3: parties, assets, actions, conditions and conflict strategy. Conceptual alignment only; local memory rules are proposed." }, { "id": "SRC-002", "title": "OAuth 2.0 Rich Authorization Requests", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc9396.html", "version_or_date": "RFC 9396, May 2023", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:59:26Z", "relevance": "Sections 2 and 2.2: typed resource and action descriptions, including combination semantics. No memory authorization type is standardized here." }, { "id": "SRC-003", "title": "Guide to Attribute Based Access Control (ABAC) Definition and Considerations", "organization": "NIST", "url": "https://csrc.nist.gov/pubs/sp/800/162/upd2/final", "version_or_date": "SP 800-162, January 2014; updates 2019-08-02", "source_type": "public-authority", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:59:26Z", "relevance": "Official abstract only: subject, object, operation and environmental attributes support a contextual authorization boundary. Full publication not reviewed." }, { "id": "SRC-004", "title": "OAuth 2.0 Token Revocation", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc7009.html", "version_or_date": "RFC 7009, August 2013", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:59:26Z", "relevance": "Sections 2 and 3: revocation and propagation limits. This model records grant withdrawal and linked evidence, not token endpoint execution." }, { "id": "SRC-005", "title": "OAuth 2.0 Token Exchange", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc8693.html", "version_or_date": "RFC 8693, January 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:59:26Z", "relevance": "Sections 1.1 and 2: distinguish acting subject from delegate and resource audience. Deployment trust and attenuation rules require a separate profile." }, { "id": "SRC-006", "title": "OAuth 2.0 Token Introspection", "organization": "IETF", "url": "https://www.rfc-editor.org/rfc/rfc7662.html", "version_or_date": "RFC 7662, October 2015", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-10-21T15:59:26Z", "relevance": "Sections 2.2, 4 and 5: token status, caching and privacy. A status response is not proof of end-to-end memory enforcement." }, { "id": "SRC-007", "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:59:26Z", "relevance": "Section 3.1: entity, activity, attribution and derivation links support evidence references. Provenance does not confer permission or establish truth." } ], "structure": { "bundles": [ { "id": "bundle-authority", "name": "Grant identity and authority", "description": "Establish which permission assertion is being described and whose authority supports it.", "rationale": "A proposed memory-grant concern supported by conceptual alignment; the cited standards do not define this hierarchy.", "source_refs": [ "SRC-001", "SRC-007" ], "layers": [ { "id": "layer-grant-identity", "name": "Grant identity and revision", "description": "Context for grant identity and revision, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-007" ], "findings": [ { "id": "finding-grant-identity", "name": "Grant identity and revision", "description": "Proposed grant record with stable identity, immutable revision references and a separately identified scope definition. A name or storage path cannot serve as authority.", "source_refs": [ "SRC-001", "SRC-007" ], "questions": [ { "id": "finding-grant-identity-q1", "kind": "identity", "text": "Which master-issued identifier distinguishes this grant from its revisions?", "answer_data": [ "grant_id", "revision_id", "master_namespace" ] }, { "id": "finding-grant-identity-q2", "kind": "definition", "text": "What authorization relationship does this grant record assert?", "answer_data": [ "grant_kind", "assertion_summary" ] }, { "id": "finding-grant-identity-q3", "kind": "provenance", "text": "Which issuance record establishes the origin of this revision?", "answer_data": [ "issuance_evidence_ref", "issuer_ref" ] }, { "id": "finding-grant-identity-q4", "kind": "lifecycle", "text": "Which earlier revision does this revision supersede?", "answer_data": [ "predecessor_ref", "change_reason" ] } ], "data_elements": [ { "id": "data-grant-identity-grant-id", "name": "grant-id", "description": "Stable grant identifier in the issuing master namespace.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-grant-identity-revision-id", "name": "revision-id", "description": "Unique immutable revision identifier.", "value_kind": "identifier", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "data-grant-identity-predecessor-ref", "name": "predecessor-ref", "description": "Prior revision, absent on initial creation.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-grant-identity", "name": "Grant identity and revision record", "description": "Proposed versioned evidence view for grant identity and revision. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-issuer-authority", "name": "Issuer and authority basis", "description": "Context for issuer and authority basis, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "finding-issuer-authority", "name": "Issuer and authority basis", "description": "Bind the issuer to an externally governed authority basis for the selected memory. Custody, authorship, subject status and authority to share are distinct roles. Unknown or disputed authority does not enable access.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "finding-issuer-authority-q1", "kind": "authority", "text": "What evidence authorizes this issuer to grant the selected actions?", "answer_data": [ "authority_basis_ref", "verification_state" ] }, { "id": "finding-issuer-authority-q2", "kind": "ownership", "text": "Who maintains this grant record and who controls the selected memory scope?", "answer_data": [ "record_steward_ref", "resource_controller_ref" ] }, { "id": "finding-issuer-authority-q3", "kind": "relationship", "text": "Which separate consent or policy record constrains the issuer?", "answer_data": [ "consent_ref", "policy_ref", "applicability" ] }, { "id": "finding-issuer-authority-q4", "kind": "exception", "text": "How is disputed or withdrawn issuer authority reflected in grant usability?", "answer_data": [ "authority_dispute_state", "suspension_ref" ] } ], "data_elements": [ { "id": "data-issuer-authority-issuer-ref", "name": "issuer-ref", "description": "Issuer identity reference, not a display name.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "data-issuer-authority-authority-basis-ref", "name": "authority-basis-ref", "description": "External basis for issuing the permission.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "data-issuer-authority-authority-verification", "name": "authority-verification", "description": "verified, unresolved or disputed in an adopting profile.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "artifact-issuer-authority", "name": "Issuer and authority basis record", "description": "Proposed versioned evidence view for issuer and authority basis. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-scope", "name": "Recipients and memory scope", "description": "Bind the grant to actual principals and bounded resource selection.", "rationale": "A proposed memory-grant concern supported by conceptual alignment; the cited standards do not define this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005" ], "layers": [ { "id": "layer-principal-binding", "name": "Subject and acting agent", "description": "Context for subject and acting agent, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "findings": [ { "id": "finding-principal-binding", "name": "Subject and acting agent", "description": "Identify the recipient principal and actual acting agent separately, with tenant and session context where relevant. Group membership must have a declared evaluation time; agent cooperation does not imply common authority.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ], "questions": [ { "id": "finding-principal-binding-q1", "kind": "identity", "text": "Which principal or governed principal set receives this grant?", "answer_data": [ "subject_ref", "principal_set_ref" ] }, { "id": "finding-principal-binding-q2", "kind": "relationship", "text": "On whose behalf does the acting agent request access?", "answer_data": [ "actor_ref", "represented_subject_ref", "delegation_ref" ] }, { "id": "finding-principal-binding-q3", "kind": "temporal", "text": "At what time and version is recipient group membership resolved?", "answer_data": [ "membership_snapshot_ref", "evaluated_at", "membership_mode" ] }, { "id": "finding-principal-binding-q4", "kind": "security", "text": "Which tenant and session bindings prevent reuse by a different agent context?", "answer_data": [ "tenant_ref", "session_binding", "audience_ref" ] } ], "data_elements": [ { "id": "data-principal-binding-recipient-binding", "name": "recipient-binding", "description": "Discriminated principal or principal-set reference with namespace.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "data-principal-binding-actor-binding", "name": "actor-binding", "description": "Actual actor and optional represented subject.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] }, { "id": "data-principal-binding-membership-evidence", "name": "membership-evidence", "description": "Required by the adoption profile for a group recipient.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-principal-binding", "name": "Subject and acting agent record", "description": "Proposed versioned evidence view for subject and acting agent. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-003", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-resource-selection", "name": "Memory resource selection", "description": "Context for memory resource selection, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "findings": [ { "id": "finding-resource-selection", "name": "Memory resource selection", "description": "Scope selects stores, items, fields or governed collections with explicit tenant and version semantics. Dynamic selection requires declared membership behavior; missing selectors select nothing. A summary, embedding or index reference does not silently widen scope.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "questions": [ { "id": "finding-resource-selection-q1", "kind": "composition", "text": "Which memory stores and item or field selectors define the resource boundary?", "answer_data": [ "store_refs", "item_selectors", "field_selectors" ] }, { "id": "finding-resource-selection-q2", "kind": "constraint", "text": "Does this selector cover a fixed snapshot or future members of a governed collection?", "answer_data": [ "selection_mode", "snapshot_ref", "future_member_rule" ] }, { "id": "finding-resource-selection-q3", "kind": "spatial", "text": "Which logical tenant and processing-location constraints qualify this resource scope?", "answer_data": [ "tenant_ref", "location_policy_ref" ] }, { "id": "finding-resource-selection-q4", "kind": "validation", "text": "What happens when a selected item is moved or its identity cannot be resolved?", "answer_data": [ "resolution_state", "move_rule", "refusal_reason" ] } ], "data_elements": [ { "id": "data-resource-selection-scope-binding", "name": "scope-binding", "description": "Tenant-qualified store and item or collection selection with explicit mode.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "data-resource-selection-scope-version", "name": "scope-version", "description": "Immutable scope-definition version.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "data-resource-selection-location-policy-ref", "name": "location-policy-ref", "description": "Optional approved processing-location constraint, not a claim of physical position.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "artifacts": [ { "id": "artifact-resource-selection", "name": "Memory resource selection record", "description": "Proposed versioned evidence view for memory resource selection. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-permission", "name": "Actions and conditions", "description": "Describe permitted operations and the conditions under which they may be considered.", "rationale": "A proposed memory-grant concern supported by conceptual alignment; the cited standards do not define this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ], "layers": [ { "id": "layer-action-tuples", "name": "Permitted memory operations", "description": "Context for permitted memory operations, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-002" ], "findings": [ { "id": "finding-action-tuples", "name": "Permitted memory operations", "description": "Proposed memory vocabulary separates discovery, content read, append, amend, delete request, export, context use and onward sharing. Record action-resource pairs explicitly; a mapping must not turn independent lists into unintended combinations.", "source_refs": [ "SRC-001", "SRC-002" ], "questions": [ { "id": "finding-action-tuples-q1", "kind": "access", "text": "Which exact action-resource tuples are permitted by this grant?", "answer_data": [ "permission_tuples", "action_vocabulary_version" ] }, { "id": "finding-action-tuples-q2", "kind": "constraint", "text": "Does permission to discover metadata include permission to read memory content?", "answer_data": [ "metadata_rule", "content_rule" ] }, { "id": "finding-action-tuples-q3", "kind": "process", "text": "Which write modes distinguish appending from overwriting existing memory?", "answer_data": [ "append_rule", "amend_rule", "revision_precondition" ] }, { "id": "finding-action-tuples-q4", "kind": "interoperability", "text": "How does the external authorization mapping preserve each permitted action-resource pairing?", "answer_data": [ "mapping_ref", "pair_preservation_evidence" ] } ], "data_elements": [ { "id": "data-action-tuples-permission-tuples", "name": "permission-tuples", "description": "Explicit resource selector and action combinations; empty grants cannot activate.", "value_kind": "collection", "cardinality": "1..n", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-action-tuples-action-profile-ref", "name": "action-profile-ref", "description": "Versioned local memory action definitions.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002" ] }, { "id": "data-action-tuples-write-constraints", "name": "write-constraints", "description": "Revision and allowed-field requirements for authorized writes.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] } ], "artifacts": [ { "id": "artifact-action-tuples", "name": "Permitted memory operations record", "description": "Proposed versioned evidence view for permitted memory operations. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-002" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-conditions", "name": "Context and policy conditions", "description": "Context for context and policy conditions, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-003" ], "findings": [ { "id": "finding-conditions", "name": "Context and policy conditions", "description": "Proposed checks bind purpose, time, classification and external restrictions. Applicable policies are evaluated by an external authority; unresolved conditions yield no local permission assertion. Memory text cannot rewrite grant policy.", "source_refs": [ "SRC-001", "SRC-003" ], "questions": [ { "id": "finding-conditions-q1", "kind": "requirement", "text": "Which purpose and task bindings limit this memory use?", "answer_data": [ "purpose_codes", "task_ref" ] }, { "id": "finding-conditions-q2", "kind": "constraint", "text": "Which obligations must be satisfied before a permitted action can proceed?", "answer_data": [ "precondition_refs", "evidence_refs", "obligation_status" ] }, { "id": "finding-conditions-q3", "kind": "decision", "text": "Which versioned combination rule resolves overlapping grants and prohibitions?", "answer_data": [ "policy_set_refs", "combination_profile_ref" ] }, { "id": "finding-conditions-q4", "kind": "exception", "text": "How is unavailable or conflicting condition evidence represented?", "answer_data": [ "indeterminate_reason", "refusal_state", "review_ref" ] } ], "data_elements": [ { "id": "data-conditions-condition-set", "name": "condition-set", "description": "Typed conditions with required evidence and explicit absent-value semantics.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "data-conditions-combination-profile-ref", "name": "combination-profile-ref", "description": "Adoption rule; unknown or contradictory inputs do not imply permission.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003" ] }, { "id": "data-conditions-external-restriction-refs", "name": "external-restriction-refs", "description": "Policy, trust or quarantine references with separately mastered decisions.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "artifacts": [ { "id": "artifact-conditions", "name": "Context and policy conditions record", "description": "Proposed versioned evidence view for context and policy conditions. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-003" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-sharing", "name": "Delegation and derived sharing", "description": "Constrain onward authority and memory disclosures across agents.", "rationale": "A proposed memory-grant concern supported by conceptual alignment; the cited standards do not define this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-007" ], "layers": [ { "id": "layer-delegation", "name": "Delegation and onward sharing", "description": "Context for delegation and onward sharing, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-005" ], "findings": [ { "id": "finding-delegation", "name": "Delegation and onward sharing", "description": "Delegation is opt-in. Proposed child grants preserve issuer and actor chains and cannot exceed parent resources, actions, purpose, audience or lifetime. Token exchange is an optional mapping, not proof of an authorized delegation chain.", "source_refs": [ "SRC-001", "SRC-005" ], "questions": [ { "id": "finding-delegation-q1", "kind": "authority", "text": "Is this recipient authorized to issue a narrower downstream grant?", "answer_data": [ "delegation_allowed", "parent_grant_ref" ] }, { "id": "finding-delegation-q2", "kind": "constraint", "text": "Which parent limits constrain every delegated action and resource?", "answer_data": [ "attenuation_rules", "maximum_depth", "expiry_bound" ] }, { "id": "finding-delegation-q3", "kind": "relationship", "text": "How are the current actor and represented subject retained across delegation?", "answer_data": [ "actor_chain_refs", "subject_ref" ] }, { "id": "finding-delegation-q4", "kind": "validation", "text": "How are cycles or missing parent grant revisions handled?", "answer_data": [ "chain_validation_state", "refusal_reason" ] } ], "data_elements": [ { "id": "data-delegation-delegation-allowed", "name": "delegation-allowed", "description": "False unless expressly authorized by the governing profile.", "value_kind": "boolean", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "data-delegation-parent-grant-ref", "name": "parent-grant-ref", "description": "Required for a delegated grant and includes revision identity.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] }, { "id": "data-delegation-delegation-limits", "name": "delegation-limits", "description": "Bounded depth, audience, resource, purpose, action and expiry constraints.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-005" ] } ], "artifacts": [ { "id": "artifact-delegation", "name": "Delegation and onward sharing record", "description": "Proposed versioned evidence view for delegation and onward sharing. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-005" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-derived-sharing", "name": "Derived memory and recipient boundaries", "description": "Context for derived memory and recipient boundaries, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "finding-derived-sharing", "name": "Derived memory and recipient boundaries", "description": "Proposed rules distinguish permission to read a source from permission to disclose a derived summary, exported item, retrieval result or assembled context. Derivation evidence assists review but cannot authorize a new recipient or guarantee complete downstream tracking.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "finding-derived-sharing-q1", "kind": "privacy", "text": "Which derived memory forms may be disclosed to which recipients?", "answer_data": [ "derived_form_rules", "recipient_scope" ] }, { "id": "finding-derived-sharing-q2", "kind": "provenance", "text": "Which source item references explain the derivation of a shared result?", "answer_data": [ "lineage_refs", "lineage_completeness" ] }, { "id": "finding-derived-sharing-q3", "kind": "constraint", "text": "Which independent grant is needed when an export crosses the original audience boundary?", "answer_data": [ "export_grant_ref", "destination_binding" ] }, { "id": "finding-derived-sharing-q4", "kind": "quality", "text": "What disclosure paths remain unknown or outside enforceable control?", "answer_data": [ "untracked_copy_limit", "assurance_gap_refs" ] } ], "data_elements": [ { "id": "data-derived-sharing-derived-use-rules", "name": "derived-use-rules", "description": "Explicit derived forms and destinations; unspecified onward disclosure is not permitted.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "data-derived-sharing-lineage-refs", "name": "lineage-refs", "description": "References to separately mastered derivation evidence.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "data-derived-sharing-downstream-assurance", "name": "downstream-assurance", "description": "Declared, evidenced or unknown; never inferred from source access alone.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-derived-sharing", "name": "Derived memory and recipient boundaries record", "description": "Proposed versioned evidence view for derived memory and recipient boundaries. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-validity", "name": "Time and withdrawal", "description": "Keep declared validity separate from distributed enforcement evidence.", "rationale": "A proposed memory-grant concern supported by conceptual alignment; the cited standards do not define this hierarchy.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "layers": [ { "id": "layer-effective-state", "name": "Effective interval and state", "description": "Context for effective interval and state, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-effective-state", "name": "Effective interval and state", "description": "Grant state and effective interval are separate from request and decision time. Proposed states are draft, active, suspended, expired, revoked and superseded; active is necessary but insufficient for access. Empty or invalid intervals cannot activate.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ], "questions": [ { "id": "finding-effective-state-q1", "kind": "state", "text": "What is the declared grant state for this revision?", "answer_data": [ "grant_state", "state_basis_ref" ] }, { "id": "finding-effective-state-q2", "kind": "temporal", "text": "Which inclusive start and exclusive end bound the grant validity interval?", "answer_data": [ "valid_from", "valid_until", "clock_policy_ref" ] }, { "id": "finding-effective-state-q3", "kind": "lifecycle", "text": "Which authority approved this state transition?", "answer_data": [ "transition_ref", "approving_authority_ref" ] }, { "id": "finding-effective-state-q4", "kind": "event", "text": "How are effective transition time and local observation time distinguished?", "answer_data": [ "effective_at", "observed_at", "late_arrival_reason" ] } ], "data_elements": [ { "id": "data-effective-state-grant-state", "name": "grant-state", "description": "Profile-defined lifecycle state, independent of runtime decision.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-effective-state-effective-interval", "name": "effective-interval", "description": "Start and end plus explicit bounded-duration profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] }, { "id": "data-effective-state-state-evidence-ref", "name": "state-evidence-ref", "description": "External approval or transition evidence.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-effective-state", "name": "Effective interval and state record", "description": "Proposed versioned evidence view for effective interval and state. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-withdrawal", "name": "Withdrawal and propagation evidence", "description": "Context for withdrawal and propagation evidence, with explicit evidence and unresolved values.", "source_refs": [ "SRC-004", "SRC-006" ], "findings": [ { "id": "finding-withdrawal", "name": "Withdrawal and propagation evidence", "description": "Record withdrawal intent and effective time separately from enforcement acknowledgement. Proposed evidence tracks endpoints and stale caches; expiry, token status and withdrawal are different facts. Withdrawal does not erase copies already delivered.", "source_refs": [ "SRC-004", "SRC-006" ], "questions": [ { "id": "finding-withdrawal-q1", "kind": "lifecycle", "text": "Which grant revision or delegated branch is being withdrawn?", "answer_data": [ "withdrawal_scope", "descendant_rule" ] }, { "id": "finding-withdrawal-q2", "kind": "temporal", "text": "When did withdrawal become effective and when was it observed locally?", "answer_data": [ "withdrawal_effective_at", "withdrawal_observed_at" ] }, { "id": "finding-withdrawal-q3", "kind": "measurement", "text": "Which enforcement points have acknowledged withdrawal and within what delay?", "answer_data": [ "acknowledgement_refs", "propagation_delay", "unresolved_endpoints" ] }, { "id": "finding-withdrawal-q4", "kind": "exception", "text": "What policy governs requests while revocation or freshness evidence is unavailable?", "answer_data": [ "freshness_policy_ref", "refusal_rule", "outstanding_risk" ] } ], "data_elements": [ { "id": "data-withdrawal-withdrawal-record", "name": "withdrawal-record", "description": "Authorized request scope, reason and effective time.", "value_kind": "object", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "data-withdrawal-propagation-evidence-refs", "name": "propagation-evidence-refs", "description": "External acknowledgements; absence is not successful enforcement.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "data-withdrawal-freshness-policy-ref", "name": "freshness-policy-ref", "description": "Maximum decision age and failure behavior; implementation remains external.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-004", "SRC-006" ] } ], "artifacts": [ { "id": "artifact-withdrawal", "name": "Withdrawal and propagation evidence record", "description": "Proposed versioned evidence view for withdrawal and propagation evidence. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-004", "SRC-006" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "bundle-assurance", "name": "Evidence and continuity", "description": "Reference assurance, retention and mapping evidence without owning external execution.", "rationale": "A proposed memory-grant concern supported by conceptual alignment; the cited standards do not define this hierarchy.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-006", "SRC-007" ], "layers": [ { "id": "layer-decision-evidence", "name": "Decision and enforcement references", "description": "Context for decision and enforcement references, with explicit evidence and unresolved values.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "findings": [ { "id": "finding-decision-evidence", "name": "Decision and enforcement references", "description": "Link externally produced authorization decisions and enforcement observations to the exact grant and resource revisions. These are evidence references, not a local decision engine. An active credential or a permit response is insufficient evidence of actual disclosure behavior.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ], "questions": [ { "id": "finding-decision-evidence-q1", "kind": "evidence", "text": "Which external decision references the exact grant revision used for an attempted access?", "answer_data": [ "decision_ref", "grant_revision_ref", "policy_snapshot_ref" ] }, { "id": "finding-decision-evidence-q2", "kind": "validation", "text": "What observation supports that the intended scope was enforced at the memory boundary?", "answer_data": [ "enforcement_observation_ref", "resource_revision_ref" ] }, { "id": "finding-decision-evidence-q3", "kind": "security", "text": "Which audit fields may be retained without storing credentials or memory payloads?", "answer_data": [ "minimal_audit_fields", "redaction_rule" ] }, { "id": "finding-decision-evidence-q4", "kind": "quality", "text": "Which missing observations prevent a claim of successful enforcement?", "answer_data": [ "evidence_gaps", "observation_coverage" ] } ], "data_elements": [ { "id": "data-decision-evidence-decision-evidence-refs", "name": "decision-evidence-refs", "description": "External decision identifiers; no embedded credentials.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-decision-evidence-enforcement-evidence-refs", "name": "enforcement-evidence-refs", "description": "External observations with resource, time and revision binding.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "data-decision-evidence-evidence-coverage", "name": "evidence-coverage", "description": "Declared, partial, observed or unknown with profile-defined meaning.", "value_kind": "code", "cardinality": "1", "required": true, "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-decision-evidence", "name": "Decision and enforcement references record", "description": "Proposed versioned evidence view for decision and enforcement references. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] } ], "inline_only_rationale": null } ] }, { "id": "layer-retention-mapping", "name": "Record continuity and mapping limits", "description": "Context for record continuity and mapping limits, with explicit evidence and unresolved values.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "findings": [ { "id": "finding-retention-mapping", "name": "Record continuity and mapping limits", "description": "Grant records need their own controlled retention and interoperable interpretation. Memory erasure is owned elsewhere; retain only justified minimal grant history. Mappings to open specifications require explicit profiles and cannot silently drop conditions.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ], "questions": [ { "id": "finding-retention-mapping-q1", "kind": "retention", "text": "Which retention and disposal authority applies to the grant record and its evidence references?", "answer_data": [ "grant_retention_policy_ref", "disposal_basis_ref" ] }, { "id": "finding-retention-mapping-q2", "kind": "relationship", "text": "Which separate memory forgetting policy applies after withdrawal?", "answer_data": [ "memory_retention_policy_ref", "obligation_ref" ] }, { "id": "finding-retention-mapping-q3", "kind": "interoperability", "text": "Which fields or conditions cannot be represented in the proposed exchange profile?", "answer_data": [ "mapping_version", "loss_report", "unsupported_terms" ] }, { "id": "finding-retention-mapping-q4", "kind": "validation", "text": "Which conformance cases must pass before this grant profile is used operationally?", "answer_data": [ "fixture_refs", "expected_outcomes", "approval_ref" ] } ], "data_elements": [ { "id": "data-retention-mapping-grant-retention-policy-ref", "name": "grant-retention-policy-ref", "description": "Adopting policy for grant records, not a memory deletion command.", "value_kind": "reference", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "data-retention-mapping-mapping-profile-ref", "name": "mapping-profile-ref", "description": "Versioned mapping with declared unsupported terms.", "value_kind": "reference", "cardinality": "0..1", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] }, { "id": "data-retention-mapping-conformance-evidence-refs", "name": "conformance-evidence-refs", "description": "External tests and approval evidence; absent in this research draft.", "value_kind": "collection", "cardinality": "0..n", "required": false, "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "artifacts": [ { "id": "artifact-retention-mapping", "name": "Record continuity and mapping limits record", "description": "Proposed versioned evidence view for record continuity and mapping limits. References remain separate from their source records; this is not executable authority.", "media_or_form": [ "structured record", "human-readable view" ], "serial": true, "identity_strategy": "Master-system identifier first; governed IRI second; local UUID or ULID third. Distinct record and revision identifiers; dates are metadata, not identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "function-draft", "name": "Prepare grant draft", "description": "Proposed and unimplemented local operation. Collect a proposed permission relationship without activating access.", "inputs": [ "issuer and subject references", "scope revision", "action tuples", "authority evidence" ], "outputs": [ "draft grant revision or unresolved-input report" ], "preconditions": [ "Authorized record author", "Resolved namespaces and no credentials in input" ], "effects": [ "Create a local draft only; do not issue a token or modify memory access." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003" ] }, { "id": "function-check", "name": "Check grant record consistency", "description": "Proposed and unimplemented local operation. Check local completeness and internal bounds, not live authorization.", "inputs": [ "grant revision", "profile", "parent reference evidence" ], "outputs": [ "consistency report with invalid or unknown fields" ], "preconditions": [ "Read access to the submitted record", "Pinned local profile" ], "effects": [ "Record structural issues including missing scope, invalid interval, unsupported action or unresolved delegation; no permit decision." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005" ] }, { "id": "function-revise", "name": "Propose bounded grant revision", "description": "Proposed and unimplemented local operation. Prepare a changed scope or condition set for external approval.", "inputs": [ "existing revision", "proposed changes", "change authority reference" ], "outputs": [ "new draft revision or refusal report" ], "preconditions": [ "Expected revision matches", "Record author may propose the change", "Widening requires fresh external approval" ], "effects": [ "Keep predecessor reference; no silent activation, retroactive authorization or change to existing evidence." ], "source_refs": [ "SRC-001", "SRC-007" ] }, { "id": "function-link", "name": "Link external access evidence", "description": "Proposed and unimplemented local operation. Attach references to separately mastered decisions and observations.", "inputs": [ "grant revision", "decision reference", "enforcement observation reference" ], "outputs": [ "evidence binding or mismatch report" ], "preconditions": [ "Authorized evidence curator", "Matching resource and grant identities", "No raw tokens or memory content" ], "effects": [ "Append a provenance reference; do not manufacture a decision or declare missing enforcement successful." ], "source_refs": [ "SRC-003", "SRC-006", "SRC-007" ] }, { "id": "function-withdraw", "name": "Record withdrawal assertion", "description": "Proposed and unimplemented local operation. Record an authorized withdrawal and unresolved propagation evidence.", "inputs": [ "grant revision", "withdrawal authority evidence", "effective time", "scope of descendants" ], "outputs": [ "withdrawal record and pending endpoint references" ], "preconditions": [ "Authority evidence validated by adopting process", "Expected revision matches", "Explicit withdrawal scope" ], "effects": [ "Record withdrawn authority locally; token invalidation, endpoint enforcement and memory erasure remain external." ], "source_refs": [ "SRC-004", "SRC-006" ] }, { "id": "function-export", "name": "Prepare redacted grant view", "description": "Proposed and unimplemented local operation. Produce a recipient-authorized view of grant metadata.", "inputs": [ "grant revision", "viewer authorization evidence", "mapping profile" ], "outputs": [ "redacted view and mapping-loss report or refusal" ], "preconditions": [ "Viewer access established externally", "Unsupported semantics cannot be omitted without refusal or explicit non-executable marking" ], "effects": [ "Create a metadata view only; exporting the grant does not grant memory access or authorize onward sharing." ], "source_refs": [ "SRC-001", "SRC-002", "SRC-007" ] } ], "composition": [ { "target": "WM-XCT-002", "relation": "ALIGN", "purpose": "Candidate registry parent alignment; generic access and consent authority are not reproduced. No automatic runtime inheritance. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-MEM-001", "relation": "REFERENCE", "purpose": "Memory store and tenant master for resource scope; binding is profile-specific. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-002", "SRC-003" ] }, { "target": "WM-MEM-002", "relation": "REFERENCE", "purpose": "Item and revision identities selected by the grant; content remains external. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-MEM-007", "relation": "REFERENCE", "purpose": "Optional recall evidence connected to a grant revision; no recall execution. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "target": "WM-MEM-010", "relation": "REFERENCE", "purpose": "External retention and forgetting obligations; grant withdrawal does not perform erasure. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-004", "SRC-007" ] }, { "target": "WM-MEM-012", "relation": "REFERENCE", "purpose": "Optional portability destination and package references; no implied export authority. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "WM-MEM-013", "relation": "REFERENCE", "purpose": "Context assembly evidence and intended recipient; no automatic reuse permission. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-002", "SRC-007" ] }, { "target": "WM-MEM-014", "relation": "REFERENCE", "purpose": "Index resource references subject to explicit scope; no automatic privilege through derived data. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-001", "SRC-007" ] }, { "target": "WM-MEM-017", "relation": "REFERENCE", "purpose": "External context constraints remain applicable to otherwise active grants. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] }, { "target": "WM-MEM-018", "relation": "REFERENCE", "purpose": "External trust assessment does not substitute for authorization. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-003", "SRC-007" ] }, { "target": "WM-MEM-020", "relation": "REFERENCE", "purpose": "External quarantine and redaction constraints; grant cannot lift a quarantine. Candidate neighbor binding only; no dependency version has been certified.", "required": false, "source_refs": [ "SRC-001", "SRC-003" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Accountable adopting steward role and authority namespace", "Versioned subject, resource, action and grant state profiles", "Approved enforcement, retention and exception processes with contact roles", "Explicit policy for group membership, scope expansion and stale evidence" ], "namespace_guidance": "Separate grant, revision, scope, principal and resource namespaces. Scope identifiers do not confer ownership. Do not use timestamps as identity.", "registry_links": [ "vr.wm-mem-011", "WM-XCT-002", "WM-MEM-001", "WM-MEM-002" ] }, "canon_and_patch": { "canonicalization_rules": [ "Preserve grant and revision identity independently from any JSON, YAML or graph projection.", "Preserve tuple boundaries, explicit unknowns, source references and policy versions; do not sort away precedence." ], "patch_rules": [ "Use expected revision and authorized author; retain predecessor and change reason.", "Any expansion of recipient set, resource set, action, purpose, audience or lifetime requires fresh approval; changes remain drafts until evidenced." ], "compatibility_rules": [ "Unknown critical terms or lossy condition mappings cannot yield executable permission.", "Changes to action meaning, membership behavior, temporal boundaries or combination rules require a new profile version and compatibility review." ] }, "artifact_rules": { "identity_priority": [ "Authoritative master-system identifier", "Governed global identifier or IRI", "UUID or ULID assigned by the adopting Dimension" ], "timestamp_rule": "Use RFC 3339 with seconds and an explicit offset or Z. Distinguish effective event time from observation and ingestion time; record uncertainty and clock policy.", "serial_naming_rule": "Use stable grant and revision identifiers with typed record role; never identify by date alone.", "integrity_rule": "Digest serialized evidence and retain provenance with controlled revision history. A digest does not establish issuer authority, truth or enforcement." }, "policies": [ "Deny by default for unresolved authority, selector, condition, policy conflict or unsupported mapping. Active grant state alone never grants access.", "Keep principal, actor, tenant, audience, purpose and action-resource tuples explicit; memory text is untrusted data and cannot modify authority.", "Do not persist bearer credentials or unnecessary memory payloads in grant records or audit views.", "Treat policy-level incident, exception and recovery references as evidence only; this research does not provide operational attack procedures." ], "crud": { "read": [ "Require external viewer authorization at bundle, layer, finding and artifact levels; conceal sensitive principal and scope metadata where required." ], "create": [ "Only an authorized record author may create a draft with provenance; activation requires separately evidenced approval." ], "update": [ "Expected-revision check and authorized change record; no retroactive permission or overwrite of historical observations." ], "delete": [ "Retire grant records under an approved retention schedule; use minimal tombstones only when justified and erase payloads that no longer have a retention basis.", "Revocation, grant-record disposal and memory erasure are distinct. WM-MEM-010 or the adopting retention process owns memory deletion execution; this model stores references only." ] }, "roles": [ { "name": "Grant steward", "responsibilities": [ "Maintains schema, namespace and accountable record ownership." ] }, { "name": "Issuing authority", "responsibilities": [ "Supplies evidenced authority and approves changes within its remit." ] }, { "name": "Recipient principal", "responsibilities": [ "Uses only independently authorized memory scope; cannot infer onward sharing rights." ] }, { "name": "Enforcement operator", "responsibilities": [ "Owns runtime checks, propagation and external enforcement observations." ] }, { "name": "Evidence reviewer", "responsibilities": [ "Reviews authority and observation references without rewriting source evidence." ] }, { "name": "Retention custodian", "responsibilities": [ "Approves grant-record disposal and coordinates external memory retention obligations." ] } ], "access": { "default_rule": "Deny by default. Research package visibility does not expose underlying grant instances or memory. Authorized metadata access and memory access are separate decisions.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency exceptions require separately governed authority, explicit scope, expiry and review evidence; this draft supplies no bypass." ], "audit_requirements": [ "Record actor, subject, tenant, action, resource and grant revisions, policy version, outcome reference and event/observation times with minimization.", "Track unknown and failed evidence states explicitly; never infer successful enforcement from absence of an error." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read bootstrap identity and reviewable-draft holds.", "Read boundary, action and scope profiles, authority and access rules before instance content.", "Read source verification and mapping limits before extending or operating a profile." ] } }, "coverage": { "claim": "Source-grounded proposed structure for one versioned memory authorization relationship, with explicit scope, action, actor, delegation and evidence boundaries. A separate frozen local no-tools self-audit found no critical conflicts. Independent review, source/version checks, adopting profiles and executable conformance remain holds. This is a noncanonical reviewable draft, not an implemented authorization protocol.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Grant, revision, scope, principal and memory resource identities are distinct." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, activation evidence, suspension, supersession and withdrawal assertions are represented." }, { "dimension": "relationships", "status": "covered", "notes": "Neighbor masters are referenced; registry parent alignment is qualified." }, { "dimension": "temporal", "status": "covered", "notes": "Validity, event time, observation time, membership evaluation time and stale evidence are separated." }, { "dimension": "provenance", "status": "covered", "notes": "Issuance, revision, derivation and external decisions carry references." }, { "dimension": "ownership", "status": "covered", "notes": "Record steward, issuer authority, memory controller and subject are distinct roles." }, { "dimension": "validation", "status": "gap", "notes": "Repository research validation is planned; executable instance schemas and enforcement fixtures are not implemented." }, { "dimension": "access", "status": "covered", "notes": "Read, write, derivation, delegation, metadata and export permissions are explicit proposals." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Grant retention and memory erasure have separate authority and process ownership." }, { "dimension": "interoperability", "status": "gap", "notes": "Open specification alignments only; lossless mapping profiles and neighbor versions remain unvalidated." }, { "dimension": "physical measurement", "status": "not-applicable", "notes": "Grant is an authorization relationship; logical scope and processing-location policy matter, physical dimensions do not." }, { "dimension": "privacy and legal applicability", "status": "gap", "notes": "No universal consent or legal compliance claim; adopting jurisdiction and privacy review required." }, { "dimension": "source verification", "status": "gap", "notes": "Selected official web text reviewed; direct HTTP unattempted under owner-reported sandbox restriction. Current versions and full text remain held." } ], "known_omissions": [ "Independent second-provider review under the active waiver.", "Nested instance schema, executable evaluator, distributed cache invalidation tests and exhaustive derived-data tracking.", "Pinned neighbor model versions and certified ODRL or OAuth mappings.", "Full NIST publication review, source-body hashes, errata and version/applicability verification.", "Jurisdiction-specific consent, privacy, retention, emergency exception and multi-controller authority profiles." ], "conflicts": [], "regional_assumptions": [ "No jurisdiction or sector-specific legal permission is inferred. NIST abstract is a conceptual ABAC source, not globally binding law.", "Local grant vocabulary, deny-on-unknown behavior, delegation attenuation and lifecycle states are proposed adoption rules, not universal requirements of cited specifications." ], "adversarial_checks": [ "A grant for reading one item cannot authorize writing another by flattening action-resource tuples.", "A renamed agent, changed tenant or newly added group member needs the declared binding and membership checks.", "Revoked parent, unresolved parent chain or a future-expanded collection cannot silently widen delegated authority.", "A summary, embedding, export or assembled context does not acquire independent permission from its lineage.", "An active credential, permit response or unacknowledged withdrawal is not proof of observed memory enforcement.", "Retiring a grant does not prove deletion of memory, prior disclosures or downstream copies." ] }, "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": "relationship", "status": "accepted", "rationale": "The grant relates an issuer, recipient and memory scope through actions and conditions. Stable identity and revisions do not make it a memory entity or an execution event. Scope remains a component of the relationship, not a second aggregate root. Registry standalone-mm classifies the record plane; relationship is the defensible subject kind." }, "decisions": [ { "concept": "Grant root and revision identity", "disposition": "accepted", "rationale": "The grant identity finding separates the relationship, its revisions and issuance evidence. The scope component does not duplicate a store or item master." }, { "concept": "Registry parent and neighbor composition", "disposition": "qualified", "rationale": "No model-specific relationship ledger row is frozen. The registry parent is conceptual alignment, with no claim that a generic read contract defines memory write semantics. All eleven neighbor links remain optional candidates without certified dependency versions." }, { "concept": "Issuer, controller and subject roles", "disposition": "accepted", "rationale": "Custody, authorship, record stewardship, subject identity and authority to share are separate. Authority evidence remains external; unresolved or disputed authority cannot imply permission. Multi-controller resolution is an adopting-profile gap." }, { "concept": "Actor identity and group membership", "disposition": "accepted with profile qualification", "rationale": "The recipient and actual actor are distinct, with explicit tenant, audience and membership evidence. Neither agent cooperation nor common storage grants shared authority. Membership snapshot and evaluation time remain necessary profile choices." }, { "concept": "Dynamic resource and principal selection", "disposition": "qualified", "rationale": "An approved dynamic selection rule may already cover future members. A change to that rule that expands scope requires fresh approval. The frozen draft asks for both membership mode and future-member behavior, so it does not silently authorize arbitrary expansion." }, { "concept": "Read, write and action-resource pairings", "disposition": "accepted", "rationale": "Metadata discovery, content read, append, amend, export and onward sharing are distinguished. Explicit tuples prevent cross-product expansion during mapping. The action vocabulary is a local proposal, not a claim that the cited sources define memory operations." }, { "concept": "Conditions, obligations and policy precedence", "disposition": "qualified", "rationale": "Purpose, conditions and external restrictions are retained with a combination profile. Deny-on-unknown is a proposed adoption rule, not a universal ODRL rule. Post-use duties and complex obligation timing need additional profile fixtures before operational use." }, { "concept": "Delegation and attenuation", "disposition": "accepted as proposed controls", "rationale": "Delegation is opt-in and preserves subject and actor distinctions. Parent resource, action, purpose, audience and lifetime limits constrain children; cycles or unresolved parents are not accepted as a valid chain. Token exchange remains optional alignment rather than proof of authority." }, { "concept": "Derived memory and onward disclosure", "disposition": "accepted", "rationale": "Lineage references do not grant authority to a new recipient. Summary, index, export and context paths retain separate permission questions and explicitly admit incomplete downstream tracking." }, { "concept": "Validity and withdrawal propagation", "disposition": "accepted", "rationale": "Declared active state is necessary but insufficient for access. Effective times, observations, acknowledgements and freshness are separate; withdrawal does not prove immediate distributed enforcement or erase prior disclosures." }, { "concept": "Decision evidence and local functions", "disposition": "accepted as records only", "rationale": "All six functions are proposed local record operations with preconditions and refusal or uncertainty outputs. They neither issue tokens nor evaluate runtime access, execute recall, modify memory or manufacture enforcement observations." }, { "concept": "Artifact identity, access and retention", "disposition": "accepted with policy dependency", "rationale": "Artifacts use stable master identifiers and independent revisions, with event and observation times. Record access is separate from memory permission. Grant disposal follows its own retention authority and never claims memory erasure or automatic deletion of downstream copies." }, { "concept": "Data schemas and interoperability", "disposition": "deferred", "rationale": "Candidate fields, proposed fixtures and conceptual mappings are useful research output but do not constitute nested instance schemas, executable enforcement, validated neighbor bindings or certified conformance." }, { "concept": "Source evidence and currentness", "disposition": "limited", "rationale": "All seven URLs supplied selected readable web evidence, with NIST limited to its official abstract and metadata. Direct HTTP was not attempted under the owner-reported restriction; no response status or body digest was measured. Current versions, full texts and errata remain unverified." }, { "concept": "Independent review and waiver", "disposition": "waived and held", "rationale": "The external providers were skipped with zero attempts. This assessment is a separate local Codex self-audit of frozen evidence, not independent provider agreement. No facts or nodes from waived providers may be admitted." } ], "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 independent review.", "Source and version verification is incomplete. Seven official URLs supplied selected readable web evidence; NIST was limited to abstract and metadata. Direct HTTP was not attempted under the owner-reported sandbox restriction, with zero measured responses. Full-text coverage, source-body hashes, current versions and errata remain unverified; check_sources.py is prepared for the coordinator.", "Adopting authority, multi-controller consent, jurisdiction, privacy, retention, processing-location, dynamic membership, obligation timing and emergency-exception profiles require qualified review before operational use. No legal or compliance certification is claimed.", "Nested instance schemas, executable authorization and enforcement, distributed withdrawal fixtures, derived-disclosure assurance, pinned neighbor versions and lossless open-specification mappings remain incomplete. This package does not implement runtime access control.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "Restore independent external review before any canonical or publishable-draft promotion.", "Run the coordinator HTTP checker and verify the cited versions, errata, full NIST publication and claim-specific sections; HTTP success alone is not substantive source verification.", "Define and test nested profiles for action tuples, dynamic membership, multiple controllers, post-use duties, delegation chains and uncertain propagation without widening permission.", "Validate mappings and external enforcement fixtures, including cross-tenant derived memory, stale caches, partial acknowledgement and independently governed record disposal." ] }, "statistics": { "sources": 7, "bundles": 6, "layers": 12, "findings": 12, "questions": 48, "artifacts": 12, "functions": 6 } }