WORKING DEMONSTRATION
Observable now
Interactive fictional workflows, a known-pair manual comparison and explicit human decisions.
Technology & trust
BCX™ is designed to organize conversion work without pretending a demonstration is a bank production system. This page separates what works today, what a pilot must control and what remains an option.
WORKING DEMONSTRATION
Interactive fictional workflows, a known-pair manual comparison and explicit human decisions.
PROPOSED PILOT CONTROL
Institution-approved identity, scope, data access, retention, monitoring and review.
FUTURE OPTION
Broader connections and automation after the narrow pilot proves value and control.
BOUNDED No live bank connection
TRACEABLE Page-cited source support
ACCOUNTABLE People retain decision authority
Working demonstration
Two supplied manuals are matched to a registered file pair, compared and converted into page-cited system gaps. Unknown files are rejected; the presentation masks vendor names.
Fictional customer records connect changed behavior to guidance, confirmations, requests and a durable human-support path.
Findings can be reviewed, accepted or returned with a named owner and decision history. The system does not treat a generated recommendation as approval.
The demonstration uses fictional data and no live bank systems. It does not move money, change entitlements or exercise transaction authority.
Proposed pilot control
A pilot should connect one approved experience to the minimum information needed to guide one conversion cohort. It should prove the operating contract before adding channels, institutions or autonomous behavior.
The bank authenticates the person and passes a short-lived, signed assertion containing only approved identity, role and customer scope.
BCX™ receives the minimum approved customer, product, task and readiness context required for guidance. The institution remains the system of record.
A confirmation, question or assistance request is recorded as a scoped event with actor, time, source and status. It is not a bank transaction.
Consequential exceptions move to an authorized person. Their decision, reason and next action become part of the record.
Data and model boundaries
IN SCOPE FOR A PILOT
OUT OF SCOPE
REQUIRED REVIEW
Architecture direction: a controlled service such as AWS Bedrock, or another institution-approved model environment, is a pilot design choice—not a capability deployed in this demonstration. Model choice follows the task: use the lowest-cost approved model that reliably meets the requirement.
Accountable assistance
BCX™ assistants can collect, compare, summarize, draft and recommend. A person with a defined role approves consequential work, and the record keeps the source support, reviewer and decision together.
A credible first pilot
Start with a small approved cohort and one identity contract, one read-only snapshot and one action-event path. Measure usefulness, customer completion, staff effort, error rates and control performance before expanding.
01GOThe workflow creates measured value and controls perform as designed.
02MODIFYThe use case is valuable, but the workflow, data or control boundary needs revision.
03STOPThe value, safety or operating burden does not justify expansion.
Technical leadership
Kevin Badinger designed and built the working BCX™ prototype and its proposed technical architecture, including the guided customer experience, source-supported gap analysis, accountable-assistant model and bounded backend workflow.
Meet the builder →The right technical conversation
A working session can examine the use case, identity path, minimum data contract, human authority and proof required for a focused pilot.