Architectural Assessment Process

A gate-driven workflow for evaluating an architecture — a whole system, a module, or the changes on the current branch — against explicit quality attributes and design principles, and turning that into a traceable, prioritized assessment that a team can act on. The output lives in docs/assessments/arch/{slug}/ASSESSMENT.md.

Two invocation modes:

• Standalone (audit a system or a design): own branch assess/arch-{slug} → PR to develop.
• Embedded in another flow: write into the caller's current branch/worktree; the assessment ships with that flow's PR. No separate branch or PR. Examples: incu-way-development evaluating a planned design at Gate 2, incu-way-docs flagging structural risk while documenting, incu-way-init sizing up a brownfield repo.

This is an assessment flow. Like incu-way-docs, it does not maintain a .ways/state.json (that model is for feature / bug / security work). It assesses and recommends — it does not implement fixes. Acting on a recommendation is a separate incu-way-development or incu-way-bugs work item.