← Back to Index

Home — Domain-Control Data-Gap Analysis

Data-gap summary for the Home screen. The full property-level treatment is backend-api-mapping-report.html §1–7 (the original Home deep dive); this is the per-set summary that matches the other screen-set reports.

Figma file R6hPjBdjSIn6946qTJasUC · node 4099:5229 (Home) · Source: Figma MCP + codebase (UserInfo, DocumentItem, MenuItem) · Branch docs/home-data-gap-finish.

Headline — analysis complete; mapped except the 3 required API changes. Home is the most fully analyzed set. Its content maps to UserInfo, DocumentItem (via GetDocuments) and MenuItem. The open backend items are exactly the three Required API Changes in §5 of the backend report: Rank (blocking), Description (minor), Favorites (cross-control). Everything else is presentation/scaffold build — not analysis.

1 · Data-source mapping

Home element	Data	Source	Status
Pilot Card — heading	"Welcome {Rank} {Name}"	`UserInfo` (name) + Rank	gap · Change 1
Pilot Card — View Contract	link text + target	first contract `DocumentItem` (Title → FileID nav). Whole card taps = same as View Contract; chevron is visual only.	mapped
card-lg feeds + Hotel Request hero	image · eyebrow · title	`GetDocuments` → `DocumentItem`; sections by Scope / Category / Grouping	mapped
card-sm tiles (DART · Flight Pay Loss · …)	title · icon · route	`MenuItem` { Title, Path/SpecialCode, ImageSource, ShowOnHomeScreen, SortOrder }	mapped
card-sm richer text variant	description / subtitle	`MenuItem` + Description	gap · Change 2
Emergency Hotline (Primary button)	label · phone action	`MenuItem` identified by `SpecialCode` → `tel:`	mapped
Section headers / View-All	title + view-all link	content-driven (Scope / Category / Grouping on the GetDocuments response)	mapped
Favorite heart (every card)	is-favorite + toggle	— shown on Home (D31, 2026-06-26); cross-control favorites gap	gap · Change 3
card-lg yellow accent	border color variant	design question — data-driven vs static	deferred · design

2 · Gaps & confirms

Change 1 — Rank → UserInfo blocking — the "Welcome Captain Johnson" greeting; no rank field today.
Change 2 — Description → MenuItem minor — for the richer text-tile variant.
Change 3 — Favorites cross-control — hearts shown on Home (D31, 2026-06-26); the capability is dedicated-consumed by the Favorites screens. Backend Change 3 (Favorites API) still pending.
Confirm: the Emergency Hotline identifying value (e.g. SpecialCode) on its MenuItem.
Resolved: feed section configuration is content-driven (Scope / Category / Grouping) — no separate config endpoint.

3 · Build status (not analysis)

The Home data-gap analysis is complete. Remaining items are presentation/scaffold build tasks, tracked separately:

done Pilot Card · Document Hero (built in the aligned Blazor Home).
to build Home Feed Carousel · Resource Tile (CardSmall) · Emergency Hotline binding · section headers — documented as domain controls; code build pending the architecture delivery.

4 · Summary

Mapped: Pilot Card · card-lg (DocumentItem) · card-sm (MenuItem) · Emergency (MenuItem) · feed config.
Backend gaps: the 3 Required API Changes — Rank, Description, Favorites (all in backend §5).
Deferred: card-lg yellow accent (design). Confirm: Emergency SpecialCode value.

Full detail: backend-api-mapping-report.html §1–7. Tracked in screen-mapping.html.