A full post pipeline for a working edit shop. One media-first 01_CONTENT bucket holds everything by what it is — video, audio, images, graphics, 3D — not by where it came from. Provenance is the second question, answered by posture folders (original, generative, stock, archival) at each leaf, so a licensed clip and a clip you shot yourself never get confused. Assets and delivery follow, ordered by how often you reach for them rather than by pipeline stage. It carries the complete naming grammar — versions that coexist, revisions that supersede, delivery rounds that never overwrite the last one you sent. It's the deepest, most complete tree here, so if you only open one workflow to see how the whole system thinks, open this one.

Built for the person steering the piece rather than cutting it: developing the idea, prepping and running the shoot, reviewing cuts, and keeping a curated reference library close at hand. It keeps POST's self-explaining folders and root-naming grammar, but trades the deep edit/comp/color pipeline for a director's actual rhythm — develop, shoot, review. The reference library is a first-class citizen here, because a director lives in references.

Not a project and not an edit — a standing archive that just grows. It belongs to the "references family": no per-project root, no postures, no app folders, because nothing here is produced or processed. You describe one shoot — the date, the title, the cameras, recorders, and devices that recorded it — and the builder stamps [YYYY] / [YYYYMMDD]_[PROJECT.TITLE] / with a lettered folder per source and a _MEDIA.REPORT sorted to the top. Raw source is Tier 1: files keep the names the camera gave them, and the folder path carries the provenance instead. It's the one workflow with an interactive builder, because a capture library is defined shoot by shoot rather than laid out all at once.

The maker's pipeline: model a part in CAD, export it, slice it, print it, finish it, then publish the shippable set. It borrows POST's posture engine wholesale — every model you didn't make yourself, a downloaded STL or a marketplace mesh, lands in a gated posture folder with its source recorded, so your own work never blurs with someone else's. Slice output and print settings follow a naming grammar of their own, and a remix-lineage note can travel with anything derived from another maker's file. Same why-first bones, a different craft on top.

The smallest tree, and the template for a whole family. It's a loose media-mirror for reference and inspiration material: the shape of the 01_CONTENT bucket, but relaxed — no postures, no gating — because reference isn't owned and isn't delivered, it's just looked at. You can nest it inside another workflow or use it on its own. Both CAPTURE LIBRARY and the director's reference library are descendants of this one idea: a place to keep what informs the work without pretending it's part of the work.

No preset fits every job. This one drops you at an empty root and hands you the folder tools — add a folder, name it, nest another inside, drop in a file placeholder — and you shape the tree from nothing but your own structure. Everything else still applies: the naming grammar, the settings, the same clean download. It's the escape hatch for the shape only you know you need.

Already have a structure — one you've run for years, or one you exported from here? Paste it in and Fileosophy renders it as an editable tree: rename, renumber, prune the dead branches, and download it cleaned up. It also re-opens the _ONBOARDING.md that every generated project carries, so an old structure can come back in to be viewed or extended. It meets the system where you already are instead of asking you to start over.

The same treatment is being cut for other disciplines: Production Design, Cinematographer, Screenwriting, Photoshoot Sessions (editing a shoot end to end — the counterpart to CAPTURE LIBRARY, which just keeps the raws), Vibe Coding, PARA (projects / areas / resources / archives), and Accounting. Each one starts from the same floor and asks the same question — where does this file go, and why — for a different kind of work. Until one lands, the two options above cover anything the presets don't.

No. Everything happens in your browser. When you build a structure and download it, that file is assembled right on your own machine — your folder names, your settings, your project details are never uploaded, never sent to a server, and never stored anywhere on our end. There's no account to create and nothing to sign into. Close the tab and the only trace left is the files you chose to save.

It's free. The guide and the folder-structure builder are a free tool — read everything, build a structure tuned to your job, and download it, all at no cost and with no account or sign-up. Nothing here is paywalled, and nothing gets upsold at you.

It started as the system one working post-production shop actually uses, cleaned up enough to hand to someone else. Where it goes from here may change, but the core — the guide and the builder — is free to use today. If it saves you an afternoon of folder-wrangling, that's the whole point.

If it does save you that afternoon and you feel like buying the next coffee, there's a tip jar in the footer. Completely optional, never gated behind anything — it just helps keep the tool free and getting better.

A template hands you empty folders and wishes you luck. But the folders were never the hard part — the hard part is the hundred small "where does this go, what do I call it" decisions you make on every job. Fileosophy answers those in advance and, more importantly, tells you why. Every folder explains what belongs in it, the naming grammar is built so files sort correctly and survive a move between machines, and nothing is arbitrary. An empty folder here is never a mystery — it's a labeled place waiting for the thing that goes there.

No, and you shouldn't force it. It's a superset on purpose — more than most jobs need. Delete the branches that don't apply; that's a five-second, no-stakes edit. The one thing you never have to do is invent a folder mid-project at 2am. Build down from complete rather than up from empty.

Then keep it — and steal the parts that help. Fileosophy is opinionated, but the opinions sit on a floor of plain best practices: name files so they sort, drop the spaces and special characters, stay consistent. That floor is portable — it makes any structure better, including yours. Adopt the whole thing, take one idea, or just tighten how you name files. All three are wins.

Once it's downloaded, the files are yours — rename, renumber, prune, whatever fits your shop. The structure is an opinionated starting point with the reasoning attached, not a rulebook. The guide explains why each choice was made, so when you change something, you're doing it on purpose instead of by accident.

Any of them. The structure is software-agnostic — it doesn't care whether you cut in Premiere, Resolve, or Final Cut, paint in Photoshop, or light in Blender. It's about where your files live, not which tools make them. There are a few optional spots for app-specific things like presets if you want them, but nothing about the structure is tied to a particular piece of software.

No. It's a website. You build the structure you want, download it as a set of empty folders, and unzip it wherever your project lives — local drive, NAS, cloud. There's nothing to install, no command line, no dependencies. And if the tree is simple enough that you'd rather recreate it by hand, the guide shows you the whole thing, so you can.

Yes on all counts. It's just folders, so it lives anywhere — a Mac, a PC, a NAS, a synced cloud drive — and moves cleanly between them. That portability is deliberate: the naming conventions (no spaces, no special characters, consistent case, numbers that sort) are chosen specifically to survive the trip between machines and operating systems. For a team, that's the whole point — everyone works from the same map, so there's no debate about where a file goes, and no three-people-invent-three-different-"exports"-folders drift.

That's where it's most complete today, but the ideas underneath — sort by what a thing is, make every folder explain itself, name files so they sort and survive — apply to anything that ends up as a folder someone has to open later. More workflows are on the way.

Quite possibly, and we'd like to. The set is meant to grow, and the best way to make that happen is to raise it in the Discord (link in the footer) — tell us what you do and how you'd lay it out. New workflows come from real people describing real work, so your ask genuinely shapes what gets built next.

You're not stuck waiting, either. At the bottom of the workflow selector are two build-your-own options: Build Your Own Folders starts you from an empty tree with the folder tools, and Bring Your Own Folders lets you paste a structure you already have and refine it. Both give you the same naming grammar and the same download as the built-in workflows — so you can generate exactly what you need today, and still pick up the official version once it lands.

There's a community Discord — the link's in the footer. It's the best place to ask a question, float an idea, flag something broken, or show off a structure you've tuned for your own kind of work. Worth being straight with you: this is a small, mostly one-person project, so the Discord isn't a staffed support desk — it's a room of people solving the same problems, and often another creator will have your answer faster than I would. The more everyone shares what's worked for them, the sharper the whole thing gets for the next person.