access sequence
- 01 A tool asks
- 02 You see the scope
- 03 You allow, deny, or revoke
- 04 The action is logged
TOOLS ASK FIRST / DATA STAYS YOURS / HISTORY STAYS VISIBLE
Software should come to it.
groundware lets tools request access to the files, notes, folders, and context you already control, without becoming the place that owns everything.Your notes stay where they are. Tools only see what you allow.
how access works
groundware shows what a tool is asking for, what it can access, how long access lasts, and what happened after.
access sequence
access.log
your-data
notes stay markdown folders are shared by choice tools only see what you allow access can expire history stays visibleyour data stays yours
groundware starts from the files and notes people already control. For Obsidian, that means your notes stay markdown and your vault stays recognisable.
Tools can ask for access to a folder without seeing the whole vault.
ways in / routes
Routes are different ways for software to come to user-owned data. They aren't separate places to put everything.
folder layer
The homepage gives the core story. The folders hold the notes, logs, principles, and system details.
private beta
We’re opening the first ground routes soon. Get notified when private beta access is ready.
30-second version
/readme/start-here.md
groundware lets software come to the data people already control. Tools ask for scoped access, users decide what is visible, and the history stays readable.
what tools can see
/access/request
what happened
/system/access.log
Most software becomes useful by asking people to move their work into a new place. groundware starts from the opposite direction: keep the files, notes, folders, and context where they are, and let software request access to what it needs.
The tool becomes temporary. The data stays durable.
A grant should not quietly become a permanent doorway. If a tool needs research notes for an hour, the permission should say that.
Expiration makes access feel more like a choice and less like a leak.
Local files are durable, inspectable, and easy to move. They are not the old thing to escape from. They are often the most stable thing in the workflow.
The interesting future is not abandoning files. It is giving software better manners around them.
Interfaces should be allowed to change. People should be able to try new tools, add agents, or leave platforms without rebuilding their memory from scratch.
The durable layer should be the data and the visible access history around it.
Obsidian comes first because markdown vaults already behave like user-owned data. The vault is local, portable, and meaningful before groundware arrives.
The point is not to replace the vault. The point is to let software ask for access around it with better boundaries.
groundware is being built by people who want software to ask before it reads, leave a visible history behind, and let users keep their files, notes, and context where they already are.
The first route is Obsidian. The access layer comes first.
principles only
/principles/data-outlives-apps.md
structured spaces
/contexts
A context is a portable space for a specific kind of work, memory, or decision-making.
Meetings, decisions, handoffs, and project memory
Sources, notes, claims, and references
Agendas, notes, actions, and follow-ups
Records, household memory, and private notes
your layer
/ground/yours
Yours is the home for your files, notes, contexts, connected tools, access history, and identity.
It's not another account. It's the place accounts ask permission to enter.
record
groundware is opening its first route soon. Email us and we’ll send a note when it’s ready.
For early builders making apps, plugins, agents, or integrations that come to user-owned data.
Email us what you want to build and we’ll send preview docs when the SDK is ready.