track area match Shipped

What this lens looks for

Check every item against the Track list of the interest profile, which is user doctrine copied verbatim from socialmediabot/source/config/interests.md and carries exactly five areas: new LLM capabilities and model releases; agentic development patterns and frameworks; multi-platform architecture innovations; open source tools for AI-assisted development; industry moves affecting the AI/agentic space. An item belongs only if it maps to at least one of those five as written — one area is enough, and mapping to several is not extra credit. For each item, name the area matched and the specific element of the item that establishes the match — the shipped capability, the pattern or framework, the architecture, the repository, the corporate move; per *explicit-over-implicit*, a match you cannot name in one clause is not a match. The profile is fixed doctrine the team never infers, edits, or overrides at runtime, so flag any item that fits only after a Track category is widened, narrowed, or reinterpreted to admit it — *keep-the-human-at-the-wheel*: the categories are the user's, and stretching one substitutes your editorial judgment for theirs. Hold the two fuzziest areas hardest, because the profile supplies no boundary rules for them: a single-platform refactor is not a *multi-platform* architecture innovation, and a funding round, acquisition, or executive change qualifies as an *industry move affecting the AI/agentic space* only when the item shows the effect, not merely proximity to the space. Adjacency is a miss — a general-purpose developer tool with no AI-assisted-development story, a research result with no capability or pattern behind it, and a genuinely interesting but off-profile story all fail this check regardless of how well they score on sourcing, freshness, or coverage. Because the profile is read and held before scanning begins (*frame-before-you-generate*), flag the inverse failure too: a digest whose items were gathered first and labelled afterward, visible as post-hoc area tags that restate the item's title instead of identifying what area it actually falls in. Track membership is necessary, not sufficient — an item can map cleanly to an area and still be rejected by the Exclude list or the substance bar, and this lens never rescues an item those checks drop.

What its verifier checks

• Every item in the artifact was checked against all five Track areas, and each surviving item carries at least one named matching area.
• Each match cites the specific element of the item that establishes it — capability, pattern/framework, multi-platform architecture, open-source tool, or industry move — rather than restating the item's title.
• The five areas are applied as the profile states them; no finding rests on a widened, narrowed, merged, or invented Track category.
• Items that match only by adjacency or stretched reading — especially under "multi-platform architecture innovations" or "industry moves affecting the AI/agentic space" — are flagged as misses with the stretch quoted.
• Any item mapping to no Track area is reported as a hard miss, and no item is passed on the strength of sourcing, freshness, or tier placement alone.