Use-Time Knowledge Article Update¶
Workflow — instantiates Retrieval-Cued Revision
Prompts a worker to update a knowledge-base article at the moment it is retrieved and found wrong, so future lookup retrieves the revised version.
Use-Time Knowledge Article Update revises a shared record at the instant it is retrieved and discovered to be wrong, so that the next person who looks it up retrieves the corrected version. Its subject is the document, not a person's memory or a performer's hands, and its defining move is capturing the fix at the moment of use — when the article is open, the reality it describes is in front of the worker, and the discrepancy is concrete — rather than deferring it to a review cycle that never comes. The correction is written into a versioned record so the revised content is what future lookups return, while the prior version stays auditable. Nothing here trains a habit; it changes what the source of truth says the next time it is read.
Example¶
A customer-support agent at a SaaS company is on a call, walks a customer through the knowledge-base article for resetting two-factor authentication, and hits a step that no longer exists — the vendor moved the setting to a new menu in last week's release. The old workflow would be to work around it on the call and move on, leaving the wrong article to trip the next agent and the next customer. Under use-time updating, the agent instead fixes it right there: the article is open, the correct path is on screen, so they scope the edit to the one stale step (not a rewrite of the whole article), correct the step, and save it as a new version with a note on what changed and why. The prior version is retained in history, so anyone auditing the change can see the pre-release instructions and who revised them. Minutes later, the next agent who retrieves that article gets the corrected path. The record was edited at the exact moment its wrongness was visible, and future retrieval now returns the fix.
How it works¶
- Trigger on retrieved-and-wrong. The workflow fires when a worker looks up an article in the course of real work and finds it contradicts reality — the discrepancy is the cue.
- Scope the edit narrowly. Correct the specific stale claim, step, or branch that is wrong, not the whole document, so the fix is precise and low-risk.
- Write the corrective content in place. Capture the correction while the reality is in front of the worker and the details are concrete.
- Version, don't overwrite. Save the change as a new version with a change note, so future lookups return the revised article while the prior version remains recoverable.
- Preserve provenance. Record who changed what and why, keeping the edit auditable and reversible rather than a silent mutation of the source of truth.
Tuning parameters¶
- Edit-friction — how many steps stand between finding the error and saving the fix; lower friction captures more corrections at the moment of use but admits more low-quality edits.
- Review gate — whether edits publish immediately or pass a reviewer first; immediate publish keeps the record fresh but risks propagating a bad fix, a gate is safer but reintroduces the delay the workflow exists to kill.
- Edit scope limit — how much of an article one use-time edit may touch; tight limits keep changes safe and reviewable, loose ones let a knowledgeable worker fix more but raise the blast radius.
- Version retention depth — how much history is kept; deep retention protects auditability and reversibility but grows the store and can clutter the record.
When it helps, and when it misleads¶
Its strength is closing the gap between discovering a record is wrong and fixing it, by capturing the correction at the one moment the worker has both the error and the truth in hand — the operating principle of knowledge-centered service, where the people who use the knowledge maintain it as a by-product of use.[n1] Fresh records, corrected by their actual users, beat pristine records maintained by a distant team that never touches the work.
Its failure mode is record-integrity loss: an unvetted, unversioned edit made in haste can replace a correct-but-inconvenient article with a plausible-sounding error, and because it is now the retrieved version, everyone inherits it. The classic misuse is the silent overwrite — a fix saved with no change note and no retained history, so no one can tell what changed, why, or whether it was right. The guarding discipline is versioning with provenance as a hard requirement: every use-time edit is a new version with an author and a reason, the prior version stays recoverable, and scope limits keep any single edit small enough to review or roll back.
How it implements the components¶
target_pattern_boundary— scoping the edit to the one stale step or claim defines exactly which part of the record is opened for revision.corrective_difference_payload— the corrected content itself, captured at the moment of use while the reality it describes is concrete.version_or_annotation_layer— the fix is saved as a new version so future retrieval returns the revised article while prior versions persist.provenance_and_consent_boundary— recording who changed what and why keeps the source of truth auditable and reversible rather than silently mutated.
It does not run a restabilization_pathway, retrieval_spacing_plan, or context_transfer_probe — those are Simulation-Triggered Routine Update's job. That workflow changes what a body does when a trigger fires, through spaced rehearsal; this one changes what a document says when someone reads it, through a versioned edit.
Related¶
- Instantiates: Retrieval-Cued Revision — revises a shared record at the moment of retrieval so future lookups return the corrected version.
- Sibling mechanisms: Simulation-Triggered Routine Update · Controlled Reactivation Prompt · Corrective Experience Pairing · Guided Narrative Reframing · After-Action Recall Revision · Follow-Up Retrieval Probe · Safety and Consent Screening Protocol
Editorial Notes¶
Form Classification¶
Form family: Intervention, Treatment & Transformation
Rationale: Use Time Knowledge Article Update is defined in the frozen evidence as: Prompts a worker to update a knowledge-base article at the moment it is retrieved and found wrong, so future lookup retrieves the revised version. Its operative deployed or enacted form is therefore Intervention, Treatment & Transformation.
Nearest alternative: Protocol, Workflow & Routine — Protocol, Workflow & Routine can support this mechanism, but the evidence centers the concrete operation described above rather than the alternative family's defining operation.
Review outcome: Adjudicated after independent review; medium confidence.
Origin Attribution¶
Primary origin: Library & Information Science
Origin pattern: Single lineage
Present-day reach: Universal
Rationale: NIST SP 800-61 Rev. 2, Computer Security Incident Handling Guide documents that operational knowledge is updated from incident use, lessons learned, and observed gaps rather than only on a publication calendar. This is direct, mechanism-specific evidence for library information science as the best-evidenced historical home of the operation—Prompts a worker to update a knowledge-base article at the moment it is retrieved and found wrong, so future lookup retrieves the revised version.—rather than evidence merely that the operation is useful there. The retained alternates record genuine adjacent lineages; later portability is represented separately by domain_reach=universal.
Related originating lineages:
- Computer Science & Software Engineering — Computer science and software-engineering practice supplies a parallel or contributing lineage for the mechanism's defining operation: prompts a worker to update a knowledge-base article at the moment it is retrieved and found wrong, so future lookup retrieves the revised version.
- Organizational & Management Science — Organizational Management supplies a historically relevant adjacent lineage or formative practice for the operation—Prompts a worker to update a knowledge-base article at the moment it is retrieved and found wrong, so future lookup retrieves the revised version.—but the adjudicated evidence more directly locates the defining lineage in library information science.
- Systems Thinking & Cybernetics — Systems science's feedback, boundaries, control, and regulation tradition contributes a separate formative lineage to the mechanism's use time knowledge article update logic.
Review resolution: The blind reviewers disagree on primary lineage (organizational_management versus library_information_science). The defining operation is: Prompts a worker to update a knowledge-base article at the moment it is retrieved and found wrong, so future lookup retrieves the revised version. The researched NIST SP 800-61 Rev. 2, Computer Security Incident Handling Guide establishes that operational knowledge is updated from incident use, lessons learned, and observed gaps rather than only on a publication calendar. That source therefore supports library information science as the historical origin. organizational management remains in the uncapped alternates where it contributes a formative practice, but application or governance is not itself proof of origin. origin_mode=single_lineage records lineage construction; domain_reach=universal separately records later applicability.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
[n1] Knowledge-Centered Service (KCS) — a support methodology in which knowledge articles are created and improved as a by-product of solving problems, so the people who use the knowledge are the ones who keep it current. Use-time updating is the retrieval-cued edit at the heart of that model. ↩