Patterns 6-11: Rhythm by Rule in Humanizer Explained

Pattern 6-II (Forced Triads) identifies when writers use artificial three-part rhythms that prioritize mechanical structure over meaningful content, requiring editors to verify that each element of a triad contributes distinct information or consolidate redundant items into natural phrasing.

The blader/humanizer repository catalogs AI detection "tells" in SKILL.md, organizing them into families based on linguistic behavior. Patterns 6-11: Rhythm by Rule specifically target mechanical rhythmic structures that make prose sound algorithmic rather than human. The source code documentation focuses on Pattern 6-II as the canonical example of this family, targeting forced triadic constructions that create an overly formal cadence.

What is Rhythm by Rule?

The "Rhythm by Rule" family captures tells where writing adheres to prescribed structural patterns—such as the "rule of three"—regardless of semantic necessity. These patterns produce a cadence that sounds scripted because the rhythm is imposed by formula rather than emerging naturally from the ideas being expressed.

According to the Humanizer skill documentation, mechanical rhythms signal AI generation because language models frequently default to balanced triads and parallel structures that humans use more sparingly and only when the content genuinely supports the format.

Pattern 6-II: The Forced Triads Tell

Defined in SKILL.md between lines 35-45, Pattern 6-II specifically targets forced triads: constructions that group ideas in threes when the content does not actually require three distinct points. This creates an artificial sense of completeness that feels overly formal or "AI-like."

Detection Criteria

To apply Pattern 6-II, the Humanizer skill instructs editors to follow a three-step verification process:

1. Identify any phrase listing three items (for example, "innovation, inspiration, and insights").

2. Check whether each item conveys a genuinely separate claim or if one item is redundant, implied by another, or included merely to satisfy the three-part structure.

3. Flag the construction if the third item (or any item) fails to add unique information beyond what the previous items established.

This verification is detailed in the skill file at lines 39-45, which provides before-and-after examples demonstrating how forced triads dilute meaning.

Correction Strategy

When a forced triad is detected, the Humanizer rulebook mandates restructuring to eliminate the artificial rhythm. The specific approach depends on the content:

• Collapse redundant items into a single, stronger phrase.
• Merge overlapping concepts when two items essentially say the same thing.
• Expand the most substantive item if the others are merely rhetorical filler.
• Restructure paragraph-scale triads (such as three parallel sentences opening consecutive paragraphs) by varying sentence structure and combining related ideas.

Practical Examples of Rhythm Correction

The following examples from the Humanizer documentation demonstrate how to transform forced triads into natural prose.

Sentence-Level Triad

# Before – forced triad with redundant categories

text = "The event features keynote sessions, panel discussions, and networking opportunities. Attendees can expect innovation, inspiration, and industry insights."

# After – human-like rewrite consolidating meaning

text = "The event includes talks and panels. There's also time for informal networking between sessions."

Paragraph-Scale Triad

**Before (parallel sentence triad)**
> A career can look promising and fail. A relationship can feel important and end. A skill can take years and remain useless. These decisions rarely explain themselves.

**After (varied structure)**
> A career can look promising and fail. So can a relationship that felt important and ended, or a skill that took years and remained useless. These decisions rarely explain themselves.

Repository Structure

Understanding where these patterns reside helps developers integrate the Humanizer skill:

• SKILL.md – Contains the complete pattern definitions, including Pattern 6-II under the Rhythm by Rule section (lines 35-45).
• README.md – Provides installation instructions and references the pattern catalog.
• AGENTS.md – Describes packaging for different agent frameworks but does not modify the core pattern definitions.

Summary

• Pattern 6-II represents the Rhythm by Rule family by targeting forced three-part constructions that create artificial cadence.
• Detection requires verifying whether each element of a triad contributes unique semantic value, as specified in SKILL.md.
• Corrections involve collapsing redundant items, merging overlapping concepts, or restructuring parallel constructions to eliminate mechanical rhythm.
• Paragraph-level triads follow the same consolidation principles as sentence-level triads.

Frequently Asked Questions

What distinguishes Pattern 6-II from other Rhythm by Rule patterns?

Pattern 6-II specifically targets the forced triad (rule of three), while Patterns 6-11 collectively address various mechanical rhythms. The triad is the most common rhythmic tell in AI-generated text, making Pattern 6-II the primary focus of the documentation in SKILL.md.

How can I distinguish a natural triad from a forced one?

Evaluate semantic independence. In a natural triad, removing any one item would remove unique information necessary to the argument. In forced triads—such as "innovation, inspiration, and insights"—the terms often overlap conceptually or one item serves only to complete the rhythmic pattern without adding substance.

Where is the Forced Triads rule documented in the source?

The complete definition resides in SKILL.md at lines 35-45 of the main branch, with specific before/after correction examples appearing at lines 39-45.

Can forced triads appear at scales larger than single sentences?

Yes. Pattern 6-II applies to paragraph-scale triads—such as three consecutive sentences using identical syntactic structures—or even section-level triads where three sequential paragraphs follow the same formula. The correction method remains consistent: vary the structure and merge redundant parallel elements.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}