crossconnect is a Bible-first platform for reading Scripture naturally while revealing the vast web of relationships that exists within the biblical canon. Its intent is not to be another Bible app with a larger collection of cross-references, but a living map of Scripture: a system where every passage can be understood not only in isolation, but within the conversations, patterns, images, words, people, events, promises, and theological trajectories that run throughout the Bible.
The Bible remains the centre of the experience. A reader opens any passage and simply reads; when they notice something interesting, they click a word, phrase, verse, person, place, event, image, or theme and begin exploring what lies behind it and where it leads. The platform's deeper purpose is to make the architecture of Scripture visible — to let a reader ask where an idea came from, what earlier passage is being echoed, how an image is developed, where a promise goes, how a word changes or deepens across Scripture, what happens to a person, event, institution, or theme later, how the New Testament reuses the Old Testament, what passages converge behind a text, what scholars actually say about a connection, and how the whole biblical story develops toward its conclusion.
The audience is serious lay readers, students, pastors, and academics: readers who want a beautiful scholarly Bible — literary, elegant, contemplative, minimal, spacious, typographically excellent, and deeply focused on the text — with complexity appearing only when they ask for it. The platform must distinguish between what the biblical text actually says, what documented data connects, what scholars argue, and what AI suggests; AI must never quietly become the authority.
crossconnect is delivered as a first-party custom web application with a backend that serves Scripture passages and relationship data. The current delivery shape is a set of cohesive, first-party destinations that together carry the accepted experience flow READ → NOTICE → CLICK → EXPLORE → COMPARE → TRACE → MAP → RETURN TO READ:
The accepted active human personas are the Scripture Reader, the Connection Explorer, the Translation and Text Comparer, and the Scholarly Evidence Reviewer. All current destinations are openly reachable; the reader's current passage and position must remain available while they explore, compare, trace, map, and return, so the application preserves reading position across the exploration lifecycle without requiring an account.
Narrow exclusions. crossconnect is not a database presented in place of a book: Scripture must be presented as a readable book rather than turning it into a database. It is not an AI dashboard, and AI-suggested content is never presented without an explicit provenance and confidence label. It does not present a force-directed node cloud on the reading surface; relationships remain typographic until the reader explicitly opens Map. It does not use a light or near-white ground, blue/indigo/violet palette, rounded cards, pill buttons, soft shadows, glassmorphism, hover-lift grids, gradient-blob heroes, 3D renders, or stock photography of people.
Delivery ownership. crossconnect is a first-party custom application. The reading surface, the relationship ledger, the evidence apparatus, the comparison columns, the trajectory timeline, and the map are all owned and rendered by the application itself. The backend supplies Scripture passages and relationship data so that reading and exploration are executable; this is supporting infrastructure, not a separate product surface.
Access ownership. All current destinations are openly reachable. The accepted journeys — reading a passage, noticing something, clicking it, exploring its relationships, comparing translations, tracing a trajectory, viewing the map, and returning to the text — do not require the reader to establish or verify an identity, and no accepted capability creates a durable obligation, entitlement, or value transfer that must remain bound to a particular participant. The reader's current passage and position are preserved as in-session reading state so that the reader can return to the Bible without losing their place; this continuity is a property of the reading experience, not an account. No account creation, sign-in, invitation, provisioning, or account-management capability is part of the current scope.
Current and future boundaries. Everything described in this document is current. No future-horizon requirements were accepted in the authoritative thread; nothing in this document is deferred, and nothing outside the accepted capabilities is implied by the product category.
Not applicable. No reference directive with a content_source authority was supplied; the authoritative material is the user-authored requirement thread and the accepted Planning Scope, whose content is carried in the requirements, personas, page coverage, and flows below.
Each requirement is a distinct story point with provenance, lifecycle facts, and observable acceptance. Provenance is explicit (source-stated), basic_default (accepted default), or required_inference (indispensable inferred mechanics).
FR-1 — Read Scripture naturally, Bible-first. As a Scripture Reader I should open any passage and simply read, with the Bible remaining the centre of the experience. Provenance: explicit. Trigger/input: the reader opens a passage. Observable result: the passage renders as readable Scripture in the reading column at the fixed 66ch measure, with the reading surface dominant. Access state: openly reachable. Failure/recovery: if relationship data cannot be resolved, the Scripture text remains fully readable. Continuation: the reader continues reading or notices something to click. Owner: Bible Reader.
FR-2 — Notice and click any element. As a Scripture Reader I should click a word, phrase, verse, person, place, event, image, or theme when I notice something interesting, and begin exploring what lies behind it and where it leads. Provenance: explicit. Trigger/input: the reader selects an element in the text. Observable result: the ochre rule draws from left to right over 260ms over the selection and the relationship ledger opens in the right columns as a hairline-ruled column. Access state: openly reachable. Failure/recovery: if the selection's relationships cannot be resolved, the ledger states that relationships are unavailable for that selection. Continuation: the reader explores the ledger or returns to reading. Owner: Bible Reader, with the ledger continuing into Connections.
FR-3 — Explore the web of relationships. As a Connection Explorer I should explore the relationships behind a selected word, phrase, verse, person, place, event, image, or theme and where they lead. Provenance: explicit. Trigger/input: a selected item. Observable result: the connected passages and their relationship types are presented. Access state: openly reachable. Failure/recovery: an item with no recorded relationships states that none are recorded and does not substitute invented connections. Continuation: the explorer moves from a phrase to its source, from its source to related passages, and onward to a larger canonical trajectory. Owner: Connections.
FR-4 — Support the full range of biblical relationship kinds. As a Connection Explorer I should see relationships of many kinds — direct quotations, Old Testament allusions, echoes, imagery, prophetic expectation, theological concepts, typology, narrative patterns, New Testament parallels, internal canonical connections, lexical relationships, people, places, events, genealogies, chronology, laws and rituals, literary structures, textual variants, manuscript relationships, and Septuagint connections. Provenance: explicit. Trigger/input: a selected item. Observable result: each connection is labeled with its relationship type. Access state: openly reachable. Failure/recovery: an unrecognized or unresolved relationship type is shown as unresolved rather than mislabeled. Continuation: the explorer filters or follows connections by type. Owner: Connections.
FR-5 — Every connection carries its full apparatus. As a Connection Explorer I should see, on every connection, its relationship type, evidence, confidence, provenance, and review status. Provenance: explicit. Trigger/input: any displayed connection. Observable result: all five attributes are present and readable on the connection. Access state: openly reachable. Failure/recovery: a connection whose evidence cannot be resolved shows an explicit unresolved-evidence state rather than being dropped or upgraded. Continuation: the explorer opens the connection's Evidence. Owner: Connections, with full detail in Evidence.
FR-6 — Distinguish text, documented data, scholarly argument, and AI suggestion. As a Scholarly Evidence Reviewer I should distinguish what the biblical text actually says, what documented data connects, what scholars argue, and what AI suggests. Provenance: explicit. Trigger/input: a connection under review. Observable result: the source class of the connection is stated explicitly. Access state: openly reachable. Failure/recovery: if a source class cannot be resolved, the connection is shown with an explicit unresolved-provenance state and is never presented as documented. Continuation: the reviewer judges the connection's standing. Owner: Evidence.
FR-7 — AI never quietly becomes the authority. As a Scholarly Evidence Reviewer I should never encounter AI-suggested content presented without an explicit provenance and confidence label. Provenance: explicit. Trigger/input: any AI-suggested connection. Observable result: the AI suggestion is labeled as AI-suggested with its confidence, and is visually distinguishable from text, documented data, and scholarly argument. Access state: openly reachable. Failure/recovery: if an AI suggestion cannot be labeled, it is not shown. Continuation: the reviewer treats it as a suggestion, not an authority. Owner: Evidence, with the label carried wherever the connection appears.
FR-8 — Strong, probable, possible, and disputed relationships are distinguishable. As a Scholarly Evidence Reviewer I should distinguish strong documented relationships from probable or possible relationships, and see disputed interpretations remain visibly disputed. Provenance: explicit. Trigger/input: a connection under review. Observable result: the confidence tier is shown, and disputed or low-confidence connections are marked in oxblood; disputes are never silently resolved. Access state: openly reachable. Failure/recovery: a connection with no resolved confidence tier is shown as unresolved rather than defaulted to strong. Continuation: the reviewer follows the dispute or returns to the text. Owner: Evidence.
FR-9 — Trace biblical ideas forward and backward. As a Connection Explorer I should trace a theme, image, promise, institution, or narrative forward and backward across the canon as a canonical trajectory. Provenance: explicit. Trigger/input: a theme, image, promise, institution, or narrative. Observable result: the trajectory renders as a horizontal timeline rule with nodes hung above and below in alternating rhythm, each node a verse reference in small caps with its confidence coded in ochre or oxblood. Access state: openly reachable. Failure/recovery: a theme with no recorded trajectory states that none is recorded rather than assembling an unsupported sequence; an unresolved node is shown as unresolved. Continuation: the explorer opens a node's passage or returns to reading. Owner: Trajectories.
FR-10 — Accepted canonical trajectories are traceable. As a Connection Explorer I should be able to follow accepted trajectories such as Eden → Tabernacle → Temple → Prophetic Temple → Christ → Church → New Jerusalem; Creation → Israel → Davidic Kingdom → Prophets → Jesus → Church → New Creation; and Egypt → Passover → Exodus → Wilderness → Sinai → Land → New Exodus → Christ → Revelation. Provenance: explicit. Trigger/input: opening one of these trajectories. Observable result: the trajectory's nodes illuminate one by one in sequence and are navigable in both directions. Access state: openly reachable. Failure/recovery: an unresolved node does not break the rest of the trajectory. Continuation: the explorer follows the trajectory to its next node or returns to reading. Owner: Trajectories.
FR-11 — Compare translations side by side without disrupting reading. As a Translation and Text Comparer I should compare multiple translations side by side with synchronized passages, without disrupting reading. Provenance: explicit. Trigger/input: opening comparison for a passage. Observable result: the reading column splits into two or three synchronized Scripture columns separated by hairlines, with the verse number pinned in the margin of each and a persistent ochre chapter mark preserving position. Access state: openly reachable. Failure/recovery: if a translation cannot be resolved, the remaining columns stay readable and the unavailable column states its unavailability. Continuation: the comparer returns to the text at the preserved position. Owner: Compare.
FR-12 — Original-language information and lexical connections. As a Translation and Text Comparer I should examine original-language information and lexical connections for a passage. Provenance: explicit. Trigger/input: a word or passage in comparison. Observable result: the Hebrew or Greek lemma is shown, with Strong's numbers set in JetBrains Mono, and lexical connections are presented. Access state: openly reachable. Failure/recovery: a word with no resolved lemma states that no lemma is recorded. Continuation: the comparer follows a lexical connection into Connections. Owner: Compare, with lexical relationships continuing into Connections.
FR-13 — Textual variants, manuscript relationships, and Septuagint relationships. As a Translation and Text Comparer I should examine textual variants, manuscript relationships, and Septuagint relationships where appropriate. Provenance: explicit. Trigger/input: a passage in comparison. Observable result: the variant apparatus and manuscript sigla are

Then I saw a new heaven and a new earth, for the first heaven and the first earth had passed away, and the sea was no more.
Genesis 1:1–3 · Isaiah 65:17 · Isaiah 66:22 · 2 Peter 3:13 · Revelation 21:1
Provenance and confidence key

Then I saw a new heaven and a new earth, for the first heaven and the first earth had passed away, and the sea was no more.
Genesis 1:1–3 · Isaiah 65:17 · Isaiah 66:22 · 2 Peter 3:13 · Revelation 21:1
Provenance and confidence key
No comments yet. Be the first!