ADR-002: Folder Structure Design
Status: Accepted Date: December 17, 2025 Decision Makers: CODITECT Engineering Team
Context
CODITECT needs a consistent folder structure in Google Drive for:
- Project organization
- Meeting recording storage
- Team collaboration
- Asset management
Decision
Implement a hierarchical folder convention under a CODITECT root folder.
Folder Structure
CODITECT/
├── Projects/
│ └── {project_name}/
│ ├── Recordings/ # Meeting recordings
│ ├── Documents/ # Project documents
│ ├── Assets/ # Images, designs, media
│ ├── Exports/ # Generated reports
│ └── Archive/ # Archived files
├── Team/
│ └── {team_name}/
│ ├── Shared/ # Team-wide resources
│ └── Templates/ # Document templates
└── Personal/
└── {user_email}/
└── Drafts/ # Personal drafts
Implementation
async def get_or_create_project_folder(project_id: str, subfolder: str) -> str:
path = f"CODITECT/Projects/{project_id}/{subfolder}"
return await drive.get_or_create_folder_path(path)
Consequences
Positive
- Predictable file locations
- Easy to navigate manually
- Clean permission inheritance
- Simple backup strategy
Negative
- Folder creation overhead on first use
- Deep nesting for projects with many subfolders
Document Control:
- Created: December 17, 2025