Aravind 76f168673a Write down what retrieval and memory actually are ...

Read from the code rather than from intent, after a conversation in which the
honest answer to "are we using RAG and memory correctly" took an hour of
digging that nobody should have to repeat.

It records three things that are easy to get wrong when describing this system
to somebody else: that retrieval is hybrid with the permission predicate as a
PRE-filter rather than a post-filter, that only two of nine agents use it and
that is the design, and that long-term memory is absent on purpose rather than
by omission — with the schema comment that says so quoted in place.

It also states what the document does NOT support claiming, because the failure
this guards against is overclaiming to a client, not under-documenting.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-10-07 19:49:04 +05:30

..

api-audit.md

agnets done

2026-08-28 11:02:02 +05:30

architecture-rag-and-memory.md

Write down what retrieval and memory actually are

2026-10-07 19:49:04 +05:30

instanced-ui-nodes.md

candidates and board ui agent issue

2026-09-05 10:46:06 +05:30