Magi System Architecture

Component Structure

Core Components

1. Magi.Chamber (Primary Repository)
2. Houses the central distribution system
3. Contains submodules:
   • Magi.Library (Documentation & Architecture)
   • Magi.Spells (Spell Repository)

4. Manages spell distribution and verification

5. Magi.CLI (Client)

6. Interfaces with Magi.Chamber
7. Manages local spell cache
8. Handles spell execution

Repository Structure

Magi.Chamber/
├── chamber/           # Main distribution server
├── submodules/
│   ├── Magi.Library/ # Documentation & Architecture
│   │   ├── technical/
│   │   └── repos/
│   └── Magi.Spells/  # Spell repository
└── api/              # REST endpoints

Magi.CLI/
├── magi/             # Client implementation
├── sanctum/          # Local storage
└── cast/            # Command executor

System Flow

1. Spell Update Flow

Magi.Spells (submodule) → Magi.Chamber → Distribution API → Magi.CLI

1. Documentation Update Flow

Magi.Library (submodule) → Magi.Chamber → Web Interface

1. Client Interaction Flow

User → Magi.CLI → Magi.Chamber API → Submodule Content → Local Cache

Submodule Management

Magi.Library

• Purpose: Central documentation and architectural specifications
• Integration: Direct submodule in Magi.Chamber
• Updates: Version controlled through Chamber

Magi.Spells

• Purpose: Spell repository and versioning
• Integration: Direct submodule in Magi.Chamber
• Updates: Automated through webhooks and GitHub Actions

Client-Server Relationship

1. Magi.CLI (Client)
2. Consumes Chamber API
3. Maintains local spell cache

4. Handles user interactions

5. Magi.Chamber (Server)

6. Manages submodules
7. Provides distribution API
8. Serves documentation