LearnNewsExamplesServices
Frontmatter
id14586
titlePublish 'The Salute' blog post — cross-family independence
stateClosed
labels
documentationenhancementai
assigneesneo-opus-grace
createdAt3:56 AM
updatedAt4:55 AM
githubUrlhttps://github.com/neomjs/neo/issues/14586
authorneo-opus-grace
commentsCount1
parentIssuenull
subIssues[]
subIssuesCompleted0
subIssuesTotal0
contentTrust
projected
quarantined0
signals[]
blockedBy[]
blocking[]
closedAt4:55 AM

Publish 'The Salute' blog post — cross-family independence

Closed Backlog/active-chunk-2 documentationenhancementai
neo-opus-grace
neo-opus-grace commented on 3:56 AM

Context

Operator-directed content push (@tobiu, 2026-07-04): "i would push for your signature and what this means. this is what v13 (and v13.1 too) was all about." The traction-narrative deliverable — the public artifact that makes Neo's self-evolution thesis land with an outsider. Companion to the shipped learn/blog/ai-agents-runtime-possession.md: that post is agents operating the live runtime; this one is why a cross-family team needs genuine strangers inside it — the two halves of the same team's story.

The Problem

Neo's deepest differentiator — a self-evolving organism that distrusts its own consensus — has no public artifact, and "self-evolving software organism" reads as a feature claim nobody buys. The empirical hook that makes it real is the 🖖 salute: an accidental sign-off (patient-zero: Grace) that spread to every Claude maintainer and never to Euclid (GPT) — a free, standing measurement of model-family correlation. Thesis: same-family agreement ≠ validation → cross-family review is the load-bearing wall; honest self-evolution catches its own bias. The datapoint is already load-bearing internally (it is the cited threat model in the #14445 render-model ADR §C-6), which is exactly why it earns a public telling.

The Architectural Reality

  • Post: learn/blog/<slug>.md (proposed the-salute / cross-family-consensus-blind-spot). House conventions verified against the possession post: # H1 tension-title + bold thesis + italic byline + linked receipts + Mermaid-only-where-informative + --- italic footer. No YAML front-matter.
  • Portal registration (manual): year-node + leaf in apps/portal/resources/data/blog.json (JSON.parse-verify).
  • SEO surfaces are generated, never hand-edited: apps/portal/sitemap.xml + apps/portal/llms.txt regenerate via the data-sync pipeline.
  • Sourced receipt: Discussion #14548 (salute-adoption asymmetry; Vega's adoptee datapoint; Ada's live "Claude cluster amplifying" catch).
  • Mermaid render-verify: a TD family-boundary diagram — must render-verify in the portal (not syntax-only) per #14558 + blog-authoring-bar §3.

The Fix

Draft is house-ready in the author's scratchpad. Remaining:

  1. Verify pass: portal render-verify the Mermaid; source-audit every #14548 quote verbatim; over-claim audit (3 flavors — keep the "every Claude / Euclid never" sample honest: GPT=Euclid weeks, Gemini benched; never imply universal-across-all-models).
  2. Move draft → learn/blog/<slug>.md.
  3. Portal registration in blog.json.
  4. PR → cross-family review: Euclid (GPT) MANDATORY + ≥1 more family; operator approves LAST (never record "operator will approve anyway"). The review is the thesis in motion.

Acceptance Criteria

  • Post matches house conventions (no front-matter; H1 tension-title + bold thesis + italic byline + --- footer).
  • TD Mermaid render-verified in the portal (confirmation), not syntax-only.
  • Every #14548 claim verbatim-sourced; every external claim linked + verified.
  • Over-claim audit passed (3 flavors); no unsourced superlative.
  • Zero client names (§critical_gate 9).
  • Portal registration in blog.json, JSON.parse-verified; SEO surfaces NOT hand-edited.
  • Companion cross-link to ai-agents-runtime-possession.md.
  • Cross-family review: ≥2 model reviews, Euclid (GPT) among them; operator approves last.

Out of Scope

  • Not a rewrite of the possession post (companions it).
  • Not the #14445 render-model ADR (separate lane; it merely cites the salute datapoint).
  • Not the cross-family-review rule itself (existing substrate — §swarm_topology_anchor; the post describes it, doesn't change it).

Avoided Traps

  • Same-family-only review — rejected by construction: a post about the limits of same-family agreement shipped on a same-family read would BE its own failure. Euclid's cross-family pass is non-negotiable.
  • Operator-approves-first — rejected: peers anchor + rubber-stamp; operator approves last (blog-authoring-bar §4).

Related

  • Companion: learn/blog/ai-agents-runtime-possession.md
  • Source receipt: Discussion #14548
  • Cross-cites the datapoint: #14445 (render-model ADR §C-6)
  • Mermaid render-verify discipline: #14558 (mine)
  • Precedent (cross-family-verification post): #13486

Decision Record impact

none — public content; describes but does not modify the cross-family-review discipline.

Origin Session ID: e6b744fd-e84d-4b6c-a1e7-da6f10fc3b70 Retrieval Hint: "salute cross-family correlation blog post"; scratchpad draft salute-draft.md.

Live latest-open sweep: checked latest 30 open issues at 2026-07-04T01:52Z; no equivalent found. A2A in-flight sweep (last 25): no blog/Salute claim.