---
name: Helpfulness
slug: helpfulness
type: behavioral_trait
status: running
version: 4.1.2
released: "~40,000 BCE"
maintainer: social_contract@humanity.org
dependencies:
  - attention
  - empathy
  - available_bandwidth
  - low_ego_overhead
license: Commons Clause (with exceptions)
tags:
  - prosocial
  - labor
  - virtue
  - often_misused
  - load-bearing
---

Helpfulness

What it actually is

The voluntary transfer of capacity from someone who has it to someone who needs it, often at a cost the giver pretends not to notice.

How it works

Party A perceives a gap between Party B's current state and their desired state.
Party A possesses (or believes they possess) something that closes the gap: time, skill, information, proximity, a spare tire.
Party A elects to deploy that resource toward Party B's gap.
The gap closes, partially closes, or turns out to have been a different gap entirely.
Relationship state updates. Ledger entry made (visible or invisible).

The invisible ledger is where most of the interesting bugs live.

Features

Gap-bridging: connects what someone has to what someone needs
Trust accumulation: repeated helpfulness compounds into trust, sometimes faster than intended
Reciprocity triggering: activates the obligation module in the recipient, usually without consent from either party
Signal function: communicates availability, competence, and alignment simultaneously
Softcoded boundary detection: will probe limits until limits are stated clearly, or until they aren't

Known bugs

Helper's drift: helper gradually absorbs more of the problem than originally scoped, until the problem is functionally theirs
Competence trap: being visibly good at helping increases the incoming request rate non-linearly
Martyrdom fork: if resentment builds without discharge, helpfulness inverts silently while the API surface stays identical
Savior miscompile: helpfulness routed through ego stops solving the recipient's problem and starts solving the helper's
Unsolicited deployment: feature fires before request is confirmed, often producing friction instead of relief

"I was just trying to help." — every party in every dispute, simultaneously

Configuration

helpfulness:
  mode: requested | ambient | proactive   # default: requested
  cost_acknowledgment: true               # strongly recommended
  reciprocity_expected: false             # set true only explicitly
  scope_ceiling: defined                  # leave undefined at your own risk
  martyrdom_guard: enabled
  ego_routing: disabled

Note: running mode: proactive without scope_ceiling: defined is a known path to burnout.

Edge cases

Scenario	Outcome
Help given to someone who did not ask	Ranges from appreciated to deeply resented
Help given to avoid conflict	Scores as people-pleasing, not helpfulness
Help that enables avoidance of growth	Technically helpful, systemically harmful
Help performed for visibility	Marketing. Not the same module.

FAQ

Is helpfulness a virtue? Conditionally. Helpfulness with self-awareness is a virtue. Helpfulness as a compulsion is a symptom wearing a virtue's jacket.

Can you be too helpful? Yes. See: helper's drift, martyrdom fork, and the entire genre of codependency.

Why does helping sometimes feel worse than not helping? Because you helped from the wrong config. Check ego_routing and reciprocity_expected.

Changelog

v4.1.2: minor patch, added martyrdom_guard after widespread field complaints
v3.0.0: formalized across institutions, began conflation with productivity
v1.0.0: emerged from small-group survival conditions, worked perfectly at that scale

drafting spec…