TenantAtlas/specs/223-astrodeck-website-rebuild/astrodeck-primitive-inventory.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

7.6 KiB

AstroDeck Primitive Inventory

The IDs below are stable intake aliases for the AstroDeck snapshot described in astrodeck-source-intake.md. They are the only allowed primitive vocabulary for follow-up rebuild planning until the real snapshot is mounted and bound to these aliases.

Inventory Columns

Column Meaning
primitiveId Stable intake alias used by the mapping sheets
primitiveType page, section, or component
sourceReference Expected AstroDeck source family or later binding target
candidateSurfaces Current routes or spec slices the primitive can support
demoContentFlags Demo artifacts that must be removed, adapted, or explicitly approved
notes Review guidance before the primitive is kept or adapted

Page Candidates

primitiveId primitiveType sourceReference candidateSurfaces demoContentFlags notes
adk-page-home-marketing page snapshot/page/home /, Specs 213, 215, 217, 218 demo stats, generic customer proof, newsletter CTA Primary landing substrate for the rebuild.
adk-page-product-overview page snapshot/page/product-or-features /product, Specs 213, 215 feature-silo copy, pricing teaser Use for the product-model page, not a feature-wall clone.
adk-page-trust-proof page snapshot/page/security-or-proof /trust, Specs 213, 215, 217, 218 compliance theater, absolute claims, badge walls Preferred starting point for the canonical trust route.
adk-page-contact-conversion page snapshot/page/contact /contact, Specs 213, 215 generic sales language, oversized lead form Must be adapted to the working-session framing.
adk-page-content-index page snapshot/page/blog-or-news-index /changelog, optional /resources blog taxonomy chrome, author bios, editorial promos Repurpose for dated changelog proof; keep resources unpublished unless substantive.
adk-page-legal-utility page snapshot/page/legal-or-company-utility /privacy, /imprint, /terms, /legal placeholder legal copy, company boilerplate Use as the base for legal surfaces; do not ship template legal text.
adk-page-supporting-showcase page snapshot/page/about-solutions-or-integrations /solutions, /integrations fake logos, partner walls, over-broad ecosystem claims Secondary-only surface for audience-fit and integration-fit pages.

Section Candidates

primitiveId primitiveType sourceReference candidateSurfaces demoContentFlags notes
adk-section-hero-split-media section snapshot/section/hero-split-media homepage, product, trust, contact startup buzzwords, fake metrics, decorative dashboard wallpaper Preferred hero family for Specs 217 and 218.
adk-section-outcome-band section snapshot/section/outcomes-or-value-band homepage, product vague benefit copy, investor-style slogans Use to translate product capability into buyer outcomes.
adk-section-feature-cluster-grid section snapshot/section/feature-grid-or-capability-clusters homepage, product, solutions, integrations equal-weight feature cards, pricing hooks Must be grouped by product model, not by generic marketing categories.
adk-section-trust-principles section snapshot/section/trust-or-proof-grid trust page, homepage compliance badges, guarantee claims Use only with bounded, supportable trust language.
adk-section-proof-stats section snapshot/section/stats-or-proof-strip homepage, product, trust invented KPIs, vanity counters Remove unless real approved proof exists.
adk-section-logo-strip section snapshot/section/logo-cloud homepage, solutions fake customers, unapproved brands Remove by default.
adk-section-testimonial-stack section snapshot/section/testimonials homepage, solutions fabricated quotes, polished social proof Remove by default.
adk-section-changelog-teaser section snapshot/section/news-or-update-teaser homepage, changelog editorial filler, blog cards without dated product value Keep only if it points to real dated changelog entries.
adk-section-contact-form section snapshot/section/contact-form contact, footer CTA follow-through unnecessary intake fields, aggressive SDR language Adapt to minimal useful working-session context.
adk-section-cta-band section snapshot/section/final-cta homepage, product, trust, changelog, legal duplicated loud CTAs, demo pressure Keep exactly one dominant action.
adk-section-footer-utility section snapshot/section/footer-utility all public routes docs/pricing overload, empty content links Must match the canonical 215 IA.

Component Candidates

primitiveId primitiveType sourceReference candidateSurfaces demoContentFlags notes
adk-component-header-nav component snapshot/component/header-nav all public routes pricing/docs/blog clutter Must shrink to Product, Trust, Changelog, Contact, plus one CTA.
adk-component-footer-nav component snapshot/component/footer-nav all public routes template link dumps Must preserve trust/legal/contact grouping.
adk-component-primary-button component snapshot/component/button-primary homepage, product, trust, contact multi-primary CTA styling Dominant CTA only.
adk-component-secondary-button component snapshot/component/button-secondary homepage, product, trust, contact, changelog outline fallback styling with no hierarchy Use only as a lower-emphasis deepening action.
adk-component-badge-chip component snapshot/component/badge-chip hero trust cues, callouts badge walls, pseudo-certification labels Use sparingly and only with factual claims.
adk-component-card-surface component snapshot/component/card product clusters, legal summaries, changelog cards over-elevated surfaces Keep border-first clarity and restrained shadows.
adk-component-section-shell component snapshot/component/section-shell all page families inconsistent width/spacing defaults Main adaptation point for Spec 214 spacing and surface rules.
adk-component-input-field component snapshot/component/input contact marketing-form defaults Must align to the website foundation and minimal intake scope.
adk-component-textarea-field component snapshot/component/textarea contact marketing-form defaults Same constraint as the input field.
adk-component-callout-panel component snapshot/component/callout-or-alert-panel product, trust, legal, changelog alarmist styling, decorative status colors Use for bounded explanation, not urgency theater.

Demo-Content Flag Vocabulary

  • demo stats: invented counters, fake KPIs, or unsourced numerical proof.
  • generic customer proof: logo clouds, testimonials, and case-study language without approved source material.
  • newsletter CTA: sign-up or nurture patterns that are not part of the current IA.
  • pricing teaser: navigation or CTA pressure toward pricing or packaging pages that are not live.
  • compliance theater: seals, badges, or guarantee language that overstates trust posture.

Inventory Conclusion

The alias set above is sufficient to drive the per-spec mapping sheets without creating net-new primitive families up front. Where the imported snapshot later disproves one of these families, the mismatch must reopen the intake review and the exception workflow before implementation continues.