Skip to main content

Explore

Federation Explorer

Pick a component. Inspect its declared runtime graph, the optional relationships left outside it, and the limits of what the registry can establish.

One model, four lenses

Everything on this page is one set of facts, projected four ways. A lens selects and frames; it never holds a fact of its own.

The federation publishes 54 components across 7 clusters, out of 55 projects its registry records. Every count on this page — including those three — is walked from that registry at build.

Every project the federation registers appears in one generated registry, with its registered version — the count on this page is computed from that registry, not typed. recorded at build · 2026-09-16

A component's declared runtime graph — and what it leaves out — is walked only from registry edges scoped as runtime, by the same function at build and in the browser. It is not a package resolver result. recorded at build · 2026-09-14

Nothing on this page runs code: there is no execution sandbox on this site, and the boundary is stated where the question arises instead of being implied away.

The sooth family is not in this explorer: it is not installable from a package index and its evidence is published under its own rails. That story is on the sooth page.

The federation at a glance

Release waves, not a calendar: a component is built only once everything below it is live.

Every published component, placed in the release wave the federation registry records for it. Waves are dependency barriers, not calendar periods: nothing in a wave is built until the wave below it is live.

Positions and membership come from release_waves in the vendored registry snapshot, generated 2026-09-14. This picture adds nothing to the list below it — the list is the same data, in text.

  1. Wave 0 12 published ipcam-app · magogi-proof · mgf-brand · mgf-common · mgf-common-zig · mgf-cost-watch · mgf-hrb-model · mgf-media · mgf-standard · mgf-website · mgf-website-template · vm-vmanager-docs
  2. Wave 1 20 published mgf-apiprobe · mgf-auth · mgf-brand-qt · mgf-brand-web · mgf-coach · mgf-django · mgf-fedres · mgf-hrb · mgf-hrb-kabi · mgf-hrb-rt · mgf-http · mgf-livepush · mgf-logship · mgf-secrets · mgf-sqlalchemy · mgf-tele-core · mgf-test-supervisor · mgf-uitest-desktop · mgf-uitest-web · mgf-vm-core
  3. Wave 2 14 published inthewords · mgf-alembic · mgf-coach-qt · mgf-common-identity · mgf-fastapi · mgf-fed-web · mgf-hrb-cap · mgf-tele-teltonika · ProofWarden · mgf-vm-firecracker · mgf-vm-forensics · mgf-vm-interchange · mgf-vm-libvirt · vm-vmanager-agent
  4. Wave 3 2 published mgf-cloud · mgf-vm-sdk
  5. Wave 4 3 published mgf-cloud-provision · mgf-cloud-web · mgf-fed
  6. Wave 5 3 published TelePlasma · hrb-app · VManager

Release waves are dependency barriers, not calendar periods: the map places every component in the wave the registry records for it. recorded at build · 2026-09-14

A worked example, pre-rendered

Computed at build by the same function the panel below runs in your browser — so this page teaches the whole lesson with scripts switched off.

Reading the declared runtime graph for mgf-http. Every line below is arithmetic over the registry snapshot generated 2026-09-14 — the same arithmetic the panel further down runs for whichever component you pick. This graph is a record of declarations, not a package resolver result.

Developer — what you would be adding

A typed asynchronous HTTP client for the federation's Python services, with retries, timeouts, header redaction and tracing-aware logging.

Declared runtime graph

  • mgf-http 0.4.13 — the component you chose · 1 direct third-party declarations
  • mgf-common 0.52.0 — pulled in by mgf-http as >=0.41,<1.0 · 3 direct third-party declarations

2 federation components in total. Their recorded direct third-party declaration counts sum to 4 direct declarations. The registry does not name those declarations, so this is not a unique package count, install footprint, or resolved dependency result.

Declared outside the runtime graph

  • mgf-test-supervisor >=0.1.3,<0.2 · optional; excluded from this runtime view

Capability this sits under: Outbound HTTP that retries and redacts

Stays out

52 published components do not enter — nothing about depending on mgf-http pulls the rest of the federation in.

  • 11 Foundational libraries
  • 9 VManager — the virtual-machine stack
  • 8 Hardware resource broker
  • 2 Telematics
  • 4 Cloud & cost
  • 15 Fleet engineering practice
  • 3 Applications & ventures

Every one of them is named in the list further down this page — and, where a script is running, in the panel beside it.

