SIMS
/
sims-hq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
76 Commits
2 Branches
0 Tags
4.9 MiB
TypeScript 96.4%
CSS 3.2%
JavaScript 0.2%
 
 
 
main
feat/client-detail-redesign
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '85adbb553a'
${ noResults }
Go to file
Thomas Joise 85adbb553a docs(spec): design for splitting HQ and Store into independent projects 
Two products share one repo: HQ (internal client book, proforma billing,
call tracking) and Store (the GST retail product shipped to ~300 clients).
Different DBs, different audiences, different cadences — 60 of 75 commits
touch HQ, 2 touch Store.

Design: two repos. HQ inherits the existing history; Store starts fresh so
its history carries zero HQ bytes. Shared packages fork into each side,
trimmed to verified usage — safe because GST rates are dated DB rows, not
code, so the forked arithmetic has no reason to diverge.

Project tracking and conversion reporting are deferred: they don't exist
yet, and mixing new features into a mechanical move hides failures.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
 		5 days ago
apps wip(store-product): returns, GST returns, offline queue, security hardening + docs 1 week ago
docs docs(spec): design for splitting HQ and Store into independent projects 5 days ago
packages wip(store-product): returns, GST returns, offline queue, security hardening + docs 1 week ago
.gitignore docs(hq): go-live runbook, env template and S3 backup script 1 week ago
BUILDING.md chore: bring the full store-product codebase under version control 2 weeks ago
README.md docs: bring README index current (build state, red-team review, HQ runbook) 1 week ago
STATUS.md wip(store-product): returns, GST returns, offline queue, security hardening + docs 1 week ago
package-lock.json wip(store-product): returns, GST returns, offline queue, security hardening + docs 1 week ago
package.json chore: root typecheck now fans out to every workspace's own tsconfig 2 weeks ago
tsconfig.base.json chore: bring the full store-product codebase under version control 2 weeks ago
tsconfig.json chore: bring the full store-product codebase under version control 2 weeks ago
vitest.config.ts feat(hq): app skeleton with health endpoint (HQ-1 task 1) 2 weeks ago

README.md
Unescape Escape

SiMS Next — Store Management Suite (Rebuild)

A ground-up rebuild of SiMS Store Software: GST-compliant retail management for India — inventory, POS billing, purchases, and accounting — for everything from a single-counter kirana shop to multi-outlet supermarket chains.

Why the rebuild: the current product runs on Oracle Forms & Reports (hard to maintain, buggy, no path to cloud/multi-store), and the market is moving. Same customers, much better product.

North star: the fastest, easiest counter workflow in the market. The customer in line never waits because of the software, and purchase entry is never a burden.

Build state (start here)

This is now a working codebase, not just a plan. Current state, run instructions, and the live-vs-wireframe breakdown live in STATUS.md and BUILDING.md.

In brief: a web-app POS + back office served by a Node store-server over a portable data layer (SQLite dev slice; Oracle 12c adapter pending the Classic DDL). Live and verified end-to-end: billing (keyboard-first, offline-capable, B2B/IGST), purchases with batch/ expiry, returns/credit notes, and GST returns (GSTR-1/3B). A full adversarial security review + P0–P2 remediation is complete — see docs/18-RED-TEAM-REVIEW.md.

Planning documents

Doc What it covers
docs/00-VISION.md Product vision, segments/editions, business model, success metrics
docs/01-SCOPE.md Full module & feature catalog with priorities and edition mapping
docs/02-ARCHITECTURE.md Offline vs online vs hybrid analysis, sync design, tech stack, multi-tenancy
docs/03-FRONTEND.md App surfaces, counter UX principles, screen inventory, design system
docs/04-ROADMAP.md Phased build plan with exit criteria, pilot & migration strategy
docs/05-CHECKLIST.md Master build checklist, grouped by area
docs/06-DECISIONS.md Open decisions that need a founder call, with recommendations
docs/07-DB-AND-CONFIG.md Everything-in-DB design (messages, plans, settings), local DB engine analysis (D12)
docs/08-MARKET-ARCHITECTURES.md How Tally/Marg/GoFrugal/Vyapar & global players architect; Android POS conclusion
docs/09-UX-FLOWS-AND-MENUS.md Screen-level UX blueprint: POS flows, back-office menu tree, Purchase Inbox, owner app
docs/10-ISSUES-REGISTER.md Consolidated failure-mode register across 6 lenses, with Top-10 risk ranking
docs/11-ADMIN-SUPPORT-CONSOLE.md Settings hierarchy, tenant Admin review, and the vendor-side HQ/support console
docs/13-SPEC-*.md Keystroke-level specs: billing polish + purchase entry (P1/P2 backlog)
docs/14-SPEC-HQ-CONSOLE.md HQ ops console for the Classic client base (D15, apps/hq)
docs/15-EDITIONS.md Lite/Standard/Pro/Enterprise: privileges, limits, costs — all configurable DB rows
docs/16-PROJECT-RULES.md The 26 hard rules (Tables Rule, money rules, config-over-code, counter rules)
docs/17-SCALE-AND-INTEGRATIONS.md The 7 committed scale gaps + full integrations catalog with status
docs/18-RED-TEAM-REVIEW.md Adversarial security review + remediation record (all findings closed)
DEPLOY-HQ.md Go-live runbook for the HQ ops console (apps/hq)

Start with STATUS.md for what's built; then 00-VISION, 02-ARCHITECTURE, 04-ROADMAP for the plan.