September 13, 2026
Going wide with Studio Conners
Can we get the Studio Conners production pipeline up?
What came of the day
The Studio Conners production pipeline is up: ObsessOS now feeds a clear Project → Work Entry publishing system in the Studio Conners Back Office, with Projects acting as durable containers, Work Entries carrying the public version of each day’s work, and Distribution built in as an optional but intentional handoff stage centered on reusable outward-facing artifacts such as vertical video. We also clarified the larger operating model: future in-house Obsessions should be worked with distribution in mind from the beginning, while Studio Conners handles the publishing and eventual social-channel automation.
The story
We started the day with a practical goal: get the Studio Conners production pipeline working well enough that finished ObsessOS work could move cleanly into the Back Office and eventually out into the world. MILITAXI became the first real test case. Rather than treating this as another design exercise, we used an actual finished Obsession and worked through what Studio Conners should receive from it. That quickly exposed an important distinction: the ObsessOS Exhibit is the full canonical record of the day, while the Studio Conners Work Entry should be a smaller public-facing version of that work. The two systems should complement each other, not duplicate each other. That led us to simplify Projects. A Project does not need its own parallel hero image, summary, and evolving write-up. It is the durable container that gives a body of work continuity. The actual published substance lives in Work Entries. An Obsession produces a Work Entry, and Work Entries accumulate into a Project. As we tested the real Back Office flow, we also found and fixed practical problems. The hero image workflow was not suitable for real use, so we added proper upload behavior and safer validation. We then stripped unnecessary editorial fields out of Projects and made public Project pages derive their current presentation from their latest published Work Entry. The biggest shift came when we examined Distribution. The original Channel Drafts idea felt too passive and too much like storing temporary copy. We realized that distribution has to begin earlier than the end of the publishing process. For relevant in-house work, the Obsession itself should be worked toward something people can actually encounter. That led to a much stronger model: create one strong outward-facing artifact during the Obsession—often a short vertical video—then let Studio Conners package and distribute that artifact across the channels where it fits. A MILITAXI video, for example, could become a YouTube Short, Instagram Reel, and TikTok, while supplying stills or clips for other channels. The creative act belongs in the Obsession; the mechanical act of publishing belongs in Studio Conners. By the end of the day, the pipeline was no longer just a way to move a summary from ObsessOS onto a website. It had become a clearer operating system for how Studio Conners can take a day of focused work, preserve its full story, distill what is worth showing, and eventually send that work much farther into the world.
Discoveries
ObsessOS Makes the Work; Studio Conners Ships It
ObsessOS and Studio Conners have distinct roles. ObsessOS is the canonical production record of what happened during an Obsession. Studio Conners takes the parts worth showing, turns them into a public Work Entry, and becomes responsible for getting that work into the world.
Projects Are Containers, Not Another Editorial Layer
A Project does not need its own hero, summary, or evolving narrative separate from its Work Entries. Its purpose is identity and continuity. An Obsession produces a Work Entry, and Work Entries accumulate into a Project.
A Work Entry Is a Distillation, Not a Second Exhibit
The ObsessOS Exhibit answers “What happened?” while the Studio Conners Work Entry answers “What is worth showing?” Trying to recreate the full Exhibit inside Studio Conners creates unnecessary duplication. The public version should be smaller, clearer, and deliberately edited for someone outside the studio.
Distribution Should Influence the Obsession Before the End
Waiting until an Obsession is finished to think about social media makes distribution an optional afterthought. For relevant in-house work, the Obsession should be worked with an outward-facing result in mind from the beginning, without allowing individual platforms to dictate the creative work.
One Strong Artifact Can Carry the Work Much Farther
Studio Conners does not need to create separate content from scratch for every social channel. A single strong artifact—often a short vertical video—can become a YouTube Short, Instagram Reel, and TikTok, while also supplying clips or stills for X and Threads. The goal is to make one thing worth showing and then adapt it.
Distribution Is Production; Posting Is Operations
Creating the video, image, demonstration, or other outward-facing artifact is meaningful creative work and can legitimately be part of the Obsession and its Exhibit. Logging into services, uploading files, publishing posts, and recording URLs is operational work that belongs in the Studio Conners Back Office.
The Work Entry Can Become the Publishing Handoff
A completed Work Entry can eventually contain everything Studio Conners needs to ship the work: the public story, hero, primary distribution asset, channel-specific packaging, and publishing state. This creates a clean handoff from the creative Obsession to an automated publishing system without requiring ObsessOS to become a social-media manager.
Results
Studio Conners Production Pipeline Established
The Studio Conners Back Office now has a working production path for taking completed ObsessOS work into Projects and Work Entries, preparing a smaller public version, and moving it toward publication and distribution.
studioconners.com/Projects + Work Entries Publishing System
Studio Conners now has a durable Project → Work Entry model. Projects act as thin containers for ongoing bodies of work, while individual Work Entries carry the actual published result of an Obsession. Public Project pages derive their current presentation from their published Work Entries rather than maintaining a duplicate editorial layer.
MILITAXI First Real Pipeline Entry
The September 12 MILITAXI Obsession was brought into the new system as the first real in-house Concept test. A MILITAXI Project and the Work Entry “What is MILITAXI?” now exist with its ObsessOS provenance, public title, summary, story, hero image, and Exhibit connection preserved.
Public-Version Workflow
Work Entries now explicitly separate the full ObsessOS source Exhibit from the smaller version Studio Conners shows publicly. The editor supports a public title, short summary, single readable public story, hero image, optional CTA, and optional link back to the full public ObsessOS Exhibit.
Working Media Upload Flow
The Work Entry hero-image workflow was corrected so images can be uploaded properly rather than being stored as oversized embedded data. Validation now protects against invalid data/blob URLs and provides usable error messages.
Distribution Handoff System
The former Channel Drafts area was replaced with a real Distribution stage. Work Entries can now carry an optional Primary Distribution Asset—designed especially for reusable vertical video—plus channel-specific distribution records for YouTube Shorts, Instagram Reels, TikTok, X, Threads, LinkedIn, and other destinations. Distribution remains optional and does not block publication.
Live Back Office Upgrade Published
The day’s Studio Conners Back Office changes were built, verified, and published, leaving the live system ready for continued use with the new Project, Work Entry, public-version, and Distribution workflow.
studioconners.com/office
Open threads
- Connect Studio Conners to the relevant social-platform APIs so the Back Office can publish Distribution packages and record the resulting URLs automatically.
- Decide exactly how Distribution Intent should become part of the beginning of future in-house Obsessions so the work naturally moves toward something worth sharing.
- Complete the first full real-world publishing cycle with MILITAXI, including a primary distribution artifact and outward social distribution.
- Test the remaining Work routes—Concept Work, Concept Became Original, Original Work, Outreach, and Client Studio Day—with real projects rather than fixtures.
- Refine how channel-specific adaptations such as stills, alternate cuts, titles, captions, and other derived assets should be represented once we begin distributing real work.