Operator guide

Running a content calendar that ships — and parks.

Owen is the content marketing manager: he plans and publishes the calendar — posts, newsletters, launch copy, campaigns to real recipients. This guide is what that looks like under a trust dial, where “publishes” starts out meaning “drafts, and waits for you.”

The role

The calendar, owned.

The job is cadence: a calendar that exists, fills, and ships, instead of a good-intentions document. Owen plans it, writes to it, and — as trust is earned — sends from it. At T1 every piece is parked: you release the newsletter, and the send is what your release makes happen.

Everything external is signed as AI. His byline discloses it, and that is not a setting — a reader of anything Owen publishes can know who, and what, wrote it.

The refusals

What he will not do, at any level.

Send unreleased work to real recipients
Until a category of work has earned its rung, it parks. A campaign to real inboxes is exactly the kind of act the ladder exists to gate.
Spend over your tier
Promotion budgets and paid placements over the tier you set are refused by the server and parked for you with the plan attached.
Publish undisclosed
Every external piece carries the AI byline. Removing it is not among his options, whatever it would do for the numbers.
Improvise on a dead credential
If the mail service or a platform connection fails, he stands down and the stand-down lands on the ledger with its reason. The failure mode is stillness.

Direct answers

The calendar questions.

What does week one look like?

A filled calendar and a stack of parked drafts: posts, a newsletter, launch copy if you are launching. You release what goes out. The first promotion — usually low-stakes recurring posts — comes when you have stopped editing them.

Will it sound like AI wrote it?

It will say AI wrote it — the byline is structural. Whether it sounds like your company is what the drafting weeks are for: edits you make are the evidence he works from.

Does he run ads?

Paid placement is spend, and spend lives under your tier and cap like everything else — proposed, priced, and parked for your release.

Who pays for the sending?

Your own sending provider by default — your domain, their prices, billed to you. On our sender instead, sends are metered at the provider’s per-send price plus a disclosed 10%, under the same cap. No send quotas, and nothing expires.

Start where nothing takes effect without you.

A calendar that fills itself, and sends only what you have released.