04 / Architecture & consulting
Make the system
make sense.
The interesting work sits between the model, the data, and the person relying on the answer.
Start with the decision.
Trace the information.
Then draw the boxes.
Principles / design perspective
Four questions.
Before another service.
- 01
Make the boundaries explicit.
Who can read a record? Which service owns it? What can an agent change? Clear boundaries make a system easier to reason about.
- 02
Keep the evidence close.
A useful answer has a path back to its source. Retrieval and structured data should support verification, especially when the output informs a decision.
- 03
Design for imperfect inputs.
Documents are incomplete. Integrations fail. Users change their minds. The recovery path deserves as much attention as the happy path.
- 04
Choose the simplest useful system.
Start with a concrete workflow and its constraints. Add infrastructure when the problem calls for it, and make the tradeoff visible.
An illustrative review framework
From a diagram
to a decision.
This is a conceptual way to structure an architecture conversation, rather than a description of any client’s internal process.
- 01
Frame
Identify the users, the decision, and the constraints that actually matter.
- 02
Trace
Follow data through the interface, application, model, tools, and storage.
- 03
Challenge
Ask what happens with missing evidence, incorrect permissions, and failed dependencies.
- 04
Sequence
Separate the essential foundation from improvements that can safely wait.