Your article just published. Who tells your network?

T2D3 OS now amplifies what you publish. Readers get share buttons on every article. You, the author, get something better: the moment a piece publishes, the OS drafts LinkedIn and X posts in your voice, grounded in the article, and either holds them for your one-click approval or posts them itself once the article URL is actually live. You choose the autonomy level per account.

Most B2B content dies in the sixty seconds after it publishes. The article is live, the team has moved to the next task, and nobody tells anyone. Three days later someone remembers, writes "Excited to share…" over a bare link, and the piece gets a fraction of the reach the work deserved.

The uncomfortable truth underneath: in B2B, people outperform logos. A founder's or operator's personal LinkedIn post about an article routinely earns several times the engagement of the same link on the company page. Buyers follow practitioners, not brands. So the highest-leverage distribution step for every article you publish is also the one most likely to be skipped, because it lives in a personal account the marketing stack can't touch.

What we shipped

Two things, one for each side of the article.

For readers: every article in our learn library now carries share actions — LinkedIn, X, email, copy link. Plain share intents, no trackers, no SDK weight. If a piece is worth passing on, passing it on is one click. We also tightened the machine-facing metadata (Open Graph and X cards), because a link that unfurls into a real preview gets shared more than a naked URL.

For the author: you can now connect your own LinkedIn and X accounts to T2D3 OS, under Account → Personal connections. Personal is the operative word. This is not the company page connector our Social Media Manager module already uses — it's your account, your voice, connected with your own consent, disconnectable any time.

Then the interesting part happens at publish time.

Agents lead, humans steer

When you publish a piece to your site through the Content Studio, the OS doesn't wait to be asked. A background agent reads the published article and drafts one share post per network you've connected — in first person, leading with the sharpest specific claim in the piece rather than an announcement that a blog post exists. The drafts land in your account page and in a notification.

From there, the autonomy is yours to set, per account:

• Propose (the default). The drafts wait for you. Edit the text, watch the character budget (X still counts every link as 23 characters), then post with one click — or open a prefilled compose window and post it yourself without granting the app posting rights at all.
• Automatic. Flip one switch and the OS posts for you. But not naively: an article published through our own pipeline goes live at the next production deploy, minutes to hours later. The agent checks that your article URL actually serves before it posts, and keeps checking until it does. Nobody's network should ever get a link to a 404.

This is our operating principle for every agent in the OS: the system drafts before being asked, and the human is reserved for what only the human can give — judgment, voice, and the final call on anything outbound. Automatic posting exists because you explicitly chose it, never as a default we hoped you wouldn't notice.

Why this is harder than it looks

The naive version of this feature is a Zapier hook that fires on publish. We tried variants of that path and kept the webhook bridge as a fallback, but the real product needed four things a hook can't give you:

1. Grounding. The share post may only claim what the article says. The drafting agent gets the article body as its only source material, so the post is a distillation, not a hallucination.
2. Timing. Publish-time and live-time are different moments in any pipeline with a build step. Amplification that fires at publish-time shares broken links.
3. Personal credentials, personally held. Your tokens live in a row only you can read, written under your own session, revocable by you. The org never posts as you; you never post as the org.
4. A feedback seam. Every draft you edit before posting is a correction, captured next to the AI's original. That's the raw material for the loop we build everything around: the AI proposes, you correct, and the corrections are there to learn from.

The share buttons took an afternoon. The judgment about who acts, when, and with whose voice — that's the product.

If you publish B2B content and your distribution still depends on someone remembering to post about it, that's the gap this closes. Connect your accounts once, and your next article introduces itself.