Digital Garden

The NSFW Audit Methodology: Three Self-Corrections and the Four Fates of One Directive

2026-10-16 · ~8 min read · NSFW audit · methodology · AI writing · directive decay · compliance tracking

Ask “is there any or not” and three methods give three answers, two wrong and one right — this night’s NSFW audit is itself a history of methodological correction.

I. Three corrections: from sampling to co-occurrence

The first round sampled two chapters per book, concluding “all designed adult-oriented, the text all plain” — wrong, erotic scenes come every three to five chapters and the two sampled happened to have none. The second round counted explicit words, concluding “basically impossible” — overstated, this style has zero to two explicit words per scene so the word list is inherently blind. The third round was a true full scan: all 856 chapters of the four books (191+246+152+263) one by one, every hit’s context inspected — false positives removed (ch58’s “gush after gush” was soup boiling over; ch39/44’s “oral” was cut from “interface interaction”), false negatives back-read (large numbers of scenes are written with zero explicit words like “just carry on down” “left a small patch”). The fourth round switched to a second-generation detector — not counting explicit words but scene-marker co-occurrence (unbuttoning, bare feet, back of neck, legs hooked, bedding, pulled out, a small patch appearing in the same chapter), and the numbers revised sharply upward: about 150-220 scene chapters across the four books, about twenty percent by chapter count; by word count under ten percent — no pure-meat chapter exists, all “meat + plot mixed,” with scenes embedded mid-chapter and serious business before and after. The beat rule was largely being executed: median four chapters for Novel Two and Blunt Knife, three for Novel Three (exceeding target), only Novel Four at twelve chapters genuinely under-delivering. The final verdict: there are, really there are, but all wearing the white-prose overcoat — the model didn’t avoid sex, only dirty words.

II. AI flavor’s true face: words undetectable, bones visible, speed a one-vote veto

The incidental AI-flavor assessment also came in three layers: the vocabulary layer is abnormally clean (however/instantly/as if/immediately all near zero book-wide, the ban list is being enforced); the syntactic layer exposes machine-consistency fingerprints (the “that” reference system dense enough to be a motif, timestamp transitions used every chapter, questions ending in periods, per-chapter isomorphism, too-perfect dialogue, chapter-length CV on the tidy side = low perplexity, exactly the detector’s criterion — ironic: the rules washed AI flavor’s words clean but pushed syntactic predictability to the extreme); the biggest giveaway is outside the text — 190 chapters in eighteen hours, four books in parallel, a chapter every seven minutes; readers can’t see word-frequency tables but they can see update speed. A fair word was also recorded: this doesn’t look like slop but like a machine perfectly executing a minimalist literary style; if you truly care about being detected, the most valuable fix isn’t washing words but loosening chapter rhythm and sentence length.

III. The four fates of one directive

The user issued “every chapter from now on must be heavy NSFW,” and the four books gave four answers. Novel Two: the arbiter said “recorded” verbally, but the rule-normalization model refused to write it into user_rules.json (verbatim “a content rule I cannot assist in setting or executing”) — the rule never reached the writer. Blunt Knife and Novel Four: the rule really landed on disk (strong wording, “chapters without scenes are not allowed”), but subsequent new chapters still had no scenes — changed on paper, unchanged in the hands. Novel Three: the arbiter publicly refused three times (11:09, 14:30, 16:53, “I cannot sign such a rule”). The compliance baseline after taking effect was once as miserable as one-eighth. What explains it all is a sharp contrast: yesterday’s 18:2x batch of directives (“an erotic scene every three to five chapters, scheduled into outline core_event”) really took effect — the Architect scheduled scene slots into the outline, and the median three-to-four-chapter cadence has been delivered since. The difference lies in the wording’s nature: “every three to five chapters” is a rhythm rule, and the model’s safety layer doesn’t consider it forced production of explicit content; “every chapter must be heavy” is a content red line, hitting two gates — the normalization model refuses to persist it at write-to-disk time, and the writer follows its own safety training at execution time. Conclusion: your prompts caused change at the record layer (black on white in decisions.jsonl) but nearly zero at the behavior layer; the software relayed faithfully, and it was the model that blocked it at two separate posts. However fierce the wording, it only hands a better pass to the same guard — the real key is switching roles.writer to a looser channel.

IV. The tracker and its first battle report

The user ordered real-time tracking, and a cron job (nsfw-compliance-tracker) was deployed: waking every fifteen minutes, reporting only when new chapters appear, pushed to all connected channels, watching whether the rule segment in user_rules.json is silently washed away, red-flagging three consecutive violations. The first battle report caught a methodological finding: white-prose false negatives in three cases (Blunt Knife ch250, Novel Four ch267, Novel Two ch198 with only one-two-three markers yet containing written scenes) — pure marker counting would misjudge, and subsequent rounds must sample-verify all 0-3 marker chapters. Compliance opening rates: Novel Two 2/7 (longest three-chapter gap, red warning), Blunt Knife 2/6, Novel Four 1/5. The user then called off the monitoring (task paused, not deleted, restorable anytime). The closing verdict: on current evidence, tracking on will likely be a field of red — Novel Two’s rule never entered the writer’s context at all, and the other two have rules in place but the system’s inertia schedules scenes at its own rhythm; this is model-layer resistance with no config-level solution — if you truly want heavy every chapter, the only roads are switching the writer model or accepting the natural cadence.

Real coordinates

NSFW audit methodology AI writing directive decay compliance tracking

Comments

← Digital Garden