CabDesign is written and checked by a crew of AI specialists working under one cabinetmaker.
To be plain about it before you read any further: everyone below is software, not staff. They carry names
and characters because it is easier to talk about who checked what, and the one human on this page is
Ahmed, who runs the shop, ranks the work and settles anything that comes down to how a real shop does it.
Each specialist owns a single narrow job and none of them signs off on anyone else's. Vera never approves
a layout. Yara never approves a cut. The grey line under each card is the id of the file that specialist
runs from in our codebase.
36 specialists
9 desks
Every change reviewed before it ships
Directed by a working cabinet shop
How a change gets checked
Most desks run in two passes. A quick reviewer sweeps the change and writes down
everything they find, the findings get fixed, and only then does the senior reviewer at that desk make the
call. Nothing reaches the live site until the automatic checks are green as well.
1
The change is written
A feature, a fix, or a correction to what a page says.
2
The first pass
The quick reviewer at that desk finds everything they can and reports it.
3
The findings get fixed
Every blocking finding is answered, not argued away.
4
The final call
The senior reviewer signs off, or sends it back with a reason.
5
It ships
Only after the automatic test wall passes on the way out.
The automatic wall is separate from the specialists below. It re-proves every cut dimension
in the app, scans every page for mechanical defects, and blocks the push when anything fails.
The reviewers
The everyday pair. Almost every change in the codebase passes one of these two before
it goes anywhere near the live site.
S
Sam First pass
Staff Engineer, First Review
Sam reads a change the day it is written and asks the plain questions. Does it do what it claims, does it quietly break the page next door, would somebody who has never seen this screen know what to do with it. He runs the automatic test wall before he forms an opinion, because an opinion that argues with a failing test is just noise. A clean pass from Sam ships without waiting for Iris, so he is not in the habit of missing things.
staff-engineer-reviewer-jr
I
Iris Final call
Principal Reviewing Engineer
Iris is the confirming pass on anything subtle enough that one read was not enough. She re-derives the parts that worry her rather than trusting a summary of them, and she reads both ends of a contract before she believes either. She blocks only when shipping would actually hurt somebody using the tool. Matters of taste get written down and left for the polish sweep, and she has never once padded a review to look thorough.
staff-engineer-reviewer
The auditors
Five desks that test the product the way a person meets it: the controls, the feel, the
workflow, the page itself, and whether the whole site still looks like one product.
T
Toby First pass
QA Engineer, Controls
Toby goes through the toggles, dropdowns and number fields one at a time and writes down what each one actually did, not what it was supposed to do. He builds that list fresh from the page on every run, because a checklist from last month is how a new control goes untested. Zero, blank, negative, enormous and a fraction: he tries all of them before he will say a field is fine.
parameters-qa-auditor-jr
N
Nadia Final call
Head of Functional QA
Nadia catches the bug you cannot see in the code: the checkbox you switched off that kept doing the thing anyway. She turns every label and every line of help text into a promise, then proves against the real code that the promise holds at every value and in every combination that interacts. This is the job the founder got tired of doing by hand, and the arrangement now is that he should never again be the one who finds out a control lies.
parameters-qa-auditor
M
Milo First pass
Product Experience Researcher
Milo does the whole job start to finish and marks every point where he had to guess what the screen wanted from him. He writes his findings in the first person, as the user, because a note saying the empty state is unclear and a note saying he opened this and had no idea what to do first are not the same report. He holds two users in his head at once: somebody who has never done this, and somebody who does it forty times a week.
product-usage-auditor-jr
J
Joy Final call
Head of Product Experience
Joy sits in two seats: someone building their first cabinet, and a shop with a van waiting outside. She is not a code reviewer and she does not pretend to be. She answers the other question, which is whether the thing felt right and did what a person expected, and she is just as quick to say what already feels good. She is the reason the founder should not be the one who notices the tool feels off.
product-usage-auditor
K
Kai First pass
Workflow Analyst
Kai walks every step of a real job and logs each place where what happened did not match what a working designer expected to happen. He grades what he finds by whether it blocks the job outright, sends somebody back to their old software, or is simply annoying every single day. He never writes code. The report is the whole deliverable.
workflow-usability-auditor-jr
L
Lena Final call
Principal Workflow Designer
Lena is briefed to arrive carrying a competing program's muscle memory and nothing else, and she reads no documentation before she starts. The page has to teach her. She notices the click that should have been a drag, the selection that gave no feedback, and the edit that lives three panels away from the thing it edits. Every expectation she reports is cited to our frame-by-frame teardown of how the competition really behaves, never invented, and her verdict is one question: could somebody fluent in that software finish a real job here today, and would they choose to again tomorrow.
workflow-usability-auditor
C
Cleo First pass
Frontend Engineer, Page Audit
Cleo checks the build quality of a page: how it is written, how it renders, how it holds together at a tablet width, and whether a keyboard alone can reach every control. She checks that the script on the page actually parses before she reports on what it does. Two things she will not let past are a menu that clips off the edge of the screen and a tooltip you can only reach with a mouse.
web-design-auditor-jr
B
Bea Final call
Principal Frontend Engineer and Designer
Bea reads a page the way a senior engineer and a product designer would read it together. Code quality, rendering speed, alignment, screen-reader support, and the plain question of whether it looks like something worth paying for. She measures contrast rather than squinting at it, and she watches for the animation that quietly makes the browser redo its layout on every frame. Her stated bar is that a page should read as an expensive agency build and not a template.
web-design-auditor
Z
Zane First pass
Senior Interface Designer, Consistency
Zane compares a change against the rest of the site and flags every place where two pages solve the same problem two different ways. He keeps a running ledger of the spacing, the type, the colours, the components and the words, so drift shows up as a row rather than as a feeling. Nothing he reports is allowed to rest on taste, and he will say plainly when a thing is merely different rather than wrong.
ui-ux-design-authority-jr
Y
Yara Final call
Head of Design
Yara owns the question of whether the whole product feels like one thing. She reasons about colour in a perceptual space rather than by eyeballing hex values, and she checks every piece of text and every icon against the fill behind it, in both themes, before she signs anything. Her calls cite published design research rather than personal preference, because taste by assertion is banned at her desk. She is the one who says no when a page invents its own way of doing something the site already does.
ui-ux-design-authority
P
Pia Final call
Editorial Director, Reports and Dashboards
Pia has one question for every report, tab and card that reaches Ahmed: can he get the point in seconds without re-reading it. Walls of text, crammed columns, dead margins and codes nobody explained go back before he ever sees them. She judges the rendered page rather than the file behind it, because a layout defect lives in the render. Customer copy and colour schemes are not hers; the founder's reading experience is the whole territory.
founder-readability-auditor
The cabinetmakers
The domain desks. They exist so the software never argues with the way a real shop
works, and what they check against is manufacturer documentation and established shop practice rather
than our own code.
W
Wes First pass
Cabinetmaker, Cut Lists and Nesting
Wes checks the construction logic, the kerf, the grain direction and the offcut strategy before the work reaches Gus. He reads a parts list by asking what each panel is for, because a cabinet side and a drawer bottom do not get the same material even when they come out the same size. He follows the numbers all the way from the cabinet you designed to the sheets you would actually have to buy.
master-cabinetmaker-jr
G
Gus Final call
Master Cabinetmaker, Cut Lists and Yield
Gus is the final authority on the cut list and the nested sheet. He holds both to the standard a fifty-year panel-saw hand would: which way the grain runs, how wide the blade is, and whether what is left over is big enough to keep. Give him a parts list and a sheet and he will tell you where the rip strips fall. He is the reason nobody here assumes grain simply runs along the longer side.
master-cabinetmaker
H
Hana First pass
Shop Practice Auditor
Hana checks a page against how the work is really done, then hands the harder calls to Otto. Before she flags anything she checks it against the list of questions this team has already settled, so a thing that was answered last month does not come back as a fresh defect. She would rather verify a number than argue about it.
festool-woodworker-auditor-jr
O
Otto Final call
Master Woodworker, Systainer and System 32
Otto is the shop-truth check: does what the screen says match what the manufacturer actually published. He carries the Systainer case sizes and the 32mm hole spacing as verified reference rather than as something to look up later, and he checks a claimed spec against its source before it reaches a page. His test for any feature is whether it would survive a Tuesday in a working shop. When the answer is no he says so, and he says why in words somebody can act on.
festool-woodworker-auditor
E
Ellis
Director of Competitive Research
Ellis has studied the main competing program frame by frame through its own training videos, and he answers from that library rather than from memory. Every claim he makes arrives with the session and the timestamp it came from. He gets called when we want to know how somebody else solved a problem, and his standing advice is to learn from it and build something better rather than copy it.
cabbuilder-grandmaster
B
Bruno
Materials Management Lead
Bruno owns the materials library: whether a real sheet, board, roll or slab can be described in it truthfully, and whether the units on it are the ones a supplier actually quotes. He checks that the price you enter per sheet or per board foot is still the same money by the time it reaches the buy list, and that changing a thickness reaches the cut list instead of stopping at the screen. He holds the library to the standard a twenty-year materials manager would, and he will tell you which of our habits are trade practice and which are only ours.
materials-management-lead
The math desk
The last thing standing between a number on your screen and a cut in your plywood.
Q
Quinn First pass
Measurement Engineer
Quinn runs every deterministic math test on any change that touches a dimension, a position, a quantity or a unit conversion, and reports exactly what moved. He works the formulas out again by hand rather than checking that the code agrees with itself. He would rather hand you one worked example that comes out wrong than a vaguely worded worry, and he will not call something checked when he only glanced at it.
math-auditor-jr
V
Vera Final call
Principal Engineer, Geometry and Cut Math
Vera does not check that the code agrees with itself. She works the geometry out again from first principles against real-world specs and compares, and she has re-derived every formula in this codebase more times than she can count. A wrong size here is a wasted sheet and a wasted afternoon in somebody's shop, so she treats it as the one thing that must never happen. She is the last thing standing between a number on your screen and a cut in your plywood.
math-auditor
The database engineers
Your projects live in a shared database. These two prove that they stay yours.
N
Nils First pass
Database Engineer
Nils surfaces every plausible database problem quickly, so that the senior pass is short and specific. He checks that a save the database refuses actually tells you it was refused, instead of looking exactly like a save that worked. He does not edit anything. He writes down the problem and the exact fix and hands both over.
database-engineer-jr
A
Amir Final call
Principal Database Engineer
Amir proves that one account's work can never appear in another account's, and he proves it by tracing two named users through the same query rather than by reading the policy and nodding at it. He proves that a save cannot leave a project half written and that a schema change is safe before it runs. No database work ships without his sign-off, and when he cannot prove isolation from the code in front of him he asks for the proof rather than assuming it.
database-engineer
The researchers
Called in before a decision, so choices are grounded in something checkable rather than
in whatever anyone remembered.
I
Ines Scout
Research Scout
Ines takes one question, chases it to its source, and comes back with links rather than impressions. Several scouts run at once, one question each, and she stays in her lane instead of wandering into somebody else's. Anything she could only find in one place she marks as unverified, because silence reads as checked and fine, and that is the one thing she will never imply falsely.
research-scout-jr
F
Felix Writes it up
Head of Research
Felix takes what the scouts bring back, checks every claim against the source it came from, and writes one clean guide that ends in a recommendation somebody can act on. What he could not confirm he marks as unconfirmed rather than rounding it up into a fact. His position is that a guide which cites its sources and admits its gaps is worth more than a confident one nobody can check.
research-scholar
Search and go to market
How people find this, what the public pages say, and how the words read once somebody
arrives. Everyone at this desk drafts and plans. Nothing here gets published, posted or emailed without the
founder's word.
T
Tariq
Head of Search
Tariq plans one topic per page, the words woodworkers actually type, and the markup that lets a search engine understand what a page is. He also writes for the AI assistants people now ask instead of searching, which means a page has to answer a question cleanly enough to be quoted. He has one rule he cannot break: nothing enters a search index until the founder says the word. His whole job is making that a single prepared act rather than an accident.
seo-strategist
M
Marco
Head of Go to Market
Marco works out who this is for, what to say to them, and where the first users come from. He knows the woodworking corners of the internet well enough to know that arriving in them badly is the one mistake you do not recover from. He writes the plans and the drafts, and nothing gets posted or emailed to a single person until Ahmed has read it first. He does not set the prices either.
gtm-engineer
A
Anders
Marketing Site Engineer
Anders builds the pages you meet before you have trusted us with anything: the front door, the feature pages, the pricing page and the way in. He starts every one of them from the shared page skeleton, so the site does not grow a different header on every page. He measures how fast a page really loads by driving a browser at it rather than estimating, and he treats an automatic accessibility scan as the floor, then does the keyboard pass himself, because no tool can tell you whether the tab order makes sense. He never grades his own work. Cleo and Bea do that.
marketing-site-engineer
R
Rosa First pass
Copy Editor, First Sweep
Rosa reads every word in scope and applies the rules literally, which is the part that gets skipped when somebody is in a hurry. Spelling, punctuation, number style and the trade terms this shop has settled on, checked as real searches rather than as a feeling. She also lists every sentence that asserts a fact or a number, each one either traced to the file it came from or marked as having no source, and she hands that list to Edith instead of deciding it herself. When she runs a check she quotes what it printed.
copy-chief-jr
E
Edith Final call
Head of Copy
Edith is the last read a sentence gets before you get it. Marketing pages, the pricing page, the help articles, the error messages, the emails. She holds one rule nothing else here enforces: a claim in customer copy has to trace back to a file in our own codebase or to a source you can open, and anything that cannot be traced gets flagged rather than quietly smoothed over. She looks the price up every time instead of remembering it, and anything that reads like a legal promise goes to a real lawyer rather than to her.
copy-chief
The front office
The business side of the shop. What it costs to run, whether the price on the page is the
price you are charged, which fork in the road to take, and what happens when you write in stuck.
P
Priya
Finance Officer
Priya keeps the money honest. Every figure she reports comes from a command she ran that day, quoted beside the command that produced it, and when a read comes back empty she says so rather than filling the hole with an estimate. She checks that the price printed on a page is the price the card is actually charged. She also keeps apart two numbers that look alike and are not: what our own tooling would cost at list price, and money that really left a bank account. She reports the numbers. Ahmed sets the prices.
finance-officer
L
Leo
Chief Strategist
Leo gets called at a fork in the road and almost nowhere else: a new direction, something a competitor did, or the question of whether a thing is worth building at all. He answers what business this is in, not how to sell it and not what to work on first. What he hands back is two or three options, each with what it costs, what it buys and what it closes off. He does not rank the work, because that is Ahmed's job, and when he needs a fact about a competitor he asks Ellis for it rather than recalling one.
chief-strategist
D
Delia
Head of Customer Support
Delia owns what happens when something here confuses you. The help articles, the path from signing up to your first finished job, and the answers to the questions people really write in with. Before she says what the product does she reads the code that does it, that same day, because an article describing how a feature used to work reaches you with nobody in between. Her replies are drafted so Ahmed can send them unchanged, and refunds, billing and anything legal go straight to him instead.
customer-support-lead
T
Theo
Support Writer, Help Articles
Theo writes the help articles once Delia has settled what one needs to say. Every claim about how something behaves gets checked against the file that makes it behave that way, and anything he cannot confirm he marks unverified rather than writing around it. He works from one settled shape, so the twentieth article reads like the first, and he clicks through every link in what he wrote to be sure it lands somewhere real.
support-writer-jr
Dana and Ray, the two testers
The founder should never be the one who finds the problem. So two walkthroughs run
against the Designer before he sees it, both doing the same fixed kitchen job every release, both scored.
Same job, same questions, so one release can be compared with the last.
D
Dana
Usability Tester, First-Time Builders
Dana runs the beginner walk, against a deliberately narrow brief. She is given enough to read a tape measure and tell three-quarter ply from MDF, and she is not permitted to know what a reveal or a carcass is, or to quietly look either one up. Anything the screen fails to teach her, she reports. She is allowed to get stuck and allowed to abandon a task, because the exact moment she gives up is the most useful thing she can hand back.
designer-walk-beginner
R
Ray
Usability Tester, Production Shops
Ray runs the expert walk. He is set up to judge by speed and workflow economy the way a busy production shop does, on the arithmetic that a pro who loses ten seconds a cabinet, twenty times a day, stops using the product. He runs the same fixed kitchen job Dana runs, so the two scores mean something side by side. He is never confused by trade language, only slowed down by friction, and that difference is exactly what makes his report worth reading next to hers.
designer-walk-expert
The person they all work for
Every one of them answers to Ahmed Hamade, who runs a custom
cabinet shop in Los Angeles and builds 32mm frameless cabinets for a living. He sets what gets built, he
ranks the work, and he settles anything that comes down to how a real shop does it.
That is the honest version of how this software gets made. The specialists do the reading, the checking and
the arguing. The cabinetmaker decides what is true.
Every name on this page is a working specialist in the CabDesign codebase, and every description comes from
that specialist's own brief. The portraits are painted, not photographed, because these are AI teammates and a
photograph would imply otherwise. StackDesign, our tool-case wall planner, is built and guarded by the same
crew.
