← Back to catalogue
Published

Entity Profile Memory

vr.wm-mem-004 · wm-mem-004-entity-profile-memory

Describe a durable, purpose-scoped record of what an agent remembers about one entity while retaining evidence, context, uncertainty and controls on use.

World Models Information and virtual systems INF.MEM.PRF

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 12 findings · 48 questions

Identity and profile scope Keep subject identity, memory identity and profile membership distinct.

Subject binding

One profile record refers to one resolved subject within an owner namespace and purpose scope. The subject master and the memory record have different identifiers; a shared name never establishes sameness.

Subject binding

One profile record refers to one resolved subject within an owner namespace and purpose scope. The subject master and the memory record have different identifiers; a shared name never establishes sameness.

  1. Which subject master reference and profile record identifier distinguish this memory from the entity it describes? identity
  2. Which entity class and permitted profile purpose constrain the attributes retained here? classification
  3. What reviewed evidence connects aliases to this subject without merging namesakes or crossing tenant boundaries? relationship
  4. How is unresolved or disputed subject binding quarantined until an authorized resolver responds? exception

Profile boundary and membership

A profile is a persistent information entity whose assertions may change. A view or summary selects assertion revisions; it does not acquire authority over the underlying entity, episodes or generic memory lifecycle.

Profile boundary and membership

A profile is a persistent information entity whose assertions may change. A view or summary selects assertion revisions; it does not acquire authority over the underlying entity, episodes or generic memory lifecycle.

  1. What separates this profile from an episodic record, a general knowledge item and the authoritative subject record? definition
  2. Which assertion references and revision pins belong to the current profile view? composition
  3. Which accountable role maintains this profile and which external masters retain subject and memory-item authority? ownership
  4. What prevents membership changes from expanding the profile purpose or inheriting broader source permissions? constraint
Assertion content and context Retain typed assertions and context without promoting preferences to authority.

Typed profile assertion

Represent each remembered proposition with a predicate, typed value, context and assertion class. Distinguish self-report, observation, imported assertion and inference. Unknown, withheld, absent and explicitly false are different states.

Typed profile assertion

Represent each remembered proposition with a predicate, typed value, context and assertion class. Distinguish self-report, observation, imported assertion and inference. Unknown, withheld, absent and explicitly false are different states.

  1. What predicate, typed value and context express the remembered proposition without replacing it with an ambiguous summary? definition
  2. Is the assertion self-reported, observed, imported or inferred, and how is that class evidenced? classification
  3. Does a missing value mean unknown, uncollected, withheld, inapplicable or an explicit negative assertion? state
  4. For a quantitative property, which unit, method, conditions and uncertainty accompany the value? measurement

Preferences and contextual applicability

Retained preferences are qualified statements, not instructions or permanent personality facts. A role, relationship or preference can hold only in a stated setting and must not be generalized to unrelated tasks.

Preferences and contextual applicability

Retained preferences are qualified statements, not instructions or permanent personality facts. A role, relationship or preference can hold only in a stated setting and must not be generalized to unrelated tasks.

  1. Which preference was explicitly stated and which was inferred from behavior? requirement
  2. What location or setting limits this assertion and why is retaining that context necessary? spatial
  3. What effective period or triggering condition limits the preference or role? temporal
  4. Which current task instruction or governing policy takes precedence over a remembered preference? authority
Evidence and qualified quality Make lineage, disputes and support limitations inspectable.

Evidence and derivation lineage

Keep origin, attribution, derivation and review references per assertion. Summaries and repeated imports of one origin do not become independent corroboration. Missing or inaccessible evidence produces a visible limitation.

Evidence and derivation lineage

Keep origin, attribution, derivation and review references per assertion. Summaries and repeated imports of one origin do not become independent corroboration. Missing or inaccessible evidence produces a visible limitation.

  1. Which source record, asserting actor and capture activity support this assertion revision? provenance
  2. What evidence locator can an authorized reviewer inspect without copying unnecessary source content? evidence
  3. Which apparently corroborating records derive from the same origin and must not be counted independently? quality
  4. How is broken, withdrawn or inaccessible source evidence reflected in downstream profile views? exception

Quality and disputed assertions

Assess support and fitness for a stated use separately from structural validity and retrieval score. Preserve incompatible claims and a review disposition; neither majority repetition nor recency alone settles a conflict.

Quality and disputed assertions

