🚀 Knowledge Base Deployment Pipeline

This document outlines the “Headless” automation architecture that synchronizes the WayCup local vault with the AI Brain (Vertex) and the Human UI (Cloudflare).

1. The Core Components

1. Authoring: Local Markdown in 01_internal/core/vault (Edited in Google Antigravity).
2. Version Control: Private GitHub Repository (waycup/waycup-vault).
3. The Brain (RAG): Google Vertex AI Search & Conversation (Project: waycup-admin-hub).
4. The UI (Static Site): Quartz v4 (Open Source Wiki generator).
5. The Host: Cloudflare Pages (Custom Domain: vault.waycupcreative.com).

2. The Automation Workflow (GitHub Actions)

Every git push to the main branch triggers two concurrent pipelines:

A. Vertex AI Sync (deploy_vault_to_gcs.yml)

• Action: Uses Google Workload Identity Federation (Keyless) to authenticate.
• Result: Rsyncs the /vault directory to the GCS bucket gs://waycup-vault-internal. Vertex AI automatically re-indexes the new content for RAG queries.

B. Cloudflare UI Deployment (deploy_quartz.yml)

• Action: Spins up a temporary Node.js 22 runner.
• Process: Clones the Quartz engine, injects your /vault files, builds the static HTML, and pushes it to Cloudflare via the Wrangler CLI.
• Result: The website at vault.waycupcreative.com is updated within 90 seconds.

3. Maintenance Protocols

• Branding: Update quartz.config.ts in the repo root to change the site title or theme.
• Security: Ensure Cloudflare Access (Zero Trust) is enabled to protect the live URL.

---

Created by the WayCup Lead Architect on 2026-05-14.