anchor.diff:  * Cause - once a problem is understood, try to state the cause of the problem as clearly as possible
   * Alternatives - you should try to come up with multiple alternative solutions for any problem (definitely for new features). Don't forget one alternative that always exists: do nothing. Use the problem to discover dimensions on which to compare the alternatives. Consider things like: performance, backwards compatibility, where the change occurs, etc.
   * Proposed solution - Restate the chosen alternative in detail and why it is the best across the considered dimensions. The Proposed solution section should cover aspect of the patch such that a reviewer is not surprised by the time they look at the code.
  -* Patch - see "Patch evaluation" below
  +* Patch - see <<screening_tickets#patches,Patch evaluation>> below
   * Performance - does the ticket include sufficient performance consideration? If a benchmark is needed, include benchmark and before/after timings. If that data is included, verify it on your own machine.
   * Does the Proposed section fully explain everything a subsequent reviewer would see in the patch?
   * Patch - is the name of the proposed patch listed? (this seems obvious ... until it isn't, so always explicitly list it, even if it's the only patch)
  
positive.code: * Read the diff, either isolated or as applied. Verify that it matches the proposed solution. If there is anything surprising and new, either the ticket or the patch should be updated.
  * Does the patch match the style of the surrounding code and the <<xref/../../dev/contrib_howto#_coding_guidelines,Coding Guidelines>>? (These are guidelines, not fixed laws of the universe.)
  * Is the documentation still correct?
  * Inlined functions that have type hints in the body will also require something in the inline function
negative.code: 
  Tickets ready for triage: https://clojure.atlassian.net/issues/?filter=10001[CLJ Open]
  
  [[vetting]]
  == Vetting process
  
  **The big picture question here is: "Is this a well stated problem?"**
  