Install

pip install --index-url https://devpi.magogi.org/magogi/prod/+simple/ "mgf-http==0.4.13"

generated · resolves against the index Generated, not typed: the distribution name and version come from the registry snapshot, and the --index-url is printed because the index's own published listing records this exact version — re-fetched at every sync, never asserted. These packages publish to the Foundation's index, never to public PyPI.

integration shape · none recorded No canonical snippet for mgf-http itself is recorded in this repository. Rather than invent example code, this page shows only what it can quote.

execution · unavailable Nothing on this page runs code. There is no execution sandbox on this site, so the composition above is arithmetic over recorded facts — the command and the integration shape are real text to take to your own machine.

Architect — the shape of the dependency

  • 1 direct declared runtime relationship; 1 after the declared runtime graph is walked transitively.
  • Depended on by 2 registered projects, of which 1 is published on this site (inthewords); the rest are registry entries this site does not publish.
  • Release wave 1 — the second of 6, numbered from zero as the registry does. A dependency barrier, not a date: nothing in a wave is built until the wave below it is live.
  • Cluster boundary: Foundational libraries — what it owns and what it deliberately does not is stated with the cluster below.
  • Replaceability: The federation's design requirement says an input/output dependency must sit behind an abstract seam with production and test implementations. The registry's third-party counts do not identify input/output dependencies or verify that an implementation follows this requirement.

Adoption — the decision, stated plainly

  • Status word: active development — a recorded editorial decision in this repository's curation layer, not a value the registry computes.
  • Registered version 0.4.13 — a working-tree value the registry records. The package index is the contract once published, so this page says "registered", never "released".
  • Conformance: the federation registry records no per-project conformance level, so this page shows none rather than implying one.
  • Maintenance model: releases go in dependency order, wave by wave — the registry records that order, not a date, and it is a dependency barrier rather than a schedule; regenerating the registry is part of every release, and a release gate checks that every federation pin accepts the current version of what it depends on.
  • The declared runtime graph for mgf-http contains 2 federation components. Direct third-party declaration counts across those rows sum to 4 direct declarations. Outside that graph, 52 other published components stay exactly where they are.

Organization — the capability, not the package

Read as a capability question, mgf-http sits under Outbound HTTP that retries and redacts. The full stack — what stays yours, what you probably already have, what the federation provides, what stays external, and the assumptions behind each row — is printed further down this page. There are no percentages in it: no adoption data exists to measure, so none is invented.

The install command is generated from the registry snapshot and the index's own published listing: it is printed complete, with the index URL, only for a component the index actually carries at that version. runnable

Where an integration snippet appears it was read verbatim out of a file in this repository at build; where none is recorded, the page shows the install command alone rather than example code nobody could check.

The federation's design rule requires an input/output dependency to sit behind an abstract seam with production and test implementations. This page states that requirement; registry counts do not prove that an implementation conforms.

Compose it yourself

Every published component, grouped by cluster. Open a cluster to read what it owns, what it deliberately does not, and every component in it; where a script is running, choosing one recomposes the panel, and where none is, this is a complete inventory.

Foundational libraries

13 published components

The floor everything else stands on.

Foundational libraries: the boundary

Owns

  • the shared error, configuration, logging and tracing surfaces
  • the rule corpus and the federation contract every repository conforms to
  • the adapter seams that keep third-party libraries replaceable

