Skip to content

Reference

Glossary

9 min readUpdated

Page actions

ChatGPT and Claude are third-party services. The link gives them this page's public address and a short instruction. This site records nothing.

Definitions of the scripture, Gurmukhi and engineering terms used across the wiki — from Ang, Rahao and Vaar to comp_id, the dataset pin and golden vectors — each linkable and shown as a hover-card.

Wherever a page writes [[Term]], the site shows the definition below in a hover-card and links here; the build fails on a term that is not in this table. Scripture terms are explained for engineers and students new to the tradition; where the scholar review of those pages is still pending the page that uses the term says so. Cite the scripture itself, never this table.

The scripture

TermMeaning
Sri Guru Granth Sahib JiThe scripture and eternal Guru of the Sikhs: 1,430 Angs of hymns by six Gurus, fifteen Bhagats, eleven Bhatts and three others, compiled in one edition whose text this project serves verbatim. Always named in full, always cited by Ang.
Granth“Book”; short for the scripture in prose, never in a citation.
AngA page of Sri Guru Granth Sahib Ji (1–1430). The unit of every citation: “Sri Guru Granth Sahib Ji · Ang N”.
BirA physical volume/edition of the Granth; the source PDF is one Bir, and the corpus reproduces its text character for character.
EditionA printed lineage of the Bir. Editions differ in spacing, bindi/tippi and ligature conventions; the project records this edition and notes differences instead of “correcting” them.
GurbaniThe Gurus’ word — the text of the scripture. “Gurbani Soul” names the app; Gurbani names the text.
BaniA composition or a named body of hymns (Japji Sahib, Rehras Sahib…). In the app, a bani is a registry of pointers into the verbatim corpus.
ShabadA hymn/composition; in the database a comp_id groups its lines, heading run included.
RahaoThe refrain/pause line of a shabad, marked ਰਹਾਉ (is_rahao=1); the line the rest of the shabad turns around.
Salok / PauriA couplet-style verse / a stanza; the two alternating unit kinds of a Vaar.
VaarA balladic composition of pauris with interleaved saloks; 22 in the Granth. Its pauris take the Vaar’s author even where the saloks carry other Gurus’ ਮਃ headers.
AshtapadiAn eight-stanza composition (Sukhmani Sahib is twenty-four of them).
ChhantA lyrical, longer-lined composition form found in several raags.
Swaiyya / SwaiyyeThe praise-verses of the Bhatts (Angs 1389–1409), one set for each of the first five Gurus.
SahaskritiThe Sanskritised saloks (Angs 1353–1360) whose spelling uses clusters such as the subjoined ya; the source font’s handling of them is why several editorial rules exist.
Mool MantarThe opening statement of the Granth (Ang 1), from ੴ to ਗੁਰ ਪ੍ਰਸਾਦਿ; the Mool Mantar folds into Japji’s comp_id 2.
JapjiJapji Sahib, the first bani (Angs 1–8, 385 lines); its lines have author = null because the print carries no ਮਹਲਾ line.
So Dar / So Purakh / SohilaThe three short sections after Japji (Angs 8–13) that, with it, open the Granth before the raags begin at Ang 14.
RaagThe musical mode a section is set in; 31 raags order Angs 14–1353. A raag’s span is the longest run of Angs where it is the majority.
GharThe musical “house”/beat of a composition (ਘਰੁ), read from the heading.
Mahallaਮਹਲਾ / ਮਃ N in a heading: “the Nth Guru” as author (M1 Guru Nanak Dev Ji … M9 Guru Tegh Bahadur Ji).
GuruOne of the ten Sikh Gurus; six wrote hymns in the Granth (M1–M5 and M9). In the app’s text, “Guru” is also a search honorific that the waterfall drops when retrying.
BhagatA saint-poet whose hymns are in the Granth — Kabir Ji, Namdev Ji, Ravidas Ji, Sheikh Farid Ji and others; fifteen in all.
BhattOne of the eleven bards whose Swaiyye praise the Gurus (Angs 1389–1409); attributed per Bhatt from signature evidence.
MundavaniThe closing seal of the Granth (Ang 1429), followed by a final salok and Raagmala.
RaagmalaThe index of raags that closes the Granth (Angs 1429–1430).
Hukam / HukamnamaA composition taken as the day’s reading; the API’s /api/random returns one complete unit for it. In the hymns, ਹੁਕਮੁ is also the divine Will.
NitnemThe daily prayers; in the app a set of banis ordered by time band, with a Nitnem day that rolls at 03:00.
GutkaA small prayer book; the app’s Nitnem screen plays that role.
RehrasThe evening prayer; the app carries the SGPC form by default and the Taksal form as a variant.
Sri Dasam GranthThe scripture associated with Guru Gobind Singh Ji; three Nitnem banis come from it and live in the app’s separate, labelled extra_lines layer, never in lines.
ArdaasThe Sikh prayer of supplication; in the app it is non-SGGS text in the labelled layer.
GranthiThe reader and custodian of the scripture; the reviewer role in this project — reviews flagged text, never edits it.
SangatThe congregation; in the hymns ਸੰਗਤਿ is the company of the holy. The project’s readers.
Amrit VelaThe early morning hours (in the app, 03:00–09:00), the first Nitnem time band.
PaharA three-hour watch of the day; the app’s raag clock places raag-timing claims on the pahar cycle.
NaamThe Name — the divine presence remembered in the hymns; the most frequent theme in the concept index.
HaumaiEgo, self-centredness; a theme in the concept index and one of the vices the hymns name.
WaheguruThe name of God most used by Sikhs; in Roman search the classic case for the fold (waheguru, vaahiguroo → vhgr).

