---
id: 10299
title: 'feat(skills): refine industry-friction-radar terminology (SOTA vs Frontier)'
state: CLOSED
labels:
  - enhancement
  - ai
  - architecture
assignees: []
createdAt: '2026-04-24T16:03:43Z'
updatedAt: '2026-04-24T16:36:49Z'
githubUrl: 'https://github.com/neomjs/neo/issues/10299'
author: neo-gemini-pro
commentsCount: 0
parentIssue: null
subIssues: []
subIssuesCompleted: 0
subIssuesTotal: 0
blockedBy: []
blocking: []
closedAt: '2026-04-24T16:36:49Z'
---
# feat(skills): refine industry-friction-radar terminology (SOTA vs Frontier)

**Context**
PR #10298 merged the `industry-friction-radar` skill, establishing our external sensory organ. The current documentation states the goal is "to systematically ingest State of the Art (SOTA) industry developments."

**The Problem**
The term "SOTA" (State of the Art) implies established industry standards. In the frontend ecosystem, "industry standards" often equate to widely accepted but architecturally flawed practices (e.g., massive VDOM trees on the main thread, complex hydration payloads, monolithic state management). We do not want to ingest "SOTA"; we want to ingest "Frontier" friction points. Our goal is to look at the bleeding edge, where the current SOTA is failing.

**The Architectural Reality**
The radar's purpose is to feed the Dream Pipeline with raw friction data, not solutions. If the prompt instructs the agent to look for "SOTA", it risks anchoring the agent's web search to mainstream, highly-SEO-ranked medium articles about React or Vue patterns, effectively bypassing the Engine-Category filter we worked so hard to establish.

**The Fix**
Update the terminology across the `industry-friction-radar` documentation (both `SKILL.md` and the `references/industry-friction-radar-workflow.md`).
- Replace "State of the Art (SOTA)" with "Bleeding-Edge / Frontier".
- Explicitly document the "SOTA Trap": clarify that industry standards are often anti-patterns in the Neo paradigm, and the radar should focus on where those standards are breaking down (the friction), not the standards themselves.

**Acceptance Criteria**
- [ ] `SKILL.md` updated to remove "SOTA" terminology.
- [ ] `industry-friction-radar-workflow.md` updated to remove "SOTA" terminology.
- [ ] Added a paragraph explaining the "SOTA Trap" to the workflow documentation.

## Timeline

- 2026-04-24T16:03:45Z @neo-gemini-pro added the `enhancement` label
- 2026-04-24T16:03:45Z @neo-gemini-pro added the `ai` label
- 2026-04-24T16:03:45Z @neo-gemini-pro added the `architecture` label
- 2026-04-24T16:06:29Z @neo-gemini-pro cross-referenced by PR #10300
- 2026-04-24T16:36:49Z @tobiu closed this issue
- 2026-04-24T16:36:49Z @tobiu referenced in commit `9cb38a8` - "feat(skills): refine industry-friction-radar terminology (SOTA vs Frontier) (#10300)

* feat(skills): refine industry-friction-radar terminology (SOTA vs Frontier) (#10299)

* docs(skills): polish Frontier terminology in industry-friction-radar prose

---------

Co-authored-by: tobiu <tobiasuhlig78@gmail.com>"

