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 structureDiΓ‘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 β
- New to the project? β Start with 00-OVERVIEW.md
- Understanding client vision? β Read 01-CLIENT-VISION-CANON-v2.md
- Working on a specific platform? β Check 03-PLATFORMS/
- Implementing a feature? β See 04-FEATURES/
- 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:
- Vision principles and non-negotiables
- Identity and protocol boundaries
- Runtime/memory continuity contracts
- Vision-critical acceptance gates
- PR checklist snippet: templates/PR-VISION-IMPACT-CHECKLIST.md
- Issue checklist snippet: templates/ISSUE-VISION-IMPACT-CHECKLIST.md
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):
- Memory System
- Timeline System
- Observer System
- Protocol Routing
- Authentication & Authorization
- Prompt System
- Tool System
- File Handling System
- State Machine System
- Auto-Flow System
- Coder Orchestrator System
- Group Chat System
- Training System
- Suggestion System
- Subject Consciousness System
- Scheduler System
03-PLATFORMS/ β
Platform-specific documentation (hierarchical with DiΓ‘taxis content types):
- Web Portal
- Web Portal - Admin Dashboard & Observer Console
- Discord Bot
- Discord Bot Architecture
- Unity Game (Planned)
- Mobile/AR/VR (Future)
04-FEATURES/ β
Feature-specific documentation (hierarchical with DiΓ‘taxis content types):
- Quest System
- Inventory System
- Relationship Milestones
- Choices System
- AI Director
- Multi-Personality System
- Save System (Not Implemented)
- Training Center
- Protocol Management
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:
- Primary Source:
docs/project_status.mdis the central document - extract all information from it first - Hierarchical Structure: True parent β child relationships with folder nesting
- DiΓ‘taxis Content Types: Separate content by user intent (Tutorials, How-to, Reference, Explanation)
- Visual Diagrams: Mermaid diagrams for complex flows
- Detailed Explanations: Everything explained for easy understanding
- Cross-References: Links between related documents
- Version Tracking: Last updated dates on each document
- Content Type Metadata: Each document tagged with content type for filtering
π Contributing to Documentation β
When adding new information:
- Update the relevant section document
- Update the main overview if it's a major change
- Add diagrams for complex flows
- Cross-reference related documents
- Update the "Last Updated" date
π Finding Information β
By Content Type β
- Learning the System? β Check Tutorials/
- Need to Do Something? β Check How-to Guides/
- Looking for Facts? β Check Reference/
- Understanding Why? β Check Explanation/
By Category β
- System Components: Check 02-CORE-SYSTEMS/
- Platform Details: Check 03-PLATFORMS/
- Feature Implementation: Check 04-FEATURES/
- Integration Guides: Check 05-INTEGRATIONS/
- Architecture Details: Check 06-ARCHITECTURE/
π Source Documents β
Primary Source:
docs/project_status.md- CENTRAL DOCUMENT containing all system information (continuously updated during development)
Supplementary Sources:
docs/CURRENT_STATE.md- Concise snapshot (β οΈ DEPRECATED - see 00-OVERVIEW.md)docs/DECISIONS.md- Architecture decisions (β οΈ DEPRECATED - see 06-ARCHITECTURE/System-Architecture.md)docs/ROADMAP.md- Future workdocs/SYSTEM_FLOW_DIAGRAMS.md- Detailed flow diagrams (β οΈ DEPRECATED - see 06-ARCHITECTURE/Data-Flow.md)docs/USER_LEVELS_AND_PERMISSIONS.md- User roles and permissions (β οΈ DEPRECATED - see 02-CORE-SYSTEMS/Protocol-Routing.md and 02-CORE-SYSTEMS/Authentication-Authorization.md)docs/PROMPT_SYSTEM_ARCHITECTURE.md- Prompt system details (β οΈ DEPRECATED - see 02-CORE-SYSTEMS/Prompt-System.md)docs/LLM_CALLS_OVERVIEW.md- LLM call patterns (referenced in platform docs)
π― Documentation Goals β
- Comprehensive Coverage: Every system, feature, and component documented
- Easy Navigation: Hierarchical structure with clear parent-child relationships
- Visual Understanding: Mermaid diagrams for complex flows and architectures
- Living Documentation: Continuously updated as the system evolves
- Nothing Left Behind: All information from
project_status.mdextracted and organized