Does not

  • hold any domain logic — a library that would only ever serve one application does not belong here
  • reach for a hosted service; these are libraries, not infrastructure
  • promise a public package index: the packages resolve from the Foundation's own index

  • mgf-common Active development 0.52.0

    The cornerstone every other Magogi library stands on: typed exceptions, one central configuration object, structured logging with redaction, and tracing.

    0 runtime federation dependencies 2 optional/test declarations runtime-used by 27 3 direct third-party declarations wave 0 foundational library

  • mgf-standard Active development 0.1.84

    The engineering standard itself as an installable package: the rule corpus, the federation contract, and the generated library registry this site is built from.

    0 runtime federation dependencies runtime-used by 1 0 direct third-party declarations wave 0 foundational library

  • mgf-test-supervisor Active development 0.1.21

    A budget-aware, crash-survivable supervisor that drives pytest from the outside, so a hung or crashed test is recorded as an outcome instead of vanishing.

    0 runtime federation dependencies 1 optional/test declarations runtime-used by 1 0 direct third-party declarations wave 1 foundational library

  • mgf-alembic Active development 0.4.11

    An async-aware Alembic helper for database schema migrations: one call configures the migration environment that otherwise takes a page of boilerplate.

    2 runtime federation dependencies 1 optional/test declarations runtime-used by 1 1 direct third-party declarations wave 2 infrastructure

  • mgf-apiprobe Active development 0.5.11

    REST API verification: typed probes that describe a request and its expected response, pluggable checks that emit structured findings, and suites that report.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 0 4 direct third-party declarations wave 1 tooling

  • mgf-auth Active development 0.1.10

    Authentication verifier seams for federation services: a session verifier and a webhook verifier, a Clerk adapter, typed 401 errors and in-process test doubles.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 1 0 direct third-party declarations wave 1 infrastructure

  • mgf-coach Active development 0.1.0

    Coaches a human through a timed physical procedure the software cannot perform itself, such as holding a button for a set time, one cue at a time.

    0 runtime federation dependencies 3 optional/test declarations runtime-used by 1 0 direct third-party declarations wave 1 foundational library

  • mgf-coach-qt Active development 0.1.0

    The Qt presentation of a coaching run: a dialog rendering the cue stream through screen, sound and the accessibility bus for an operator whose hands are busy.

    2 runtime federation dependencies 3 optional/test declarations runtime-used by 0 1 direct third-party declarations wave 2 foundational library

  • mgf-django Active development 0.4.10

    Django adapters for federation services: one app entry and two middlewares bring request ids, request context and JSON logging to an unchanged Django project.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 0 1 direct third-party declarations wave 1 infrastructure

  • mgf-fastapi Active development 0.6.13

    FastAPI adapters for federation services: request ids, exception translation, lifespan wiring, webhook verification, IP allow-lists and a test-app helper.

    1 runtime federation dependency 3 optional/test declarations runtime-used by 2 1 direct third-party declarations wave 2 infrastructure

  • mgf-http Active development 0.4.13

    A typed asynchronous HTTP client for the federation's Python services, with retries, timeouts, header redaction and tracing-aware logging.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 2 1 direct third-party declarations wave 1 infrastructure

  • mgf-livepush Active development 0.1.9

    A realtime push pipeline for services: server-sent event streaming, a pluggable pub/sub broker seam with a Redis adapter, and per-key connection caps.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 1 0 direct third-party declarations wave 1 infrastructure

  • mgf-sqlalchemy Active development 0.5.10

    Typed async SQLAlchemy plumbing for services: engine and pool defaults, session factories, Postgres row-level tenant scoping and cursor pagination.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 2 1 direct third-party declarations wave 1 infrastructure

VManager — the virtual-machine stack

9 published components

A working application, and the libraries that were carved out of it.

VManager — the virtual-machine stack: the boundary

Owns

  • the virtual-machine domain model, its state machine and its contracts
  • the hypervisor and storage adapters that implement those contracts
  • the client library both the command line and the desktop interface import

Does not

  • run a hosted control plane — this is software you would run yourself
  • tie the domain model to one hypervisor; the second adapter exists to prove that
  • claim a public download today

  • VManager Active development 0.4.0

    VManager — end-to-end KVM/QEMU virtual-machine management for Linux: a typed core with a command-line tool and a desktop GUI over the same library.

    6 runtime federation dependencies 5 optional/test declarations runtime-used by 0 15 direct third-party declarations wave 5 application

  • mgf-vm-core Active development 0.1.14

    The pure VM-domain core behind VManager: a state machine, an engine-neutral VM specification, the backend contracts, provided fakes and a conformance suite.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 7 2 direct third-party declarations wave 1 infrastructure

  • mgf-vm-firecracker Active development 0.1.5

    The Firecracker microVM adapter for VManager: a second hypervisor backend, planned to prove the engine-neutral contracts against a different engine.

    2 runtime federation dependencies 1 optional/test declarations runtime-used by 0 1 direct third-party declarations wave 2 infrastructure

  • mgf-vm-forensics Active development 0.1.9

    VM forensics for VManager: packet-capture analyzers, case management and top-talker, DNS and TLS server-name extraction, kept apart from the VM engine core.

    2 runtime federation dependencies 1 optional/test declarations runtime-used by 1 1 direct third-party declarations wave 2 infrastructure

  • mgf-vm-interchange Active development 0.2.5

    OVA and OVF interchange for VManager: it parses a portable appliance into the engine-neutral VM specification and exports one back to a portable archive.

    2 runtime federation dependencies 1 optional/test declarations runtime-used by 1 1 direct third-party declarations wave 2 infrastructure

  • mgf-vm-libvirt Active development 0.1.13

    The libvirt adapter for VManager: it implements the core hypervisor and storage contracts against libvirt, KVM and QEMU — wrapping libvirt, not marrying it.

    2 runtime federation dependencies 1 optional/test declarations runtime-used by 1 2 direct third-party declarations wave 2 infrastructure

  • mgf-vm-sdk Active development 0.1.10

    The VManager client SDK: one client interface over an in-process transport for a single host, with a gRPC transport for a fleet to follow.

    2 runtime federation dependencies 2 optional/test declarations runtime-used by 1 0 direct third-party declarations wave 3 infrastructure

  • vm-vmanager-agent Active development 0.1.1

    The VManager per-host agent: the component on each hypervisor host that brokers hardware to the control plane, starting with the device-passthrough seam.

    3 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 2 application

  • vm-vmanager-docs Active 0.1.0

    The single source of truth for the VManager system: its architecture, component contracts, decision register and roadmap, end to end.

    0 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 0 infrastructure

