← Home

Case studies

These cards describe deployment patterns that are safe to publish without customer names or contract figures. Logos, metrics, and counsel-approved artifacts stay in the member data room and DECK assets.

The public version shows problem shape, configuration, and evidence category only. Customer names, amounts, and regulated claims should be promoted into separate cards after approval.

Policy-routing pilot

Scope
Payment and settlement requests move from client apps into a policy router before permissions, limits, and approval state are checked.
Outcome
Pilot teams can review payment and settlement flow separately from business rules.
Evidence
Demo environment, policy-flow diagram, and routing-log samples link into approved evidence packs.

Modular dApp rollout

Scope
STEM, CELLs, and BLOOM split user surfaces and operating routes by product line.
Outcome
Operators can stage contact and security review per line before broadening scope.
Evidence
Line pages, contact routes, and DECK asset URLs are managed from the admin workflow.

Ledger and OPS observability

Scope
Transaction, settlement, and operating events connect back into the BWL data-room context.
Outcome
The public story stays separate from ledger evidence while still pointing to explainable operating views.
Evidence
OPS boards, IR panels, and member-agent tool results are used as the evidence layer.