# mgf-fed — Magogi Foundation federation orchestrator

Runs the recurring cross-repo work — quality gates, local/remote release, status —
**consistently, controllably, and trackably** across the `mgf-*` fleet, in dependency-wave
order. It *composes* existing assets rather than reinventing them:

| Concern | Reused asset |
|---|---|
| release/build **order** | `mgf-standard` registry (`MGF_LIBRARIES.json` → `release_waves`) |
| gate/test **runner** | `mgf-test-supervisor` (`mtest`) |
| **local CI** | `woodpecker-cli exec` (the real `.woodpecker` pipeline, in containers) |
| **SCM/release** flow | `tea` + `git`, with the federation guardrails baked in |

Plan & rationale: see `mgf-standard/docs/inprogress/federation-automation-and-release-plan.md`.

## Status (Phase 0)
Read-only tracker only:

```
mgf-fed status              # the federation matrix (version, conformance %, scaffolding)
mgf-fed status --json       # machine-readable -> ~/.mgf/MGF_FED_STATUS.json
mgf-fed status --shape python
```

Set `MGF_ROOT` if the sibling repos aren't under `~/PycharmProjects`.

Later phases (stubbed in `--help`): `gates`, `local-ci`, `release-local`, `release-remote`,
`scaffold`, `drift-check`, `registry`.
