Internal Documentation Navigation Hub

Purpose: Internal development team navigation for restructured documentation Audience: Agents, developers, architects, and internal contributors Public Documentation: See README.md for pmorgan.tech public site

Last Updated: March 9, 2026 Status: ✅ Complete Internal Navigation System - Role-based access for development teams

Note: This navigation serves internal development workflows. For public project information, getting started guides, and user documentation, visit the main README.md which powers the pmorgan.tech website.

🚀 Quick Start by Role

Essential Briefings (Start Here)

Progressive Loading

Each essential briefing includes triggers for loading detailed documentation as needed.

🧭 Quick Navigation by Role

👨‍💼 Product Managers

🏗️ Architects

🧠 MUX Object Model (Grammar & Consciousness)

The MUX track establishes Piper’s unified object model: “Entities experience Moments in Places”

Core Philosophy:

Implementation Reference:

Patterns (in patterns/):

Developer Guides (in development/):

👨‍💻 Developers

🚀 DevOps / Release Engineering

📚 Researchers & Historians

👥 External Users

🧪 Alpha Testers

📁 Documentation Architecture

🔓 Public Documentation (public/)

External-facing content for users and developers

🔒 Internal Documentation (internal/)

Working documents for active development

Development (internal/development/)

├── active/                    # Current work by status
│   ├── in-progress/          # Active development
│   ├── pending-review/       # Files needing review
│   └── ready-for-integration/ # Completed work
├── methodology-core/         # 20 development methodologies (see INDEX.md)
├── tools/                    # Development tools and guides
└── planning/                 # Current planning cycles

Architecture (internal/architecture/)

├── current/                   # Active architectural decisions
│   ├── models/               # Hub-and-spoke model docs (39 models)
│   ├── adrs/                 # Current ADRs
│   ├── patterns/             # Established patterns
│   └── [core-specs]          # API, technical specifications
├── evolution/                # Architectural evolution tracking
└── decisions/                # Decision logs and rationale

Architecture Patterns

Developer Guides

Examples

Planning (internal/planning/)

├── current/                  # Active planning cycle
│   ├── data/                 # Planning data and analysis
│   ├── draft-issues/         # Issue development
│   ├── editorial/            # Content planning
│   └── integration/          # Integration planning
├── conversational-glue/      # M0 sprint planning docs (NEW Feb 2026)
│   ├── gap-analysis.md       # Gap analysis
│   ├── design-spec.md        # Design specification
│   └── implementation-guide.md # Implementation guide
├── audits/                   # Planning audits (NEW Feb 2026)
├── mobile-skunkworks/        # Mobile PoC planning
├── roadmap/                  # Long-term strategic planning
└── historical/               # Previous planning cycles

📚 Knowledge Base (knowledge/)

Files that exist in claude.ai project knowledge but have no other home in the repository

This folder contains files that are useful in the claude.ai web project knowledge base but don’t belong elsewhere in the docs/ hierarchy. Examples:

Note: BRIEFING-* files now live canonically in docs/briefing/ (not symlinked). The roadmap lives in docs/internal/planning/roadmap/roadmap.md.

knowledge/
├── gameplan-template.md             # Gameplan template
├── agent-prompt-template.md         # Agent prompt template
├── piper-morgan-glossary-v1.1.md    # Project glossary
├── CLAUDE.md                        # Agent entry point
├── serena-briefing-queries.md       # Live system state queries
└── README.md                        # Knowledge base workflow guide

See: knowledge/README.md for complete workflow documentation

📦 Archives & Historical Content

Historical preservation and archaeological research

Session Logs (dev/YYYY/MM/DD/)

Working documents and session logs are stored in date-stamped directories:

dev/
├── 2025/                     # Historical year
│   └── MM/DD/               # Date-stamped directories
├── 2026/                     # Current year
│   └── MM/DD/               # Date-stamped directories
└── active/                   # Current working documents

Omnibus Logs (docs/omnibus-logs/)

Weekly/monthly session consolidations - 100+ consolidated logs for historical research.

ADRs & Decisions

🎨 Assets (assets/ and docs/assets/)

Binary files and multimedia content with size management

Root Assets (assets/)

├── images/                   # Organized by purpose
│   ├── architecture/         # System diagrams
│   ├── screenshots/          # Development captures
│   └── blog/                 # Blog content (186+ files)
├── diagrams/                 # Source and generated
│   ├── source/               # Editable formats
│   └── generated/            # PNG/SVG outputs
└── documents/                # Templates and exports
    ├── templates/            # Document boilerplates
    └── exports/              # Generated documentation

Documentation Assets (docs/assets/)

└── images/                   # Documentation images
    └── alpha-onboarding/     # GUI setup wizard screenshots (5 images)

Note: docs/assets/ is for documentation-embedded images (alpha guides, user docs). Root assets/ is for general project assets.

🔍 Finding What You Need

By Work Type

By Time Period

By Content Type

🔧 Documentation Workflow

For Daily Work

  1. Check active status in relevant internal/ directory
  2. Review methodology for process guidance
  3. Create session artifacts in local dev/YYYY/MM/DD/ structure
  4. Process to archives for permanent preservation

For Research & Investigation

  1. Start with yearly index for time-based research
  2. Use monthly indices for detailed period investigation
  3. Cross-reference artifacts with session logs
  4. Follow agent collaboration patterns and handoffs
  5. Check omnibus logs for strategic insights

For New Content Creation

  1. Determine audience (public, internal, or archive)
  2. Follow asset guidelines for binary files
  3. Update navigation as needed for major additions
  4. Maintain cross-references between related content

📊 Restructuring Achievement Summary

Transformation Completed (September 20, 2025)

Key Organizational Improvements

Performance Metrics

🚀 Quick Access Links

Most Frequently Used

For New Team Members

For Research & Analysis

🆘 Help and Support

Contributing to Documentation

Comprehensive navigation system established: September 20, 2025 Supporting role-based access to restructured documentation architecture