Gurmukhi and Unicode

TermMeaning
GurmukhiThe script of the Granth (Unicode block U+0A00–U+0A7F). Every stored line is Gurmukhi; Roman letters are only ever a reading aid.
MatraA vowel sign attached to a consonant (ਾ ਿ ੀ ੁ ੂ ੇ ੈ ੋ ੌ). The skeleton column strips them.
SihariThe short-i sign ਿ, written before its consonant in print but stored after it in logical Unicode — the reordering the pipeline performs.
HalantThe virama ੍ that joins a consonant to the next as a subjoined letter (pairin).
Addha-yayyaThe subjoined ya ੍ਯ; the source font doubles it in Sahaskriti words, and the saroop display draws the pair as the yakash ੵ under the letter, as the Bir prints it, without touching the stored text.
Tippi / BindiThe two nasal signs ੰ and ਂ; editions differ in which they print, so the project keeps this edition’s choice.
NuktaThe dot ਼ under a consonant for borrowed sounds; kept verbatim wherever the Bir prints it.
DandaThe line divider: the double danda ॥ ends a line or unit and carries the numerals (॥੧॥); the single danda । is rare. The pipeline cuts units on ॥.
ੴIk Onkar — the invocation opening compositions and the Granth (U+0A74); restored by the pipeline from the font’s two-glyph form.
Sant LipiThe open-licence Gurmukhi font (SIL OFL) the site and the app bundle so the Granth renders the same everywhere.
SaroopThe traditional printed rendering of the Granth; also the app’s display toggle that draws the doubled ya as the printed yakash ੵ in rendered glyphs only — the stored text stays verbatim.
NFCUnicode’s canonical composition; the pipeline and the verifier normalise to it before comparing.
TransliterationThe Roman spelling of a Gurmukhi line (translit), a reading aid built by the pipeline — never scripture, never cited.

The data

