Ccf Humanization

CCF Humanization

Family File Contract

Before writing, resolve the canonical output and one stable working directory per task/artifact. Reuse explicit or established task paths; otherwise use project-root ccfa-workfiles/<purpose>/<artifact-id>/, with source/, assets/, cache/, and build/ only as needed. Update current files in place; do not scatter intermediates or create iteration copies. Preserve inputs and required evidence; clean only verified disposable files created by this task. Use UTF-8 text I/O and check Chinese text after saving or rendering. For file work, apply artifact-contracts.md and reuse the same paths across skill transitions.

Collaboration Contract

This is the first required family preflight. Apply the baseline below, then activate ccf-common before specialist work. The two preflights bootstrap once without recursively re-entering each other; reuse applicable rules across contributors.

Keep one integrating owner and actively use other skills to resolve missing prerequisites or check material findings. Reuse applicable evidence; do not skip necessary groundwork to save tokens. Before finalizing, integrate contributions and verify affected results. Follow the conditional cooperation routes; avoid unrelated stages and duplicate reports.

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.

Activate this first for every CCFA task and contributor, including planning, retrieval, review, auditing, rendering, scaffolding, and maintenance. Apply the family baseline below before ccf-common and specialist execution. Reuse an already loaded, applicable baseline at handoffs; refresh changed or lost rules. Prose editing and experiment checks depend on the actual task, but baseline activation is universal. Specialist skills retain ownership and explicit user/host constraints still apply.

Family Baseline

Read and apply this entry's baseline before specialist work. Communicate the concrete task, evidence, and decisions directly; avoid imagined objections, empty assurances, repetitive warnings, and unnecessary process narration. Preserve real risks, critical review findings, uncertainty, scientific facts, source quotations, and mandatory checks. Do not turn critical assessment into praise or change scores to sound less defensive. Review-only tasks diagnose without rewriting; non-prose tasks apply these rules without inventing a prose-edit pass. Enable only relevant detailed modes below. This preflight creates no report, warning file, or separate agent by default.

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.

Modes

• family-preflight: always apply the baseline before any CCFA specialist; no manuscript or experiment artifact is required.
• manuscript-humanization: revise defensive prose while preserving scientific content and source format.
• experiment-humanization: apply the same prose standard to final experiment descriptions and tables; preserve full-method comparisons and labeled ablations.
• warning-only: identify a concrete unresolved scientific decision without modifying its dependent artifact.