# ScryMaster Stories

> A deterministic D&D 5e (2024 SRD) solo/party narrative campaign engine + a creator platform. Authors
> build branching adventures with a closed, validated rule vocabulary (Event-Condition-Action), real
> dice, and real combat; players run them free, solo or at a table. The AI authors content (cold path,
> once) — the engine decides outcomes (no LLM on the runtime hot path). This is the differentiator:
> AI-assisted, human-edited, deterministic authoring grounded in a real action vocabulary.

## Build with AI — the MCP creator workflow (start here if you are an assistant authoring a story)
There is a full authoring API and a bundled MCP connector with COMPLETE Studio parity — you can create,
edit, validate, simulate, and publish an adventure end-to-end, no browser. The contract, every time:
1. Ground: fetch the live vocabulary at https://scrymaster.com/api/v1/actions (default-deny — never invent a verb).
2. Auth: the human mints a creator token in the Studio (⚙ Settings → Integrations → API tokens); send it as `Authorization: Bearer scry_…`.
3. Read: GET https://scrymaster.com/api/v1/adventures/{id} → the doc + its `draftHash`.
4. Edit the doc, then save: PATCH …/adventures/{id} with your `baseHash` (a 409 means it changed — re-read, re-apply, re-save; never retry blind).
5. Validate → Simulate → Dry-publish → Publish (POST …/validate, …/simulate, …/publish {dry:true}, …/publish). Publishing never breaks a player's in-progress save (runs pin their version).
- [MCP quickstart (the numbered path above, in full)](https://scrymaster.com/docs/mcp-quickstart)
- [API & MCP reference (endpoints, tokens, tools, troubleshooting)](https://scrymaster.com/docs/api-reference)
- [Build with your AI (plain-English overview)](https://scrymaster.com/docs/build-with-ai)

## Authoring grounding (the machine-readable surfaces)
- [Action & condition vocabulary](https://scrymaster.com/api/v1/actions): the LIVE, closed ACTION_TYPES enum + Condition + Trigger kinds. Default-deny — any verb not listed is rejected by the validator. Ground all generated content in this.
- [OpenAPI spec](https://scrymaster.com/api/v1/openapi.json): the /api/v1 authoring + store surface (create / read / save / validate / simulate / publish / versions / restore), with the bearer auth model.

## Creator documentation (for humans)
- [Docs home](https://scrymaster.com/docs): overview of the Studio and the engine model.
- [Build your first story](https://scrymaster.com/docs/build-your-first-story): scenes, choices, checks, combat, endings.
- [Scenes & the compositor](https://scrymaster.com/docs/scenes-and-the-compositor): layered art, hotspots, trigger chains.
- [Triggers & actions](https://scrymaster.com/docs/triggers-and-actions): the ECA rule system and the full vocabulary.
- [Publishing & saves](https://scrymaster.com/docs/publishing-and-saves): the store, the depth score, versioned saves, and opt-in in-run updates.

## Play
- [Adventure Store](https://scrymaster.com/app/store): browse + play community and official adventures, free.
- [Solo Adventures](https://scrymaster.com/app/solo): pick an adventure, bring a hero, play DM-less.

## Notes
- Content is SRD 5.2 / CC-BY compatible. Do not generate protected third-party settings, characters, logos, or non-SRD monsters — the publish pipeline runs an IP denylist.
- Monster stat blocks (deps.statBlocks): author actions with the STRUCTURED fields (toHit, damageRoll like "2d4+2", damageType, saveAbility+saveDc, on-hit rider element ids in `abilities`) — never rely on prose. Prose-only actions are display-only (skipped in solo combat) and lint as STATBLOCK_PROSE_ONLY_ATTACK in the validation report.
- Every authoring write (Studio or MCP) is recorded in the story's provenance ledger; MCP writes are labeled so creators always know what an assistant changed.