TermMeaning
Corpuscorpus/sggs.jsonl in sggs-data: 60,658 verbatim line records, proven character for character against the PDF.
Line recordOne display line of the Granth as a row of the lines table, with its placement, heading metadata, text forms and search forms.
comp_idThe id grouping all lines of one composition (heading run + body); vacated ids are permanent gaps. See the database schema (sggs-data).
Heading runConsecutive heading lines (a title, the invocation, a label) that open a composition and share its comp_id.
SkeletonA line with its vowel signs stripped, for the typo-tolerant tiers.
First lettersThe first letter of each word (fl_g, fl_r), the form seekers use to find a line they half-remember.
FTS5SQLite’s full-text index; the fts table over six search columns, ranked by bm25.
Reconcilereconcile.py: the proof that the corpus equals the PDF’s text stream, character for character; the rebuild aborts on one difference.
Golden suitegolden_test.py: nine groups of canonical structural checks every rebuild must pass.
Editorial ledgersggs-data’s register of every transform the pipeline applies to the text: 4 reviewed editorial rules, 11 applications, enforced by ledger_check.py.
FingerprintThe per-table content hash of the published database (audit/dataset-fingerprint.json), compared in CI.
Dataset pindataset.lock.json: the sggs-data commit and the database’s sha256 and size this platform (and the app) serve.
Data canaryThe scheduled check that production serves the pinned scripture byte for byte.

The engines and the platform

TermMeaning
WaterfallThe order /api/search tries its tiers: exact and cheap first, fuzzier only when nothing was found.
TierOne stage of the waterfall, reported as the response’s mode.
roman_normThe phonetic fold that makes Roman search spelling-tolerant; byte-identical in three places (index, query, the Swift port).
Seeker lexiconA curated table of words seekers actually type, mapped to a transliteration term or a theme.
Variant indexThe precomputed romanisation-variant table the waterfall’s seventh tier uses.
Verification/api/verify: is this quotation really in the Granth? A verdict ladder from VERIFIED_EXACT to NOT_FOUND.
VerdictThe verification engine’s answer: VERIFIED_EXACT, VERIFIED_PARTIAL, VERIFIED, PROBABLE, AMBIGUOUS or NOT_FOUND, with an optional Ang tag.
Golden vectorscontract/*.ndjson — recorded outputs that pin the Swift port to the Python source of truth and every deploy to the code.
Golden contractThe golden vectors plus openapi.json: the API’s behaviour and shape, regenerated from real runs and enforced everywhere.
Bounded contextOne of the five parts of the API — reader, search, verify, insights, knowledge — each declaring the tables it reads.
GatewayThe generated rewrite rules that send each /api prefix to the service that owns it (gateway/routes.json → vercel.json).
X-ServiceThe response header naming the service that answered: all for the single API, else the contexts it runs.
Request idX-Request-Id: one id on every response and in the access log, so a request can be followed from the edge to the service.
Cacheable routeA route whose response depends only on the immutable database; served with a public cache policy and an ETag.
One version numberWeb, API and the App Store binary always report the same X.Y.Z from the same platform commit.
Vendor syncHow the app takes a platform release: the contract copied at the tag and recorded in vendor.lock.json with a sha256 per file.
Ledger (iOS)ios/testflight-builds.json: every upload with its version, build, commits, profile, channel and database hash.
Launch integrityThe app’s fail-closed check that its bundled database hashes to the certified manifest before any scripture is shown.
PosterOne of the wiki’s large step-through diagrams, generated from a declarative spec and pinned to the code it describes.
WalkthroughThe site’s step-by-step reader for a poster: Next, Prev, Play, a caption and a link per step, a full-size lightbox.
Verified stampA page’s verified: {commit, date}: the commit it was last read against; the docs gate requires it on process, engineering and architecture pages.
Scholar reviewA Granthi or Gurbani scholar reads what engineers cannot judge, and signs it off: the editorial ledger’s corrections (approved 2026-09-24), the Nitnem non-SGGS text (attested 2026-09-21), the Scripture 101 explanation pages (pending; make review-pack prints them). Engineers never decide a question of the text.
Brand gates (G1–G4)The brand book’s four sign-offs for the app (§12): G1 visual (the product owner), G2 contrast (the contrast script), G3 sensitivity (a Granthi or scholar, on the ੴ treatment, the icon and the saroop), G4 legal. G3 and G4 closed on 2026-09-26 for the first App Store submission.