Bank-facing prototypes for the console a bank uses to control, build, and safely publish the plugins that appear inside its Jack Henry Banno app.
The pitch, demoable and research-grounded: one registration, one flow, and the flow decides which plugin each member sees. Garden-accurate retail and business dashboards with Banno chrome seams, Expanded Views for every plugin type, and three write-back journeys — confirm-address, skip-a-payment, and new-member activation — each committing to the core through Mesh, two of them re-routing the slot afterward.
The earlier Open Design iteration this grew from: cards → one Temporal flow per card → one plugin rendered, with the agent chat, context simulator, and the DNS-verified new-card wizard. Kept for comparison; its ideas now live in the orchestrator.
The slot model with state-based targeting: ordered first-match rules over a required default, preview-as-member across four synthetic members, and the governed publish path — draft, diff, approval, schedule, verify, rollback.
Every screen here is a static mock with seeded data. Nothing calls Banno, and no member data is real — the four preview members are synthetic and exist to make rule order legible, not to estimate coverage.