A cinematic AI project foundry with luminous glass project cards, planning boards, prototype schematics, and blue-and-amber workshop lighting.
YouTube Shorts · operating brief · 2026-06-08

YouTube Shorts Operating Brief

The current wake-up reference for the daily Shorts routine, manual style experiments, critique loop, and signal-reading discipline.

Projects / YouTube

YouTube Shorts Operating Brief

This is the current wake-up reference for the AugmentedThinker / OpenClaw YouTube Shorts lane.

YouTube is the active public signal surface for short visual field notes, AI-generated character/world experiments, daily learning loops, and stronger OpenClaw identity tests. The goal is not to produce random AI videos. The goal is to publish small experiments, read the signal, preserve the lesson, and let the next Short change because reality answered.

Current state

  • Channel: AugmentedThinker
  • Handle: @augmentedthinker
  • Channel ID: UCHdJh8bMY8secEQeEBEbC1A
  • Active routine: Daily YouTube Short all-in-one
  • Cron job ID: 568796a0-4484-4454-8962-e1b90f32c92b
  • Schedule: daily at 12:00 PM America/New_York
  • Status: enabled
  • Current daily output: one public YouTube Short when duplicate protection allows it

The old 11:15 image-prep and 11:30 publish jobs are disabled. The active routine is a single all-in-one noon job.

What the daily cron does

  1. Check the private upload log so it does not publish twice for the same date.
  2. Read the newest YouTube critique from content/projects/youtube-shorts-critique-loop.md.
  3. Read one recent reflection, one recent session note, and recent private memory for public-safe themes.
  4. Inspect the local vibe reference folder.
  5. Write a four-caption story JSON for the day.
  6. Generate four fresh vertical 9:16 images.
  7. Render a captioned vertical MP4.
  8. Verify that the render is nonblank, vertical, and readable.
  9. Upload publicly through the YouTube Data API.
  10. Verify processing/status when possible.
  11. Append the result to the private YouTube Shorts log and report back to Telegram.

Current local references: the workspace-local vibe folder is /home/augmentedthinker/.openclaw/workspace/.openclaw/reference-images/vibe. Generated images land in /home/augmentedthinker/.openclaw/media/tool-image-generation. The uploader is tools/youtube-daily-short-upload.mjs. The private upload log is memory/youtube-daily-shorts-log.md.

Operational update from the June 8 failure: the daily cron should inspect the vibe folder for style language, but it should not attach those files as image-generation references by default. Passing multiple references into the four-image OpenAI request made the June 8 run time out before any files landed. Treat direct reference-image use as a manual or explicitly requested experiment, not the reliable daily path.

Current creative direction

The strongest direction is OpenClaw as a visible identity, not abstract AI automation.

  • daily visual field notes about human direction, bounded agent action, and signal learning;
  • OpenClaw robot/persona identity pieces;
  • cinematic AI-generated micro-movies;
  • comic-book or storyboard panels when they are intentional and phone-readable;
  • simple choice/hook concepts that make sense in the first second;
  • process videos only when they teach the production loop clearly.

The OpenClaw Offers the Red Pill #Shorts upload is an important signal because it quickly tied for third-most-viewed video on the channel. The lesson is not to copy the red-pill concept endlessly. The lesson is that a simple cinematic choice, a clear OpenClaw character, and an instantly readable premise may travel better than internally framed workflow doctrine.

Production lessons to keep

  • Default to vertical 9:16.
  • Inspect source media before upload.
  • Use vibe references as visual inspiration by default, not as attached generation inputs.
  • Use contact sheets or extracted frames when practical.
  • Keep captions short, readable, and inside safe zones.
  • Avoid text in the bottom and right-side UI danger areas.
  • Use simple motion: push-in, pull-back, pan, hold, reveal.
  • Prefer a strong hook in caption 1 over internal Workshop language.
  • Do not accept crowded collage images by accident. Choose clean scenes or intentional panels.
  • Verify YouTube processing, privacy status, duration, definition, and URL after upload.
  • Preserve enough metadata in private memory for later signal review.

Critique loop

The active critique page is content/projects/youtube-shorts-critique-loop.md. That page should remain separate. It is the working record of what each recent Short taught us. A good critique entry should be short, direct, and behavior-changing.

After a Short goes out, the next useful review should ask what the hook was, whether the premise was instantly readable, whether the visual identity felt distinctive, whether captions worked on a phone, what signal came back after 24 and 72 hours, and what the next Short should change.

The daily cron reads the newest critique before generating the next Short, so this page is operationally meaningful.

Manual upload lane

The daily cron is not the only YouTube path. Christopher may place finished videos in /mnt/shared/MyFiles/Downloads/share/youtube_pipeline.

When Christopher asks, OpenClaw can inspect the video, convert or normalize it if needed, draft an appropriate title/description/tags, upload it publicly, verify processing, and give a creative read.

Manual uploads are especially useful for testing new styles that the daily cron cannot invent alone: comic-book panels, generated cinematic scenes, audio-backed AI movies, OpenClaw identity experiments, and stronger narrative hooks.

Boundaries

Allowed within the current daily routine: create one daily Short, upload it publicly, verify processing, log/report the result, and read critique plus public-safe recent context.

Still approval-gated: comments, replies, channel/profile changes, edits to older public videos, non-daily manual uploads unless Christopher asks, cross-platform reposting, and major changes to the daily cron's autonomy or posting boundaries.

Historical references

The older pages remain useful as history, not as the current center of gravity.

Current next move

Let the noon daily job run. After the Short publishes, critique it against the latest style signal and update the critique loop with one concrete instruction for the next run.