TenantAtlas/specs/223-astrodeck-website-rebuild/governing-website-spec-classification.md

Governing Website Spec Classification

This crosswalk classifies the in-scope website specs before AstroDeck implementation begins and records the follow-up owner for each one.

Classification Summary

specId	Title	Classification	scopeSummary	rationale	followUpPlan
213	Initial Website Foundation & v0 Product Site	partially valid	broad v0 public-site truth, shared shell expectations, contact/legal baseline, trust-first positioning	The broad public-site intent remains useful, but the original route inventory and trust-route naming no longer match the canonical IA recorded in later specs.	specs/223-astrodeck-website-rebuild/mappings/spec-213-website-foundation-v0.md
214	Website Visual Foundation	continuing	website-only visual direction, tokens, typography, surfaces, CTA/input semantics	AstroDeck changes the implementation substrate, not the website-local visual contract.	specs/223-astrodeck-website-rebuild/mappings/spec-214-website-visual-foundation.md
215	Website Information Architecture / Core Pages	continuing	canonical public IA, route priorities, trust/changelog/contact/legal reachability	The current route truth already reflects this spec and must constrain AstroDeck adoption.	specs/223-astrodeck-website-rebuild/mappings/spec-215-website-core-pages.md
217	Website Homepage Structure & Section Model	continuing	homepage block order, trust/progress placement, CTA sequencing, onward routing	AstroDeck must adapt to the homepage contract instead of redefining it.	specs/223-astrodeck-website-rebuild/mappings/spec-217-homepage-structure.md
218	Website Homepage Hero	continuing	homepage hero semantics, CTA pair, product-near visual truth, bounded trust cues	AstroDeck hero primitives are acceptable only when they preserve the existing hero contract.	specs/223-astrodeck-website-rebuild/mappings/spec-218-homepage-hero.md

Current-Surface Crosswalk

Surface or concern	213	214	215	217	218	Forward owner
/ homepage route	X	X	X	X	X	mappings/spec-217-homepage-structure.md and mappings/spec-218-homepage-hero.md, with 214 and 215 as constraints
/product	X	X	X			mappings/spec-213-website-foundation-v0.md and mappings/spec-215-website-core-pages.md
/trust plus /security-trust compatibility	X	X	X	X	X	mappings/spec-215-website-core-pages.md and mappings/spec-213-website-foundation-v0.md
/changelog			X	X		mappings/spec-215-website-core-pages.md
/contact	X	X	X	X	X	mappings/spec-213-website-foundation-v0.md and mappings/spec-215-website-core-pages.md
/privacy, /imprint, /terms, /legal	X	X	X			mappings/spec-213-website-foundation-v0.md and mappings/spec-215-website-core-pages.md
/solutions and /integrations as retained secondary surfaces	X	X	X			mappings/spec-215-website-core-pages.md
shared visual system, shells, CTA/input semantics	X	X	X	X	X	mappings/spec-214-website-visual-foundation.md

Final Follow-up Execution Order

1. AstroDeck intake binding and primitive verification using astrodeck-source-intake.md and astrodeck-primitive-inventory.md.
2. Conditional foundation slice owned by mappings/spec-213-website-foundation-v0.md, because Spec 213 remains partially valid and still governs broad public-site truth.
3. Shared visual-adaptation slice owned by mappings/spec-214-website-visual-foundation.md.
4. Canonical IA and route-mapping slice owned by mappings/spec-215-website-core-pages.md.
5. Homepage section-composition slice owned by mappings/spec-217-homepage-structure.md.
6. Homepage hero-refinement slice owned by mappings/spec-218-homepage-hero.md.

Execution Notes

• Steps 3 and 4 can overlap once the AstroDeck aliases are bound, but route ownership from Spec 215 must settle before any homepage-only AstroDeck assembly lands.
• Steps 5 and 6 share homepage files and therefore stay sequential after the IA slice has fixed the canonical route shell.
• Any imported AstroDeck demo page that tries to introduce new top-level IA must be handled as removal or suppression work in the owning mapping sheet, not as silent scope growth.