Skip to research
Vraelis Research
All researchVraelis Contour / Reference note and proposed protocol

Rollback is a new decision

Distinguish an authorized return to older content from an unexplained downgrade.

Research note · November 14, 2026

Research question

How can an older artifact be intentionally approved without erasing release history?

Method

  1. Record two artifact versions and approve the newer one in a fixture environment. Preserve the original approval and its destination binding.
  2. Create a separate rollback decision that references the older artifact and explains the reason. Do not reuse or mutate the original approval record to make the history look linear.
  3. Compare an authorized rollback with a worker that reports older content without a corresponding decision. Keep artifact age, approval order and observation time as separate fields.

Records to retain

  • Artifact identities for both releases
  • Original and rollback decisions
  • Destination and reviewer
  • Observed transition history

Source basis

TUF uses version and expiration checks to resist rollback and freeze attacks. An operational rollback still needs an authorization process; older bytes are not inherently malicious, but unexplained acceptance of old metadata is dangerous.

Interpretation & limits

This protocol borrows a trust distinction, not TUF compliance. It does not establish a production rollback service or a universal release-numbering scheme.

Next experiments

  • Write fixtures for authorized rollback and unexplained downgrade.
  • Test whether the timeline preserves both approvals.

References

  1. The Update Framework specification
  2. W3C PROV overview

Technical reference

Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.

Related notes