Skip to content

someli-mono-repo

This is the documentation subtree for Someli-ai/someli-mono-repo, an aggregated read-only snapshot of the canonical someli-api (under backend/) and someli-platform (under frontend/) repos.

Component summary
Component name someli-mono-repo
Purpose Snapshot tree that combines the main app backend + frontend into one git repo, for tooling / wider-scope search / archival
Tech stack (mirrors the upstream — see someli-api/architecture-overview.md and someli-platform/02-architecture.md)
Source of truth No — this is a snapshot; the source of truth is someli-api and someli-platform
Audit version 0.1
Last verified 2026-05-17

Index

The "full" audit subtree is intentionally not reproduced here. Every concern that would normally have its own doc (architecture, security, deployment, …) is already covered for the canonical repos and applies verbatim. If you find yourself wanting to write architecture documentation here, that's a signal you should be editing the canonical repo instead.

Quick facts

  • Last commit at audit time: becd0c85 "Merge branch 'be-main'", 2026-01-20
  • Two branches merged: be-main and fe-main (apparently a manual merge of the backend and frontend snapshots into a single tree)
  • Structure:
  • backend/ — copy of someli-api as of around early 2026
  • frontend/ — copy of someli-platform as of around early 2026
  • README.md — one line: "# Someli Mono Repo"
  • No CI configured here; deploy pipelines all live in the canonical repos.
  • The frontend snapshot is heavily stale: 333 files diverge from the canonical someli-platform. See overlap-with-canonical.md.
  • The backend snapshot is moderately stale: 49 files diverge from the canonical someli-api.

When you would touch this repo

You should not edit code here. Legitimate reasons to come here are:

  1. Reading: You need a single grep target across both backend and frontend (less awkward than two repos open).
  2. Re-syncing: Someone has been asked to refresh the snapshot. The process is: clear backend/ and frontend/, copy from canonical, commit. There is no automated sync.
  3. Archival reference: You need to know what the platform looked like at a past date and the snapshot's commit date matches.

If you find a bug here, fix it in the canonical repo (someli-api or someli-platform) and let the snapshot decay until someone re-syncs it.