Use this when
The situation fits this depth.
- A credible diagnosis or equivalent internal evidence already exists
- The change crosses roles, workflow, authority, information, or technology
- Specialist builders need an implementation-ready design
Level 03
System Architecture
Design only the change the evidence justifies.
System Architecture translates a credible problem definition into decision rights, roles, workflows, information ownership, governance, and an implementation sequence.
Not for
This should not become a shortcut.
- A problem that is still disputed or weakly evidenced
- Generic best practices or SOP writing
- A request for SE Ocean to become the delivery owner
Inputs and evidence
Depth begins with evidence, not terminology.
SE Ocean separates observation, evidence, hypothesis, interpretation, and recommendation throughout the work.
- Credible problem definition
- Decision owner and internal sponsor
- Implementation constraints
- Systems, roles, and information affected
Concrete outputs
What should exist when this scope ends.
Decision rights and authority model
Roles and responsibility design
Workflow, handoff, and escalation architecture
Information and metric ownership
Human-AI responsibility boundaries when relevant
Target operating model
Implementation requirements
Acceptance criteria and sequence
Specialist applications
AI, search, and workflow are system contexts, not competing service pillars.
- Operating model and workflow architecture
- AI and human workflow architecture
- Search and discovery architecture
- Decision rights and governance
- Performance and KPI systems
Boundaries
Uncertainty should be written down, not hidden.
- The client retains executive authority
- Specialists retain technical responsibility
- Design does not silently include implementation delivery