Hardware resource broker

8 published components

Who is allowed to touch which piece of hardware, and on what terms.

Hardware resource broker: the boundary

Owns

  • the resource vocabulary and the claim/lease model
  • the abstract kernel seam and its conformance suite — a new backend is correct exactly when that suite is green
  • capability rights whose attenuation can only shrink authority

Does not

  • replace the operating system's drivers
  • require the from-scratch capability kernel it is designed to be liftable onto — that remains an ambition, not a shipped thing
  • expose raw register access as an ordinary right

  • hrb-app Active development 0.2.1

    The desktop instrument for the hardware resource broker: device tree, leases, doctor checks, and an embedded command line in one PySide6 window.

    4 runtime federation dependencies 4 optional/test declarations runtime-used by 0 2 direct third-party declarations wave 5 application

  • mgf-hrb Active development 0.1.14

    The hardware resource broker: userspace arbitration of PCIe, USB, GPU and CPU resources — a Zig broker and a Python SDK talking over a Unix socket with no FFI.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 2 0 direct third-party declarations wave 1 application

  • mgf-common-identity Active development 0.1.0

    The identity-continuity comparator: after a device re-enumerates and every handle to it changes, it estimates whether this is still the same physical device.

    2 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 2 infrastructure

  • mgf-common-zig Active development 0.0.0

    The shared Zig commons, and the home of the federation's Zig coding standard.

    0 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 0 foundational library

  • mgf-hrb-cap Active development 0.1.0

    The capability engine: unforgeable rights whose attenuation can only ever shrink authority, with direct register access treated as its own distinct right.

    2 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 2 infrastructure

  • mgf-hrb-kabi Active development 0.1.0

    The abstract kernel seam: nine operations with no Linux-specific nouns, plus a fake backend and a conformance suite that decides when a new backend is correct.

    1 runtime federation dependency runtime-used by 2 0 direct third-party declarations wave 1 infrastructure

  • mgf-hrb-model Active development 0.1.0

    The broker's vocabulary as a leaf module on the Zig standard library alone: resource families, the resource-name type and matcher, claim modes and errors.

    0 runtime federation dependencies runtime-used by 4 0 direct third-party declarations wave 0 infrastructure

  • mgf-hrb-rt Active development 0.1.0

    The runtime primitives behind the broker's reliability guarantees: a lock-free single-producer ring, file-descriptor passing and connection-liveness heartbeats.

    1 runtime federation dependency runtime-used by 0 0 direct third-party declarations wave 1 infrastructure

Telematics

2 published components

A vendor-neutral seam, and the first vendor behind it.

Telematics: the boundary

Owns

  • the provider interface, the frame types and the failure vocabulary
  • a mock implementation so consumers can be tested without hardware
  • one concrete decoder implementation

