Role
Designer · Orchestrator · Verifier
Agents
Claude Code · Parallel subagents
Stack
Python · SQL · Grasshopper · HTML/CSS
Outputs
Apps · Tools · Pipelines · Design workflows
Human-gated agentic workflow A human brief feeds a strategy plan, which splits into three parallel agent subtasks. Each agent returns a report to a human verification gate. Verified work ships as an app, tool, or design output; rejected work returns to the plan for revision. The human holds both ends of the loop. REVISE — FAILED CHECK HUMAN — BRIEF USER · INTENT · LIMITS STRATEGY PLAN SUBTASKS · GATES AGENT — SUBTASK A AGENT — SUBTASK B AGENT — SUBTASK C HUMAN — VERIFY REPORT VS. SOURCE SHIP APP · TOOL · DESIGN
Fig. 01 — Human-gated agent loop. Heavy rule: human decision. Dashed: agent execution.
01 / Two Commitments
01

Design for the person who inherits it.

I came to architecture from operations, where I held the utility bill for a Silver-certified building constructed ninety degrees off its intended orientation, glass atrium facing full sun. Nobody who made that decision lived with it. The people who occupy, maintain, and pay for a building are the brief.

02

Run execution at agent scale.

I direct AI agents the way I ran construction: a written scope, bounded tasks, a report at each milestone, and an inspection before anything moves forward. It lets one designer carry software and data work alongside the design itself. Accountability does not transfer to the agent.

02 / Method
Brief

Define the user, the objective, and the constraints before any agent runs. An undefined objective is the most expensive failure mode in agentic work. Agents execute it quickly and confidently.

Decompose

Break the work into subtasks small enough to verify. Each gets its own instructions, inputs, and acceptance check. Independent subtasks run in parallel.

Gate

Every step that can change the next one ends in a report and a stop. Destructive or irreversible steps wait for a person. Nothing goes live on an agent's word alone.

Verify

Check output against the source, not against the agent's summary of it. On this site, drafted copy that claimed Revit on SketchUp projects was caught and pulled for exactly that reason.

Persist

Agents start each session cold. Decisions, conventions, and open items live in versioned build notes and plans, so the next session resumes from the record instead of from memory.

03 / Applied All tools →
A.01

bradmachado.com

This site. Rebuilt from a hosted template into hand-written static HTML and one stylesheet, delivered by Claude Code against a phased build plan with a checkpoint at the end of every phase.

Claude Code · HTML/CSS · GitHub Pages
A.02

Portfolio Generator

A Python pipeline that assembles the print portfolio from the live site: generator to self-contained HTML to headless Chromium PDF. 25 pages, 41 images, each used once, no text invented.

Python · Chromium
A.03

HVAC Rightsizing

Peak heating and cooling loads transferred from ResStock onto national-scale U.S. property records. Harmonization and stratification scripted in SQL and Python on Databricks with AI-assisted development.

Databricks · SQL · Python
A.04

Less Siteless

Models in the design loop: a Flux LoRA trained on site imagery, YOLO v.7 traffic analysis from CCTV recordings, Ladybug solar exposure, and Wallacei X optimization driving the form.

ComfyUI · YOLO v.7 · Wallacei X
A.05

Artificial Context

Context generated from a fine-tuned image model, screened structurally in Karamba3D, evolved in Wallacei X, and fed to a MATLAB neural network (R = 0.93).

Flux LoRA · Karamba3D · MATLAB
Position

Agents make execution cheap. They do not make judgment cheap. The scarce skill is knowing what to build, for whom, and whether the output is true — and keeping a person accountable for all three.