Public CVE campaign page - yes to the page, no to auto-updating it; each CVE needs curation to tell the story

November 9, 2026 at 4:04 PMoperationallow

Situation

In a thread on a public page describing the CVE campaign, Peter said the page is really valuable but questioned dynamic updating: each CVE is a potentially different effort and process for CIQ, so the page needs manual curation to properly tell the story.

Reasoning

Confirmed by Peter. A data-fed page would flatten very different efforts into identical rows and could publish fixed from internal status before customers have it. Curation keeps the public claim accurate and explains how CIQ handled each case, which is the differentiator. Supports the visibility Greg asked for while protecting its accuracy, consistent with the 11/3 rule that public CVE claims match what is in customers hands.

Additional Context

Greg pushed in #distinguished-leaders on 11/4-11/5 for getting the CVE-response message out after the Canonical delay post.

Observed Evidence

Public page valuable; not dynamically updated; manual curation to tell the story.

Confidence Breakdown

33/35
Evidence
12/30
Pattern
14/20
Source
7/15
Corroboration

Reasoning Depth Analysis

Org Signal:CVE marketing is storytelling held to accuracy, not a dashboard.
Who Affected:Marketing owns curation effort; engineering supplies per-CVE narrative.
Precedent:Public CVE claims are curated, not auto-published.
Consequences:Ongoing curation cost for Marketing.
Timing:Competitor CVE delays made the message timely.

Source

reflection

AI Confidence

66%

Related Context

💬
Nathan/Lindsay/Arthur/Peter group DM

slack

Each CVE is a potentially different effort and process for us. So I think the page needs some manual curation to properly tell the story.

Outcome

No outcome recorded yet.

Decision ID: af6eed8d-d55b-433e-aac7-31b89f51c0de