TASK-C03: Architecture Pack and Diagram Briefs

• Status: Ready
• Scope Type: Architecture teaching content
• Recommended Model Tier: Frontier
• Recommended Reasoning: High

Objective

Explain how the system is designed and produce diagram briefs that can be turned into Draw.io diagrams without guesswork.

Scope

Create architecture pages for:

1. system context
2. project and layer map
3. domain model
4. workflow and state model
5. runtime sequences

Required Diagrams

At minimum, brief these diagrams:

• system context diagram
• project and layer dependency diagram
• domain class diagram
• workflow state diagram
• start-run sequence diagram
• fault and recovery sequence diagram

Non-Scope

• completing all visual assets
• adding new product requirements
• changing architecture in code

Files To Read First

• docs/requirements.md
• docs/adrs/ADR-001-use-central-app-state-store.md
• docs/adrs/ADR-004-use-one-operational-maturity-slice-before-specialized-modules.md
• docs/specs/SLICE-001-first-strong-vertical-slice.md
• docs/specs/SLICE-004-operational-maturity.md
• key files in src/InspectionPrototype.Application, src/InspectionPrototype.Presentation, and src/InspectionPrototype.Infrastructure

Verification

• diagrams are explicit enough for Draw.io implementation
• architecture claims match code and ADRs
• npm run docs:build

Copy/Paste Prompt

You are working in C:\Lcn.Workspaces\lcn-wafer-inspection-desktop.

Audience: a newcomer software engineer or automation engineer learning this project.
Goal: turn this repo into a high-quality engineering training course, not just reference docs.
Style: practical, detailed, blog-quality English; clear headings; concrete examples; no fluff.
Ground all claims in the repo docs and code. Do not invent behavior that the current project does not support.
Prefer reusing and linking existing content under docs/lessons, docs/specs, docs/tasks, docs/adrs, docs/implementation, and the source code when helpful.
For diagrams, do not generate binary assets. Instead, produce a Draw.io-friendly diagram brief: title, purpose, nodes, edges, grouping, caption, and destination file path.
If you edit docs, keep VitePress navigation coherent and make sure npm run docs:build passes.

Task: Create the architecture teaching pack for this repo.

Create under docs/architecture:
- index.md
- 01-system-context.md
- 02-project-and-layer-map.md
- 03-domain-model.md
- 04-workflow-and-state-model.md
- 05-runtime-sequences.md

For each page:
- explain the design in newcomer-friendly engineering-blog style
- include code references where helpful
- include trade-offs and why this design was chosen
- include at least one Draw.io-friendly diagram brief

Cover at least these diagrams:
- system context diagram
- project and layer dependency diagram
- domain class diagram
- workflow state diagram
- start-run sequence diagram
- fault and recovery sequence diagram

Verify with npm run docs:build.