How we work
Restraint, recorded.
Honesty, enforced.
256Bank is built by infrastructure engineers, not consumer-fintech marketers. The discipline below is how we keep humans and AI honest while building financial infrastructure intended to operate for fifty years.
Honesty discipline
Real, not mock.
Every implementation task in our roadmap is tagged REAL or MOCK. A mocked function that pretends to work is more dangerous than no function at all — it lets the team believe progress that has not been made. The platform refuses to ship work where this distinction is blurred.
Tagged in code.
Every stub carries a MOCK_OK marker with a reason and a trigger for replacement. The build pipeline blocks unmarked stubs.
Verified before "done".
The Stop hook fails the session if tests are red, if unmarked stubs exist, or if more than 20 files have uncommitted changes. There is no soft completion.
Brutal honesty in status.
"Implemented and verified" lists what works. "Mocked with marker" lists what fakes it. "Not yet implemented" lists what is missing. No "pretty much done."
Adversarial review.
Every completion claim is reviewed by a fresh-context agent that has not seen the build. If it cannot reproduce the claim, the task reopens.
Governance
ADR-first. Every time.
Every architecture decision lives in a written record before any code is written. No silent deviations. No "I will just decide and move on." The ADR catalogue is the contract between past, present, and future engineers.
Why ADRs matter in fintech
Banks do not move fast. A wrong call on settlement ordering, fee splits, or a cryptographic primitive can compound into months of unwinding. The ADR makes the trade-off visible at decision time and reviewable forever. When a reviewer asks why, we have an answer in writing.
What goes through an ADR
Anything touching cryptography, auth, billing, settlement timing, external integrations, or data residency. The mark grammar lives in ADR-001. The dual-channel brand system lives in ADR-002. The signature gesture lives in ADR-004.
The signature gesture
The mark is the button.
Every signed transaction in 256Bank is a press-and-hold on the mark. The mark is not a logo on a button — it is the button. Eight satellites fire in sequence, representing the parallel checks running underneath: biometric, device, signature, ledger, compliance, fraud, balance, network. Release early to cancel. Hold for the full duration to sign.
Try it
Press and hold the mark.
Standard transactions sign in 800 milliseconds. High-value transactions (over €1,000, or member-configured) require 1,500 milliseconds. Cancel by releasing early. On mobile: haptic feedback on start, on each satellite firing, and a distinct thump on success.
Hold the mark to sign
Keyboard: focus the mark and press Space.
Voice
Considered, not breathless.
We do not celebrate that money moved correctly. Settlement times are features, not fine print. No exclamation marks in transactional surfaces. No emoji on payment confirmations. The bank does not perform — the work speaks for itself.
Plain, not technical
"Cleared funds" is plain English that happens to be precise. "Settlement orchestration cycle" is precise but unreadable.
Considered, not breathless
"Payment signed." not "Payment successful!". The verb describes what happened. The full stop closes it.
Long-view, not promotional
"Settles same day · 14:00 cycle" respects the member. "Lightning-fast transfer!" does not.
Want the long version?
Read the project briefings.
The full design system, voice rules, ADRs, and current production plan live in the internal briefings on scicel. Request access for the full picture.
Request access