TenantAtlas/specs/223-astrodeck-website-rebuild/mappings/spec-213-website-foundation-v0.md
ahmido 71f94c3afa
Some checks failed
Main Confidence / confidence (push) Failing after 44s
spec: finalize 223 AstroDeck rebuild planning consistency (#262)
## Summary
- finalize Spec 223 planning artifact set for AstroDeck website rebuild
- align `spec.md`, `plan.md`, `tasks.md`, `research.md`, `data-model.md`, `quickstart.md`, and contract schema
- add/complete inventory, mapping, exception, drift-follow-up, and supersession artifacts
- mark legacy website-spec task references as superseded and wire follow-up ownership

## Key Outcomes
- no remaining cross-artifact consistency findings in the Spec 223 bundle
- explicit Spec 213 handling path added
- material-drift follow-up rules normalized
- exception register and documented exception model made explicit and schema-backed

## Validation
- Integrated browser smoke check passed for main website routes (`/`, `/product`, `/trust`, `/changelog`, `/contact`, `/privacy`, `/imprint`, `/legal`, `/security-trust`)
- no console errors/warnings observed during route smoke navigation
- YAML contract parses successfully

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #262
2026-04-22 07:52:32 +00:00

4.1 KiB

Mapping: Spec 213 - Initial Website Foundation & v0 Product Site

Status

Field Value
classification partially valid
follow-up owner specs/223-astrodeck-website-rebuild/mappings/spec-213-website-foundation-v0.md
legacy task file specs/213-website-foundation-v0/tasks.md
exception outcome no exception required
material drift references 223-DRIFT-213-ia, 223-DRIFT-213-nav, 223-DRIFT-213-trust

Spec 213 remains useful as the broad v0 public-site contract, but its original route emphasis predates the later canonical IA. This mapping sheet keeps the surviving truth while moving all implementation ownership onto AstroDeck.

Mapping Records

Requirement reference Candidate primitive(s) Disposition Adaptation summary Acceptance mapping materialDriftReferences exceptionReference
Core public-site shell, header/footer reachability, and one coherent page family adk-component-header-nav, adk-component-footer-nav, adk-component-section-shell adapt Collapse AstroDeck navigation to Product, Trust, Changelog, and Contact plus one primary CTA; preserve footer legal grouping; keep repo-level website contracts intact. 213 FR-002, FR-003, FR-010, FR-011, FR-017 223-DRIFT-213-nav none
First-pass product explanation across Home and Product adk-page-home-marketing, adk-page-product-overview, adk-section-outcome-band, adk-section-feature-cluster-grid adapt Keep the trust-first governance story, but replace the current custom page assembly with AstroDeck landing and product shells. 213 FR-001, FR-004, FR-005, FR-012, FR-016 none none
Trust, contact, and legal baseline adk-page-trust-proof, adk-page-contact-conversion, adk-page-legal-utility, adk-section-trust-principles, adk-section-contact-form adapt Route trust to /trust, preserve /contact as the primary next step, and repurpose legal/company utility pages for privacy, imprint, terms, and the retained legal hub. 213 FR-007, FR-008, FR-009, FR-010 223-DRIFT-213-trust none
Secondary pages and compatibility behavior adk-page-supporting-showcase, adk-page-content-index, adk-page-trust-proof adapt Keep /solutions, /integrations, /legal, and /terms published as secondary surfaces; preserve /security-trust as a redirect only; add /changelog and /imprint through adapted content/legal shells. 213 SC-002, SC-004, plus the Spec 223 rebuild rule for preserved history 223-DRIFT-213-ia none

Replacement Tasks

  1. Bind the AstroDeck aliases for the landing shell, product shell, trust proof page, contact page, and legal utility page before any code is copied out of the current apps/website implementation.
  2. Adapt adk-component-header-nav and adk-component-footer-nav to the canonical Product/Trust/Changelog/Contact navigation model with retained legal footer grouping.
  3. Map adk-page-home-marketing and adk-page-product-overview to the v0 product-story surfaces without carrying over AstroDeck demo proof, pricing, or newsletter behavior.
  4. Repurpose adk-page-trust-proof, adk-page-contact-conversion, and adk-page-legal-utility for /trust, /contact, /privacy, /imprint, /terms, and /legal.
  5. Add a route-suppression pass that removes AstroDeck demo pages from top-level discoverability and keeps /security-trust as a compatibility redirect only.
  6. Re-run the Spec 213 acceptance trace against the later canonical IA so the broad v0 truth remains visible without overriding Specs 214, 215, 217, and 218.

Spread Control and Acceptance Trace

  • Spread control: this mapping sheet does not authorize any new public IA beyond the canonical route family already documented in the current-site inventory and Spec 215.
  • Acceptance trace: broad v0-site requirements remain owned here, but route inventory, navigation, and trust-route naming defer to the later specs and the drift ledger.
  • Exception note: no exception is approved. If the mounted AstroDeck snapshot lacks a usable legal utility page or trust-proof page, the missing family must reopen exception-register.md.