# Plan: Heading — forward roadmap

**Status:** Phase 1 (current = stable gallery tier 3)
**Author:** Mavis (B4 migration, 2026-08-14)

## Phase 1 — Current (v9 GOLD 11-file structure)

- Re-export pattern from `avidtech6/fv-module-gallery` canonical home (FWV v8 §17.5)
- 3 legacy files preserved (index.js, module-meta.json, recipe.md)
- 9 new files added (codex.md, rules.md, ingredients.json, diffs/CHANGELOG.md, trace-atlas/index.json, dna/origin.json, plan.md, coverage-matrix.md, module.json)
- Inspector integration via `module.json` v0.5.1 schema (6-tab pattern: Content / Layout / Background / Style / Animation / Advanced)

## Phase 2 — Next (post-B4)

- Wire `Heading` into the inspector's universal 6-tab pattern
- Add B3 amendment's per-breakpoint `order` + `visibility` (per a531)
- Migrate to the v1.2.29 manifest schema (when B3 work lands)

## Phase 3 — Future

- v9 GOLD visual fidelity sweep (B3 amendment, 4-level colour scheme: Heading is **Green** as a component)
- Mobile-first responsive review (≥300px panel width, 36px tap target)
- Performance budget review (currently 16ms render, 256KB memory)

## Open questions

- Does Heading need its own per-block theme tokens, or does it inherit the region's?
- Should the inspector's "Advanced" tab surface accessibility settings (aria-label, focus order)?
- Is there a tier promotion path (tier 3 → tier 2) for Heading, or is it always tier 3?

## Out of scope

- Widget logic changes (operator constraint: "Do not modify widget code")
- Oscar integration (operator constraint: "Do not modify Oscar")
- CMS chrome changes (operator constraint: "Do not modify CMS chrome")