Skip to content

Architecture Decision Records

Short records of the significant technical choices in this repository.

Unlike a reconstructed history, most of these records were written with the change they describe — the reasoning is first-hand. Where a decision inherits from the Karat (AIM GOLD) repository's proven setup, the record says so.

# Decision Status
0001 Record architecture decisions accepted
0002 Restore the Go backend from git history accepted
0003 Keep the fantasy modules and MongoDB superseded by 0010
0004 Single-VPS Docker Compose + Caddy edge accepted
0005 GitHub Actions → GHCR → pull-based deploy accepted
0006 Next.js admin portal against the existing admin API accepted
0007 Grafana LGTM monitoring with provisioned alerts accepted
0008 aimstoreorg.com as the production domain accepted
0009 Secrets hygiene: server-side generation, names-only in git accepted
0010 Remove the gaming/fantasy and affiliate domains accepted
0011 Retire the gaming-era wallet currencies accepted
0012 Referral attribution (no rewards) and email verification accepted
0013 Multiple images per product accepted
0014 Razorpay credential incident closure accepted
0016 Customer support desk: Help Centre, ticket lifecycle, SLA, grievances and the email outbox accepted, amended by 0018
0017 Affiliates: admin-issued referral codes, synced to PANGALI accepted
0018 Support portal and the Support role accepted
0019 Automatic internal GST sales invoices accepted
0020 Product GST/HSN classification and beginner-friendly tax setup accepted
0021 Internal sample invoice preview (read-only, watermarked; issuance unchanged) proposed
0022 Automatic GST invoice issuance: stored documents, controlled operation, historical-order controls proposed
0023 Super Admin has full application access: one central role policy, the series manager, nothing bypassed proposed
0024 Scalable automatic GST invoice numbering (several series, automatic rollover, finite documented capacity), verified tax rates, recorded GST decisions, readiness by class proposed
0025 A verified person (a mobile number proven by its holder) behind every two-person rule: backfill approver ≠ runner, tax maker ≠ checker and checker ≠ verifier, fail closed, audited refusals (GitHub issue #103) proposed
0026 Product HSN/GST: one authorized, verified person enters, checks and approves (supersedes the tax maker/checker of 0025 and the separate verification step of 0024); the historical-backfill rule is unchanged (GitHub issue #103) proposed
0027 KARAT 24 customer KYC: a provider-ready, server-side gate (shared Gold/Silver profile, masked data only, no Aadhaar, signed idempotent webhooks, audited read-only staff view) with trading still off accepted
0028 Paid but out of stock: credit the verified captured amount to the existing Shopping Credit exactly once (no automatic gateway refund), durable two-step recovery, read-only staff view accepted
0029 Accounts and Support portal improvements: location, bill verification, supplier statements, full-set reports, activity fix - and what was deliberately not invented (bank balances) accepted
0030 Size-wise stock: per-size inventory for sized products, derived parent total, same-size restock, SIZE_REQUIRED for old apps accepted
0031 Warehouse order queue, courier/AWB details and the 4 × 6 shipping label in the Accounts Portal: derived queue, one shipment table, manage_warehouse permission, what was not invented (SKU, return address, courier APIs) accepted
0032 Accounts Portal record lists open on All Time; period reports keep their period; per-route date scope, Reset, explicit choices win accepted
0033 Server-side pagination for portal record lists: shared architecture (unbounded All Time, DataTable server mode, DB summary, bounded exports) + Orders migrated; remaining modules listed accepted
0034 Product families: admin-assigned same-design colour options (no automatic grouping, independent colour products), the in-app Available Colors picker, and a deterministic mixed default feed accepted
0035 Admin is the highest role the Support scope needs: Admin approves/activates/deletes support content and edits system templates in place; Super Admin gates outside Support are untouched accepted