Appearance

QRSETUInternal Developer Portal

A proactive business assistant for Indian SMBs. Two frontend stacks, one shared TypeScript core, one Supabase backend — and the guardrails that keep it enterprise-grade.

⭐ Current Architecture State
User Ecosystem
The one hard rule →

The Setu Card

Every user's universal public identity at qrsetu.com/:slug. Server-rendered DOM, edge-cached, readable with no account and no app. The platform's core differentiator, not a module.

One merchant app, three surfaces

A universal Expo/React Native codebase shipping Android native, iOS native and Web PWA together. Parity is a requirement, not a follow-up — the exception path is retired.

Industry × archetype × primitives

3 archetypes, 11 closed-set primitives, ~45 industries. The platform's cost is O(primitives), not O(industries) — a new vertical is configuration, never code.

Feature control on three axes

Applicability AND entitlement AND availability, across 8 grant scopes. Applicability is derived from primitive composition, so grants stay sparse.

RPC reads, Edge-Function writes

supabase.from() is banned in app code. Reads go through SECURITY DEFINER RPCs, writes through Edge Functions — both behind the packages/data seam.

Docs are load-bearing

deploy-prod.yml refuses a production change that is not declared in release.json. A process step that is not gated does not exist.

What this portal is ​

The single source of truth for how QRSETU is built and operated.

⭐ Start at Current Architecture State

It is the one index of what is decided, what is built, and what is open — and it exists because on 2026-08-07 a decision taken the previous day was verified to exist in five source files and to have reached no ADR and no overview page (QRS-384). Across 114 portal documents, per-page freshness is not achievable by discipline; one authoritative index plus supersession banners is. Trust that page over any other — and if a document contradicts it, report the document as stale rather than following it.

Authority, highest first (since 2026-09-23, QRS-1288): (1) the enforcement point — a migration, release.json, a parity contract, a test; (2) the portal page that a .claude/rules rule or CLAUDE.md's routing table points at; (3) the repo-root CLAUDE.md for the rule text itself (its rules are generated from Operating rules); (4) the state record and memory, as pointers. Where a page and CLAUDE.md disagree about a fact, the page is the SSOT and CLAUDE.md is the one to fix — "if it isn't documented, it isn't done."

Start here ​

  1. ⭐ Current Architecture State — decided / built / open.
  2. Platform Overview — what QRSETU is, the system map, the stack.
  3. User Ecosystem — the six user types and how each maps to real tables.
  4. Data Access Strategy — the most important rule in the codebase.
  5. Tier System — two stacks, and where the code actually lives.
  6. Coding Standards — what the gates enforce.
  7. ⭐ Strategy: competitor analysis & market positioning — the commercial counterpart to step 1. Who we actually compete with, whether the differentiation is real, and what the revenue target requires. Added 2026-08-18, because until then no page in this portal named a single current competitor.

⚠ Before you follow any page in this portal ​

The platform was redesigned from first principles on 2026-08-07/08 (ADR-0020 … ADR-0025), and the database baseline is authored but not yet applied to Dev — verified 2026-08-08: public holds 0 tables. Two consequences for anyone reading:

  • Do not read a decision as a feature. Most of the architecture is designed, not built. The built-vs-designed split is maintained here.
  • Retired vocabulary appears in historical records on purpose. ADRs, the tracker and release records are logs — they legitimately mention BioLink, profiles, capabilities and subscription_tiers as things that were decided. A reference or architecture page naming them as current is a bug. The full retired-vocabulary list is in the glossary, and npm run check:docs gates it.

Status legend ​

  • [ENFORCED] — applies to all new code now; migrate existing code when you touch it.
  • [TRANSITIONAL] — current reality the program is moving away from; do not add to it.
  • 🟠 Wave 2 — designed and specified, no table and no code yet.
  • legacy/ — the retired Vite SPA. Reference only; never the current shape of anything.