Route Notes to SOP Update Protocol or Directly to Articles

Task Library

Move every Knowledge Capture Note to its correct destination – into the SOP Update Protocol when it changes how work is done, or directly into a definitive article when it adds facts.

Category: Knowledge System Maintenance

Use this when Knowledge Capture Notes are sitting in the shared capture location – routing runs on a fixed cadence so notes become changes instead of a graveyard of good intentions.

Inputs

  • The shared capture location with unrouted Knowledge Capture Notes
  • The SOP Amendment Proposal queue (Process 2) and edit access to definitive articles
  • The entity map of which definitive article owns which concept

Steps

  1. Review all new notes at a fixed cadence (daily or each working session); high-priority notes jump the queue immediately.
  2. Apply the routing test per note: does this insight change how we do work? Yes → it is an SOP/process change → route into the SOP Update Protocol. No, it adds a fact, example, number, or proof → route directly into the destination definitive article.
  3. SOP path: draft (or request from the note's author) the ≤500-word SOP Amendment Proposal, citing the note's source as one real example – remember the protocol requires at least two, so pair it with a second occurrence or hold it tagged until one appears.
  4. Article path: update the destination article directly – place the addition where it supports the declared topic (SEO Tree test), keep Blog Posting Guidelines compliance, and respect methodology/implementation separation (Process 4).
  5. Verify the note's stated destination is actually correct before acting; the capturer guessed under a 24-hour clock. Re-route to the true owning hub if needed.
  6. Mark each note routed: destination, action taken, date. No note remains unrouted past the next cycle – "parked" is a status with a reason, not a default.
  7. If many notes pile up against one SOP or article, that is a pattern – feed it to the 6-month pattern review rather than processing them one by one forever.

Definition of done (QA checklist)

  • Every note in the location is routed, actioned, or parked-with-reason – none silently pending past one cycle
  • SOP-path notes became (or joined) a four-part amendment proposal in the queue
  • Article-path notes landed in the correct hub, passing the SEO Tree test and Blog Posting Guidelines
  • Each note marked with destination, action, and date – auditable later
  • Pile-up patterns flagged for the 6-month recursive review
  • Linked back to the definitive article and relevant siblings
  • Complies with Blog Posting Guidelines (if it publishes content)

Example(s)

  • /knowledge-system-maintenance – Process 3 defines the two routes (SOP Update Protocol vs direct article update) as the only exits from the capture pipeline.
  • Example needed – run the Meta-Article Prompt (/meta-article-prompt-template) after the first routing cycle and link the meta-article here.

File in the zip: skills/knowledge-system-maintenance/route-notes-to-sop-update-protocol-or-directly-to-articles.md. Download the Task Library zip.

Index: Task Library. Article guidelines.

Scroll to Top