Skip to content

Closes #8 Adds a "Known Limitations" section documenting the retrospective-only nature of provenance and referencing synix plan as workaround. #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Abdeltoto wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Closes #8 Adds a "Known Limitations" section documenting the retrospective-only nature of provenance and referencing synix plan as workaround. #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -62,6 +62,19 @@ sqlite3 build/search.db "SELECT artifact_id, layer_name FROM search_index LIMIT

**Architecture evolution** — Swap monthly rollups for topic-based clustering. Transcripts and episodes stay cached. No migration scripts.

## Known Limitations

Synix provenance is retrospective: it tracks which inputs and prompts
produced each artifact. However, it cannot answer forward-looking
questions such as:

> "If I change this transcript, what downstream artifacts would be affected?"

Answering this requires re-running `synix plan`.

This is a known limitation of the content-addressed caching model.


## Where Synix Fits

| | Mem0 | Letta | Zep | LangMem | **Synix** |
Expand Down