Content architecture — Amberbrew Story
This is a family-story and documentation archive, not a software project. The structure separates project decisions, established continuity, lived gameplay and possible future fiction.
Project documents: what belongs where
| File | Record here | Do not put here |
|---|---|---|
| README.md | Family-wide introduction, navigation, current phase | Full stories or long decision histories |
| CONCEPT.md | The creative's purpose, intended reader experience, world and scope | Prescriptive plot beats or invented character biography |
| ROADMAP.md | Completed work, next editorial steps, deferred possibilities | Claims that unwritten chapters or unapproved lore already exist |
| WRITING-GUIDE.md | Ten agreed literary principles and future writing boundaries | Actual fictional scenes |
| docs/DECISIONS.md | Approved choices, rejected alternatives and source/provenance | An unsifted transcript of every AI suggestion |
| docs/DEVLOG.md | Brief human-perspective narrative of meaningful project evolution and AI contribution | Step-by-step tool output or invented memories |
| docs/AI_COLLABORATION.md | Authorship, approval and attribution process | Unreviewed claims of human or AI action |
| CHANGELOG.md | Concrete repository modifications | In-world chronology |
| AGENTS.md | Rules future AI assistants must follow | Character scenes or assistant roleplay |
Canon and creative material
| Location | Responsibility |
|---|---|
| CANON.md | Confirmed character and family facts |
| TIMELINE.md | Established temporal order and qualified undated snapshots |
| character/ | Buxbrew-specific details |
| family/ | The Amberbrew household, Bess, Arandor, Loni, Morkah and family traditions |
| relationships/ | Confirmed relationships and guild affiliations |
| places/ | Established family places and setting context |
| lore/ | Original family lore, Warcraft reference, disputes and continuity |
| journal/ | Actual/remembered gameplay and RP, clearly labeled |
| stories/ | AI-assisted story retellings and imagined family scenes, labeled separately from canon |
| assets/ | Approved images, screenshots and references with source information |
| archive/ | Superseded material preserved for traceability |
Documentation workflow
- Identify whether an input is a confirmed creative decision, AI proposal, canon fact, gameplay account, story example or open question.
- Record creative motivation and the broader intended experience in CONCEPT.md.
- Record rules for future writing in WRITING-GUIDE.md; do not write the fiction there.
- Put confirmed decisions and rejected approaches in docs/DECISIONS.md, distinguishing explicit choices from summaries.
- Summarize important iterations and actual AI work briefly in docs/DEVLOG.md; track files changed in CHANGELOG.md.
- Touch CANON.md, TIMELINE.md or character/topic pages only when the creative actually establishes or revises character facts.
- Keep the raw private discussion out of the public repository; summarize source-derived decisions without reproducing it verbatim.
Current scope: Storytelling has been explicitly requested as a new phase. Seven chapters have been drafted from previous discussions and the established family archive. Story-specific dialogue and incidental details do not expand canon without approval.
Continuity note
Loni is the older sister and Buxbrew the younger. Arandor is their father and Morkah their grandfather. Those established facts remain in CANON.md, not in a new fictional story.