This update added the first collaboration and access-control systems. Stories can now have multiple contributors working on the same project. Each story owner can invite other Talescape users and define what they are allowed to change.

The new Collaborators panel in Story Settings manages invitations and permissions. Each collaborator can be given rights to edit story content, publish new versions, or manage the media library. The owner always keeps full control of the story and cannot be removed.

The system includes an activity log that records all relevant actions inside a story. It tracks edits, uploads, and permission changes. This makes it easy to see who changed what and when. A comment system was added as well. Comments can be written on any element, including scenes, dialogue lines, and events. This allows teams to discuss specific parts of a story directly inside the editor without using external tools.

Permissions are stored per story and can be modified at any time. This structure makes it possible to work in teams where writers, editors, and artists collaborate in the same environment. It is also the first step toward larger studio projects with shared workflows and internal review processes.

This update added the first version of the internal validation and testing tools. The new Checks System automatically scans each story for structural and technical problems. It looks for missing media, unreachable scenes, incomplete dialogues, undefined variables, or incorrect marketplace data. Each issue is sorted by severity into informational notes, warnings, or failures. A story that still contains failures cannot be published.

Checks can be run globally for the whole story or locally inside individual editors such as scenes, chapters, or dialogues. Results are shown immediately with clear messages and timestamps. These same checks will later be reused in the automated review process when stories are submitted for release.

The second addition was the Debug Menu, available during Story Preview. It allows inspection and manipulation of the current story state while testing inside the editor. It includes tabs for logs, variables, and inventory. Logs display triggered events, variable updates, and dialogue progress. Variables can be viewed and changed in real time, and inventory contents can be adjusted to test conditions. All changes are temporary and reset when the preview stops.

Together, the Checks System and the Debug Menu form the first complete quality-assurance workflow in the editor. Stories can now be validated, debugged, and verified directly inside the tool before release.

I implemented the full Story Settings module. Each story now includes detailed metadata fields that define its language, tags, description, and visual presentation in the marketplace. Authors can set categories, language, and accessibility preferences directly inside the editor.

The new content section adds support for age groups and content warnings. Each story must now declare whether it is intended for All Ages, Teen (13 plus), Mature (16 plus), or Adult (18 plus). Warnings can be added for violence, death, horror, discrimination, or similar subjects. Stories that include AI-generated images, voices, or music can be flagged accordingly. This ensures that the platform can apply the correct visibility and moderation rules automatically.

I also added fields for story metadata such as description, thumbnail, screenshots, and tags. These will later be used by the marketplace to organize search results and listings. All of these settings are stored per story and can be updated at any time, although changes to metadata or content warnings will require a new release once publishing is live.

At the same time, I prepared the first systems for feedback and review. These are simple data structures for storing comments and ratings that will later connect to the publishing workflow. They will be used to handle moderator reviews and reader feedback once stories go public.

Together these changes complete the administrative side of story creation. Each story now has a defined identity, content rating, and moderation baseline. It is the groundwork for the upcoming release system and monetization features that will build on this data.