StackDesign is written and checked by a team 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 involved is Ahmed Hamade, who runs the shop and settles anything that comes down to how a real shop does it. Each specialist owns a single narrow job. Below are the ones whose work you feel most directly: the sizes on your wall, the parts on your sheet, and whether your projects stay yours. Each one is a real specialist in this codebase, working to a written mandate.
Everything on this site ends as a number you cut to. Two separate checks stand between that number and your saw.
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.
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.
Four domain desks, here so the software never argues with the way a real shop cuts and assembles. What they check against is manufacturer documentation and established shop practice, not our own code.
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.
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.
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.
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.
You should never be the one who finds the broken control. That is the whole point of this desk.
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.
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.
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.
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.
Your walls, your case inventory and your saved projects live in a shared database. These two prove they stay yours.
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.
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.
StackDesign and CabDesign are built by the same team. Beyond the desks above there are designers who keep every screen consistent, researchers who check a claim before it becomes a feature, a reader whose only job is making sure a report can be understood in seconds, and two testers who run the same fixed job every release and score it. They work across both products.
All of them answer to Ahmed Hamade, who runs a custom cabinet shop in Los Angeles and builds 32mm frameless cabinets for a living. He decides what gets built, and he settles anything that comes down to how a real shop does it.
The portraits above are painted rather than photographed, because these are AI teammates and a photograph would imply otherwise. The names and the briefs are real: each one is a working specialist in this codebase, with a written mandate behind it.