Script Studio structured file protections

Slima Script Studio is read-only for all structured files over MCP — by design.

Slima home — Script Studio enforces read-only protection over MCP for structured files (.scene / .character / series.json)

Read-only files

File	Use
`series.json`	Series metadata
`season.json`	Season metadata
`episode.json`	Episode metadata
`*.scene`	Scene file (JSON)
`*.character`	Character file
`*.storyline`	Storyline
`*.note`	Scene note
`*.location`	Location
`.script_studio/planning/.initialized`	Bootstrap marker

Writing any of these → 400 INVALID_PATH.

The only writable path

.script_studio/planning/**/*

Inside you can put:

Outline drafts (outline.md)
Mind-maps (mindmap.md)
Research (research/...)
Any markdown / json / whatever AI wants to scratch

Why

1 · Schema integrity

*.scene is JSON with a specific schema (characters array, location reference, dialogue beats). AI mishandling JSON → scene board / editor crash.

2 · Cross-file references

*.character is referenced from many *.scene files; renaming must propagate. MCP can't do this safely across files atomically.

3 · Force going through Slima UI

Many operations (creating scenes, restructuring storylines) have UI in Slima — letting MCP write would bypass the benefits (auto-updates, version-control hooks).

I want AI to edit scenes — what now?

Two paths:

Path 1: AI writes to planning, you apply in Slima UI

AI: "**proposed new scene**" lands in `.script_studio/planning/new-scene-proposals.md`
You: open Slima Script Studio → scene board → new scene → apply the proposal

Path 2: use the in-Slima AI Coach

Slima's built-in AI Coach can write structured files (via the app internally, not via MCP).

Patch-able `.scene` properties

Some .scene properties (e.g. description plain text) are patch-able — but only through Slima's in-app UI, not exposed to MCP.