Pattern 50
Resolve the reference before navigating
Separate a Bible reference from a keyword query, then make ambiguity recoverable.
Concrete takeaway
Recognise complete references and preserve the requested range, edition and origin.
Choose an approach
These are editorial decision conditions to validate. Some alternatives are successive states or can be combined; they are not always exclusive choices.
| Alternative | Use when | Tradeoff or requirement |
|---|---|---|
| A · Exact lookup | The complete reference is recognised | Preserve edition and both range endpoints |
| B · Missing book | The reference lacks a book or is ambiguous | Clarification costs a step but prevents a wrong destination |
| C · Edition unavailable | The specified edition is unavailable | Substitution needs disclosure and user choice |
The problem
A typed or linked reference may include a book abbreviation, range, edition, unfamiliar numbering or an ambiguous name. Treating it as keywords can land at the wrong passage.
The pattern
Recognise complete references and preserve the requested range, edition and origin. Distinguish reference lookup from full-text search; show what was understood before navigation where ambiguity exists. Resolve translated book names and canon or versification differences using reliable mappings. Offer a choice for ambiguity and an honest missing state for unavailable text. A link-specified edition and a preferred edition need an explicit policy; name any substitution. Do not guess the nearest verse and present it as the requested text.
Compare the alternatives
Separate a Bible reference from a keyword query, then make ambiguity recoverable.
A · Exact lookup
The full range is retained as a destination.
B · Missing book
An incomplete reference needs clarification before navigation.
C · Edition unavailable
Substitution is offered rather than hidden.
Original wireframe proposals · No live controls · Grey rows represent schematic text, not loading states · Labelled placeholders are not Scripture quotations
Download this wireframe as SVGFailure modes
Silently dropping a range endpoint; searching keywords when an exact reference was entered; replacing an unavailable edition without notice; inventing a canonical match.
What to validate
Test abbreviations, translated book names, ambiguous names, invalid ranges, cross-chapter ranges, unavailable books and edition-specific numbering.
Research-informed design proposal. These visual alternatives have not been tested with users in this atlas. Source findings, documented behaviour and this proposed adaptation are different kinds of evidence.
Sources and adaptation
This card is an original design synthesis. The following sources inform its content distinctions, interaction approach or review requirements; they do not validate the whole pattern.
- Scripture structure documentationRelevant structure and marker references reviewed · A format is not a complete model of app behaviour, annotations or formation.
Common scenarios and flows
- Open a reference and retain context — Reach the intended verse or range without losing the search or conversation.
Design principles in this decision
Editorial application of Missional by Design. These values frame review questions; they do not validate a pattern’s effectiveness.
- Hospitality — Who can use this approach in their actual context, and what complete alternative exists for someone who cannot?
- Honesty — Could this interface lead a person to infer more authority, certainty, privacy or human support than the service provides?
Compare alternatives using the task and evidence above. Record competing needs instead of treating a principle as an automatic verdict.