9. Prepare a private trial and publish a revision

Return to Lesson 7’s complete 0.5 pack. This download starts at revision 8 and finishes at revision 10, with a clearer description and the same stable IDs. Revision numbers need to increase; they need not be consecutive. This lesson does not ship a public 0.3–0.5 uploader or claim that these drafts have been played or published.

Keep the evidence with the work

Review the story text, every image and any sources. The included original teaching assets and checker have scoped reuse terms in LICENSE.txt; StoryOrbit branding and the private Playground toolkit are not included in that grant. For your own assets, record the actual author/source and permission. If you generated them with a tool, keep the required generation record and the real service/model details rather than inventing them.

The worked pack keeps provenance[].review: "pending", original basis, no fabricated source references, private visibility and a truthful rights statement. A successful local check is not a reason to change review to accepted. Complete the review through the authorized host workflow. Do not paste account tokens into a pack, screenshot, public issue or download.

Check the handoff

1. Run the structural checker against the exact bundled schema and retain its SHA-256.
2. Match each declared asset ID to a local file in media-manifest.json; confirm hash, byte size and MIME. When replacing art, update all three and check crops/frame alignment.
3. Use a compatible authenticated host uploader. It must support the actual protocol and feature revision, validate semantics, attach every declared asset, and report review issues before starting a trial.
4. If you have access to the separately distributed Playground, its check --schema-only covers its bundled contracts; its full check, new, HTML preview and submit remain 0.2 only. Do not run its submit command for this 0.5 example. Ask the host maintainer for the authorized State/VN submission path.

The downloaded checker needs no account. Service submission and private trials do. There is no browser player bundled with this lesson. The old Web Playground is archived; the current authoring toolkit is not a live VN reader.

A short private trial script

Start a fresh private journey. Confirm the opening image, Rowan’s identity, the three opening choices and neutral sprite. The legacy frames preserved in this download do not animate in current readers. Say you might help later: state should stay unchanged. Complete one care action, then another: moisture and trust should become 1, then 2, and the achievement should appear. Accept the offered seed in one turn, then leave: expect seed_home. Start another fresh journey and leave immediately: expect quiet_goodbye.

Also try declining, asking an unrelated question and reloading. Check suggestion relevance, stable state, reward visibility, paragraph/speaker alignment and accessible motion behavior on each supported reader. Record actual results, host/client versions, schema digest and any failures. These are instructions for your trial, not claims of an already completed live test. The site’s automated tests only rehearse authored observations and validate media/semantics.

Publish deliberately and revise safely

After rights/content review, successful host admission and private trial, use the host’s explicit publication action. Confirm the intended audience, cover, description and visibility there. Merely writing public in JSON or uploading bytes does not establish a published story.

For a later edit, preserve story/entry IDs and unchanged outcome/badge identities, increase manifest.revision, recheck assets and anchors, and trial the new revision before publishing it. For changed earning conditions, ending priority, reward artwork, badge links or Pin recipes, assign new outcome/badge IDs and update references; reuse of an existing identity with different semantics is rejected as PROGRESSION_ID_REUSED. Keep the previous pack and exact schema. Existing journeys retain their starting revision; verify a new journey sees the new one.

If the service rejects the draft, keep the actual issue report. Troubleshooting separates JSON errors, semantic issues, media problems and unsupported tooling so you can fix the right layer.

Complete lesson download · 0.5 → 0.5 · revision 8 → 10

Download start + finished packs, media and checker (.zip · 31 KB)

Includes exact schemas and reuse terms. No account or API key is needed for local structure checks.

Verify this download

SHA-256: 22bfc25dbfc8e0725b259bc87c15ccb80101fead535f6d97ea3b1f9fc6a07bc2

0.5: 18756b09a11f4f234d1e2fcd5237a93be0b4bad8f9afae7d2a99243d7d9cd959

The original teaching artwork

Static previews of the actual downloaded images. The sprite frames are shown separately for comparison; this is not a live player.

greenhouse_art

rowan_neutral

seedling_reward

rowan_smile

rowan_blink

rowan_talk

Check your work locally

From the extracted bundle folder, create the environment and install the pinned dependencies once. Then check both files, and repeat the start check after your edits. The same commands work for every lesson.

macOS / Linux

python3 -m venv .venv
.venv/bin/python -m pip install -r requirements.txt
.venv/bin/python check.py start/pack.json
.venv/bin/python check.py finished/pack.json

Windows PowerShell

py -3 -m venv .venv
.venv\Scripts\python.exe -m pip install -r requirements.txt
.venv\Scripts\python.exe check.py start/pack.json
.venv\Scripts\python.exe check.py finished/pack.json

Expected for the finished pack: Structural check passed: Creator Pack 0.5 followed by the exact Schema SHA-256. This is a structural check, not host admission or a live playtest.

Working excerpt from the finished pack

This excerpt is generated from the tested download. It is not a complete pack; edit the named fields inside start/pack.json or compare finished/pack.json.

{
  "revision": 10,
  "visibility": "private",
  "rights": {
    "basis": "original",
    "statement": "Original teaching material under the included reuse license; this draft still needs its own review before publication."
  },
  "provenance": [
    {
      "path": "",
      "basis": "original",
      "review": "pending",
      "source_refs": []
    }
  ]
}

Look up the fields: provenance · publication

Return to the learning path