The OBTF philosophy
OBTF is not an app and not a productivity system. It is a philosophy of owning your text: one file that remains yours across editors, clouds, operating systems, and AI models.
Text belongs to the person who writes it. A tool should never become a prison for your own notes.
Manifesto
OBTF starts with removing what is unnecessary. You do not need a service to write down a thought. You do not need a database to find it a year later. You do not need a subscription to open your own archive.
- Notes belong to the author, not the app.
- Simplicity is a feature, not a limitation.
- Search beats hierarchy.
- Chronology preserves context.
- Format matters more than the tool.
- The system should serve thought, not the other way around.
- AI may read the archive, but it should not own it.
Principles
Ownership and portability
The file lives on your disk. It opens in any editor, can be copied, encrypted, synced, or handed to another person. Changing tools does not require a migration.
Durable format
Plain text remains readable for decades. Apps appear and disappear, clouds change their pricing, companies shut down. Text remains text.
Low friction
There should be as few actions as possible between a thought and a record. Open the file, write, close. Everything else can wait.
Search over hierarchy
People spend hours on folders, tags, and links, then search anyway. OBTF starts with search and adds structure only where it is truly needed.
Chronology over catalog
Entries follow time. A task keeps its context, a decision keeps its reason, an idea keeps the moment it appeared.
Local-first and control
The file works offline. Sync, encryption, and backups are your decisions, not a service's terms. You choose the level of privacy.
Reversibility
OBTF does not lock data into a proprietary format. It is easy to move to Obsidian, Notion, or another system — or to stay in plain text forever.
AI readiness
One text file is easy to pass to models, index, summarize, and use in RAG. No export from a closed app is required.
Main theses and benefits
| Thesis | Practical benefit |
|---|---|
| One file lowers friction | More notes and fewer abandoned thoughts: you never have to decide where a thought belongs. |
| Plain text outlives apps | The archive opens in 10–20 years without converters or subscriptions. |
| Search replaces complex structure | Less time organizing, more time thinking and working. |
| Chronology preserves context | You can see why a decision appeared and what was happening around it. |
| A local file gives control | You can encrypt, back up, and choose a cloud without vendor lock-in. |
| Open text is AI-ready | Search, summarization, and RAG are easier with local or external models. |
| No vendor lock-in | Changing an editor, OS, or cloud does not break the system or require migration. |
| Low cost of ownership | No subscription, mandatory updates, or infrastructure to maintain. |
What it gives you
- Speed. The file opens instantly and does not wait for sync.
- Longevity. The format does not depend on a company or app version.
- Focus. No feeds, notifications, sidebars, or temptation to “configure the system”.
- Savings. No subscription for notes, databases, or AI connectors.
- Privacy. The file stays local; encryption and sync are your choice.
- Flexibility. Start with one file and later add Git, Obsidian, scripts, or RAG.
What OBTF is not
- It is not an app or a SaaS product.
- It is not a task manager, a PKM framework, or a team tool.
- It is not a rejection of tools: an editor, Git, a cloud drive, and AI can all be part of the process.
- It is not a productivity contest or a requirement to write every day.
- It is not a replacement for backups, encryption, or common sense.
OBTF does not force a choice between simplicity and capability. It provides a minimal base on which you can build anything — or nothing at all.
In practice
- One
everything.txtfile in UTF-8. - New entries on top, older entries below.
- A date on its own line; markers
TODO:,DONE:,Idea:. - Search with
Ctrl+F,grep, orrg. - Regular backups and, when needed, encryption.
- Yearly archiving when the file grows large.
From there, go deeper: set up sync, enable encryption, choose an editor, and connect a paper notebook to an LLM.
How to start
You do not need to design the perfect system. Create a file, add a date, and write the first thought. Within a week you will see which markers and sections you actually need.
Start with the main OBTF guide or download the ready-made starter .txt.
Closing
Apps change. Subscriptions end. Clouds shut down. The file remains.
OBTF is not about using fewer tools. It is about freedom from them.