← MRM/Projects/Bastion
Consolidation Platform Complete · Phases 1–5 Rust · air-gapped · no AI

Bastion

Four systems, consolidated onto one cryptographic kernel — each proven byte-for-byte against the original.

Most teams end up with a pile of disconnected tools. Bastion is the opposite move: it takes four separate systems — a risk-graph engine, a compliance-evidence platform, an infrastructure scanner, and five federal products — and reparents them onto one shared, deterministic, cryptographically-verifiable kernel. Every vertical is proven byte-for-byte against its frozen original before the next is added, and a cross-vertical remediation pipeline turns all their findings into one prioritized action plan. Air-gapped by default. No AI, no phone-home.

bastion — cross-vertical remediation
$ bastion remediate ✔ ingesting findings · 22 risk lenses · compliance controls · infra SPOFs ✔ 1,204 findings → de-duped across verticals → 38 actions ✔ ranked by severity × blast radius ✔ every number tagged: measured vs attested · plan sealed

Representative output — not a live instance.

One kernel, four verticals
●One shared cryptographic kernel — content-addressed IDs (BLAKE3), an entity graph with five analysis primitives (blast-radius, single-point-of-failure, path enumeration, orphan detection, scoring), a hash-chained ed25519 evidence vault, and exact-cents money — all iterative and panic-free, verified on 100k-node graphs.
●Risk-graph vertical — the full 22-lens catalogue (vendor risk, permission explosion, outage cost, dead code, digital-twin what-if…), 22 of 22 lenses parity-proven against the original.
●Compliance vertical — controls-as-code with explainable verdicts, five frameworks scored from one shared control pack, and a forensic evidence vault (blake3 objects, ed25519 hash-chain, byte-level tamper localization, signed Merkle completeness).
●Infra-discovery vertical — a COBOL / JCL / SQL / PL-I / generic source scanner with estate merge, blast-radius and single-point-of-failure analysis, and deterministic DOT / JSON export.
●Five federal products — accessibility, approvals, CMMS, data-integration and procure-to-pay, reparented onto the kernel they originally seeded — all 207 of their original tests run green, unchanged.
Consolidated, proven, runnable
●Cross-vertical remediation — one unified finding model de-dupes issues across every vertical (one problem → one action), ranks them by severity × blast radius, and emits a single prioritized action plan.
●Provenance on every number — each fact is measured (observed) or attested (asserted); a score or dollar states which operator inputs drive it, and flags anything resting on unverified assertions.
●Byte-for-byte parity — each vertical is proven identical to its frozen original before the next lands. The harness was rigorous enough to catch latent nondeterminism in the originals — Bastion's reparented versions are deterministic and reproduce the normalized bytes exactly.
●Runnable & air-gapped — one offline CLI (bastion remediate / audit / arch scan / …) plus an optional read-only localhost dashboard behind an opt-in feature (std-only, no network by default — the default binary literally can't open a socket).
Proof
0
tests green on a default build · clippy clean
22/22
risk lenses parity-proven
0
systems consolidated
0
crates, one kernel
byte-exact
parity vs. frozen originals
~10k
nodes — measured comfortable estate size
Rust · 13-crate workspaceBLAKE3ed25519-dalekclapserdestd-only networking (opt-in)no async runtime · no AI
ℹ
What it consolidates, and what it doesn't: Bastion unifies four of my own systems (risk graphs, compliance, infra-discovery, and five federal products) into one platform. The live/network capabilities — active TCP probing, agent command execution, live collectors — deliberately stay in the frozen originals; Bastion is air-gapped by default. It's complete, runnable code with 770 passing tests — not a shipped or sold product.
🔒
Architecture and verified results shown. Source and binaries are private — this is a capability showcase, not a distribution.

Consolidating a
pile of tools?

I unify sprawling systems into one verifiable platform — with byte-for-byte proof that nothing changed behavior along the way. Tell me what you're trying to bring together.

Start a project →