Skip to content

ASO Universal Consciousness System - Documentation Index ​

Last Updated: 2025-01-16
Content-Type: Explanation
Audience: All
Purpose: Comprehensive hierarchical documentation of the ASO system


πŸ“š Documentation Structure ​

This documentation follows a hierarchical structure with DiΓ‘taxis content types for easy navigation:

aso-docs/
β”œβ”€β”€ 00-OVERVIEW.md                     # Start here - Complete system overview
β”œβ”€β”€ 01-CLIENT-VISION-CANON-v2.md        # Canonical client vision contract (current)
β”œβ”€β”€ 01-CLIENT-VISION-AND-ALIGNMENT.md   # Historical baseline (superseded)
β”œβ”€β”€ 02-CORE-SYSTEMS/                   # Core backend systems
β”‚   β”œβ”€β”€ Memory-System/
β”‚   β”‚   β”œβ”€β”€ README.md                  # Overview (Explanation)
β”‚   β”‚   β”œβ”€β”€ Tutorials/                  # Step-by-step learning
β”‚   β”‚   β”œβ”€β”€ How-to/                      # Task-focused guides
β”‚   β”‚   β”œβ”€β”€ Reference/                   # API, schemas, facts
β”‚   β”‚   └── Explanation/                 # Architecture, design
β”‚   └── [Other 15 systems]/             # Same structure
β”œβ”€β”€ 03-PLATFORMS/                      # Platform-specific documentation
β”‚   └── [Each platform]/                # Same hierarchical structure
β”œβ”€β”€ 04-FEATURES/                       # Feature-specific documentation
β”‚   └── [Each feature]/                # Same hierarchical structure
β”œβ”€β”€ 05-INTEGRATIONS/                   # Integration documentation
β”‚   └── [Each integration]/            # Same hierarchical structure
└── 06-ARCHITECTURE/                   # System architecture & diagrams
    └── [Each architecture doc]/        # Same hierarchical structure

DiΓ‘taxis Content Types ​

Each system/platform/feature is organized by content type to match user intent:

  • Tutorials (Action + Acquisition) - Step-by-step learning guides
  • How-to Guides (Action + Application) - Task-focused instructions
  • Reference (Cognition + Application) - Precise, factual information
  • Explanation (Cognition + Acquisition) - Deep context and architecture

πŸš€ Quick Start ​

  1. New to the project? β†’ Start with 00-OVERVIEW.md
  2. Understanding client vision? β†’ Read 01-CLIENT-VISION-CANON-v2.md
  3. Working on a specific platform? β†’ Check 03-PLATFORMS/
  4. Implementing a feature? β†’ See 04-FEATURES/
  5. Understanding architecture? β†’ Review 06-ARCHITECTURE/

πŸ“– Main Documents ​

00-OVERVIEW.md ​

Complete system overview including:

  • System architecture
  • Core components
  • Technology stack
  • Current implementation status
  • System flow diagrams

01-CLIENT-VISION-CANON-v2.md ​

Canonical client vision contract:

01-CLIENT-VISION-AND-ALIGNMENT.md ​

Historical baseline alignment analysis (superseded):

  • Original vision capture
  • Earlier gap matrix and roadmap snapshots

πŸ“ Documentation Sections ​

02-CORE-SYSTEMS/ ​

Core backend systems documentation (hierarchical with DiΓ‘taxis content types):

03-PLATFORMS/ ​

Platform-specific documentation (hierarchical with DiΓ‘taxis content types):

04-FEATURES/ ​

Feature-specific documentation (hierarchical with DiΓ‘taxis content types):

05-INTEGRATIONS/ ​

Integration documentation (hierarchical with DiΓ‘taxis content types):

06-ARCHITECTURE/ ​

System architecture documentation (hierarchical with DiΓ‘taxis content types):


πŸ“Š Documentation Status ​

Last Updated: 2025-01-16

Completed βœ… ​

  • High Priority Core Systems: 8 systems documented
  • High Priority Frontend: 3 major UIs documented
  • High Priority Discord Bot: Architecture documented

See DOCUMENTATION-STATUS.md for complete status.


πŸ”„ Documentation Maintenance ​

This documentation is living and updated during each interaction. Key principles:

  1. Primary Source: docs/project_status.md is the central document - extract all information from it first
  2. Hierarchical Structure: True parent β†’ child relationships with folder nesting
  3. DiΓ‘taxis Content Types: Separate content by user intent (Tutorials, How-to, Reference, Explanation)
  4. Visual Diagrams: Mermaid diagrams for complex flows
  5. Detailed Explanations: Everything explained for easy understanding
  6. Cross-References: Links between related documents
  7. Version Tracking: Last updated dates on each document
  8. Content Type Metadata: Each document tagged with content type for filtering

πŸ“ Contributing to Documentation ​

When adding new information:

  1. Update the relevant section document
  2. Update the main overview if it's a major change
  3. Add diagrams for complex flows
  4. Cross-reference related documents
  5. Update the "Last Updated" date

πŸ” Finding Information ​

By Content Type ​

By Category ​


πŸ“š Source Documents ​

Primary Source:

  • docs/project_status.md - CENTRAL DOCUMENT containing all system information (continuously updated during development)

Supplementary Sources:


🎯 Documentation Goals ​

  1. Comprehensive Coverage: Every system, feature, and component documented
  2. Easy Navigation: Hierarchical structure with clear parent-child relationships
  3. Visual Understanding: Mermaid diagrams for complex flows and architectures
  4. Living Documentation: Continuously updated as the system evolves
  5. Nothing Left Behind: All information from project_status.md extracted and organized

ASO Universal Consciousness System Documentation