• conforms_to::[[Pattern Form Contract]]
• authored_by::[[Deep Context Community]]
• has_lifecycle::[[Seed Stage]]
• has_curation::[[Working Draft]]
• in_domain::[[Deep Context Architecture]]

Acknowledge Before Revise

Heart

Before proposing any revision to a contribution, name what the contribution added. The curator's first move in any curation pass is acknowledgment — what node the contribution introduced, what gap it closed, what edge it made tractable, what distinction it surfaced. Only then does revision enter the conversation. The sequence is the move; reversing it (revise first, acknowledge later) does not produce the same outcome.

Problem

Revision that arrives without acknowledgment is experienced by the contributor as overwriting, even when the revision is good. The contributor's work disappears into the revised form without a trace that the work was received, considered, and built upon — only the resulting revision is visible, and the resulting revision reads as the curator's authorship. The contributor's relationship to the graph moves from "I contributed something that became part of this" to "something I wrote was changed," which are structurally different experiences.

The default curator posture is revision-first. The curator opens a node, sees what needs to change, and changes it. Acknowledgment feels like friction — an extra step before the work can be done. In a single-author garden, the friction produces no cost (the author is both the contributor and the curator). In a multi-contributor graph, the absence produces the contributor-erasure dynamic that [[Pride and Humility Are Both Cultivable]] names.

The difficulty is habit, not mechanics. Once the curator has internalized acknowledge-first, the acknowledgment is a sentence or two in a curation-pass note. The craft this Pattern teaches is fighting the revision-first habit at the moment the curator opens a node to revise.

Forces

• Revision-first is the natural curator flow. The curator opens the node because they see something to revise. Pausing to name what the contribution already added feels like delay from the work's perspective. The force that pulls toward revision-first is ordinary workflow momentum, not disregard for the contributor.
• Acknowledgment is invisible without discipline. The contribution's additions are visible to the curator — that is why the curator opened the node — but are invisible to a reader who sees only the revised output. Without explicit acknowledgment in the curation pass's record, the contribution's role dissolves into the revised form and the contributor's work becomes unattributable.
• Contributor experience compounds. A single revision without acknowledgment is a small signal; repeated unacknowledged revisions across a contributor's work is a pattern. The compound effect reaches the contributor even when no single revision was problematic — the contributor experiences the curation surface as one where their work is silently absorbed.
• Acknowledgment is not affirmation of every choice. The curator does not have to agree with the contribution's every choice to acknowledge what the contribution added. Acknowledgment names what the contribution did; revision may then address choices the curator reads differently. Collapsing the two — "if I acknowledge it, I endorse it" — distorts the Pattern.

Solution

In every curation pass, before proposing or making any revision to a contribution:

1. Name what the contribution introduced. One or two sentences identifying the specific addition — the new node, the new predicate, the new annotation, the new edge, the surfaced distinction. Be specific enough that a reader who does not know the contribution's history can tell what arrived.
2. Name what the contribution addressed. If the contribution closed a gap, resolved an Open Question, corrected a drifted account, or added a missing edge, name that. The acknowledgment is thicker than "X added a node"; it is "X added a node that grounds the previously-ghost Aspiration at the contributor-transition layer."
3. Then revise. Propose the revision, make the edit, or note the drift correction. The revision sits inside a recognized contribution; the contributor sees both their work and the revision's relation to it.
4. Capture the acknowledgment in the curation-pass record. The acknowledgment is not only a moment in a conversation; it is a durable part of the curation-pass output. Contributors reading the output see what the curator recognized in each contribution, not only what the curator changed.

The sequence's order matters. Acknowledging after revising — a curation-pass note that describes the revision then adds "and X's original contribution was valuable" — does not produce the same contributor experience. The post-hoc acknowledgment reads as mitigation of the revision rather than as recognition of the contribution.

Consequences

