📐 Crystal Studio Labs Architecture Specification

This document details the architectural standards, repository organization, and technical stack principles across all Crystal Studio Labs projects.

🏛️ Ecosystem Overview

                          ┌────────────────────────┐
                          │   Crystal Studio Labs  │
                          │   Organization Hub     │
                          └───────────┬────────────┘
                                      │
       ┌──────────────────────────────┼──────────────────────────────┐
       │                              │                              │
┌──────▼───────┐              ┌───────▼──────┐              ┌────────▼───────┐
│ Security &   │              │ Systems &    │              │ Applications & │
│ Automation   │              │ Utilities    │              │ Web Interfaces │
├──────────────┤              ├──────────────┤              ├────────────────┤
│ • ARGUS      │              │ • MenuForge  │              │ • InkMD        │
│   Action     │              │ • Crystal-   │              │ • AsciiVision  │
│ • SpecKit    │              │   System.js  │              │ • BharatOps    │
└──────────────┘              └──────────────┘              └────────────────┘

🛠️ Stack & Layering Declarations

1. Developer Tools & CI Actions

• Primary Languages: JavaScript (Node.js ESM), Shell (Bash / Zsh), Go, Rust.
• Architectural Rules: Zero external runtime overhead, fast cold-start performance, strict defensive input handling.

2. Terminal UI (TUI) & System Monitors

• Primary Frameworks: gum, Charm ecosystem, standard POSIX utilities.
• Architectural Rules: Fallback rendering mode for legacy terminals, minimal CPU/RAM footprint (< 25MB working set).

3. Web Applications & Static Portals

• Primary Tech Stack: Static HTML5, Vanilla JavaScript, CSS3 custom properties with glassmorphic tokens, Jekyll engine compatibility for GitHub Pages.
• Architectural Rules: No bloated multi-megabyte bundlers for simple sites; fast first-contentful-paint (< 1s); responsive design across mobile and desktop.

🔒 Security & Code Quality Rules

• Zero Secret Exposure: Public repositories must never commit token keys, private certs, or test credentials.
• Idempotency: Automation tasks and scripts must be idempotent and safely re-runnable without unintended state mutation.
• Strict Review Rules: Governed by ARGUS-01 (Zero-Placeholders), ARGUS-02 (Spec-Compliance), and ARGUS-03 (Structural-Clarity).