Does not

  • assume one vendor's protocol is the architecture
  • include the fleet-operations application itself — that is a separate venture that consumes this seam

  • mgf-tele-core Active development 0.1.9

    The vendor-neutral telematics seam: a device-session contract, codec-agnostic record types, typed errors and a scripted mock that vendor packages build on.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 2 0 direct third-party declarations wave 1 infrastructure

  • mgf-tele-teltonika Active development 0.1.9

    The first vendor package on the telematics seam: a decoder for Teltonika Codec 8 and 8 Extended and a device-session provider for its FMB, FMC and FMM trackers.

    2 runtime federation dependencies 1 optional/test declarations runtime-used by 1 0 direct third-party declarations wave 2 infrastructure

Cloud & cost

4 published components

How the Foundation runs its own machines — and watches the bill.

Cloud & cost: the boundary

Owns

  • the Foundation's own virtual machines, storage and provisioning
  • a cost estimate that runs on a schedule and fails loudly

Does not

  • offer hosting to anyone — the local console binds to the loopback interface and its own documentation disclaims being a service
  • belong on a product list; it is shown inside the engineering story

  • mgf-cloud Active development 0.1.5

    The federation's cloud-resource interface: virtual machines, storage and networking on Infomaniak Public Cloud, driven from a CLI or a local web console.

    1 runtime federation dependency 3 optional/test declarations runtime-used by 2 3 direct third-party declarations wave 3 infrastructure

  • mgf-cloud-provision Active development 0.1.3

    Declarative, idempotent provisioning of the federation's self-hosted services, such as the package index and the CI host: plan, apply and destroy over a spec.

    2 runtime federation dependencies 2 optional/test declarations runtime-used by 0 1 direct third-party declarations wave 4 infrastructure

  • mgf-cloud-web Active development 0.1.0

    The cloud console: a local, single-user web front-end for viewing and managing cloud resources through the cloud-resource interface — not a hosted service.

    4 runtime federation dependencies 2 optional/test declarations runtime-used by 0 4 direct third-party declarations wave 4 application

  • mgf-cost-watch Active development 0.1.0

    A daily cloud-cost estimate with teeth: a scheduled job prices live cloud resources at published rates and fails when the monthly run-rate breaches a threshold.

    0 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 0 tooling

Fleet engineering practice

15 published components

The estate's most distinctive work is how it is operated.

Fleet engineering practice: the boundary

Owns

  • release order, gates, drift checks and fleet status
  • the record that a suite really ran, and what hung or crashed
  • the declaration of every credential — with no values in the registry
  • runnable proofs that produce identical digests on different processor architectures

Does not

  • constitute a product — none of this is offered to anyone
  • publish continuous-integration results: those live on a private server and no durable artifact is exported yet
  • publish coverage percentages; the thresholds are committed policy, the measured numbers are not durable

  • magogi-proof Active development 0.1.0

    The estate's runnable proof repository: an all-integer numerical core that digests identically across processor architectures, with its accuracy gaps on record.

    0 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 0 tooling

  • mgf-fed Active development 0.25.12

    The federation orchestrator: it runs the recurring cross-repo work — gates, releases in dependency-wave order, status and drift checks — across the whole fleet.

    0 runtime federation dependencies 5 optional/test declarations runtime-used by 0 0 direct third-party declarations wave 4 tooling

  • mgf-fed-web Active development 0.2.4

    The federation dashboard: a read-mostly console over the fleet's recorded state. It reads state; it never authors it.

    2 runtime federation dependencies 3 optional/test declarations runtime-used by 0 3 direct third-party declarations wave 2 application

  • mgf-fedres Active development 0.5.0

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

    0 runtime federation dependencies 3 optional/test declarations runtime-used by 2 1 direct third-party declarations wave 1 infrastructure

  • mgf-logship Active development 0.1.9

    Centralised log forwarding: a fail-open handler that sends canonical log records to a collector, so a logging outage never takes an application down with it.

    1 runtime federation dependency 1 optional/test declarations runtime-used by 1 0 direct third-party declarations wave 1 infrastructure

  • mgf-secrets Active development 0.7.0

    The credential plane: a registry that declares every credential and stores no values, plus a read-only doctor proving declared, deployed and consumed agree.

    0 runtime federation dependencies 3 optional/test declarations runtime-used by 0 1 direct third-party declarations wave 1 tooling

  • mgf-uitest-desktop Active development 0.1.2

    Observable-behaviour UI testing for the desktop applications — the tier that exists because a broken button once shipped past a green suite.

    0 runtime federation dependencies 3 optional/test declarations runtime-used by 0 3 direct third-party declarations wave 1 tooling

  • mgf-uitest-web Active development 0.1.2

    Browser-level UI testing for the internal consoles, driving a real browser with an accessibility pass in the loop.

    0 runtime federation dependencies 3 optional/test declarations runtime-used by 0 3 direct third-party declarations wave 1 tooling

  • ProofWarden Active development 0.1.9

    ProofWarden — the testing and CI authority console, where a per-project warden is the sole test executor and a test cannot run twice at once by construction.

    2 runtime federation dependencies 3 optional/test declarations runtime-used by 0 0 direct third-party declarations wave 2 application

  • mgf-brand Active 0.1.0

    The Foundation's knowledge base and brand: the canonical facts about Magogi, the business and legal procedures, and the brand identity from logo to palette.

    0 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 0 infrastructure

  • mgf-brand-qt Active development 0.1.3

    The brand kit for Qt desktops: locked tokens, a generated stylesheet, self-hosted fonts, the icon set, marks, patterns and brand widgets in one package.

    0 runtime federation dependencies 3 optional/test declarations runtime-used by 2 1 direct third-party declarations wave 1 infrastructure

  • mgf-brand-web Active development 0.5.3

    The brand-web kit as an installable package: tokenised CSS, components, self-hosted fonts, logo marks and patterns, so every web surface shares one source.

    0 runtime federation dependencies 3 optional/test declarations runtime-used by 2 0 direct third-party declarations wave 1 infrastructure

  • mgf-media Active 0.1.0

    The Foundation's media library: provenance-bearing records of films, scores, renders and posters; git holds the record, object storage will hold the payload.

    0 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 0 infrastructure

  • mgf-website Active development 0.1.0

    This site. It is in the registry like everything else, and it is built from the registry.

    0 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 0 application

  • mgf-website-template Active development 0.2.0

    A cookiecutter template for Magogi marketing and showcase websites: a static site with the brand system on by default and a contact-form handler.

    0 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 0 infrastructure

