Torah Commentary Database - Field Definitions and Update Procedures

Purpose

This document provides complete specifications for the torah_database_FINAL_SESSION.xlsx file, including field definitions, data formats, and step-by-step update procedures for the Interactive Workflow Protocol.

Database Overview

File: torah_database_FINAL_SESSION.xlsx
Total Fields: 38
Books Covered: Genesis (19 units), Leviticus (22 units), Deuteronomy (13 units)
Purpose: Single source of truth for all unit data and structural relationships

Field Categories and Definitions

CATEGORY 1: CORE IDENTIFICATION

Fields that uniquely identify each unit

Field Name	Type	Format	Example	When to Update
unit_id	String	BOOK-##	`GEN-05`	At unit creation
book	String	Full name	`Genesis`	At unit creation
unit_number	Integer	1-22	`5`	At unit creation
verse_range	String	Book C:V-C:V	`Genesis 11:10-13:4`	At unit creation
opening_formula	String	Free text	`These are the generations of Shem`	After Part A complete
structure_type	String	regular/irregular	`regular`	After Part A complete
dimensions	String	Grid or standalone	`3×2` or `23332`	After Part A complete
analysis_status	String	complete/partial/placeholder	`complete`	Update as work progresses

Update Trigger: Create row when starting any unit work. Update as analysis progresses.

CATEGORY 2: INTERNAL STRUCTURE

Fields describing the unit's internal organization

Field Name	Type	Format	Example	When to Update
rows	Integer	Number	`3`	After internal structure analyzed
columns	Integer	Number	`2`	After internal structure analyzed
warp_pole_1	Text	Thematic summary	`Divine speech/action`	After warp analysis complete
warp_middle	Text	Thematic summary	`Mediation/transition`	Only if triad structure
warp_pole_2	Text	Thematic summary	`Human response/consequence`	After warp analysis complete
weft_thread_1	Text	Thematic summary	`Introduction/calling`	After weft analysis complete
weft_thread_2	Text	Thematic summary	`Development/crisis`	After weft analysis complete
weft_thread_3	Text	Thematic summary	`Resolution/closure`	If row 3 exists
weft_thread_4	Text	Thematic summary		If row 4 exists
weft_thread_5	Text	Thematic summary		If row 5 exists
has_subdivisions	Boolean	TRUE/FALSE	`TRUE`	After internal structure analyzed
subdivision_pattern	String	Type	`A,B,C` or `parallel_indicators`	After internal structure analyzed

Update Trigger: Complete after Part D (Unit Commentary) internal structure section written.

Important Notes:

warp_middle only exists for triadic structures (3-column units)
weft_thread_3/4/5 only fill if those rows exist
Dyads have 2 columns, triads have 3 columns

CATEGORY 3: TORAH-WIDE ORGANIZATION

Fields showing how unit fits into larger structure

Field Name	Type	Format	Example	When to Update
unit_triad_membership	String	A-H	`B`	After Part B complete
warp_thread_number	Integer	1-3	`2`	After Part B complete
creation_paradigm_position	String	God/people/mediating	`God-oriented`	After Part B complete
anomalous_status	Boolean	TRUE/FALSE	`FALSE`	After Part B complete

Update Trigger: Complete when book's Part B (Discovering the Map) is written.

Genesis Three-Ring Structure Reference:

Triads A ↔ F (Outer Ring): Kingship - Divine (Creation) ↔ Human (Joseph)
Triads B ↔ E (Middle Ring): Covenants - Deity and rulers, altars, sacred places
Triads C ↔ D (Inner Ring): Family - Brothers' children ↔ Brothers

CATEGORY 4: LEVITICUS SPECIAL FEATURES

Field unique to Leviticus analysis

Field Name	Type	Format	Example	When to Update
ring_identifier_type	String	place/time/person/none	`place`	Leviticus units only

Update Trigger: When analyzing Leviticus units after structure determined.

Note: Other books use different ring identification systems. This field only applies to Leviticus.

CATEGORY 5: THEMATIC CONTENT

Fields capturing literary and theological content

