Architecture

How it fits together

One picture of the whole chain: the systems the data comes from, the platform that owns it, the services that serve it, and the package that puts it on your page. Read it top to bottom — the data flows the same way.

Layer by layer

The same chain as four layers, foundation first. You only ever touch the last two.

Go deeper

The platform and the framework document themselves; these are the pages the elements lean on.

Sync AgentPipelines that move data in. A run counts only when every step completed; retries, batch-level errors and logging are built in.Core platformSQL per service; Cosmos DB and DuckDB / Parquet as the shared read layer. Rastgo watches freshness and correctness.Lookup ServicesRead-only lookups with the platform’s rules applied — eligibility, warranty, recalls. Serverless HTTPS APIs.Dealer websiteservice booking, part searchDistributor portalwarranty desk, dealer networkShowroom & service kioska plate, a screen, a resultAny page you already haveno build step, no frameworkShift FrameworkShiftEntity, ShiftIdentity and TypeAuth — entities, identity and type-safe authorization, shared by every Shift product.ADP servicesLookup, synchronisation and domain models built on that foundation. They own the data and the rules.adp-web-componentsThis package. Custom elements that call those services and render what comes back.Your siteA module tag and an element.ADP documentationThe platform behind the lookups — vehicles, parts, services, warranty, the Sync Agent and Rastgo.Shift FrameworkThe foundation ADP stands on: entities, identity and type-safe authorization.Vehicle lookup resultThe response shape every vehicle element renders, field by field.Part lookup resultThe response shape the part elements render.