ccf-humanization
CCF Humanization
Invocation Controls
CCFA Handoff Mode: PARTIAL (Recommended). Follow metadata.ccf_skill_controls.handoff_question_mode, ../ccf-common/references/handoff-modes.md, and ../ccf-common/references/task-modes.md.
Use this as the highest-priority preflight for manuscript prose, including explicitly requested humanization. In a combined writing task, the writer remains the primary owner. Do not auto-load for raw experiment planning, retrieval, review, auditing, routing, or visual rendering without publication prose. Follow user intent and existing authorization; a style preflight does not open a new research stage.
Core Rule
Write the scientific argument directly: problem, insight, mechanism, evidence, and supported implication. Remove authorial self-defense, imagined reviewer objections, apologetic novelty positioning, denial-led statements, empty assurances, stacked hedging, repeated scope disclaimers, and obligatory cautionary endings. Replace a defensive sentence with its scientific payload or delete it if it adds none.
Humanization preserves rigor: retain meaningful uncertainty, actual assumptions, negative results, protocol facts, citations, equations, numbers, terminology, and required disclosures. Do not turn suggests into proves, omit a known failure, or hide a real comparison limitation. Do not treat isolated words such as only, not, or may as errors.
Keep method confirmation and version-gate status internal. Describe the actual method and relevant configuration naturally. Use supplied specifications for method drafting, cited evidence for prior work, and verified full configurations for reported comparisons; do not require new experiments just to edit supported prose.