Artifacts
Everything we have built, in one place.
16 working artifacts behind Canteen: the design direction and the system drawn from it, the bank integration and what its rails can carry, the flow a member walks, the log of what it took, how the whole thing is tested, and the marks it goes to market under. Each one opens on claude.ai.
Design
What Canteen looks like, the tokens that keep it from drifting, and the words that go with it.
Design Direction
The visual direction: obsidian and brass, challenge-coin onboarding, live micro-interactions.
Design System
The living system: color tokens, type, the coin, components, motion.
Message Catalog
All fifteen messages, set as push banners, SMS bubbles, and email, in the copy that ships.
Security Emails
The two codes the app sends and the two notices that follow a sign-in, rebuilt on the waitlist email's shell. Before and after.
The Flow
What a member walks through, from download to a funded account. Three ways to see the same path: the walkthrough is cut to the thirteen steps the app ships, the prototype and the reel are older.
Issued in One Sitting
Fifteen screens end to end in the design that ships, and what the same path produced against the real bank partner.
Onboarding Prototype
Interactive, value-first tap-through: the flow with the virtual card at the end.
Onboarding Reel
The same flow, self-playing and captioned. Hand it to someone who will not tap.
The Bank
What our banking partner will actually move for us, and what that puts within reach.
What the Rails Can Carry
Every way money can move under our Managed program, and the product each rail puts within reach.
Market Model
Population stocks times revenue per member, and a conservative three-year conversion case. Live: move an assumption and the model re-runs.
Engineering
How the account actually gets opened, what has been built so far, and how to walk a room through it.
Bank Integration
Canteen to the bank partner: topology, data mapping, and the sequence diagrams for each call.
The Build Log
Day by day: real accounts at the bank partner, email and passkey auth, and what broke on the way.
Build Review & Demo Script
The presentation narrative: architecture, integrations, and the order to show them in.
canteen-api Cutover
The rename, the three API hostnames, and the four repos repointed at them. What broke first, and what it turned up on the way.
Testing
How we know it works, one strategy per codebase. Both start from the failures these repos have actually had rather than from a generic pyramid.
Trademarking
The marks as drawn, taken from the ones the product already uses rather than made for the application. Nothing is filed yet.