Publish from the same canvas

The work should not become a second document when it is time to ship. In Shyne, the frame or sequence you edited is also the source for a post, a scheduled release, an email, a public link, or an export.

That removes a familiar handoff: download the latest image, rename it, open a scheduler, rebuild the caption, choose the crop again, and hope nobody fixed the price after you left the canvas. Shyne keeps the creative source in one place and treats delivery as an explicit action around it.

What you can publish

Select a frame, an ordered sequence, or supported media on the canvas. Open Share, choose Social, select a connected channel, and either post now or schedule for later. The same release engine supports connected social accounts and email delivery.

The source matters:

• A frame can become a text, image, or video post.
• An ordered sequence can become a carousel.
• A timed sequence can become a video.
• Selected uploaded images or a video can be published without creating a duplicate design.

You can still export PNG, JPG, PDF, HTML, PowerPoint, or MP4 when a file is the right handoff. Publishing does not replace export. It gives finished canvas work a direct route to connected destinations.

Connect destinations first

Open Settings → Connections and connect the accounts you intend to use. Shyne reads the available channels from those connections and shows the options each provider supports, including placement, privacy, caption, title, or other provider-specific fields when they apply.

Provider credentials stay behind the Shyne service boundary. The editor and agent can use a connection without receiving its raw token. That distinction is important: permission to publish one post is not permission to copy a credential somewhere else.

Connect only accounts you understand and check the selected channel before sending. A technically valid post can still be wrong if it reaches the wrong profile.

Post yourself or ask the teammate

There are two honest paths through the same system.

From Share, you select the destination, edit the caption, inspect the preview, and click Post or Schedule. That is a direct action by the signed-in person.

The teammate can also prepare an inline post preview. You can change the caption, choose channels, and post or schedule from that card. When the agent calls publishing_create itself, Shyne treats the call as consequential: the client shows what will be sent, where it will go, and when it will run, then asks for your permission before the operation proceeds.

This is an immediate permission gate on the real publishing operation, not a background grant of authority. If you reject it, nothing is sent. If you approve it, the release enters the same render, delivery, and status flow as a release created from Share.

What happens after approval

A release records its project, canvas, source, targets, caption, schedule, and timezone. Shyne renders the required media, validates it for each destination, waits until the scheduled instant when necessary, then delivers each target.

Scheduled posts appear on the calendar and can be cancelled before delivery. The canvas remains editable, but scheduled artwork is a deliberate snapshot: use the refresh action when you want a later canvas change to replace the frozen media for that scheduled post.

Multi-target releases report each destination separately. One provider may publish while another fails, so a release can be partially published. Do not turn a successful tool call into a claim that every target went live.

Trust the persisted status

A scheduled time is not proof of delivery. A permission approval is not proof of delivery. A release id is not proof of delivery.

The saved release record and its targets are the truth. A release can be scheduled, publishing, published, partial, or failed; each target separately records whether it is pending, rendering, publishing, processing, published, or failed. When a provider returns a public URL, Shyne keeps it with that target so the posted badge can open the real destination.

If someone asks “did it go out?”, read the current release record. Do not answer from memory of the click.

Renditions stay tied to the source

Different destinations accept different media shapes and limits. Shyne renders and validates the source for the selected target instead of asking you to rebuild it in a separate scheduler.

Inspect the preview before sending. If a logo is too close to the edge or a title does not survive the crop, fix the frame on the canvas and inspect again. For a scheduled post whose artwork has already been frozen, refresh the release after the correction.

When two channels genuinely need different creative, duplicate the frame or sequence on the canvas and make the difference visible there. Do not hide the only corrected version inside a provider’s native editor, where the project and the next collaborator cannot see it.

Email uses the same principle

For email, a flow-layout frame is the message. Shyne compiles it to client-safe HTML at send time instead of asking the agent to hand-write a second copy. The release names the recipient, subject, verified sender, and any exported project-file attachments.

The same safety rule applies: an agent-initiated send asks for permission first. Inspect the frame and the audience before approving it. The release receipt then carries the delivery result.

Public links and exports

Sometimes the destination is simply a URL. Shyne can publish a public artifact snapshot and revoke it later. That is different from a social release: it is a hosted view of the selected project work, not a post delivered to a connected provider.

Sometimes the destination still needs a file. Use PNG or JPG for stills, PDF for a leave-behind, HTML for a hostable document, PowerPoint for an editable deck, and MP4 for a timed sequence. Hosted MP4 rendering draws from the organization’s credit pool; the free plan can export video too.

The choice is practical, not ideological. Use a live project for collaboration, a public snapshot for a viewable link, a release for a connected channel, and an export for a file handoff.

A complete release loop

Imagine a three-frame product announcement adapted from yesterday’s launch deck.

1. Duplicate the three frames that still read without a presenter.
2. Select the resulting sequence in Share.
3. Choose the exact connected channel.
4. Check the caption, media type, placement, privacy, and publish time.
5. Inspect the preview at the destination’s shape.
6. Fix any problem on the canvas and refresh the preview.
7. Post or schedule. If the teammate initiated the action, approve only after the prompt matches your intent.
8. Check the saved target status and open the provider URL when it appears.

Nothing in that loop requires a second creative source. The sequence stays editable. The release keeps a durable receipt. The connected provider receives the version you inspected.

Publish from the same canvas. Approve consequential actions deliberately. Believe the status, not the story of the click.