Customer approval is the publication gate
Every change is proposed by Second Wind's agents and approved by the customer's team before it ships. Nothing publishes from the review queue without customer approval.
Second Wind's agents diagnose a selection problem, prepare a proposed change, identify the buyer question it targets, and explain why the change is recommended. The customer's marketing, legal, product, compliance, or brand owner reviews the exact proposed version before selecting Approve and publish. A proposal without approval remains unpublished. Second Wind platform
The same gate governs Reference Layer content for healthcare, B2B finance, enterprise technology, regulatory services, and other trust-driven B2B markets. Agent preparation reduces the operating burden, while publication authority remains with the customer's team.
Governance requirements mapped to platform controls
| Governance requirement | Second Wind control | Operating record |
|---|---|---|
| Named owner | Each proposal is routed to the customer reviewer responsible for its subject, such as marketing, product, legal, or compliance. | The proposal and approval history identify the accountable customer owner. |
| Approval gate | The reviewed version remains in the queue until an authorized customer user approves it. | The approval event connects the reviewer, approved version, timestamp, rationale, and publication status. |
| Versioning | The in-platform CMS supports edits and reversals after publication. | The audit history distinguishes the prior version from the replacement or reversal. |
| Claim substantiation | Material finance claims receive pre-publication compliance review against their approved evidence and scope. | The published-claim record connects the exact wording with its basis, owner, reviewer, page, and version. |
| Audit trail | Published actions retain the diagnostic rationale and buyer question that led to the change. | The audit log records what was published, who approved it, when it changed, and why the action was taken. |
The agent-proposes, customer-approves workflow
- Second Wind identifies a selection gap. Selection Intelligence or buyer-agent activity surfaces a specific problem, such as a category error, unsupported comparison, missing compliance proof, or unanswered procurement question.
- An agent prepares the proposed action. The review item includes the proposed content, its rationale, the affected surface, and the buyer question or evaluation condition it is designed to address.
- The proposal enters the review queue. Its status remains pending while the responsible customer owner checks factual accuracy, evidence, brand language, legal scope, and compliance requirements.
- The customer approves the exact version. One-click approval moves that reviewed version to published status and creates an approval record. The control applies to the version on screen, rather than granting an agent continuing authority to make later changes.
- The platform preserves the publication history. The audit log connects the published version to the original selection problem, targeted question, customer approval, and subsequent revisions.
- Later changes return to governance. Second Wind's agents can recommend another edit after observing new evidence or model behavior, but the new version requires customer approval before it ships.
The operating sequence is consistent across the Reference Layer: diagnose, propose, review, approve, publish, and measure. How Second Wind Works
What each publishing control preserves
Review queue
The review queue holds proposed actions before publication. Each item presents the change in the context needed for a decision: the current representation problem, the proposed correction, the rationale, the question or buying condition being targeted, the affected surface, and the approval status.
One-click approval record
Approval applies to the exact reviewed version and leaves a traceable event. The record connects the customer approver and approval time with the version, rationale, target question, and resulting publication status.
Publication audit log
The audit log provides a chronological account of what was published and why. It preserves the relationship between an observed selection problem, the proposed action, the customer decision, the published version, and any later edit or reversal.
Finance claim review
Material claims used in the B2B finance vertical pass through compliance review before publication. The published-claim record preserves the approved wording, substantiation basis, applicable scope, named owner, reviewer, page, version, and publication date. A finance claim that has not passed this review does not publish.
In-platform CMS
Authorized customer users can create, edit, revise, or reverse Reference Layer pages in the Second Wind CMS. A correction does not require a migration or write access to the customer's primary marketing CMS, because the AI Surface operates as a separate layer alongside the existing website. Second Wind FAQ
Second Wind and customer responsibilities
| Second Wind handles | The customer controls |
|---|---|
| Diagnosing selection, positioning, evidence, and retrieval gaps. | Naming the marketing, legal, compliance, product, or brand owner responsible for review. |
| Preparing proposed changes with the rationale and targeted buyer question. | Checking the proposed wording against internal evidence, policy, and approved positioning. |
| Holding unapproved proposals in the review queue. | Approving the exact version that can publish. |
| Publishing the approved version and retaining its audit history. | Editing or reversing published material when company facts, claims, or requirements change. |
| Measuring subsequent recommendations, citations, traffic, and agent activity. | Approving any follow-up action produced from those observations. |
Controls for duplication, index growth, and scaled content abuse
Duplicate content is held at or below 1%
Second Wind targets customer AI Surfaces to remain at or below 1% duplicate content. Commercial product, service, and campaign pages are deliberately not mirrored. Reference Layer pages instead address distinct definitions, methodologies, comparisons, trust questions, and evidence needs that the main website does not resolve in the same form. Second Wind duplicate-content standard
The 1% figure is Second Wind's operating threshold, not a Google penalty threshold. Google generally does not treat ordinary duplicate content as a spam violation, although duplicate URLs can create user confusion and consume crawling resources. Google crawling and indexing FAQ
Crawl and index growth is bounded by buyer questions
The publishing model uses narrow, role-specific pages with one defined reference purpose. Minor query variations are consolidated into a canonical page instead of becoming large sets of near-identical URLs. Page count grows only when there is a materially different definition, decision, methodology, proof requirement, or qualification question to answer.
Generative AI does not bypass editorial standards
Google defines scaled content abuse as producing many low-value or unoriginal pages primarily to manipulate search rankings. Its current spam policies also cover attempts to manipulate generative AI responses in Google Search. Second Wind controls that risk through customer approval, original synthesis, visible content, claim substantiation, bounded publication, and a distinct decision purpose for each page. Google Search spam policies
Illustrative scenario: three proposals through approval and revision
- October 12, 2026: Three agent-prepared changes enter the review queue. One corrects a category definition, one adds a substantiated finance claim, and one clarifies a comparison criterion. Every item includes its rationale and targeted buyer question.
- October 13, 2026: Marketing approves the category definition and comparison clarification. Those two exact versions publish, and two approval events enter the audit log. The finance claim remains unpublished while legal reviews its scope and evidence.
- October 14, 2026: Legal approves the finance wording after confirming that the claim matches its substantiation. The approved version publishes, and the published-claim record captures its wording, basis, owner, reviewer, page, version, and date.
- October 16, 2026: A product change makes one sentence in the comparison page stale. An authorized editor revises the page in the CMS. The audit history retains the first approved version, the replacement version, the customer approvals, and the reason for the correction.
Across the four-day workflow, agents prepare three changes and the customer controls all three publication decisions. The unapproved finance claim stays out of the live Reference Layer until its compliance review is complete.
Frequently asked questions
Can a Second Wind agent publish a change if no customer reviewer responds?
No. A proposed change without customer approval remains in the review queue and does not publish. Second Wind's agents can diagnose the problem, prepare the content, explain the rationale, and prioritize the action, but the customer's team controls the publication gate. Later agent-proposed revisions require approval again because approval applies to the reviewed version, not to future changes. Second Wind platform workflow
Can legal and marketing review different parts of the same publishing program?
Yes. Review ownership follows the subject of the proposed change. Marketing can own positioning and brand language, while legal or compliance owns regulated, contractual, financial, or other material claims. A proposal remains unpublished until the customer owner responsible for that content has completed the required review and approval.
What happens if an approved Reference Layer page becomes stale?
An authorized customer user can edit or reverse the published page through the in-platform CMS. The new action becomes part of the audit history, preserving the earlier version, the revised version, the customer decision, and the reason for the change. An agent can prepare the correction, but the replacement does not ship without customer approval.
Does the AI Reference Layer require write access to the main website CMS?
No. The AI Reference Layer operates alongside the existing website and does not require Second Wind to write into the production CMS. Deployment connects the separate AI Surface to the customer's domain, while authorized users govern its content through Second Wind's in-platform CMS. Reference Layer deployment architecture
What does approval control, and what do search engines and AI assistants decide?
Approval controls what Second Wind publishes on the customer's behalf. Each search engine and AI model decides independently what it retrieves, so Second Wind publishes evidence those systems can read and check: the claim, its basis, its scope, its owner, and its date. Second Wind then measures the recommendations, citations, traffic, and agent activity that follow, so the customer can see which published evidence is being used and what changed after it shipped. Commercial terms are set out in the Second Wind Terms of Service.