I’m trying to build a "living memory/context engine" for my business. Help me architect it.
I’m trying to build a "living memory/context engine" for my business. Help me architect it.

I’m trying to build a "living memory/context engine" for my business. Help me architect it.

I'm working on an idea I call a Context Engine and would love feedback on the architecture.

The problem: I have hundreds of projects running in parallel across different regions, teams, and timelines. A huge amount of context lives in emails, documents, spreadsheets, meeting notes, call recordings, chats, and random files. I spend too much time searching, reconstructing context, and remembering details.

The vision: a personal "living memory" system that continuously ingests information from multiple sources (email, local files, call transcripts, notes, etc.), builds a dynamic knowledge graph of projects, people, decisions, risks, and timelines, and provides context on demand.

Instead of searching for information, I want to ask things like:

- What's the latest status of Project X?

- What decisions were made about Project Y?

- What are the unresolved issues in Project Z this month?

- Summarize everything important that happened while I was away.

What architecture would you recommend for a system that acts as a continuously evolving external brain?

submitted by /u/BaronsofDundee
[link] [comments]