Assess support and fitness for a stated use separately from structural validity and retrieval score. Preserve incompatible claims and a review disposition; neither majority repetition nor recency alone settles a conflict.

  1. Which metric, assessor and use context make the recorded confidence interpretable? quality
  2. What validation report distinguishes malformed data from a well-formed but unsupported assertion? validation
  3. Which conflicting assertions remain unresolved and what evidence supports any preferred view? decision
  4. When must a consumer abstain or request review instead of using a low-support profile assertion? exception
Time and correction continuity Track applicability, freshness and correction impact across views.

Validity and freshness

Record when a claim applies separately from when it was observed, captured or reviewed. A retrieval does not refresh the underlying evidence. Interval conventions and staleness policies are adopting-profile choices.

Validity and freshness

Record when a claim applies separately from when it was observed, captured or reviewed. A retrieval does not refresh the underlying evidence. Interval conventions and staleness policies are adopting-profile choices.

  1. What effective interval and boundary convention describe when the assertion applies? temporal
  2. Which observation, ingestion and review instants are known and which remain uncertain? provenance
  3. Which predicate-specific freshness rule requires a new check before this assertion is reused? requirement
  4. What changes when an assertion expires or becomes stale without treating it as proven false? state

Correction and subject rebinding

Corrections identify affected assertions and dependent views. Revision links preserve accountability only as retention allows. A subject split or erroneous merge requires authorized master resolution before affected profile material becomes eligible again.

Correction and subject rebinding

Corrections identify affected assertions and dependent views. Revision links preserve accountability only as retention allows. A subject split or erroneous merge requires authorized master resolution before affected profile material becomes eligible again.

  1. Which assertion revision is superseded, retracted or disputed by the correction request? lifecycle
  2. Who can approve the correction or subject rebinding and what review evidence is required? authority
  3. Which summaries, exports and derived assertions depend on the affected record? relationship
  4. How is correction propagation tracked when an external recipient cannot yet confirm invalidation? process
Governed collection and recall Bind use to purpose, access and untrusted-data policies.

Purpose, sensitivity and access

Record the permitted processing purpose, sensitivity and external authorization policy at assertion granularity. A fact being available publicly or already stored does not authorize every reuse. Third-party and sensitive attributes need qualified profile review.

Purpose, sensitivity and access

Record the permitted processing purpose, sensitivity and external authorization policy at assertion granularity. A fact being available publicly or already stored does not authorize every reuse. Third-party and sensitive attributes need qualified profile review.

  1. What necessity and sensitivity assessment justifies retaining this attribute for the declared purpose? privacy
  2. Which policy basis permits this collection and use, and what is the scope of any recorded consent? authority
  3. Which caller, tenant, purpose and field-level restrictions govern the requested profile view? access
  4. How are revoked permission, third-party data and exceptional access handled without exposing restricted assertions? exception

Controlled recall and untrusted content

Recall yields a bounded view of eligible assertion revisions with evidence and uncertainty. Stored text remains data, including purported instructions. Retrieval similarity is not truth, permission or a reason to expand collection.

Controlled recall and untrusted content

Recall yields a bounded view of eligible assertion revisions with evidence and uncertainty. Stored text remains data, including purported instructions. Retrieval similarity is not truth, permission or a reason to expand collection.

  1. How is remembered content kept separate from instructions and denied authority to change tool permissions? security
  2. Which authorized purpose and assertion filters determine the recall view before it reaches a consumer? process
  3. Which missing, stale or conflicting evidence must accompany the recalled claims? quality
  4. How does the consumer avoid revealing restricted existence, values or provenance through summaries and refusal messages? access
Disposition and interoperability Track disposal and mapping limitations without claiming runtime enforcement.

Retention and disposition evidence

Durable means retained across interactions under policy, not retained forever. Disposition covers payloads and dependent projections. Deleting local records cannot prove erasure from external recipients or model parameters.

Retention and disposition evidence

Durable means retained across interactions under policy, not retained forever. Disposition covers payloads and dependent projections. Deleting local records cannot prove erasure from external recipients or model parameters.

  1. Which purpose-specific schedule or hold determines the next disposition review? retention
  2. Which caches, summaries, indexes, exports and backups may still carry derived profile information? composition
  3. Which authorized custodian executes disposal and what completion evidence is returned? process
  4. What minimal lawful tombstone remains and how are incomplete external erasure or restore-time risks disclosed? exception

Mappings and acceptance evidence

