Atlas node · Scenes / Systems · public-safe excerpt

Memory Engine

Participant-facing memory environment tying invitation, retention, retrieval, decay, and revocation into one local-first room system.

Repository →

What remains in the room

Memory Engine treats memory as behavior, not storage. Invitation, return, forgetting, and revocation become parts of the room instead of policies hidden behind it.

The work sits in the fragile space between offering a trace and keeping that trace from becoming extraction. A memory system has to explain what it keeps, what it releases, and how a participant can still refuse.

The flow diagram, catalog record, and source trail let the public page show structure without making participant material carry the proof.

The strongest public version stays partial, redacted, and careful. The page should make retention and revocation legible without exposing the people whose traces give the work its weight.

What it is

Memory Engine is a room-facing memory system where contribution, retrieval, forgetting, and revocation are part of the artwork's visible behavior. Publicly, it should read as a bounded systems and ethics stub until stronger proof objects are surfaced safely.

What it lets people do

It lets a reader understand memory as designed system behavior rather than as passive storage, while keeping the public framing careful about participation, retention, and room context.

What is public now

Evidence status

Status: public-safe excerpt. The project has a clear public thesis and a source trail, but stronger public proof should remain diagrammatic and redacted until retention, retrieval, and participant-flow artifacts can be shown safely.

Next proof object: Redacted interface or kiosk capture paired with a short note on retention, retrieval, and revocation behavior.

Boundary note

This page intentionally avoids participant imagery, room-specific details, and any retention example that would overexpose the work's private or personal dimensions.

What remains unresolved

  • The page should not imply public deployment or participant outcomes beyond the current source trail.
  • A public-safe example of the retrieval or decay behavior would make the core idea more concrete.
  • The retention and revocation logic needs a stronger public-facing note if the page expands.

Methods surfaced

Proof objects

  • Memory Engine flow diagram Status: public. Public-safe diagram of contribution, response, and return logic.
  • Catalog item Status: public. Machine-readable public summary and relationship context.
  • Redacted interface or kiosk capture Status: needed. Still needed to show retention, retrieval, and revocation behavior without exposing participants.
  • Human-Buffer Shares the consent-forward interface and refusal logic that shapes participant entry.
  • machine-docs Supports the diagrams, ops notes, and retention logic that make the system legible.
  • live-rig Connects the room-facing scene branch to a larger performance and operations topology.

Source trail

The Atlas is the relationship layer. Use the repository for current project-specific truth, and use studio-notes when methods, decisions, or teaching material need to travel across the fleet.

Where to go next