Applications & ventures

3 published components

Products in preparation, stated as such.

Applications & ventures: the boundary

Owns

  • the domain and the customer-facing shape of each venture
  • the honest state of each: in preparation, in design, or deliberately not presented

Does not

  • claim availability, deployment or customers for anything here
  • carry the reusable logic — by contract that lives in a library first
  • include every application the estate has built: one is held back pending a positioning decision

  • inthewords Active development 0.0.0

    A platform for real-time conversation and structured debate — claims, citations and resolution states rather than a comment thread.

    2 runtime federation dependencies runtime-used by 0 1 direct third-party declarations wave 2 application

  • ipcam-app Planned 0.1.0

    A design study for an IP-camera streaming and recording platform: the design suite and contract skeletons exist; the implementation does not.

    0 runtime federation dependencies runtime-used by 0 0 direct third-party declarations wave 0 research

  • TelePlasma Active development 0.1.0

    A multi-tenant fleet-operations platform built on the vendor-neutral telematics seam.

    8 runtime federation dependencies 4 optional/test declarations runtime-used by 0 13 direct third-party declarations wave 5 application

The capability stack

The same model read as an organization would read it: what stays yours, what you probably already have, what the federation actually provides, and what remains outside — assumptions printed, no percentages invented.

The organization view is qualitative by decision: what stays yours, what you may already have, what the federation provides, what remains external — with the assumptions printed, and no percentages, because no adoption data exists to measure.

Typed failures and one configuration object

You own
What counts as a failure in your domain, and which settings your product actually has.
You may already have
Most teams already have an exception base class and a settings module — usually one per service, written twice.
Magogi provides
mgf-common
Still external
Nothing: this is ordinary application code either way. The question is whether it is written once or once per service.

Assumptions behind this row

  • Adoption means depending on a library, not running a service.
  • The gain is consistency across projects, which only pays off above a handful of services.

Structured logging, redaction and traces

You own
Your retention policy, and what is sensitive in your domain.
You may already have
A logging library and, often, a collector.
Magogi provides
mgf-common mgf-logship
Still external
The log store and its query interface stay outside — the shipping side fails open so an outage there never takes an application down.

Assumptions behind this row

  • Redaction is only as good as the field list it is given.
  • No claim is made about a hosted logging product.

Outbound HTTP that retries and redacts

You own
Which upstreams you call and what a safe retry means for each.
You may already have
An HTTP client is already in every stack; retry policy usually is not.
Magogi provides
mgf-http
Still external
The upstream services themselves.

