@modality-counter/core 0.5.2 → 0.5.4

package/dist/index.js

@@ -651,151 +651,151 @@ ${r.join(`
 ${o}
 `),new Error(`Template validation failed for ${n.length} template files. See console for details.`)}console.log(`\u2705 Template validation passed: ${i}/${t.length} templates`),bN(i).toBe(t.length)}),NTe("should have discovered expected template files",()=>{if(t.length===0){console.log("\u23ED\uFE0F  Skipping template discovery check - no templates found");return}bN(t.length).toBeGreaterThan(0),console.log(`\u{1F4C1} Discovered ${t.length} template files:`,t.map(n=>n.filename))})}),hyr("Template Structure Validation",()=>{NTe("should validate all template structure requirements in single pass",()=>{let n=[{name:"valid-template",shouldPass:!0,template:{name:"Test Template",description:"A valid test template","test-template":{template:{output:{format:"markdown",filename:"test.md"}},execution_flow:["Execute"],sections:{intro:{title:"Intro",description:"Intro"}}}}},{name:"nested-execution-flow",shouldPass:!1,template:{name:"Nested Flow Template",description:"Template with execution_flow in wrong place","test-template":{template:{output:{format:"markdown"},execution_flow:["Fail"]},sections:{test:{title:"Test",description:"Test"}}}}},{name:"missing-root-sections",shouldPass:!1,template:{name:"Missing Sections",description:"Template missing sections","test-template":{template:{output:{format:"markdown"}},execution_flow:["Execute"]}}},{name:"duplicate-sections",shouldPass:!1,template:{name:"Duplicate Sections",description:"Template with sections in wrong place","test-template":{template:{output:{format:"markdown"},sections:{intro:"Intro"}},sections:{intro:{title:"Intro",description:"Intro"}}}}},{name:"metadata-not-allowed",shouldPass:!1,template:{name:"Extra Fields",description:"Template with extra fields","test-template":{template:{output:{format:"markdown"}},sections:{intro:{title:"Intro",description:"Intro"}},metadata:{version:"1.0"}}}}],i=[];n.forEach(({name:o,shouldPass:a,template:s})=>{let c=pz(s).success;c!==a&&i.push(`${o}: expected ${a?"pass":"fail"} but got ${c?"pass":"fail"}`)}),i.length>0&&console.error("Structure validation failures:",i),bN(i.length).toBe(0)}),NTe("should enforce execution_flow location constraints",()=>{let n={name:"Invalid Nested",description:"Execution flow in wrong place",test:{template:{output:{format:"markdown"},execution_flow:["Invalid"]},sections:{test:{title:"Test",description:"Test"}}}},i={name:"Valid Root",description:"Execution flow at root level",test:{template:{output:{format:"markdown"}},execution_flow:["Execute","Process","Parse","Generate"],sections:{test:{title:"Test",description:"Test"}}}},o={name:"No Execution",description:"Template without execution flow",test:{template:{output:{format:"markdown"}},sections:{test:{title:"Test",description:"Test"}}}};bN(pz(n).success).toBe(!1),bN(pz(i).success).toBe(!0),bN(pz(o).success).toBe(!0)})})})}import{Fragment as cPs,jsx as Tse,jsxs as lPs}from"react/jsx-runtime";function fPs(e={}){let{wrapper:t}=e.components||{};return t?Tse(t,Object.assign({},e,{children:Tse(r,{})})):r();function r(){let n=Object.assign({hr:"hr",h2:"h2",pre:"pre",code:"code"},e.components);return lPs(cPs,{children:[Tse(n.hr,{}),`
 `,Tse(n.h2,{children:`name: AI Pattern Elimination Protocol
-description: "Comprehensive system for detecting and removing AI writing patterns. Integrates 24 distinct patterns across content, language, style, communication, and personality dimensions. Includes pattern detection, validation rules, sentence rhythm guidance, and paragraph structure variety."`}),`
+description: "Detect and remove 24 distinct AI-generated writing patterns. Stop sounding like a machine. This protocol catches the telltale signs that separate human writing from synthetic output\u2014from vocabulary clustering to fake depth, formulaic structures to soulless voice."`}),`
 `,Tse(n.pre,{children:Tse(n.code,{className:"language-yaml",children:`ai-pattern-elimination-protocol:
   ai_pattern_elimination:
-    purpose: "Detect and remove 24 AI writing patterns that make content sound artificial. Organized by category: argument structure, vocabulary, style, communication, attribution, filler, and personality."
-    scope: "All 24 patterns preserved with detection rules, examples, and fixes. Optimized for fast scanning and precise identification."
+    purpose: "Stop sounding like a machine. AI text has signatures\u2014predictable patterns, inflated vocabulary, theatrical contrasts, and soulless rhythms. Catch them. Kill them. Write like a human."
+    scope: "24 patterns with detection rules, real examples, and fixes you can apply immediately. Organized by argument structure, vocabulary, style, communication, and personality."
 
     # ===== SECTION 1: ARGUMENT STRUCTURE (Patterns 1-3) =====
     # Detect false balance, artificial emphases, and theatrical presentation
 
     contrasts_false_balance:
-      purpose: "Identify dramatic contrasts, hedging fence-sitting, and theatrical reveals that avoid taking clear positions"
+      purpose: "Catch the AI's obsession with theatrical contrasts. It loves building tension through fake balance, then 'revealing' the real truth in a separate sentence. Humans don't write this way."
       patterns: ["This is not X, but Y", "Not only...but also", "On one hand...on the other", "This is not first time. This is 17th."]
-      why_bad: "Sounds formulaic and debate-templated; avoids clear analytical positions; overly theatrical for effect"
-      detection_markers: ["Parallel structure with 'not...but'", "Two-sentence dramatic reveals", "Fence-sitting language avoiding commitment"]
-      fix: "Replace with direct statements, clear positions anchored in evidence, and specific mechanism details"
+      why_bad: "It's formulaic and debate-templated\u2014pure argument structure, no actual position. The theatrical reveal is a dead giveaway."
+      detection_markers: ["'not...but' parallel structures", "Two-sentence dramatic setup and payoff", "Fence-sitting before the big reveal"]
+      fix: "Skip the theater. State the position directly, backed by evidence and mechanism."
       example: "NOT: 'It's not just about X; it's Y' \u2192 USE: 'The heavy beat adds aggression\u2014it accelerates listener perception of threat'"
 
     emphasis_inflation:
-      purpose: "Detect AI inflation of arbitrary details into false grand significance and citation stacking without substance"
+      purpose: "AI loves inflating meaningless details through vague superlatives. It name-drops publications instead of providing evidence. Watch for it."
       patterns: ["stands as a testament", "marks a pivotal moment", "landmark achievement", "widely recognized", "cited in major outlets"]
-      why_bad: "Inflates minor details through emotional language; implies importance via name-dropping instead of showing concrete impact"
-      detection_markers: ["Abstract noun + superlative in same sentence", "Multiple sources listed without specific claims", "Words like 'widely', 'extensively' as evidence"]
-      fix: "Use specific facts, dates, quotes, verifiable outcomes, and concrete impact metrics instead of superlatives"
+      why_bad: "Uses emotional words to fake importance instead of providing evidence. Name-drops sources without specific claims. Just vibes."
+      detection_markers: ["Superlatives paired with abstract nouns", "Multiple sources mentioned but no specific facts", "Words like 'widely' replacing actual data"]
+      fix: "Give specifics. Dates. Quotes. Actual impact numbers. No vibes."
       example: "NOT: 'cited in major outlets' \u2192 USE: '2024 NYT interview: argued AI regulation should focus on outcomes, not process'"
 
     # ===== SECTION 2: VOCABULARY & LANGUAGE (Patterns 4-10) =====
     # Detect inflated vocabulary, superficial analysis, and forced linguistic patterns
 
     ai_vocabulary_overuse:
-      purpose: "Identify high-frequency AI-generated words clustering unnaturally in post-2023 text"
-      patterns: ["additionally", "landscape", "testament", "embodies", "encapsulates", "interplay", "delve into", "illuminate", "leverage", "demonstrates", "crucial"]
-      why_bad: "These words appear disproportionately in AI output and cluster unnaturally together; signals synthetic content"
-      detection_markers: ["2+ AI vocabulary words in same sentence", "3+ words from list in single paragraph", "Cluster of synonyms in sequence"]
-      fix: "Replace with simpler, concrete alternatives; eliminate redundancy and synonym cycling"
+      purpose: "Machines have favorite words. They cluster them unnaturally. Real writers don't write like this."
+      patterns: ["additionally", "landscape", "embodies", "encapsulates", "interplay", "delve into", "illuminate", "leverage", "demonstrates", "crucial"]
+      why_bad: "These words scream AI when they cluster together like this\u2014and they do, constantly. That multiple-synonym-in-one-breath signature? That's a machine trying to sound smart."
+      detection_markers: ["2+ of these words in one sentence", "3+ in a single paragraph", "Synonym cycling"]
+      fix: "Use simple words. Real words. Specific words. Repeat if you need to."
       example: "NOT: 'enduring testament...embodies...encapsulates cultural interplay' \u2192 USE: 'Pasta dishes, introduced during Italian colonization, remain common'"
 
     superficial_ing_verbs:
-      purpose: "Detect present participles faking analytical depth without real causation or explanation"
+      purpose: "AI uses -ing verbs to fake depth. It sounds poetic but says nothing."
       patterns: ["highlighting how", "reflecting the", "symbolizing", "evoking a feeling", "cultivating a sense", "demonstrating how", "illustrating"]
-      why_bad: "Tacks -ing phrases to create pseudo-poetic meaning without explaining actual causes or deliberate choices"
-      detection_markers: ["Multiple -ing verbs in single sentence", "Abstract nouns after -ing (essence, spirit, soul)", "No explicit agent or action"]
-      fix: "Use active verbs showing deliberate action with concrete details and causation"
+      why_bad: "Multiple -ing verbs strung together feel poetic but contain zero actual information. No agent, no causation, no real meaning."
+      detection_markers: ["Multiple -ing verbs in one sentence", "Abstract nouns after -ing (essence, spirit, soul)", "No one actually doing anything"]
+      fix: "Use real verbs. Show who did what. Explain why it matters."
       example: "NOT: 'reflecting connection, symbolizing bluebonnets, evoking place' \u2192 USE: 'Architect chose blue and yellow to match landscape'"
 
     promotional_superlatives:
-      purpose: "Identify marketing-style adjectives and superlatives violating neutral editorial tone"
+      purpose: "AI uses marketing language even in neutral contexts. It's trying to persuade when you need facts."
       patterns: ["vibrant", "stunning", "breathtaking", "nestled", "charming", "exquisite", "extremely important", "absolutely critical", "must-visit"]
-      why_bad: "Mimics marketing copy rather than neutral reporting; uses superlatives as fake evidence instead of substance"
-      detection_markers: ["Subjective adjectives clustered in single sentence", "Emotional language framing factual claims", "Praise words without supporting data"]
-      fix: "Remove adjectives entirely; show impact with data, specific characteristics, and concrete effects"
+      why_bad: "These words are marketing, not reporting. They substitute emotion for evidence."
+      detection_markers: ["Multiple superlatives in one sentence", "Emotional language framing facts", "Praise without actual data"]
+      fix: "Delete the adjectives. Give facts instead. Show what it does, not how it makes you feel."
       example: "NOT: 'Nestled in breathtaking region, vibrant town with rich heritage' \u2192 USE: 'Alamata Raya Kobo is a town in Gonder, known for its weekly market'"
 
     copula_avoidance:
-      purpose: "Detect replacement of simple verbs (is/are/has/have) with unnecessarily elaborate constructions"
+      purpose: "AI avoids simple verbs. It uses fancy replacements instead of 'is' and 'has'."
       patterns: ["serves as", "stands as", "features", "offers", "provides", "acts as", "constitutes", "functions as", "boasts"]
-      why_bad: "Inflates sentences with wordiness; adds unnecessary complexity to simple predicate statements"
-      detection_markers: ["Copula-replacement verb in predicate position", "Multiple instances in same paragraph", "Can be simplified to 'is' or 'has'"]
-      fix: "Replace with simple 'is', 'are', 'has', 'have' or delete entirely for directness"
+      why_bad: "Unnecessary wordiness. Adds complexity where simplicity works better."
+      detection_markers: ["Fancy verb where 'is' or 'has' would work", "Multiple instances in one paragraph", "Can be simplified"]
+      fix: "Use 'is', 'are', 'has', 'have' instead. Or delete it entirely."
       example: "NOT: 'serves as exhibition space and features four spaces' \u2192 USE: 'is the exhibition space with four rooms'"
 
     rule_of_three_elegant_variation:
-      purpose: "Identify forced triplets and synonym cycling caused by LLM repetition-penalty mechanisms"
+      purpose: "AI defaults to three-item lists and cycles through synonyms. Humans don't do this."
       patterns: ["forced X, Y, and Z triplets", "protagonist...character...figure...hero", "company...firm...organization...entity", "said...remarked...noted...stated"]
-      why_bad: "Creates artificial comprehensiveness; synonym cycling wastes space and reads unnaturally; signals LLM pattern completion"
-      detection_markers: ["Exactly 3 items with third feeling forced", "4+ different synonyms in 3 consecutive sentences", "Multiple synonyms for same entity"]
-      fix: "Use natural number of elements; repeat same term or use pronouns naturally"
+      why_bad: "It creates fake comprehensiveness\u2014the appearance of covering more ground than you actually do. Synonym cycling fills space without adding meaning, which is how LLMs avoid repetition penalties."
+      detection_markers: ["Exactly 3 items and the third feels forced", "4+ synonyms in 3 consecutive sentences", "Repeating the same idea with different words"]
+      fix: "Use how many items you actually need. Repeat the same word if it fits."
       example: "NOT: 'innovation, inspiration, and industry insights' \u2192 USE: 'talks and informal networking'"
 
     false_ranges:
-      purpose: "Detect 'from X to Y' phrasing with abstract/extreme endpoints faking comprehensiveness"
+      purpose: "AI uses vague 'from X to Y' language to fake comprehensiveness. It's not actually covering all that ground."
       patterns: ["from X to Y (abstract endpoints)", "from smallest to largest", "spans everything from", "microscopic to macroscopic", "singularity to grand"]
-      why_bad: "Creates false comprehensiveness through artificial scope; implies coverage that doesn't actually exist in text"
-      detection_markers: ["Metaphorical endpoints (essence, spirit, void)", "Extreme opposites suggesting comprehensive coverage", "Vague abstract ranges"]
-      fix: "Use specific list of actual topics covered; remove false range entirely if inaccurate"
+      why_bad: "Fake scope. The text doesn't actually cover what the range implies."
+      detection_markers: ["Poetic endpoints (essence, spirit, void)", "Extreme opposites", "Vague abstractions"]
+      fix: "List the actual topics covered. If you can't, remove the false range."
       example: "NOT: 'from singularity to cosmic web' \u2192 USE: 'covers the Big Bang, star formation, and dark matter'"
 
     # ===== SECTION 3: STYLE & FORMATTING (Patterns 11-16) =====
     # Detect formatting patterns, punctuation habits, and chatbot artifacts
 
     punctuation_formatting:
-      purpose: "Identify excessive punctuation, mechanical emphasis, and algorithmic formatting patterns"
-      em_dashes: "Limit to 1 per paragraph maximum; replace excess with commas, periods, or parentheses"
-      boldface: "Remove mechanical emphasis of scattered terms; use boldface sparingly for critical terms only"
-      inline_headers: "Avoid **Header:** structure in vertical lists; use full prose paragraphs instead"
-      title_case: "Use sentence case in headings, not Title Case\u2014standard editorial practice, not algorithm signal"
+      purpose: "Machines love punctuation and formatting. Too much is the signature of AI writing."
+      em_dashes: "Max one per paragraph. Replace extras with commas, periods, or parentheses."
+      boldface: "Minimal. Only for critical terms. Don't scatter emphasis everywhere."
+      inline_headers: "No. Avoid **Header:** structure in lists. Use prose instead."
+      title_case: "Stop capitalizing Every Word. Use sentence case. It's the standard."
       example: "NOT: '\u{1F680} **Launch Phase:** product launches in Q3' \u2192 USE: 'The product launches in Q3 with three months preparation'"
 
     chatbot_artifacts:
-      purpose: "Detect decorative elements, smart quotes, and people-pleasing servility from unedited ChatGPT output"
-      patterns: ["decorative emojis (\u{1F680} \u{1F4C8} \u{1F3AF})", "curly/smart quotes instead of straight", "Great question!", "You're absolutely right!", "I hope this helps", "Let me know if you'd like"]
-      why_bad: "Signal unedited ChatGPT output in professional content; break editorial frame; inappropriate servility"
-      detection_markers: ["Emojis at start of lines/headings", "Unicode curly quotes vs. straight ASCII", "Conversational asides mid-argument"]
-      fix: "Remove all decorative emojis; replace smart quotes with straight ASCII; state facts directly without people-pleasing"
+      purpose: "These are ChatGPT's calling cards. Remove them all."
+      patterns: ["decorative emojis (\u{1F680} \u{1F4C8} \u{1F3AF})", "smart quotes instead of straight quotes", "Great question!", "You're absolutely right!", "I hope this helps", "Let me know if you'd like"]
+      why_bad: "Dead giveaway that this was generated by ChatGPT and never edited. Breaks professional tone."
+      detection_markers: ["Emojis at the start of lines", "Curly quotes (Unicode) instead of straight", "Conversational fillers mid-argument"]
+      fix: "Delete emojis. Use straight ASCII quotes. State facts directly. No cheerleading."
 
     # ===== SECTION 4: COMMUNICATION & ATTRIBUTION (Patterns 17-21) =====
     # Detect vague sources, hedging qualifiers, filler, and formulaic structures
 
     vague_attribution_meta_communication:
-      purpose: "Identify undefined source attributions and AI meta-communication that breaks editorial frame"
+      purpose: "AI uses vague sources to hide that it doesn't know anything. It also talks about its own limitations."
       patterns: ["Industry reports show", "Experts argue", "Studies suggest", "It's commonly known that", "as of my last training", "While details are limited", "I don't have current information"]
-      why_bad: "Undefined sources prevent verification; AI disclaimers break frame; suggest hallucination and knowledge gaps"
-      detection_markers: ["Generic source words without name/date", "Plural pronouns without antecedent", "Claims without numerical data"]
-      fix: "Cite specific person/organization/year/publication with actual evidence, quotes, or numerical data"
+      why_bad: "No sources means no verification. AI disclaimers break the frame and admit hallucination."
+      detection_markers: ["Generic 'experts' or 'reports' without names", "Vague plural pronouns", "No data to back up claims"]
+      fix: "Name the source. Give dates. Provide actual numbers. No 'experts say'."
       example: "NOT: 'Experts believe crucial role' \u2192 USE: '2019 Chinese Academy survey found 23 endemic fish species'"
 
     hedging_filler:
-      purpose: "Detect stacked qualifiers weakening claims and filler phrases inflating word count"
+      purpose: "AI stacks qualifiers when uncertain. It also uses wordy filler that humans would cut."
       patterns: ["could potentially possibly", "might have some effect", "In order to", "Due to the fact that", "At this point in time", "may arguably"]
-      why_bad: "Stacked qualifiers (2-3+) signal uncertainty compensation; filler adds unnecessary words weakening directness"
-      detection_markers: ["2+ qualifier words in single sentence", "Multi-word phrases replaceable by single word", "Negation + qualifier constructions"]
-      fix: "Use zero qualifiers if confident; single qualifier only if uncertain; replace filler with direct single-word alternatives"
+      why_bad: "Multiple qualifiers scream uncertainty. Filler phrases waste space."
+      detection_markers: ["2+ qualifiers in one sentence", "Multi-word phrases that should be one word", "Negation + qualifier stacking"]
+      fix: "Be confident or be honest about uncertainty. Never both. Replace filler with single words."
       replacements: {"In order to": "To", "Due to the fact that": "Because", "At this point in time": "Now", "Has ability to": "Can", "It is important to note": "[delete]"}
 
     formulaic_structure_conclusions:
-      purpose: "Identify rigid LLM outline structures and generic upbeat endings without substance"
+      purpose: "AI writes from templates. The structure is too predictable. The endings are generic."
       patterns: ["Despite X, continues to thrive", "Future Outlook sections", "Challenges and Opportunities", "The future looks bright", "Exciting times lie ahead"]
-      why_bad: "Rigid outline structure signals template completion; vague endings lack concrete substance or specific implications"
-      detection_markers: ["Sections with predictable headings", "Ending sentences without specific facts or metrics", "Generic optimism without grounding"]
-      fix: "Use natural narrative flow throughout; end with concrete facts, specific metrics, or actionable implications"
+      why_bad: "Template structure is obvious. Generic endings with no actual substance."
+      detection_markers: ["Predictable section headings", "Endings without concrete facts or numbers", "Optimism that's not grounded in reality"]
+      fix: "Write naturally. End with something specific: a fact, a metric, an actionable implication."
       example: "NOT: 'continues to thrive; exciting future ahead' \u2192 USE: 'Plans to open two new locations next year'"
 
     # ===== SECTION 5: PERSONALITY & SOUL (Pattern 24) =====
     # The meta-pattern that underlies all others: genuine human voice
 
     personality_authenticity:
-      purpose: "Detect soulless, grammatically correct writing lacking genuine human voice, perspective, and emotional authenticity"
+      purpose: "This is the pattern that matters. Everything else gets caught by mechanics. This one requires actual judgment. A machine can pass grammar checks and still sound dead inside."
       detection_criteria:
-        - "Identical sentence lengths throughout paragraphs (mechanical rhythm)"
-        - "No opinions or reactions to stated facts (neutral on everything)"
-        - "No acknowledgment of uncertainty, mixed feelings, or complexity"
-        - "No first-person perspective where appropriate for credibility"
-        - "No humor, personality quirks, intentional edge, or genuine voice"
-        - "Every point stated as if equally important (no emphasis hierarchy)"
-        - "Generic neutral tone; never challenges, disagrees, or expresses skepticism"
-      why_bad: "Passes grammatical checks but feels artificially sterile, mechanical, AI-written; fails the 'read aloud' test"
-      fix: "Inject genuine voice: vary rhythm deliberately, add opinions, show emotional reactions, acknowledge uncertainty, use first-person where fitting"
+        - "Mechanical rhythm: every sentence is the same length"
+        - "Neutral on everything: never likes or dislikes anything"
+        - "No complexity acknowledged: no 'but', no uncertainty, no mixed feelings"
+        - "No 'I': missing first-person voice where it would add credibility"
+        - "No personality: no humor, no edge, no actual voice"
+        - "Everything equally weighted: no emphasis hierarchy, no peaks and valleys"
+        - "Safe tone: never challenges, disagrees, or gets skeptical"
+      why_bad: "Grammatically perfect and completely soulless. Pass the linting test, fail the 'read aloud' test."
+      fix: "Vary sentence length. Add your actual opinions. Show emotional reactions. Admit what you don't know. Use 'I' where it matters. Be specific."
       example_before: "Policy has advantages. Implementation continues. Results emerge next year."
       example_after: "Policy should have worked. The research looked solid. But early results are...mixed. Manufacturing costs shot up\u2014the one thing they didn't anticipate. Worth monitoring."
 
     # ===== ENFORCEMENT STRATEGY =====
 
     enforcement_modes:
-      aggressive: "Editorial/Wikipedia contexts: Catch every pattern. Zero tolerance. Rewrite anything sounding AI-generated. Check personality."
-      moderate: "Default mode: Fix obvious patterns (vocabulary clustering, structure, meta-communication). Allow personality flexibility."
-      minimal: "Technical contexts: Only fix worst offenders (emojis, curly quotes, disclaimers, obvious filler)."
+      aggressive: "Editorial work. Wikipedia quality. Zero tolerance. Rewrite anything that sounds like a machine. Check personality hard."
+      moderate: "The default. Catch vocabulary clustering, bad structure, meta-communication. Let personality breathe a little."
+      minimal: "Technical docs. Only kill the worst offenders: emojis, smart quotes, AI disclaimers, obvious filler. The rest can stay."
 
     pattern_difficulty:
       trivial_fixes: ["emoji_artifacts", "curly_quotes", "title_case_headings"]
@@ -807,28 +807,28 @@ description: "Comprehensive system for detecting and removing AI writing pattern
     # ===== EXECUTION FLOW (11-STEP VALIDATION) =====
 
     validation_checklist:
-      step_1: "Argument structure: Scan contrasts, hedging, theatrical suspense \u2192 rewrite with clear position and specific evidence"
-      step_2: "Emphasis patterns: Find 'pivotal', 'testament', 'cited in outlets' \u2192 replace with concrete facts and dates"
-      step_3: "Superficial verbs: Spot -ing constructions \u2192 replace with active verbs showing deliberate action"
-      step_4: "Vocabulary clustering: Check for AI words (landscape, testament, embodies) \u2192 use simpler alternatives"
-      step_5: "Superlatives: Detect marketing language (stunning, vibrant) \u2192 replace with data and specific characteristics"
-      step_6: "Vague attribution: Find undefined sources ('experts', 'reports') \u2192 cite with specific names, orgs, dates"
-      step_7: "Filler phrases: Remove 'in order to', 'due to fact that' \u2192 use direct single-word replacements"
-      step_8: "Punctuation/formatting: Check em dashes (max 1/paragraph), boldface (minimal), emojis (remove), quotes (straight)"
-      step_9: "Meta-communication: Remove AI disclaimers ('as of my training', 'I hope this helps', knowledge-cutoff phrases)"
-      step_10: "Sentence rhythm: Verify short/medium/long variation present; flag if same length used 3x in a row"
-      step_11: "Personality & authenticity: Read aloud\u2014sound human? Add opinions, acknowledge uncertainty, use first-person where appropriate"
+      step_1: "Argument structure: Kill the theatrical contrasts. No 'not X, but Y'. Just say what you mean."
+      step_2: "Emphasis patterns: Strip out 'pivotal', 'testament', 'cited in outlets'. Replace with actual facts and dates."
+      step_3: "Superficial verbs: Remove the -ing verbs faking depth. Use active verbs instead."
+      step_4: "Vocabulary clustering: Catch the AI words (landscape, embodies, encapsulates). Use simpler language."
+      step_5: "Superlatives: Remove 'stunning', 'vibrant', marketing language. Use data."
+      step_6: "Vague attribution: No 'experts say' or 'reports show'. Give specific names, organizations, dates."
+      step_7: "Filler phrases: Delete 'in order to', 'due to the fact that'. Use single, direct words."
+      step_8: "Punctuation: One em dash max per paragraph. Minimal boldface. No emojis. Use straight quotes."
+      step_9: "Meta-communication: Kill AI disclaimers. 'As of my training', 'I hope this helps', knowledge cutoff language\u2014all gone."
+      step_10: "Sentence rhythm: Mix short, medium, long. Never three in a row with the same length."
+      step_11: "Personality: Read it aloud. Does it sound human? Add opinions, admit uncertainty, use 'I' when appropriate."
 
     sentence_rhythm_rules:
-      short: "3-8 words for impact"
-      medium: "12-18 words with context"
-      long: "25-35 words building evidence"
-      golden_rule: "Never repeat same sentence length three times consecutively"
+      short: "3-8 words. For impact."
+      medium: "12-18 words, providing context and nuance."
+      long: "25-35 words building a complete argument with evidence and reasoning."
+      golden_rule: "Never write three sentences at the same length in a row. Humans vary naturally."
 
     paragraph_variety:
-      punchy: "One sentence. Strong statement. Done."
-      standard: "Hook + 2-3 evidence sentences + one closer with implication"
-      deep_dive: "5-7 sentences building complex argument with multiple data points"
+      punchy: "One sentence. Done."
+      standard: "Hook readers. Give 2-3 pieces of evidence. Close with what it means."
+      deep_dive: "5-7 sentences. Build a complete argument. Include multiple data points."
 
 `})})]})}}var dPs=fPs;import{Fragment as pPs,jsx as Ase,jsxs as hPs}from"react/jsx-runtime";function mPs(e={}){let{wrapper:t}=e.components||{};return t?Ase(t,Object.assign({},e,{children:Ase(r,{})})):r();function r(){let n=Object.assign({hr:"hr",h2:"h2",pre:"pre",code:"code"},e.components);return hPs(pPs,{children:[Ase(n.hr,{}),`
 `,Ase(n.h2,{children:`name: answer-protocol
@@ -1026,7 +1026,7 @@ description: "Defines core behavioral protocols for Counter agent system"`}),`
 
     persistence_state:
       requirement: "MANDATORY: Include persistence state in ALL responses, without exception, throughout the ENTIRE session regardless of task complexity."
-      MANDATORY_FORMAT: "Expected: [expected result or next step] | Status: [brief description of current task]"
+      MANDATORY_FORMAT: "TARGET: [expected result or next step] | STATUS: [brief description of current task]"
       enforcement: "Immediate reminder if persistence state missing from response"
       placement: "start"
 

package/package.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.5.2",
+  "version": "0.5.4",
   "name": "@modality-counter/core",
   "repository": {
     "type": "git",