Patterns

Recurring craft moves that resolve specific tensions.

• [[Acknowledge Before Revise]] -- The curator's first operational move in any curation pass is to name what each contribution added
• [[Convergent Motivation as Load-Bearing Signal]] -- Four or more independent motivations converging on one architectural solution is the signal that the solution is structural rather than contingent
• [[Coordinate at Content, Not at Git]] -- When two graphs share a meta-layer, coordinate via per-node grafts and external wikilinks rather than git-level forks or merges; let neither graph claim canonical ownership of t...
• [[Gloss the Translation Surface]] -- When two contributors' vocabularies meet, write the glossary entry that names what each term preserves
• [[Let the Exercise Audit the Contract]] -- When a new Contract holds through speculative drafting but has not been run against real cases, exercise the first conforming skill or node against real data and let the exercis...
• [[Progressive Summary Before Substance]] -- When authoring or reviewing a node, arrange content so consumers encounter progressively denser material as they commit context, with each tier complete at its own scale
• [[Reconcile the Standing Account]] -- When a document's accuracy depends on something external that has moved, audit the document and reconcile
• [[Refactor the Predicate's Axes]] -- When a predicate carries two or more independently-moving axes, recognize the axes and split the predicate into single-axis named predicates before corpus use ossifies the overl...
• [[The Curation Pass]] -- The composed unit of curation work
• [[Treat Objection as Structural Contribution]] -- When a participant objects to a term, predicate, or framing, the objection names a distinction the proposer did not see or a frame the proposal imposes

10 nodes in this section.