Skip to content

Multi-Year Roadmap

2026 → 2029+ : Building Punnaraj as a five-department family organization.

Vision Statement

By 2029, Punnaraj will be a professionally-structured family organization with documented processes, clear authority, measurable outcomes, and knowledge that survives across generations.

Not to control people. To protect knowledge and ensure continuity.


Five Departments (2026-2029)

Phase 1: DEV Department (2026)

Focus: Technology, Process, Knowledge Systems
Status: ACTIVE
Timeline: Jan - Dec 2026 (12 months)
Budget: 100 units

Goals: - ✅ Build command-center observability system - ✅ Deploy MCP server on local Mac - ✅ Create control planes (Cloudflare, GitHub) - ✅ Establish evidence standards - ✅ Real family testing (observation cycles)

Key Repositories: - command-center - alpha_workspace - mcp-cloudflare, mcp-github - magga-940-secretman

Success Criteria: - System observable (what exists, what state) - Authority boundaries clear - Evidence standards followed - First family observation cycle complete - Lessons documented


Phase 2: Finance Department (2027)

Focus: Capital, Economics, Sustainability
Status: PLANNED
Timeline: Jan - Dec 2027 (12 months)
Budget: 80 units

Goals: - Design capital movement framework - Document investment principles - Create financial tracking system - Model sustainability scenarios - Train family on capital management

Key Repositories: - punnaraj-system (finance schemas) - family-vault (financial records)

Success Criteria: - Capital framework documented - Financial tracking system working - Budget allocation model tested - Family trained


Phase 3: Operations Department (2027-2028)

Focus: Coordination, Scheduling, Execution
Status: PLANNED
Timeline: Jul 2027 - Jun 2028 (12 months)
Budget: 90 units

Goals: - Build operational coordination system - Create scheduling framework - Implement task management - Document decision protocols - Enable cross-department coordination

Key Repositories: - punnaraj-mcp (operational API) - containers-punnaraj (automation)

Success Criteria: - Operations observable (active tasks, blockers) - Coordination framework working - Decision protocols followed - Cross-department communication clear


Phase 4: Production Department (2028)

Focus: Output, Deliverables, Results
Status: PLANNED
Timeline: Jan - Dec 2028 (12 months)
Budget: 100 units

Goals: - Define what "production" means for family - Create quality standards - Build delivery infrastructure - Measure outcomes - Document best practices

Key Repositories: - punnaraj-system (output schemas) - containers-punnaraj (CI/CD)

Success Criteria: - Output standards defined - Quality metrics established - Delivery process working - Best practices documented


Phase 5: HR Department (2028-2029)

Focus: People, Development, Succession
Status: PLANNED
Timeline: Jul 2028 - Dec 2029 (18 months)
Budget: 110 units

Goals: - Build people development system - Document succession planning - Create training programs - Identify future leaders - Enable knowledge transfer - Plan for generational handoff

Key Repositories: - continuity (succession planning) - punnaraj-family (people management)

Success Criteria: - People development system working - Succession plan documented + tested - Next generation trained - Knowledge transferred successfully


Budget Allocation (600 Total Units)

Phase Focus Units % Timeline
Phase 1 DEV 100 17% 2026 (12 mo)
Phase 2 Finance 80 13% 2027 (12 mo)
Phase 3 Operations 90 15% 2027-2028 (12 mo)
Phase 4 Production 100 17% 2028 (12 mo)
Phase 5 HR 110 18% 2028-2029 (18 mo)
Buffer Contingency 120 20% Ongoing

Success Metrics by Phase

Phase 1 (DEV)

  • [ ] System observable (what exists, status)
  • [ ] Authority boundaries documented
  • [ ] Evidence standards operational
  • [ ] Zero secrets in public repos
  • [ ] First family observation cycle complete (3+ months)
  • [ ] Lessons documented (LESSON-001, LESSON-002, etc)

Phase 2 (Finance)

  • [ ] Capital movement framework documented
  • [ ] Financial tracking system working
  • [ ] Budget allocation model validated
  • [ ] Family education program completed
  • [ ] Quarterly financial reports generated

Phase 3 (Operations)

  • [ ] Operations dashboard live
  • [ ] Task management system working
  • [ ] Decision protocol enforced
  • [ ] Cross-department coordination tested
  • [ ] Incident response procedures documented

Phase 4 (Production)

  • [ ] Output quality standards defined
  • [ ] Outcome metrics established
  • [ ] Delivery pipeline working
  • [ ] Best practices documented
  • [ ] Continuous improvement process active

Phase 5 (HR)

  • [ ] People development program active
  • [ ] Successor identified + trained
  • [ ] Knowledge transfer process documented
  • [ ] Succession plan tested (dry run)
  • [ ] Multi-generational continuity established

Key Principles

Sequential, Not Parallel

Build each phase to completion before starting the next. Understanding Phase 1 informs Phase 2 design.

Measure Before Optimizing

Don't speed up Phase 2 before Phase 1 is stable. Measure first, then improve.

Learning Over Shipping

Each phase teaches lessons for the next. Mistakes are valued as data.

Generational Thinking

Every decision asks: "Will the next generation understand why we chose this?"

Evidence-Based

Budget allocation based on actual learning, not predictions.


Quarterly Review Cycles

Every 3 months:

  1. Observe — What happened?
  2. Measure — Metrics + evidence
  3. Learn — What surprised us?
  4. Adjust — What's next?
  5. Document — So others can learn

No pressure to follow original plans if evidence says otherwise. Adapt as you learn.


Beyond 2029

Once all five departments are operational (2029):

  • Continuous improvement — Each department self-improves
  • Generational handoff — Train successor + transfer authority
  • Multi-generational evolution — System evolves as family grows
  • Publishing — Share methodology so other families can learn
  • Expansion — What new departments might emerge?

Current Status

Phase 1 (DEV): ✅ IN PROGRESS
- Command Center reorganization (Phase 1 complete) - MCP server deployed locally - Control planes (Cloudflare, GitHub) designed - First family observation cycle: Starting

Phase 2-5: ⏸️ WAITING
- Documented and ready - Start when Phase 1 complete


Next: Understand Family Identity System

See: /07-identity/