What problem does it solve? Feature folders in the Bubbles framework fail artifact lint and state-transition guards when spec.md, design.md, scopes.md, report.md, or state.json are missing required sections or control-plane fields, forcing manual rework. ## Core Features & Use Cases - Canonical artifact structure: Defines the required files (spec.md, design.md, scopes.md, report.md, uservalidation.md, state.json) with their owning roles and content rules. - v3 control-plane fields: Documents policySnapshot, scenario-manifest.json, certification., executionHistory, and followUps requirements for state.json. - Anti-pattern detection: Lists rejected patterns such as placeholder content marked done, missing per-DoD-item evidence, and dropped SCN- scenario IDs. - Use Case: When starting a new feature under specs/NNN-feature-name/ or refreshing one flagged MAJOR_DRIFT by bubbles.spec-review, apply this template so artifact-lint.sh passes without exemptions. ## Quick Start Create a new feature folder for the booking feature using the canonical Bubbles feature template with all required artifacts and control-plane fields.