[codex] add NCP semantic grounding#19
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
NCP_SEMANTIC_GROUNDING.mdand links it from the README for AI and tool consumers.The new guide explains how NCP consumers should preserve Dramatica-informed meaning while reading, writing, or transforming protocol data. It covers:
Character Intentions,Character Repercussions,Dissonance,Relief,Friction, andAccommodationWhy
As more developers and writers feed NCP files into LLMs, the schema alone is not enough to prevent semantic drift. Models tend to flatten Dramatica terms into generic storytelling concepts: Main Character becomes hero, Objective Story becomes plot summary, Storyform becomes a beat sheet, and Holistic labels become vague emotional language.
This document gives adopters a public, protocol-safe grounding layer. It helps tools interoperate with NCP more accurately by explaining how to carry Dramatica-informed meaning across systems without turning the schema into a general-purpose theory manual or product workflow guide.
The goal is straightforward: make NCP easier for external tools and AI systems to consume while keeping terminology precise, portable, and aligned with the protocol.
Validation
git diff --check HEAD~1..HEADnpm run validate:schema->Schema validation checks passed (8 valid + 11 invalid fixtures).