Skip to content

Publish metadata

scene-studio doesn’t upload video automatically. The last step goes only as far as making the publish metadata. publish-copywriter makes metadata like the title, description, hashtags, and thumbnail candidates in publish.md, and the platform upload is done by the user.

On both tracks, once the last gate is cleared, publish-copywriter makes publish.md. The metadata needed for per-platform publishing gathers here. The video file is in video_drafts/, and the publish metadata is the text paired with that video.

There are two reasons it doesn’t auto-publish. A platform upload involves account authentication and policy agreement, and video is a spot that, once up, gets exposed to the algorithm, so a human’s final judgment is needed (S8). So the base makes only the metadata and leaves the upload in the user’s hand.

The global-virality skill helps a publish that favors the global algorithm. When _workspace/globalization_decision.json is active, the policy is planted at every stage.

  • Dialogue-free first: video with no language barrier
  • English subtitles first
  • Romanized character names
  • Language-neutral BGM
  • English-first publish metadata

This decision is made once in the brief and applied at every stage. It’s a policy that targets the spot where the global algorithms of TikTok, Reels, and Shorts favor dialogue-free, language-neutral content. For a channel targeting only the domestic market, turn this flag off.

The publish-meta skill enforces the publish-metadata format. Because the two tracks use the same format, the publish metadata of a generative video and a remix video stays consistent. If the title or description contains a real name, phone number, or real address, it’s auto-detected and masking is recommended. It doesn’t mask automatically. Whether to publish is the user’s call (S6).

A remix video auto-attributes the source per license-policy. The source is planted in the publish metadata, reducing copyright disputes on upload. This isn’t a metadata-stage thing; it’s a spot license-policy planted at every stage, and the publish metadata reflects the result.

The next section is updates. It covers the spot where the base’s new skills or updated policies are brought safely into a fork.