Field Name	Type	Format	Example	When to Update
primary_theme	Text	One-line summary	`Abraham's call and testing`	After Part D written
movement_type	String	Predefined types	`separation_to_unity`	After Part D written
divine_names_pattern	Text	Distribution notes	`YHWH dominant, Elohim in Row 3`	After Part C/D written
key_intersection	Text	Cell reference + meaning	`2B: Jacob becomes Israel`	After Part D written
emergent_meaning	Text	Structural insights	`Two-dimensional reading reveals...`	After Part D written
literary_techniques	Array	Comma-separated	`chiasm, envelope, triadic`	After Part D written
visual_hierarchy	Text	Spatial description	`Center position emphasizes covenant`	After Part D written
supernatural_content	Boolean	TRUE/FALSE	`TRUE`	After Part D written

Update Trigger: Complete after Part D (Unit Commentary) finished.

Movement Types:

unity_to_separation - Things start together, end apart
separation_to_unity - Things start apart, come together
intensification - Pattern builds/escalates
circular - Returns to starting point
static - No movement, establishes baseline

Literary Techniques Vocabulary:

chiasm - ABBA or ABCBA pattern
envelope - Same material at beginning and end
triadic - Three-part structure
concentric_rings - Nested layers
parallel - Similar structures repeated
inversion - Pattern reversed

CATEGORY 6: CROSS-UNIT RELATIONSHIPS

Fields showing connections between units

Field Name	Type	Format	Example	When to Update
inverted_units	Array	Comma-separated IDs	`GEN-05, GEN-12`	After Part C written
structural_family	String	Group name	`3×2_group`	After Part A/B written
triad_pair_partner	String	Triad letter	`F` (if unit in Triad A)	After Part B written
thematic_chain	Array	Comma-separated IDs	`GEN-07, LEV-16, DEU-09`	As cross-book patterns identified

Update Trigger:

inverted_units and structural_family: After book's Part B complete
triad_pair_partner: After book's Part B complete (Genesis: A↔F, B↔E, C↔D)
thematic_chain: As cross-book patterns discovered

CATEGORY 7: ANALYSIS METADATA

Fields tracking the analysis process

Field Name	Type	Format	Example	When to Update
confidence_level	String	high/medium/low	`high`	After Part D written
primary_source	String	Scholar/work	`Kline, Before Chapter and Verse`	At unit creation
color_coding_verified	Boolean	TRUE/FALSE	`TRUE`	After visual patterns checked
notes	Text	Free text	`Unusual envelope structure...`	Anytime observations made

Update Trigger: Throughout the process. notes field especially important for uncertainties or special cases.

Update Procedures by Workflow Stage

Stage 1: Unit Creation (Starting Analysis)

User Action: Opens database, creates new row

Fields to Complete:

