feat(memory): let Stacky file things into the vault, not just read it - #60
Merged
Conversation
Stacky could search everything the family knows and add nothing to it.
Told "merk dir, dass Bart eine Erdnussallergie hat", it had nowhere to
put that: capture had exactly one door, and you had to be the archivist
watching a Matrix room to use it.
`stack memory capture` is that door, for the three shapes a family
actually drops into a room:
stack memory capture "Bart has a peanut allergy" --by homer
stack memory capture "https://example.com/tent" --by homer
stack memory capture --file receipt.jpg --by homer
It runs the archivist's own pipeline, so what lands here is classified,
tagged, summarised, mirrored and attributed exactly like a note pasted
into a room. `--bucket family/camping` files it under a shared topic.
The command noun sits in memory's namespace because memory owns the
vault. The handler still lives under docs/bot because the capture
pipeline does, and moving that pipeline is its own piece of work; when
it moves, this travels with it and the dispatcher changes one path.
A host `--file` is read on the host and piped to the container, which
cannot see the caller's disk. Prose citing a link stays a note rather
than being replaced by the fetched page.
arthware-dev
marked this pull request as ready for review
August 3, 2026 13:05
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
1 participant
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.
Stacky could search everything the family knows and add nothing to it. Capture had one door, and you had to be the archivist watching a Matrix room to use it.
stack memory captureis that door, for the three shapes a family drops into a room: pasted text, a link, an image or PDF. It runs the archivist's own pipeline, so what lands here is classified, tagged, mirrored and attributed exactly like a note pasted into a room.The command noun sits in memory's namespace because memory owns the vault; the handler still lives under
docs/botbecause the capture pipeline does. Moving that pipeline is its own piece of work, and when it moves this travels with it.