# Magogi Foundation Standards — Conformance Tracker (mgf-brand-qt)

> **Status (2026-06-29).** Initial conformance audit at **0.1.0**. The per-rule
> ledger in §Z was **seeded from a sibling** so that every one of the **262 corpus
> MUSTs** is accounted for from day one; it is being **refined for mgf-brand-qt's
> shape** — a **pure asset package** (tokenized CSS + fonts + SVG shipped as
> package data + a tiny `static_dir()` accessor), so most runtime / provider /
> service rules are N/A; what applies is packaging (AP/PKG), docs (DOC), and the
> gate stack. The four engineering gates (ruff, mypy `--strict`, import-linter,
> pytest @ **100%** coverage) and the `app-doctor --standards` runtime gate pass.
> **Scope.** mgf-brand-qt's conformance to the standards at
> [mgf-standard/docs/standards/](https://codeberg.org/magogi-admin/mgf-standard/src/branch/main/docs/standards/).
> **Audience.** Maintainer-tomorrow, AI coding agents, future contributors.
> **Cross-references.** [README.md](../../README.md), [CHANGELOG.md](../../CHANGELOG.md).

---

> **SEEDED 2026-07-10 at extraction** from the mgf-brand-web ledger
> (same shape, same rule families). Every row reset to ⏳ pending this
> repo's own first per-rule audit — inherited ✅ claims would cite
> another repo's evidence. The import-linter contracts, palette lint,
> contrast guard, and Qt-freeness test are already live (see tests/).

## §1 You are here

**Project shape:** a **UI-kit library** (`mgf.brand_qt`, GUI-01 carve-out 2026-07-10) — the
Magogi design tokens, generated QSS, OFL fonts, 42-icon set, marks/patterns,
and brand widgets for PySide6 desktops. **One runtime dependency (PySide6)**;
no domain imports and a Qt-free token core (both import-linter-enforced). That shape makes most rules N/A: no service / CLI
/ runtime, no credentials, no provider SDK, no async surface.

**Current version:** **0.1.0** (single-sourced — `mgf.brand_qt.__version__`;
the `app-doctor` AP-13 check pins it to `pyproject.toml::project.version`).

**Declared TARGET conformance level: L2.** Current standing: the four engineering
gates (ruff, mypy `--strict`, import-linter, pytest @ **100%** coverage) and the
`app-doctor --standards` runtime gate pass. The §Z per-rule rows are **inherited
from a sibling** as a starting accounting (see Status above) and are being walked
for this package's asset-only shape; treat a row that cites service / CLI /
provider evidence as "inherited, N/A for an asset package" until refined.

**Honest level note (CFM-02).** L2 = *every MUST met*; L3 = *every MUST **and**
SHOULD + runtime enforcement*. The 2026-06-25 depth audit (the 113-agent
`l3-audit-1b1` workflow, adversarial-refute-filtered) found **24 MUST + 7
lower-severity gaps** in mgf-cloud. The Item 1b-1 uplift (stages 1 + 2) **closed
22 of the 24 MUSTs in code** and the lower-severity batch; the **2 remaining MUSTs
(PKG-01, WF-11) are fleet-infra items** — the publish channel and the CI install
method are governed by the `mgf-standard` woodpecker template + the devpi backfill
gap, which mgf-cloud cannot change unilaterally without breaking template-parity.
Per [non-adoption-is-valid](https://codeberg.org/magogi-admin/mgf-standard/src/branch/main/docs/standards/principles/non-adoption-is-valid.md),
these are deferred-with-rationale, not declined. **mgf-cloud is therefore at the
L2 bar on every surface it controls.**

**2026-06-28 full per-MUST tally (§Z).** Of the **263 MUSTs**: **138 ✅** ·
**19 ⏳** · **9 🚫 declined** · **97 N/A** (premise service/GUI/deploy-shaped).
Applicable (non-N/A) = **166**; **138/166 (83%)** evidenced ✅ — every code-quality
family (DP, EH, LG, SC, TS, AP) lands ✅. The **19 ⏳** are doc/test-pin polish
(AP-01, SC-04, EH-09, LG-16, OB-01/OB-11, TM-04, DOC-03, OP-04, CF-01/06/08) + the
WF publish-chain cluster (WF-03/05/06/07/08/11). The **9 🚫** are the deliberate
self-hosted-devpi channel cluster (PKG-01..06, PKG-09 — B2 migration, §3/§4) + two
narrow auditor-🚫 (EH-07 best-effort bundle catch, LG-15 events not yet
registered). Counting the 4 indexed SHOULDs audited as rows (OB-06, PF-06,
PR-02 🚫, PR-06) → **267 rows** in §Z.

| Marker | Meaning here |
|---|---|
| ⏳ | conformant against the live 0.1.3 code (evidence in §Z where audited) |
| ⏳ | applicable MUST not met — open gap with a plan (§4) |
| N/A | rule's premise is service/GUI-server/deploy-shaped; mgf-cloud is operator tooling |
| ⏳ | declined-with-rationale (CFM-04 — §3) |

---

## §2 Per-standard audit (2026-06-25, re-baselined to corpus 263 MUSTs / 22 families)

| Family | MUSTs | Verdict | Notes (evidence: §Z where audited) |
|---|---|---|---|
| **AG** AGENTS | 19 | ✅ / N/A | AGENTS.md + docs/memory present, `my_stuff/` gitignored (AG-17/18/19); AG-14 propagation followed in this uplift (PUBLIC_API + CHANGELOG + this ledger walked together). |
| **AP** API_DESIGN | 15 | ⏳ | `__all__` on every public module; AP-13 version single-sourced; **AP-10/AP-11** PUBLIC_API.md now enumerates all 24 names with Tier+Since (was "added in Passes 2-3"); **DOC-08** md↔`__all__`↔json drift pins. AP-01: `cost.py` now carries `__all__`. |
| **CF** CONFIGURATION | 12 | ⏳ | `config.py` — typed pydantic models, layered resolution (explicit → `$MGF_CLOUD_CLOUDS_YAML` → `OS_*` → search paths), `SecretStr` secrets; rates via TOML + env. CF-09 `--clouds-yaml` flag present. |
| **DEP** DEPLOYMENT | 11 | N/A | mgf-cloud is operator-run tooling, not a deployed service (no systemd unit / container image / deploy pipeline of its own). |
| **DOC** DOCUMENTATION | 19 | ⏳ | DOC-01 root set + `docs/` tree; **DOC-08** PUBLIC_API regen + pins; **DOC-09** `mgf-common <verb>` → `mgf-fed <verb>` swept (STARTHERE/FEEDBACK); **DOC-15/CFM-03** this re-baseline. |
| **DP** DESIGN_PRINCIPLES | 13 | ⏳ | Closed-box import-linter (3 contracts, all KEPT), mypy --strict, frozen pydantic models, lazy provider loading; DP-13 SSH client closed in `finally`. |
| **EH** ERROR_HANDLING | 13 | ⏳ | Typed vocabulary onto `mgf.common.exceptions` (+ `CredentialsError`/`ProviderNotFoundError`, EH-08 attrs-before-super); **EH-01** `rates_from_config` raises `ConfigError`; **EH-04** CLI top-level routes untyped bugs to `report_now`; **EH-12** idempotent `create_volume`. |
| **FB** FEEDBACK | 1 | ⏳ | FEEDBACK.md present + referenced. |
| **GUI** GUI_CONSUMERS | 10 | N/A | The PySide/Qt desktop-GUI rules; mgf-cloud's GUI is a server-rendered local web page, not a Qt app. |
| **LG** LOGGING | 17 | ⏳ | **OB-01/LG-02/LG-06** `mgf.common.bootstrap` wired at both entry points (CLI `main`, web `serve`); per-module `get_logger`; **LG-11** INFO operation start/end with a stable `operation` field + `duration_ms` at the Infomaniak `_boundary` + `remote.run_commands`. |
| **NM** NAMING | 3 | ⏳ | Hyphen slug + dotted namespace + PEP-420 (no `src/mgf/__init__.py`); NM-05: no `utils/misc/helpers` junk modules (every module domain-named). |
| **OB** OBSERVABILITY | 10 | ✅ / N/A | OB-01 logs pillar wired (above). Metrics/traces/SLO (OB-02..08) legitimately N/A — operator tooling, no page-able service surface. |
| **OP** OPERABILITY | 12 | ⏳ | **OP-01** rich `version` (+`--json`: pkg + git SHA + python + platform + dep versions); **OP-02** `doctor` (offline install+config health, exit = failed-check count); **OP-05** `explain` (resolved CloudConfig + winning source, secrets redacted); **OP-07** `bundle` (redacted diagnostic tarball). OP-09..12 N/A (no service). |
| **PF** PERFORMANCE | 7 | N/A (leaning) | mgf-cloud's latency is dominated by remote OpenStack/SSH calls, not local CPU; no in-process hot path warrants a perf-baseline harness. PF-02 `perf` marker available via mgf-common. Not yet formally evidenced — the honest L3 gap. |
| **PKG** PACKAGE_DISTRIBUTION | 12 | ⏳ PKG-01 (§4) | Hatchling, `py.typed`, extras-gated SDKs; **PKG-06** pyproject index comment corrected to the actual devpi single-index. **PKG-01** = the devpi-vs-Codeberg channel reconciliation (fleet-infra, §4). |
| **PR** PRESENTATION_LAYER | 5 | ✅ / 🚫 | **PR-01** closed-box forbidden floor raised (typer/fire/rich/prompt_toolkit/qasync); **PR-04** new `independence` contract between `cli` and `web` (only the lazy launcher edge whitelisted); **PR-02** (dedicated `-app` repo) declined-with-rationale (§3); PR-06 N/A. |
| **REL** RELEASING | 13 | ⏳ | **REL-03/REL-06** version coherence: `__version__`/wheel/PUBLIC_API.json all single-sourced from metadata, pinned push-time. Annotated tags; CI publish + post-publish verify (channel = PKG-01). |
| **SC** SECURITY_STANDARD | 18 | ⏳ | `SecretStr` everywhere (never logged/repr'd); gitleaks; **SC-07** finite configurable `api_timeout` on the OpenStack Connection; **SC-17** `audit=true` structured records at the clean seams (`ssh.connect`/`disconnect`, `auth.ok`/`auth.fail`) carrying host/user/auth_url, never the secret; **SC-10** in-tree CVE triage. |
| **SP** SCOPE | 6 | ⏳ | SCOPE.md (SP-01..06) authored; tight 3-dep core, SDKs/web split behind extras. |
| **TM** TIME | 6 | ⏳ | UTC at boundaries (`datetime.now(UTC)` in cost/audit), ISO serialisation; resource ages computed from UTC creation times. |
| **TS** TESTING | 28 | ⏳ | pytest matrix (3.11–3.13), markers, timeout, coverage floor; **TS-01** `tests/test_mirror.py` allow-list (now incl. the four new ops-verb modules); 137 tests green incl. the new ops-verb + version-sync pins. |
| **WF** WORKFLOWS | 13 | ⏳ WF-11 (§4) | Generated `.woodpecker.yml`; four-gate CI (ruff/mypy/lint-imports/pytest) + full-clone fix; WF-02 `ruff format --check` present. **WF-11** = CI install via frozen lock (fleet-infra, §4). |

**Tally:** of the 263 MUSTs, the applicable set for this shape is met **except
PKG-01 + WF-11** (both fleet-infra deferrals, §4). The DEP / GUI / most OB / PF
families are N/A-by-shape (operator tooling, not a deployed service or a Qt
desktop app).

**Authoritative-audit note (2026-06-28).** The per-MUST **§Z** audit below is now
complete — all **263 MUSTs** (+ 4 indexed SHOULDs) carry a row — and is
**authoritative**: where a family roll-up in the table above predates it, §Z
governs. Full tally: **138 ✅ / 19 ⏳ / 9 🚫 / 97 N/A**. The per-MUST pass refined
three roll-ups above: **EH** and **LG** each carry one auditor-🚫 + one ⏳
(EH-07/EH-09, LG-15/LG-16); **PKG** is **🚫** across the devpi-channel cluster
(PKG-01..06/09) with PKG-10/12 ✅; and **AP/SC/TM/DOC/OP/OB/CF** each carry a single
⏳ polish item.

---

## §3 Decline-with-rationale ledger (CFM-04)

| Rule | Decision | Rationale |
|---|---|---|
| **PR-02** | 🚫 declined | "2+ UI consumers → a dedicated `-app` repo." mgf-cloud bundles its CLI and its single local web GUI in one repo deliberately: they share the exact same provider-agnostic core, there is one maintainer + one release cadence, and the web GUI is an optional `[web]` extra (not a separate distributable product). PR-04's `independence` import-linter contract enforces that the two surfaces stay decoupled, so the spirit of PR-02 (no UI/UI coupling) is mechanically met without the repo split. Revisit if a third UI consumer appears. |

---

## §4 Open gaps — tracked with a plan (⏳)

Both remaining items are **fleet-infra, not mgf-cloud-owned defects** — they are
governed by the `mgf-standard` woodpecker template and the federation devpi
rollout, which a single sibling cannot change without breaking template-parity
(`mgf-fed drift-check`). Per non-adoption-is-valid, deferred-with-rationale.

| Rule | Standard | Status |
|---|---|---|
| **PKG-01** | PACKAGE_DISTRIBUTION | ⏳ **Fleet-governance.** The L1-binding PACKAGE_DISTRIBUTION.md still names Codeberg, while the woodpecker publish/verify (a generated, drift-checked artifact) was retargeted to the self-hosted devpi index during the federation B2 migration. Reconciling the channel — either bless devpi in the L1 doc or revert the template to Codeberg + regen the fleet — is a federation-wide decision tracked at mgf-standard. PKG-06 (the stale pyproject index comment) was the part mgf-cloud *does* own and is fixed. |
| **WF-11** | WORKFLOWS | ⏳ **Fleet-infra.** Wants CI to install from a hash-pinned `uv.lock` (`uv sync --frozen`) instead of range-resolving `pip install -e .[...]`. `.woodpecker.yml` is a generated, drift-checked template artifact; fleet-wide adoption is blocked by the devpi backfill gap (the full-graph fleet lock doesn't resolve). Tracked at mgf-standard as the WF-13 template uv-migration. |

---

## §SHOULD — the 8 indexed SHOULD rules

L3 requires every SHOULD met or justified. The corpus indexes **8** SHOULDs:

| Rule | Verdict | Evidence |
|---|---|---|
| **NM-04** | N/A | Operator-chosen local clone layout; never appears in an artifact. (mgf-cloud is in fact cloned to its slug.) |
| **NM-05** | ⏳ | No junk-drawer modules: `find src/mgf/cloud -name '*.py'` yields zero `utils/misc/helpers/util.py`; every module is domain-named (`config`, `cost`, `models`, `remote`, `providers/*`, `cli/*`, `web/*`). |
| **OB-06** | N/A | SLI→SLO targets are for a deployed, page-able service. mgf-cloud is operator-run tooling with no SLO surface. |
| **PF-06** | N/A | "Document non-obvious public-API perf" — mgf-cloud's public surface is data models + thin provider methods whose cost is the remote API call, not local complexity worth annotating. |
| **PR-02** | ⏳ | Declined-with-rationale (§3) — single-repo CLI+web is deliberate; PR-04 enforces the decoupling. |
| **PR-06** | N/A | The optional "medium-agnostic `fmt` helpers" path is not exercised; output goes through the CLI `emit` helper + the web templates. |
| **TM-05** | ⏳ | User-facing datetime display happens at presentation (the `cost` command renders `%Y-%m-%d %H:%M UTC`); core carries UTC-aware datetimes. |
| **TM-06** | N/A / justified | No OTel span emission of its own; audit/log timestamps follow the federation ISO-8601 log contract (logship → OpenObserve), deliberately not ns-epoch. |

**Result: 8/8 met / N-A / justified-or-declined.** The remaining L3 distance is the
full per-MUST `file:line` evidence audit + a verdict on the PF baseline family,
not an open SHOULD.

---

## §5 Audit log

| Date | Auditor | Trigger | Findings |
|---|---|---|---|
| 2026-06-28 | multi-agent L3 ledger build (family fan-out + adversarial refute) | maintainer directive — write the complete per-MUST conformance ledger (DOC-15 / CFM-03) matching the passing mgf-sqlalchemy sibling shape | **Full per-MUST §Z built**: all **263 MUSTs** (+ 4 indexed SHOULDs) now carry a Rule · Family · Evidence · Status row. Tally **138 ✅ / 19 ⏳ / 9 🚫 / 97 N/A** (166 applicable). Completeness cross-checked against the sibling rule list; **9 MUSTs absent from the prior partial §Z were added** (CF-01/03/04/06/07/08/09/11 + FB-05). No code changed — ledger only. Declared **L2 on every owned surface** (target L3; remaining distance = PF baseline family + the ⏳/🚫 surfaced here). |
| 2026-06-25 | Item 1b-1 L3 depth-audit uplift (stages 1 + 2) | maintainer directive — uplift the high-stakes repos toward L3 against the mgf-common reference | **24 MUST + 7 lower-severity gaps found** (113-agent adversarial-refute workflow). **Closed 22/24 MUSTs in code** + the lower-severity batch: observability wiring (OB-01/LG-02/LG-06/LG-11/SC-17), version coherence (AP-13/REL-03/REL-06/OP-04), typed errors + guards (EH-01/EH-04/EH-12), SC-07 api_timeout, AP-10/AP-11/DOC-08 PUBLIC_API enumeration, PR-01/PR-04 import-linter, AP-01, TS-01, DOC-09, SC-10, PKG-06; **stage 2** shipped the **OP-01/OP-02/OP-05/OP-07** operability verbs (version/doctor/explain/bundle) + this ledger re-baseline (CFM-03/DOC-15). Gates green: ruff + mypy --strict + lint-imports + 137 tests. **Deferred: PKG-01 + WF-11** (fleet-infra, §4). Declared **L2 on every owned surface** (target L3). |
| 2026-06-14 | Pass-1 scaffold | new sibling bootstrap | Structural baseline met; per-MUST audit deferred to "Pass 7". Declared L1. (Superseded — the deferred surface has since shipped; this 2026-06-25 re-audit replaces the v0.1.0-frozen scaffold and its false N/As.) |

---

## §6 Cross-references

- [`mgf-standard/docs/standards/`](https://codeberg.org/magogi-admin/mgf-standard/src/branch/main/docs/standards/) — the corpus this audits against (263 MUSTs / 8 SHOULDs).
- [`PUBLIC_API.md`](../../PUBLIC_API.md) / [`PUBLIC_API.json`](../../PUBLIC_API.json) — the audited public surface (AP-10/DOC-08).
- [`.importlinter`](../../.importlinter) — the DP-01 / PR-01 / PR-04 closed-box + independence contracts.
- [`../../FEEDBACK.md`](../../FEEDBACK.md) — feedback filed against this sibling.
- The mgf-common reference ledger: [`mgf-common/docs/inprogress/MGF_STANDARDS_CONFORMANCE.md`](https://codeberg.org/magogi-admin/mgf-common/src/branch/main/docs/inprogress/MGF_STANDARDS_CONFORMANCE.md).

---

## §Z Per-MUST evidenced audit — all 263 MUSTs (DOC-15 / CFM-03 completeness)

> **2026-06-28 — multi-agent L3 ledger build (family fan-out + adversarial refute).**
> Every one of the **263 corpus MUSTs** carries a row below (per-family auditor
> fan-out, each ✅ adversarially refute-filtered), plus the **4 indexed SHOULDs**
> that were audited as rows (OB-06, PF-06, PR-02, PR-06) → **267 rows**. Columns:
> Rule · Family · Evidence (`file:line`) · Status (✅ / ⏳ / 🚫 / N/A). **Tally across
> the 263 MUSTs: 138 ✅ · 19 ⏳ · 9 🚫 · 97 N/A** (166 applicable). Completeness was
> cross-checked against the passing mgf-sqlalchemy sibling ledger; the 9 MUSTs
> absent from the prior partial §Z (CF-01/03/04/06/07/08/09/11 + FB-05) were added.
> This supersedes the partial gap-closing §Z tables.

| Rule | Family | Evidence | Status |
|---|---|---|---|
| AP-01 | API_DESIGN | src/mgf/cloud/__init__.py:52-77, src/mgf/cloud/models.py:14-33, src/mgf/cloud/cost.py:34-42 — __all__ lists exist but are NOT sorted: __init__.py has DEFAULT_OWNER before CloudConfig; models.py has OWNER_TAG before Flavor; cost.py has HOURS_PER_MONTH before CostReport. Only config.py and remote.py are properly sorted. | ⏳ |
| AP-02 | API_DESIGN | src/mgf/cloud/config.py:124-149 from_clouds_yaml docstring explains intent; src/mgf/cloud/models.py:43-58 all public functions/classes have docstrings (owned_metadata, is_owned, Server, Volume, etc.); src/mgf/cloud/providers/__init__.py:32-44 get_provider and available_providers both documented | ⏳ |
| AP-03 | API_DESIGN | pyproject.toml:3 version="0.1.3" (MAJOR.MINOR.PATCH); CHANGELOG.md:6 adheres to SemVer; operating in 0.x window where MINOR may break per AP-03 | ⏳ |
| AP-04 | API_DESIGN | No deprecations exist in v0.1.3; rule governs deprecation cycle once adoptions are announced (young project) | N/A |
| AP-05 | API_DESIGN | src/mgf/cloud/providers/__init__.py:37-44 get_provider(name, credentials=None) has optional kwarg with default; src/mgf/cloud/cost.py:87-102 Rates.flavor_rate(flavor \| None, flavor_name: str) signature stable with keyword-only defaults; all new parameters follow the pattern | ⏳ |
| AP-06 | API_DESIGN | src/mgf/cloud/__init__.py return types pinned narrowly: CloudConfig, CloudProvider, Server, Volume, CostReport, etc. (not broad Iterable/Sequence); src/mgf/cloud/providers/base.py:35-182 CloudProvider Protocol methods return specific types (list[Server], list[Flavor], None, Image, etc.) | ⏳ |
| AP-07 | API_DESIGN | src/mgf/cloud/config.py:43-89 Credentials docstring + raise CredentialsError documented; src/mgf/cloud/providers/__init__.py:37-44 raises ProviderNotFoundError, CredentialsError, ConfigError documented in docstring; all exceptions inherit from mgf.common typed hierarchy (EH-01) | ⏳ |
| AP-08 | API_DESIGN | grep confirms 21/21 Python files in src/mgf/cloud have `from __future__ import annotations` at top; verified in __init__.py:14, config.py:14, models.py:10, providers/*.py:10 etc. | ⏳ |
| AP-09 | API_DESIGN | src/mgf/cloud/py.typed exists (0-byte PEP 561 marker); pyproject.toml:129-130 [tool.hatch.build.targets.wheel] packages=["src/mgf"] ships the marker in wheel; classifier includes "Typing :: Typed" | ⏳ |
| AP-10 | API_DESIGN | PUBLIC_API.md exists at repo root, lines 18-46 list every public name from __all__ with tier and one-line description (CloudConfig, CloudProvider, Credentials, Flavor, Server, Volume, etc.); tests/unit/test_public_api_pin.py:31-38 pins md mentions every name in CI | ⏳ |
| AP-11 | API_DESIGN | PUBLIC_API.md:12-16 declares all public names as "experimental" tier; lines 20-46 Stability column shows experimental for every entry; consistent with 0.x convention (AP-11 requires declared tier per name) | ⏳ |
| AP-12 | API_DESIGN | CHANGELOG.md documents breaking changes with migration guidance: line 51 'Typed errors (EH-01)... cost.rates_from_config raises ConfigError (was a raw FileNotFoundError)' shows before/after + reason; CHANGELOG.md:6 adheres to AP-12 format | ⏳ |
| AP-13 | API_DESIGN | src/mgf/cloud/__init__.py:43-50 __version__ = _pkg_version("mgf-cloud") single-sourced from installed metadata; tests/unit/test_version_in_sync.py:24-29 pins it to pyproject.toml on every push (never drifts) | ⏳ |
| AP-14 | API_DESIGN | .importlinter file with three contracts: (1) mgf-cloud-closed-box forbids unrelated frameworks; (2) mgf-cloud-core-light (lines 45-64) forbids SDK imports from core modules; (3) mgf-cloud-cli-web-independence enforces CLI/web independence; import-linter in pyproject.toml:98 ensures enforcement | ⏳ |
| AP-15 | API_DESIGN | No backward-compat shims exist in v0.1.3; rule applies once names are removed (young project, all names are new) | N/A |
| AP-16 | API_DESIGN | pyproject.toml:34 pins the one mgf-* dependency with the federation window `mgf-common[standards]>=0.47,<1.0` (floor kept, ceiling `<1.0` per API_DESIGN §4.4) — widened in the AP-16 cohort wave, PR #3 (2b3f7b7, 2026-07-01). The `mgf-common-matrix` floor re-run step is not spliced into .woodpecker.yml here and honestly cannot be: the template splices it only for a **runtime** mgf-common floor (frag-mgf-common-matrix — "spliced only into repos that carry a versioned mgf-common dependency"; mgf-fed derives the floor from `[project.dependencies]`), and this package has **zero runtime dependencies** — mgf-common is an optional `[standards]` tooling extra consumed only by CI's standards steps, so the runtime floor matrix is N/A by shape. Adopted in the AP-16 cohort wave 2026-07-01; row added when mgf.standard 0.1.61 entered AP-16 into the released MUST index (264→265). | ⏳ |
| DP-01 | DESIGN_PRINCIPLES | .importlinter file enforces layering via three contracts: closed-box (forbids unrelated frameworks), core-light (forbids SDK/web in core), CLI-web-independence (PR-04); pyproject.toml:98 includes import-linter in dev dependencies | ⏳ |
| DP-02 | DESIGN_PRINCIPLES | src/mgf/cloud/providers/base.py:35-182 CloudProvider is a @runtime_checkable Protocol (the ABC); src/mgf/cloud/providers/fake.py implements it in-memory; src/mgf/cloud/providers/infomaniak.py:79-96 implements it for real OpenStack; openstacksdk imported only in infomaniak.py (line 32) | ⏳ |
| DP-03 | DESIGN_PRINCIPLES | src/mgf/cloud/models.py:61-63 class _Frozen(BaseModel) with ConfigDict(frozen=True); all domain models inherit from it (Flavor, Image, Keypair, Server, Volume, VolumeSnapshot, SecurityGroup, etc., lines 65-233); src/mgf/cloud/config.py:47 Credentials frozen=true; src/mgf/cloud/remote.py:42-51 RemoteHost frozen=true | ⏳ |
| DP-04 | DESIGN_PRINCIPLES | pyproject.toml:193-208 mypy strict=true, disallow_untyped_defs=true, disallow_incomplete_defs=true; lines 210-221 Any usages justified: openstacksdk, boto3, botocore, paramiko, keystoneauth1 marked ignore_missing_imports (have no stubs); every public function type-annotated | ⏳ |
| DP-05 | DESIGN_PRINCIPLES | src/mgf/cloud/providers/fake.py implements FakeProvider in-memory (no network); src/mgf/cloud/remote.py:85-152 FakeRemoteClient in-memory (records commands/files); tests/ structure mirrors src/ (test_config.py, test_providers.py, test_remote.py, etc.); no credentials/live cloud in unit tests | ⏳ |
| DP-06 | DESIGN_PRINCIPLES | CHANGELOG.md v0.1.2 section documents all four concerns: Security (line 39 audit records SC-17), Reliability (line 31 idempotent volume EH-12), Performance (cost.py module), Error reporting (line 43 crash handling EH-04); every PR touch addresses concerns | ⏳ |
| DP-07 | DESIGN_PRINCIPLES | src/mgf/cloud/config.py:124-149 from_clouds_yaml docstring explains intent + parameters; src/mgf/cloud/providers/__init__.py:32-44 available_providers/get_provider documented with intent + exceptions; src/mgf/cloud/models.py:43-233 all classes have docstrings (intent + fields) | ⏳ |
| DP-08 | DESIGN_PRINCIPLES | src/mgf/cloud/providers/__init__.py:1-7 docstring documents lazy loading + swap mechanism; providers/base.py:1-8 docstring explains CloudProvider interface allows swapping adapters; README + design docs describe plugging different providers (infomaniak/aws/fake) | ⏳ |
| DP-09 | DESIGN_PRINCIPLES | Library is synchronous (no asyncio.create_task, no long-running operations owned by library); cancellation not applicable (all functions are factories or one-shot) | N/A |
| DP-10 | DESIGN_PRINCIPLES | src/mgf/cloud/providers/__init__.py:49-62 raises ProviderNotFoundError (explicit, not silent); config.py:128-149 raises CredentialsError on parse failure; every error path raises typed exception, never silently continues | ⏳ |
| DP-11 | DESIGN_PRINCIPLES | Library is synchronous, no asyncio.create_task or bare task creation; DP-11 applies to async code only | N/A |
| DP-12 | DESIGN_PRINCIPLES | src/mgf/cloud/cost.py:23 from datetime import UTC, datetime; line 76 datetime.now(tz=UTC); line 185 datetime.now(UTC); src/mgf/cloud/cli/_bundle.py:24,76 datetime.now(tz=UTC).strftime(...Z); all datetime construction is UTC-aware, never naive | ⏳ |
| DP-13 | DESIGN_PRINCIPLES | src/mgf/cloud/remote.py:68-82 RemoteClient Protocol line 80 close() for cleanup; FakeRemoteClient line 96 closed flag; src/mgf/cloud/providers/infomaniak.py:148-193 _boundary is @contextmanager ensuring cleanup; resources (connections, clients) released deterministically | ⏳ |
| DP-14 | ✅ | No canonical corpus set is restated in this repo's code/tests; taxonomies derive from their source. | New MUST, corpus v3.3.0 (DP-4/CIR-21/PAPER-131). |
| EH-01 | ERROR_HANDLING | src/mgf/cloud/exceptions.py:13-19 — Reuses mgf.common exception hierarchy (ConfigError, ProviderError, ResourceNotFoundError, ResourceAlreadyExistsError, OperationError), all of which descend from AppError | ⏳ |
| EH-02 | ERROR_HANDLING | src/mgf/cloud/providers/infomaniak.py:149-193 — _boundary() method maps openstacksdk exceptions (os_exc.ResourceNotFound, os_exc.ConflictException, ka_exc.Unauthorized, os_exc.SDKException) to typed federation exceptions with proper `from exc` chaining | ⏳ |
| EH-03 | ERROR_HANDLING | src/mgf/cloud/config.py:149,174; src/mgf/cloud/providers/infomaniak.py:167,169,187 — All re-raised exceptions use `raise ... from exc` cause chaining | ⏳ |
| EH-04 | ERROR_HANDLING | src/mgf/cloud/cli/_app.py:811-831 — CLI entry point installs top-level handler in main() via try/except catching typed _CLOUD_ERRORS and bare Exception, routing untyped exceptions to report_now() | ⏳ |
| EH-05 | ERROR_HANDLING | src/mgf/cloud/cli/_app.py:828-829 — Unhandled exceptions are routed to report_now(exc, source='mgf.cloud.cli') which writes crash reports locally | ⏳ |
| EH-06 | ERROR_HANDLING | No GUI worker threads exist in this codebase; code is CLI + web app (FastAPI, not Qt workers) | N/A |
| EH-07 | ERROR_HANDLING | src/mgf/cloud/cli/_bundle.py:97-98 — `except Exception as exc:` returns sentinel string `(failed to collect: {exc})` without being documented as best-effort observer loop or cleanup path (EH-07 carve-outs a/b) | ⏳ |
| EH-08 | ERROR_HANDLING | src/mgf/cloud/exceptions.py:40-61 — CredentialsError and ProviderNotFoundError both set machine-readable fields (.source, .missing, .provider, .available) before calling super().__init__() | ⏳ |
| EH-09 | ERROR_HANDLING | Error messages exist throughout (e.g., config.py:128,139, providers/infomaniak.py:183) but lack explicit actionable-step suffix guarantees; tests/unit/test_exceptions.py exists but does not pin actionable-hint substrings per EH-09 MUST | ⏳ |
| EH-10 | ERROR_HANDLING | No best-effort observer loops (hook executors, scheduler ticks, alert evaluators) exist in this codebase | N/A |
| EH-11 | ERROR_HANDLING | No retry logic exists in src/; openstacksdk and paramiko handle retries internally, not in mgf-cloud code | N/A |
| EH-12 | ERROR_HANDLING | Cloud VM/volume/storage operations are idempotent by design (OpenStack/AWS semantics) but mgf-cloud does not retry; single-attempt calls to provider SDK | N/A |
| EH-13 | ERROR_HANDLING | No unbounded retry loops or circuit breaker needed; mgf-cloud is a synchronous CLI/web adapter with single-attempt external calls | N/A |
| SC-01 | SECURITY_STANDARD | src/mgf/cloud/config.py:43-89 — Credentials use pydantic SecretStr for password/secret fields; all credentials sourced from clouds.yaml/OS_*/env, never hardcoded; SECURITY.md §27-36 documents secret handling | ⏳ |
| SC-02 | SECURITY_STANDARD | src/mgf/cloud/cli/_version.py:52-57 — subprocess.run() uses argv list with shell=False (implicit default); no shell=True found via grep | ⏳ |
| SC-03 | SECURITY_STANDARD | src/mgf/cloud/config.py:129 — YAML parsing uses yaml.safe_load(); no pickle, yaml.load, or unsafe deserialization found | ⏳ |
| SC-04 | SECURITY_STANDARD | src/mgf/cloud/cli/_bundle.py:87,99 use write_text() in tempdir (acceptable); src/mgf/cloud/cli/_app.py:417 uses write_bytes() without explicit mode 0o600 for object download; remote.py:130-135 properly sets modes via sftp.chmod() | ⏳ |
| SC-05 | SECURITY_STANDARD | No cryptographic primitives (encryption, signing, hashing) used in mgf-cloud; all crypto delegated to openstacksdk/boto3 and paramiko | N/A |
| SC-06 | SECURITY_STANDARD | src/mgf/cloud/remote.py:168-170 — paramiko SSHClient respects accept_new parameter, defaulting to RejectPolicy (strict) with explicit opt-in for AutoAddPolicy; OpenStack SDK default verify=True for TLS | ⏳ |
| SC-07 | SECURITY_STANDARD | src/mgf/cloud/remote.py:153 — connect() has timeout=30.0 default; src/mgf/cloud/providers/infomaniak.py:76 — _API_TIMEOUT=30 passed to openstacksdk proxies; src/mgf/cloud/cli/_version.py:56 — git timeout=2 | ⏳ |
| SC-08 | SECURITY_STANDARD | src/mgf/cloud/config.py:43-89 — Credentials is a pydantic.BaseModel with typed fields; src/mgf/cloud/models.py:61+ — all resource specs use frozen pydantic models; input validation at boundary via model_validate() | ⏳ |
| SC-09 | SECURITY_STANDARD | src/mgf/cloud/config.py:21 — SecretStr used for password fields; src/mgf/cloud/cli/_bundle.py:64,67 — Redactor applied to bundle text; mgf.common.observability handles formatter-side redaction | ⏳ |
| SC-10 | SECURITY_STANDARD | uv.lock committed at repo root with pinned hashes (version=1, all packages have sha256 hashes); .woodpecker.yml:103-112 runs pip-audit --strict on every PR, gating merge on findings | ⏳ |
| SC-11 | SECURITY_STANDARD | src/mgf/cloud/config.py:21 — SecretStr prevents repr() leaks; src/mgf/cloud/providers/infomaniak.py:182-185 — exception messages are user-facing, not secrets; mgf.common.observability.report_now() redacts crash reports | ⏳ |
| SC-12 | SECURITY_STANDARD | SECURITY.md at repo root (4698 bytes) contains: supported versions table, security contact (email + Codeberg private advisory), embargo expectations (90-day default), and disclosure timeline (3/7/30-90 days) | ⏳ |
| SC-13 | SECURITY_STANDARD | mgf-cloud stores no cryptographic keys at rest; credentials are loaded at runtime from clouds.yaml/env, never persisted | N/A |
| SC-14 | SECURITY_STANDARD | mgf-cloud has no authentication boundary; it is a provider adapter that assumes credentials are already authenticated (passed in via clouds.yaml or env) | N/A |
| SC-15 | SECURITY_STANDARD | No external-input-derived filesystem paths constructed; remote.py handles paramiko file paths (not user-supplied); bundle.py uses tempfile.TemporaryDirectory() which is OS-safe | N/A |
| SC-16 | SECURITY_STANDARD | mgf-cloud performs no privileged operations (no sudo, setuid, chmod 4755, container --privileged); all operations are in-process or via cloud SDK APIs | N/A |
| SC-17 | SECURITY_STANDARD | src/mgf/cloud/providers/infomaniak.py:173-181 — Unauthorized (auth failure) emits INFO log with audit=true, operation='auth.fail', including auth_url and user fields for SIEM filtering | ⏳ |
| SC-18 | SECURITY_STANDARD | Reproducible builds are a release concern; mgf-cloud is a library (sdist + wheel), not a binary service. CI builds (twine check) verify metadata validity per .woodpecker.yml:150+ | N/A |
| SC-19 | ✅ | Introduces no credential of its own; the secrets its pipeline consumes (`codeberg_ssh_clone_key`, `codeberg_ssh_host_key`, `devpi_password`) are all declared in `mgf-standard/SECRETS.toml` and verified by `mgf-secrets doctor` C3 (unregistered-actual). |
| SC-20 | N/A | Stores no credential values — it consumes Woodpecker-injected secrets at run time and writes none to disk. The encrypted store owns them. |
| SC-21 | N/A | No `my_stuff/` bare-value cache in this repo — nothing to hold at 0600. |
| SC-22 | N/A | Manages no Woodpecker secrets. Add/rotate/re-scope for the secrets it consumes is performed in `mgf-secrets` (`sync` / `rotate`), which owns the playbook and the cross-family contract surface. |
| SC-23 | ✅ | 1 fail-fast guard line(s) in `.woodpecker.yml` on the secret-consuming step(s) — a secret unscoped for the event fails the step with a named FATAL instead of injecting empty. |
| LG-01 | LOGGING | cli/_app.py:42, web/_app.py:27, remote.py:25, infomaniak.py:69 all use get_logger(__name__) | ⏳ |
| LG-02 | LOGGING | cli/_app.py:821 and web/_app.py:258 both wrap entry points in bootstrap() context manager | ⏳ |
| LG-03 | LOGGING | bootstrap() from mgf.common wires JsonFormatter which adds trace_id/span_id automatically | ⏳ |
| LG-04 | LOGGING | bootstrap() wires Redactor from mgf.common before any sink | ⏳ |
| LG-05 | LOGGING | No ERROR-level logging calls; exceptions are raised not logged at ERROR level | ⏳ |
| LG-06 | LOGGING | bootstrap() configures console (stderr) + rotating file sink under <state>/logs/ | ⏳ |
| LG-07 | LOGGING | Not a desktop GUI app; mgf-cloud is a CLI with optional localhost-only web GUI (not user-facing) | N/A |
| LG-08 | LOGGING | cli/_app.py:825 LOG.warning uses lazy %-formatting; all extra fields in extra={} not concatenated | ⏳ |
| LG-09 | LOGGING | All logging calls use extra={} for structured fields: remote.py:143-149, infomaniak.py:138-144, web/_app.py:259-262 | ⏳ |
| LG-10 | LOGGING | Not a headless service; mgf-cloud is a CLI tool | N/A |
| LG-11 | LOGGING | remote.py:199-201 and 216-223 log operation start/end with operation field; infomaniak.py:161 and 190-192 do same | ⏳ |
| LG-12 | LOGGING | Log emission cost delegated to mgf.common.bootstrap; no heavy formatting in call sites | ⏳ |
| LG-13 | LOGGING | No high-frequency log sites; loops and callbacks do not emit logs | N/A |
| LG-14 | LOGGING | Uses OTel trace context via bootstrap(); no custom correlation context | N/A |
| LG-15 | LOGGING | remote.py:142,180,199,217 emit messages as event identifiers ('ssh.disconnect','ssh.connect','remote.run_commands') but not in explicit 'event' field; infomaniak.py:136,173,190 emit 'auth.ok','auth.fail' as messages not event fields; web/_app.py:259 emits 'web.serve' as message; EVENTS.md:9 states '(none yet)' — events not registered per LG-15 | ⏳ |
| LG-16 | LOGGING | cli/_app.py:825 LOG.warning lacks WHY context as structured field and HOW hint; infomaniak.py:173 LOG.warning has WHY (auth_url,user) but no HOW remediation hint | ⏳ |
| LG-17 | LOGGING | LG-17 is a SHOULD (not MUST); no ERROR-level logging calls in code | N/A |
| OB-01 | OBSERVABILITY | Logs ✓ (via bootstrap), Traces ✓ (via bootstrap+OTel), Metrics ✗ (not a service; CLI shape does not emit metrics per OB-01 carve-out 'CLIs and library shapes MAY skip metrics') | ⏳ |
| OB-02 | OBSERVABILITY | Not a service; no metrics emitted per OB-01 carve-out for CLI | N/A |
| OB-03 | OBSERVABILITY | Not a service; no metrics emitted | N/A |
| OB-04 | OBSERVABILITY | bootstrap() from mgf.common wires OTel SDK; operation_span() available for explicit span wrapping | ⏳ |
| OB-05 | OBSERVABILITY | CLI tool, not a continuous service; no customer-facing operations requiring SLI per OB-05 scope | N/A |
| OB-06 | OBSERVABILITY | Dependent on OB-05; CLI has no SLIs | N/A |
| OB-07 | OBSERVABILITY | Dependent on OB-05; CLI has no alerts | N/A |
| OB-08 | OBSERVABILITY | Dependent on OB-05; no operability docs needed for CLI | N/A |
| OB-09 | OBSERVABILITY | LogRecord schema evolution managed by mgf.common.observability; mgf-cloud consumes conformant schema | ⏳ |
| OB-10 | OBSERVABILITY | mgf.common handles canonical LogRecord wire shape; bootstrap() uses JsonFormatter which emits byte-identical records | ⏳ |
| OB-11 | OBSERVABILITY | Log statistics not explicitly visible in mgf-cloud codebase; may be delegated to mgf.common's LogStatsCollector if enabled | ⏳ |
| NM-01 | NAMING | pyproject.toml:2 — name = "mgf-cloud" (hyphens, not underscores) | ⏳ |
| NM-02 | NAMING | src/mgf/ has no __init__.py; implicit namespace package under mgf.* (verified by find: only __init__.py files are under mgf/cloud/, mgf/cloud/cli/, mgf/cloud/providers/, mgf/cloud/web/) | ⏳ |
| NM-03 | NAMING | git remote origin shows ssh://git@codeberg.org/magogi-admin/mgf-cloud.git (hyphen slug, matching NM-01) | ⏳ |
| CF-01 | CONFIGURATION | config.py:43-89 typed frozen pydantic `Credentials` + config.py:177-202 `load()` resolve/validate at the boundary; CF-02 precedence ✅ corroborates an owned schema, but per-MUST load-time schema-validation not separately pinned in this batch — applicable, conservatively ⏳ (added in completeness pass) | ⏳ |
| CF-02 | CONFIGURATION | config.py:177-202 (load function) implements precedence: explicit path → $MGF_CLOUD_CLOUDS_YAML → OS_* env → standard clouds.yaml search paths, matching CF-02's top-to-bottom override pattern | ⏳ |
| CF-03 | CONFIGURATION | Config inputs are the external clouds.yaml (OpenStack format) + a flat rates TOML/env; no mgf-cloud-owned versioned config schema requiring a schema_version + migration path (added in completeness pass) | N/A |
| CF-04 | CONFIGURATION | mgf-cloud reads clouds.yaml/rates and writes no persistent config/state file (the bundle is a tempdir tarball, SC-04); the atomic-write/0o600 config-write premise is absent (added in completeness pass) | N/A |
| CF-05 | CONFIGURATION | config.py:55,58 uses SecretStr for application_credential_secret and password; no committed .env or clouds.yaml files containing secrets; credentials loaded only from external sources (files, env, vault-style) | ⏳ |
| CF-06 | CONFIGURATION | config.py:124-149 from_clouds_yaml + rates parsing accept the documented keys; unknown-key (forbid-extra) rejection on the owned surface not per-MUST evidenced in this batch — conservatively ⏳ (added in completeness pass) | ⏳ |
| CF-07 | CONFIGURATION | No satellite/sub-config files (hooks/schedules/profiles); configuration is a single clouds.yaml + one rates source, so the same-shape sub-config MUST has no surface (added in completeness pass) | N/A |
| CF-08 | CONFIGURATION | Config flows via load()/from_clouds_yaml and is passed to get_provider(name, credentials=...) (no module-global Settings singleton apparent); the inject-by-argument discipline is not separately pinned in this batch — conservatively ⏳ (added in completeness pass) | ⏳ |
| CF-09 | CONFIGURATION | config.py:177-202 load() accepts an explicit clouds.yaml path; the CLI exposes a `--clouds-yaml` flag (§2) and the precedence chain (CF-02) includes the standard clouds.yaml search-path default (added in completeness pass) | ⏳ |
| CF-10 | CONFIGURATION | tests/unit/test_cost.py:16 (_NOW = fixed datetime); test_ops_verbs.py:76-77 uses monkeypatch to clear env vars; cost.estimate() accepts explicit now parameter for tests, avoiding env-var leakage | ⏳ |
| CF-11 | CONFIGURATION | Young 0.1.x config surface; no renamed owned config field requiring a back-compat pydantic Field alias + deprecation warning (clouds.yaml keys follow the external OpenStack schema) (added in completeness pass) | N/A |
| CF-12 | CONFIGURATION | mgf-cloud has no pydantic config schema with mutually-exclusive backend variants; provider selection is code-level (get_provider function), not config-modeled | N/A |
| TM-01 | TIME | cost.py:23 imports UTC; lines 163,185 use datetime with UTC (ts.replace(tzinfo=UTC), datetime.now(UTC)); cli/_bundle.py:24,76 uses datetime.now(tz=UTC); all datetimes crossing boundaries are tz-aware UTC | ⏳ |
| TM-02 | TIME | cli/_app.py:185 serializes report.generated_at via .isoformat() to JSON, producing ISO-8601 format with timezone offset; cost.py:159 parses ISO-8601 timestamps with fromisoformat() | ⏳ |
| TM-03 | TIME | remote.py:198,221 uses time.perf_counter() for duration measurement; infomaniak.py:160,189 uses time.perf_counter() for request timing; no wall-clock subtraction for elapsed time | ⏳ |
| TM-04 | TIME | cli/_bundle.py:76 calls datetime.now(tz=UTC) directly without clock injection in testable function run_bundle; test_ops_verbs.py:138-150 tests bundle but passes explicit output path, so timestamp generation is uncovered; cost.estimate() properly injects clock (now parameter with default at line 185), showing the pattern is known | ⏳ |
| TM-07 | TIME | grep for PST/EST/IST/CET/CEST returns no matches; all timezone references use UTC (from datetime import UTC); no pytz or POSIX abbreviations found in src/ | ⏳ |
| TM-08 | TIME | web/_app.py:186-187 uses async def with await file.read() (proper async pattern); grep finds no time.sleep() or asyncio.sleep() calls in src/; no blocking sleeps in async code | ⏳ |
| PF-01 | PERFORMANCE | mgf-cloud is network-bound (OpenStack/SSH calls dominate latency); no local perf-sensitive code paths to baseline. Tracker acknowledges this as 'N/A (leaning)'. | N/A |
| PF-02 | PERFORMANCE | pyproject.toml:245–246 defines `perf` marker; line 238 excludes it via `addopts = "-m 'not perf'"` | ⏳ |
| PF-03 | PERFORMANCE | No tests/perf/baselines.json file exists; not applicable to I/O-bound application with no local hot paths | N/A |
| PF-04 | PERFORMANCE | No perf tests or re-baselining workflow in repo; not applicable without PF-01/PF-03 infrastructure | N/A |
| PF-05 | PERFORMANCE | No tests/perf/ conftest or harness infrastructure exists; not applicable without active perf tests | N/A |
| PF-06 | PERFORMANCE | SHOULD rule (not MUST); PUBLIC_API.md does not document perf characteristics but conformance tracker notes correctly as N/A | N/A |
| PF-07 | PERFORMANCE | No perf tests exist to surface comparison numerics; not applicable without PF-01/PF-03/PF-05 infrastructure | N/A |
| PF-08 | PERFORMANCE | No hardware-tier recording in baselines.json; not applicable to network-bound application without local perf baselines | N/A |
| PR-01 | PRESENTATION_LAYER | .importlinter:16–39 forbids `PySide6`, `PyQt6`, `click`, `typer`, `fire`, `rich`, `prompt_toolkit`, `qasync` at mgf.cloud root; lint-imports enforced in CI | ⏳ |
| PR-02 | PRESENTATION_LAYER | docs/inprogress/MGF_STANDARDS_CONFORMANCE.md:101 — declined with documented rationale: single repo with shared core + PR-04's independence contract enforces decoupling (indexed SHOULD) | ⏳ |
| PR-03 | PRESENTATION_LAYER | Architecture: shared library (models/config/cost/remote/providers) + independent CLI (src/mgf/cloud/cli/) and web (src/mgf/cloud/web/) consumers. Not canonical three-layer but equivalent shape per PR-03 §5.5 variance clause; spirit met (framework-free shared layer, independent UI implementations) | ⏳ |
| PR-04 | PRESENTATION_LAYER | .importlinter:45–76 contains `mgf-cloud-core-light` contract (forbids provider SDK + web framework in core modules) + `mgf-cloud-cli-web-independence` contract (enforces cli/web separation, whitelisting only lazy launcher); mechanically enforced in CI | ⏳ |
| PR-05 | PRESENTATION_LAYER | .importlinter:69–76 `independence` contract ensures mgf.cloud.cli and mgf.cloud.web never import each other (except cli._app → web for launcher); both import shared library (models/config/cost/remote/providers) as the contract permits | ⏳ |
| PR-06 | PRESENTATION_LAYER | SHOULD rule (not MUST); conformance tracker acknowledges N/A: 'output goes through CLI `emit` helper + web templates', not stdlib-only fmt module | N/A |
| PR-07 | PRESENTATION_LAYER | docs/inprogress/MGF_STANDARDS_CONFORMANCE.md §Z covers only PR-01 + PR-04; missing enumeration of PR-03/PR-05/PR-07 per audit-outcomes taxonomy. PR-07 itself is present but incomplete. | ⏳ |
| GUI-01 | GUI_CONSUMERS | mgf-cloud's GUI is FastAPI/Jinja2 server-rendered (src/mgf/cloud/web/_app.py:14 imports fastapi, not PySide6); Qt framework rules do not apply | N/A |
| GUI-02 | GUI_CONSUMERS | No Qt worker pattern needed; web GUI is async server-side (uvicorn), not client-side blocking calls | N/A |
| GUI-03 | GUI_CONSUMERS | No CancellationToken plumb-through needed; web GUI is stateless HTTP handlers, not long-running client operations | N/A |
| GUI-04 | GUI_CONSUMERS | No worker threads in FastAPI app; exception handling at HTTP level via @app.exception_handler(AppError) in web/_app.py:42–50 | N/A |
| GUI-05 | GUI_CONSUMERS | No Qt message handler bridge needed; mgf.common.bootstrap wired at web entry point (web/_app.py:254–258) for logging, not Qt excepthook | N/A |
| GUI-06 | GUI_CONSUMERS | No Qt presentation widgets; web routes are FastAPI handlers calling provider methods directly + rendering Jinja templates | N/A |
| GUI-07 | GUI_CONSUMERS | No streaming worker signals; web GUI uses HTTP request/response, not streaming QObject signals | N/A |
| GUI-08 | GUI_CONSUMERS | No QSettings; web GUI is stateless (state in cloud resources); no BaseAppSettings in web layer | N/A |
| GUI-09 | GUI_CONSUMERS | No pytest-qt; web GUI tests use FastAPI TestClient + httpx (tests/integration/test_web_*.py), not Qt framework | N/A |
| GUI-10 | GUI_CONSUMERS | No capability-query UI controls; web GUI features are stateless; no disable/hide logic based on .capabilities() | N/A |
| TS-01 | TESTING | tests/test_mirror.py:19-43 explicitly maps every source module to mirror test file(s) with documented allow-list; test_every_source_module_is_in_the_allow_list() enforces no gaps | ⏳ |
| TS-02 | TESTING | Unit suite uses FakeProvider (tests/unit/test_providers.py) and mocked clients; no real cloud credentials, network calls, or external daemon initialization in default pytest run | ⏳ |
| TS-03 | TESTING | Tests in isolated unit/integration/smoke directories; conftest.py at root (tests/conftest.py:1-4) is minimal with no shared module-state mutations | ⏳ |
| TS-04 | TESTING | pyproject.toml:260-261 sets filterwarnings = ['error', 'ignore::starlette.exceptions.StarletteDeprecationWarning'] | ⏳ |
| TS-05 | TESTING | pyproject.toml:235-236 sets addopts = ['--strict-markers', '--strict-config', ...] | ⏳ |
| TS-06 | TESTING | pyproject.toml:284 fail_under = 80; .woodpecker.yml:92-93 runs coverage gate on 3.12 job; coverage report enforces threshold | ⏳ |
| TS-07 | TESTING | mgf-cloud raises AppError subclasses from mgf.common (ConfigError, ProviderError, etc.) not custom typed exceptions; no locally-defined AppError hierarchy requiring TS-07 test coverage | N/A |
| TS-08 | TESTING | No exception translation at I/O boundaries in src/ (OpenStack/boto3 errors bubble to caller per provider protocol); TS-08 scope is providers/base.py:CloudProvider which is an abstract protocol with no translation | N/A |
| TS-09 | TESTING | No best-effort observer fan-out in src/ (EH-10 scope); CLI handlers and web endpoints use direct try/except, not observer patterns | N/A |
| TS-10 | TESTING | tests/unit/test_config.py tests credential parsing and validation; tests/unit/test_exceptions.py pins exception fields; tests/unit/test_providers.py asserts provider rejection on missing creds | ⏳ |
| TS-11 | TESTING | No GUI worker threads (no PySide6/Qt/QThread); pyproject.toml has FastAPI web app but no GUI framework | N/A |
| TS-12 | TESTING | No async coroutines in src/mgf/cloud or tests/; all code is sync; pytest-asyncio not listed in [dev] (pyproject.toml:90-106) | N/A |
| TS-13 | TESTING | No round-trip (parse/serialize, save/load) operations using Hypothesis; no property tests in test suite | N/A |
| TS-14 | TESTING | No performance budgets or @pytest.mark.perf tests; perf marker registered (pyproject.toml:256) but no benchmarks committed | N/A |
| TS-15 | TESTING | tests/integration/test_infomaniak_live.py:42-44 marked @pytest.mark.integration with skipif(not _LIVE); requires MGF_CLOUD_LIVE=1 env var to run | ⏳ |
| TS-16 | TESTING | test_exceptions.py:11-26 uses assert with message context; test_mirror.py:55-56 raises AssertionError with sorted() context; test_imports_smoke.py:15 uses f-string assert message | ⏳ |
| TS-17 | TESTING | tests/conftest.py exists at root (shared by all); no tests/unit/conftest.py or tests/integration/conftest.py (fixtures are file-local or root-level only) | ⏳ |
| TS-18 | TESTING | pyproject.toml:258 registers 'slow: legacy marker for tests >1s wall-clock (TS-18). Deprecated; removed in v2.0.'; addopts excludes '-m not perf and not slow' | ⏳ |
| TS-19 | TESTING | pyproject.toml:245-259 declares 13 layer + orthogonal markers (smoke, e2e, integration, contract, property, regression, fuzz, concurrency, conformance, use_case, perf, stress, slow); --strict-markers enforces registry | ⏳ |
| TS-20 | TESTING | tests/ partitioned: unit/ (default), integration/ (@pytest.mark.integration), smoke/ (@pytest.mark.smoke); each directory contains test_*.py files | ⏳ |
| TS-21 | TESTING | tests/smoke/test_imports_smoke.py marked @pytest.mark.smoke; test_every_public_name_reachable() imports mgf.cloud and asserts every __all__ name is reachable; run completes in <100ms (7ms per .gates/last-run/run.jsonl) | ⏳ |
| TS-22 | TESTING | pyproject.toml markers tier mapping (tier-0/1/2/3); .woodpecker.yml:146 runs 'mtest --tier 0' + supervisor accepts --tier N syntax; mgf-test-supervisor>=0.1.3 in [dev] (pyproject.toml:101) | ⏳ |
| TS-23 | TESTING | .gates/ directory present with supervisor self-check (line 130-135) and tier-0 (line 140-146) runs in .woodpecker.yml; mtest subprocess invocation never imports project under test | ⏳ |
| TS-24 | TESTING | .gates/last-run/run.jsonl contains one-per-line JSON objects with schema_version (1.1.0), test_id, outcome, duration_ms, tier, markers, code, summary, detail, why, remediation, captured_stdout/stderr, perf, run_id, ts_iso fields | ⏳ |
| TS-25 | TESTING | .gates/quarantine.json present (0600 mode); mgf-test-supervisor>=0.1.3 (pyproject.toml:101) implements auto-quarantine; entry in pyproject.toml markers (line 245) | ⏳ |
| TS-26 | TESTING | Pure-Python library (no compiled artifacts, no Zig/Go/Rust/C dependencies); pyproject.toml build-backend is hatchling with no native extensions | N/A |
| TS-27 | TESTING | .gates/last-run/failures/ directory present and populated by supervisor; each failure gets a bundle file carrying traceback, captured streams, process state, environment fingerprint, and perf attribution | ⏳ |
| TS-28 | TESTING | No @pytest.mark.perf tests in suite; perf_span context manager not used in src/ or tests/; perf marker registered but no benchmarks implement attribution (L2 deferred) | N/A |
| REL-01 | RELEASING | git tag -l: v0.1.0, v0.1.1, v0.1.2, v0.1.3; git cat-file -t on each returns 'tag' (all annotated, not lightweight) | ⏳ |
| REL-02 | RELEASING | Version sequence: 0.1.0 → 0.1.1 → 0.1.2 → 0.1.3 monotonically increasing; each tag on distinct commit; dist/ builds are from tagged commits only | ⏳ |
| REL-03 | RELEASING | PUBLIC_API.md:3-7 carries literal master-HEAD banner stating 'Verify your pinned version via mgf.cloud.__version__'; references PUBLIC_API.json as machine-readable companion | ⏳ |
| REL-04 | RELEASING | .woodpecker.yml:254-256 stores devpi_password as Codeberg secret (from_secret:), never plaintext; environment variable only in publish step (tag-scoped) | ⏳ |
| REL-05 | RELEASING | CHANGELOG.md shows version bumps (0.1.0 → 0.1.1 → 0.1.2 → 0.1.3) with distinct content per release; no silent re-uploads or version reuse | ⏳ |
| REL-06 | RELEASING | .woodpecker.yml:176-280 implements strict ordering: tag-coherence (line 185-208) → smoke (line 213-231) → publish (line 238-260) → verify-devpi (line 264-280); each stage depends_on the prior; green gates required before tag-coherence | ⏳ |
| REL-07 | RELEASING | FEEDBACK.md:§2 states 'No papers yet'; release v0.1.3 (CHANGELOG.md:8) touches only mgf-common pin, not a FEEDBACK closure; REL-07 scope binds only when a PAPER is shipped | N/A |
| REL-08 | RELEASING | .woodpecker.yml:213-231 smoke step: pip installs freshly-built dist/mgf_cloud-*.whl into /tmp/smoke ephemeral venv; asserts __version__ matches tag (line 224-228); runs mgf-cloud --version entry point (line 231) | ⏳ |
| REL-09 | RELEASING | FEEDBACK.md:§2 'No papers yet'; no FEEDBACK entries shipped in v0.1.3; REL-09 scope binds only when a status flip occurs | N/A |
| REL-10 | RELEASING | Single library; cohort-walk applies only when mgf-common MINOR breaks a dependent's pin upper-bound; REL-10 is federation-coordination, not per-library | N/A |
| REL-11 | RELEASING | Single library; Phase A/B split is a cohort-wave discipline; not applicable to standalone releases | N/A |
| REL-12 | RELEASING | Single library; Phase A pytest-denial fallback is an agent discipline for multi-library waves; not applicable to standalone releases | N/A |
| REL-13 | RELEASING | Federation consistency gate (mgf-common gen_mgf_libraries.py) is supervised by mgf-common maintainer, not per-library; mgf-cloud is a consumer of the gate, not subject to it at release time | N/A |
| REL-14 | ✅ | Released via the cohort/tag flow; releasing (not re-tagging) clears any main-vs-tag drift. | New MUST, corpus v3.3.0 (DP-3/CIR-17/PAPER-130). Release-currency enforced by the fleet currency check. |
| PKG-01 | PACKAGE_DISTRIBUTION | pyproject.toml:307 index-url = 'https://195.15.203.250.sslip.io/magogi/prod/+simple/' (devpi); pyproject.toml:44 and :116-121 explicitly acknowledge 'self-hosted devpi index' not Codeberg; standard requires Codeberg magogi-admin registry | ⏳ |
| PKG-02 | PACKAGE_DISTRIBUTION | .woodpecker.yml:260 uploads to 'https://195.15.203.250.sslip.io/magogi/prod/' (devpi); line 275 verifies on 'https://195.15.203.250.sslip.io/magogi/prod/+simple/mgf-cloud/' (devpi simple index); standard requires https://codeberg.org/api/packages/magogi-admin/pypi endpoints | ⏳ |
| PKG-03 | PACKAGE_DISTRIBUTION | .woodpecker.yml:254-256 uses devpi_password Woodpecker secret for devpi; standard requires Codeberg access token with write:package scope for the magogi-admin account | ⏳ |
| PKG-04 | PACKAGE_DISTRIBUTION | .woodpecker.yml:238-260 publish step uploads to devpi (line 260 'https://195.15.203.250.sslip.io/magogi/prod/'); standard requires ordered flow to Codeberg with build-in-CI + twine check + upload to Codeberg + REL-01 tag | ⏳ |
| PKG-05 | PACKAGE_DISTRIBUTION | .woodpecker.yml:264-280 verify-devpi queries devpi simple index (line 275); standard requires POST-publish verification against Codeberg REST API (…/api/v1/packages/magogi-admin/pypi/<name>/<version>), never pypi.org | ⏳ |
| PKG-06 | PACKAGE_DISTRIBUTION | pyproject.toml:307 bare index-url = devpi (not Codeberg); no [tool.uv.sources] explicit per-package pinning as standard PKG-06 requires to avoid dependency-confusion | ⏳ |
| PKG-07 | PACKAGE_DISTRIBUTION | Devpi allows delete+re-upload (immutable by policy, not by index); PKG-07 governs recovery workflow, applicable to index operator, not library repo | N/A |
| PKG-08 | PACKAGE_DISTRIBUTION | Retention is account-level (magogi devpi instance quota), not per-library-repo artifact; PKG-08 scope is org/account-wide package hygiene, not mgf-cloud repository | N/A |
| PKG-09 | PACKAGE_DISTRIBUTION | .woodpecker.yml:13-18 when: clause includes 'event: tag' with 'ref: refs/tags/v*'; build (line 152) runs before tag; publish (line 238) is tag-driven but targets devpi, not Codeberg; standard requires CI publishing MUST be tag-driven to Codeberg with token scope tied to tag events | ⏳ |
| PKG-10 | PACKAGE_DISTRIBUTION | pyproject.toml:2 name = 'mgf-cloud' (hyphenated); src/mgf/cloud/ is dotted import (PEP 420 namespace); wheel normalizes to mgf_cloud per PEP 503; [project.urls] Homepage/Issues point to Codeberg repo | ⏳ |
| PKG-11 | PACKAGE_DISTRIBUTION | mgf-cloud ships no agent/federation version-check tooling (scripts/ is empty bar __init__.py); PKG-11 scope is agents checking published versions, not applied to this library | N/A |
| PKG-12 | PACKAGE_DISTRIBUTION | grep -rn 'pypi.org' over src/, pyproject.toml, .woodpecker.yml, README.md, CHANGELOG.md returns no publishing/distribution surface refs to pypi.org; only third-party package refs permitted (e.g., boto3 from PyPI) | ⏳ |
| DOC-01 | DOCUMENTATION | Root docs present: README.md, LICENSE, CHANGELOG.md, CONTRIBUTING.md, SECURITY.md, FEEDBACK.md, AGENTS.md, STARTHERE.md, DEPS.md, FEDERATION.md at repo root; docs/ directory exists with six buckets (standards, reference, inprogress, claude, cutover, recipes, memory). | ⏳ |
| DOC-02 | DOCUMENTATION | Docs organized into six buckets: docs/standards/README.md (pointer), docs/reference/README.md (charter), docs/inprogress/README.md (workspace), docs/claude/README.md, docs/cutover/README.md, docs/recipes/README.md, plus docs/memory/ (MEMORY.md present but no README.md — see DOC-03). | ⏳ |
| DOC-03 | DOCUMENTATION | docs/memory/ lacks README.md charter; other buckets (standards, reference, inprogress, claude, cutover, recipes) have README.md with charter. docs/memory/MEMORY.md exists (AG-17) but bucket README missing per DOC-03 requirement. | ⏳ |
| DOC-04 | DOCUMENTATION | CHANGELOG.md exists at repo root, follows Keep a Changelog format, entries include version headers, categories (Changed/Added), and describe breaking changes with cross-references. | ⏳ |
| DOC-05 | DOCUMENTATION | docs/cutover/v0.1.0.md exists (2400 bytes, created 2026-06-14); documents the 0.1.0 cutover path. | ⏳ |
| DOC-06 | DOCUMENTATION | No living priority trackers; mgf-cloud maintains only adoption/conformance trackers (MGF_STANDARDS_CONFORMANCE.md, etc.), which follow different DOC-15/CFM-03 shape, not DOC-06 priority-tracker shape. | N/A |
| DOC-07 | DOCUMENTATION | docs/claude/CLAUDE.md exists, contains federation-wide briefing pointer + project-specific rules (standing instructions, top-30 rules, gotchas), dense-lookup format per DOC-07. | ⏳ |
| DOC-08 | DOCUMENTATION | PUBLIC_API.md (4647 bytes) enumerates all 24 names from __all__ with Kind/Stability/Since/Notes; PUBLIC_API.json (598 bytes) generated from __all__; tests/unit/test_public_api_pin.py pins md↔__all__↔json drift. | ⏳ |
| DOC-09 | DOCUMENTATION | PUBLIC_API.md names are drift-detected via test_public_api_pin.py (pins md↔json↔__all__); mgf-common cross-references swept via linting; STARTHERE.md updated to point to mgf-fed instead of mgf-common per DOC-09 and AG-14 propagation. | ⏳ |
| DOC-10 | DOCUMENTATION | FEEDBACK.md (2513 bytes) is repo-scoped (mgf-cloud issues file here), with clear guidance to file federation-wide issues in mgf-common/FEEDBACK.md; docs/inprogress/ reserved for internal trackers. | ⏳ |
| DOC-11 | DOCUMENTATION | No closed inprogress trackers yet to archive; docs/inprogress/ contains only active tracker shell (RELIABILITY_AND_ACCURACY.md, SECURITY_HARDENING.md, PERFORMANCE_AND_CAPACITY.md marked 'initial — no items yet'). | N/A |
| DOC-12 | DOCUMENTATION | Docs use relative links throughout (../reference/foo.md style); file paths use src/mgf/cloud/... format; headings hierarchical (## §N. Title pattern present in docs/standards/README.md, docs/inprogress/README.md, etc.). | ⏳ |
| DOC-13 | DOCUMENTATION | FEEDBACK.md header states 'mgf-cloud-specific → file HERE' and directs federation-wide to mgf-common/FEEDBACK.md; repo-scoped discipline enforced by file location rule. | ⏳ |
| DOC-14 | DOCUMENTATION | Federation sibling (per ADP-04 carve-out): MGF_ADOPTION.md not required for siblings; adoption relationship documented in mgf-common's federation_roadmap.md and mgf-cloud's own CHANGELOG. DOC-14 MUST applies to consumer applications only. | N/A |
| DOC-15 | DOCUMENTATION | docs/inprogress/MGF_STANDARDS_CONFORMANCE.md (5800+ bytes) exists, declares L2 conformance level at top, provides per-MUST audit with ✅/⏳/N/A markers, open-gap tracking (§4), decline-with-rationale (§3), audit log (§5), per-MUST evidence (§Z). | ⏳ |
| DOC-16 | DOCUMENTATION | DEPS.md (3501 bytes) at repo root contains §1 what mgf-cloud depends on (mgf-common>=0.47,<0.50; pydantic; pyyaml) and §2 who depends on mgf-cloud (mgf-fed is sole consumer listed). | ⏳ |
| DOC-17 | DOCUMENTATION | FEDERATION.md (833 bytes) is a pointer stub; opens with 'pointer' heading, links to mgf-common/FEDERATION.md as canonical contract, does NOT duplicate contract content; directs readers to linked location. | ⏳ |
| DOC-18 | DOCUMENTATION | 2026-06-25 re-audit (conformance tracker §5) followed DOC-18: when PUBLIC_API surface was enumerated (AP-10/AP-11), same commits updated CHANGELOG.md, PUBLIC_API.json, MGF_STANDARDS_CONFORMANCE.md, and conformance tracker ledger; change propagated to all dependents (same commit discipline observed in recent history). | ⏳ |
| DOC-19 | DOCUMENTATION | LESSON_LEARNED.md (895 bytes) exists at repo root, append-only structure with dated entries (single entry: 'Build federation libs with providers lazy-loaded' from 2026-06-14). | ⏳ |
| AG-01 | AGENTS | AGENTS.md (1679 bytes) exists at repo root; marks itself as thin pointer ('managed by mgf-fed catch-up — do not edit it'); directs to mgf-fed agents CLI for canonical briefing; marked GENERATED. | ⏳ |
| AG-02 | AGENTS | AGENTS.md points to mgf-fed agents as canonical briefing source (first command readers are told to run); federation-wide briefing not duplicated in AGENTS.md. | ⏳ |
| AG-03 | AGENTS | Agent signing-trailer rule (Signed-off-by + Co-Authored-By); applies when agents write commits. Infrastructure in place (.gitmessage, .githooks/prepare-commit-msg, scripts/check_commit_trailers.py) and gated by CI (commit-trailers step in .woodpecker.yml:53-59). | N/A |
| AG-04 | AGENTS | Agents file friction as FEEDBACK papers when they encounter it; applies at session time, not a codebase compliance rule. | N/A |
| AG-05 | AGENTS | Agent memory verification rule (verify recalled facts before acting); applies during agent sessions, not a codebase rule. | N/A |
| AG-06 | AGENTS | Risky-operation confirmation rule; applies during agent sessions when the agent is operating the codebase. | N/A |
| AG-07 | AGENTS | TaskCreate for multi-step work; applies during agent sessions, not a codebase rule. | N/A |
| AG-08 | AGENTS | Memory writes federation-scoped (not session-scoped); applies to agent runtime behavior, not codebase. | N/A |
| AG-09 | AGENTS | Verify federation sibling published version; applies during agent sessions when recommending from published versions. | N/A |
| AG-10 | AGENTS | Standards drift filing rule; applies when agents notice drift during code review. | N/A |
| AG-11 | AGENTS | Cross-project feedback routing (file in TARGET project's FEEDBACK.md); applies when agents file papers. | N/A |
| AG-12 | AGENTS | Project-scoped agent briefing via mgf-fed agents --project; depends on mgf-fed CLI implementation (not a mgf-cloud codebase rule). | N/A |
| AG-13 | AGENTS | Only mgf-common supervisor may change a library; enforcement rule (no agents change mgf-cloud unilaterally). | N/A |
| AG-14 | AGENTS | Change propagation followed in 2026-06-25 re-audit (agents walked the DOC-18 matrix): PUBLIC_API enumeration, CHANGELOG, conformance ledger, and test pins updated in tandem (same-commit discipline). | ⏳ |
| AG-15 | AGENTS | Agent empowerment charter (agents empowered to exercise judgment, file FEEDBACK, use channels); applies to agent autonomy, not codebase structure. | N/A |
| AG-16 | AGENTS | Standards corpus resolvable: pyproject.toml line 57-59 declares optional [standards] extra with mgf-common[standards]>=0.47,<0.50; dev extra includes mgf-standard>=0.1.6,<0.2; agents can resolve mgf-fed standards CLI. | ⏳ |
| AG-17 | AGENTS | In-repo agent memory: docs/memory/MEMORY.md exists (582 bytes), contains AG-17 index with template guidance, one-fact-per-file structure (though no entries yet seeded). Travels with repo, survives fresh clone. | ⏳ |
| AG-18 | AGENTS | Git configuration in place: .gitignore ignores my_stuff/ (line 64), .gitmessage exists (569 bytes), .githooks/prepare-commit-msg exists, scripts/check_commit_trailers.py exists; .woodpecker.yml runs commit-trailers gate (WF-02 enforcement). | ⏳ |
| AG-19 | AGENTS | Runtime auto-memory backing (version-controlled private store); applies to agent machine-local setup, not codebase rule. | N/A |
| WF-01 | WORKFLOWS | .woodpecker.yml line 13-18: when clause includes push, pull_request, tag (v*), manual events; CI runs on every push and PR. | ⏳ |
| WF-02 | WORKFLOWS | .woodpecker.yml implements four gates: lint (line 33-44: ruff check + lint-imports), typecheck (line 62-67: mypy --strict), test (line 73-100: pytest on 3.11/3.12/3.13 with coverage gate), commit-trailers (line 53-59); all gates block on red. | ⏳ |
| WF-03 | WORKFLOWS | PKG-01 fleet-infra deferred (per conformance tracker §4): publish channel reconciliation (Codeberg vs devpi) blocked; mgf-cloud cannot unilaterally change without breaking template-parity. Tag-driven publish infrastructure partial. | ⏳ |
| WF-04 | WORKFLOWS | Publish credentials stored in CI secret store: .woodpecker.yml publish step would reference codeberg_package_token CI secret (per WORKFLOWS.md rule WF-04); platform secret store handles access control. | ⏳ |
| WF-05 | WORKFLOWS | Tag-version coherence check deferred with WF-03 (PKG-01 fleet-infra); would be implemented in publish workflow step once channel is settled. | ⏳ |
| WF-06 | WORKFLOWS | Fresh wheel build requirement deferred with WF-03 (PKG-01 fleet-infra); publish workflow would build wheel in CI rather than reusing dist/. | ⏳ |
| WF-07 | WORKFLOWS | Pre-publish smoke deferred with WF-03 (PKG-01 fleet-infra); would install freshly-built wheel and import package before publish step. | ⏳ |
| WF-08 | WORKFLOWS | Post-publish verify deferred with WF-03 (PKG-01 fleet-infra); would poll Forgejo registry API to confirm artifact appearance after upload. | ⏳ |
| WF-09 | WORKFLOWS | .woodpecker.yml pins external dependencies: python:3.12-slim (line 34, 62, etc. — all steps use specific minor version), woodpeckerci/plugin-git:2.9.2 (line 27). | ⏳ |
| WF-10 | WORKFLOWS | .woodpecker.yml test matrix runs in parallel: test-3.11 (line 73), test-3.12 (line 80), test-3.13 (line 95) execute independently; no sequential dependencies between test versions. | ⏳ |
| WF-11 | WORKFLOWS | WF-11 fleet-infra deferred (per conformance tracker §4): Wants `uv sync --frozen` from hash-pinned uv.lock; .woodpecker.yml is generated template artifact. Full-graph fleet lock doesn't resolve due to devpi backfill gap. Fleet-wide adoption blocked. | ⏳ |
| WF-12 | WORKFLOWS | .woodpecker.yml steps surface exit codes and log context: failure messages printed to stdout/stderr (captured by Woodpecker), step names are descriptive (lint, typecheck, test-3.11, etc.), coverage gate provides explicit failure message on threshold breach. | ⏳ |
| WF-13 | WORKFLOWS | .woodpecker.yml line 1-3: marked GENERATED from mgf-standard/templates/woodpecker/; template source noted; regenerate comment present; never hand-edited discipline enforced by drift-check. | ⏳ |
| WF-14 | N/A | CI installs resolve via `pip` (no `uv` verb in .woodpecker.yml). | New MUST, corpus v3.3.0 (DP-5/CIR-04). WF-14 binds CI `uv` verbs; N/A here. |
| OP-01 | OPERABILITY | src/mgf/cloud/cli/_version.py implements version_facts() + render_version() returning package version (0.1.3 from metadata), git SHA, Python version (3.x), platform, dependency versions; tests/unit/test_ops_verbs.py::test_version_* verifies output. | ⏳ |
| OP-02 | OPERABILITY | src/mgf/cloud/cli/_doctor.py implements run_doctor() returning offline health checks (provider availability, credentials parse, rates parse) via mgf.common.doctor.DoctorBundle; exit code = failed-check count; tests/unit/test_ops_verbs.py::test_doctor_* verifies. | ⏳ |
| OP-03 | OPERABILITY | .woodpecker.yml lint step (line 42): grep verifies no placeholder URLs (example.com, <org>, <your-, placeholder-, TODO-URL, FIXME-URL) in pyproject.toml/README.md; pyproject.toml lines 112-114 contain live URLs (codeberg.org/magogi-admin/mgf-cloud). | ⏳ |
| OP-04 | OPERABILITY | Partially verified: README.md declares status 'In active construction (0.1.x)' and recent pin (`mgf-cloud = '>=0.1,<0.2'`); version is current (0.1.3); test counts should be verified (TS-06 coverage gate 80% on the main branch). Full OP-04 mechanizable check (pytest --collect-only) not yet gated in CI. | ⏳ |
| OP-05 | OPERABILITY | src/mgf/cloud/cli/_explain.py implements run_explain() showing resolved CloudConfig + which source won (explicit/env/yaml/search); secrets redacted via SecretStr (**********); test test_explain_reports_source_and_redacts asserts secret never leaks. | ⏳ |
| OP-06 | OPERABILITY | mgf-cloud is CLI operator tooling (not a service); logs are operational not user-facing; log access via mgf.common.bootstrap() which configures rotating file + console sink (not a OP-06 'recent logs accessible' requirement). | N/A |
| OP-07 | OPERABILITY | src/mgf/cloud/cli/_bundle.py implements run_bundle() producing .tar.gz diagnostic artifact (version + explain output + doctor + log tail + crash reports), all text redacted via mgf.common.observability.Redactor; test test_bundle_writes_redacted_tarball verifies. | ⏳ |
| OP-08 | OPERABILITY | No state directories (mgf-cloud is CLI tooling); crash reports + logs managed by mgf.common bootstrap (mgf-common responsibility, not mgf-cloud's). | N/A |
| OP-09 | OPERABILITY | Service-only rule (production safety guards); mgf-cloud is operator tooling, not a deployed service. | N/A |
| OP-10 | OPERABILITY | Service-only rule (deployable-artifact versioning); mgf-cloud ships as a wheel package, not a containerized service. | N/A |
| OP-11 | OPERABILITY | Service-only rule (alert routing + runbooks); mgf-cloud is operator tooling with no alerting surface. | N/A |
| OP-12 | OPERABILITY | Service-only rule (backup + restore drills); mgf-cloud is stateless tooling with no persistent data to back up. | N/A |
| DEP-01 | DEPLOYMENT | Service-only rule (Infrastructure-as-Code); mgf-cloud is operator tooling, not a deployed web service. | N/A |
| DEP-02 | DEPLOYMENT | Service-only rule (Configuration-as-Code on VMs); not applicable to operator tooling. | N/A |
| DEP-03 | DEPLOYMENT | Service-only rule (immutable release artefacts); mgf-cloud is a library, not a deployed service. | N/A |
| DEP-04 | DEPLOYMENT | Service-only rule (production secrets management); not applicable to operator tooling. | N/A |
| DEP-05 | DEPLOYMENT | Service-only rule (environment-explicit deploy scripts); mgf-cloud is not a deployed service. | N/A |
| DEP-06 | DEPLOYMENT | Service-only rule (reversible deploys + rollback runbooks); not applicable to operator tooling. | N/A |
| DEP-07 | DEPLOYMENT | Service-only rule (deploy/ directory structure); mgf-cloud is not a deployed web service. | N/A |
| DEP-08 | DEPLOYMENT | Service-only rule (production observability); mgf-cloud is operator tooling, not a page-able service. | N/A |
| DEP-09 | DEPLOYMENT | Service-only rule (DNS + TLS infrastructure); not applicable to operator tooling. | N/A |
| DEP-10 | DEPLOYMENT | Service-only rule (first-production-cut runbook); mgf-cloud is not a deployed service. | N/A |
| DEP-11 | DEPLOYMENT | Service-only rule (multi-environment deployability); mgf-cloud is operator tooling with no deployment topology. | N/A |
| SP-01 | SCOPE | SCOPE.md §1 lists IN-scope items: compute, block storage, object storage, networking, bootstrap, provider abstraction, CLI + web GUI surfaces. | ⏳ |
| SP-02 | SCOPE | SCOPE.md §2 lists OUT-of-scope with reasons: full app deployment (→Ansible), declarative IaC (→Terraform), k8s (→provider's managed k8s), multi-user web (future), DNS/billing/account (not VM-or-storage), OpenStack passthrough (→openstacksdk). | ⏳ |
| SP-03 | SCOPE | SCOPE.md §3 documents scope-creep gate: PR adding module MUST answer three questions (IaaS primitive? core light? consumer demand signal?). Referenced in code review discipline. | ⏳ |
| SP-04 | SCOPE | SCOPE.md §4 lists Adjacent items (AWS adapter stub, S3, load balancers, DNS, snapshot schedules, multi-user GUI) requiring consumer demand signal before promotion to IN. | ⏳ |
| SP-05 | SCOPE | SCOPE.md §5 cites ecosystem alternatives for each OUT-of-scope item (Ansible, Terraform/OpenTofu, provider's managed k8s, openstacksdk directly, future). | ⏳ |
| SP-06 | SCOPE | SCOPE.md §6 states scope revisited at every MAJOR boundary; confirms it re-justifies surface against §1/§2 and re-affirms provider-agnostic / stateless / core-light invariants. | ⏳ |
| FB-05 | FEEDBACK | FEEDBACK.md present at repo root + referenced (corroborated by the DOC-10/DOC-13 rows); repo-scoped, with federation-wide items routed to mgf-common/FEEDBACK.md per the documented convention (added in completeness pass) | ⏳ |


---

## AG-20 — owned-infrastructure discipline (standards v2.26)

✅ **Accounted 2026-06-29.** Review-enforced agent conduct (like AG-04 / AG-05 /
AG-15 — no single checkable artifact). Before declaring an action **blocked /
human-gated / impossible**, an agent consults
[`MGF_INFRA.md`](https://codeberg.org/magogi-admin/mgf-standard/src/branch/main/MGF_INFRA.md)
(the fleet infrastructure / access registry) and attempts the self-owned recovery
path — an auth/access failure on Magogi-owned infra (expired token, 401, stopped
service) is a solvable sub-problem, not a terminal wall. Recorded "blocked" /
"gated" notes carry an unblock-path + as-of date and are re-derived against current
capabilities. Added with the v2.26 corpus bump (AG-20 + the MGF_INFRA registry).

### §Z.seeded — pending assessment

Rows added because the corpus declared these MUSTs and this ledger had no
entry for them. **⏳ means not yet assessed — it is not a conformance
claim.** Replace each with a real verdict and evidence as it is reviewed.

| Rule | Status | Evidence | Notes |
|---|---|---|---|
| AG-21 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| AG-22 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-01 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-02 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-03 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-04 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-05 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-06 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-07 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-08 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-09 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-10 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-11 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| CRT-12 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SEAT-01 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SEAT-02 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SEAT-03 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SEAT-04 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SEAT-05 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SEAT-06 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SEAT-07 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SEAT-08 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-01 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-05 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-06 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-07 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-08 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-09 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-10 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-11 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-12 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| SHP-13 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
| TS-29 | ⏳ | — | seeded by `mgf-fed ledger-seed`; not yet assessed |
