# The Fortune Below Bootstrap

This bootstrap registers source evidence only. It does not extract facts or promote generated prose into canon.

## 1. Apply Artifex Migrations

Use the configured PostgreSQL database so scene state and model-request provenance survive across processes.

```bash
python manage.py migrate
```

## 2. Register Shared Hard Canon

Shared canon belongs to a series-reference work. Book scene retrieval automatically includes this work.

```bash
python manage.py story_sources register \
  --root S:/PycharmProjects/wraith-book-projects/AuthorCompanion/manuscripts/the-fortune-below \
  --series-slug labyrinth-hero \
  --series-title "Labyrinth Hero" \
  --work-slug fortune-below-series-reference \
  --work-title "Fortune Below Series Reference" \
  --work-type series_reference \
  --authority canon \
  --document-type canon \
  --include-glob "canon/fortune-below-world-lore.md"
```

`fortune-below-restructure-canon.md` and `fortune-below-series-arc.md` identify themselves as planning
documents. Archive them under `fortune-below-book-two-legacy` with `planning` authority; never register them
as shared canon.

## 3. Register Mainline Book Two Planning

Planning documents are retrievable only when a scene command explicitly includes `planning` authority. Do
not use a broad `book-two/planning/*.md` glob: that directory also contains Sabine/Corin side-novel material.

```bash
python manage.py story_sources register \
  --root S:/PycharmProjects/wraith-book-projects/AuthorCompanion/manuscripts/the-fortune-below \
  --series-slug labyrinth-hero \
  --series-title "Labyrinth Hero" \
  --work-slug the-fortune-below \
  --work-title "The Fortune Below" \
  --authority planning \
  --document-type planning \
  --include-glob "book-two/planning/fortune-below-book-two-cerys-*.md" \
  --include-glob "book-two/planning/fortune-below-book-two-corins-*.md" \
  --include-glob "book-two/planning/fortune-below-book-two-male-friends-*.md" \
  --include-glob "book-two/planning/fortune-below-book-two-missing-scene-roadmap.md" \
  --include-glob "book-two/planning/fortune-below-book-two-permission-slips-*.md"
```

Register the current folded-route plan and approved pilot artifacts separately from the Artifex artifact root.

## 4. Register The Sabine/Corin Side Novel

The side novel is a distinct work even though its chronology overlaps Books Two and Three.

```bash
python manage.py story_sources register \
  --root S:/PycharmProjects/wraith-book-projects/AuthorCompanion/manuscripts/the-fortune-below \
  --series-slug labyrinth-hero \
  --series-title "Labyrinth Hero" \
  --work-slug fortune-below-sabine-corin \
  --work-title "Fortune Below: Sabine and Corin" \
  --authority planning \
  --document-type planning \
  --include-glob "book-two/planning/*sabine-corin*.md"
```

Register selected Sabine/Corin scenes and manuscript drafts against this side work, never against
`the-fortune-below`.

## 5. Archive Existing Mixed Book Two Material

The old planning and scene directories mix mainline, side-novel, alternate, and superseded structures. Preserve
the complete directories under the `fortune-below-book-two-legacy` work before selecting any source into a
current work. The legacy work is `other`, so its documents are not visible to mainline or side-novel retrieval.

Pure Sabine/Corin sources may then be registered separately under `fortune-below-sabine-corin`. Do not leave
active copies attached to `the-fortune-below`.

## 6. Register Existing Mainline Scenes Safely

Existing mainline scenes enter as provisional evidence. Do not use a broad `book-two/scenes/*.md` glob because
that directory contains side-novel drafts and noncanon experiments.

```bash
python manage.py story_sources register \
  --root S:/PycharmProjects/wraith-book-projects/AuthorCompanion/manuscripts/the-fortune-below \
  --series-slug labyrinth-hero \
  --series-title "Labyrinth Hero" \
  --work-slug the-fortune-below \
  --work-title "The Fortune Below" \
  --authority provisional \
  --document-type scene \
  --include-glob "book-two/scenes/fortune-below-book-two-cerys-*.md" \
  --include-glob "book-two/scenes/fortune-below-book-two-selka-cerys-*.md" \
  --include-glob "book-two/scenes/fortune-below-book-two-estate-*.md" \
  --include-glob "book-two/scenes/fortune-below-book-two-short-ch01-*.md"
```

Register the ten-turn manuscript under the side work as provisional manuscript material until its assembly is
approved.

```bash
python manage.py story_sources register \
  --root S:/PycharmProjects/wraith-book-projects/AuthorCompanion/manuscripts/the-fortune-below \
  --series-slug labyrinth-hero \
  --series-title "Labyrinth Hero" \
  --work-slug fortune-below-sabine-corin \
  --work-title "Fortune Below: Sabine and Corin" \
  --authority provisional \
  --document-type manuscript \
  --include-glob "book-two/ten-turn-manuscript/*.md"
```

## 7. Plan A Scene

The default context includes hard canon only. This example deliberately includes planning material and pins the
two current rule documents.

```bash
python manage.py fiction_scene run \
  --series-slug labyrinth-hero \
  --work-slug fortune-below-sabine-corin \
  --title "New Scene Title" \
  --brief S:/path/to/new-scene-brief.md \
  --target-words 2200 \
  --include-authority canon \
  --include-authority planning \
  --pin-document book-two/planning/fortune-below-sabine-corin-turn-and-household-rules.md \
  --pin-document book-two/planning/fortune-below-sabine-corin-physical-continuity-reconciliation.md
```

Inspect the returned plan before approving it. Final scene approval registers the artifact as `provisional`, not
`canon`. Mainline scene commands must not pin side-work documents.