Scope
Decide exactly what an AI can see
This is the heart of it. You hand intelligence a slice of your knowledge — a whole source, or a bounded project scoped by rules you set — and nothing outside that line is in the room. The boundary is enforced where the data is read, not promised on a settings page.
Available
Your sources, your switches
Work notesobsidian
Visible to AIChatGPT historychatgpt
Visible to AIPersonal journalday one
HiddenClient contractsfilesystem
HiddenReadwise highlightsreadwise
Visible to AIWhen the assistant searches, hidden sources simply don't exist to it — no results, no snippets, no citations.
01
Why it matters
Hand an AI your whole memory and you've traded one risk for another. Useful context has to be granted, scoped, and revocable — not siphoned wholesale.
02
What Nolocron provides
- Grant access at the grain you want: a whole source, or a bounded project scoped to exactly the sources you choose.
- A per-source switch turns any source off-limits to every assistant, instantly.
- Every actor — you, an assistant, an importer — runs with an explicit identity and scope; default-deny when no grant applies.
- Scope can tighten but never silently widen mid-task; the boundary is enforced in the query layer.
03
How it works
- Choose what an assistant may see — a source or a bounded project.
- It runs against that slice and nothing else.
- Revoke or narrow the grant whenever you want.
- Check what any actor was allowed to reach.
04
Proof
- Nothing runs without a known actor and scope, and no action can quietly widen its own access.
- Even you act through a scoped identity — there's no master key that silently sees everything.
- Today scope runs through sources and projects; one unified grant-anything control — hand-picked sets included — is on the roadmap.
Related