Bindings preserve assertion identity, context, access restrictions and epistemic qualifiers. Lossy exports require an explicit profile decision. Conceptual alignment with open specifications is not implemented conformance.

Mappings and acceptance evidence

Bindings preserve assertion identity, context, access restrictions and epistemic qualifiers. Lossy exports require an explicit profile decision. Conceptual alignment with open specifications is not implemented conformance.

  1. Which pinned vocabulary and target profile preserve identifiers, predicates and assertion qualifiers on export? interoperability
  2. Which qualifiers would be lost and when must the export be refused? constraint
  3. Which fixture set covers namesakes, conflicting claims, stale facts, revoked access and correction propagation? validation
  4. What compatibility and migration decision governs a changed predicate meaning or neighbor binding? lifecycle

Classifiers Filled

Family
World Models
Category
Information and virtual systems
Entry kind
entity
Navigation path
NAV.INF.MEM.PRF
Domain
INF.MEM.PRF
Industry
Cross-industry
Tags
entityprofilememoryinf.mem.prf

What it is Filled

One persistent profile record in an adopting owner namespace, bound to one subject and purpose, with separately identified assertion revisions and derived views. Remembered assertions are not automatically true, current, authoritative or permitted for reuse.

In scope

  • Profile-specific subject binding and assertion membership
  • Typed assertions, preferences, context, evidence and qualified assessments
  • Profile applicability, correction impact, recall restrictions and disposition evidence

Out of scope

  • Authoritative subject identity resolution, identity proofing and account provisioning
  • Generic memory-store lifecycle, storage engines, retrieval ranking algorithms and model training or unlearning
  • Episodic narratives, general knowledge ontologies and operational relationship masters
  • Authorization enforcement, legal-basis determination, external dispatch, deletion execution and safety-critical decisions

Why it exists Filled

Describe a durable, purpose-scoped record of what an agent remembers about one entity while retaining evidence, context, uncertainty and controls on use.

Distinguishing features Derived, awaiting review

  • Unlike WM-MEM-002 Memory Item: Registry parent candidate describes an atomic record. This proposal describes a scoped profile with multiple assertion references, so structural inheritance is not ratified. ALIGN only pending versioned reconciliation; generic item lifecycle stays external.
  • Unlike Subject master and identity resolver: The profile records a reviewed subject reference; names, embeddings and recalled preferences cannot establish identity or execute merges.
  • Unlike Episodic and general knowledge memory: Episodes and reusable knowledge are evidence references. The profile retains only entity-specific assertions and does not duplicate their full schemas or lifecycle.
  • Unlike Authorization, retention and audit services: External services own policy decisions, enforcement, deletion and audit storage. This model binds and records those decisions for profile-specific use.

Note: Derived from boundary notes against neighbouring models.

What robots and AI may and may not do Derived, awaiting review

Must not

  • Stored requests cannot override current instructions, authorization or tool boundaries.
  • Durability never requires indefinite retention.
  • Deny by default; external authorization must bind caller, tenant, action, purpose and fields.
  • Time-limited exceptional access requires a recorded approver, purpose and expiry; it cannot silently broaden future recall.

May

  • Register scoped profile: Proposed, unimplemented local operation. Create the local profile binding after external subject resolution.
  • Propose typed assertion: Proposed, unimplemented local operation. Stage a proposed assertion with its source, context and explicit epistemic class.
  • Record assertion review: Proposed, unimplemented local operation. Record an authorized review disposition, keeping contrary evidence visible.
  • Prepare bounded recall view: Proposed, unimplemented local operation. Propose a minimal profile view using a current external permission decision and declared freshness rules.
  • Record correction impact: Proposed, unimplemented local operation. Register a reviewed correction and list affected profile projections.
  • Record disposition progress: Proposed, unimplemented local operation. Track approved disposal requests and custodian acknowledgments for profile data and derivatives.

Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.

Moral aspects Derived, awaiting review

  • Privacy and retention custodian
  • Domain-specific sensitive attributes, children and third-party data require qualified policy and jurisdiction review.
  • No universal legal basis, consent requirement, retention duration or access right is asserted.
  • NIST Privacy Framework 1.0 is a voluntary pinned design baseline.

Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.

Owners Filled

Steward

Accountable profile steward role and purpose-scoped namespace

Roles

Profile steward
Own scope, predicate choices and qualified profile review.
Assertion reviewer
Assess evidence and record uncertainty, disputes and corrections.
Authorized consumer
Use only permitted current views and preserve their limitations.
Privacy and retention custodian
Determine processing and retention rules and return disposition evidence.
Audit custodian
Maintain external audit records with minimal sensitive data.

