# SCOPE — mgf-fed

**SP-01 Purpose.** `mgf-fed` is the Magogi Foundation **federation orchestrator**: it runs
the recurring cross-repo work — quality gates, local/remote release, status tracking,
drift detection — consistently and trackably across the `mgf-*` fleet, in dependency-wave
order.

**SP-02 In scope.**
- Read-only federation introspection (`status`, `drift-check`, `local-index`).
- Orchestrating release flows (local-first → optional remote promotion) and gate runs by
  **composing** existing tools (`mgf-standard` waves, `mgf-test-supervisor`, `woodpecker-cli`, `tea`/git).
- The canonical scaffolding policy + drift detection against it.

**SP-03 Out of scope (delegated).**
- *Defining* the standards/registry → `mgf-standard`.
- *Running* tests/tiers → `mgf-test-supervisor`.
- *Executing* CI pipelines → `woodpecker-cli` / Woodpecker.
- *Library functionality* → each member library.
mgf-fed **invokes** these; it does not reimplement them.

**SP-04 Non-goals.** Not a build backend, not a package index server, not a CI engine, not
a replacement for `tea`/git. No bespoke validators where a composed tool exists.

**SP-05 Consumers.** Federation maintainers + automation (CLI + `MGF_FED_STATUS.json`).

**SP-06 Stability.** Pre-1.0; the `status`/`drift-check`/`local-index` read-only surface is
stable; release subcommands land per the phased plan.
