# START HERE — mgf-fed

> **Audience:** anyone — human or AI agent — working in this repo.

`mgf-fed` is the **Magogi Foundation federation orchestrator**: one CLI that runs the recurring
cross-repo work — status tracking, drift detection, quality gates, local CI, and the two-mode
(local-first → remote) release — consistently across the `mgf-*` fleet. It *composes* existing
assets (the `mgf-standard` registry/waves, `mgf-test-supervisor`, `woodpecker-cli`, `tea`/git)
rather than reimplementing them.

## If you're an AI agent working here

Run **`mgf-fed agents`** and do what it prints — the canonical, federation-wide briefing.
Then read this repo's [`docs/claude/CLAUDE.md`](docs/claude/CLAUDE.md) (dense-lookup notes) and
[`SCOPE.md`](SCOPE.md).

## Use it

```sh
mgf-fed status            # the federation matrix
mgf-fed drift-check       # repos vs the canonical scaffolding policy
mgf-fed gates             # fast static lint+format sweep
mgf-fed local-ci <repo>   # the real .woodpecker pipeline (woodpecker-cli exec)
mgf-fed release-local  <repo>   # build-once → validate → publish to the local index
mgf-fed release-remote <repo>   # promote the local-validated wheel → Codeberg
mgf-fed registry --check  # REL-13 federation consistency + currency gate
```

Set `MGF_ROOT` if the sibling repos aren't under `~/PycharmProjects`; set `$MGF_CODEBERG_TOKEN`
to publish.

## Layout

`src/mgf/fed/` (one module per command) · `tests/` · `docs/` · the standard root-doc baseline.
Conformance: [`docs/inprogress/MGF_STANDARDS_CONFORMANCE.md`](docs/inprogress/MGF_STANDARDS_CONFORMANCE.md).
Plan + rationale: `mgf-standard/docs/inprogress/federation-automation-and-release-plan.md`.