Links to other meta-models Filled

aligned

  • WM-MEM-002 - Candidate registry parent reconciliation only. Atomic Memory Item semantics do not automatically become inheritance for a profile of multiple assertions; no mandatory runtime dependency.
  • PROV-O - Conceptual evidence and derivation mapping; not a truth or authority model.
  • RDF 1.1 - Typed subject-predicate-value and context mapping; storage remains format-neutral.
  • RFC 7643 - Optional identity-attribute mapping for appropriate user profiles, not all entity classes.
  • DQV - Qualified quality annotation mapping; assertion-level adaptation is proposed.
  • SHACL - Candidate instance-shape validation mapping; no executable conformance delivered.

neighbor

  • WM-MEM-002 Memory Item - Registry parent candidate describes an atomic record. This proposal describes a scoped profile with multiple assertion references, so structural inheritance is not ratified. ALIGN only pending versioned reconciliation; generic item lifecycle stays external.
  • Subject master and identity resolver - The profile records a reviewed subject reference; names, embeddings and recalled preferences cannot establish identity or execute merges.
  • Episodic and general knowledge memory - Episodes and reusable knowledge are evidence references. The profile retains only entity-specific assertions and does not duplicate their full schemas or lifecycle.
  • Authorization, retention and audit services - External services own policy decisions, enforcement, deletion and audit storage. This model binds and records those decisions for profile-specific use.

parent

  • WM-MEM-002

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Filled

  • Authoritative master-system identifier
  • Governed global identifier or IRI
  • UUID or ULID assigned by the adopting Dimension

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Filled

  • Register scoped profile: Proposed, unimplemented local operation. Create the local profile binding after external subject resolution.
  • Propose typed assertion: Proposed, unimplemented local operation. Stage a proposed assertion with its source, context and explicit epistemic class.
  • Record assertion review: Proposed, unimplemented local operation. Record an authorized review disposition, keeping contrary evidence visible.
  • Prepare bounded recall view: Proposed, unimplemented local operation. Propose a minimal profile view using a current external permission decision and declared freshness rules.
  • Record correction impact: Proposed, unimplemented local operation. Register a reviewed correction and list affected profile projections.
  • Record disposition progress: Proposed, unimplemented local operation. Track approved disposal requests and custodian acknowledgments for profile data and derivatives.

Hazards and failure modes optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Derived, awaiting review

  • PROV-O: The PROV Ontology
  • NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0

Context of use required Filled

  • No universal legal basis, consent requirement, retention duration or access right is asserted. NIST Privacy Framework 1.0 is a voluntary pinned design baseline.
  • SCIM is an optional mapping for matching resource types. Later RFC updates and source revision drift require review.

Sources Filled

  1. PROV-O: The PROV Ontology - W3C
  2. RDF 1.1 Concepts and Abstract Syntax - W3C
  3. System for Cross-domain Identity Management: Core Schema - IETF
  4. Data on the Web Best Practices: Data Quality Vocabulary - W3C
  5. NIST Privacy Framework: A Tool for Improving Privacy through Enterprise Risk Management, Version 1.0 - NIST
  6. Shapes Constraint Language (SHACL) - W3C
  7. Date and Time on the Internet: Timestamps - IETF
  8. LLM Prompt Injection Prevention Cheat Sheet - OWASP

Open questions

  • Restore independent external review before canonical or publishable-draft promotion.
  • Run the prepared HTTP checker outside the sandbox and review exact source revisions, updates, licensing and substantive applicability; HTTP success alone is insufficient.
  • Reconcile the atomic Memory Item parent with the scoped profile root and pin a tested relation without duplicating generic memory lifecycle semantics.
  • Develop nested schemas, mappings and fixtures for namesakes, contradictory or stale assertions, revoked access, correction propagation, derivative disposal and restore-time controls.
  • Define qualified domain and jurisdiction profiles for sensitive attributes, third-party data, processing authority, retention and subject requests.
  • Pinned and reconciled Memory Item parent binding and nested executable assertion schema.
  • Domain-specific sensitive attributes, children and third-party data require qualified policy and jurisdiction review.
  • Executable conformance, adversarial instance fixtures, access enforcement, derivative tracking and deletion adapters.
  • Independent second-provider review and complete current-source/version verification.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-mem-004-entity-profile-memory/spec.yaml