TenantAtlas/specs/226-astrodeck-inventory-planning/inventory/sections.md
ahmido ccd4a17209
Some checks failed
Main Confidence / confidence (push) Failing after 1m36s
spec: finalize 226 astrodeck inventory planning artifacts (#263)
## Summary
- finalize Spec 226 artifacts for AstroDeck inventory planning
- include completed planning set: spec, plan, research, data model, quickstart, tasks, checklist, contracts, and inventory outputs
- apply consistency fixes from the project analysis review

## Included changes
- updated `.github/agents/copilot-instructions.md` from agent-context sync
- added/updated all files under `specs/226-astrodeck-inventory-planning/`

## Notes
- docs/spec workflow changes only
- no runtime code paths changed

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

5.2 KiB

Section Inventory

  • catalog_id: astrodeck-226-baseline
  • primitive_class: Section
  • entry_count: 8

section.page-hero

  • entry_id: section.page-hero
  • identifier: PageHero
  • primitive_class: Section
  • file_ref: apps/website/src/components/sections/PageHero.astro
  • functional_role: Renders the primary hero composition for the homepage and all secondary pages.
  • default_semantics: Hero section with badge, headline, supporting copy, CTA cluster, and optional product visual or trust proof.
  • default_visual_character: bold-visual
  • tenantatlas_relevance: high
  • suitability_class: A
  • markers: [tenantatlas-likely, hero-candidate]
  • notes: This is the most important rebuild primitive because it already defines homepage and subpage hero behavior in one place.

section.feature-grid

  • entry_id: section.feature-grid
  • identifier: FeatureGrid
  • primitive_class: Section
  • file_ref: apps/website/src/components/sections/FeatureGrid.astro
  • functional_role: Presents feature or rule clusters in a repeatable grid with a section header.
  • default_semantics: Product-explainer or rule-list section that relies on structured cards rather than freeform prose.
  • default_visual_character: enterprise-neutral
  • tenantatlas_relevance: high
  • suitability_class: A
  • markers: [tenantatlas-likely, product-explainer-candidate]
  • notes: Strong direct-fit section for product, solutions, and integrations surfaces.

section.cta-section

  • entry_id: section.cta-section
  • identifier: CTASection
  • primitive_class: Section
  • file_ref: apps/website/src/components/sections/CTASection.astro
  • functional_role: Delivers the final conversion handoff from any route back into contact or the next core page.
  • default_semantics: Closing CTA band with one required primary action and one optional secondary action.
  • default_visual_character: enterprise-neutral
  • tenantatlas_relevance: high
  • suitability_class: A
  • markers: [tenantatlas-likely, contact-candidate]
  • notes: It appears across the route set and already encodes the preferred evaluation handoff pattern.

section.capability-grid

  • entry_id: section.capability-grid
  • identifier: CapabilityGrid
  • primitive_class: Section
  • file_ref: apps/website/src/components/sections/CapabilityGrid.astro
  • functional_role: Explains the grouped product model through clustered capability cards.
  • default_semantics: Product-explainer section with structured clusters, optional metadata badges, and linked supporting detail.
  • default_visual_character: enterprise-neutral
  • tenantatlas_relevance: high
  • suitability_class: A
  • markers: [tenantatlas-likely, product-explainer-candidate]
  • notes: Strong fit for any rebuild surface that needs to explain how TenantAtlas capabilities connect.

section.outcome-section

  • entry_id: section.outcome-section
  • identifier: OutcomeSection
  • primitive_class: Section
  • file_ref: apps/website/src/components/sections/OutcomeSection.astro
  • functional_role: Frames product value through outcome cards rather than a feature checklist.
  • default_semantics: Mid-page section with a header plus three outcome cards.
  • default_visual_character: enterprise-neutral
  • tenantatlas_relevance: high
  • suitability_class: A
  • markers: [tenantatlas-likely]
  • notes: Useful for the homepage because it translates product truth into buyer outcomes without inflating surface complexity.

section.trust-grid

  • entry_id: section.trust-grid
  • identifier: TrustGrid
  • primitive_class: Section
  • file_ref: apps/website/src/components/sections/TrustGrid.astro
  • functional_role: Shows the public trust posture through structured trust-principle cards.
  • default_semantics: Trust-proof section with a header and a fixed card grid.
  • default_visual_character: enterprise-neutral
  • tenantatlas_relevance: high
  • suitability_class: A
  • markers: [tenantatlas-likely, trust-candidate]
  • notes: Canonical trust section for both the homepage trust block and the dedicated trust route.

section.logo-strip

  • entry_id: section.logo-strip
  • identifier: LogoStrip
  • primitive_class: Section
  • file_ref: apps/website/src/components/sections/LogoStrip.astro
  • functional_role: Displays ecosystem-fit badges or logo-like entries in a compact supporting strip.
  • default_semantics: Supporting proof section that compresses partner, ecosystem, or integration signals into a narrow banner treatment.
  • default_visual_character: decorative
  • tenantatlas_relevance: medium
  • suitability_class: C
  • markers: [needs-heavy-adaptation, semantic-risk]
  • notes: The pattern is reusable only when ecosystem proof is concrete; otherwise it risks overstating breadth and slipping into decorative social proof.

section.progress-teaser

  • entry_id: section.progress-teaser
  • identifier: ProgressTeaser
  • primitive_class: Section
  • file_ref: apps/website/src/components/sections/ProgressTeaser.astro
  • functional_role: Surfaces recent dated progress entries and links back to the full changelog.
  • default_semantics: Changelog teaser section with compact dated cards and one follow-up CTA.
  • default_visual_character: utility-dense
  • tenantatlas_relevance: high
  • suitability_class: A
  • markers: [tenantatlas-likely, changelog-candidate]
  • notes: Directly aligned with the visible-progress requirement for the current website strategy.