Borrowed Tomorrow
Project library

Launch plan and production readiness

Before publishing the first video

  1. Check working channel name/handle and potential mark conflicts. The website is a concept library, not proof a YouTube channel exists.
  2. Perform Episode1 aloud. Mark breaths and actual duration. Create a 60–90-second ORIGINAL pilot from its opening with no source frames or voice imitation. Runtime remains unknown until performance.
  3. Lock original character silhouettes, room geography, props and lighting; make 6–10 varied pilot shot intentions, not a render-ready shot count for all episodes.
  4. Discover account-specific image/voice/music capabilities, exact executable IDs, rights and costs. Obtain operation-specific generation approval and a spend cap. No media spending is currently authorized.
  5. Build and test a frame-manifest validator before any paid production. The downloadable skill specifies its contract but contains no executable validator.
  6. Time actual narration, align half-open frames, review generated/owned assets and provenance; measure final loudness/true peak against chosen distribution spec. Watch/listen to the entire local render.
  7. Complete three episodes before announcing a provisional weekly release. If production cannot sustain it, release less often rather than recycle weak filler.
  8. Use fictional-story labeling, accurate titles, accessible captions, and chapter/playlist navigation. Do not claim the narrated events are real.

Practical episode assembly

Cold open on a concrete wrong thing; establish the need through action; reveal costs through people and evidence; make the protagonist choose; finish the advertised transaction; use the last consequence to motivate the next episode. This is a review lens, not a forced identical beat order. Each episode's production notes supply visual beats and thumbnail concept; these are not a timed storyboard. Actual narration determines frame allocations.

Per asset retain input/source, license/permission, exact prompt and model ID, job ID, cost/currency, path/hash, reviewer and status. No credentials belong in this ledger. File-delivery publication is independent of permission to generate media or upload videos.

Creator effort versus engineering effort

Planning estimates, not measured effort or quotes. Assume one supervised pilot, a familiar local compositor, verified provider access and a competent editor. Revision volume and character continuity can multiply work.

Work Human writing/art/review Engineering/integration Model spend
60–90-second pilot 1–3 creator-days for performance, original art direction and review 3–6 engineer-days for validated manifest, one provider integration, compositor and technical QA Unknown; obtain live account pricing and retry budget before approval
Repeatable production runner Creator review remains required per asset/episode Additional8–15 engineer-days for job tracking, idempotent retries, ledgers, render queue and QA Unknown; automation is not spend permission
Polished6–9-minute episode Approximately4–9 creator-days or more after text drafting; target runtime is not timed audio Pipeline reuse reduces incremental engineering; failed formats/integrations add work Unknown until actual shot/voice/revision plan
Season of15 Do not multiply an optimistic pilot into a guaranteed schedule; sample at least two episodes first Do not build a large runner before the pilot proves the format No current authorization

Editorial checks

Channel discovery and business hypotheses

Use honest impossible-service titles, season playlist, pinned next-episode comment only when the next upload exists, and end screens with a real destination. Short teasers can dramatize one choice and lead to the full story without fabricating scenes. Potential later revenue: platform advertising if eligible, optional story collections or supporter extras after audience demand—not promised earnings. Avoid sponsorships that make fictional predatory financial services look like real advice. Validate audience fit with pilot comprehension/satisfaction, not only clicks.

Readiness statement — 2026-10-30

Text development and website publication only. No final images, narration, music, video, timed manifest or executable validator delivered. Thumbnail CTR, commercial name availability, provider licensing/cost and actual runtime remain unknown. Do not label this package render-ready or production-certified.