View models
The typed shapes loaders and hooks return. These are deliberately not database rows — they are a stable surface the platform maintains across schema changes.
Generated from the SDK’s type definitions. Fields shown are the top-level ones.
the prop contracts for THEME-AUTHORED account-area page bodies (login, account, orders, order detail, subscriptions, addresses).
one entry from the customers.addresses JSONB array.
the resolved customer identity.
the merchant's brand-side customization (the platform-mandated floor per MECSTO_THEME_CONTRACT §3.2).
taxonomy used to group listings.
input to `useCheckoutInit`.
generic content entries (rich HTML pages, articles).
Content view-models — the canonical shapes the sites-* content endpoints emit (MECSTO_SITES_PUBLIC_VIEW_MODELS.md §3.5–3.15).
the signed-in customer's view-model.
the shape of a manifest-declared editable field, plus the resolved value type used at render time.
a sellable item (bookable service, digital product, or project).
the customer's balance for the tenant's program.
the resolved business-concept SINGLETONS a renderer composes (mec/mbrain/ARCH_MERCHANT_MODEL_V1.md v3).
customer-facing receipt view.
preview of a discount applied to a base amount.
the tenant's full public view.
customer's recurring purchase view.
a person on the merchant's team.
minimal identity record for the resolved tenant.
the shape of a resolved TokenSet themes consume at render time.