Skip to main content

Anchor Handoff

Anchor handoff defines when a system moves from active development ownership to accepted production operations ownership.

Three-Company Model​

  • EGI owns software development, internal SOPs, CI rules, and development workflows for EGI-built systems.
  • Mast owns software development, internal SOPs, CI rules, and development workflows for Mast-built systems.
  • Anchor owns managed production operations only after a system is formally accepted into Anchor-managed production.

Throughout this section, development company means the company actively building the system, usually EGI or Mast.

Core Rule​

The old engine-tracking model is sunset. It must not be recreated as the center of runtime ownership or production governance.

Before handoff:

  • The development company owns the system.
  • The development company controls change velocity.
  • The development company may own dev and staging deployments, Cloudflare, PostHog, and similar tooling during active development.

After handoff:

  • Anchor owns accepted production operations.
  • Anchor owns production monitoring, logging, alerting, backups, secrets operations, security visibility, incident response, and operational runbooks.
  • Engineering changes still originate from the development company, but production execution is governed through Anchor processes.

Platform-Agnostic Requirement​

These SOPs are capability-based, not platform-bound. A system may run on Kubernetes, Vercel, Cloudflare, VMs, managed databases, or other hosting models.

Anchor's current operating stack includes tools such as PostHog Cloud, CrowdSec Console, Grafana, Prometheus, Loki, Alertmanager, Uptime Kuma, Wazuh, Restic, Vault, Slack, and Twilio. Those tools are examples of how Anchor currently fulfills its operational responsibilities, not mandatory implementation choices for every system.

Handoff Pages​