## Summary - bump the TenantPilot constitution to v1.11.0 - add the operator-facing UI naming standard as `UI-NAMING-001` - propagate the naming rule into the Spec Kit plan/spec/tasks templates ## Scope This PR includes only the constitution and Spec Kit template updates needed to enforce operator-facing naming consistency. ## Details - primary actions standardize on `Verb + Object` - scope terms such as `Workspace` and `Tenant` are not used as primary action labels - source/domain wording stays secondary unless disambiguation is required - run labels, notifications, and audit prose align to the same domain vocabulary Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #159 |
||
|---|---|---|
| .. | ||
| memory | ||
| scripts/bash | ||
| templates | ||
| plan.md | ||
| README.md | ||
| research_t186.md | ||
| spec.md | ||
| tasks.md | ||
.specify/ (Tooling)
This folder contains SpecKit tooling (templates, scripts, constitution, etc.).
Important
- Do not create new feature specs in
.specify/spec.md,.specify/plan.md,.specify/tasks.md. - Active feature specs live under
specs/<NNN>-<slug>/:spec.mdplan.mdtasks.mdchecklists/requirements.md
The files .specify/spec.md, .specify/plan.md, .specify/tasks.md may exist as legacy references only.