Correct and Supersede a Community Profile
A correction should make the old claim easier to understand, not harder to find. If a profile has the wrong printer identity, omitted a material condition, exposed private data, failed a stated test, or became misleading after a release or hardware change, preserve the original revision where the platform and privacy rules allow it, then publish a clearly linked correction or superseding revision. Do not silently replace history while leaving readers to guess what changed.
Choose the lifecycle action
- Clarification: the claim remains valid, but an ambiguous label, missing qualifier, or explanation needs to be added.
- Correction: a factual, identity, packaging, or test-context error affects interpretation. Name the affected field and the safe reading.
- Supersession: a new revision replaces the old one after a deliberate change or revalidation. Keep the old identifier as history and rollback unless it contains a secret or unsafe data.
- Withdrawal: the result should no longer be reused—for example, the artifact is corrupted, the setup cannot be identified, the test was invalid, or a safety or compatibility concern is unresolved. State that the withdrawal is not a new test result.
- Retirement: the profile is no longer maintained or relevant, but it may remain useful as historical context when its limitations are clear.
These labels describe a transparent record; they do not override the hosting service’s moderation, editing, release, or deletion rules.
Publish a correction record
record_type: "clarification / correction / supersession / withdrawal / retirement"
affected_profile: "profile identifier and revision"
reported_or_found: "date and source of the issue"
problem: "precise field, identity, artifact, or test-context problem"
impact: "who should stop using it and what may be affected"
replacement: "new profile or corrected section, or none"
verification: "what was checked, by whom, on which setup, and observed result"
status: "current lifecycle state"
rollback: "previous or replacement revision"
privacy_action: "secret removed / artifact replaced / no private data / unknown"
remaining_unknowns: ["unresolved questions"]
Use plain language: “This revision was tested only on a 0.4 mm brass nozzle and should not be copied to the hardened-nozzle setup” is more useful than “fixed.” If a value was copied from a preset rather than measured, correct the evidence state as well as the number. If the issue is only a missing context field, do not imply that the print result itself was invalid.
Protect people and artifacts while correcting
Remove API keys, passwords, access tokens, private addresses, account identifiers, local paths, private model files, and identifying photos before reposting a profile. If a published artifact cannot be safely edited in place, mark it unavailable where allowed and attach a sanitized replacement with a new revision. Do not quote a secret in the correction note to prove that it was present.
Keep the old file when it is safe and useful for comparison, but mark it superseded or withdrawn in the surrounding text and link the replacement prominently. For release-like artifacts, an immutable publication may protect the original asset and tag from later mutation; that makes the correction link and lifecycle note more important, not less. A stable artifact can still be wrong for a particular printer or material.
Close the loop
Tell readers what to do now: stop using the affected revision, import the replacement into an isolated profile, compare effective values, inspect the preview and final output, and run the smallest physical check needed for the changed claim. Record whether the correction was software-only, a re-analysis of an old result, or a new physical test. If no new test exists, say so. Link disputes to the relevant source or test context and keep moderation decisions separate from technical validity.
A correction is complete when a reader can identify the affected revision, understand the impact, find the replacement or rollback, see what was verified, and know which unknowns still block safe reuse.