“my draft notes on the queue redesign”
Draft: the retry queue redesign feels over-engineered — revisit after the Q3 load test before proposing it.
- Scope
- personal · follows you
- Visible to
- you, in every project and tool
Use cases / Private memory
Yours. Everywhere.And only yours.
Some of what you know is not the team's business. Zephr keeps one personal memory that follows you across every project and every connected tool — and can never surface in a teammate's search, because it is never written into the index team search reads. Not a privacy setting. A wall.
Shipped — demoed live on the landing pagepersonal scopewalls not settingslocal mode available
the scopes · where a memory lives
Personalyours, in every tool
Projectthis worktree
Teamplanned · managed cloud
personal scope is never indexed for team search — the wall is at write time
Illustrative example — not live data
The problem you actually have
Shared memory is useful right up until it is yours.
Team memory answers the team's questions — but the moment everything is shared, you stop saving the half-formed thing. The draft note you are not sure about, the observation about a flaky process, the personal shortcut that would look odd in a team index: these need memory that is unambiguously yours. Without it, they go back to sticky notes and lost buffers, which is the forgetting problem all over again.
The same search, two scopes
Your own recall finds your note. The identical query run as the team finds nothing — because the note was never written into the index team search reads.
“draft notes on the queue redesign”
No results — and that is the point. Not access-denied, not redacted: not found, because the note never entered the index this search reads.
- Why
- Never indexed for this scope
Illustrative example — not live data
The wall
Three scopes. One of them is sealed.
Step through the rings. A memory's scope is chosen when it is written — and personal scope is never indexed for team search. Not filtered at read time; absent at write time. There is no permission to misconfigure.
PersonalProjectTeam
Personal scope
ring 1 of 3- Saved here
- Draft notes, personal shortcuts, half-formed observations
- Visible to
- You — in every project and every connected tool
- Team search
- Never indexed. Not filtered out — never written into the index.
The wall is structural. A personal memory is not hidden from team search — it was never written into the index team search reads. There is no permission to misconfigure.
illustrative — the rings mirror the shipped personal/project/team scope model
How it works for you
Save once. Carry it everywhere. Share nothing by accident.
The loop is deliberately boring — the entire feature is that nothing surprising can happen between step one and step three.
- 01
Save
Save it as yours
- 02
Follow
It follows you
- 03
Wall
The team cannot see it
Or
unconfirmed stays out
Suggestions that a human never confirms do not enter the durable ledger and are not recalled as settled fact.
zephr pack- 01
Save it as yours
A draft thought, a preference, a shortcut — saved to your personal scope. It never enters any shared index, from the first byte.
- 02
It follows you
Open a different project in a different tool tomorrow. Your notes are there, because they were never attached to a repository in the first place.
- 03
The team cannot see it
A teammate searching team memory gets nothing — not a redacted result, nothing. The record is not in the index their search runs against.
What exists today
All shipped — including the trade-offs.
This is the furthest-along non-code story Zephr has, so the grid below is mostly green. The honest edges are trades, not gaps: local mode gives up sync for a stricter wall, and widening a record's scope is deliberately manual.
One personal space, every project
ShippedPreferences, shortcuts, and working notes save into a space keyed to you, not to a repository — switch projects or tools and it is already there.
personal scope · cloud-persistent
Invisible to team search by construction
ShippedTeam recall queries an index your personal records are never written into. There is no visibility flag to misconfigure — the wall is which index the record enters, decided at write time.
scoped indexes — demoed live on the landing page
Three scopes, explicit at write time
ShippedPersonal, project, team. A record names its scope when it is saved, and widening a scope is a deliberate re-save — never a side effect of recall.
scope on the record, not on the query
Local mode: the stricter option
ShippedWant it never to leave the machine at all? Local mode is one file on disk, offline, no account — the same review flow and signatures, scaled to one device. No cross-device sync is the trade, stated plainly.
free · single machine
Export everything, any time
ShippedYour personal space exports as a signed file in a documented format with one command. Leaving is a workflow, not a ticket.
zephr pack
Cross-device personal sync
ShippedThe cloud path syncs your personal space between machines. Local mode deliberately does not — pick the wall you want.
cloud path
Why walls, not settings
A checkbox can be wrong. An index cannot leak what it never held.
Most tools implement privacy as a visibility flag checked at read time — one misconfiguration, one migration bug, one over-broad query away from a leak. Zephr decides at write time which index a record enters. Team search runs against the team index; your personal records were never in it. That is why the landing-page demo can let you try the leak — search a personal note as the team — and show you the refusal: the failure mode is not found rather than found but hidden.
Try the wall yourself.
The landing page has the live demo: save spaces, switch scopes, and try to read a personal note as the team. Then start free — your first personal memory takes about a minute.