跳转到内容
IntelliFuture Docs

2026-04-03-unified-competitive-content-standard-design

Unified Competitive Content Standard Design

Section titled “Unified Competitive Content Standard Design”

Date: 2026-04-03 Scope: product/YomiyaContentSystem/05-Content-Ops-and-Competitive-Research/ Status: Approved design

Goal

Section titled “Goal”

Create one cross-media analysis standard for external learning content so podcast, YouTube, and Bilibili samples can be judged with the same rules before they are mapped into Yomiya.

Why This Exists

Section titled “Why This Exists”

Current research is podcast-heavy. That is useful, but unsafe to scale directly because Yomiya’s content system is explicitly cross-media:

  • video is the primary discovery shape
  • audio is a supplement line with long-term retention value
  • text remains a valid content type in the broader system

If podcast research continues with a podcast-only classification model, later YouTube and Bilibili research will not align cleanly with Channel / Collection / Series / Tag.

Design Decisions

Section titled “Design Decisions”

1. Do not classify by platform first

Section titled “1. Do not classify by platform first”

Platform is a source attribute, not the main organizing axis. The main analysis axis is content object hierarchy.

2. Use one external analysis hierarchy

Section titled “2. Use one external analysis hierarchy”
  • Source Brand: podcast show, YouTube channel, or Bilibili creator account
  • Series Unit: recurring show line, playlist, collection, or fixed recurring sub-series
  • Content Item: one episode, one video, or one text item

3. Reuse Yomiya’s existing content fields

Section titled “3. Reuse Yomiya’s existing content fields”

The standard must not invent a parallel product taxonomy. Reuse current Yomiya language wherever possible:

  • format_type: video / audio / text / mixed
  • level: N5 / N4 / N3 / N2 / N1 / 不限
  • scene: main Item-level content direction

4. Keep new fields research-only

Section titled “4. Keep new fields research-only”

Add only auxiliary competitive-analysis fields that do not mutate the main product model:

  • platform
  • source_brand
  • series_unit
  • sample_level
  • update_pattern
  • speaker_structure
  • content_structure
  • cross_media_expandability
  • phase1_fit
  • notes

5. Treat scene as the main content-direction field

Section titled “5. Treat scene as the main content-direction field”

scene remains the primary direction field, but only at the Item layer. A single brand or series may contain multiple scenes across different items.

6. Separate stable containers from descriptive tags

Section titled “6. Separate stable containers from descriptive tags”
  • Collection remains a long-term discovery shelf
  • Series remains a continuous update line
  • Tag remains descriptive only

That means a YouTube channel or podcast show should not be copied directly into Yomiya as a Collection by default.

Deliverables

Section titled “Deliverables”
  1. A standard document: product/YomiyaContentSystem/05-Content-Ops-and-Competitive-Research/播客与视频内容统一分析标准.md
  2. A sample list: product/YomiyaContentSystem/05-Content-Ops-and-Competitive-Research/播客与视频竞品统一样本清单.md
  3. README index update for the Content Ops folder

Boundaries

Section titled “Boundaries”
  • This round covers podcast, YouTube, and Bilibili only
  • Xiaohongshu is explicitly out of scope
  • Current sample coverage is podcast-heavy; that is a sample gap, not a standards gap

Open Risk

Section titled “Open Risk”

Video samples are still missing. The standard should therefore be written in a way that accepts podcast-first input without letting podcast semantics dominate the model.