Write the problem hypothesis
For [user], the agent loses or retrieves [information] incorrectly across [scope], causing [wrong action or repeated work].
You can name one user, one situation and one measurable consequence without proposing a feature.Feature Request: Team, agent, and memory-level access control
Evidence observed in vectorize-io/hindsight, a Agent Infrastructure project.
2 comments5 positive reactions85 days openProject Radar 92
Start free validation sprint4 guided steps · private notes · cloud sync
SOURCE EVIDENCE
Read original GitHub Issue ↗Start with what users actually said
Reporter context: Summary I would like to request a discussion around a more detailed permission and sharing model for the open-source Hindsight server. The current OSS authorization model seems intentionally simple: : one shared API key mapped to the configured schema. : one Supabase user JWT mapped to a schema derived from that…Excerpted from the public Issue. Read the complete thread before interpreting it.
Interview five affected users
- Which information must persist?
- For how long and within what scope?
- Show the last wrong or missing recall.
- What data must never cross boundaries?
- How do you correct memory today?
Run the smallest experiment
Test one constrained memory scope with a small real dataset and a written expected-recall benchmark.
The system retrieves the right evidence across repeated sessions without leaking or inventing context.Make a build decision
- Build: repeated pain and active commitment
- Narrow: pain is real but the audience or job differs
- Stop: weak frequency or no behavioral proof
Why this brief exists
Information has value only when it changes action. This page turns one public signal into a bounded validation exercise. It is a research aid, not proof of demand, investment advice or a product recommendation.