{"schema_version":1,"experiment_id":"eoa_inverse_innovation_exp04_retrieval_first_paired20_20260802","cell_id":"layer_decay_and_expiration_management__film_media_production","hypothesis_id":"H1","search_queries":["video review platform comments previous version carry over new version superseded feedback","online proofing new version comments remain visible compare versions approval status official","film post production review notes version history comments new cut automatic carry forward","patent media review annotations version superseded comments editorial","site:help.wipster.io versions comments previous version resolve feedback","site:help.filestage.io version comments previous versions review decision official","site:help.vimeo.com video review comments versions previous version official","film post production conflicting feedback revision rework study editorial review comments"],"sources":[{"source_id":"PA1-S1","title":"How to copy and paste comments (Legacy)","publisher":"Frame.io","url":"https://help.frame.io/en/articles/1711085-how-to-copy-and-paste-comments-legacy","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Frame.io comments do not automatically carry over within version stacks.","Users can manually copy comments to another asset while retaining timecodes and annotations, functioning as selective renewal."]},{"source_id":"PA1-S2","title":"Review and Approve Videos","publisher":"EditShare MediaSilo","url":"https://helpdesk.editshare.com/hc/en-us/articles/24641423786779-Review-and-Approve-Videos","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Comments are scoped to the selected media version and prior-version comments are read-only in review links.","Users can resolve and hide comments without deleting them, compare versions, display comments from all versions, and retain a visible version label on each comment."]},{"source_id":"PA1-S3","title":"How to manage video versions and access history","publisher":"Vimeo","url":"https://help.vimeo.com/hc/en-us/articles/12426058338961-How-to-manage-video-versions-and-access-history","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Replacing a video automatically creates a new version and increments its version number.","Comments from earlier versions remain in version history, while a restored or new version can provide a clean comment slate and preserve the prior feedback audit trail."]},{"source_id":"PA1-S4","title":"How to verify that everyone’s feedback has been met","publisher":"Filestage","url":"https://help.filestage.io/en/articles/9113215-how-to-verify-that-everyone-s-feedback-has-been-met","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Filestage displays two versions side by side with their comments to verify prior feedback.","Its version history and downloadable reports preserve comments, review decisions, reviewer groups, and timestamps by version."]},{"source_id":"PA1-S5","title":"Upload a New Proof Version","publisher":"Teamwork.com","url":"https://support.teamwork.com/projects/proofing/proof-versions","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","claims_supported":["Proof creators upload a new version after acting on requested changes.","Comments are associated with the version on which they were made, and only comments for the selected version appear in the feedback panel."]},{"source_id":"PA1-S6","title":"US 2021/0406268 A1 — Search Result Annotations","publisher":"Google LLC / United States Patent Application Publication","url":"https://patentimages.storage.googleapis.com/b5/c7/08/e6bb65634ec995/US20210406268A1.pdf","source_class":"PUBLISHED_PATENT_APPLICATION","claims_supported":["The application describes a version-change annotation indicating that an item has been replaced or updated.","The annotation may identify and link to a successor and include the newer version's release date, establishing neighboring-domain prior art for explicit supersession markers."]},{"source_id":"PA1-S7","title":"Review Bottlenecks in Post Production: 2026 Fixes","publisher":"Sohonet","url":"https://www.sohonet.com/article/review-bottlenecks-in-post-production-2026-fixes","source_class":"COMMERCIAL_FIRST_PARTY","claims_supported":["Sohonet reports that contradictory feedback or feedback applied to the wrong version produces additional post-production review rounds and unnecessary work.","It presents a vendor case observation in which centralized, frame-accurate review reduced average review rounds from 4.2 to 1.8 across three projects; this is suggestive but not controlled independent research."]}],"proximity":"SUBSTANTIAL_COLLISION","closest_analogues":[{"name":"MediaSilo version-scoped and resolvable comments","similarity":"It already binds comments to a cut version, makes prior-version feedback read-only, labels comments by version, supports resolved/hidden states, and preserves all-version review history.","remaining_difference":"The documentation does not show every prior note receiving an explicit automatic expired-or-superseded state on revision or a first-class renewal link to its successor note.","source_ids":["PA1-S2"]},{"name":"Vimeo automatic version history with clean comment slates","similarity":"A replacement automatically creates a new current version while earlier comments remain preserved in version history, functionally demoting them from the active review surface.","remaining_difference":"The lifecycle transition is expressed through version scoping rather than an explicit per-note supersession state and renewal decision.","source_ids":["PA1-S3"]},{"name":"Teamwork proof-version comment isolation","similarity":"Each revision has its own feedback set, and changing to a new proof version prevents old comments from appearing as current feedback by default.","remaining_difference":"No documented per-comment renewal, supersession marker, or successor lineage exists across proof versions.","source_ids":["PA1-S5"]},{"name":"Frame.io non-carryover plus manual comment copying","similarity":"Old comments remain with their source version, while selected feedback can be manually copied to another cut with its timing and annotations intact, approximating expiration plus renewal.","remaining_difference":"Renewal is a manual copy operation and the source note is not documented as automatically labeled expired or linked to the renewed copy.","source_ids":["PA1-S1"]},{"name":"Generic version-change successor annotation","similarity":"The patent describes explicitly marking an item as replaced or updated and identifying or linking to its successor.","remaining_difference":"It concerns search-result items, not editorial notes whose lifecycle is triggered by a new cut revision.","source_ids":["PA1-S6"]}],"overlapping_components":["version-linked editorial note identity","automatic creation and ordering of cut versions","default demotion of prior-version comments from the current feedback surface","per-version comment visibility and read-only historical state","manual resolved-or-hidden comment state","selective carry-forward of still-valid feedback","preserved comment and approval audit history","version comparison for checking whether prior feedback was addressed","generic replaced-by or successor marker"],"remaining_contrastive_claim":"Unlike documented version-scoped review systems, the treatment would automatically assign every note an explicit expired-or-superseded state when its referenced cut changes, while requiring an explicit renewal decision and preserving a machine-readable source-to-successor note link.","claim_falsifier":"Official documentation, a reproducible product test, or an earlier patent showing that uploading or promoting a new cut automatically transitions each prior comment to an explicit expired or superseded state and supports provenance-preserving renewal or successor linkage would falsify the remaining claim.","problem_support":"MODERATE","recommendation":"REJECT","world_novelty_boundary":"This bounded eight-query search found established film and creative-review practice for version-scoped comments, automatic separation of old feedback from a new revision, manual resolution or carry-forward, and preserved audit history; it did not establish an earlier film-review implementation of explicit per-note automatic expiration plus renewal and successor linkage, but that narrow interface distinction does not overcome the substantial functional collision with existing versioned-review workflows."}