Provenance-first
The surface must orient users around grounded memory objects, not free-floating answers.
Explore memory objects, not just generated answers.
La route memory est la porte d'entree cliente vers le retrieval BrainCaps. Elle doit rendre visible la provenance, les objets memorises, les trajectoires et les zones encore a brancher.
V1
Search, evidence framing, and route clarity before deeper editing or automation.
Trust
Users should understand what BrainCaps knows, where it came from, and how current it is.
What the memory route should make tangible
Customers need to browse memory as structured organizational intelligence, not as opaque AI output.
- Retrieval-first entrySearch and contextual recall remain the first product motion.
- Object lineageEach memory object should keep its links to source, status, and confidence cues.
- Document-to-memory bridgeIngestion outcomes should feel like durable memory, not a parser dump.
Next product endpoints worth adding
The first richer routes after the V1 shell should improve browseability, not broaden scope.
- Search route contractA dedicated `GET /api/memory/search` endpoint would reduce dashboard overloading.
- Object detail contractA dedicated object route would improve provenance and evidence display.
- Saved context viewsUseful later once customer navigation patterns are stable.
What must stay explicit
BrainCaps memory is powerful only if the customer can trust its grounding.
- No memory equals no certaintyThe UI should make absence or low confidence visible instead of implying certainty.
- Provenance over theaterShow source and status cues before decorative AI confidence theatrics.
- Correction mattersMemory must preserve what changed, not just the latest answer veneer.