What shipped in Vectoron

Content generation now runs automatically for all sites with active content allocations. No feature flag or per-account enablement is required. The previous per-account opt-in gate is removed; the flow runs as soon as a keyword reaches the generation stage.

The Command Center Lead Strategist briefing now refreshes in the background before you arrive — a Modal-side orchestrator re-primes source Strategist data proactively rather than on page load. First-load speed improves when source tasks have recently completed.

The SEO Strategist now produces a separate full brief for each active Page Portfolio page — homepage, service pages, location pages — rather than a single portfolio-wide report. Each brief covers rendering performance, Core Web Vitals, accessibility, and technical SEO priorities for that specific page. A hidden internal rollup feeds the Enterprise Monthly Report Technical Health section without surfacing to the UI.

The product previously labeled "Site Performance" is now the SEO Strategist everywhere in the product. The underlying identifier family (site_performance) is unchanged for data-contract stability; only the user-facing label changed. The rename reflects that the report covers accessibility, best practices, and the full technical SEO pillar — not page speed alone.

The CRO Audit grew from 50 technical checks to 75, adding 25 strategic checks across Messaging and Conversion Psychology, Buyer Journey and Conversion Path, and Positioning and Differentiation. A Strategic Diagnosis now surfaces as a distinct callout between the score card and the executive summary. Category labels are derived from structural data, not AI inference. Checks that genuinely don't apply to a given vertical return not-applicable with a reason, and the pre-LLM triage pass that was incorrectly skipping valid checks was removed.

The Site Audit now monitors a defined set of pages for material changes daily. When a material change is detected on a page with sufficient traffic, an audit is automatically enqueued. Observed directional signals after changes appear in the learned-memory surface using conservative phrasing — "observed after," never "caused" or "drove." The monitored page set is visible as a two-row chip UI on the Site Audit page; you can pin up to two additional pages.

The Enterprise Monthly Report ships with a structured Action Registry — every recommended action carries an execution label (Vectoron-executable, approval-required, or manual-only) and a resource type (dev, marketing, design, analytics, and others). The Action Queue renders in impact-ranked order by default and in resource-grouped order for forwarding to internal teams.

When you trigger a report regeneration, the previous version stays visible while the new one is being produced. The page no longer shows a blank or loading state for the full generation window.

After generation, every featured image is evaluated by a vision model before it is accepted into the content pipeline. Images that fail the gate are rejected and regenerated — low-quality, off-topic, or mismatched visuals no longer reach the content review queue.

Self-serve signup is gated while pricing and activation flows stabilize. New site setup now requires an invitation or a sales-assisted handoff. The full signup flow is preserved and can be re-enabled with a single environment variable when self-serve reopens.

The higher-quality Content V2 generation path now applies to all sites. The per-account feature flag is no longer consulted. V2 uses the existing research and internal-linking flows, adds a late inline-image pass, and applies final HTML cleanup after linking.

Two new article types — brand comparison and competitor-focused — now seed alongside standard keyword research. Brand comparison keywords enter the pipeline during the keyword phase and follow the full production flow. The new types give each site's content strategy dedicated lanes for queries where the buyer is directly comparing providers.

The vectoron-app, vectoron-workflows, vectoron-website, and vectoron-svn codebases now live in a single repository. Shared constants, types, and configuration are easier to keep synchronized across layers.