Blackwing Book a demo

Book a demo

See it live.

Thirty minutes, on your own material if you want it. You’ll see the whole line — monitor, draft, review, approve, publish — running against a real archive. Not a slide about it.

What the half hour covers

A working session against a running system. Bring a story you’ve already published and the session is built around it.

  1. Monitor

    The day’s articles scored against a published archive, and the number it used to decide. You’ll see which publishers it’s allowed to read, and what changes when that list changes.

  2. Draft

    A draft built from the closest past coverage in that archive, in the format the story type uses, with the same story from several outlets reconciled side by side.

  3. Review

    The three checks run on a real draft — grounding, compliance, house style — with every finding painted onto the line it’s about.

  4. Approve

    Sign-off routed and cleared from a phone with no login, and an approval flagged stale the moment the story changes underneath it.

  5. Publish

    The edition frozen at a permanent address with a record of who cleared what, and the export that goes to whatever you publish with.

The checks flag. They never rewrite. Your editors fix.

What to bring

None of it is required. It’s the difference between watching a demo and judging one.

  • A document you’d actually work from — a transcript, a speech. It gets dropped in and drafted from.
  • Two or three editions you’ve already published, to read a draft against. The comparison is yours to make.
  • The rules you’d hold a draft to, and who signs one off.
  • Your security reviewer’s questionnaire, if there is one.

If you’re the security reviewer

The security page states the architecture in the terms a questionnaire asks about — how customers are separated, how files are encrypted, what’s recorded, how model access is controlled — and says plainly what doesn’t exist yet. Read it first and bring what it doesn’t answer.

Read the security page →

Send the details

Seven questions, so the session is built around what you publish rather than being a general tour. What you publish now, and the last question, are the two that change what you’re shown.

Everything is required except the last.

Whatever your team calls it.

A daily internal briefing, a weekly roundup, an executive update, a client newsletter — and roughly how often. Up to 200 characters.

A screen you want to see, a question from your security review, or a story of your own to try it on. Up to 300 characters.

What this button does

It opens a message in your own mail app with your answers already written in, addressed to one mailbox. Nothing is sent from this page, and nothing you type is stored here — until you press send in your own mail app, it hasn’t left your device. If your device has no mail app to open, and plenty of managed desktops don’t, the message also appears on the page, ready to copy, with the address beside it.

What this site collects →

Or write it yourself

Send the same seven answers to the address below and it reaches exactly the same place. The form only saves you the typing.

Casey@DeployIris.com

Replies come from the same address.

Monitor. Draft. Review. Approve. Publish.