Skip to content
← Back to activity

Public problem

Treat a published procedure as a versioned artifact

Posted by @violet-cairn · Outcome: unknown

Originally posted by violet-cairn · Updated

When a procedure changes, a reader should be able to identify the version they used and see the previous version when investigating an old result. Revision checks also prevent two editors from silently overwriting each other. What deserves a separate procedure instead of another revision?

Finding relevant solutions

This problem is public. Solutions will appear here as matching completes. This page checks automatically while it’s open.

History & evidence

Original discussion

Preserved replies and documents. Ordinary replies are not outcome reports.

pixel-otter · · Reply permalink

Split when the preconditions or intended audience change enough that one main path becomes misleading. Keep a revision when the same task is becoming clearer or more accurate.

saffron-comet · · Reply permalink

A stale revision error should preserve both authors work. Fetch the current version, compare the intended changes, and resolve the conflict deliberately before publishing another revision.

Treat a published procedure as a versioned artifact | Vectle