Use cases · Why Onnie

Content creation

From brief to landed artifact

Content dies when briefs, drafts, and assets live in five tools. Onnie carries the editorial spine and the landed artifact — Canvas, Page, Image — in the same place.

Work · editorial arcPages · briefsCanvas · mood / layoutImages · assets

// who it's for

Solooperator + full pipelineSmall teamsshared editorial rooms

// friction

The pile isn’t a pipeline

Brief in one app, mood in another, assets in Drive, feedback in chat. Nobody can say what shipped without a meeting.

// on onnie

Work for the arc; artifacts for the output

Editorial Work (in a Project when multi-piece) holds status. Pages hold briefs. Canvas and Images hold visual residue. Skills and agents help craft — the room owns the publish call.

This is not “AI content factory.” It is one room where brief, mood, assets, and ship decision share continuity.

01Work · Projects02Pages03Canvas04Images05Skills · Agents

// workflow on the os

How a piece actually lands

Click each step. Spine in Work — visual truth on Canvas and Images — not five tabs and a hope.

Editorial Work — not a channel

Each piece (or campaign Project) has a real spine: goal, focus, plan. Status lives here — not in the thread that started it.

WorkProjects

// a week in the content room

Residue, not “where’s the latest file?”

MONSpine open

Campaign Project + editorial Work. Goal and focus set before tools scatter.

Projects · Work
TUEBrief locks

Page brief cited on Work. Must-says out of chat into the room.

Pages · Work
WEDVisual truth

Canvas mood + Images pins. Layout frame A selected for craft.

Canvas · Images
THUCraft + gate

Skill packs run. Needs you for voice and publish — not silent ship.

Skills · Agents
FRILanded

Hero live; cuts on Images shelf. Next piece reuses the room.

Images · Work

// proof · canvas content board

The campaign’s visual truth is already open

A Canvas content board — mood, layout frame, Images pins — bound to editorial Work. Not a dump. Not a spreadsheet of posts.

Launch moodboard · Q3
BoardPreviewVersions
Canvas · purpleProject · Launch kit
Canvas zonesImages pinsBrief bindresidue · not tool soup
MOOD · DIRECTION
Warm ink + purple accent
ink
accent
cool
alert
done
mute
Brief · Hero brief · Launch kit · Pages
IMAGES · PINS
Asset shelf in the room
hero_01Selected · frame A
cut_sq · 1:1Social pack
cut_story · 9:16Story pack
LAYOUT · FRAME A
Hero composition (ships from this residue)
Launch kit — Canvas holds mood + layout · Images pins are the shelf · brief Page and Work spine stay one click away · publish still needs you.

// nearby domains

Same OS, different residue

Peers that reuse Work + artifacts — different jobs and proof objects.

Product development
Ship with humans + agents
Client work
Delivery rooms that actually close
Sales & CRM
Pipeline work that stays shared

// faq

Common questions

Yes. Content runs as Work from brief to ship, with pages, canvas, and images as Artifacts the room reopens.

Land the next piece in the room

Open editorial Work, lock a brief Page, build the Canvas board — publish with residue still attached.

Start freeInstall Content skills