Bibble Daily
Editorial Methodology
How the character pool becomes a consistent daily deduction game.
Purpose and scope
Bibble Daily organizes biblical people for one specific purpose: producing comparisons that are understandable, repeatable, and fair enough for a daily guessing game. The data is not a new Bible translation, a complete concordance, or a claim that every tradition must describe each person in exactly the same way.
The searchable pool is intentionally finite. A character is added only after names, story locations, Roles, Circles, relationships, Hints, and answer difficulty can be reviewed together. This avoids enlarging the roster with entries whose distinctions are too uncertain for consistent gameplay.
From candidate to playable character
- Identify the central narrative.Record the Books and references that establish the character's main story rather than treating every passing mention equally.
- Review names and ambiguity.Add useful aliases while keeping people with shared names—such as different Jameses, Marys, or Philips—clearly distinguishable.
- Assign gameplay taxonomy.Choose the Testament, primary and secondary Eras, story Books, strong and soft Roles, story Circles, and broader Circles used by the five comparison columns.
- Check relationships.Direct connections require reviewed evidence between the two people; broader association alone does not produce the fire Clue.
- Write and test Hints.Verse and Story Hints should help without exposing the answer too quickly. Answer-name forms are checked so a displayed verse does not accidentally reveal the hidden name.
- Audit the full pool.Automated tests check identifiers, references, taxonomy values, answer eligibility, comparison symmetry, and schedule integrity; editorial review handles contextual judgment those tests cannot.
How close matches are kept meaningful
Not every shared label deserves the same signal. A strong Role such as prophet or priest can produce a green match. A softer but still useful connection may produce yellow. Very generic labels are prevented from producing a match by themselves, because doing so would make unrelated characters appear more similar than their stories support.
Circles follow the same principle. A direct reviewed relationship produces fire; a close shared story group produces green; and a wider association may produce yellow. The game reports no match when the evidence does not support one of those boundaries.
Text, sources, and attribution
Verse Hints use the public-domain World English Bible. Compatible open structured datasets can help identify candidates or check references, but imported records do not become shipped gameplay data without review. Each published character retains an evidence record for its central story, Roles, relationships, and Circles.
The Data Credits page lists registered sources and licenses. Bibble Daily is independently created and is not affiliated with a church, denomination, Bible publisher, or the maintainers of those source projects.
Corrections and player feedback
After a completed run, the optional feedback form can report a confusing Clue, questionable classification, missing character, or technical problem. The submitted gameplay path provides the diagnostic context needed to reproduce the comparison without asking for the player's identity.
A correction is based on the underlying evidence and consistency of the full roster, not simply on whether one result felt difficult. When a boundary changes, related characters and tests must be reviewed so the fix does not create a new inconsistency elsewhere.