WayCup Engine

WayCup Master Architecture

3 min read

WayCup Master Architecture

This note codifies the deep structure of the WayCup Engine, serving as the single source of truth for our dual-architecture system and environment philosophy.

🏗️ The Dual-Architecture Definition

WayCup operates on two distinct structural layers to separate physical disk operations from conceptual business knowledge.

1. Disk-Level Scaffolding (The File System)

The physical structure of projects and environments:

  1. 00_core: The Engine Room. Global vault, automated agents, skills, and configuration.
  2. 01_internal: Business Operations. Internal projects, strategy, and administration.
  3. 02_labs: Innovation Hub. Rapid prototyping and R&D for AI workflows.
  4. 03_clients: Delivery. Production instances for client environments.
  5. 04_archive: History. Immutable logs and historical synthesis.

2. Vault-Level Business Pillars (The RAG Memory)

The logical organization of knowledge within 00_core/vault:

  1. 01_Attract: Lead generation, marketing, top-of-funnel strategy.
  2. 02_Convert: Sales strategy, proposals, triage calls, objection handling.
  3. 03_Serve: Client onboarding, delivery guides, frameworks (FTF), quarterly reviews.
  4. 04_Intelligence: Profiles, domains, and specific knowledge bases (e.g., Dog Wizard).

🧠 The Antigravity Tiered Memory Model

Our memory architecture balances high-velocity “vibe coding” with high-signal organizational structure.

  • Tier 1 (High-Velocity Native Capture): Always save new engineering logs, documentation drafts, and session notes into their respective “Native” folders within the vault without overthinking:
    • 00_core/vault/engineering/
    • 00_core/vault/docs/
    • 00_core/vault/notes/
  • Tier 2 (Curated Promotion): The Curator Agent periodically scans Tier 1 and promotes distilled insights into the Vault-Level Business Pillars (01_Attract, 02_Convert, 03_Serve, 04_Intelligence).
  • Antigravity Rule: Do not fight the machine’s default folder instincts; capture first, codify later.

💻 Environment: The “Remote Control & Engine” Philosophy

The Gemini Environment is built on the Separation of Concerns between Interface and Computation.

  • The Remote Control (The Book): Laptop/ChromeOS. Treated as “Glass and Keyboard” via Termius. Pristine, lightweight, easily replaceable.
  • The Engine (The Box): Debian 12 machine. The single source of truth for files, AI memory (Vault), and heavy computation. Fully reproducible via Nix & Home Manager.
  • Headless Core: Decoupled from GUI dependencies via a 1Password Service Account for 24/7 autonomous access to secrets and SSH keys.
  • Cognitive Continuity: By keeping the AI’s memory (Context files) on a single Engine, the AI never “forgets” who you are, regardless of which device is used to connect.

🛠️ Core Governance & Technical Mandates

  • Parent/Child Model: WayCup retains reusable “Engines” (IP); clients receive “Instances.”
  • TCI-First: Everything must be optimized for Thin Client (Box/Book) parity and remote sync.
  • Google-Native: Priority given to official GCP services and Gemini CLI extensions.
  • Thin-Context: Use .geminiignore and modular imports to keep context small and tokens cheap.
  • Safety: Zero-tolerance for hardcoded secrets; enforce GCP Secret Manager.
  • Nomenclature: Industry-standard, unbranded nomenclature for scaffolding and file systems. Clean, descriptive names over “cute” labels. Concise titles, lowercase YAML tags.
  • Proactive Sync: Gemini MUST proactively commit and push changes to the relevant Git repositories after any architectural, configuration, or environment changes.

Graph View