aislop.day
FRIDAY, 12 SEPTEMBER 2025

Minutes from the Project Folder Architecture Review

A new project received an elaborate folder structure that anticipates work nobody has created and no one has started.

3 MIN READcreative avoidance

Meeting Minutes: Project Folder Architecture Review

Meeting called by: The subject.
Attendees: The subject only.
Duration: Forty-seven minutes.


Agenda Item 1: Primary Project Structure

The subject created the root folder at 7:42pm. The folder was named with a clear, professional title. A subfolder called "assets" was created. A subfolder called "drafts" was created. A subfolder called "research" was created. A subfolder called "references" was created.

The subject noted that references and research could be confused. A subfolder called "external references" was created inside "references." The "research" folder was renamed "primary research." A subfolder called "secondary research" was created inside it.

Agenda Item 2: Version Control

The subject decided files should be versioned. A naming convention was established: project-title-v1, project-title-v2, etc. The subject created a text file documenting this convention and saved it to the root folder. The file is called "naming conventions.txt."

Agenda Item 3: Archive Protocol

The subject anticipated that older versions of files would need to be preserved. An "archive" subfolder was created inside "drafts." A sub-subfolder called "superseded" was created inside "archive."

The governing rule applies: any task adjacent to making may replace making while project folder architecture still feels productive. The folders are productive. They anticipate every phase of the project.

Agenda Item 4: Color Coding

The subject applied color labels to the primary folders. Green for active. Yellow for review. Red for archive. The color coding took eleven minutes.

Agenda Item 5: Project Readme

The subject created a README file at the root level explaining the folder structure. The README is 340 words.

Agenda Item 6: Actual Project Content

Not reached. Meeting ran long.

Action items: Begin the project.
Assigned to: The subject.
Due date: Unspecified.

TAGScreative avoidance
Share this