Memory Engine

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

• Project repo Current implementation source.
• Memory Engine flow diagram Public-safe diagram of contribution, response, and return logic.
• Catalog item Machine-readable project summary and related themes.

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

• Consent-Forward Systems Retention, deletion, and revocation are part of the visible structure.
• Evidence Before Polish Diagrams and bounded proof objects come before atmospheric overclaiming.
• Documentation as Interface Flow diagrams and retention notes are part of how the work is understood.

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.

Related Fleet Projects

• 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

• Project repo — Implementation truth.
• Catalog item — Public summary and related themes.
• Last reviewed: 2026-05-15

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

• Open Human-Buffer — See the clearest public consent-forward precursor.
• Open Privacy & Ethics — See the boundary layer that explains why this page stays cautious.