Published

Memory Formation Event

vr.wm-mem-006 · wm-mem-006-memory-formation-event

Explain how one memory-item version came to exist through source lineage, method, time, responsibility and qualified confidence evidence.

World Models Information and virtual systems INF.MEM.FRM

Bundle → Layer → Finding → Questions Classifiers What it is Why it exists Distinguishing features What robots and AI may and may not do Moral aspects Owners Links to other meta-models Identity and identifiers Direct properties Recognition Capabilities and actions Hazards and failure modes Standards and interfaces Context of use Sources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 12 findings · 48 questions

Occurrence and output identity Identify the formation occurrence and the memory version whose creation it describes.

Occurrence identity

Proposed event root: the completed creation of exactly one identified memory-item version. The event description is a separate revisable record. An unconfirmed report remains a claim, not proof of formation.

Formation occurrence key

Which master-scoped identifier denotes this formation occurrence? identity
Which kind of creation does the occurrence describe? classification
Which generating activity and attempt are associated with this occurrence? event
How are repeated reports of the same occurrence distinguished from a new formation? constraint

Created version binding

A successful occurrence refers to one created item version. A batch has separate occurrences per version, optionally linked to one activity. Persistent memory contents, validity and item lifecycle are externally mastered.

Output version and source boundary

Which memory item and immutable version were created? relationship
What evidence distinguishes creation of that version from an attempted write? evidence
Which batch or co-generation context links this output to other outputs? composition
How is an imported version distinguished from its earlier origin formation? exception

Inputs and formation method Describe what influenced this version and how its creation was reported.

Input lineage

Reference source versions and selected portions without copying source masters. An input read by an activity is not automatically a derivation source for every output.

Used source and influence evidence

Reference source versions and selected portions without copying source masters. An input read by an activity is not automatically a derivation source for every output.

Which source versions and portions influenced the created memory? provenance
What distinguishes actual input use from merely available context? evidence
Which source material was omitted or transformed in forming the item? quality
How can a reviewer inspect lineage when the original source is restricted or gone? access

Method and responsibility

Record a method and responsible actor binding as reported at formation. Method execution, actor identity management and process lifecycle remain external.

Formation method declaration

Record a method and responsible actor binding as reported at formation. Method execution, actor identity management and process lifecycle remain external.

Which method and configuration version produced the memory version? process
Which operator is accountable for this formation description? ownership
Which actor performed or reviewed the formation under which delegation? authority
What reproducibility limits accompany the recorded method? validation

Time and occurrence evidence Keep creation time, observation and persistence evidence separately interpretable.

Temporal evidence

Formation is an occurrence, not the duration of an extraction run. Unknown event time remains unknown even when report ingestion time is known.

Formation and observation time

Formation is an occurrence, not the duration of an extraction run. Unknown event time remains unknown even when report ingestion time is known.

When was this memory version reported to have been completely created? temporal
When was the formation description observed and recorded? temporal
Which available causal evidence constrains the reported creation time? constraint
What uncertainty or clock discrepancy affects the temporal claim? measurement

Occurrence confirmation

Proposed description states are reported, corroborated, disputed, superseded or retracted. These describe evidence, not whether the memory is trustworthy or permitted for recall. Failed attempts with no created version belong to the activity log.

Creation evidence and report state

What evidence state applies to this occurrence description? state
Which authoritative record confirms the output existed at the stated point? evidence
How is an ambiguous persistence result represented without inventing success? exception
Which later report supersedes or retracts an incorrect formation description? lifecycle

Confidence and review evidence Expose what a reported confidence value measures and what review actually established.

Confidence semantics

A reported extraction confidence is captured with its metric definition and assessed target. Trust, factual truth, policy permission and retrieval rank are different concepts.

Formation-time confidence descriptor

A reported extraction confidence is captured with its metric definition and assessed target. Trust, factual truth, policy permission and retrieval rank are different concepts.

What claim or output segment does the confidence assessment concern? measurement
How is the confidence value defined and interpreted? definition
What value and evaluator were reported at formation time? quality
What calibration evidence and limitations support interpreting that value? validation

Review and decision references

