Skip to content

Documentation Restructure Proposal

Purpose: Redesign the documentation to be clear, actionable, and cognitively manageable

Current Problems

  1. Duplicate files - Same content in /Docs/ and /3-REFERENCE-DETAILS/
  2. Cognitive overload - Main points buried with nice-to-haves
  3. Meta statements - Internal notes visible to readers who don't need them
  4. No clear entry point - Multiple "executive summaries" competing
  5. Inconsistent language - Sattva app vs. Sattva principle, varying terminology
  6. File-level assumptions - Scattered and not tracked

Proposed Structure

AoL-DC-Center/
│
├── README.md                    # Entry point - navigation only (no content duplication)
│
├── _META/                       # Meta files that DRIVE the project (not for general readers)
│   ├── ASSUMPTIONS.md           # Central assumption registry
│   ├── PRIORITIES.md            # Working consensus on priorities
│   ├── GLOSSARY.md              # Terminology definitions (Sattva, intro session vs talk, etc.)
│   ├── DECISIONS-LOG.md         # Key decisions made and rationale
│   └── IDEAS-BACKLOG.md         # Nice-to-haves, future possibilities, parking lot
│
├── 1-STRATEGY/                  # WHY and WHAT (for board, leadership)
│   ├── VISION.md                # One-page vision and goals
│   ├── BOARD-PROPOSAL.md        # Crisp board presentation (stories + ask)
│   └── DOMAIN-BRIEF.md          # Market context, positioning (reference)
│
├── 2-CAMPAIGNS/                 # IMMEDIATE ACTIONS (for campaign leads)
│   ├── World-Meditation-Day.md  # WMD campaign - complete playbook
│   └── Mega-Course-January.md   # Mega Course campaign - complete playbook
│
├── 3-FOUNDATIONS/               # PARALLEL INFRASTRUCTURE (for enabler leads)
│   ├── Communication-Systems.md # Basic streamlining, tools, channels
│   ├── Neighborhood-Presence.md # Outreach strategy and partnerships
│   ├── Center-Presentation.md   # Physical space improvements
│   └── Volunteer-Engagement.md  # Roles, activation, retention
│
├── 4-REFERENCE/                 # HOW details (for executors, when needed)
│   ├── Messaging-Templates.md   # All templates in one place
│   ├── Contacts-Directory.md    # Property managers, venues, partners
│   ├── Metrics-Framework.md     # What to track, how to measure
│   ├── Technical-Setup.md       # IT team reference
│   └── Research-Citations.md    # SKY research for credibility
│
└── 5-ARCHIVE/                   # Old versions, superseded docs
    └── (move current /Docs/ contents here)

Meta Files Explained

_META/ASSUMPTIONS.md (exists - keep)

Central registry of confirmed and unresolved assumptions. All docs reference this.

_META/PRIORITIES.md (new)

# Working Priorities

## Immediate (Now)
- WMD Campaign (Dec 21) - 3 weeks
- Mega Course (Jan) - ongoing, first in ~1 month
- Basic Communication Streamlining

## High Priority (Parallel)
- Neighborhood Presence

## Backlog (Earliest Opportunity)
- Center Presentation / Digital Kiosk
- Deeper IT Infrastructure

## Beyond 6 Months
- Entrance Construction
- Major Physical Changes

_META/GLOSSARY.md (new)

# Glossary

**Sattva** - Sanskrit for purity, harmony, goodness. Guides how we interact. NOT the Sattva app (that's central body's domain).

**Intro Session / Intro Talk** - Free 60-90 min educational session introducing SKY breathing. Gives partial experience.

**Core Journey** - Intro Session → SKY Course → Sahaj Samadhi → Silent Retreat

**Participant** - Someone attending our programs (preferred over "customer" or "client")

**Graduate** - Someone who completed SKY Course

**Ambassador** - Graduate who actively brings others

_META/DECISIONS-LOG.md (new)

# Decisions Log

| Date | Decision | Rationale | Decided By |
|------|----------|-----------|------------|
| 2024-12-06 | Sattva = principle, not app funnel | App conversion is central body's domain | BMad |
| 2024-12-06 | Whitney Building = brief mention only | Byproduct of execution, not strategic focus | BMad |
| 2024-12-06 | IT team builds, volunteers use familiar tools | Reduce cognitive load on general volunteers | BMad |

_META/IDEAS-BACKLOG.md (new)

# Ideas Backlog

Nice-to-haves and future possibilities. Not in scope now but captured for later.

## Center Improvements
- Digital kiosk system (prioritized in backlog)
- Garden beautification / "Nature does Yoga" corner
- Entrance construction (beyond 6 months)

## Technology
- Advanced CRM integration
- Automated retention workflows
- Metrics dashboard

## Partnerships
- Embassy meditation programs
- Corporate wellness packages
- Healthcare facility partnerships

## Programs
- FitDC graduate conversion ($50 in-person repeat)
- Teacher training pipeline

Document Principles

1. Separate "Main Points" from "Nice-to-Haves"

Each document should have: 

## [Main Content]
Clear, focused, actionable

---

## Notes & Considerations
<details markdown="1">
<summary>Additional details (click to expand)</summary>

- Nice-to-have ideas
- Alternative approaches considered
- File-level assumptions

</details>

Using <details> tags keeps secondary info available but collapsed.

2. File-Level Assumptions

Each document ends with: 

---

## Assumptions in This Document

- [A1] Volunteers available for X role
- [A2] Budget approved for Y
- [A3] Timeline assumes Z

*See _META/ASSUMPTIONS.md for project-wide assumptions*

3. No Meta Statements in Main Content

Remove things like: - "This document reflects..." - "As discussed in the planning session..." - "Per our strategy..."

Just state the content directly.

4. Single Source of Truth

  • ONE messaging templates file (not 3 versions)
  • ONE contacts directory
  • ONE volunteer structure definition
  • Reference via links, don't duplicate

Migration Plan

Phase 1: Create Structure

  1. Create _META/ folder with new meta files
  2. Create numbered folders (keep existing content in place for now)

Phase 2: Consolidate

  1. Move current ASSUMPTIONS.md to _META/
  2. Merge duplicate files (keep best version)
  3. Archive old versions to 5-ARCHIVE/

Phase 3: Rewrite Key Docs

  1. Update README.md as navigation-only
  2. Rewrite BOARD-PROPOSAL.md (crisp, no meta statements)
  3. Update campaign docs with consistent language

Phase 4: Clean Up

  1. Add file-level assumptions to each doc
  2. Add collapsible "Notes & Considerations" sections
  3. Remove meta statements from main content

Questions for You

  1. Does this structure make sense for how you'll use these docs?
  2. Should _META/ be visible to all readers or truly hidden (e.g., ._meta/)?
  3. Any folders/categories missing?
  4. Ready to proceed with migration?