unit_id: [BOOK-##]
book: [Full book name]
unit_number: [Integer]
verse_range: [Complete range]
analysis_status: placeholder
primary_source: Kline, Before Chapter and Verse

Claude Provides:

NEW UNIT ENTRY - Copy/Paste Format
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Row: [Next available row number]

unit_id: GEN-05
book: Genesis
unit_number: 5
verse_range: Genesis 11:10-13:4
analysis_status: placeholder
primary_source: Kline, Before Chapter and Verse

✓ Entry created? Type 'confirmed' to proceed.

Stage 2: Part A Complete (Units Identified)

User Action: Unit boundaries and structure determined

Fields to Update:

opening_formula: [Key opening words]
structure_type: regular OR irregular
dimensions: [e.g., 3×2 or 23332]
structural_family: [e.g., 3×2_group]
analysis_status: partial

Claude Provides:

PART A COMPLETION - Database Update
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Find Row: [BOOK-##]
Update These Columns:

opening_formula: These are the generations of Shem
structure_type: regular
dimensions: 3×2
structural_family: 3×2_group
analysis_status: partial

✓ Updated? Type 'confirmed' to proceed.

Stage 3: Part B Complete (Book Map Discovered)

User Action: Book structure and triad relationships determined

Fields to Update:

unit_triad_membership: [A through H]
warp_thread_number: [1, 2, or 3]
creation_paradigm_position: [God-oriented/people-oriented/mediating]
triad_pair_partner: [Partner triad letter]
anomalous_status: [TRUE/FALSE]

Claude Provides:

PART B COMPLETION - Database Update
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Find Row: GEN-05
Update These Columns:

unit_triad_membership: B
warp_thread_number: 1
creation_paradigm_position: God-oriented
triad_pair_partner: E
anomalous_status: FALSE

✓ Updated? Type 'confirmed' to proceed.

Stage 4: Part D Complete (Unit Commentary Written)

User Action: Individual unit commentary finished

Fields to Update: All remaining structural and thematic fields

Claude Provides:

UNIT COMMENTARY COMPLETION - Database Update
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Find Row: GEN-05
Update These Columns:

rows: 3
columns: 2
warp_pole_1: Divine call and promise
warp_pole_2: Human response and testing
weft_thread_1: Journey and calling (11:10-12:9)
weft_thread_2: Crisis in Egypt (12:10-20)
weft_thread_3: Return and resolution (13:1-4)
has_subdivisions: FALSE
subdivision_pattern: none
primary_theme: Abraham's call and initial testing
movement_type: circular
divine_names_pattern: YHWH dominant; explicit divine appearances
key_intersection: 1A: "YHWH said to Abram, Go from your country"
emergent_meaning: Geographic envelope creates circular journey
literary_techniques: envelope, geographic markers, altar building
visual_hierarchy: Center (Row 2) contains crisis; outer rows frame
supernatural_content: TRUE
confidence_level: high
color_coding_verified: TRUE
analysis_status: complete
notes: Sister-wife motif creates pattern across corners

✓ Updated? Type 'confirmed' to proceed.

Data Entry Best Practices

Consistency Standards

1. Divine Names:

Always capitalize: YHWH, Elohim
Use compound form: YHWH Elohim (not "Yahweh-Elohim")

2. Verse References:

Full format: Genesis 11:10-13:4
No abbreviations in verse_range field

3. Boolean Fields:

Use Excel TRUE/FALSE (not yes/no or 1/0)

4. Array Fields:

Comma-separated with single space: GEN-05, GEN-12, GEN-16
No brackets or quotes

5. Empty Fields:

Leave blank (not "N/A" or "none")
Exception: subdivision_pattern should be "none" if no subdivisions

6. Thematic Descriptions:

Be specific but concise (aim for 5-15 words)
Focus on observable structural features, not interpretations

Quick Reference: Required Fields by Stage

Stage	Minimum Required Fields
Unit Created	unit_id, book, unit_number, verse_range, analysis_status
Part A Done	+ opening_formula, structure_type, dimensions, structural_family
Part B Done	+ unit_triad_membership, warp_thread_number, creation_paradigm_position, triad_pair_partner
Part D Done	+ ALL structure fields, ALL thematic fields, confidence_level

Common Issues and Solutions

Issue: Not sure about warp vs. weft themes

Solution:

Warp (columns/poles): Read DOWN each column - what's the thematic unity?
Weft (rows/threads): Read ACROSS each row - what's the thematic progression?

Issue: Unit has irregular structure

Solution:

Set structure_type: irregular
Set dimensions to actual pattern (e.g., 23332)
Note irregularity in notes field

Issue: Multiple movement types seem to apply

Solution:

Choose the DOMINANT pattern
Note secondary patterns in notes field

Issue: Uncertain about triad membership

Solution:

Set confidence_level: medium or low
Document uncertainty in notes field
Mark for review after more units analyzed

Database Maintenance

Monthly Tasks:

Backup database file with date stamp
Review analysis_status field for stalled units
Check for missing cross-references as new units completed

After Each Book Completed:

Verify all units have analysis_status: complete
Check that all triad relationships documented
Update thematic_chain fields as patterns across books emerge

File Management

Location: /Admin/torah_database_FINAL_SESSION.xlsx

Backup Protocol:

Save dated backup before major updates: torah_database_YYYY-MM-DD.xlsx
Keep last 5 backups minimum

Version Control:

torah_database_COMPLETE.xlsx = Reference version (read-only)
torah_database_FINAL_SESSION.xlsx = Working version (edit this one)

Integration with Interactive Workflow Protocol

This database document works with the Interactive Workflow Protocol document:

Protocol triggers database update at completion checkpoints
Claude formats data according to these field definitions
User copies/pastes into Excel
Progress tracked through analysis_status field

Result: Consistent, complete data entry with minimal manual formatting