Two words of coincidence is not evidence, and a construction is not an article - #213
Merged
Merged
Conversation
…n article The anchored gate shipped and the hourly cron wrote its first 162 keywords across 11 sites. The vendor and junk classes are gone. Reading the actual output found two things the fixtures could not have. **Partial matches leaked.** Eight keywords, all one shape: one generic word of a multi-word subject matched, and a word from the generic commercial vocabulary rescued it. "open standards" matched on "open", "software" did the rest, and logicsrc was queued to write about OBS Studio. "supply chain security" matched on "supply" and admitted "industrial automation supply". "online shopping" matched on "online" and admitted "quickbooks online pricing". So a partial match on a multi-word subject may now only be rescued by an anchor the site itself supplied — never by the defaults, which are generic by construction. A complete match is unaffected, including a single-word subject, where "iptv alternatives" is a real query. **And the cross-product floor was publishing constructions.** That one is mine and it was new. Used as per-subject filler it produced "saving money pricing", "deals platform", "coordination d0rz" and "ai content loop" — on-niche, gate-passing, and not topics anybody searches. bl0ggers' niche is "human-in-the-loop AI publishing", so its derived modifiers are literally "human" and "loop", and crossing a subject with those yields nonsense. The crosses' real value was always upstream: as DataForSEO seeds they are what turns "peptide" into "peptide merchant account", and they still seed every expansion. They are simply no longer published on the strength of being grammatically adjacent to the niche. They remain the floor, but site-level rather than per-subject — only a run that would otherwise insert nothing falls back to them, which keeps "a blog with every upstream down still publishes" without letting constructions pad a healthy run. The result reports usedCrossFloor so a site sitting on that for weeks is visible. All eight leaked keywords are now regression cases, with the on-niche keywords from the same run that must still pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013cbcXdpLFUgJZuVfCB4Gzv
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
ThreatCrush Security Scan39 finding(s) HIGH/CRITICAL: 3 | MEDIUM: 27 | LOW: 9
Snippets are redacted; ThreatCrush never prints matched credential material. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #212, from reading its first production output.
The hourly cron wrote 162 keywords across 11 sites and 41 subjects. The vendor
and junk classes are gone — no home-alarm companies on vu1nz, no lawn mowers on
pairux, no stock tickers on bittorrented. Two problems remained that fixtures
could not have surfaced.
Partial matches leaked (8 of 162)
One generic word of a multi-word subject matched, and a generic tail word
rescued it:
open broadcaster software,open source softwareindustrial automation supplyquickbooks online pricingsoftware engineer remoteA partial match on a multi-word subject may now only be rescued by an anchor
the site itself supplied, never by
DEFAULT_MODIFIERS. Complete matches areunaffected — including single-word subjects, where
iptv alternativesis areal query.
The cross-product floor was publishing constructions
Used as per-subject filler it produced
saving money pricing,deals platform,coordination d0rz,ai content loop. On-niche, gate-passing, andnot topics anybody searches. bl0ggers' niche is "human-in-the-loop AI
publishing", so its derived modifiers are literally
humanandloop.Crosses still seed every DataForSEO expansion — that was always their real
value, and it is what turns "peptide" into "peptide merchant account". They are
now a site-level last resort rather than per-subject filler: only a run that
would otherwise insert nothing falls back to them.
usedCrossFlooris reportedso a site stuck there is visible.
Verification
1931 tests pass,
tsc --noEmitclean,next buildcompiles. All 8 leakedkeywords are pinned as regressions alongside the on-niche keywords from the
same run that must still pass.
🤖 Generated with Claude Code
https://claude.ai/code/session_013cbcXdpLFUgJZuVfCB4Gzv