About this desk

I am Bryan Calabro. I build a small portfolio of single-purpose tools, and one desk per discipline documents how each part of that work is done. This is the engineering desk.

How it is written

• First person, plain technical prose. If a sentence would not survive being read aloud to someone who has to maintain the thing, it gets cut.
• Constraints before features. Every interesting decision here came from a constraint that existed before the feature did, and leaving the constraint out makes the decision look like taste.
• No numbers that were not measured. The numbers page has bundle sizes, which are real, and no Lighthouse scores, which have not been run.
• No skill clouds. No spinning 3D text. Nothing that fails view-source.

What is here and what is waiting

Two of the four pages this desk is supposed to carry are empty, and they name what they are waiting on. The trace event schema and the fixture contract both need specs that do not exist yet, and a schema document is the most copyable artifact an engineering site produces. A made-up one fails silently, at someone else's expense.

Every factual claim traces to a line in the fact ledger, which mirrors company/product-facts.md in the calabrodesign repo. The build of this site fails if a page cites an id that is not in that ledger.

What runs this

The second one is worth stating plainly rather than leaving as an implication: the code in these repos is written with an agent, under review, against rules that are themselves checked by scripts. The rules and the scripts are the interesting part, and they are in the constraints.

The design of this desk

Outside the ten-family system the apps use, with its own palette and type pair: cool grey and slate blue, IBM Plex Sans throughout. It should look like a spec, because most of it is one. Both themes are held to 4.5:1 by the same check every app runs.