• Revision becomes legible as collaboration. A contributor reading a curation pass that acknowledges their contribution and then proposes revisions engages with the revisions as participation in a shared practice. Without the acknowledgment, the same revision reads as erasure.
• Curation-pass records are thicker. The acknowledgment becomes part of the record; readers who were not present at the curation pass can see what was recognized in each contribution, not only what was changed. The thicker record serves contributor sustainability and graph legibility.
• Revision quality improves. A curator who has named what the contribution added has already read the contribution closely enough to revise it accurately. Revision without prior acknowledgment is often revision without full understanding; the Pattern produces closer reading as a byproduct.
• Acknowledgment becomes sustainable with practice. The initial cost of the Pattern is real — adding a sentence or two per contribution feels like friction until it becomes habit. Once practiced, acknowledgment is a natural part of opening a node to work on it.
• Acknowledgment-without-cultivation signals drift. A curator who acknowledges contributions mechanically ("X added a node") without naming what the contribution added substantively has drifted back to revision-first disguised as acknowledge-first. The Pattern fails gracefully only when the curator understands why the sequence matters.

Instances

• Curation-pass notes in a multi-contributor pass. When the first non-founder contributor authors in the graph, the curation pass that addresses their work is the canonical instance of this Pattern. The pass's note names what the contribution added (specific nodes, predicates, annotations) before any revision. The contributor reading the pass sees both recognition and revision; the pattern the Pattern creates is what the contributor's experience of revision becomes.
• Mid-authoring self-acknowledgment. Applied recursively by a single author during authoring: before revising a draft, name what the draft already carries. The self-application is a craft discipline that produces closer reading of one's own work; it also keeps the Pattern fresh for curators who will apply it to others' work.
• Acknowledgment at the edge of reconciliation passes. When [[Reconcile the Standing Account]] runs and a passage is collapsed to a pointer, the reconciliation note names what the collapsed passage contributed before the collapse (recorded the exploration, framed the narrative, sat as a holding zone for unextracted claims). The collapsed passage's role is not erased by the collapse; it is acknowledged in the reconciliation record.

Also Known As

• Affirm first — the terse version; useful as a curation-session reminder.
• Validate before critique — adjacent framing from design-thinking practice. The underlying move is the same; this Pattern's framing emphasizes the sequencing as the operative move rather than the validation-versus-critique distinction alone.

Relations

• grounded_in::[[Pride and Humility Are Both Cultivable]]

  • The Aspiration names affirmation-before-critique as a design target: "Affirmation is not a rhetorical courtesy; it is a specific early step that makes subsequent revision legible as collaboration rather than as override." This Pattern lifts the target to craft. The Aspiration is the directional commitment; the Pattern is the concrete move a curator runs.

• grounded_in::[[Meaningful Wiki Contribution Requires Both Pride and Humility]]

  • The Observation names the trait-pair whose cultivation this Pattern participates in. Pride sustains when contribution is recognized; the Pattern is one mechanism for making recognition operational at the curation layer. Without the Pattern, cultivation has a gap at the point where contributor and curator work meets.

• composes_with::[[Reconcile the Standing Account]]

  • Both are curator-side Patterns. Reconcile the Standing Account addresses the document layer (account becomes inaccurate; reconcile collapses duplication to pointers and realigns stale descriptions). This Pattern addresses the contributor layer (work arrives; acknowledge before revising). Applied together, a reconciliation pass both keeps documents trustworthy and keeps contributors' work legible as contribution.

• composes_with::[[Treat Objection as Structural Contribution]]

  • Both Patterns structure curator posture against default review flow. Treat Objection reframes objection as contribution; this Pattern reframes contribution itself as requiring acknowledgment before revision. Both resist the default posture that treats contributor work (positive contribution or objection) as friction to resolve rather than input to engage.

• composes_with::[[The Curation Pass]]

  • The compound curation Pattern this Pattern is a component of. The Curation Pass is the session-level unit of curation work; this Pattern is the curator-side acknowledgment move the pass applies to each contribution it addresses. The compound names the session; this Pattern names one of its component moves.

• informs_downstream::[[The Second Cycle of Contribution Happens]]

  • The Aspiration's contributor-level transition names "acknowledgment within a week" as a candidate cadence; this Pattern is what acknowledgment operationally looks like inside that cadence. The Pattern supplies the content; the Aspiration's cadence supplies the timing.