root
2.4 KiB
RentalDriveGo Decision Log v13.0
Date: 2026-06-25
Scope: Phase 13 multilingual homepage assembly
D13-001: Assemble rather than fork the component system
Status: Accepted.
The homepage is composed from Phase 12 components and semantic layout primitives. No duplicate button, card, accordion, preview, workflow, comparison, or CTA family was introduced.
D13-002: Keep route content typed and locale-owned
Status: Accepted.
A typed HomepageContent model transforms complete EN, FR, and AR catalog messages into stable route-level content objects. Presentation code does not index translation arrays directly.
D13-003: Treat unavailable destinations as product state
Status: Accepted.
Demo, product-tour, pricing, and sales actions remain non-navigable with localized disabled reasons. No empty hash, root fallback, guessed URL, CRM call, or fake submission was added.
D13-004: Publish measurement definitions, not fictional results
Status: Accepted.
The results section explains KPI definitions and evidence methodology without numeric claims. Customer evidence, testimonials, logos, certifications, SLAs, and partner names remain suppressed.
D13-005: Use an illustrative operational preview
Status: Accepted.
The hero uses the Phase 12 ProductPreview with deterministic fictional rows from localized catalogs. It is explicitly captioned as illustrative and does not impersonate an approved product capture.
D13-006: Preserve document-level RTL and identifier isolation
Status: Accepted.
Arabic uses the existing document-level RTL shell. Layout CSS uses logical declarations, while vehicle identifiers remain isolated left-to-right through BidiText. Media and brand elements are not globally mirrored.
D13-007: Make section anchors real
Status: Accepted.
The existing header and footer hashes now resolve to implemented product, workflow, modules, pricing, and faq sections. Locale routing continues through the approved route helper.
D13-008: Record environment limits without converting them into acceptance
Status: Accepted.
Static validation, formatting, lint, strict type checking, unit coverage, production build, and direct HTTP locale responses are recorded as executed. Chromium loopback navigation remains administrator-blocked, so browser, axe, visual, keyboard, touch, screen-reader, zoom, and forced-colors acceptance remain open.