# BTC–Bible Epoch Model

Version: 0.1  
Status: Working structural model, not proof  
Date: 2026-06-13  
Project: RTW-02 / Human & AI – LAB  

## Purpose

This document records the first structured epoch model built from the imported raw OT, NT, BTC, anchor, chronology, and E7 use-case files.

The machine-readable model is:

- `data/rtw-02/epoch_model_v0_1.json`

Its schema and validator are:

- `data/rtw-02/epoch_model_schema_v0_1.json`
- `scripts/validate_epoch_model.py`

## Interpretation Boundary

Historical labels and dates are source data or chronology-model data.

Bible–BTC epoch correspondences are working structural mappings. Puzzle relations are interpretive working hypotheses. Neither category is proof of hidden intent or causal historical connection.

## Model Contents

### Generic Epoch Types

The model contains the full E0–E10 sequence:

- E0 Preparation
- E1 Revelation
- E2 Foundation
- E3 Pioneer Wilderness
- E4 Distribution
- E5 Decentral Rule
- E6 Unity Era
- E7 Division Conflict
- E8 Crisis Exile
- E9 Restoration
- E10 Global Spread

### Domain Epochs

- 9 Old Testament epochs: OT1–OT9
- 3 New Testament epochs: NT1–NT3
- 8 Bitcoin epochs: BTC1–BTC8

Each epoch contains stable IDs, source IDs, domain, order, generic-type references, time spans where supplied, and notes.

The validator does not require invented dates. BTC epochs without explicit raw-source date ranges keep an empty `time_spans` array.

### Chronology Models

- `MODEL_A`: early Exodus chronology
- `MODEL_B`: late Exodus chronology
- `MODEL_X`: 30 AD crucifixion boundary
- `MODEL_Y`: 33 AD crucifixion boundary

BCE years use negative integers and CE years use positive integers. Year zero is not permitted.

### Events and Anchors

The model contains:

- 15 events
- 14 primary anchors
- anchor aliases retained from the E7 use case

The event layer includes OT/NT anchors and the BTC6 Blocksize War, BCH split, and SegWit activation events supplied by the raw use case.

### E7 Use Case

`MAP5_OT7_BTC6` connects:

- `OT7_Divided_Kingdom`
- `BTC6_SegWit_Scaling_Era`
- `E7_DIVISION_CONFLICT`

The source-supplied similarity score of `10/10` is preserved but explicitly marked as not independently validated.

The `PZ5 / TRIBE_DAN / BIVIUM` relation is preserved as an interpretive working hypothesis, not as established evidence.

## Validation

Run:

```bash
python3 scripts/validate_epoch_model.py
```

The validator checks:

- required top-level collections
- duplicate IDs and order indexes
- source-file existence
- generic-type references
- chronology-model references
- epoch/event domain consistency
- time-range ordering and forbidden year zero
- anchor-to-event and anchor-to-epoch references
- use-case event, anchor, epoch, and concept references
- similarity score bounds
- BTC puzzle-event reference

Validation result on 2026-06-13: `PASS`.

## Tény / Számítás / Hipotézis / Következő Lépés

### Tény

- The structured model was created from imported raw repository files.
- All current cross-references pass the validator.
- The model contains 11 generic types, 20 epochs, 15 events, 14 anchors, and 1 use case.

### Számítás

- BCE dates are normalized to negative integers.
- CE dates are normalized to positive integers.
- Source ranges remain approximate or disputed where the raw files say so.
- No cryptographic, wallet, or xpub calculation is included.

### Hipotézis

- E0–E10 may be useful as a shared structural vocabulary across OT, NT, and BTC history.
- `MAP5_OT7_BTC6` is a structural analogy requiring controls and alternative comparisons.
- The puzzle relation remains interpretive and unproven.

### Következő Lépés

- Add controlled comparison cases that do not use OT7/BTC6.
- Define a reproducible similarity rubric instead of relying on an unexplained `10/10` score.
- Add JSON entities for Joshua tribes and connect only explicitly documented relations.
- Consider a later API/query layer after the model stabilizes.