U-ROCK® ACADEMY · EDITORIAL

The Editor's Desk — From the Wire to the Front Page

TRAINING SIGNAL ACTIVE
// ONE NEWSROOM · MANY FRONT PAGES

Gather once. Publish everywhere it belongs.

editor.urock.network is the network's newsroom. Raw material lands on the wire, becomes packets, packets become stories, and stories feed urock.today, the affiliates, the trade paper and the zines. Editors work their queue. The chief editor and HQ publish. Ten minutes here and the desk works for you instead of against you.

THE POSTURE IN ONE PARAGRAPH. The desk runs on one database and one direction of authority: editors edit, judge and flag; the chief editor runs the full desk, publishing included, with no HQ console; packet fan-out is HQ-only. Approval is not publication. Editors cannot delete; only HQ can delete — archive is reversible, always. And nothing goes to the public with a hole in it.
01 // THE STORY LIST

Archived leaves the mix — nothing leaves the vault

The main list shows working material only. Archived stories drop out of view the moment they're archived — pick archived in the status filter when you want the vault. Editors never delete records (only HQ can); an archive is a shelf, not a shredder.

02 // ASSET PACKAGES

Gather once, use many times

Packet fan-out is HQ-only. The fan-out route itself would accept a chief-editor seat, but editorial seats can't load the packet list, so in practice fan-out is HQ-only. Editorial seats (chief editor and editors) get 403 on packets; ask HQ to fan out. In the Wire view, the ASSET PACKAGES panel lists every packet sitting in READY. Each story has exactly one home: U-Rock® Today (urock.today), U-Rock® Radio Trade (URockRadio.today), COMMUNITY (the station page), or ESPORTS. Choose the one correct destination. Do not publish the same story to several homes. Rights land as review required until an editor clears them.

One interview, many outputs, one canonical trail back to the packet. The field gathering never gets repeated — that's the whole economy of the desk.

M01 // PUBLISHING A WIRE ITEM

Publishing a wire item

POST /api/content/wire/items/:id/publish with body {publication_destination, channel}. A publication_destination set on the wire item itself is ignored. Sign in as deskeditor@urock.network. Never use master_admin.

M04 // ONE HOME, PROSPECTIVE GATE

One home, prospective gate

Every story has exactly one home. The publish gate applies to new publications only. Do not reopen or re-gate stories that are already published.

03 // THE ARTICLE EDITOR

Image, tags, artist link — the three moves that matter

Image (optional) — Find Image opens the existing cleared-image picker from the U-Rock® Media Library. Review it, select it, pass the rights check, then insert it as the hero, or cancel. Use only images with established provenance and rights. A story with no image may publish text-only.

Tags — hit auto-tag: the desk derives tags from the channel, story type, scope, station and title keywords, then merges anything you typed. Add the extras, save.

Artist link — when a story is about an accepted artist, set the artist link (the canonical record). Exact links beat title matching everywhere downstream: rotation cards, artist pages, discovery.

04 // ZINES

One heading per station

Every station collapses under a single row: issue count and a view latest PDF link right on the heading. Click the row to unfold that station's full issue history. Weekly zines print from the stories each station actually published — its own paper, its own week.

05 // ROTATION COVERAGE GAPS — NO DEAD LINKS IN PUBLIC. A band card on urock.today only links out when a published story exists, and only shows a photo when the press photo is in. The Signals view carries the ROTATION COVERAGE GAPS panel naming every accepted artist still missing one or both. Clear the gap and the card lights up on its own. The public never clicks into a hole — that rule doesn't bend.
06 // WHO DOES WHAT

Seats see their job

Editors — edit, judge, flag. Their assigned queue only.
Chief editor — the full desk, publishing included, no HQ console.
HQ — assign, configure, fan out packets, and delete (delete is HQ-only). Publishing does not require HQ.
Head of programming — lives at program.urock.network and never needs this desk.

Permission rolls down, never sideways, never up. That's the tenet, not a suggestion.

M05 // REMOVAL, DELETE, AND KNOWN DESK GAPS

Removal, delete, and known desk gaps

Delete is HQ-only. Do not use Wire Desk Unpublish / Roll Back (it deleted a record 10/23).

Walk 10/26: PASS for login, wire list, Find Image, approval, and the publish/unpublish controls. FAIL for the wire item detail view, the source link on the wire card, and the destination selector. Until these are fixed, check the source through the API/record, and set the destination through the publish API.

07 // THE DOOR AND THE TABS

One door, eight tabs

editor.urock.network is the only editor door. The chief editor sees the full desk. Tabs: Newsroom (the queue) · Wire (ingest) · Zines · Feed (pins — keep it scarce) · Images (library) · Signals (thin alerts, not the newsroom) · Lineup (the day clock; empty means no lineup) · Network (lift only).

Programming is program.urock.network. Sales is sales.urock.network. Neither is this desk.

08 // WHERE IT GOES

Classify first, place second

Classify before placing: Community / Music / Trade / Network / Show / Commercial. A Wilmington community row does not appear on Phoenix. If the block is labeled Latest national stories, it may only show scope=network and distribution_level=network. Local rows stay on their affiliate until they earn a lift.

Commercial stays in Sales. Do not launder an ad through the newsroom.

M02 // ESPORTS DESTINATION

ESPORTS destination

ESPORTS is a live destination. Public feed: https://api.urock.network/api/public/esports/stories (also served at dashboard.urock.network). A story tagged 'pinned' returns pinned:true and sorts first; use it for the founding story. The Chief Editor has authority here; HQ is not needed.

How to publish today: set publication_destination=ESPORTS through the API. The desk has no destination selector (known defect). Leave channel blank: channel 'esports' is rejected (known defect).

Known gap: the eSports.urock.network page does not yet show a stories block, so a published story is visible in the feed but not on that page yet.

M03 // COMMUNITY STORIES AND LINKS

COMMUNITY stories and links

A COMMUNITY story's urock.today/s/<slug> link 301-redirects to its station page by design (rule GO1055-C). This is not a bug. The station reader renders the story from the feed body.

09 // MUSIC SUBMIT AND VIDEO

Selected, not applied — and video is a URL on the story

Announce an artist when they are SELECTED into discovery or rotation. Never publish “they applied.” Fetch audio belongs on the canonical submit record — the affiliate is not the download mule.

Station video sections take a YouTube or Vimeo URL on the story (source_url) plus a thumb. A raw link on the public page is a renderer bug. Report it to Technical.