Documentation · SOP format

Filing rules in plain English.

Standard Operating Procedures are markdown files that describe how you want files organized. The SOP parser converts them into deterministic operations that flow through the Curative Triad like any other plan.

Example

An SOP file is a markdown file.

No special syntax. Headings group rules. Bullet lists enumerate cases. The parser handles ambiguity by surfacing it for confirmation rather than guessing.

# Personal Filing SOP

Move every screenshot to ~/Pictures/Screenshots, organized by year.
Move installers (.exe, .dmg, .pkg) to ~/Software.
Archive any .zip or .tar.gz older than 6 months to ~/Archive.

Documents:
- Receipts (PDFs with "receipt" or "invoice" in the name) → ~/Documents/Receipts
- Anything from "scanner" → ~/Documents/Scans
- Resumes → ~/Documents/Career

Never touch ~/Downloads/Inbox — it's my staging area.
Trash anything in ~/Downloads/Trash older than 30 days.

How it works

Three steps.

1. Parse.The SOP file is sent to the configured AI provider (Gemini 2.0 Flash by default) along with the directory inventory. The provider returns a structured plan.
2. Doctrine.The plan flows through the same six layers as any other Curative plan — Jail, Vault, Guardrail, Halt, Architect, Security. SOPs cannot bypass the safety architecture.
3. Apply.Run filemayor apply to execute. Run filemayor undo --all to reverse if you change your mind.

Status

SOP parsing is a Pro feature. Free tier supports manual organization via the organize command.