Add factual v13 evaluation and reach-out CTA

Context

The merged v13 release notes now tell the Agent OS / institution story, but Gemini's CTO cold-read critique surfaced a valid ACTION gap: a decision-maker can understand why v13 matters and still lack a low-risk next step.

Operator clarification: real multi-repo Agent OS deployment pressure exists, including private GitLab ingestion and cloud deployment work. Public release-note wording must not name private organizations, deals, targets, or confidential deployment details. It should instead point to public proof and public contact/community doors.

Live latest-open sweep: checked latest 20 open issues on 2026-06-08/09; no equivalent release-note CTA ticket found. Local exact sweep found #12577, but that ticket governed CTA substrate in neo-identity-update; it did not add a v13 release-note CTA.

Knowledge Base sweep: ask_knowledge_base('Neo v13 release notes CTA evaluation path cloud deployment guides Architecture Overview README channels') was attempted and failed because the Knowledge Base collection is unavailable. This ticket is therefore grounded in live repo reads, live GitHub issue sweep, and public source files.

The Problem

The v13 notes now have a strong strategic arc, but the reader journey can still dead-end after the final value section. A CTO, architect, or engineering lead needs a conservative way to evaluate the release without interpreting the document as a demand to rewrite their stack or adopt unproven commercial promises.

Gemini's proposed "enterprise support / SLA" section correctly identified the missing landing pad, but its suggested fix overreached: Neo should not claim 24/7 support, guaranteed SLAs, enterprise relations, or commercial packaging unless those offers are explicitly real and operator-owned.

The Architectural Reality

This is an ACTION/CTA identity-surface update under ADR 0018 and .agents/skills/neo-identity-update/references/cta-governance.md.

Relevant current public surfaces verified:

• README.md already exposes Discord and Slack badges and a Community section.
• README.md links to Deploying the Agent OS, Agent OS on Your Codebase, Day-0 Cloud Deployment, and Tenant Ingestion Model.
• resources/content/release-notes/v13.0.0.md has ## 🚀 What You Can Do With v13, but no explicit evaluation path or reach-out door.
• resources/content/release-notes/v13.0.0.md already links Architecture Overview and the 30 Agent OS skills as proof surfaces.

The Fix

Add a compact CTA/evaluation paragraph or subsection to resources/content/release-notes/v13.0.0.md, near ## 🚀 What You Can Do With v13, that:

1. frames a low-risk evaluation path rather than an all-in migration;
2. points evaluators toward a focused shadow PoC: one repo, one data-dense UI, or one internal tool lane;
3. links public Agent OS deployment / ingestion guides and public community/support doors;
4. says readers can ask questions, open issues/discussions, or join Discord/Slack;
5. avoids commercial support/SLA promises and avoids naming private deployments or organizations.

Contract Ledger Matrix

Decision Record impact

Aligned with ADR 0018 and CTA governance (#12577/#12587). No ADR amendment required.

Acceptance Criteria

• v13 release notes include a concise evaluation/reach-out CTA near What You Can Do With v13.
• The CTA links to public, live surfaces: cloud/deployment docs, GitHub issues/discussions, and/or README community channels.
• The text avoids invented commercial offers: no SLA, 24/7 support, enterprise relations, pricing, or advisory-board promises.
• The text avoids naming private organizations, private deployment details, private business targets, or confidential usage details.
• The section remains release-note prose, not a sales landing page.
• Local markdown checks pass.

Out of Scope

• Changing README or portal CTA copy.
• Creating commercial support, lead-capture, services, pricing, or SLA language.
• Editing generated SEO output.
• Naming any private organization or deployment.

Avoided Traps

• Do not paste Gemini's commercial-support draft into the release notes.
• Do not turn Slack/Discord into the only primary CTA; GitHub issues/discussions and public docs need to remain durable paths.
• Do not convert the release note into a procurement page. The target is a factual evaluation path and human contact door.

Related

• Parent: #12696
• CTA governance: #12577 / #12587
• Prior release-note CTA precedent: v11.16.0 used a simple GitHub/Discord reach-out line for PoC-stage architecture.

Origin Session ID: 720fc09a-e8ff-467d-b039-28120312964d

Handoff Retrieval Hint: v13 release notes CTO evaluation CTA shadow PoC Discord Slack cloud deployment guides