working brief / local only
start with the hard part.
track 01 / 03
01 / selected engineering question
track focus / product engineering
the question
sets the work.
Which person, workflow, or decision needs a better product?
build the product.
A customer-facing application, an internal tool, or a platform with several moving parts. The job is to turn the required behavior into a coherent, operable system.
what this brief can make concrete
- Application architecture and data model
- Accessible interfaces and core workflows
- APIs, integrations, and permission boundaries
- Verification, release, and handover documentation
02 / the whole system
A conceptual model.
No black boxes.
good software
goes all the way down.
The screen is only the beginning. Select a layer to see the questions underneath it.
where people meet the product.
Screens, interactions, accessibility, and the feedback that helps someone finish a real task.
Can someone find the next action, recover from a mistake, and use it with a keyboard?
↳ Hands a clear user intent to the workflow layer.
where intent becomes action.
Business rules, integrations, and AI steps with explicit boundaries, review points, and recovery paths.
What is automated? Who approves the consequential steps? What happens when a dependency fails?
↳ Coordinates actions against the data layer.
where the system keeps its word.
The information model, permissions, and history that keep the product consistent as work moves through it.
Who can read or change each record? Can you trace a decision back to its source?
↳ Depends on infrastructure for durable storage and access.
where everything has to hold.
Deployment, monitoring, recovery, and the operating routines that make a system understandable after release.
How will you notice a failure, restore the service, and change it without guessing?
↳ Supports every layer with observable, repeatable operation.