Reports, list-based articles and reaction videos

Answered on 4 October 2026. Joe approved Trend Report as a distinct type, Listicle as searchable article structure, and Reaction Video as a whole-piece type. The decision record and Content model carry the approved meanings. No further answer is needed for these three choices. Database, prompt and search changes have not been made.

The original recommendations and alternatives follow for context. The earlier review bundled these with Corporate Film and recommended accepting all four together. This page separates them. Corporate Film stays with the pending video discussion; no answer here settles it.

1. Keep Trend Report distinct

I recommend Trend Report as a whole-piece type: a report whose main purpose is to identify and explain patterns or changes in a field. Research Report remains an approved type for reporting research findings. The two are not automatic synonyms. A piece can qualify as both when both descriptions genuinely fit.

For example, YouTube's 2024 Culture & Trends report describes changes in fandom and explains that the team studied trends, consulted specialists and commissioned surveys. It illustrates overlap, not equivalence. A report on an experiment need not discuss trends; a publisher's trend outlook need not establish original research. Classification should not imply that a report's conclusions are reliable.

Alternative: retain the applicable report type and make trends a defined, searchable focus. That keeps the type list smaller. I favor the recognizable Trend Report name, without automatically folding it into Research Report or White Paper. Preserve the original title and source in either approach.

Original choice: keep Trend Report as a distinct type, or use a trends-focus filter alongside the applicable report type. Its browsing heading can be reviewed separately.

2. Keep Listicle searchable as article structure

I recommend a defined list-based structure filter, with Listicle as a familiar search name. It describes an article organized around a list of items, recommendations or reasons. It can accompany the article's actual type. A few bullets inside an otherwise different piece are not enough.

Microsoft's Five Ways to Implement the Great Copilot Journey has five lettered approaches in its main section. List structure helps find that presentation; it does not replace what the article explains. This is my reading of its structure, not a type assigned by Microsoft.

Alternative: make Listicle a whole-piece type whenever the list organizes the article. That is workable under the approved multiple-type rule. I favor the separate structure description because advice, comparisons and editorial articles can all use it. Setting the term aside must not mean losing the ability to find this work.

Original choice: searchable structure alongside type, or Listicle as a whole-piece type. This does not yet select a database field or approve the existing Writing Style vocabulary unchanged.

3. Recognize Reaction Video by the whole piece

I recommend Reaction Video as a type when someone's presented response to source material, an event or a product is the central structure of the video. A creator reacting to a trailer is an illustrative case. An audience reaction shot inside an event recap is a moment, not a reason to label the entire recap Reaction Video. A product review is not automatically a reaction video.

YouTube's fandom report discusses reaction videos alongside trailer breakdowns and analytical videos. That supports recognizing the form without making a social feed its defining condition. No individual reaction clip was fully reviewed for this packet.

Alternative: keep reaction as a searchable description alongside the actual whole-piece type. I favor the type where the response organizes the whole video, just as an interview must organize the piece to describe it as an Interview. This does not infer sponsorship or campaign membership. Link the material being reacted to when it is identifiable and the evidence supports the connection.

Original choice: Reaction Video as a defined type, or reaction as a description only. Channel, sponsorship and browsing placement remain separate.

What the bounded audit found

Research Report is already in the approved type list; that approval is not being requested again. The live registry still describes White Paper using both white-paper and research-report wording. The selected registry check found no type entries for Trend Report, Research Report, Listicle or Reaction Video. Those observations show a reconciliation need; they do not prove the library contains no qualifying work.

The current Writing Style path covers copy and script descriptions. Its stored vocabulary has no Listicle entry. Local code writes those descriptions to a relationship table and reads them for filtering; the live table can relate a description to a piece or a segment. That is a possible implementation path to audit, not proof that article structure belongs in the same field or that the deployed path preserves every correction.

The Content model still governs whole-piece versus moment classification and useful document parts. These choices must preserve source identity, parent documents, captures and evidenced subject relationships. Research documents do not automatically become creative references. No proposed label creates a campaign, product or company connection.

Approval here settles meanings only. Registry reconciliation, prompt choices, correction handling, filtering and representative data checks follow before any relabeling. The review agenda retains every other pending choice.

Last reviewed 4 October 2026.