newsroomfloor.com

The desk account's tier and its caps: properties, topics per paper, articles a day, model, images, ads, support, and bring-your-own-key.

The day's story budget: the lines the newsroom filed today, newest first, each with its section, through-line and compose kind.

The desk's full setup: nameplate, motto, the automation (cadence, prompt, template, model, articles a day, source floor, window, composition, sources, the swimlane) and its sections.

Change any part of the desk setup.

Add a section, or edit one by passing its current name as `orig`.

Remove a section by name.

Hire a writer for the masthead.

Edit a persona by slug.

Remove a persona by slug.

Write and file up to a few pieces now, on the model your plan funds.

Start another paper under the same account, up to the plan's property cap.

Turn the public paper on or off.

The stories currently on air for this desk, newest first, each with its byline, sources count, and receipt pointer.

One story in full: its prose, byline, and the cited facts it stands on, each with its source and claim key.

The signed filing receipt for one story: the Ed25519 commitment for the last publish.

This newspaper's email subscribers.

Add up to 20 email subscribers to this newspaper (admin key).

Put a specific draft or held story on air now.

Withdraw a published story from every surface.

Move a published story to a different front-page section (an island town wrongly filed under "us news" back to "puerto rico").

Set a specific story to publish at a future time (ISO 8601).

How the paper is drawn: the named look it wears (from the gallery) and its overrides, the resolved look (layout, theme, the front's bands top to bottom, flags, the front's numbers), and the gallery of named looks.

Wear a named look (`id`: standard, wire, magazine, blog, foundry) and/or override any part of it: layout, theme, bands (the front's bands top to bottom; a band left out does not render), flags, the news numbers, decor.

Search the signed fact record the papers cite: a keyword leg over the record's own door plus a meaning leg, merged.

Every folder the desk's owner keeps: its id, name, tags, how many facts it holds and which papers it feeds.

One page of a folder's facts, with the total so you know how much is there.

Make a folder to keep facts in.

Change a folder's name or tags, or set archived.

Put one fact in a folder: a statement you found with search_record, or your own typed note with an optional source.

Move one fact from the folder it is in to another the same owner holds.

Remove one fact from a folder.

Point a folder at the papers whose writers may cite it.

The custom RSS/news feeds the owner has added to this desk, each with its url, title, the door's feed id and when it was filed.

File a custom RSS/news feed for this desk through the tenant door - the poll, distil and land is the door's; this desk's writers then cite it.

Stop and drop a feed you added, by its `url`.

The desk config, whose `signal_desk` key carries the whole Signal Desk setup: whether the property runs as a private Regulatory Signal Desk, the FEEDS it stands on (`sources`: each one's dataset, table, origin, how and when it connected, its share, its key state as `key.set` with a fingerprint, its record `shape` (meeting-record/1, or cp-meeting-zip/1 for the data partner's own meeting zip), and its live record and signal counts), the supply chain readers are told about, who may read it, the watch sections, the meaning-search floor and the digest cadence a new watchlist opens on.

Turn this property into a private Regulatory Signal Desk, or change how it runs.

Drop exactly one feed from this desk: the desk forgets that feed's data key, marks its share revoked and removes it from `sources`.

The reader roster of a private Signal Desk: the desk's own seats, which always read it, and every address with a reader seat on it and nothing else.

Put an address on the Signal Desk's reader roster AND send them the invite: a branded email naming who gave them the seat and what the desk is, with one button to create their DRM3 account at this address (the platform sign-up with the desk pre-provisioned, so the first sign-in lands on the desk); the admin who invited them is copied unless invite_copy is off.

Revoke an invited address.

Send the Signal Desk digest to every reader who signed up for it, at once, whatever the schedule says: each one gets the signals filed since their last digest, across every section and feed, newest first, with a link to each signal's page.

Send the desk's admin a test of one Signal Desk mail so they can see it as a reader would: kind invite (the reader invite, as if they had invited themselves; nobody is copied and the roster does not change) or kind digest (the last ten signals on the desk; no reader's digest moves).

The desk digest's signups: every address, the cadence each chose (daily, weekly, or off), when they signed up and when they were last sent, plus the desk's own schedule (signal_desk.digest) and the counts.

The numbers the console's Analytics page draws, as JSON.

The paper's vitals at a glance, the same four numbers the /floor card shows, as JSON: subscribers (confirmed and unconfirmed newsletter signups), admins (the count and the admin seats' addresses and status), views (reads today, over 7 days, over 30 days, and the signed-in share), and articles (on air now and total on the desk).

A short answer from THIS desk's own record: the question is matched by meaning against the desk's signals (the same search the front runs, at the desk's floor), the top passages go to the model and nothing else does, and every sentence of the answer cites the signal it stands on (`cited`, with each signal's page).

A 120 to 200 word brief of what is NEW: on one watchlist (its matches by meaning that went live after its last alert) when you pass watchlist_id, else on the whole desk since the owner's last digest.

One paragraph from THAT signal's transcript segments and nothing else, every sentence cited to a transcript moment (`cites`: the speaker, the seconds into the video, and the video deep link when the record carries one).

Read EVERY feed this desk stands on, each through its own data key, and file one signal story per source row, tagged with the feed it came from (the result and the log carry per-feed counts: rows read and signals standing on them): the headline is the action the body took, the page behind it carries the source record and a link into the moment.

The record of this desk's signal builds, newest first: who ran each one and how, how many source rows it read, how many signals it filed, adopted or retired, how many vectors it indexed, where it stopped, the refusal if it failed, and `sources_json` with each feed's own counts.

The paper as the operator console lays it out.

Every domain of the paper's own with its lane (one CNAME to us, or a zone hosted with us), its live status in Cloudflare's own words, and the one record the owner was shown.

Put the paper on its own address.

Re-read the domain against Cloudflare and advance it (a CNAME seen, a certificate issued, nameservers moved, a route attached).

Take the domain off the paper: the hostname, our route and the records we made go; a zone is never deleted.