veldris-ltd / midgard-app

# Midgard
> **The sovereign enclosure.** A sovereign, open-source, post-quantum alternative to the Palantir platform family — one core platform and four composable products, fully specified and partly implemented. What runs today, and how far each capability goes, is in the claims ledger.
Midgard is a **Veldris Ltd** project. This repository holds three things that fit together:
1. **The specification** — the Solutions Architecture Documents (the "what and why").
2. **The design system** — a complete, branded UI system (the "how it looks and behaves").
3. **The implementation** — a post-quantum, air-gap-capable platform built from the spec: a 70-crate Rust workspace (core services, Mimir, Forge, Bifrost, Heimdall, admin, clients) plus the console UIs and gateway edge.
The implementation was produced, phase by phase, from BUILD_PLAYBOOK.md; in the full working history, one commit maps to each playbook prompt. This public repository begins from a squashed initial import of that verified state.
- **Just want to see it?** → Run the design system (static files, no toolchain).
- **Want to run it?** → Run the platform locally (gateway edge + console, step by step).
- **Want to verify it?** → Verify the platform (build, test, and the 72-criterion air-gapped gate).
- **Want to understand how it was built?** → GETTING_STARTED.md and BUILD_PLAYBOOK.md.
---
## Status
**Implementation: five services run and are tested; most other subsystems are tested libraries. Release: not yet cut.**
The status of each capability is in the claims ledger. A CI check holds every row to the source, tests and service tests it cites.
The gate was last recorded at commit `3c8b1614bb1d`, in a run started 2026-10-16T18:34:30Z (UTC) in the pinned toolchain image under `docker run --network none`. The record lists every criterion's result and every test invocation, and carries the complete logs. Commits after `3c8b1614bb1d` are not covered by it.
| | |
|---|---|
| Gate result | **PASS** |
| Acceptance criteria | **72 / 72 pass** |
| Tests run by the acceptance suite | 251 passed · 0 failed · 0 ignored |
| Tests run by `just test` | **878 passed · 0 failed · 0 ignored**, in 50 of 50 invocations (289 test binaries) |
| Crypto backends | backend-fips, test-backend, in separate invocations |
| Phase definitions of done | 8 / 8 met |
| Toolchain | `rustc 1.82.0 (f6e511eec 2024-10-15)` |
| Network during the run | none (`--network none`) |
| Exit | acceptance `0` (`>>> FULL SUITE PASSED`) · `just test` `0` |
What that does **not** yet mean:
- **No release has been tagged yet.** Version `0.1.0-rc.1` is prepared: the release workflow, the verify-before-run images and the signed air-gap bundle are in place (see the release candidate notes). Tagging it needs a key ceremony and a provisioned signing runner, which are the owner's to do, so `.github/workflows/release.yml` has not run yet.
- **Most subsystems are still libraries, not services.** Every crate is implemented and tested. Five are runn