Engineering overview

How E-FACTS ships software across website, iOS, backend, and this internal docs site. Skim the top for executives; use the linked pages for implementers.

UI look-and-feel: always defer to Design language. Product intent: Product.

Repo map

Cross-repo architecture questions: query Graphify (~/.graphify/global-graph.json) with tags such as efacts_inc_2026, efacts_v1, efacts_backend, efacts_iosapp, efacts_website. See Agent tooling.

System at a glance

flowchart TB
  subgraph clients [Clients]
    iOS[iOS app]
    Web[Marketing website]
    Docs[Internal docs]
  end
  subgraph api [Backend]
    Fastify[Shopper / retail APIs]
    PG[(PostgreSQL)]
    Redis[(Redis / BullMQ)]
  end
  iOS --> Fastify
  Web --> Fastify
  Docs -.->|docs auth gate only| Docs
  Fastify --> PG
  Fastify --> Redis

In this section

Related

• Product
• Design language
• Repo README.md — env table and Design Language URL map