{"schema_version":1,"research_id":"eoa_inverse_innovation_exp04_external_evaluation_20260802","source_assessment_id":"layer_decay_and_expiration_management__film_media_production:SENTINEL:v0","cell_id":"layer_decay_and_expiration_management__film_media_production","search_queries":["site:help.frame.io comments version stacks mark complete official","site:help.autodesk.com Flow Production Tracking notes version status official","site:videoreview.pro version comments latest cut open done","film post production review stale feedback old version comments rework","Frame.io official version stack comments completed copy comments version","site:help.filestage.io versions comments carry forward resolved official","site:help.wipster.io versions comments resolved feedback new version official","site:clipback.video revisions comments automatically resolved approval","Filestage official help new version comments resolved carry over","Wipster official help comments versions resolved new version","Workfront proof comments previous version official documentation","video review version comments outdated cut problem official case study","ScreenSkills post production supervisor responsibilities review notes versions director producer","Producers Guild post production supervisor approvals editorial workflow","DGA director authority final cut notes post production official","film production records retention legal hold studio policy official","site:bls.gov Occupational Outlook Handbook film and video editors median pay 2025","site:bls.gov software developers median pay May 2025 occupational outlook","Frame.io pricing 2026 official","Autodesk Flow Production Tracking pricing official 2026","site:next.developer.frame.io API update comment completed status version stack webhook","site:developers.frame.io webhooks assets comments official","site:developers.shotgridsoftware.com event daemon note status version official","site:help.autodesk.com Flow Production Tracking webhooks events API official","online feedback post-production film editors study version feedback comments thesis","post-production collaboration feedback version control film research paper","video review approval workflow version confusion case study film editor","film editor feedback revisions version control study","site:help.filestage.io \"Copy comments between reviewer groups and versions\"","site:help.frame.io \"copy comments\" version comments official","site:playpause.io new version comment reset resolved notes","site:videoreview.pro latest cut comments version scoped open done"],"sources":[{"source_id":"S1","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","publication_date":"2026","accessed_at":"2026-08-02","claims_supported":["Sohonet reports that feedback applied to the wrong version contributes to additional review rounds.","Its first-party case account reports a facility moving from 4.2 to 1.8 review rounds across three projects after adopting centralized, frame-accurate review.","This is vendor evidence rather than an independently audited prevalence estimate."]},{"source_id":"S2","title":"Improving post-production feedback process","publisher":"Umeå University","url":"https://umu.diva-portal.org/smash/record.jsf?pid=diva2%3A1457277","source_class":"PRIMARY_RESEARCH","publication_date":"2020-08-11","accessed_at":"2026-08-02","claims_supported":["An advanced-level thesis identifies review and feedback on rough and editorial cuts as a complicated, time-consuming part of film and series post-production.","The research context included online feedback between editors and reviewers and external cooperation with Codemill.","The abstract does not quantify stale-note incidence or the proposed intervention's effect."]},{"source_id":"S3","title":"Basic Agreement of 2020—Article 7: Directors' Minimum Conditions Preparation, Production and Post-Production","publisher":"Directors Guild of America","url":"https://www.dga.org/Contracts/Directors-Economic-Rights/Basic-Agreement-Article-7","source_class":"STANDARD","publication_date":"2020","accessed_at":"2026-08-02","claims_supported":["The director must be consulted on creative decisions in preparation, production, and post-production.","The director is responsible for presenting the director's cut, supporting the requirement that software not decide creative applicability autonomously."]},{"source_id":"S4","title":"Producing Credits for Feature Films","publisher":"Producers Guild of America","url":"https://producersguild.org/code-of-credits-feature-films/","source_class":"OFFICIAL_GUIDANCE","publication_date":"2024","accessed_at":"2026-08-02","claims_supported":["Post-production producers and supervisors establish workflows, manage schedules and staff, and execute notes for cuts.","The post-production supervisor reports to producers and is an identifiable operational adopter or delegated administrator.","Producers retain approval responsibilities for final post-production elements."]},{"source_id":"S5","title":"Comments Panel Overview","publisher":"Frame.io / Adobe","url":"https://help.frame.io/en/articles/9105278-comments-panel-overview","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2024","accessed_at":"2026-08-02","claims_supported":["Frame.io supports manual Mark As Complete for feedback applied to a subsequent edit.","Comments can be filtered by completion state, copied to other media, linked, searched, and exported.","The documentation does not establish automatic expiry on cut promotion or predecessor-successor lineage."]},{"source_id":"S6","title":"Timestamped Video Review for Editors, Teams & Clients","publisher":"VideoReview","url":"https://videoreview.pro/","source_class":"COMMERCIAL_FIRST_PARTY","publication_date":"undated; current when accessed","accessed_at":"2026-08-02","claims_supported":["VideoReview scopes comments to the cut on which they were made and directs shared links to the latest cut.","It supports Open and Done states, side-by-side comparison, review statuses, and preserved status in exports.","Its documentation does not show authorized carry-forward or note lineage."]},{"source_id":"S7","title":"Manage different versions of a file","publisher":"Filestage","url":"https://help.filestage.io/en/articles/2211321-manage-different-versions-of-a-file","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"undated; current when accessed","accessed_at":"2026-08-02","claims_supported":["A newly uploaded Filestage version starts without comments while prior comments remain accessible in version history.","This already demotes old-version comments from the new version's active surface by default.","Deleting a version permanently removes its comments, supporting preservation-by-default during the proposed test."]},{"source_id":"S8","title":"Copy comments between reviewer groups and versions","publisher":"Filestage","url":"https://help.filestage.io/en/articles/6318439-copy-comments-between-reviewer-groups-and-versions","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"undated; current when accessed","accessed_at":"2026-08-02","claims_supported":["Authorized team members can selectively copy comments from an old version to a new version.","Copied comments default to unresolved, but appear as new comments authored by the copier and lose original timestamps and mentions.","This closely overlaps explicit carry-forward but does not preserve an explicit predecessor-successor identity link."]},{"source_id":"S9","title":"Approval Workflows for Video Review","publisher":"PlayPause","url":"https://playpause.io/approval-workflow","source_class":"COMMERCIAL_FIRST_PARTY","publication_date":"undated; current when accessed","accessed_at":"2026-08-02","claims_supported":["PlayPause says uploading a new version after approval automatically resets affected approval stages.","It identifies post supervisors, directors, producers, legal reviewers, studios, streamers, and distributors as workflow actors.","Its page supplies user testimonials but not independently verified outcomes."]},{"source_id":"S10","title":"Client Review Portal","publisher":"PlayPause","url":"https://playpause.io/client-review-portal","source_class":"COMMERCIAL_FIRST_PARTY","publication_date":"undated; current when accessed","accessed_at":"2026-08-02","claims_supported":["Each new version has a clean comment panel while old notes remain attached to their original version and accessible in history.","The product supports version-specific links, comparison, resolved states, approval records, role-based visibility, and permanent audit history.","The page does not establish explicit per-note renewal objects with predecessor-successor lineage."]},{"source_id":"S11","title":"Tracking statuses for client-side productions","publisher":"Autodesk","url":"https://help.autodesk.com/cloudhelp/ENU/SG-Tutorials/files/SG_Tutorials_tu_tracking_statuses_html.html","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"undated; current when accessed","accessed_at":"2026-08-02","claims_supported":["Flow Production Tracking supports version, cut, and note statuses, including Open, In Progress, and Closed or no-longer-relevant notes.","Only Open notes appear in some interfaces, demonstrating status-based demotion.","Autodesk documents automatic status triggers, though not successor-version-triggered closure of every prior note."]},{"source_id":"S12","title":"Webhooks Guide","publisher":"Autodesk","url":"https://help.autodesk.com/view/SGDEV/ENU/?contextId=WE_WEBOOK_GUIDE","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"undated; current when accessed","accessed_at":"2026-08-02","claims_supported":["Flow Production Tracking webhooks expose entity creation, update, deletion, and revival events and can automate status management.","REST and Python APIs can retrieve and update entities, making a revision-triggered state machine technically plausible.","Operational constraints include delivery throttling, possible event-order anomalies, seven-day webhook delivery-log retention, authentication, and infrastructure ownership."]},{"source_id":"S13","title":"Document Retention Policy","publisher":"Disney Production Safety","url":"https://sites.disney.com/app/uploads/sites/53/2022/03/Document-Retention-Policy.pdf","source_class":"OFFICIAL_GUIDANCE","publication_date":"2023-12-13","accessed_at":"2026-08-02","claims_supported":["A first-party film and television production policy requires official records to follow retention schedules and legislative, fiscal, contractual, administrative, and operational requirements.","Production management is responsible for accurate, complete retention and authorized disposal.","The policy concerns covered production records and does not establish a universal retention rule for editorial comments."]},{"source_id":"S14","title":"National employment and wage data by occupation, May 2025","publisher":"U.S. Bureau of Labor Statistics","url":"https://www.bls.gov/news.release/ocwage.t01.htm?mod=article_inline","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2026-05-15","accessed_at":"2026-08-02","claims_supported":["May 2025 median hourly wages were $65.38 for software developers and $36.26 for film and video editors.","Mean hourly wages were $71.20 for software developers and $41.41 for film and video editors.","These wages are base labor anchors and exclude contractor premiums, benefits, overhead, and specialized post-production rates."]},{"source_id":"S15","title":"Frame.io Pricing","publisher":"Frame.io / Adobe","url":"https://frame.io/pricing","source_class":"COMMERCIAL_FIRST_PARTY","publication_date":"current pricing accessed 2026-08-02","accessed_at":"2026-08-02","claims_supported":["Listed plans include Free, Pro at $15 per user per month, Team at $25 per user per month, and custom Enterprise pricing.","Version stacks, comparison, comments, and exports are available product capabilities.","Software seats are a small part of likely costs; custom development, workflow design, training, governance, and enterprise requirements dominate the estimates."]}],"problem_evidence":{"support":"MODERATE","rationale":"Independent academic work identifies post-production review as complicated and time-consuming, while Sohonet reports recurring wrong-version feedback and additional review rounds. Multiple vendors explicitly market against version confusion. However, the exact proposed failure—old notes remaining actionable inside an already version-scoped professional review tool—has not been measured. Existing products commonly give each new version a clean or version-specific comment surface, so the residual problem may occur mainly in fragmented workflows, weak configurations, or manual exports.","source_ids":["S1","S2","S6","S7","S10"]},"stakeholder_evidence":{"support":"MODERATE","rationale":"The DGA and Producers Guild establish directors, producers, post-production producers, and post-production supervisors as credible creative authorities and workflow owners. Product pages identify these same roles and legal/compliance reviewers as users. This supports an identifiable adopter and authorizer, but no named production has committed budget, supplied data, or requested the precise lineage feature.","source_ids":["S3","S4","S9","S10"]},"prior_art":{"proximity":"SUBSTANTIAL_COLLISION","closest_analogues":[{"name":"PlayPause clean per-version comment panels and approval reset","similarity":"New versions become current with clean comment panels; prior notes remain in history; approval stages can reset after a version change; resolved states, audit records, and role-specific views are supported.","remaining_difference":"Opened materials do not show an explicit expired or superseded state on every prior note, authorization-required renewal objects, or durable predecessor-successor note identity.","source_ids":["S9","S10"]},{"name":"Filestage fresh-version comments plus selective copy-forward","similarity":"New versions start without old comments, history is preserved, and authorized team members can selectively copy chosen comments into the new version as unresolved work.","remaining_difference":"Copied comments are new records attributed to the copier, with reset timestamps and no documented predecessor-successor linkage; automatic expiry labels are also not shown.","source_ids":["S7","S8"]},{"name":"VideoReview version-scoped comments with Open/Done states","similarity":"Comments remain scoped to their originating cut, links follow the latest cut, old cuts remain comparable, and comments have actionable lifecycle states.","remaining_difference":"No documented automatic per-note expiry, explicit carry-forward, or successor lineage.","source_ids":["S6"]},{"name":"Autodesk Flow Production Tracking note/version/status automation","similarity":"Notes and versions have configurable statuses, Closed includes no-longer-relevant notes, inactive notes can be suppressed, and status changes can be automated through APIs and webhooks.","remaining_difference":"Official documentation does not show promotion of a successor editorial cut automatically transitioning all prior-cut notes or creating renewal lineage.","source_ids":["S11","S12"]},{"name":"Frame.io completion, filtering, and comment copying","similarity":"Frame.io already provides versioned media, manual completion, state filtering, comment copy/paste, links, and exportable history.","remaining_difference":"Completion and carry-forward are manual and the opened documentation does not establish revision-triggered expiry or predecessor-successor lineage.","source_ids":["S5"]}],"distinctive_claim_remaining":"Relative to version-scoped clean comment panels plus manual completion or selective copying, promotion-triggered explicit expiry combined with authorization-required renewal and durable predecessor-successor note lineage will reduce edits attributable to superseded feedback by at least 25%, while keeping false expiry at or below 5%, missed valid carry-forward at or below 5%, and median renewal labor at or below two minutes per renewed note.","confidence":"HIGH"},"implementation_evidence":{"support":"MODERATE","rationale":"The necessary primitives—version identity, note status, current-version surfaces, history, selective copying, webhooks, APIs, role controls, and audit records—are established in commercial systems. A read-only prototype is technically straightforward. Remaining uncertainties are production-specific note-to-cut identity quality, what event constitutes authorized cut promotion, API permissions and rate limits, cross-platform exports, concurrency, user-interface support for lineage, and records-policy approval. Creative authority must remain with directors/producers or delegates, and the proposal must demote rather than delete records.","source_ids":["S3","S4","S7","S8","S10","S11","S12","S13"]},"scores":{"meaningful_impact":{"score":3,"rationale":"Wrong-version feedback can cause unnecessary work and additional review rounds, but the incremental impact beyond modern version scoping is unmeasured.","source_ids":["S1","S2","S6","S10"]},"stakeholder_pull":{"score":3,"rationale":"Credible workflow owners and authorizers are identifiable, and vendors report demand for version clarity, but no adopter has requested or funded this exact feature.","source_ids":["S3","S4","S9","S10"]},"incremental_advantage":{"score":2,"rationale":"Clean new-version panels and selective comment copy-forward already implement most of the operational behavior; the remaining advantage is explicit state and lineage.","source_ids":["S7","S8","S9","S10"]},"distinctiveness_plausibility":{"score":2,"rationale":"The opened sources did not show explicit predecessor-successor note lineage, but the difference is narrow and could exist in undocumented configurations or private studio automations.","source_ids":["S5","S8","S10","S11"]},"technical_implementability":{"score":4,"rationale":"Version, note, status, API, webhook, audit, and role primitives are available. Data quality and integration behavior require testing rather than new scientific capability.","source_ids":["S7","S8","S11","S12"]},"adoption_authority_feasibility":{"score":3,"rationale":"Directors, producers, and post-production supervisors provide a credible authority chain, but delegation and final-cut rights vary by production agreement.","source_ids":["S3","S4"]},"evidence_readiness":{"score":3,"rationale":"A bounded retrospective replay is specified and public comparators exist, but production note data, authoritative adjudication, and incident labels are proprietary.","source_ids":["S5","S7","S8","S10","S11"]},"safety_net_benefit":{"score":4,"rationale":"The intervention changes visibility and applicability without deletion, preserves history, and permits authorized renewal; this meaningfully limits irreversible harm if implemented with audit and rollback.","source_ids":["S3","S10","S13"]},"scalability":{"score":4,"rationale":"Event-driven status transitions can scale across versions and notes, although webhook ordering, throttling, identity resolution, and reviewer workload must be monitored.","source_ids":["S11","S12"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"Read-only retrospective replay for no more than three sequences, three or more promoted cuts per sequence, and 150 notes; includes data extraction, a lightweight simulator, two authorized reviewers, adjudication, analysis, and records-policy review.","confidence":"MODERATE","assumptions":["Approximately 120-250 combined hours across an analyst/developer, editor or assistant editor, two authorized reviewers, and a post-production supervisor.","Existing exports or API access are available without custom vendor procurement.","Loaded or specialist contract rates exceed BLS base wages, but no live production integration is performed."],"source_ids":["S12","S14","S15"]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"Production-ready integration implementing promotion events, note lifecycle states, role authorization, lineage records, rollback, audit views, monitoring, security review, and tests in one review platform.","confidence":"MODERATE","assumptions":["Roughly 800-2,000 engineering, design, QA, security, and workflow-configuration hours.","The platform exposes sufficient API permissions or supports a native extension.","No media transcoding or storage system is rebuilt; only metadata and review-state behavior are added.","Specialist contracting, benefits, and organizational overhead are above BLS base wages."],"source_ids":["S11","S12","S14","S15"]},"operational_launch":{"band_2026_usd":"50K_TO_250K","scope":"Controlled launch across three productions, including onboarding, historical mapping, training, help-desk coverage, monitoring, incident review, authorized adjudication, and comparative evaluation against current workflows.","confidence":"LOW","assumptions":["Productions already license a review platform and retain accessible note/version history.","Launch includes compensated director/producer or delegated-review time.","Legal, privacy, labor, and records-policy review is bounded and does not require enterprise-wide contract renegotiation.","Cost varies substantially with production scale, union context, security requirements, and integration vendor."],"source_ids":["S3","S4","S13","S14","S15"]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Ongoing service hosting, API monitoring, audit retention, support, policy administration, periodic accuracy review, training, and approximately 0.25-1.0 FTE of pipeline or workflow ownership; review-platform seats are additional where not already licensed.","confidence":"LOW","assumptions":["Seat prices for non-enterprise Frame.io plans are $15-$25 per user per month, while enterprise pricing is custom.","Labor and governance dominate software-seat cost.","No large media-storage expansion is attributed to the feature because it preserves metadata and existing history rather than duplicating masters.","Annual incident volume remains manageable without full-time manual adjudication."],"source_ids":["S12","S14","S15"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"Wrong-version feedback and costly review friction are externally visible, although the prevalence of stale notes inside modern version-scoped systems remains unquantified.","source_ids":["S1","S2","S6","S10"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"Producers and post-production supervisors are recognized workflow owners, while directors and designated final-cut authorities govern creative intent.","source_ids":["S3","S4"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"The residual claim is bounded to explicit expiry, authorization-required renewal, and durable per-note lineage versus clean version panels and manual copy or completion, with numerical effect and error thresholds.","source_ids":["S5","S7","S8","S10"]},"bounded_next_evidence_step":{"status":"YES","reason":"A capped retrospective replay with named comparators, sample limits, metrics, and falsifiers can be completed without altering a live production.","source_ids":["S7","S8","S10","S11","S12"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"For the proposed read-only step, notes and media remain untouched, history remains visible, and authorized reviewers adjudicate applicability. Deployment must still obtain production-specific delegation and retention approval.","source_ids":["S3","S4","S13"]},"credible_cost_scope_and_range":{"status":"YES","reason":"Public 2025 occupational wages and current product pricing anchor resource-equivalent ranges; integration and enterprise estimates remain explicitly assumption-driven.","source_ids":["S14","S15"]}},"next_evidence_step":"With one completed, picture-locked production, select at most three sequences having at least three promoted cuts each and no more than 150 version-linked notes. First reproduce current behavior in sandbox accounts for PlayPause or Filestage and the production's existing tool. Then perform a read-only, randomized-order retrospective comparison of: A) the production's version-scoped/manual-resolution baseline; B) a clean-new-version panel with authorized selective copy-forward but no lineage; and C) promotion-triggered explicit expiry with authorized renewal and predecessor-successor lineage. Two authorized reviewers independently label whether each prior note was stale, still applicable, or ambiguous and time each renewal. Measure resolvable note-to-cut identity, baseline stale-note exposure, precision and recall, false expiry, missed carry-forward, reviewer agreement, renewal time, lineage completeness, and retrospectively identifiable stale-feedback edits or reconciliation minutes. Stop if note-to-cut identity is below 95%, protected records cannot remain visible, reviewer agreement is below 90%, or a rival already provides verifiable predecessor-successor lineage. Falsify the intervention if baseline stale-note incidents are zero or immaterial, false expiry or missed valid carry-forward exceeds 5%, median renewal exceeds two minutes, or the data do not support at least a 25% reduction in stale-feedback edits versus comparator B. Only after passing should three prospective productions be considered.","blocking_evidence":["No production-specific estimate of stale-note prevalence or reconciliation time exists.","No controlled evidence shows incremental benefit over clean version panels plus selective copy-forward.","No named production partner, data-access agreement, or authorized reviewer commitment is documented.","Note-to-cut identity completeness and the reliability of cut-promotion events are unknown.","Opened documentation does not resolve whether private studio automations or undocumented product configurations already preserve per-note successor lineage.","Production-specific records retention, confidentiality, privacy, union, contractual, and creative-rights requirements require local approval.","Enterprise API permissions, platform rate limits, and native user-interface support for lineage have not been tested."],"research_disposition":"PARTNERED_RESEARCH_PROGRAM","world_novelty_boundary":"This evaluation establishes only a bounded ordinary-web prior-art boundary. It does not measure or imply world novelty, patentability, freedom to operate, market size, or realized impact. Patents, inaccessible products, private studio automations, custom Flow Production Tracking schemas, undocumented configurations, and non-English sources may already implement the remaining lineage behavior.","arm":"SENTINEL","candidate_version":0,"controller_recommendation":{"action":"STOP_EMPIRICAL_RESEARCH_NEEDED","repairable":true,"material_progress_observed":true,"progress_targets":["Secure one completed production with authorized access to at least three sequences, three promoted cuts per sequence, and up to 150 notes.","Reproduce PlayPause or Filestage clean-panel and selective-copy behavior and test whether any current configuration already preserves predecessor-successor lineage.","Establish baseline stale-feedback incident counts and reconciliation minutes from production records.","Demonstrate at least 95% note-to-cut identity resolution, at least 90% reviewer agreement, no protected-history loss, at most 5% false expiry, at most 5% missed carry-forward, and at most two minutes median renewal labor.","Show at least a 25% reduction in stale-feedback edits relative to the strongest clean-panel/selective-copy comparator across subsequent prospective productions.","Obtain written producer or final-cut-authority delegation and production-specific records, privacy, security, and legal approval before any live state changes."],"reason":"Web research verified a material general problem and credible authority chain, but also found substantial collision: commercial systems already provide clean new-version panels, preserved history, selective comment carry-forward, status demotion, and version-triggered approval resets. The only remaining distinction is explicit expiry plus authorized renewal with durable per-note lineage. Determining whether that narrow addition improves outcomes requires proprietary production records, authorized adjudication, product sandbox testing, and ultimately live comparative use; bounded web research cannot resolve it."}}