Brendan.dev handles the technical case. This page handles the artifacts that work better as visual surfaces: infographics, fabrication-adjacent outputs, and public-safe studio assets that explain the systems quickly.
The flagship studio artifact: hardware, model lanes, and system topology in one public poster.
These are the assets that do the best job of making the system legible without dragging a visitor straight into documentation first.
Local runtime, model routing, hardware context, and built system lanes in one visual.
The second flagship visual: draft, verify, review, approve, execute. It works here as a studio artifact because the story is visual first, while the operating detail lives on Brendan.dev.
Hubsays is where the broader range sits: fabrication, visual explanation, and the public storytelling layer around the flagship systems.
Desk artifacts, staged prints, and the way digital systems spill into the physical workspace.
Architecture notes, advisory work, and public-safe references that explain system decisions without exposing private internals.
The active product direction used to pressure-test the same operating posture in a more creative environment.