Repository map

Three repositories, one purpose each (ADR-0007). Open a folder to see what lives in it; every entry links to the file or directory on GitHub.

Algorythmos-AI/sggs-platform — the API and the web — serves exactly the database dataset.lock.json pins

• open Algorythmos-AI/sggs-platform on GitHub

• dataset.lock.json — the sggs-data commit + database sha256/size this platform serves
• webapp/ — the stdlib server and the API

  • open webapp/ on GitHub

  • webapp/serve.py — composition root: build identity, the ROUTES table, the HTTP layer, startup
  • webapp/sggs/ — the five bounded contexts: core, search, reader, verification, insights, knowledge
  • webapp/verify.py — the quotation-verification engine
  • webapp/romannorm.py — the query-time Roman fold (byte-identical to the index-time fold)
  • webapp/static/ — the prebuilt website the server serves
  • webapp/tests/ — server, contract and repo-gate tests
• frontend/ — the website's Astro source (built into webapp/static/)

  • open frontend/ on GitHub

  • frontend/vercel.json — the gateway rewrites, generated by tools/gen_gateway.py
  • frontend/public/contributors.json — the public-domain chronology of the Granth's contributors (vendored by the app)
• contract/ — the golden contract: recorded outputs of the engines plus openapi.json; vendored by the app
• gateway/routes.json — per environment, where /api traffic goes; frontend/vercel.json is generated from it
• tools/ — generators, harnesses and gates

  • open tools/ on GitHub

  • tools/gen_golden_vectors.py — records the golden contract from the real functions
  • tools/gen_openapi.py — contract/openapi.json from the route declarations and real responses
  • tools/gen_gateway.py — frontend/vercel.json from serve.ROUTES and gateway/routes.json
  • tools/gen_route_table.py — docs/api/routes.md from the dispatcher and the OpenAPI declarations
  • tools/contract_http.py — replays the golden contract over HTTP against any running API
  • tools/roundtrip_harness.py — search recall: every line's own transliteration
  • tools/casual_quote_harness.py — search recall: casualised fragments of real lines
  • tools/chaos_harness.py — search recall: adversarial attack files against a running server
  • tools/docs_check.py — the wiki's gate: frontmatter, links, widgets, palette, scripture rule, posters, stamps, drift
  • tools/fetch_sibling_docs.py — installs the sibling repositories' docs at their pinned commits
  • tools/data_canary.py — production serves the pinned scripture byte for byte
  • tools/perf_baseline.py — p50/p95 per context against one origin; the +10 % gate for the service split
  • tools/slice_db.py — a service's database slice from the pinned one, proven equal in content
  • tools/build_api_functions.py — the per-context API functions deployed inside the web project
• scripts/ — ci, release, ops and data tooling

  • open scripts/ on GitHub

  • scripts/data/fetch_dataset.py — installs db/sggs.sqlite from the pin, sha256-verified, atomically
  • scripts/ci/ — what the workflows call: wait for checks, smoke deploys, verify functions
  • scripts/release/ — bump the unified version, preflight a release, prove a release complete
  • scripts/ops/verify_prod.py — prove what production serves by commit identity
  • scripts/gh/apply_rulesets.sh — apply .github/rulesets/*.json to the repository
• docs/ — this wiki's pages (PR-reviewed Markdown; rendered by docs-site/)
• docs-site/ — the Astro Starlight site over docs/: plugins, widgets, posters, gates, e2e
• .github/workflows/ — every CI workflow — the CI gates map
• .github/rulesets/ — the branch protection as code
• qa/chaos/ — adversarial search inputs for the chaos harness
• Makefile — every developer and CI entry point: make help

Algorythmos-AI/sggs-data — the scripture: corpus, database, rebuild pipeline, gates, editorial ledger, evidence

• open Algorythmos-AI/sggs-data on GitHub

• corpus/sggs.jsonl — 60,658 verbatim line records, proven character for character against the PDF
• db/sggs.sqlite — the published database (Git LFS), by commit and sha256
• pipeline/ — PDF → corpus → database, every stage gated

  • open pipeline/ on GitHub

  • pipeline/rebuild_all.sh — the one-command reproducible rebuild
  • pipeline/build_corpus.py — extraction: page content, fix_text, segmentation, headers, post-passes
  • pipeline/sggs_pipeline.py — fix_text, transliteration, roman_norm, segment_units, detect_header
  • pipeline/reconcile.py — the corpus equals the PDF's text stream, character for character
  • pipeline/golden_test.py — nine groups of canonical structural checks
  • pipeline/build_db.py — the SQLite tables and the FTS5 index
  • pipeline/build_ios_db.py — the iOS database pair, two profiles (vendored by the app)
  • pipeline/ledger_check.py — code == the editorial ledger; a scripture change needs an entry
  • pipeline/verify_regroup.py — only comp_id and line_no may change between databases
• audit/ — the evidence: editorial ledger, dataset fingerprint, data-quality and scripture baselines
• docs/ — the data repository's docs (pinned and published on this wiki under /data/)
• Answer-Protocol.md — how Gurbani questions are answered from this knowledge base

Algorythmos-AI/gurbani-soul-ios — the app: SwiftUI, widgets, the bundled database pair, TestFlight and App Store tooling

• open Algorythmos-AI/gurbani-soul-ios on GitHub

• vendor.lock.json — the platform contract and the database builder, pinned by commit and sha256 per file
• dataset.lock.json — the same sggs-data pin as the platform
• ios/App/ — the app target (project.yml → XcodeGen)

  • open ios/App/ on GitHub

  • ios/App/Sources/Data/LaunchIntegrity.swift — the fail-closed launch check against the manifest
  • ios/App/Sources/Persistence/SavedLine.swift — the bookmarks store and its versioned schema
• ios/Packages/GurbaniSearchKit/ — the Swift ports of search, verify, reader, timing, banis, insights — and their parity tests
• ios/tools/testflight_archive.sh — the only sanctioned way to build a TestFlight or App Store candidate
• ios/testflight-builds.json — the ledger of every upload
• scripts/vendor_sync.py — re-vendor the contract or the database builder at a pinned commit
• docs/ — the app's docs (pinned and published on this wiki under /ios/)

On the rendered wiki this is an expandable map; on GitHub, the same map is docs/reference/repo-map.json, one line per path, checked by tools/gen_repo_map.py --check so that no listed path can go missing.

How to read it

• sggs-platform is this repository: the API and the website, and the wiki you are reading.
• sggs-data owns the scripture: nothing here writes it; it arrives by pin.
• gurbani-soul-ios owns the app: it vendors this repository’s contract at a release tag.

When a newcomer asks “what is this file?”, the answer belongs in the map. Add the path with a one-line purpose; the check refuses a path that does not exist.