---
kind: constraint
status: active
confidence: high
severity: <must|should|may>
category: <architecture|ui|ux|language|workflow|security|performance|other>
scope: <global|scope-name>
globs:
  - "<path-or-glob>"
  - "<path-or-glob>"
---

# Constraint — <title>

## Statement

A clear, enforceable rule. Use MUST/SHOULD/MAY language.

## Rationale

Why this constraint exists. What problem does it prevent or what quality does it preserve?

## Applies to

- PRDs/epics/bets in scope: `<scope>`
- Categories: `<category>`

## Examples

- Example of compliant design.
- Example of violation.

## Related

- Link to ADRs, records, or other constraints this reinforces or limits.