In May you showed us Mesh and we asked to be first in the sandbox. Rather than wait, we built our answer on synthetic rails so you can click it today: gantry.blackflag.design (flip the rails switcher to Trabian Mesh). This page is the build plan behind it.
Aaron said it best on our April call: a firm that does what we do doesn't want to do what Trabian does, and Trabian can't do what we do. Trabian owns the trust layer: connectivity, constraints, compliance, durable workflows. Black Flag is the zero-to-one application layer on top: the agents and member-facing surfaces your clients and their fintechs keep asking for, shipped at AI speed, governed by Mesh. Call it an MCP server, a plugin, or an agent; the form doesn't matter, a working build does.
Keith shipped both at Z Suite across dozens of bank cores. They run on one backbone (below). The screens are easy; the hard part is the connective tissue: clean data out of the bureau and decisioning layer and into each core in the exact shape it expects, across cores mid-migration or running two systems at once. That seam is exactly what Mesh already owns.
We're fluent in the landscape: Jack Henry (Symitar, SilverLake), Fiserv, Q2, and the file-based vs. real-time integration patterns underneath them (Symitar's member-centric vs. account-centric model is the classic normalization case). Our job is to plug into the adapters and durable workflow layer Mesh already has, not re-solve them; every agent step becomes a replayable, auditable Temporal activity, which is exactly how AI belongs inside a bank.
Give us one build as a beachhead. Two candidates: the CD maturity retention agent from the demo (a workflow every community FI wants, and a clean showcase of Mesh governing an agent end to end), or one stuck feature for a named Trabian client, built by us on Mesh while Trabian stays the trusted vendor of record. Because we build against Mesh instead of raw cores, the first one ships in weeks. The pilot that proves it is a $50,000 fixed scope on a 30-day clock against the sandbox. And it compounds: each build seeds a library Trabian can package for every client on Mesh.
We built the model overnight so you can click it instead of imagining it: gantry.blackflag.design. A working agent console with a library of sixteen bank-ops agents and one fully playable run: CD maturity retention end to end (query, segmentation, drafting, an officer approval gate that actually pauses the run, CRM writes, a hash-chained audit export, and a kill switch). Flip the rails switcher to Trabian Mesh and the whole console speaks durable activities, because that is how we would actually build it. Synthetic data, simulated rails, real interaction. Point it at the real sandbox and this stops being a demo.
Three small unblocks and this starts: (1) the mutual NDA Aaron offered in May: send it over and we sign same day; (2) Mesh sandbox access: we build against it the same week it lands; (3) pick the first client or workflow. We'll be at fintech_devcon in Denver Aug 3 to 5 (front row for Aaron's Temporal workshop on the 4th) if the working session should happen in person.