Design Change

Only apply DESIGN.md-class items to the design document.

Steps

1. Identify the target portal design guide (web/apps/<portal>/DESIGN.md).
2. Read the current design guide and related governance:
   • docs/architecture/web.md
   • docs/constitution/web.md
   • openspec/config.yaml
3. Read relevant active OpenSpec change artifacts if UI-affecting work is in flight.
4. Classify each requested change using the rule above.
5. Update DESIGN.md with invariant-only changes.
6. Keep drift controls intact:
   • do not add feature workflow steps
   • do not add API behavior rules
   • keep anti-drift guardrail statements present
7. Provide a handoff summary:
   • what was applied to DESIGN.md
   • what should be captured in OpenSpec
   • what should be captured in ADR
   • what was deferred to backlog

Guardrails

• Do not transform DESIGN.md into a feature spec.
• Do not remove stable invariants without explicit replacement rationale.
• If a requested change is not clearly durable, prefer deferring it rather than encoding it as an invariant.
• If no valid invariant changes are identified, explicitly report that no design-doc mutation should occur.