someli-project¶
This is the documentation subtree for Someli-ai/someli-project, an aggregated read-only snapshot of all six canonical product repos (app + designer + admin pairs).
Component summary¶
| Component name | someli-project |
| Purpose | Snapshot tree that combines all three product pairs into one git repo, for cross-product navigation / archival |
| Source of truth | No — this is a snapshot; the source of truth is the canonical repos |
| Audit version | 0.1 |
| Last verified | 2026-05-17 |
Index¶
The same rationale as someli-mono-repo applies: the audit subtrees for each canonical repo are the place to read about architecture / security / deployment / etc. This subtree exists only to call out the snapshot's status.
Structure¶
someli-project/
├── backend/
│ ├── admin-backend/ # snapshot of Someli-admin-api
│ ├── app-backend/ # snapshot of someli-api
│ └── designer-backend/ # snapshot of designer-api
├── frontend/
│ ├── admin-frontend/ # snapshot of admin_console_R
│ ├── app-frontend/ # snapshot of someli-platform
│ └── designer-frontend/ # snapshot of Someli-Designer
└── readme.md # one line: "welcome to someli"
Quick facts¶
- Last commit at audit time:
050a5546"feat(main): add admin frontend", 2026-01-23 - The git log shows the snapshot was assembled by six successive commits, each adding one of the six product copies (5 of which date to 2026-01-23, and the initial commit dating shortly before). It is a one-shot import, not a live mirror.
- No CI configured here; deploy pipelines live in the canonical repos.
Drift vs canonical¶
| Snapshot path | Mirrors | File diffs vs canonical |
|---|---|---|
backend/admin-backend/ |
Someli-admin-api/ |
0 — identical |
backend/app-backend/ |
someli-api/ |
49 (same drift as someli-mono-repo/backend) |
backend/designer-backend/ |
designer-api/ |
6 |
frontend/admin-frontend/ |
admin_console_R/ |
0 — identical |
frontend/app-frontend/ |
someli-platform/ |
333 (same drift as someli-mono-repo/frontend) |
frontend/designer-frontend/ |
Someli-Designer/ |
14 |
The admin pair and (nearly) the designer pair are well-aligned with the canonical sources. The app pair is the heavily-stale one, because the canonical app repos move faster.
See overlap-with-canonical.md for the file-by-file diff lists.