Future SaaS Template
The future SaaS template defines the reusable project layout that should be considered for later products.
Summary
Section titled “Summary”Future SaaS projects should separate implementation, board memory, backups, external experimentation, and automation labs.
Why This Matters
Section titled “Why This Matters”Separation keeps implementation history, generated intelligence, experiments, and automation from contaminating each other.
Evidence Sources
Section titled “Evidence Sources”- ForYouTune board structure
- Automation plan
- Harness docs
- Source safety rules
What Happened
Section titled “What Happened”ForYouTune used a separate development repo and board repo, with external lab and automation lab boundaries defined outside the board.
Decision / Lesson / Pattern
Section titled “Decision / Lesson / Pattern”Use explicit repo and folder boundaries before adding automation.
What To Preserve
Section titled “What To Preserve”| Path Pattern | Purpose |
|---|---|
PROJECT_DEV | Main product implementation and raw project history |
PROJECT_BOARD | History-first board, generated docs, curated records, exports |
PROJECT_BACKUP | Backup and historical archives outside active automation |
PROJECT_EXTERNAL_AI_LAB | External AI experiments and study-only outputs |
PROJECT_AUTO_LAB | Automation experiments before promotion |
What To Recheck
Section titled “What To Recheck”- Whether each path has a clear write owner
- Whether the board sync has read-only access to source
- Whether external labs are prevented from becoming source of truth
Carry Forward
Section titled “Carry Forward”Start future SaaS projects with the same separation, then adapt naming and categories to the new product.