AFAAQ / Capability / 01
Web / SaaS
The surface most people mean when they say the system.
Argument
Web is an entry surface, not the system. It introduces an experience layer above the application platform — which is why replacing it does not replace what it sits on.
Role in the system
An entry surface over a platform.
Adding web to a composition introduces one node in the experience layer, above the API platform and the governed data behind it. Everything the interface can do is bounded by the contracts underneath it.
That separation is the point. A web surface that owns its own data becomes a system of its own, and the next entry point has to duplicate it.
System effect
It adds a layer, not a stack.
The composed system below shows what web contributes: an experience layer, with the audience above it and the application and data layers beneath. It does not introduce services, and it does not introduce infrastructure.
AFAAQ / System effectWeb / SaaS
- Audience: Users
- Experience: Web experience
- Application: API platform
- Data: Data
- ▣Contributed by this capability
- ▭Always present
Context
Evidence