The hard part was never getting agents to read files.
The hard part was giving them durable identity, current context, exact authority, safe writes, and a result another human or agent could trust tomorrow.
I started Folderbase from a practical constraint: the source of truth already exists in folders full of mixed files. Replacing those files with another proprietary knowledge container creates a new migration problem. The better primitive is an open database layer that leaves ordinary files authoritative.
AUTHORIZED WORKSPACECOMPOSED, NEVER INHERITED
Proof before theater.
A product claim should point to a protocol decision, executable proof, user workflow, or clearly stated direction. If it cannot, it is still a hypothesis.
Folderbase is being built in public through an Apache-2.0 Core, explicit architecture decisions, conformance fixtures, portable agent skills, and product proofs against real mixed-format folders. The commercial App and Cloud build on that public authority instead of inventing a private second protocol.
What I write about.
My essays focus on the operating lessons behind Folderbase: agentic filesystems, local-first architecture, permission design, safe agent delegation, and why the infrastructure beneath agents matters more than another chat surface.