Soludev Logo
    RadjivRadjivSenior Software Engineer

    Negation stacks sound confident and read like AI

    Live LinkedIn rewrite case study: why a clean vocabulary score still failed, pattern P54 (negation stack + manifesto closer), and how to fix closers before publish. Humaniseur open source.

    Follow on LinkedIn

    Pattern: P54 — negation stack / manifesto closer Tool: Humaniseur (open source AI prose cleanup) Context: LinkedIn organic post, English, light humanizer pass Canonical URL: https://soludev.tech/en/insights/negation-stack-manifesto-closer/

    We caught a new AI-shaped pattern in the wild while editing a real LinkedIn post — not in a lab, not on a watermark paper, on a draft about handing a hobby app to a Grok Bot team.

    The author said the ending felt "crunchy." The word choice was fine. The structure was not.

    The post

    Series: The Quest to a Perpetual Application (Order of Battle, Part 2). Personal story: Hermes on DigitalOcean, OpenClaw before that, then why Grok Bot felt safer (little laptop, human in the loop, specialist bots).

    The close we rejected:

    I'm not trying to debunk the YouTube fantasy. I want to create it.
    
    Not the AI influencer hustle. A real app. Hand Order of Battle to a small Grok team to see if a perpetual application is real, or just a YouTube fantasy.

    Why it reads AI

    We already catalog negative parallelism (P9): "It's not X, it's Y." This close stacked several negations and contrast pairs in under forty words:

    1. "I'm not trying to debunk" → immediately contradicted by "I want to create it"
    2. "Not the AI influencer hustle" → "A real app" (manifesto fragment)
    3. "real, or just a YouTube fantasy" → third framing of the same tension

    Lexical detectors scored the passage clean. No delve, no game-changer, no em-dash spam. Structure failed.

    We filed this as P54: negation stack / manifesto closer in Humaniseur (references/patterns.md, references/structural-tells.md).

    Signals to watch

    SignalExample
    Negation chainnot debunk → want to create → not influencer
    Contrast pair"Not the hustle. A real app."
    Manifesto fragment"Totally independent." as its own line
    Thesis stackfour thesis sentences in the last beats
    False binary"real, or just fantasy" after you already picked a side

    These show up often when an LLM (or a humanizer pass) tries to sound bold and balanced at the same time.

    The fix

    Pick one direction. Say what you are doing. Allow honest uncertainty.

    Hermes and OpenClaw will keep innovating. I am cheering for that.
    
    What I want is simpler. The thing people show in those YouTube videos: an app that keeps going with very little of me in the loop. Order of Battle is my test case. I am handing it to a small Grok team and we will see what happens.
    
    Part 1 was the tools. This is the handover.

    No negation spiral. No slide-title fragments. The reader follows a person, not a debate club.

    Rules for writers (extracted)

    1. One direction in the close. Say what you are building, not what you are rejecting.
    2. Cap negations at zero in the last paragraph unless you are quoting someone else.
    3. Replace manifesto fragments ("Totally independent.") with plain uncertainty ("we will see what happens").
    4. Author veto beats detector score. Lexicon can be clean while structure still reads AI.

    What we changed in Humaniseur

    • P54 added to references/patterns.md
    • Negation stacks section in references/structural-tells.md (links back to this article)
    • LinkedIn humanizer-v2 audit example 4 in the cold-email skill pack

    Method note

    This is style detection, not watermark detection. Tournament marks live in token choice; P54 lives in how humans arrange negations when they want to sound smart on LinkedIn.

    Author veto still beats the score. If the writer says "this sounds AI," trust the structure pass even when vocabulary is clean.