WayCup Engine Rules and Standards

🎯 Strategic Intent

Enforce nomenclature, metadata, and operational standards across the WayCup Engine to ensure high-signal RAG and automated curation.

Concise Titles: Eliminate redundant prefixes.
Metadata: YAML frontmatter must include title, lifecycle_stage, ctox_origin, and tags.
Nomenclature: Use Functional Naming (e.g., Changelog, SOP, Roadmap).

Separation of Powers: Nix strictly manages immutable packages and infrastructure hooks. Mutable file states, active profile paths, and live tokens are completely decoupled from Nix and managed natively.
SQLite Network-Mount Isolation: SQLite database files (such as active_config and credentials.db for gcloud) must remain on local disks to prevent cross-network locking corruption. Only text-based configs (e.g. gcloud/configurations/) can reside on SSHFS network mounts.
Ephemeral Secrets: All secrets, tokens, and API keys are dynamically retrieved in-memory via the 1Password CLI (op read). Enforce zero tolerance for plaintext secrets, tokens, or API keys written to disk.
Asymmetric Syncing (sync-all): Sync protocols are context-aware. The Engine (The Box) functions as the master pusher, whereas the Terminal (The Book) acts strictly as a read-only pull client.
UI Execution: The antigravity UI runs natively in the foreground, auto-clearing stale Singleton locks upon initialization and forcing the terminal tab title to 🌌 Antigravity IDE.
Intelligence: Vertex AI Search (RAG) is the primary engine.
UI: Cloudflare Pages (Quartz) provides the vault interface.
Git Sync: Every change must be committed and proactively pushed to main to preserve workspace parity.

Source: original_core_rules.md