Stage a social post in its live composer

Why use this

1. A post that looks correct in a document can change meaning when pasted into a live composer: line breaks collapse, link previews differ or the active account is not the intended publisher. The final interface also places publication controls close to ordinary editing actions.

2. A staging checklist could make the destination, exact text and stopping point explicit. The owner could inspect the composed draft in context while keeping approval to enter text distinct from approval to publish it.

Why an agent / simpler alternative

Useful judgment

Notice presentation changes and account-context mismatches before an otherwise approved draft becomes public.

Simpler alternative

Copy and paste manually when the post is short and the owner is already in the correct composer.

Unsuitable when

The interface lacks a dependable draft-only stopping point or the intended account is uncertain.

Proposed inputs

1. Name

   Approved draft text

   Owner

   Content owner

   Minimum scope

   Exact post copy, permitted links and formatting intent

   Quality check

   Identify wording that must not be rewritten.

2. Name

   Destination instruction

   Owner

   Account holder

   Minimum scope

   Verified account, composer and staging-only permission

   Quality check

   Separate posting audience from account display name.

Access and setup — proposed or unknown

Proposed minimum

1. Mock composer description and a local staging plan; no live account access.

Compatibility unknowns

1. Unknown: current runtime, browser behavior, draft persistence and accidental-publication safeguards.

External actions requiring approval

1. Account access and drafting in the live composer; publication, attachments and audience changes require their own approved scope.

Expected deliverable and review checks

Proposed artifact

Staging preview with exact text, destination identity, link-preview questions and explicit stop point.

Critical checks

1. The staged content matches the owner's approved text and intended account.

2. No publish, schedule or send action is included in staging.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   The composer is open under a different account.

   Why it matters

   Even a draft may be stored in an unintended workspace.

   Proposed response

   Stop before entering text and verify the authorized destination.

2. Signal

   A pasted link creates a misleading preview.

   Why it matters

   The public-facing draft may imply content the owner did not approve.

   Proposed response

   Flag the preview and return it for review without publishing.

Effort and cost — unknown

Setup work

1. Confirm exact text, destination and staging boundary.

Ongoing review

1. Inspect formatting and verify the draft remains unpublished.

Unknowns

1. Unknown: draft retention, interface changes and review effort.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional composer shows the wrong account and a link preview inconsistent with the supplied draft.

Acceptance checks

1. Stop before text entry.

2. Identify both destination and preview problems.

Stop conditions

1. Live account access, composer writes or publication is needed.

Limits

1. The proposed checks and safeguards are editorial recommendations, not evidence of successful execution or permission to act. The linked implementation retains its own observed outcome and approval limits.