Repository navigation
A remembered fact says which agent recorded it, in words - #42
Merged
keirsalterego merged 1 commit intoAug 2, 2026
Merged
keirsalterego merged 1 commit into
keirsalterego merged 1 commit into
Conversation
The memory panel already printed provenance. It printed a UUID. The store has carried this since the facts were first written — `memory_scope` puts the calling node's id in `run_id` precisely so a fact knows where it came from — and the panel dutifully showed it. Who told you this and when are the two axes anyone scans a memory list on, and half of that was a string with no meaning to the person reading it. That is worse than showing nothing: a raw id reads as an identifier you are supposed to recognise, so it sends someone looking for a place to look it up, and there is not one. So it resolves against the tabs that are open and says the agent's name. A fact from a session that has since been closed says "an earlier session" rather than falling back to the id, for the same reason: the id is not a thing a person can act on. It stays on hover, where someone actually debugging would want it. No migration and no new column — this is a render over data that was already there, which is what made it worth doing now rather than later.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The memory panel already printed provenance. It printed a UUID.
The store has carried this since the facts were first written —
memory_scopeputs the calling node's id inrun_idprecisely so a fact knows where it came from — and the panel dutifully showed it.Who told you this and when are the two axes anyone scans a memory list on, and half of that was a string with no meaning to the person reading it. That is worse than showing nothing: a raw id reads as an identifier you are supposed to recognise, so it sends someone looking for a place to look it up, and there is not one.
After
A fact from a session that has since been closed says so rather than falling back to the id, for the same reason: the id is not a thing a person can act on. It stays on hover, where someone actually debugging would want it.
No migration and no new column. This is a render over data that was already there, which is what made it worth doing now rather than later — it was priced as new work, and it was half-shipped.
tsc,bun testand the frontend build are clean.