Assumptions behind this row

  • The wrapper sits over a widely-used client rather than replacing it.
  • Retry policy is a decision, not a default anyone should inherit blindly.

Web service scaffolding — request identity, error translation, auth seams, live push

You own
Your endpoints, your domain, and your identity provider.
You may already have
A web framework, and some middleware that grew organically.
Magogi provides
mgf-fastapi mgf-django mgf-auth mgf-livepush
Still external
The identity provider itself sits behind a verifier seam rather than being absorbed.

Assumptions behind this row

  • Two frameworks are supported today; a third would be new work.
  • The auth surface is a verifier seam with a mock, not an identity product.

Async database access with tenant scoping and migrations

You own
Your schema, your data, and your tenancy model.
You may already have
An object-relational mapper and a migration tool.
Magogi provides
mgf-sqlalchemy mgf-alembic
Still external
The database server.

Assumptions behind this row

  • Row-level tenant scoping assumes a database that supports it.
  • These are helpers over established tools, not a new persistence layer.

A test run that survives crashes, and interfaces tested as behaviour

You own
Your tests. No tool writes them for you.
You may already have
A test runner and a continuous-integration job.
Magogi provides
mgf-test-supervisor mgf-uitest-desktop mgf-uitest-web ProofWarden mgf-apiprobe
Still external
Your continuous-integration provider.

Assumptions behind this row

  • The supervisor records outcomes; it does not raise coverage.
  • No coverage percentage is published anywhere on this site — the thresholds are committed policy, the measured numbers are not durably recorded.

Releasing many repositories in dependency order

You own
Your release decisions, and your appetite for a shared standard.
You may already have
A release script per repository, and a wiki page describing the order.
Magogi provides
mgf-fed mgf-fedres mgf-standard
Still external
Your forge, your continuous-integration server, and your package index.

Assumptions behind this row

  • The value appears at fleet scale; for one repository it is overhead.
  • Waves are dependency barriers, not calendar dates.

Knowing which credentials exist, without holding their values

You own
The secrets themselves and where they live.
You may already have
A password manager, and some environment variables nobody has audited.
Magogi provides
mgf-secrets
Still external
Your vault or secret store — the registry declares, it does not store.

Assumptions behind this row

  • A registry with zero values can be committed; that is the whole design.
  • It proves declared, deployed and consumed agree — it does not rotate anything for you.

Managing virtual machines from a typed domain model

You own
Your hosts, your images and your capacity decisions.
You may already have
A hypervisor and a pile of shell scripts around it.
Magogi provides
mgf-vm-core mgf-vm-libvirt mgf-vm-firecracker mgf-vm-sdk mgf-vm-forensics mgf-vm-interchange
Still external
The hypervisor itself — it sits behind a backend contract with a second adapter proving the seam.

Assumptions behind this row

  • The domain library is hypervisor-agnostic by construction; the adapters are where the coupling lives.
  • No hosted control plane exists or is planned as part of this.

Arbitrating hardware between processes with revocable rights

You own
Your hardware and your policy for who may claim what.
You may already have
Operating-system permissions, and the convention that everyone is careful.
Magogi provides
mgf-hrb mgf-hrb-model mgf-hrb-kabi mgf-hrb-cap mgf-hrb-rt
Still external
The kernel and its drivers — the seam is abstract precisely so the backend can change.

Assumptions behind this row

  • This is pre-1.0 work with a live desktop instrument, not a supported product.
  • The from-scratch capability kernel it is designed to be liftable onto does not exist today.

What this page is standing on

One snapshot, recorded and re-hashed at every build.

One library is depended on by most of the others; the dependency count is computed from the registry's own reverse-dependency lists. recorded at build · 2026-09-14

The registry's reverse-dependency lists name the cornerstone 39 times across all declared scopes. The runtime compositions above apply the scope labels before walking.

The Explorer sums each runtime-graph row's direct third-party declaration count. The registry does not record names, so the sum is neither a unique package count nor a resolved installation footprint. recorded at build · 2026-09-14

Source
mgf-standard
Generated
2026-09-14
Vendored
2026-09-16
sha256
91a8353c48beca10955c7d60464730d1b590c80eec31b4311f9f784fd1ca8fc7

The snapshot is re-hashed at every build and compared with the recorded digest, so a fact on this page cannot drift from the registry without failing the build.