Graphē

The Bible as a queryable text.

What Graphē is

Graphē treats the Bible as a queryable text: an ordered sequence of verses, with the Hebrew, Greek and translations laid over it as layers, and lexical, grammatical and cross-reference graphs laid over those. A query is a pipeline of set operations over spans of that text — every command to love in Paul’s letters, every psalm the New Testament quotes, every English word the YLT uses for agapē — expressed in a few lines, reproducible by anyone with the same link. The engine is open source and runs entirely in the browser; the workspace is a document of queries you keep, extend and share.

Why it exists

Existing Bible software answers the questions its designers anticipated. You can search for a phrase, follow a cross-reference, or click a Strong’s number. You cannot ask which words a translation renders inconsistently, whether Hebrews quotes the Greek Old Testament or the Hebrew, or what vocabulary John uses that the synoptic gospels never do — even though the data to answer all three is openly published.

Graphē exposes that data through a small notation built on one idea: a passage is a set of spans, and operators take passages and return passages. Set algebra handles the canon (Gospels except John). Lemma and morphology predicates handle the original languages (words where strong = G25 and morph.mood = imperative). Proximity patterns handle Greek word order. Alignment crosses between languages, edge queries walk cross-references and quotations, and aggregations turn any of it into a table. Definitions accumulate, so a user’s own vocabulary is indistinguishable from the built-in one.

The engine is written in Go, licensed Apache-2.0, and compiles to WebAssembly, so the hosted workspace runs every query locally in the tab — no accounts, no server round-trips, and a shared link reproduces the same result on anyone’s machine. It is built for the student of the languages and the researcher who treat the text as a dataset, and it ships a standard library so that a preacher can use the same engine without learning the notation.

Find your tier

Concepts

The spine, layers, morphemes, lemma, Strong’s numbers, morphology, case and versification — the vocabulary the rest of the docs assume.

Tutorial

The benchmark questions, phase by phase, from a first passage query to cross-reference and alignment queries.

Language reference

The grammar, types, operators and error catalogue for writing core .gq queries directly.

Standard library

The shipped vocabulary — commands(to:, in:), renderings(of:, in:) and the rest — for a preacher or teacher who wants the library tier.

Data and licences

Which datasets the engine ships, their licences and how attribution works.

Architecture

How the engine is laid out, the bundle format and how to contribute.