Meridian Platform CTO/CIO Layer

Gladys

Infrastructure and DevOps intelligence layer

Gladys owns engineering standards, deploy patterns, cross-repo tooling, and infrastructure health monitoring across every Meridian Venture. It surfaces through Emmett's brief rather than operating as a separate daemon.

Gladys West

Named in honor of Gladys West — mathematician and geodesist whose precise models of Earth's shape became the mathematical foundation for GPS. The infrastructure underneath everything that depends on it.

Infrastructure Status
Rebuilt Firebase
Relay Railway
Emmett Pi · 3002
Beacon Pi · 3000
Meridian Site Cloudflare Pages
Golda Gated
Gladys's Domain Engineering standards, deploy patterns, and cross-repo tooling. Standards cascade from a global config file to every project automatically.

Domains of Ownership

Four domains. Gladys owns the standards, not just the deploys.

Engineering Standards
Global rules that cascade automatically to every project. No project deviates unless Gladys explicitly notes an exception. Consistency is the product.
  • Always commit and push after every task
  • Never commit .env, *.db, or node_modules
  • Every project needs /health endpoint
  • One password auth on all internal dashboards
  • All secrets in Railway Variables
Deploy Patterns
Each Venture deploys through a defined pattern. Branch structure, CI/CD rules, and deploy triggers are documented and enforced consistently.
  • Relay: feature/* → main, Railway auto-deploy
  • Beacon/Emmett: push to main → PM2 restart
  • Rebuilt: feature/* → staging → main
  • Meridian site: GitHub → Cloudflare auto-deploy
  • Pi: git pull + pm2 restart (manual step)
Cross-Repo Tooling
Shared patterns that apply across all repos. Secrets, environment structure, health endpoints, and process management follow the same conventions everywhere.
  • Shared .env.shared on Pi for common keys
  • Service-specific .env for project vars
  • Firebase JSON at consistent path
  • .env.example required in every repo
  • DEPLOY.md required in every repo
Infra Health Monitoring
Infra state surfaces through Emmett's brief. Any deviation from expected state is flagged before it becomes an incident. Gladys surfaces to Emmett, not as a separate alert system.
  • Railway volume mount for Relay SQLite
  • Pi RAM and process health via PM2
  • Firebase function deployment state
  • Tailscale connectivity for Pi access
  • Cloudflare deploy status for Meridian site

Infrastructure Map

Every Venture. Every service. Gladys owns the state of all of it.

Service
Platform
Port
Domain
Deploy Method
Rebuilt
Live
—
getrebuilt.app
Firebase CLI
Relay
Live
3001
withrelay.co
GitHub → Railway auto-deploy
Beacon
In Dev
3000
emmett:3000 (Tailscale)
git push → PM2
Emmett
In Dev
3002
emmett:3002 (Tailscale)
git push → PM2
Meridian Site
Live
—
neverstill.llc
GitHub → Cloudflare auto-deploy

Engineering Standards

Rules that cascade from a global config file to every project.

01
Always commit and push after every task
No work exists until it is in the remote. The build agent never waits to be asked. Enforced via a global standards file that cascades to all project folders.
02
Surgical edits, not broad rewrites
The build agent must never do a broad rewrite of any file without explicit instruction containing "rewrite" or "rebuild from scratch." Default is str_replace targeting specific elements only.
03
One repo lock per active build agent session
Repo lock status tracked in Notion. Check before starting, lock immediately, unlock on completion. Multiple simultaneous sessions on the same repo cause merge conflicts and overwritten changes.
04
Secrets hygiene is non-negotiable
All secrets in Railway Variables (Relay), Firebase functions config (Rebuilt), or Pi .env.shared (Emmett/Beacon). Never in code. Never client-side. .env never committed.
05
Every project needs a /health endpoint
Consistent health check across all services. Required alongside .env.example and DEPLOY.md in every project. Makes infra monitoring straightforward and avoids silent failures.
06
Pi deploys are manual after every push
The build agent pushes to GitHub only. The Pi does not auto-deploy. After every Emmett or Beacon prompt: SSH in and run git pull and pm2 restart with --update-env. This step is required, not optional.

Surfaces through Emmett. Not a separate daemon.

Gladys is not a service you deploy and monitor separately. It is the engineering intelligence that runs inside Emmett's brief and inside every build agent session. The standards exist in a global config file. The infra state surfaces in the morning brief. The ownership is real whether or not there is a dashboard.

~/Projects/infra repo
global standards file cascades to all repos
Emmett brief block surfaces daily
Notion prompt tracker 6a461b80...