Session 7 β Process, Projects & Cleanup β
Goal: Review governance docs, active project trackers, and identify cleanup candidates. Estimated time: 45 min
Process & Governance β
| # | File | Lines | What It Covers |
|---|---|---|---|
| 1 | guidelines.md | ~110 | PARA frontmatter spec, agent roles, AI constraints |
| 2 | trunk-based-development.md | ~60 | TBD workflow, feature flags, migrations |
| 3 | AREAS.md | ~70 | Master index of all area docs |
Active Project Trackers β
| # | File | Lines | What It Covers |
|---|---|---|---|
| 4 | TODOS.md | 343 | Master gap tracker β 10 sections |
| 5 | TODO_BEFORE_FIRST_CLIENT.md | ~50 | Pre-launch checklist |
| 6 | PRODUCT_schema-feature-gaps.md | ~100 | Schema-level feature gaps |
Compliance Projects β
| # | File | Lines | What It Covers |
|---|---|---|---|
| 7 | gdpr-migration-plan.md | ~150 | GDPR migration plan |
| 8 | tenant-credentials-encryption.md | ~80 | Encryption plan |
| 9 | GoBD-Phase2-Implementation-Plan.md | ~100 | GoBD compliance plan |
| 10 | GoBD-Phase2-Task-Checklist.md | ~40 | GoBD task checklist |
Other Projects β
| # | File | Lines | What It Covers |
|---|---|---|---|
| 11 | docs-hub.md | ~200 | Docs portal deployment spec |
| 12 | STRATEGY_future-ideas.md | ~86 | Archived long-term visionary concepts |
Colocated App Docs (skim) β
| Location | Files |
|---|---|
apps/workspace/docs/ | fleet-and-staff-specs, dispatch-board, user-journeys, project-roadmap, ux-design-decisions, fleet-and-staff-journeys, product-requirements, pricing-screen, features |
apps/workspace/src/features/*/ | tours.md, boarding-points.md, ancillary-catalog.md, bookings.md, dispatch.md, inbox.md |
apps/booking-widget/docs/ | user-journeys, features |
apps/driver/docs/ | user-journeys, features |
Cleanup Candidates β
| File | Issue |
|---|---|
| agentic-led-company-spec.md | 382 lines β actively guiding decisions, or archive? |
π What to Validate β
- [ ] TODOS.md: go through every item. Update statuses. Many completed items (
strikethrough) remain β consider pruning. - [ ] TODOS.md has grown into containing detailed implementation specs (e.g., secrets-sync bootstrap) β extract into proper resource docs.
- [ ]
guidelines.mdreferences.antigravity/rules/base.mdfor directory structure β does that file exist? - [ ]
agentic-led-company-spec.mdat 382 lines β still relevant or speculative? - [ ] Colocated app docs: are they consistent with the central area docs? Any contradictions?
- [ ]
AREAS.md: does it list every file in2-areas/? Any missing entries?
πΊοΈ Mindmap & Path Optimization β
Grab your pen and paper:
- [ ] Assess Colocated Feature Docs vs. Central Docs: Draw the relationship between
apps/workspace/src/features/tours/tours.mdanddocs/2-areas/domain/domain-backoffice.md.- Observation: Having feature specs scattered inside the codebase is great for context, but terrible for discoverability.
- Optimization: Should
AREAS.mdact as an index that explicitly links to these colocated feature docs?
π Findings & Actions β
| Severity | File / Topic | Issue & Optimization Potential | Action Required |
|---|---|---|---|