Appearance
Architecture — start here
The decision records, the current-state index, the platform model and the cross-cutting designs. Start at Current architecture state and read its "Maintained" date before trusting it — it is the one index of what is decided, built and open, and it goes stale like every other page.
Read before changing anything architectural or cross-cutting
- Current architecture state (read the date, then diff it against
git log) · - Operating rules (R-00 … R-07 in full) · 3. the relevant ADR in ADR index — most are 🟡 Proposed; only 0002, 0003, 0006, 0008, 0011, 0012, 0014, 0015, 0016 and 0019 are Accepted, and ADR-0018 is cited by code but has no file · 4. Data access ·
- Platform model · 6. Architecture change protocol for any change to a core entity (
check:arch-proposal). Your plan must answer: which ADR governs, whether it is Accepted or Proposed, and which of the four customer types (consumer · solo SMB · dealership · enterprise) the change was assessed for.
Pages
- Admin Portal — backend readiness assessment (measured against Dev)
- ADR-0001 · Tenancy & identity model
- ADR-0002 · Subscription & billing system of record
- ADR-0003 · Template system scalability
- ADR-0004 · Advertising & sponsored placements platform scope
- ADR-0005 · Affiliate, referral & growth rewards program
- ADR-0006 · RBAC & authorization model
- ADR-0007 · Feature entitlements & subscription gating
- ADR-0008 · Email & notifications (ZeptoMail + Zoho Campaigns)
- ADR-0009 · Business-vertical archetype platform (metadata-driven verticals)
- ADR-0010 · Analytics & reporting data architecture (the command-center read model)
- ADR-0011 · Frontend platform architecture (surface-matched: web-DOM + universal RN)
- ADR-0012 · Monorepo structure, package boundaries & documentation standard
- ADR-0014 · Public data exposure & least-privilege grants
- ADR-0015 · Design governance & drift reconciliation
- ADR-0016 · Reminders domain model
- ADR-0017 · Cross-platform parity automation
- ADR-0019 · Setu Card rendering, preview, versioning & switching
- ADR-0020 · Platform schema, redesigned from first principles
- ADR-0021 · Feature entitlement & control plane
- ADR-0022 · Organization resource sharing
- ADR-0023 · Organization hierarchy, locations & seat licensing
- ADR-0024 · Enterprise operating model: divisions, oversight & assets
- ADR-0025 · Campaigns, offers & the targeting primitive
- ADR-0026 · Vendor verification & governance
- ADR-0027 · Card freshness: purge-on-write, never TTL
- ADR-0028 — URL namespace and audience routing on one origin
- ADR-0029 · WhatsApp communication platform via Meta Cloud API, direct
- ADR-0030 · Tenant communication identity & credit monetization
- ADR-0031 · Domain schemas for bounded contexts
- ADR-0032 · Chat and platform identity
- Architecture Decision Records
- Architecture change protocol
- Backend / Edge Functions
- Business-domain coverage: what QRSETU can and cannot absorb
- Core platform capability vs industry-specific capability
- Current architecture state — the single index
- Data Access Strategy
- QRSETU platform data architecture
- Database & RLS
- Frontend Architecture
- High-Level Design (HLD)
- Declare EVERY core entity the body discusses. P7 cross-checks the prose against this list, because a
- chat: a conversation is between PRINCIPALS
- Employee Setu Card: linking a card to a member, not only a workspace
- feature_grants: add an exactly-one-scope XOR CHECK (QRS-1018)
- Platform operator control plane
- Architecture assessment: 10M users, N industries
- Security Architecture
- Tier system
- User lifecycle: deactivation, attribution and erasure