Review uncommitted schema edits

Author: jhull

HISTORY.md

@@ -5,6 +5,7 @@
 - Added an optional `story.ideation` object for pre-narrative concept development, with required domains `character`, `theme`, `plot`, and `genre` whenever `ideation` is present.
 - Added lightweight shared ideation node validation requiring `id` and `summary`, with open metadata for beginner and LLM-assisted workflows.
 - Added optional `narratives[].status` with canonical values `candidate`, `draft`, and `complete` to represent potential or in-progress narratives without splitting data into separate arrays.
+- Made `subtext.storypoints[].narrative_function` and `subtext.storybeats[].narrative_function` optional so blank-slate templates can omit narrative function assignment until later authoring.
 - Preserved backward compatibility for existing stories by keeping `story.ideation` optional and retaining `story.genre` as a concise top-level story label.
 
 ## Recent Canonical Terminology Updates

README.md

@@ -65,6 +65,10 @@ npm run validate:schema
 `examples/example-mapping.json` is a mapping fragment example, not a full schema document.
 Use [/VALIDATION.md](/VALIDATION.md) for validating your own NCP files and CI setup.
 
+## Templates
+
+- [Complete Storyform template](/examples/complete-storyform-template.json): blank-slate NCP fixture with canonical Storypoint Appreciations excluding `Event` and `Progression` labels, plus Signpost-only Storybeats (no Progression/Event Storybeats). `narrative_function` is intentionally omitted so teams can fill in only what they need.
+
 ## For Adopters (Self-Serve)
 
 If you found this repository and want to validate your own NCP JSON, do this:
@@ -97,6 +101,7 @@ narrative-context-protocol/
 │   ├── ideation-beginner.json
 │   ├── anora.json
 │   ├── the-shawshank-redemption.json
+│   ├── complete-storyform-template.json
 │   ├── example-mapping.json
 │   ├── invalid/
 │   │   ├── ideation-missing-domain.json

SPECIFICATION.md

@@ -246,7 +246,7 @@ These labels preserve authorial framing voice while retaining compatibility with
 ## Validation and Narrative Integrity
 
 To ensure integrity and consistency in narratives structured with NCP:
-- Storypoints and Storybeats must include canonical terms from schema enums.
+- Storypoints and Storybeats must use canonical terms from schema enums when `narrative_function` is provided.
 - Linear-focused and Character-framing Appreciations are both canonical-valid labels for holistic framing workflows.
 - Regardless of Appreciation framing, NCP normalization reduces these terms to canonical Story Goal / Story Consequence families for interoperability.
 - Linear stories should use linear-focused Appreciations; holistic stories may use either linear-focused or Character-framing Appreciations.

VALIDATION.md

@@ -33,8 +33,10 @@ npm run validate:schema
 This validates:
 
 - `/examples/example-story.json`
+- `/examples/ideation-beginner.json`
 - `/examples/anora.json`
 - `/examples/the-shawshank-redemption.json`
+- `/examples/complete-storyform-template.json`
 - Expected failures in `/examples/invalid/*.json`
 
 ## Validate Your Own NCP File(s)

docs/narrative-context-protocol-schema.md

@@ -105,6 +105,8 @@ Quick heuristic:
 
 ## Narrative Layers
 
+Each item in `story.narratives[]` is a Dramatica storyform: a single, complete argument structure within the story, expressed through `subtext` and `storytelling` layers.
+
 Each item in `story.narratives[]` contains:
 
 - `id`
@@ -181,9 +183,11 @@ Custom extension fields:
 
 Required keys per item:
 
-- `id`, `appreciation`, `narrative_function`, `illustration`, `summary`, `storytelling`, `perspectives`
+- `id`, `appreciation`, `illustration`, `summary`, `storytelling`, `perspectives`
+
+Optional canonical key:
 
-`appreciation` and `narrative_function` are validated against canonical enums in the schema.
+- `narrative_function` (validated against canonical enum when provided)
 
 Custom extension fields:
 
@@ -194,12 +198,13 @@ Custom extension fields:
 
 Required keys per item:
 
-- `id`, `scope`, `sequence`, `narrative_function`, `summary`, `storytelling`, `perspectives`
+- `id`, `scope`, `sequence`, `summary`, `storytelling`, `perspectives`
 
 Optional keys:
 
 - `signpost` (1-4)
 - `throughline`
+- `narrative_function` (validated against canonical enum when provided)
 - `custom_narrative_function`, `custom_narrative_function_namespace`
 
 `scope` controls allowed `sequence` range (enforced in schema):