You write. Oknola files. Your agent reads.

Why a folder at all

Your instinct was right. The upkeep is what kills it.

Most people who run a business alone have already tried this: a folder of markdown, a naming scheme, a template, a weekly tidy. It works for a month. Then a busy week lands, the tidy gets skipped, and the folder turns back into a pile you have to read to use.

The folder is the answer. The tending is the part you shouldn’t be doing.

Start where you are.

Point Oknola at a folder you already keep, or start an empty one. Nothing is imported into a database, because there is no database. The files stay files, on your own disk, in the editor you like.

Oknola files what lands.

A note, a receipt, a client, a meeting: each one becomes a markdown file carrying its own fields, following OKF, the open markdown spec Google introduced in 2026. The app writes the type, the tags and the description, so you are not the one sitting there tagging.

The structure holds while you work.

Indexed Brain, our architecture, decides where a file belongs at 40 notes and at 34,000. A file that breaks the schema is fixed or refused, and that runs in both directions: what an agent writes has to conform too. Plain text all the way down, so every change is inspectable and reversible.

An agent sees what you point it at.

Tags are the permission model, not folders. A business agent gets your clients and your ledger; your journal stays dark, whatever folder it sits in. Agent off, your files never leave your device. Agent on, you chose the scope.

The exit

Leaving is copying a folder.

Delete the app and the folder is still there, readable in any editor, by you and by any AI you choose. Nothing you keep is stored in a format you would need us to open, and that holds for the paid apps too.

We would rather be the app you stay with because leaving is easy.