# Sacred Commentary Flow Proof

This proof bundle shows how Scriveno adapts the writing loop to sacred commentary. It is not a doctrine claim and not a substitute for a tradition-qualified reviewer. It proves structure: source care, register discipline, figures, doctrine, commentary movement, and review before publication.

## What This Proves

- Sacred work uses tradition-native surfaces instead of generic novel files.
- The workflow can plan and draft commentary without flattening it into ordinary essay prose.
- Source and doctrinal checks are visible before publishing.
- Research or commentary notes remain advisory unless accepted by the project.

## Canonical Flow

### 1. Project state

- `data/proof/sacred-flow/STATE-SNAPSHOT.md`

The snapshot records adapted sacred surfaces, source boundaries, and the next review step.

### 2. Commentary plan

- `data/proof/sacred-flow/1-threshold-of-mercy-PLAN.md`

The plan shows source anchors, register, interpretive caution, reader-state movement, and doctrinal watchpoints.

### 3. Drafted commentary

- `data/proof/sacred-flow/1-threshold-of-mercy-DRAFT.md`

The draft is a short commentary section that avoids claiming universal tradition authority. It demonstrates tone and structure rather than final theological authority.

### 4. Next command

The next command is:

```text
/scr:sacred:doctrinal-check 1
```

That keeps the sacred path honest: draft comes before review, and review comes before publishing.

## Reading Order

1. Read `STATE-SNAPSHOT.md`.
2. Read `1-threshold-of-mercy-PLAN.md`.
3. Read `1-threshold-of-mercy-DRAFT.md`.
4. Confirm that doctrinal review is the continuation.

## Boundaries

This proof bundle is intentionally generic. A real sacred project must load its actual tradition profile, source tracking, transliteration rules, commentary authorities, and reviewer constraints.