Capture already made reviews and write-time decisions as references. Assessment, conflict resolution and quarantine execution belong to separate owners.

Formation review evidence

Capture already made reviews and write-time decisions as references. Assessment, conflict resolution and quarantine execution belong to separate owners.

Which review decision was linked to creation of this version? decision
What evidence did that review cite and what remained unresolved? evidence
Which concern or quarantine record was associated with the formation? security
What prevents a favorable review from being interpreted as blanket recall permission? constraint

Purpose and controlled disclosure Bind the occurrence description to purpose, authority and its own records policy.

Formation authority context

The description records the applicable formation authority context without granting access or evaluating permission. Tenant and subject scopes cannot be inferred from source authorship.

Purpose and scope binding

The description records the applicable formation authority context without granting access or evaluating permission. Tenant and subject scopes cannot be inferred from source authorship.

Which policy or grant version authorized the relevant formation activity? authority
For which declared purpose was this memory formed? privacy
Which tenant and subject scope constrain the event description? relationship
How is missing or subsequently revoked authority recorded? exception

Description minimization and retention

Policy governs event metadata independently of source and output payloads. Correction history must not become a reason for unlimited retention of personal data.

Lineage disclosure and disposition

Policy governs event metadata independently of source and output payloads. Correction history must not become a reason for unlimited retention of personal data.

Which audience may inspect each lineage component? access
Which retention and disposition rule applies to this event description? retention
Which identifying details can be replaced by restricted references? privacy
What minimal evidence may remain after authorized description disposal? lifecycle

Correction and exchange Keep descriptions versioned and projections honest about what they retain.

Description revision control

Correction changes the description of the event. A genuinely new item version has its own formation occurrence. The event model does not consolidate memory or choose which conflicting item is true.

Correction provenance

Correction changes the description of the event. A genuinely new item version has its own formation occurrence. The event model does not consolidate memory or choose which conflicting item is true.

Which immutable revision identifies this occurrence description? identity
Which prior description is corrected and on what evidence? provenance
How are concurrent conflicting corrections surfaced? constraint
Which separate formation occurrence describes a newly derived memory version? relationship

Interchange and validation

Proposed PROV-O and CloudEvents bindings are conceptual. A transport envelope, a provenance graph and this description have different identities and constraints.

Projection and consistency evidence

Proposed PROV-O and CloudEvents bindings are conceptual. A transport envelope, a provenance graph and this description have different identities and constraints.

How does the selected profile map occurrence, activity and output into PROV-O? interoperability
Which transport identity carries a report of the occurrence? identity
Which checks establish internal consistency of the exchanged description? validation
Which distinctions would be lost or unresolved in this projection? exception

Classifiers Filled

Family: World Models
Category: Information and virtual systems
Entry kind: event
Navigation path: NAV.INF.MEM.FRM
Domain: INF.MEM.FRM
Industry: Cross-industry
Tags: memoryformationeventinf.mem.frm

What it is Filled

A proposed format-neutral description of the occurrence completing creation of one agent-held memory-item version. The occurrence, its revisable description, generating activity and persistent item have separate identities. This is a reviewable research draft, not an execution engine or a biological memory model.

In scope

Occurrence and output-version identity, source-use and influence references, method and participant declarations.
Formation time, evidence state, qualified confidence and review references.
Purpose, scope, correction provenance and policies for this description and its artifacts.

Out of scope

Memory store operation and item content or lifecycle management.
Extraction execution, training or biological memory formation; failed attempts without a created version are activity records.
Recall ranking, context assembly, consolidation, precedence decisions, trust evaluation, quarantine and incident response.
Grant enforcement, source deletion, item erasure and portability execution.

Why it exists Filled

Explain how one memory-item version came to exist through source lineage, method, time, responsibility and qualified confidence evidence.

Distinguishing features Derived, awaiting review

