System Architecture
Puffer runs a multi-agent acquisition pipeline. A raw listing enters at the front door and is passed, agent by agent, through sifting, area intelligence, condition grading, financial screening, cost modelling, verdict and portfolio management — each agent doing one job and handing off to the next. A separate systems-intelligence layer watches the machine itself. Tap any agent to see what it does, what it reads, and what it produces.
Top to bottom is execution order. The dashed branch off Sherlock is a side output (agent correspondence) that does not feed downstream.
These agents are not part of the linear funnel. They monitor the system — model compliance, code & test health, spend, external tooling — and report up to the Director's Office.
Documented and designed, not yet built. These extend Puffer beyond acquisition into property & portfolio management, finance and security.
Generated from config/model_registry.json + agents/*.md by scripts/build_pipeline_page.py. Every fact on this page is read from those sources at build time. Claude builds and maintains the system; Ash makes every acquisition decision.