History

ahmido edf7646a18 Some checks failed Main Confidence / confidence (push) Failing after 43s Details Spec 200: add Filament surface rules constitution (#248 ) ## Summary - add Spec 200 for the Filament nativity and custom-surface constitution slice - amend the shared constitution with native-by-default, fake-native, shared-family, state-layer, reviewer-guidance, and exception language - add the full Spec 200 artifact set: spec, plan, research, data model, quickstart, tasks, contract, and requirements checklist - align the operator UX standards doc to the new constitution vocabulary - remove superseded `001-*` spec artifacts that were replaced by the new feature work ## Validation - completed consistency analysis across spec, plan, tasks, and contract artifacts - completed integrated-browser smoke check on the current TenantPilot dashboard - no runtime tests executed because this is a docs-only governance change ## Notes - runtime application behavior is intentionally unchanged - enforcement automation, grep/lint guards, and regression test operationalization remain deferred to Spec 201 Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #248		2026-04-18 15:33:26 +00:00
..
memory	Spec 200: add Filament surface rules constitution (#248 )	2026-04-18 15:33:26 +00:00
scripts/bash	dev-merges/c709b36 (#3 )	2025-12-21 23:15:12 +00:00
templates	docs: add Spec 212 test authoring guardrails (#245 )	2026-04-18 10:08:00 +00:00
plan.md	docs: deprecate .specify specs and update references (#53 )	2026-01-10 21:40:46 +00:00
README.md	docs: add Spec 212 test authoring guardrails (#245 )	2026-04-18 10:08:00 +00:00
research_t186.md	docs: deprecate .specify specs and update references (#53 )	2026-01-10 21:40:46 +00:00
spec.md	docs: deprecate .specify specs and update references (#53 )	2026-01-10 21:40:46 +00:00
tasks.md	docs: deprecate .specify specs and update references (#53 )	2026-01-10 21:40:46 +00:00

README.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.md
- plan.md
- tasks.md
- checklists/requirements.md
Runtime-changing or test-affecting work MUST carry actual test-purpose classification (Unit, Feature, Heavy-Governance, Browser), affected lanes, fixture/default cost risks, heavy-family changes, escalation decisions, and minimal validation commands through the active spec.md, plan.md, and tasks.md.
Review-oriented checklists MUST surface lane fit, hidden defaults, heavy-family visibility, and runtime-budget follow-up before merge; lane upkeep belongs to the feature, not to a later cleanup pass.

Review Entry Point

Use the active feature's spec.md, plan.md, and tasks.md together with the generated checklist based on .specify/templates/checklist-template.md.

Confirm the spec names the affected validation lane(s) or a deliberate N/A, the test family impact, setup-cost impact, reviewer handoff, and any escalation outcome.
Confirm the plan turns that into changed test types, narrowest proving commands, helper/default widening checks, and the note target for budget or trend drift.
Apply the checklist and end with one explicit outcome: keep, split, document-in-feature, follow-up-spec, or reject-or-split.

Low-Impact Rule

Docs-only or template-only work may answer N/A or none.
Do not force fake lane prose when no runtime or suite impact exists.

Escalation Rule

Use document-in-feature for contained cost or drift that belongs in the active feature.
Use follow-up-spec only for recurring pain or structural lane or family changes.
Use reject-or-split when hidden test cost or wrong-lane scope is still unresolved.