Fileosophy.

(file + philosophy)

Sections

ORIGINAL / ungated gated posture · _UNCLEARED placeholder / SRC_ batch special (_starter / _archive) app-native (exempt) naming example (a file, not a folder)

// Workflow

Production company

Project title

Project

Client

Editor — optional

Initials

Code

Date

Job number format

Job number

Type — optional

Root folder name — drag to rearrange; this is how jobs sort on disk

The root folder becomes

Working file names — drag to lead with more; files travel, folders don't

§8.2 leads a produced file with the project.

A working file becomes

stamp naming examples into the folders add an _ABOUT.txt context file to each folder add naming guidance inside file placeholders

Version and revision — the two ways a produced file changes (§8.3)

version always show the slot

Parallel takes that coexist — v01, v02 side by side. A new version never replaces the last; you keep them all and pick.

revision

Sequential passes on one thing — rev001 supersedes rev000. The old one moves to _ARCHIVE; only the latest is live.

Casing

Prefix style

Prefix padding

Prefix separator

Placeholders

show SRC_ / [variable]

Archive folders

include _ARCHIVE folders (work-in-progress folders only)

Folder numbering

forced order (off = alphabetical)

Postures (job uses)

ORIGINAL GENERATIVE STOCK ARCHIVAL

Apps used — off by default; ticking one stamps the exact folders it watches

Root folder — from Project setup

[CLIENT]_[YYMM]_[PROJECT]

Full job number — carries the type (§8.5)

Your folders

Hover a folder to add / rename / delete · drag to move · drop on the root name to move to the top level.

Bring your own folders

Paste your folder structure

Paste an indented list, an ASCII tree (├──), or Markdown bullets. Fileosophy renders it, names the root from Project setup, fills any [CLIENT] / [PROJECT] tokens it finds, and lets you download or copy it like any other workflow. Leading numbers (01_) become numbering the style knobs can toggle.

Coming soon

This workflow is on the way. Same interface, same generator — a different opinionated folder tree, built with the same care as Post Production. Pick Post Production in the selector above to explore the one that's ready.

Fileosophy.

file + philosophy

Staying organized isn't the hard part of a job — it's the quiet part. The tax you pay in the background: where does this go, what do I call it, which of the three export folders is the real one. Every one of those is a small decision skimmed off the top of the attention you'd rather spend actually making something. And the bill comes due twice — once now, and again in eighteen months when you need the project back and it's gone feral.

Because left to itself, any project turns into a graveyard: FINAL_v2_real_FINAL, a folder called stuff, three copies of what you sent to the client finds itself in three different places, and an edit session named after whatever the editor had for lunch that day. Tuna is not a version. NEW FOLDER (3) is not a location. None of it is laziness exactly — naming a file is a thoughtful decision, and one nobody wants to make at 2am.

So Fileosophy makes the decisions in advance. One structure, one naming grammar, and a folder tree that explains itself: every folder tells you what belongs in it, and every asset you didn't create — downloaded, generated, licensed, inherited — lands somewhere that remembers where it came from and whether you're actually cleared to ship it.

Decide once, up front. Now, let's go make something.