One person approves one exact revision for one place.

An approver signs off one exact revision for one destination, an edit sends it back, and live means the destination confirmed it.

One approval is required before any piece leaves.
Approval binds to a revision hash and a destination.
A queued job never reads as a live page.

Why freelance women in Delhi and Bengaluru are still chasing 60-day-old invoicesRevision 2 of 2, edited by Harsh Songra yesterday

Changes requested

Revision: 2 of 2 · c4e2b71
Sources: 4 linked
Dollop: Complete

AngleHarsh Songra, on paragraph 1

Good idea, boring hook. Open with the invoice that is 60 days late, not with the category. The number is the story.

Approval binds to c4e2b71. A later edit returns the piece to review.

Roles decide who can release a piece.

Permissions come from your signed-in session, so Oat's agents never hold a publishing credential, and people release what Oat prepares.

Roles

Owner manages access and policy.
Editor edits, comments and submits.
Approver signs off one exact revision and releases it.

An approval names a hash and a destination.

An approval records the revision hash, the destination, who approved and when, and an edit afterwards returns the piece to review.

The approved revision goes to WordPress, Vercel or GitHub.

WordPress receives a draft, Vercel gets a deploy hook Oat watches, GitHub gets a commit on your branch, and every workspace can export Markdown and HTML.

DeliveryThe hostel curfew, priced in missed shifts. Revision 9a30c2e, your site.

Export queuedRevision 9a30c2e approved for your site (WordPress draft)10:42
ExportingDraft created on your site, post id 284110:42
ExportedMarkdown and HTML written to private storage10:42
LiveYou published the draft in WordPress. Oat checked the public URL.11:07

Had the site not answered, this line would read Outcome unknown, and Oat would say so until it could check.

The state on screen is the state at the destination.

A piece shows as live only when the destination confirms it, and a retry runs under the same intent, so nothing publishes twice.

Delivery states

Deploying: The site is rebuilding and Oat is watching.
Live: The destination confirmed the page is public.
Outcome unknown: The destination did not answer, so Oat keeps checking.

Every action stays on the record.

Approvals, revisions, comments, role changes and deliveries are logged with who and when, and the log never copies your writing.