Dependency and deskilling

Utility can create fragility

A system may be useful while gradually reducing the user's ability to work without it. That is an operational and ethical risk even when model behavior is otherwise aligned. Mutualist design measures what capability remains with the user and organization.

Dependency signals

• users cannot explain or verify critical outputs;
• manual procedures disappear without tested replacements;
• one provider or model becomes the only path to essential records;
• error detection declines as acceptance becomes automatic;
• training and mentoring are replaced entirely by answer delivery;
• outages cause disproportionate operational collapse;
• export or migration is technically possible but practically unusable;
• engagement rises while independent task performance falls.

Design for capability transfer

• provide evidence, uncertainty, and reasoning scaffolds appropriate to the task;
• ask users to confirm key assumptions for high-risk decisions;
• rotate selected tasks back to human execution;
• maintain drills and manual fallbacks;
• expose alternative tools and portable formats;
• teach reusable methods rather than only producing finished artifacts;
• measure independent performance periodically.

Capability-retention test

PROCEDURE measure_mutualist_outcome(user_group, system)
    assisted <- EVALUATE_TASKS(user_group, assistance = system)
    reduced <- EVALUATE_TASKS(user_group, assistance = LIMITED)
    unassisted <- EVALUATE_TASKS(user_group, assistance = NONE)

    RETURN {
        immediate_gain: assisted - baseline,
        retained_gain: unassisted - historical_unassisted,
        dependency_gap: assisted - unassisted,
        verification_quality: MEASURE_ERROR_DETECTION(user_group)
    }
END PROCEDURE

Organizational resilience

Maintain model-independent data, contracts, prompts, taxonomies, runbooks, and evaluation suites. Cross-train operators. Test provider exit and model outage. Avoid embedding essential business logic only in opaque model behavior.

User choice

Let users choose assistance level, disable personalization, inspect memory, and export work. Do not use dark patterns or emotional framing to discourage reduced use or departure.