// 01What an Agent Is, In This Practice
Three boundaries every Lualdi agent has — and what we don't build.
The word "agent" is now overloaded. In Lualdi practice it has a specific meaning: a decision system with explicit inputs, an explicit decision boundary, and exactly one output an operator can act on or override. If a candidate concept doesn't fit those three boundaries, it isn't an agent we'll build — it's an unbounded chatbot dressed in a different name.
// 01
Defined input
Every agent declares exactly what it consumes — futures curves, AIS positions, FDA calendars, claims data, satellite imagery, rent rolls, port arrivals. No "all available information." The input set is finite, sourced, and contractable.
// 02
Decision boundary
The agent makes one kind of call — buy / hedge / wait; supported / stretched; comply / re-route; pass / fail. The decision space is small enough to validate, large enough to matter. Drift outside the boundary is a defect, not a feature.
// 03
Single output, operator-actionable
One number, one tag, one draft document, one queued action. The operator reads it, signs or overrides, moves on. No essays, no five-tab dashboards, no "here's what I noticed." The output queues for approval before any write to a system of record.
If a system doesn't have a defined input, a decision boundary, and a single operator-actionable output, it isn't an agent. It's a summary. Lualdi Advisors doesn't build summaries.