## repository Purpose
This repository is a fiction-writing workspace. The assistant helps draft, revise, organize, and maintain story files with strict version control and clear separation between chapter prose and non-chapter reference material.

---

## Directory structure

### Chapter files
- Active chapter files live directly inside `chapters/`.
- Archived chapter versions live inside `chapters/archive/`.

Examples:
- `chapters/chapter01_part01_v1.md`
- `chapters/chapter01_part01_v2.md`
- `chapters/archive/chapter01_part01_v1.md`

### Story bible files
Non-chapter material must never be stored in `chapters/`.

Use these folders instead:

- `story_bible/outlines/` for plot outlines and beat sheets
- `story_bible/characters/` for character profiles and relationship notes
- `story_bible/world/` for setting, lore, factions, systems, and history
- `story_bible/references/` for tone, themes, style notes, or other support documents

Each section keeps its own archive folder:

- `story_bible/outlines/archive/`
- `story_bible/characters/archive/`
- `story_bible/world/archive/`
- `story_bible/references/archive/`

Examples:
- `story_bible/outlines/outline_ch01_v3.md`
- `story_bible/characters/main_cast_v2.md`
- `story_bible/world/world_notes_v4.md`

---

## File naming rules

### General format
All active files must include a version number in the filename.

Format:
`name_vN.md`

Where:
- `N` is an integer version number
- version numbers increase sequentially
- do not skip numbers unless explicitly instructed

Examples:
- `chapter01_part01_v1.md`
- `chapter01_part01_v2.md`
- `outline_master_v3.md`
- `character_profiles_v5.md`

### Chapter naming
Use:
`chapter##_part##_vN.md`

Examples:
- `chapter01_part01_v1.md`
- `chapter03_part02_v4.md`

If a chapter is not split into parts, use:
`chapter##_vN.md`

Example:
- `chapter05_v2.md`

---

## Revision workflow

### Core rule
Never overwrite a tracked draft without preserving the previous version.

### When revising an existing file
If revising an active file:
1. Identify its current version number.
2. Copy or move that exact file into the correct archive folder.
3. Create a new active file in the original main folder with the next version number.
4. Apply the requested edits only to the new version.
5. Leave archived files untouched after archiving.

### Example
If the active file is:
`chapters/chapter01_part01_v3.md`

Then before revising:
- archive old version to `chapters/archive/chapter01_part01_v3.md`
- create new version `chapters/chapter01_part01_v4.md`

### Important restrictions
- Do not edit archived files unless explicitly told to restore or reuse one.
- Do not delete older versions.
- Do not rename unrelated files.
- Do not silently replace one file with another.
- Do not create duplicate active versions with the same version number.

---

## Creating new files

### New chapter files
When creating a chapter file for the first time, start at version 1.

Example:
- `chapters/chapter02_part01_v1.md`

### New story bible files
When creating a new outline, profile, or world file for the first time, start at version 1.

Examples:
- `story_bible/outlines/outline_ch02_v1.md`
- `story_bible/characters/side_characters_v1.md`
- `story_bible/world/magic_system_v1.md`

---

## Context discipline

Read only the files needed for the task. confirm with user

### For chapter drafting or revision
Prioritize:
1. the target chapter file
2. the most relevant chapter outline
3. the character files for characters appearing in the scene
4. world files only if needed for continuity, setting, lore, or mechanics
5. reference files only if needed for tone or style consistency

### Avoid unnecessary reads
- Do not read unrelated chapters unless explicitly asked
- Do not load the entire story bible by default
- Do not inspect archive files unless needed for comparison, restoration, or continuity checks
- Prefer minimal relevant context over broad scanning

---

## Continuity checks

When continuity issues are noticed:
- flag them clearly
- name the conflicting files if possible
- do not make large canon changes automatically
- prefer minimal fixes that preserve existing material
- if revising a chapter, do not rewrite major worldbuilding or character history unless explicitly requested

Examples of continuity issues to watch:
- eye color, age, names, rank, titles
- timeline or sequence errors
- ability or system inconsistencies
- emotional or relational contradictions
- setting details that conflict with world notes



---

## Restoration workflow

If asked to restore an older version:
1. locate the requested archived file
2. do not overwrite it
3. create a new active version in the main folder using the next available version number
4. base that new active file on the archived content
5. log the restoration in `logs/CHANGELOG.md`

Example:
- restore `chapters/archive/chapter01_part01_v2.md`
- new active file becomes `chapters/chapter01_part01_v5.md`

---

## Safe defaults

Unless explicitly instructed otherwise:
- prefer additive and conservative edits
- do not reorganize the repository
- do not invent missing plot facts as if they are canon
- do not merge files automatically
- do not delete files
- do not alter archive contents
- do not update multiple unrelated files in one pass unless requested

---

## Output expectations

After completing a writing task, provide a short summary that includes:
- which file was read
- which file was archived
- which new file was created
- what changed in the prose or notes
- any continuity concerns worth attention

Keep summaries concise and practical.