Foundational libraries
mgf-common
The cornerstone every other Magogi library stands on: typed exceptions, one central configuration object, structured logging with redaction, and tracing.
What it is
The cornerstone library of the Magogi federation: typed exceptions, one central, layered configuration object, structured logging, tracing, crash reporting and process management in one typed Python package. Framework adapters for FastAPI, Django, SQLAlchemy and HTTP are separate sibling packages that depend on it, so the core itself stays framework-free. The engineering standards it implements live in mgf-standard, which it depends on and surfaces through the federation tooling.
It belongs to Foundational libraries — the floor everything else stands on. That cluster states its own boundaries on the work page, including what it deliberately does not own.
Try the public package
Build one structured log record and check its redaction.
The lesson uses the published mgf-common 0.52.0 API, installs
anonymously from the Foundation's package index, and asserts a stable result.
Their source repositories are not anonymously accessible (anonymous access measured 2026-09-13); the wheel is the public artifact tested here.
- Checked
- 2026-09-13
- Evidence
- locally executed example
- Wheel SHA-256
0c5a7a405f2728e10dd5771703d50ce01d046e2bf38b5fa95631468db41f778b- Limit
- One passing example does not establish recognition of every secret shape, correct application handlers, secure log transport, production suitability, or public source access.
State
- Status
- Active development
- Registered version
- 0.52.0
- Category
- foundational library
- Cluster
- Foundational libraries
- Release wave
- 0
- 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 connectsRelations
Declared dependencies, by scope
- mgf-standard optional
- mgf-test-supervisor optional
Declared dependents, by scope
- hrb-app runtime
- inthewords runtime
- mgf-alembic runtime
- mgf-apiprobe runtime
- mgf-auth runtime
- mgf-brand-qt optional
- mgf-brand-web optional
- mgf-cloud runtime
- mgf-cloud-provision runtime
- mgf-cloud-web runtime
- mgf-coach optional
- mgf-coach-qt optional
- mgf-django runtime
- mgf-fastapi runtime
- mgf-fed optional
- mgf-fed-web optional
- mgf-fedres optional
- mgf-hrb runtime
- mgf-http runtime
- mgf-livepush runtime
- mgf-logship runtime
- mgf-secrets optional
- mgf-sqlalchemy runtime
- mgf-tele-core runtime
- mgf-tele-teltonika runtime
- mgf-test-supervisor optional
- mgf-uitest-desktop optional
- mgf-uitest-web optional
- mgf-vm-core runtime
- mgf-vm-firecracker runtime
- mgf-vm-forensics runtime
- mgf-vm-interchange runtime
- mgf-vm-libvirt runtime
- mgf-vm-sdk runtime
- ProofWarden optional
- TelePlasma runtime
- vm-vmanager-agent runtime
- VManager runtime
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 hoodEngineering
- Third-party packages declared
- 3
- Optional extras
- dev · observability · standards · vault
- 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-common 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-common, 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 recordEvidence
Read the declared runtime graph
Inside mgf-common's declared runtime graph
- mgf-common 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 — 3 on mgf-common's row and 3 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: VManager — the virtual-machine stack · Hardware resource broker · Telematics · Cloud & cost · Fleet engineering practice · 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