Main Confidence / confidence (push) Failing after 44s

Details

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

3.5 KiB

Raw Blame History

Mapping: Spec 217 - Website Homepage Structure & Section Model

Status

Field	Value
classification	continuing
follow-up owner	`specs/223-astrodeck-website-rebuild/mappings/spec-217-homepage-structure.md`
legacy task file	`specs/217-homepage-structure/tasks.md`
exception outcome	no exception required
material drift references	none

Spec 217 remains the homepage structure contract. AstroDeck can supply section families, but it may not reorder the homepage into a generic feature wall or proof-heavy template.

Mapping Records

Requirement reference	Candidate primitive(s)	Disposition	Adaptation summary	Acceptance mapping	materialDriftReferences	exceptionReference
Hero to outcome flow	`adk-section-hero-split-media`, `adk-section-outcome-band`	adapt	Keep the homepage order of hero first, outcome framing second, and route visitors into a product-near reading path immediately.	217 FR-001, FR-002, FR-003, FR-004, FR-008	none	none
Grouped capability model instead of route-job cards	`adk-section-feature-cluster-grid`	adapt	Use grouped capability clusters that route deeper explanation to `/product` instead of equal-weight marketing cards.	217 FR-009, FR-010	none	none
Trust and progress before the final CTA	`adk-section-trust-principles`, `adk-section-changelog-teaser`, `adk-section-cta-band`	adapt	Keep trust and visible product movement ahead of the closing CTA and route them to `/trust` and `/changelog`.	217 FR-011, FR-012, FR-013, FR-014, FR-018	none	none
Optional proof sections that risk fake maturity	`adk-section-proof-stats`, `adk-section-logo-strip`, `adk-section-testimonial-stack`	remove	Remove by default unless the team has approved, real, public-safe proof material.	217 FR-017, FR-020	none	none
Header/footer discoverability and mobile continuity	`adk-component-header-nav`, `adk-component-footer-nav`, `adk-section-footer-utility`	adapt	Preserve the published route set and keep the same meaning order on narrow screens.	217 FR-005, FR-006, FR-015, FR-016, FR-019, FR-021	none	none

Replacement Tasks

Adapt adk-section-hero-split-media into the homepage entry point without letting AstroDeck proof strips or testimonial blocks appear above the product explanation.
Adapt adk-section-outcome-band so buyer-oriented outcomes appear before any capability cluster or proof section.
Rebuild adk-section-feature-cluster-grid into grouped capability coverage that routes to /product instead of acting like a route list.
Place adk-section-trust-principles and adk-section-changelog-teaser ahead of the closing adk-section-cta-band.
Remove adk-section-proof-stats, adk-section-logo-strip, and adk-section-testimonial-stack unless real proof assets are explicitly approved later.
Re-check the homepage route transitions, footer legal reachability, and mobile section order after the mapped sections are in place.

Spread Control and Acceptance Trace

Spread control: homepage-only structure work may not pull in extra AstroDeck sections simply because they are visually available.
Acceptance trace: the mapping preserves the required homepage block set, section order, trust/progress placement, and onward routing from Spec 217.
Exception note: no exception is approved. If the mounted snapshot lacks a usable outcome or changelog-teaser family, reopen the exception workflow before composing a net-new homepage section.

3.5 KiB Raw Blame History