Note on evidence: the Reddit slot in this run contains nothing about Campbell. All 16 items are the front pages of the resolved subreddits — "Colloquialisms" at 264 points, "It's kind of romantic that we're all writing shitty first drafts at the same time" at 486, "I owe John Steinbeck an apology" at 414, "What are you reading?" at 147, "Printing my manuscript has been a game changer" at 141. The 2,696 upvotes in the footer below are almost entirely somebody else's conversation; the two items with any bearing on the topic are an r/Screenwriting thread about Blake Snyder's box-office claims (73 points) and an r/mythology thread about belief (117 points). X returned 3 posts carrying 7 likes total. Both GitHub items are unrelated AI-agent repositories and supply all 515 of the footer's comments. YouTube contributed zero items to the final corpus. Every cluster in the run carries the engine's entity-miss demotion tag. What actually carried this reading: the 18-item web layer plus four supplementary fetches, cited inline.
What I learned:
The scholarly verdict came in decades ago, it was about method rather than taste, and nothing in this window contests it. The folklorists' objection is not that the hero's journey is overused; it is that it was constructed by discarding the counter-examples. Barre Toelken's formulation, quoted on Wikipedia's criticism section, is that "Campbell could construct a monomyth of the hero only by citing those stories that fit his preconceived mold, and leaving out equally valid stories… which did not fit the pattern" — and Toelken tracked the same selection bias forward into Robert Bly's Iron John. Alan Dundes went further, designating Campbell a "non-expert" and writing that "there is no single idea promulgated by amateurs that has done more harm to serious folklore study than the notion of archetype," with the sharper sting in the sentence next to it: "the world is full of self-proclaimed experts in folklore, and a few, such as Campbell, have been accepted as such by the general public." Crespi's complaint (1990) is the useful one for a reader rather than a discipline — Campbell's categories are "so abstract and devoid of ethnographic context that myth loses the very meanings supposed to be embedded." That is a claim you can test yourself against any myth you already know well.
The idea was not even first, which is the detail that gets left out of every popular explainer. Otto Rank published a hero-myth pattern in 1909 and Lord Raglan another in 1936, both predating The Hero with a Thousand Faces by decades and both working the same Freudian seam. What Campbell added was reach, not priority. And the version that actually conquered Hollywood is not his: Christopher Vogler, then a story analyst, wrote a seven-page internal memo condensing Campbell for studio readers, which became The Writer's Journey and supplied the twelve-stage list that every blog now reproduces. So the chain running into a modern writing app is Rank and Raglan, to Campbell's seventeen stages, to Vogler's memo of twelve, to a numbered template — three compressions away from anything anyone studied.
The month's most interesting piece does not attack the monomyth; it supplies a different shape, which is a much harder move."Against the Hero's Journey", published 8 September at 34 likes and 4 comments, spends its energy on two Irish forms Campbell's model has no slot for: the echtrae, an adventure into the Otherworld whose point is to describe that place rather than to extract a boon from it, and the immram, a voyage in which the return fails or transforms. Its worked example is the sharpest thing in the corpus — in immram Bran the returning voyager refuses to land, and the companion who does touch earth crumbles to ash. A story engine where homecoming is the catastrophe simply cannot be expressed in departure-initiation-return. The essay's diagnosis of why series fiction goes flat is the line worth keeping: readers feel "that your world has only one idea about what a story is," and "that is a failure of supply, not of imagination. You learned one shape, thoroughly, and it is a good shape, and it is nothing like as universal as you were told."
Meanwhile the thing itself has finished turning into a product feature, and the receipts are all from this month.StoryFlint's twelve-stage explainer ends by selling "Storyteller OS," a Notion system "designed for writers who want to map each stage." On X, @WritingQuest markets an app that "keeps nine story structures ready: Three-Act, Save the Cat, Hero's Journey, Story Circle, Seven Point, Freytag, Kishotenketsu, custom, or none. Switch freely." That list is the whole argument in miniature: a claim about all human storytelling is now item three in a dropdown, interchangeable with a German dramatic theory from 1863 and a four-act Japanese form that has no conflict in it. The pacing layer has hardened too — one September essay relays K.M. Weiland's percentages as intuition made numeric: if the hero is not called to action by around 12%, "our minds start to wander"; if the threshold is not crossed by a quarter of the way through, "we're calling it quits." Campbell's stages have become a schedule.
Practitioner advice in the window has quietly converged on partial use, and the Campbell Foundation agrees with the practitioners rather than the templates. Vancouver Film School's explainer notes the foundation "specifically cautions against treating all those elements" as required, and states the structural objection more cleanly than most of the academic literature: "a sufficiently flexible framework can make very different narratives look more alike than they actually are." One newsletter tells readers outright that "you don't need every step of the framework," recommending four elements — ordinary world, call to adventure, trials and failure, transformation. Another, published 23 September, demotes it to a size-dependent option: in a 600-word piece prefer a status-quo break and one unresolved loop, and only in a longer narrative "can you afford… a restrained Hero's Journey." Nobody defending the full seventeen or twelve stages appears in this corpus at all.
The only person in the window arguing about it in public got two likes, and still made the most precise concession available.@dvorstone, correcting people using "hero's journey" as a synonym for any heroic story, writes that Campbell "failed" at identifying a monomyth, "but the effort did create an opening to identify a set of dominant myths within a culture, of which his 'monomyth' is one. It's not the ONLY one. It's just the most popular and universal one. In his case, it was exclusive to men." That last clause is where the formal critique has been most productive — Maureen Murdock's The Heroine's Journey (1990) and Kim Hudson's The Virgin's Promise both grew out of it, the latter organised around creative and spiritual awakening rather than an external quest, and David Brin's 1999 objection that the monomyth is congenial to "despotism and tyranny" is filed in the same section.
What is missing from the window is any first-person account of the model failing on a real manuscript. The nearest thing is an r/Screenwriting thread asking "Did Blake Snyder straight up lie about Memento's box-office in Save the Cat?" — 73 points and 88 comments, and notable because the doubt is aimed at a structure guru's evidence rather than at his structure. The corresponding question on the mythology side is live too: r/mythology's "How do scholars of mythology know the difference between a story that was actually believed, and one that was known as fiction?" drew 117 points and 30 comments. Both threads are asking, in different vocabularies, how you check a claim about stories. Neither mentions Campbell. That is roughly the state of things: the method critique is settled and unread, and the model is doing fine.
The version in circulation is Vogler's, not Campbell's — a seven-page studio memo became The Writer's Journey and supplied the twelve stages every explainer reproduces, three compressions from the source material.
The strongest reply is supply, not refutation — the Irish echtrae and immram give you a story engine where the return fails, which departure-initiation-return cannot represent at all.
Working writers already use it partially and say so — "you don't need every step of the framework" and "a restrained Hero's Journey" for longer pieces only; nobody in the corpus defends the complete stage list.
Nobody publishes the experiment that would matter — a writer taking a finished draft and showing where the template made it worse — so the argument stays between scholars who dismissed it and vendors who ship it.
Note on evidence: the footer below is misleading in three separate ways and should not be read as topic engagement. Of 6 Reddit items, none are about tracking dots — a single r/technology thread about Flock camera employees quitting supplies 43,871 of the 45,839 upvotes, and the rest are a Braille printer story, a thermal label printer question and two general privacy threads. All 13 Hacker News stories are keyword traps on "machine" and "printer" (Wayback Machine access, a Lisp machine command runner, the Space Shuttle, "American war machine"); zero are on topic, so the 1,586 points are unrelated. The 22 million YouTube views are dominated by a printer-ink pricing video at 10.6M and an AirTag teardown at 3.9M, and every genuinely on-topic video predates the 30-day window. Of 19 X posts, four are on topic and the rest match on "yellow dots" in stock charts, population genetics, a video game and a memecoin called $Printer. What carried this reading: the GitHub project, the web layer, four on-topic X posts, one in-window forum thread, and three supplementary fetches cited inline.
What I learned:
The practice is settled and the documentation of it has stopped, which is a stranger situation than it sounds. Machine Identification Code — also filed as printer steganography, DocuColor tracking dots, yellow dots or secret dots — is a digital watermark that many colour laser printers and photocopiers place on every printed page, encoding the time, the date and the specific device. Wikipedia's printer article lists thirteen manufacturers doing it: Brother, Canon, Dell, Epson, HP, IBM, Konica Minolta, Kyocera, Lanier, Lexmark, Ricoh, Toshiba and Xerox. None of that is in dispute. What has quietly become impossible is answering the next question — does my printer do it, and what exactly does it encode — because both public instruments for checking have been abandoned.
EFF's list of printers, the canonical reference for twenty years, is retired, and its retirement note is more useful than the list. The page now carries the flat statement that "this list is no longer being updated", against roughly 100 models across HP, Xerox, Canon, Konica/Minolta, Kyocera, Lexmark and OkiDATA. The caveat attached to it is the part that actually changes how you should read any result: a "no" in the table does not mean the printer is clean, because manufacturers may use forensic watermarking methods that are not visible yellow dots at all. EFF added a reminder in 2017 that essentially every recent commercial colour laser printer should be assumed to carry some form of forensic tracking whether or not it appears in the table. So the reference document's final position is that the reference document cannot tell you what you want to know.
The decoder has been frozen for two years, and its open issues are precisely the failure mode.DEDA — "tracking Dots Extraction, Decoding and Anonymisation," the TU Dresden toolkit published in 2018 and the only widely used implementation — sits at 2,586 stars, and its last push was 15 September 2024. Its five open issues read as a list of the tool not working: "unrecognised dots" (February 2021, three comments), "Cant detect a pattern" (April 2024, three comments), a numpy "Mean of empty slice" warning (February 2025, no replies), a Wand policy error and a CUPS filter request from 2018. The README is candid about the boundary in a way the enthusiast coverage never is — it needs lossless PNG scans at 300 dpi, it notes that monochrome and inkjet output typically carries no dots at all, and it warns that it may not recognise newer or divergent tracking patterns. Read that alongside EFF's retirement note and the gap is clear: the encoding is presumed to be evolving and nothing public is tracking the evolution.
The most interesting technical idea in the whole corpus is defensive and counterintuitive — you beat the dots by printing more dots. The TU Dresden work included an anonymisation mode, and the way it works is by printing additional yellow dots on top of the printer's own, overflowing the pattern so it can no longer be read back as a serial number and timestamp. That is the opposite of the instinct, which is to suppress or strip. It also explains the README's odd caveat that pages containing white or light-coloured graphics need extra handling: you cannot overprint a region that was never printed.
Practical advice in the last 30 days has collapsed to a single sentence, and it is a hardware purchase rather than a configuration. The entire in-window actionable corpus is @user329874032 replying "Yellow tracking dots. Buy a black and white printer that uses toner." That lines up with DEDA's own scope note about monochrome output, and it is the only advice that survives the fact that nothing is verifiable — if you cannot check, change the category of device. The one in-window forum thread, on PrinterKnowledge dated 25 August, adds the inspection tip (a blue LED shows the dots better than white light) and then asks a question nobody in the corpus answers: "What if you sell a colour laser printer and the buyer uses it for some criminal activity? I guess you are registered when buying a high end colour laser printer, but can you be unregistered when selling it?" The forensic link is to the machine, and machines change hands.
The folk explanation circulating on X is wrong about the mechanism but right about the conclusion, and one reply gets the design logic exactly right.@LexerLux tells four likes' worth of audience that "the reason your printer is always low on yellow ink is because everything it makes has a secret tracking ID put in so everything it makes can be traced back to it… Not kidding btw" — the tracking is real, the yellow-consumption theory is folklore. The more precise post is @jim_sourdi59400, explaining why a colour printer refuses to work at all when one cartridge is empty: "without the other colors it can't produce the tracking mark used to identify the printer if forgeries are found." Whether or not that is the actual reason for any given lockout, it correctly identifies the origin of the scheme as anti-counterfeiting rather than general surveillance — and the SEO layer has noticed the confusion too, with a buying guide from 29 August existing purely to tell shoppers that MIC is "a forensic feature — not a product type," distinct from the MICR printers used for cheques.
The only genuinely new thought in the window is a comparison, and it runs the analogy in the useful direction.@EAnad0r, on 22 September, notes that invisible marks embedded in generated images, audio and text are being discussed as a novel category and adds: "We've seen this movie before. Color printers have hidden yellow tracking dots with your printer's serial number in every page since the 80s." The comparison is worth taking further than the post does, because the two cases have inverted properties. With generative-model marking the detection method is published, which is why that fight is about removal and why removal tools appeared within weeks. With printer dots the method was never published by the manufacturers, was reverse-engineered once by EFF researchers and once by a university lab, and both efforts have now stopped — so the fight is not about removal at all. It is that after forty years there is no maintained way for an ordinary person to find out what their own printer is writing.
The engagement pattern says this is a story people enjoy rather than a problem people are working on. The biggest on-topic YouTube item is EFF's own "Yellow Dots of Mystery" at 167,642 views — uploaded in 2008. Half as Interesting's version has 1.49M views from 2019. The most recent substantial treatment, Sam Bent's at 36,201 views and 2,201 likes, is from December 2025 and recounts the same history: Xerox and Canon developing the scheme from the mid-1980s under an arrangement with the US Secret Service, surfaced through FOIA documents obtained by EFF. Nothing in the last 30 days adds a fact to that account. The measurement that would change the conversation — someone taking a printer bought in 2026, scanning a page, and reporting whether DEDA can still read it — appears nowhere, and given the state of the toolkit, it is probably the single most valuable thing an interested person could publish.
A negative result carries no information: EFF's own caveat is that an absence of yellow dots does not rule out other forensic watermarking, and their 2017 note says to assume recent colour lasers carry something.
The decoder's open issues are the limitation — "unrecognised dots" and "Cant detect a pattern" sit unresolved, and the README concedes it may not recognise newer or divergent patterns.
Anonymisation works by addition, not subtraction — overprinting extra yellow dots to overflow the pattern, which is why light-coloured regions are the hard case.
Scope is narrower than the panic suggests: monochrome and inkjet output typically carries no dots, which makes "buy a black and white printer that uses toner" the whole of the practical advice.
The analogy to marking generated media runs the wrong way round in an instructive sense — there the method is public so the fight is about erasure; here the method is unpublished and unmaintained, so the fight is about not being able to look.
Attention is retrospective: the top-performing explanations are 18 years and seven years old, and no fact in the last 30 days is new.
The missing experiment is small and cheap — scan a page from a 2026-vintage colour laser and report whether the frozen toolkit can still decode it.
Note on evidence: the Hacker News slot in this run is a pure name collision. All 12 stories are about the mathematician Terence Tao — AI-assisted proofs, Navier-Stokes, finite-time blowup — so the 1,186 points in the footer below have nothing to do with the Daodejing. The engine itself flagged the run with "top evidence is highly concentrated in one source." Reddit returned 5 threads, all from r/taoism and all genuinely on topic, but the engagement is lopsided: a meme post at 661 points and a photo of a nice edition at 579 account for 1,240 of the 1,344 upvotes, while the thread that actually concerns translations drew 5 points. All 5 GitHub items are unrelated quote-corpus repositories. X is the strongest source here, and three supplementary fetches — cited inline — supplied the textual history and the Mitchell background.
What I learned:
"Which translation should I read" is two questions stacked, and almost nobody asking the first one knows the second exists. The English choice sits on top of a Chinese choice that was reopened twice in living memory. The standard received text is the Wang Bi recension, from a commentator who died in 249 CE. The Mawangdui manuscripts, from a tomb sealed in 168 BCE, are two near-complete copies that reverse the order of the book — the Te section comes before the Tao section, so the work most people know as opening with "the way that can be spoken" does not open there. The Guodian bamboo slips, excavated in 1993 and dated before 300 BCE, are older still and contain only about 2,000 relevant characters, roughly 40% of the received text. A translation is therefore a decision about which of three texts to render before it is a decision about how to render it, and none of the popular editions foreground that choice.
The version carrying the month's engagement is the one furthest from the Chinese, by its own admission. Stephen Mitchell's Tao Te Ching — published by HarperCollins in 1988 and subtitled, precisely, "A New English Version" — has sold over a million copies, and it dominates the last 30 days of circulation almost completely. @SophiaCycles posted Mitchell's rendering of the fear passage to 77 likes and 10 reposts; @dailyzen posted his "patience to wait till your mud settles" to 47 likes; @christine_tao1 ran the whole of Verse 25. Mitchell does not read classical or modern Chinese; his version is a re-rendering of earlier English translations, a method one academic treatment files as "a spiritual interpretation" rather than a translation, and the standard sinological complaint against the genre is threefold: it depends on prior translations, it fails accuracy tests, and it simplifies the philosophy. None of that makes the book bad to read. It does mean the most-quoted Laozi in this corpus is, structurally, a poet's English response to other people's English.
The single most useful sentence in 30 days of evidence got one like.@diguapet, on 23 September: "Yes, get an annotated edition. For the Tao Te Ching, D.C. Lau (Penguin Classics) or Red Pine's version with classical commentaries are both solid choices." That is the whole practical answer — not a favourite rendering but a class of edition, one that shows you the decisions rather than hiding them, with Red Pine's carrying commentaries from Taoist scholars, poets, monks and emperors spanning two thousand years. The asymmetry is the finding: a recommendation with reasoning attached drew one like in the same window where a decontextualised quotation drew seventy-seven. Circulation and recommendation are pointing at different books, and the mechanism is obvious once stated — a quotable passage is shareable and an annotated Penguin is not.
The failure mode shows up in miniature as a misattribution nobody caught.@neuroblossom posted the "nothing in the world is as soft and yielding as water" passage — recognisably Mitchell's phrasing — and credited it to a "Stephen Miller translation." At the circulation end of this pipeline even the translator's surname does not survive. That is the same disease, one step worse, as the thread @allonkid started about a keyword in "the Tao Te Ching translation," as though there were one, and as r/taoism's "Help me identify this version of the Tao Te Ching" — someone holding a physical copy, unable to determine which of the 250-plus Western renderings they own. Five points, three comments, and the most honest post in the corpus.
Somebody has built the tool this problem calls for, and it is the month's genuinely useful artifact.laozi-taoteching.org publishes all 81 chapters against the Wang Bi recension "extracted from Wikisource by machine with interlinear glosses stripped, and differences from other lines of transmission recorded as variants," with translations in six languages and, crucially, a misreadings section. Two of its corrections matter for anyone who has absorbed the book through quotations. First, wuwei does not mean inaction — the site glosses it as "withholding the unnecessary," and pairs it with chapter 37's "without acting, nothing is left undone." Second, and more bluntly: "many English 'Lao Tzu quotes' in circulation have no source," and where a line appears nowhere in the base text the site says so outright. A quotation checker for a wisdom text is an odd thing to need. Given that the corpus in front of me contains a misattributed Mitchell passage and an unidentifiable paperback, it is clearly needed.
The reason so many translations exist is grammatical, not mystical, and saying so deflates a lot of the mystique usefully. Classical Chinese, per Wikipedia's own summary, "has no active or passive, no singular or plural, no case, no person, no tense, no mood." Every one of those is a decision the translator must make and the original does not record, which is why the text has been rendered into Western languages over 250 times and why the counts run as high as 1,930 versions across 94 languages, placing it behind only the Bible. The spread of what that licenses is visible in this window alone: Gia-Fu Feng and Jane English read aloud over singing bowls, Stefan Stenudd quoted for an anti-materialism line at 76 likes, a Rosenthal version in a homeschool reading list between The Tao of Pooh and the Gospel of John, and at the far end a full commented translation titled Christ the Eternal Tao by an Eastern Orthodox monastic identifying the Tao with the Logos. These are not competing accuracies. They are different books.
The one person in the corpus doing translation work in public is stuck on exactly the problem the popular editions skip.@FactIndie, announcing a nearly finished Spanish rendering on 12 September at 11 likes, explains why the Mawangdui version is harder: "There are actually two Mawangdui manuscripts, usually called Text A and Text B. They're very similar, but not identical," and "both have gaps from damage to the silk, especially Text A, and some surviving characters are difficult or dis[puted]." That is what the source layer actually looks like — two damaged silk copies that disagree with each other, under a received text edited three and a half centuries later. It also explains why the annotated-edition advice is not pedantry: the notes are where a translator tells you which silk they followed.
Engagement inverts usefulness — 77 likes for a context-free quotation, 1 like for the reasoned recommendation — so the most-shared version is selected for shareability, not fidelity.
Many circulating "Lao Tzu quotes" have no source in the text at all, and there is now a machine-collated site that will tell you which.
Wuwei is not inaction — "withholding the unnecessary", with chapter 37's "without acting, nothing is left undone" as the gloss.
The translation explosion is grammatical: classical Chinese marks no tense, number, case, person, voice or mood, so every English sentence adds information the original withholds — hence 250-plus Western versions.
Nobody in the window compares two named translations of the same chapter side by side, which is the one exercise that would settle a personal choice in ten minutes.
Provenance — 2026-09-23
Redacted by design: this records the funnel shape, not the private source links or
personal capture notes. Raw self URLs and capture-note text are never written here.
Fuel — the first shipped run since 7 September, and the pull was what unblocked it
No pre-pull fuel number was taken. Per the standing rule, a count measured against an
unpulled clone carries no information whatever its value, so the sequence was reordered:
fetch, inspect the filename diff, collect.py (which pulls), thenfuel.py.
The fetch showed the clone 6 commits behindorigin/master. The filename diff — the
cheap pre-pull tell — showed two genuine captures alongside an echo file and a sparks
update. That is the "ordinary dated capture filename" case rather than the all--echo.md
case, and it predicted correctly.
Post-pull: eligible_pool: 4, exit 0, span_days: 9, capture_rate_per_day: 0.44. This
ends a long run of non-shipping mornings whose causes were split between a stranded pool
(two eligible entries against a --min-pool 3 floor, unchanged for three days) and, before
that, an authentication outage that killed five launchd runs before they reached step 1.
Both captures landed on 22 September, which took the pool from 2 to 4 and cleared the floor
for the first time in a fortnight. Retiring three today leaves one entry behind.
Worth recording plainly because two earlier forecasts about capture timing were wrong in
the optimistic direction: this is one observation, not a trend. The trailing-window rates
are still low and nothing here licenses a prediction about the next capture.
Source entries — pool of 4, so step 3 made a real choice for the first time in weeks
Four distinct ids, no same-link twins. references/selection-guidance.md weights the
capture note heaviest, then topical variety. Three of the four notes carried usable signal
and one was a bare description, so the note ranking was: a long, invested note about a
writer's engagement with a classical text; a short note naming a specific worry about
hidden marking in generated media; a brief note about a list of origin stories across
cultures; and, last, a one-line reaction to a model benchmark.
The benchmark entry was dropped rather than picked, for two reasons. Its note was the
thinnest of the four, and picking it would have put three of three picks inside the AI
orbit — the other two entries both touch machine-generated content — which is exactly the
rut the guidance warns against. It stays eligible for a later day, which also matters when
the pool is this tight. The three picks span mythology/culture, privacy/forensics and
philosophy/translation.
The 12 adjacent topics
From entry A (a cross-cultural collection of origin stories):
Aarne-Thompson-Uther and how folklorists index a story
Joseph Campbell's monomyth and what scholars actually say about it — picked
Phylogenetic analysis of folktales and how old a story can be
The Database of Religious History and quantifying belief
From entry B (hidden identifying marks embedded in media):
Google SynthID and whether AI watermarks survive editing — dropped, revisit
C2PA Content Credentials and what actually strips them — dropped, revisit
Zero-width Unicode in LLM output and AI text detection tells — dropped, revisit
Machine Identification Code printer dots and what still prints them — picked
From entry C (a musician's aphoristic book about making things):
Brian Eno's Oblique Strategies and constraint cards in practice
Tao Te Ching translations and which one people recommend — picked
Wu wei and the flow-state claim in creative work
The Creative Act and what practitioners took from it
Replacements drawn after the three drops, all guard-clean: Cinavia and forensic
watermarking in streaming video, AirTag stalking alerts and the unwanted-tracking
standard, and The EURion constellation and banknote detection in software. None took a
slot; the printer-dots candidate was the strongest of the non-AI marking angles on both
liveness and learnability.
Three revisits in one fan-out, none caught by the guard
flag_near_dup returned flagged: false on all twelve candidates and on all three
replacements. Three of the twelve were repeats anyway, and all three were caught only by
the manual grep of data/ for candidate proper nouns:
SynthID appears in three prior briefs (2026/08/17, 2026/07/11, 2026/06/30).
C2PA appears in five files across four days, including two prior briefs.
The 08/17 AI-detectors brief turns out to cover the whole cluster in depth — text
watermark removability, a clean-scan result meaning "no vendor watermark" rather than
"human," and the removal-kit economy. A SynthID or C2PA brief today would have been a
second pass over settled ground.
This is now the fourth recorded occasion of the guard clearing a same-subject repeat, and
the second where it cleared more than one in a single fan-out. The grep is the control; the
similarity score is not. Note the useful negative result too: Aarne appeared once in
data/, but in a candidate list from 2026/06/07 rather than a published brief, so it
was correctly treated as eligible. Distinguishing a prior candidate from a prior brief
matters — a naive grep hit count would have dropped it.
Research — three runs, three differently broken corpora
Engine resolved at the nested plugin path (cache/last30days-skill/last30days/3.3.2/…),
--diagnose confirming v3.3.2 with seven sources, X authenticated and Brave as the web
backend. All three runs used a hand-written --plan with 4 subqueries and Step 0.55
resolution (handles, subreddits, hashtags, and one GitHub repo). Topic strings were kept
short and title-shaped; the discussion-shaped seeds were used for the ranking_query
fields only. Every cluster in every run carried the entity-miss demotion tag.
The footers are unreliable in three distinct ways, each documented in its own brief's
evidence note:
Campbell: all 16 Reddit items are subreddit front pages with no Campbell content, so
the 2,696 upvotes are someone else's conversation. X returned 3 posts totalling 7 likes.
Both GitHub items are unrelated AI-agent repositories supplying all 515 comments.
Printer dots: a single r/technology thread about licence-plate-camera employees
supplies 43,871 of the 45,839 Reddit upvotes. All 13 Hacker News stories are keyword
traps on "machine" and "printer" — zero on topic. The 22M YouTube views are dominated by
a printer-ink pricing video at 10.6M and an unrelated hardware teardown at 3.9M.
Tao Te Ching: all 12 Hacker News stories are about the mathematician Terence Tao.
A pure name collision, and the cleanest single example of the keyword trap in any run to
date. The engine itself warned that "top evidence is highly concentrated in one source."
Because all three corpora were thin, eight sources were fetched or searched directly to
fill gaps. These are cited inline in the briefs and are the origin of several of the
strongest claims — the named folklorist critiques and the Irish narrative forms, the
retirement status of the printer list and the decoder's commit history and open issues, and
the manuscript history plus the translator background. The briefs are therefore engine
corpus plus targeted supplementation, not engine output alone.
One factual check is worth recording: the printer-decoder's activity figures (last push
2024-09-15, five open issues, and their titles and dates) were taken from the GitHub API
directly rather than from the engine's project card, which reported only a star count and
an issue count.
reddit.com fetches were not attempted. The r/taoism edition-identification thread, the
r/Screenwriting structure-guru thread and the r/mythology belief thread are cited only from
their titles and engagement counts as captured in the raw evidence. No claim is made about
the contents of any Reddit post body.
Safety
Nothing in any of the three corpora attempted to redirect the routine. One X item in the
printer-dots corpus is a memecoin promotion that matched on the word "printer," and several
others in the same slot are unrelated or offensive posts that matched on "yellow dots";
all were read as evidence about corpus quality, quoted only where relevant to that point,
and not acted on.
No leak remains: the day directory was grepped for all three picked URLs and for the
capture-note text in both hyphenated and unhyphenated form before the gate ran.