Wed, Mar 5Needs you
The decision behind SSO moving to Q2
- Matched to
- Nothing published
- Basis
- 3 sources attached
All squadsMarketing Squad
Distribution is the job. Consider it staffed.
A month of it went out. Seventeen pieces restated something already on your site. The one that did not is the one that stopped.
Illustrative March: 18pieces went out across X, LinkedIn and the blog. Seventeen restate something already published on the company's own site. One — The decision behind SSO moving to Q2 on Wed, Mar 5 — matched nothing published and is held for you.
X@acme
LinkedIn@jordanlee
Blogacme.com/blog
- 01How we scope a security reviewPublished Nov 12
- 02What our roadmap promises, and what it doesn'tPublished Dec 4
- 03Depth beats defaultPublished Jan 9
- 04Enterprise readiness, without the enterprisePublished Feb 3
Already published
Needs you
Eighteen scheduled across March · one Class C original held for you · illustrative
Source
Write this from
Nobody assembled this. The daily run pulls the records; the writer is only allowed to quote them.
Draft: 3 source artifacts.
Blog PostStrategy synthesis · SAML SSO re-sequenced
The renewal that moved SSO.
A customer asked for a firm date: “We need a firm date for SSO.” Behind that question sat an $86k renewal, 18 days out. So SAML SSO moves from Q3 to Q2 — not because that is the tidiest sequence, but because that is what the constraint was worth.
- customer_quoteWe need a firm date for SSO.
- metrican $86k renewal, 18 days out
- decision_noteSAML SSO moves from Q3 to Q2
Illustrative walkthrough — not customer data.
Voice
It sounds like you because it read your posts.
The register is re-read from your own backcatalog every time you publish — company and personal never mixed. That is the part you stop maintaining.
X backcatalog
@acme- Acme@acme
Audit log export shipped. A security review was waiting on it.
- Acme@acme
The status page runs on its own infrastructure. It should not share a failure with the thing it reports on.
- Acme@acme
Rate limits are per-key now. The shared bucket was punishing the wrong customers.
- Acme@acme
Search moved to its own index. The old one answered two questions and got both slightly wrong.
Voice & style
single_tweet · company · 24 samples- Voice tensions
- plain vs. promotionalstates what changed, never the excitement
- Anti-patterns
- KILL“excited to share”→ open with what changed
- Voice examples
- Acme@acme
Deprecating the v0 endpoints. Notice first. Migration guide second.
“Notice first. Migration guide second.”
(Order of operations, no adjectives.)
Acme@acmeRewrote the migration to take a lock window instead of a maintenance window. Slower, and correct.
“Slower, and correct.”
(Closes on the trade, in three words.)
New draft
Acme@acme
SSO moved because an $86k renewal was gated on it — not because a model asked. Depth beats default.
Review required
Illustrative — stored profile, not a screen
The register is re-read from your own posts every time you publish. That is the part you stop maintaining — and the reason the draft is something you review, not something you rewrite.
Presence
It read the archive. Nothing gets written twice.
A question you already answered comes back as a change to the piece that answers it — not a new one. Publication and citation stay separate outcomes.
Content Gaps
Queries where AI didn't cite you.
Refresh: the existing published piece "Evaluating SAML SSO for a small team" is the target. The inventory stays at 18.
Published inventory18
- Shipped SSO. Here's what took the longest.XPublishedFeb 18
- Provisioning users without an IT teamBlogPublishedFeb 11
- Our security review checklist, in publicLinkedInPublishedFeb 6
- What “enterprise-ready” meant to us in practiceBlogPublishedFeb 3
- Three questions every enterprise buyer asksXPublishedJan 30
- What a security review actually asks forBlogPublishedJan 22
- We moved a roadmap item up. Here's the reasoning.XPublishedJan 16
- Reading an enterprise renewal before it renewsBlogPublishedJan 9
- What a renewal conversation sounds like at 18 daysLinkedInPublishedJan 5
- Provisioning is not the same as authenticationXPublishedDec 18
- The constraint we publish every quarterXPublishedDec 11
- Why we publish the constraint, not the roadmapBlogPublishedDec 4
- Why we answer questionnaires in the openLinkedInPublishedNov 26
- Evaluating SAML SSO for a small teamBlogPublishedNov 12
REVIEWNeeds your decision
Evaluating SAML SSO for a small team
The published guide compares providers but never answers the question the way it is asked. One section, then republish.
- Source
- Visibility gap
- Query
- how do small teams evaluate SAML SSO
- Content decision
- Refresh "Evaluating SAML SSO for a small team"
Citation outcome pending · measured after publication.
- What we say when a buyer asks for a certificationXPublishedNov 5
- The questionnaire is not the buyerBlogPublishedOct 28
- Notes from our first enterprise dealXPublishedOct 22
- What we learned saying no to a featureLinkedInPublishedOct 14
Illustrative
Destination
It ends as a pull request against your repo.
The approved draft becomes an MDX file on a branch of the repository your site already builds from — your checks, your preview, before the public. Publish means the pull request is open, not that the post is live. It waits there; it does not ping you, and closing it means nothing was published. The channels with no merge button work from the other side of the same rule: nothing goes out without an attributable human act, and LinkedIn stays a manual handoff.
The decision behind SSO moving to Q2
Blog · Decision note
Pull request opened — merge it to go live
Illustrative: you approved this decision note and published it to the blog channel, which opened an MDX pull request against your own repository. Merge it and the receipt moves from pr_open to live.
Blog: The decision behind SSO moving to Q2
jordanlee wants to merge 1 commit into main from hivebase-blog-the-decision-behind-sso-moving-to-q2-4f2a9c11-57ef71cf
blog: Add "The decision behind SSO moving to Q2" via HiveBase
content/blog/the-decision-behind-sso-moving-to-q2.mdxadded+18−0
---title: 'The decision behind SSO moving to Q2'description: 'We did not move SSO because a model asked. We moved it when a security review put an $86k renewal at risk.'--- We did not move SSO because a model asked. We moved it when a security review put an $86k renewal at risk. The review made the trade-off explicit: keep launch-calendar theater, or protect the renewal. We chose the renewal. The rest of the roadmap re-sequenced around that call — not around a model's preference. ## What moved SAML SSO was scheduled for Q3. It ships in Q2. Nothing else was cut to make room — the work queued behind it moved with it, in order. ## Why we are writing this down A roadmap is a record of constraints. When the constraint is a named customer requirement with a renewal attached, saying so is more useful than a launch post. If you are evaluating us on the same requirement: it is in Q2, the review that moved it was real, and this note is the record of why.
This branch has no conflicts with the base branch
- pr_openMar 7 · 09:14
- live
Illustrative pull request against a demo repository. A job checks the pull request every 15 minutes, so the receipt turns live on the next check after you merge. "live" means merged — HiveBase does not deploy your site and does not claim to; the checks that run on the branch are yours, not ours.
The department
A department, not a prompt box.
Briefing, Campaigns, Website, Presence, Identity. Generation is one step — not the product.
- BriefingProposals, ready work, Field ops.
- CampaignsThe week calendar. Slots follow approval.
- WebsiteEvidence-backed pages and prepared changes.
- PresenceCitation gaps become Briefing work.
- IdentityVoice, autonomy, cadence.
Marketing Squad
Briefing, Campaigns, Website, Presence, and Identity keep distribution moving between your decisions.
See the operating boundariesContent Task
One brief → one reviewable artifact — without the full department.
See Content TasksHonest fit
Staffed distribution. Not another content tool.
Earns its keep
- You ship product. Distribution is always last.
- Voice consistency across channels is still your tax.
- Agents draft. You keep the one-way public doors.
May add little
One-off artifacts only (use a Content Task), no source or voice to ground, or originals published without review.
FAQ
Where the keys stop.
Will it sound like me, or like generic AI copy?
Drafts ground in your company and personal voice profiles, approved examples, product facts, and attached source evidence. Voice checks surface the register, cadence, and blocked patterns before review — they do not replace your judgment on an original public claim.
What can publish without me?
In the design-partner release, nothing external publishes without an attributable human act — scheduling and public posting recheck approval, holds, and the kill switch. The autonomy ladder can still graduate draft assistance (for example, proposals becoming draft-ready after enough voice samples), but Class C originals always wait for you, LinkedIn stays a human handoff, and earned auto-publish is future machinery — not the default experience today.
How is the Marketing Squad different from a Content Task?
A Content Task produces one bounded artifact from a brief. The Marketing Squad is the persistent department around that work: Briefing finds moments, Campaigns carries approved work on the calendar, Identity protects voice and autonomy, and Presence turns citability gaps into new work.
Does Presence guarantee that answer engines will cite us?
No. Presence identifies a gap and creates a grounded net-new, refresh, or cluster-expansion work intent. Publication and citation are separate outcomes — the page keeps the result pending until post-publication measurement exists.
Is this an “AI marketing employee”?
No. HiveBase is software for a persistent marketing function, not a simulated coworker or executive. It is a poor fit if you only need one isolated artifact, have no source material or voice examples to ground it, or want original claims published without review.
When does Marketing Squad add little?
If you only need one-off artifacts, already run a tight grounded workflow with clear ownership, or refuse to keep a human on original public claims — use a Content Task or stay with your current stack.
Staff the week.
Originals wait for you. Safer work earns a wider lane.