Data model
Schema, migrations and the invariants the application refuses to violate.
WEB-03 / APPLICATIONKNOuX WEB
Web Application
Software where the user is doing work
A build with real state, real permissions and real failure modes. The interesting engineering is in the data model, the authorisation boundaries and what the interface does when a request is slow or fails.
FIG. WEB / APPLICATIONState and permission topology
01Data model02Authorisation03Interface states04Operations
01 / ARCHITECTURE
The disciplines
Authorisation
Who may read and write what, enforced on the server and not only in the interface.
Interface states
Empty, loading, partial, error and offline treated as designed states.
Operations
Logging, backups and a deployment path that can be run more than once.
02 / HANDOVER
What the build contains
- Data model and migration path
- Authenticated application with role-based access
- Admin surfaces and audit trail
- Deployment and recovery documentation
03 / PLATFORM
Starting points
01Next.js with a typed API layer
02A split frontend and service tier when the domain warrants it
04 / SCOPE
Questions that change the architecture
- Who are the user roles, and what may each one not do?
- What is the expected volume and the cost of a wrong write?
- Does this replace an existing system of record?
05 / CONNECTIONS
Connected capabilities
Related across KNOuX
WEB-03 / NEXT STEP
Define the brief.
Software where the user is doing work