Pride and Humility Are Both Cultivable

The practice works toward conditions that help contributors simultaneously feel their contribution is worthwhile (pride) and accept that others can improve it (humility). Both traits are treated as cultivable through practice design rather than as contributor preconditions the practice selects for. The directional target is that contributors who did not arrive with both traits develop them through participation, and contributors who arrived with both find the traits sustained rather than eroded by the practice's norms.

Why It Is Worth Pursuing

The pride-humility dichotomy ([[Meaningful Wiki Contribution Requires Both Pride and Humility]]) identifies the trait-pair as a filter that selects contributors rather than a condition the practice develops. A community that treats the traits as preconditions loses contributors who would develop them with the right conditions; a community that treats them as cultivable expands the population who can sustain participation. The Aspiration commits the practice to the second position: trait development is part of what the practice is for.

The cultivation frame is distinct from selection. Selection rewards contributors who already hold the traits; cultivation shapes the practice so that contributors who hold one or neither can develop both. Selection narrows the contributor population; cultivation widens it. A community that targets the second cycle ([[The Second Cycle of Contribution Happens]]) and the newcomer transition ([[Newcomers Cross the Second-Cycle Threshold]]) needs cultivation rather than selection — selection filters at entry, and the losses compound across cycles.

The Aspiration is adjacent to [[Contributors Across Vocabularies Can Collaborate]] and [[Participation Diversity Is Legible and Valued]] at a different design layer. Those Aspirations target plural participation as a property of the practice's inclusivity surface; this Aspiration targets trait development as a property of the contributor's experience within the practice. The three compose into a plural-participation stance with a contributor-development dimension — the community is plural in vocabulary and form, and the contributor's traits develop through participation rather than filtering the participation.

The sovereignty stance in [[Vocabulary Diversity Is a Feature]] argues that contributor vocabulary is the contributor's own and that curation translates rather than normalizes. The same stance at the contribution layer says contributions are the contributor's own and revision is collaboration rather than correction. The Aspiration extends the sovereignty reading from vocabulary to the trait-development surface — curation's revisions respect the contributor's pride because the revision is a response to the contribution's value, not a rejection of the contributor's worth.

Current Gap

Current conventions specify what to author (forms, predicates, annotations) but not how to develop the psychological and social conditions for authoring to feel worthwhile and revisable. The convention layer addresses mechanics; trait development is a separate design surface that is currently implicit. A contributor whose first contribution is revised without acknowledgment may experience the revision as overwriting rather than collaborating; the convention layer does not name this concern.

Revision rituals are not established. Revision happens in the graph — curation passes modify nodes, reconciliation collapses duplicated claims to pointers — but the ritual around revision is absent. A contributor does not know when their contribution might be revised, who is doing the revising, or how the revision is communicated. Without the ritual, revision is experienced as something that happens to contributions rather than as something contributors participate in.

Curation output is not visible to contributors between cycles. The [[Newcomers Cross the Second-Cycle Threshold]] Aspiration names this gap from the contributor-transition angle; the trait-cultivation reading of the same gap is that contributors cannot develop humility toward revision if they do not see revision as an ongoing practice they participate in. Invisibility turns revision into an external operation rather than a shared one.

Contribution recognition surfaces are implicit. Pride sustains when contribution is recognized; the graph encodes recognition in edges (who authored, what is cited) but does not surface recognition to the contributor. A contributor whose node was cited by fifteen subsequent nodes has no view of that; the pride that recognition would sustain goes uncultivated because the graph's structure does not reach the contributor through an acknowledgment channel.

Work It Asks

Design affirmation practices that validate contribution before critique in the curation cadence. The curator's first operational move in any curation pass is to name what each contribution added — what node it introduced, what gap it closed, what edge it made tractable — before proposing revisions. Affirmation is not a rhetorical courtesy; it is a specific early step that makes subsequent revision legible as collaboration rather than as override.

Design revision rituals that normalize "others improve mine" as expected participation rather than as threat. The rituals name revision as a planned and visible part of the practice — scheduled curation passes, public reconciliation moves, acknowledged back-edges — rather than as surprise editing. A contributor who knows their contribution will be revised, sees the revision happening, and participates in the reconciliation develops humility toward revision differently than one who discovers revisions after the fact.

Establish curation practices visible to contributors so being revised is felt as participation in a practice rather than as rejection. The curation-output-as-contributor-surface work described in [[Newcomers Cross the Second-Cycle Threshold]] is the mechanism; the trait-cultivation Aspiration names the purpose — visibility is what lets contributors develop humility toward revision as an ordinary practice.

Consider whether contribution recognition can be built into the graph's own structure. first_authored_by:: predicates preserved through revision, so the original author is still visible even when the node has evolved; cited_by:: aggregation so contributors see what their contributions have come to ground; per-contributor summary surfaces that aggregate a contributor's graph footprint. The specifics are open and belong in the Predicate candidates subsection of CONVENTIONS.md; the commitment is that recognition becomes part of the graph rather than a separate acknowledgment system.

Name the conditions under which the cultivation can fail. Some contributors may arrive with traits that resist cultivation — a contributor whose pride rests on non-revisable authorship will not find the practice's revision rituals cultivating; a contributor whose humility is absolute will struggle to develop the pride that sustains contribution. The practice names these edge cases rather than assuming universal cultivability; the Aspiration's honest target is "cultivable for most contributors who engage with the practice's rituals" rather than "cultivable for all."

Progress Recognition

First-time contributors return for a second contribution after their first has been revised. The return demonstrates that the revision was experienced as participation rather than rejection. The specific return is less important than the pattern — multiple first-time contributors returning after revision signals that the rituals are working.

Curators report contributors volunteering their work for revision rather than resisting it. A contributor who asks a curator to look at their node, or who flags their own work for attention, is demonstrating humility as a cultivated trait rather than as a precondition. The volunteering is the specific behavior the rituals target.

Contributors explicitly cite both felt worth and accepted revisability in qualitative reports. The citation does not need to be formal — a contributor saying "I felt like my contribution mattered, and I'm glad X revised it" — but it must be recurrent across multiple contributors for the Aspiration to be making progress.

Affirmation practice is sustainable in the curation cadence rather than falling away under pressure. Curators carry the affirmation-before-critique discipline forward through several curation passes; the discipline does not become an optional gesture that disappears when the curation queue gets long. Sustainability is the measure — one-time affirmation is not cultivation.

The graph's recognition surface is visible in at least one contributor's experience. A contributor can point at a surface — a per-contributor summary, a node preservation through revision, an acknowledgment in a curation-pass output — and say "this surface shows me what my contribution has done." Without such a surface, the recognition remains graph-internal and does not reach the contributor where cultivation happens.

Sources

Relations