Purpose: Standardized format for KJVEL psalm decodes. Built from psalm_55_decode.md and psalm_140_decode.md. Copy this file, rename it psalm_NNN_decode.md, and fill in the <<PLACEHOLDER>> fields.
Required prep before writing:
`python
import json
d = json.load(open('data/kjv_parsed.json'))
for v in d:
if v['book']=='PSA' and v['chapter']==NNN:
print(f"{v['verse']:>2}: {v['text']}")
def g(s): return sum(ord(c.upper)-64 for c in s if c.isalpha)
def dr(n):
while n>=10: n=sum(int(d) for d in str(n))
return n
def T(n): return "Tesla" if dr(n) in (3,6,9) else ""
`
Required passes before writing — do all five:
Required honesty checks:
Decode date: <<YYYY-MM-DD>>
Form: <<verse count>> verses, superscription "<<superscription text>>"
Tradition: <<one-line traditional reading and historical context>>
Companion decodes: <<list of related project_.md or psalm__decode.md files>>
In plain English: <<3–5 sentence blockquote. Required opening for every decode. Explain what the psalm is on the surface, what the gematria reveals underneath, and why this decode matters. Write for a smart 12-year-old. Lead with the single most striking lock — if the psalm has an alpha-omega handshake (petition integer = promise integer), open with that. If it has a central verb-substitution, open with that. If neither, open with the most loaded master lock.>>
<<Gematria table of superscription, author, named figures, and any classifying terms.>>
| Term | Gematria | DR | Lock |
|---|---|---|---|
| <<superscription full>> | <<n>> | <<n>> | <<KJVEL family match or note>> |
| <<author>> | <<n>> | <<n>> | <<>> |
| <<key named figure>> | <<n>> | <<n>> | <<>> |
| SELAH (if present) | 45 | 9 ✓ | = PIT — every Selah marks a depth marker |
Key lock — <<superscription anchor>>: <<Explain how the superscription locks to a figure/theme/integer inside the psalm. This is the reflexive lock. Reference Psa 55's CHIEF MUSICIAN=120 lock or Psa 140's A PSALM OF DAVID=EVIL SPEAKER=123 lock as precedents if applicable.>>
<<10–15 row table. This is the highest-value section. Every entry must be a verified gematria identity between two phrases that appear in the psalm OR between a phrase in this psalm and a phrase in a previously decoded psalm. Three or more occurrences at the same integer = a lock. Two occurrences = a notable. One occurrence with a strong KJVEL family match = also notable. Sort by impact (most striking first).>>
| Verses | Phrase / Term | Gematria | Equals | Meaning |
|---|---|---|---|---|
| v<<a>> → v<<b>> | <<P1>> ↔ <<P2>> | <<n>> = <<n>> | same integer | <<one-line meaning>> |
| v<<a>> | <<P3>> | <<n>> | = <<KJVEL family>> | <<one-line meaning>> |
| <<...>> | <<...>> | <<...>> | <<...>> | <<...>> |
<<End the section with: "N locks across V verses." This signals decode density.>>
<<If the psalm has a unique structural pattern (Selah density, refrain, acrostic, double-blessing, lament-to-praise pivot, etc.), give it a section here. Examples:
If the psalm has no unique structural feature, skip this section and renumber.>>
<<For each verse (or each cluster of 2-3 verses if the psalm is long), present:
The header for each group should describe the movement, not just verse numbers. e.g.:
Each Lock paragraph should be 2-4 sentences:
Reserve the bulk of the analysis for the killer locks (Section 2) and the focus-verse deep dive (Section 5). This section is the systematic walk-through, not the showcase.>>
Lock (v<<n>>): <<finding>>
<<Repeat for each movement.>>
<<full verse text>>
<<One-paragraph orientation: what the verse says on the surface, why it carries the psalm's weight.>>
<<For each major finding in the focus verse, write a numbered "Lock N-A / N-B / N-C..." paragraph. Each lock is 3-6 sentences. Reference cross-decodes by file name. Reference prior locks in the same decode where the integer recurs.>>
Lock <<N>>-A — <<name of finding>>: <<3-6 sentence explanation>>.
Lock <<N>>-B — <<name of finding>>: <<3-6 sentence explanation>>.
<<...continue for 4-8 locks.>>
<<One paragraph rereading the verse with all the integer-meanings substituted in. This is the "translated" verse — what the gematria layer shows the verse is actually saying. Always quotable.>>
<<Verse N>> is <<one-line capstone meaning>>.
<<If the psalm has a verb-substitution or boomerang at a specific integer, document it here. This is one of the most powerful sections — it shows the psalm is engineered around a single mobile integer that David asks God to redirect.
Format example:
`
v<a> (suffering mode): "<original phrase>" = <integer>
↓
(intervening verses of descent/diagnosis)
↓
v<b> (instruction mode): "<resolution phrase>" = <same integer>
`
State the verb-direction reversal in one sentence: "The problem doesn't change. The verb does."
If the psalm has no such handshake, document the central mechanism it does have (refrain locking, ABA structure, double-blessing, etc.).>>
<<KJVEL families to look for in EVERY psalm:
If your psalm hits 2+ of these clusters, document each in its own subsection. If a single cluster carries the psalm (like 64 in Psa 55, 108 in Psa 140), give it its own section here.>>
<<Optional. Use for unique mechanisms the psalm has that don't fit a standard cluster. Examples:
<<Map the psalm to a movement structure (typically 5-7 movements). Each row of the table identifies which integer anchor dominates each movement. Use this table to show the structural arc.>>
| # | Verses | Movement | Integer anchor |
|---|---|---|---|
| 1 | v<<a>>–<<b>> | <<name>> | <<n>> (<<what>>) |
| 2 | <<...>> | <<...>> | <<...>> |
<<Close with a one-paragraph summary identifying which movements form handshakes/boomerangs/etc.>>
<<Numbered list of 5-7 practical reading instructions. Each item:
<<ASCII code-block table listing every major lock in the psalm. Use this format:>>
`
v<<a>> <<TERM A>> = v<<b>> <<TERM B>> = <<n>> [<<short label>>]
v<<a>> <<TERM A>> = <<KJVEL family>> = <<n>> [<<short label>>]
`
<<Aim for one summary lock per identity found. Format the lines so the integers line up in a column. Close with one sentence: "N verses, M cross-verse identity locks." This is the final at-a-glance proof of decode density.>>
<<Use this section if the psalm has a final-verse capstone worth its own block. Mirrors the focus-verse section but shorter — 2-3 paragraphs reading the final verse with all the locks substituted in. Always quotable.>>
<<phrase from final verse>> — at <<integer>> = <<KJVEL family>>. <<one-sentence meaning>>.
<<phrase from final verse>> — at <<integer>> = <<KJVEL family>>. <<one-sentence meaning>>.
Read together, <<verse N>> says: "<<one-paragraph translation using the gematria meanings>>". The psalm is the resolution of <<what>> at one verse, by integer-superposition.
Decode generated <<YYYY-MM-DD>> using src/name_decoder.py and verse-by-verse gematria sum against data/kjv_parsed.json. Cross-cluster references: <<list>>. Companion analyses: <<list>>.
Before publishing a decode built from this template:
> In plain English: blockquote (3-5 sentences)