🏗️ Global WayCup Architecture Standards

Core Governance

  • 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. Avoid “third-party bloat.”

Technical Mandates

  • Thin-Context: Use .geminiignore and modular imports to keep context small and tokens cheap.
  • Cognitive Continuity: Persist preferences and session-specific logic to hierarchical memory.
  • Safety: Zero-tolerance for hardcoded secrets; enforce GCP Secret Manager via /gcloud.
  • Functionality: Use 'function name {' standard for all Bash scripts.
  • Naming: Industry-standard, unbranded nomenclature for scaffolding and file systems. Clean, descriptive names over “cute” labels.
  • Proactive Sync: Gemini MUST proactively commit and push changes to the relevant Git repositories after any architectural, configuration, or environment changes.