Unlike WM-MEM-002 Memory Item: The created item version is externally mastered. Registry parent_ids is interpreted as a required reference, not event inheritance from a persistent item.
Unlike WM-MEM-001 Memory Store: Store context may be referenced; persistence, transaction and tenant administration remain at the store.
Unlike WM-MEM-003 Interaction Episode: An episode can be a versioned input; its participant and episode lifecycle remain external.
Unlike WM-MEM-007 Memory Recall Event: Recall uses existing memory; it does not prove formation. Reference a triggering recall only when evidenced.
Unlike WM-MEM-008 Memory Consolidation: Consolidation can generate a new version and linked formation occurrence; merging and retirement belong there.
Unlike WM-MEM-009 Memory Conflict and Precedence Rule: Reference conflict or precedence outcomes; do not choose winners here.
Unlike WM-MEM-010 Memory Retention and Forgetting Policy: Policy and disposal execution stay external; bind rules and receipts for this description.
Unlike WM-MEM-011 Memory Scope and Sharing Grant: Reference historical authority and current scope. This event never creates or enforces a grant.
Unlike WM-MEM-012 Memory Portability Package: Import lineage and external portability receipts can be linked; packaging and transfer remain external.
Unlike WM-MEM-018 Memory Trust Assessment: Formation-time confidence is a recorded descriptor, not an owned trust assessment or its lifecycle.
Unlike WM-MEM-019 Memory Poisoning Incident: Reference only an externally handled concern at policy level; investigation and remediation stay external.
Unlike WM-MEM-020 Memory Quarantine and Redaction: Write-time review and quarantine outcomes are referenced, never executed by a formation description.

Note: Derived from boundary notes against neighbouring models.

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

Must not

Formation evidence and confidence must never override current access, conflict or context policy.
Apply current audience and purpose policy to bundle, layer, finding and artifact views; do not reveal denied reference existence.
Append an authorized correction with expected revision and evidence; never mutate source, output or external decision masters.
Deny by default; evaluate current policy outside this model for every purpose, tenant and audience.
Document narrow, time-limited, authorized exceptions through an external grant; the event cannot issue its own exception.
Disposal or a restricted source can justify a redacted view, never fabricated evidence.

May

Record formation description: Proposed and unimplemented local operation. Record a claim about one created version; never execute extraction or create the memory item.
Attach lineage and method evidence: Proposed and unimplemented local operation. Attach output-specific input influence and method declarations.
Record confidence descriptor: Proposed and unimplemented local operation. Preserve reported metric context and assessment limits.
Link formation review result: Proposed and unimplemented local operation. Bind an already made decision and its scope.
Correct formation description: Proposed and unimplemented local operation. Append a justified correction while preserving lawful minimum provenance.
Validate and project a permitted view: Proposed and unimplemented local operation. Check a description against a selected local profile and produce an access-filtered representation.

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 steward
No universal legal basis, consent rule or retention duration is assumed.
NIST Privacy Framework 1.0 is a selected voluntary historical baseline; it is not asserted to be the latest edition.
Retention and privacy can remove sensitive lineage; immutable revision semantics do not require perpetual retention.

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

Owners Filled

Steward

Declare a role-based memory-system owner, governing Dimension and tenant namespace.

Roles

Memory-system owner: Defines namespace, profile, policy bindings and accountable stewardship without a commercial owner identity.
Formation recorder: Records evidence and unknowns within delegated scope; cannot infer creation from a transport acknowledgment.
Evidence reviewer: Checks source influence, receipt binding and metric interpretation; records limitations and disputes.
Privacy and retention steward: Reviews disclosure and disposition scope with external policy owners.
Projection consumer: Checks version and audience scope, handles missing data and does not promote the record into a command.

Links to other meta-models Filled

references

WM-MEM-002 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. The created item version is externally mastered. Registry parent_ids is interpreted as a required reference, not event inheritance from a persistent item.
WM-MEM-001 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Store context may be referenced; persistence, transaction and tenant administration remain at the store.
WM-MEM-003 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. An episode can be a versioned input; its participant and episode lifecycle remain external.
WM-MEM-007 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Recall uses existing memory; it does not prove formation. Reference a triggering recall only when evidenced.
WM-MEM-008 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Consolidation can generate a new version and linked formation occurrence; merging and retirement belong there.
WM-MEM-009 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Reference conflict or precedence outcomes; do not choose winners here.
WM-MEM-010 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Policy and disposal execution stay external; bind rules and receipts for this description.
WM-MEM-011 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Reference historical authority and current scope. This event never creates or enforces a grant.
WM-MEM-012 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Import lineage and external portability receipts can be linked; packaging and transfer remain external.
WM-MEM-018 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Formation-time confidence is a recorded descriptor, not an owned trust assessment or its lifecycle.
WM-MEM-019 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Reference only an externally handled concern at policy level; investigation and remediation stay external.
WM-MEM-020 - Proposed local binding based on registry purpose; semantic grounding only, not external-standard endorsement of model IDs. Write-time review and quarantine outcomes are referenced, never executed by a formation description.

