Memora - Projects

Introducing yourself again after switching tools

Personal context and preferences often stay inside individual conversations. At AdventureX 2024, I joined the team building Memora to explore carrying that context into the next question through a browser extension. This was a hackathon demo rather than a mature cross-platform service.

Changing tools should not require another introduction. Reconstructed demo with synthetic examples, or historical promotional material; not a complete long-term memory service. — Personal preferences belong to the user across conversation contexts. Reconstructed experience illustration.

Personal background and the current question

Historical Markdown records are processed through an external workflow into a topic-based summary. The online service supplies profile, performance, and the current question to an enhancement workflow. These paths illustrate context preparation and prompt enhancement, with continuous updating and retrieval still requiring a complete memory workflow.

Organize personal background separately from the question. Reconstructed demo with synthetic examples, or historical promotional material; not a complete long-term memory service. — Historical context preparation and current-input enhancement serve different tasks. Mechanism reconstruction.

Previewing and adopting an enhanced prompt

The extension reads the current input, requests an enhancement, and presents the returned text in a floating preview. A replacement button writes it back to the original input. This keeps the decision with the user and fits the sequence of writing, checking, and choosing a prompt.

Preview the enhancement before adopting it. Reconstructed demo with synthetic examples, or historical promotional material; not a complete long-term memory service. — Read input, request enhancement, preview it, and replace manually. Synthetic demo interaction.

The browser plugin entry point

Page adapters identify input elements, the extension background handles messages, and a Flask service queries user context and calls the external workflow. Five configured website targets describe adaptation intent; they do not establish five successful live integrations. Reconstructed screens explain the demo architecture.

Place the capability beside an existing conversation. Reconstructed demo with synthetic examples, or historical promotional material; not a complete long-term memory service. — The extension, backend service, and external workflow have separate responsibilities. Source-based architecture.

What the demo still leaves unconnected

Archived versions differ in their use of memory and process endpoints. Display controls are not fully connected to storage or backend control, while login and memory editing remain plans. The prototype makes the next engineering questions concrete: how context updates, how users control it, and how enhancement inputs can be inspected.

Input enhancement still needs a consistent memory loop. Reconstructed demo with synthetic examples, or historical promotional material; not a complete long-term memory service. — Memory updates, user controls, and input enhancement still need a consistent workflow. Prototype scope.

My first AdventureX as a participant

I co-created and helped develop the connected team demo, which led to an interview opportunity before the project stopped progressing. This 2024 participation is separate from the 2025 AdventureX event-platform work. Module ownership is not individually itemized; the lasting product decision was to separate personal context from the chat entry point and keep adoption under user control.

My contribution: a first hackathon as a participant. Reconstructed demo with synthetic examples, or historical promotional material; not a complete long-term memory service. — Team demo at AdventureX 2024, separate from the 2025 event-platform work. Includes historical promotional material.