Downloads
Everything you need to build a module: a working example of each type, the schemas they validate against, and the table definitions the app reads.
Sample modules
Each of these is a real, installable .lamp file. They are deliberately tiny — a few verses or entries each — so you can decompress one, open it in any SQLite browser, and see the whole thing at once. Download one to your device and open it to watch the import work.
Each file is named after the module it holds. Keep the name if you pass one on: on iPhone and iPad the app reads the module’s identifier from it, and refuses a file whose name and contents disagree.
Translation
Verse text with Strong’s tagging, headings, footnotes and poetry markers.
Six CC0 Berean Standard Bible verses across Genesis, John and Psalms, with Strong’s annotations, two section headings, a translator footnote and a full-text index.
Dictionary
Lexicon entries keyed by Strong’s number or lemma, with numbered senses.
Three public-domain Strong’s entries — two Hebrew, one Greek — each with numbered senses, glosses, transliteration and part of speech.
Commentary
Exposition keyed to verses or pericopae, one book of a series per file.
Original notes on the opening of Genesis, showing the section → pericope → verse nesting and both Strong’s and scripture annotations.
Book
A long-form publication in nested sections, with footnotes shared across the book.
An original preface and chapter, with a section nested in the chapter, a book-wide footnote and scripture reference annotations.
Reading plan
Dated reading assignments across a cycle.
A seven-day plan, one reading per day, through the creation account and the prologue of John.
Quiz
Age-graded questions tied to a reading plan’s readings.
Ten questions on day one of the sample plan — five for each of two age groups — with themes and cross-references.
Notesyou edit
Verse-keyed study notes, one book per file.
A chapter introduction and two notes on John 1, anchored to verses 1 and 14.
Devotionalyou edit
A long-form document, not tied to a single passage.
One short original reading, with a summary, tags and a key scripture.
Highlightsyou edit
Highlight spans and colour themes for one translation.
Four highlights against the sample translation — one in each of the four styles, with character offsets that land on real words — and two colour themes.
JSON Schemas
The schemas every module source document validates against. They share common definitions for annotations, verse references, metadata and media. Two commentary examples are included alongside them — a full one and a minimal one.
- book_schema.json11.0 KB
- commentary_example.json3.5 KB
- commentary_schema.json16.6 KB
- commentary_series_schema.json5.1 KB
- commentary_simple_example.json995 B
- devotional_schema.json12.1 KB
- highlight_schema.json3.7 KB
- lexicon_mapping_schema.json1.5 KB
- lexicon_schema.json17.3 KB
- notes_schema.json7.6 KB
- plan_schema.json2.8 KB
- quiz_schema.json6.4 KB
- translation_schema.json10.3 KB
SQLite table definitions
The tables the app expects inside a decompressed .lamp, one file per module type, each including the module_format table every module needs. Run them with executescript() or sqlite3 < file.sql before inserting rows.
- translation.sql1.9 KB
- dictionary.sql1.0 KB
- commentary.sql1.5 KB
- book.sql1.7 KB
- plan.sql726 B
- quiz.sql1.3 KB
- notes.sql1.3 KB
- devotional.sql1.3 KB
- highlights.sql890 B
Provenance
The JSON Schemas here are copies, kept in step with the module tooling by a sync script that records the source revision and a SHA-256 for every file. These copies were taken on 2026-10-28 from revision 98291056062e.
manifest.json lists every file with its hash, so you can confirm a download arrived intact.
Where to go next
- Building a .lamp file — the mechanics, step by step, with the compression details and the mistakes to avoid.
- Authoring modules — verse reference encoding, annotation types, and the JSON shape of each module type.
- The module system — how modules fit into the app.