The filesystem is the foundation.
Treat it like one.

Every document, project, photo, and piece of work you have ever made lives somewhere on a filesystem. It is the oldest and most personal layer of computing. And for most people it is an unmanaged pile. FileMayor exists to fix that — carefully.

1. 01

   The mess is not your fault.

   You do not lack discipline. You lack a tool that works with how humans actually accumulate files — in bursts, across contexts, without a predetermined taxonomy. Every productivity system that requires consistent upfront labelling is asking you to be a different person. FileMayor doesn't. It diagnoses what's already there and proposes a structure that fits what you made, not what you planned.

2. 02

   Reversibility is not a feature. It is the product.

   The reason people don't clean up is not laziness. It's the cost of being wrong. A file moved to the wrong place — or a folder restructured in a way that breaks something downstream — is expensive to undo. So the rational response is to not touch it at all. FileMayor inverts this: the journal makes every session fully reversible, and undo --all costs exactly one command. When the cost of being wrong approaches zero, people act.

3. 03

   The AI proposes. You decide. The machine executes.

   FileMayor is not autonomous. It will never run without approval. The AI reads your folder structure, reasons about it, and presents a plan in plain English. You read it, change whatever you want, and approve. Then the engine — not the AI — executes it, under six layers of safety checks. This is the right division of labour: AI for pattern recognition, human for judgement, software for precision.

4. 04

   Your files belong to you.

   File contents never leave the machine. Not for analysis, not for training, not for any reason. The AI sees only what you'd see in a file listing: names, sizes, paths, extensions. That is enough to reason about structure. It is not enough to read your documents. This is a deliberate constraint, not a limitation.

5. 05

   Six layers is not paranoia.

   An AI with write access to your filesystem is not a toy. We built the Chevza Doctrine — six independent safety layers, each with a single responsibility — because every previous design we tried put too much trust in a single check. Jail constrains scope. Guardrail inspects batches. Halt makes crashes safe. Architect validates semantic coherence. Security hardens input. These are not bullet points on a marketing page. They are the code that runs before anything moves.

6. 06

   Built by one person, in South Africa.

   FileMayor is not a VC-backed startup optimising for growth metrics. It is a product built to be genuinely useful, priced to sustain the person who builds it, and designed to last. The code is the founding document: every decision in it is a decision about what kind of tool this is and what kind of relationship it has with the people who use it.