Skip to main content

Fleet engineering practice

mgf-fedres

The federation-resources spine: the shared convention, schemas, manifest and sync engine that both consoles read state from.

What it is

The shared core beneath the federation dashboard and the testing console: a per-project directory convention for generated, authored and live resources, one versioned set of schemas, a manifest with content digests, and a sync engine. Its truth model is that a project is in sync only when regenerating its resources yields byte-identical output, and every other state — stale, tampered, unknown, unreadable — is named rather than left blank. A command-line tool exposes the same contract the web consoles consume, and a registry-adapter seam lets a second family plug in its own registry.

It belongs to Fleet engineering practice — the estate's most distinctive work is how it is operated. That cluster states its own boundaries on the work page, including what it deliberately does not own.

State

Status
Active development
Registered version
0.5.0
Category
infrastructure
Cluster
Fleet engineering practice
Release wave
1
Language recorded
python

Versions shown here are the versions the registry records for the working tree. The package index is the publication contract, and the two are not guaranteed to agree — the index is what an install command actually resolves against. recorded at build · 2026-09-04

A project page is one row of the federation registry, read at build: the registered version, the projects it depends on, and the projects that depend on it — all of them the registry's own values. recorded at build · 2026-09-16

how it connects

Relations

Declared dependencies, by scope

Declared dependents, by scope

Left: what mgf-fedres depends on. Right: what depends on it. Every relation the registry records for mgf-fedres is published here and named above. Relations are read from mgf-libraries.json, synced from mgf-standard at 87915ba on 2026-09-16.

A project's release wave is its position in the dependency order recorded upstream — a barrier that says what must be published first, never a date. recorded at build · 2026-09-16

under the hood

Engineering
Third-party packages declared
1
Optional extras
dev · standards
Requires Python
>=3.11

The registry records a direct third-party declaration count for each project. This site can sum those row counts, but it does not have the names needed to deduplicate them or describe a resolved installation. recorded at build · 2026-09-16

The rule families it is measured against

mgf-fedres answers to the same corpus every registered project does: 323 anchored rules in 25 families, of which 313 are binding. This is the corpus, not a score — nothing on this page claims a conformance result for mgf-fedres, because no durable per-project record of one is published. The corpus, family by family →

Counted from mgf-rules-index.json, synced from mgf-standard at 169b511 on 2026-09-04.

Every registered project is measured against the same corpus: the rule families, their sizes, and how many of their rules are binding come from the standard's own machine-readable index, not from prose about it. recorded at build · 2026-09-04

the record

Evidence

Read the declared runtime graph

Inside mgf-fedres's declared runtime graph

  • mgf-fedres itself.
  • no other Magogi library in its declared runtime graph. Optional and test declarations may still appear in the relations above.
  • a sum of direct third-party declaration counts — 1 on mgf-fedres's row and 1 across the declared runtime graph. The registry supplies no names, so this is not a unique package count or a resolved installation.

Outside this graph

  • the other 53 published components are not reached by these declared runtime relationships. The explorer counts the same graph. This graph is a registry model, not a package-resolver result.
  • anything from these clusters: Foundational libraries · VManager — the virtual-machine stack · Hardware resource broker · Telematics · Cloud & cost · Applications & ventures
  • a hosted service, an account, or a runtime the Foundation operates for you.

The design rules require a third-party dependency that performs input or output to sit behind an interface with both a production and a test implementation. The rule states the required design; the registry's dependency counts do not verify implementation conformance. recorded at build · 2026-09-04

A project's declared runtime graph, and what stays outside it, is computed only from registry edges scoped as runtime. Optional and test declarations remain outside that view; the graph is not a resolved installation. recorded at build · 2026-09-16