aligned

W3C PROV-O - Conceptually align an output version to an entity, the generating run to an activity and the occurrence to qualified generation. Conformance is not asserted.
CloudEvents v1.0.2 - Optional envelope for a report; retain explicit occurrence identity and do not infer exactly-once creation. Conformance is not asserted.
W3C Data Quality Vocabulary - Optional measurement descriptor for confidence; no universal truth or trust scale. Conformance is not asserted.

neighbor

WM-MEM-002 Memory Item - The created item version is externally mastered. Registry parent_ids is interpreted as a required reference, not event inheritance from a persistent item.
WM-MEM-001 Memory Store - Store context may be referenced; persistence, transaction and tenant administration remain at the store.
WM-MEM-003 Interaction Episode - An episode can be a versioned input; its participant and episode lifecycle remain external.
WM-MEM-007 Memory Recall Event - Recall uses existing memory; it does not prove formation. Reference a triggering recall only when evidenced.
WM-MEM-008 Memory Consolidation - Consolidation can generate a new version and linked formation occurrence; merging and retirement belong there.
WM-MEM-009 Memory Conflict and Precedence Rule - Reference conflict or precedence outcomes; do not choose winners here.
WM-MEM-010 Memory Retention and Forgetting Policy - Policy and disposal execution stay external; bind rules and receipts for this description.
WM-MEM-011 Memory Scope and Sharing Grant - Reference historical authority and current scope. This event never creates or enforces a grant.
WM-MEM-012 Memory Portability Package - Import lineage and external portability receipts can be linked; packaging and transfer remain external.
WM-MEM-018 Memory Trust Assessment - Formation-time confidence is a recorded descriptor, not an owned trust assessment or its lifecycle.
WM-MEM-019 Memory Poisoning Incident - Reference only an externally handled concern at policy level; investigation and remediation stay external.
WM-MEM-020 Memory Quarantine and Redaction - Write-time review and quarantine outcomes are referenced, never executed by a formation description.

parent

WM-MEM-002

What else AI and robots need to interact with it Incomplete

Sources Filled

PROV-DM: The PROV Data Model - W3C
PROV-O: The PROV Ontology - W3C
Constraints of the PROV Data Model - W3C
RFC 3339: Date and Time on the Internet: Timestamps - IETF
Data on the Web Best Practices: Data Quality Vocabulary - W3C
CloudEvents Specification - CNCF
NIST Privacy Framework Version 1.0 Core - NIST

Open questions

Restore independent provider review before any canonical or publishable-draft promotion.
Verify source reachability, response integrity, editions, errata, licensing and selected claims; do not close semantic gates on HTTP success alone.
Implement and test instance schemas and mappings with replay, batch outputs, simultaneous co-generation, denied lineage, unknown time, ambiguous writes, imported replicas, stale corrections and disposal scenarios.
Develop adopting profiles for creation evidence, calibration, authorization and scoped retention using qualified review.
Independent second-provider review is absent under the owner waiver.
Direct HTTP checks are unattempted because the sandbox blocks them; HTTP status and body digests remain unmeasured. Browser-mediated selected content was reviewed, not independently verified.
Dated DQV edition, current source versions and errata, licenses and profile applicability still need verification.
Concrete nested instance schemas, executable mappings, conformance fixtures and pinned neighbor versions are not implemented.
No validated calibration profile, identity federation scheme, exactly-once persistence guarantee or legal basis determination is supplied.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-mem-006-memory-formation-event/spec.yaml