{"schema_version":1,"research_id":"eoa_inverse_innovation_exp03_external48_20260801","source_assessment_id":"eoa_inverse_innovation_exp03_opportunity320_20260801","cell_id":"layer_decay_and_expiration_management__film_media_production","selection_stratum":"HIGH_UPSIDE_RESEARCH_OPTION","search_queries":["site:fiafnet.org digital preservation principles audiovisual archive files access copies preservation masters","media asset management lifecycle archive restore proxy version official documentation","site:help.autodesk.com ShotGrid dependency tracking publish files versions official","iconik archive restore asset storage official documentation","MovieLabs ontology asset version relationship provenance official specification media creation","PREMIS preservation metadata dependencies rights events official Library of Congress","site:movielabs.com case study media production file duplication version confusion storage","film post-production data management version confusion storage survey study","visual effects production version management file dependency research paper","site:archives.gov audiovisual records retention disposition digital media legal hold","site:aws.amazon.com/s3/pricing Glacier Deep Archive pricing US East 2026","site:bls.gov Occupational Employment Wage Statistics film and video editors May 2025"],"sources":[{"source_id":"S1","title":"Learning to Love End-to-End Cloud Production in Love Hurts","publisher":"MovieLabs","url":"https://movielabs.com/case_study/learning-to-love-end-to-end-cloud-production-in-love-hurts/","source_class":"OFFICIAL_ORGANIZATION_DATA","publication_date":"n.d.","accessed_at":"2026-08-02","claims_supported":["A feature-production pilot used 325 TB of cloud data and a centralized store to reduce duplication and version/synchronization confusion.","Enabling storage versioning unexpectedly tripled volume, and the completed production retained duplicate, mistaken, and otherwise unclean files.","The case study says clean production-asset archiving still needs improvement and identifies coordination, training, hybrid systems, software-version support, and archive-team involvement as implementation requirements."]},{"source_id":"S2","title":"Archive and Restore","publisher":"Iconik / Backlight","url":"https://help.iconik.backlight.co/hc/en-us/articles/25303782583703-Archive-and-Restore","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2024","accessed_at":"2026-08-02","claims_supported":["A current media-asset system can move original formats to archive storage and restore them.","The system exposes archive and deleted-on-main-storage status while retaining restorability.","Archive and restore operations are permission-controlled through specific roles."]},{"source_id":"S3","title":"Ontology for Media Creation: Versions Ontology v2.7","publisher":"MovieLabs","url":"https://mc.movielabs.com/omc/Asset/Asset_Versions/ML_Ontology_Pt3B_Versions_v2.7.pdf","source_class":"STANDARD","publication_date":"2024-07-31","accessed_at":"2026-08-02","claims_supported":["The media-creation ontology represents versions, revisions, variants, derivations, representations, provenance, source-asset relationships, and human-readable change annotations.","It recognizes that review and approval across revisions is complex and that selecting which revision proceeds downstream requires workflow policy.","It explicitly leaves decisions such as when intermediate work becomes a revision to local workflow processes."]},{"source_id":"S4","title":"Managing Audiovisual Records","publisher":"U.S. National Archives and Records Administration","url":"https://www.archives.gov/records-mgmt/publications/managing-audiovisual-records.html","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"1999","accessed_at":"2026-08-02","claims_supported":["Audiovisual lifecycle management includes inventory, scheduling, provenance, ownership-rights documentation, transfer, and authorized disposition.","Relationships among audiovisual records and complementary files matter, and withdrawn programs should not be disposed of without consultation between records and audiovisual officials.","The federal guidance requires authorized schedules before destruction and recommends periodic inspection, controlled access, separation of originals and use copies, and preservation of related production documentation."]},{"source_id":"S5","title":"Depends: Workflow Management for Research and Visual Effects","publisher":"Linköping University Visual Computing Laboratory","url":"https://computergraphics.on.liu.se/dependsworkflow.net/","source_class":"PRIMARY_RESEARCH","publication_date":"2014","accessed_at":"2026-08-02","claims_supported":["An implemented visual-effects workflow system represents processes as a dependency graph and preserves provenance.","It includes built-in versioning, stale-data tracking, file-presence and validity checks, typed inputs and outputs, and execution validation.","The implementation demonstrates that dependency and stale-state tracking are technically feasible in a bounded VFX pipeline, although it is not an archive-disposition system."]},{"source_id":"S6","title":"PREMIS Data Dictionary, Version 3.0, Now Available","publisher":"Library of Congress / PREMIS Editorial Committee","url":"https://www.loc.gov/standards/premis/version-3-0-dd-announcement.html","source_class":"STANDARD","publication_date":"2015-06-10","accessed_at":"2026-08-02","claims_supported":["PREMIS supports preservation objects, events, agents, rights, structural and derivative relationships, version information, and preservation-level metadata.","It models software, hardware, plug-ins, and other technical dependencies needed to interpret digital objects.","It provides established metadata building blocks for recording preservation actions and rights, reducing the candidate's component-level distinctiveness."]},{"source_id":"S7","title":"Archive a Blob","publisher":"Microsoft","url":"https://learn.microsoft.com/en-us/azure/storage/blobs/archive-blob","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2026-06-12","accessed_at":"2026-08-02","claims_supported":["Cloud storage already supports manual and policy-driven transitions from online to archive tiers and later rehydration.","Archive data can become unreadable for hours and incur retrieval and minimum-duration costs.","Age or access-based lifecycle rules can rearchive restored data unless explicit exclusions are configured, illustrating why candidate-specific governance gates and markers may matter."]},{"source_id":"S8","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","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2026-05-15","accessed_at":"2026-08-02","claims_supported":["May 2025 mean hourly wages were $41.41 for film and video editors, $54.27 for special-effects artists and animators, $33.96 for archivists, and $55.10 for computer systems analysts.","These wage data provide a conservative labor anchor for broad 2026 resource-equivalent cost bands; they exclude benefits, overhead, legal review, software, storage, and vendor margins."]}],"problem_evidence":{"support":"MODERATE","rationale":"The MovieLabs feature-production case directly observed duplicate and mistaken files, version/synchronization risk, an accidental tripling of storage after versioning was enabled, and difficulty creating a clean archive. It verifies that the candidate's problem can be material in a real major-studio production, but one case does not establish prevalence across productions or isolate lifecycle sprawl from configuration, permissions, naming, and search defects.","source_ids":["S1","S3"]},"stakeholder_evidence":{"support":"MODERATE","rationale":"Universal, post houses, vendors, archive staff, security teams, and production-support teams participated in or were affected by the documented workflow, and MovieLabs reports continued interest in cloud archiving. Iconik and NARA also demonstrate real permission-bearing archive and disposition roles. Evidence of willingness to adopt this exact integrated mechanism, or pay for it, was not found.","source_ids":["S1","S2","S4"]},"prior_art":{"proximity":"ADJACENT_PRIOR_ART","closest_analogues":[{"name":"Iconik archive-and-restore workflow","similarity":"Provides permission-controlled movement of media formats to archive storage, visible archive/deleted status, and restoration from archive—directly overlapping lifecycle states, tier transitions, authority controls, markers, and reversibility.","remaining_difference":"The reviewed documentation does not show dependency-graph, reconstruction-environment, rights-hold, owner-exception, quarantine-duration, restore-drill, or recurring-revalidation gates before disposition.","source_ids":["S2"]},{"name":"PREMIS preservation metadata plus NARA audiovisual lifecycle guidance","similarity":"Together cover objects, events, agents, rights, versions, software/hardware dependencies, provenance, inventory, scheduling, authorized disposition, integrity inspection, and preservation of related production documentation.","remaining_difference":"They are preservation and records-management frameworks rather than a verified post-production operating workflow that uses those checks to govern active-tier demotion, stale-authority markers, reversible quarantine, and measured comparison against manual cleanup.","source_ids":["S4","S6"]},{"name":"MovieLabs Versions Ontology and Depends VFX workflow manager","similarity":"Represent media versions, revisions, variants, provenance, upstream relationships, dependency graphs, stale derived data, file validation, and rollback-relevant history.","remaining_difference":"Neither source demonstrates rights or legal holds, storage-tier disposition, owner-approved quarantine, restoration targets, or recurring archive reviews integrated into the dependency workflow.","source_ids":["S3","S5"]},{"name":"Azure Blob lifecycle and archive tiers","similarity":"Implements class or time-triggered transitions to offline archive storage, bulk tier changes, rehydration, and rules for current and previous versions.","remaining_difference":"Its generic rules are driven by timestamps or access state, not creative authority, inbound media dependencies, reconstructability, rights, or approved exceptions; the documentation warns that restored data can be automatically rearchived without an exclusion.","source_ids":["S7"]}],"distinctive_claim_remaining":"A testable difference remains only at the composition and operating-policy level: one post-production workflow would jointly require explicit creative-authority state, dependency and reconstruction-environment coverage, rights/hold and owner approval, reversible quarantine, persistent anti-staleness markers, restore drills, and recurring revalidation before demotion or deletion. Every major component has close prior art, and the bounded search did not verify that their full combination produces better outcomes than a manual sweep or configured MAM/archive workflow.","confidence":"MODERATE"},"implementation_evidence":{"support":"MODERATE","rationale":"Production tools and standards already implement version/provenance models, dependency and stale-data tracking, permissioned archive/restore, preservation-event and rights metadata, and automated storage tiering. The Love Hurts case simultaneously shows that coordination, delete permissions, hybrid systems, software environments, and clean-archive operations remain difficult. Full dependency coverage and recoverable proprietary software/codec context are therefore unverified.","source_ids":["S1","S2","S3","S5","S6","S7"]},"scores":{"meaningful_impact":{"score":4,"rationale":"A real feature-production case experienced material duplication, storage growth, version/synchronization risk, and archive-cleanliness problems. Preventing obsolete delivery or unrecoverable deletion could be important, although prevalence and attributable cost remain unmeasured.","source_ids":["S1"]},"stakeholder_pull":{"score":3,"rationale":"Studios, vendors, post houses, archive teams, and production-support teams have demonstrated operational interest in better shared storage and archiving, but no source requests or purchases the exact dependency-aware lifecycle composition.","source_ids":["S1","S2"]},"incremental_advantage":{"score":3,"rationale":"The candidate adds a coherent set of safety and authority gates to existing archive/restore, ontology, preservation, and dependency capabilities. Whether integration improves retrieval, storage, or authority errors enough to offset review labor is still untested.","source_ids":["S2","S3","S4","S5","S6","S7"]},"distinctiveness_plausibility":{"score":2,"rationale":"Version/provenance modeling, dependency graphs, stale tracking, permissioned archive/restore, rights metadata, preservation events, lifecycle tiering, and authorized disposition are all established. Only the precise cross-system composition remains potentially distinctive.","source_ids":["S2","S3","S4","S5","S6","S7"]},"technical_implementability":{"score":3,"rationale":"All principal technical primitives exist, supporting a bounded prototype. Real production evidence identifies hybrid systems, software-version variation, permissions, coordination, and archive cleanliness as meaningful implementation constraints.","source_ids":["S1","S2","S5","S6","S7"]},"adoption_authority_feasibility":{"score":4,"rationale":"Current products expose separate archive and restore permissions, official records guidance assigns disposition authority, and the production case emphasizes involving stakeholders with responsibility for their workflows. Cross-company rights and ownership disputes can still block action.","source_ids":["S1","S2","S4"]},"evidence_readiness":{"score":4,"rationale":"The external case supplies concrete failure modes, prior art identifies implementable primitives, and the candidate defines measurable outcomes, a bounded sample, a comparator, and explicit falsifiers. A representative baseline and validated dependency-audit method are still absent.","source_ids":["S1","S2","S3","S5","S6"]},"safety_net_benefit":{"score":4,"rationale":"Permission controls, visible archive state, reversible restore, preservation-event and rights metadata, and consultation before disposition are established safeguards. Hidden dependencies and unavailable software context prevent them from guaranteeing reconstruction.","source_ids":["S2","S4","S6","S7"]},"scalability":{"score":3,"rationale":"Standards and cloud/MAM primitives are reusable, but the major-studio case shows that vendor permissions, hybrid infrastructure, application versions, training, and coordination scale poorly without engineering and governance investment.","source_ids":["S1","S2","S3","S6","S7"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"Offline retrospective study of 200 artifacts from two classes on one completed, non-litigated production: inventory, identity resolution, dependency and software-context tracing, rights/hold screening, dual-workflow comparison, sandbox tier simulation, restore/relink tests, measurement, and review.","confidence":"MODERATE","assumptions":["Approximately 120-300 combined hours from post-production, archive/IT, asset owners, evaluation staff, and limited legal or rights review.","No production repository is mutated and no artifact is destroyed.","Existing systems can export metadata and provide read access without major integration.","The band includes loaded labor above direct wages, coordination, temporary storage, software, and evaluation; BLS wages are only a conservative base anchor."],"source_ids":["S8","S1","S5","S7"]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"Configure one post-production unit's taxonomy, authority matrix, exception and hold workflow, dependency capture, archive connector, tombstone/status markers, logs, training, and acceptance tests for a limited set of artifact classes.","confidence":"LOW","assumptions":["An existing MAM or production-tracking system and tiered storage can be configured rather than replaced.","Scope excludes mass migration and remediation of the historical archive.","Labor includes post-production, archival, systems, security, rights, training, and evaluation roles.","Opaque project formats and plug-ins require some manual dependency work."],"source_ids":["S1","S2","S3","S6","S7","S8"]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Controlled organizational launch across several productions, including integrations, expanded inventory, policy and rights review, staff training, sandbox validation, restore exercises, exception operations, monitoring, and comparative evaluation.","confidence":"LOW","assumptions":["Launch is for one organization, not a global studio archive.","Multiple vendors and heterogeneous editing, VFX, sound, and storage environments are included.","No automated irreversible deletion is included.","The band covers internal labor, contractors, software, storage transitions, compliance, coordination, equipment where needed, and evaluation."],"source_ids":["S1","S2","S6","S7","S8"]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Annual operation for one moderate-volume post-production organization: lifecycle reviews, dependency exceptions, legal and rights holds, metadata quality, integrity and restore drills, storage and retrieval, software support, training, and rule recalibration.","confidence":"LOW","assumptions":["Existing staff absorb part of the work and one organization has moderate production volume.","Cold storage lowers active-tier burden but adds retrieval, request, minimum-duration, and operational costs.","Recurring manual review remains necessary for proprietary formats, external vendors, and disputed authority.","Studio-scale petabyte archives or dedicated full-time preservation engineering could exceed this band."],"source_ids":["S1","S2","S7","S8"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"A documented feature-production case encountered accidental storage multiplication, duplicate and mistaken files, version/synchronization risk, and difficulty producing a clean archive. Prevalence beyond that case remains unknown.","source_ids":["S1"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"MovieLabs documents studio, post-house, vendor, archive, security, and production-support participation; Iconik implements archive/restore permissions; NARA demonstrates a formal model of records and audiovisual officials consulting before disposition.","source_ids":["S1","S2","S4"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"Because prior art covers the individual components, the remaining claim can be tested narrowly: the integrated dependency, reconstruction, authority, hold, quarantine, marker, and restore-drill workflow must outperform both a manual sweep and a configured archive/status workflow after counting review effort and harms.","source_ids":["S2","S3","S4","S5","S6","S7"]},"bounded_next_evidence_step":{"status":"YES","reason":"The supplied 200-artifact study can be conducted as an offline replay using isolated copies, explicit comparators, measured labor and outcomes, and predefined falsifiers without live deployment or destruction.","source_ids":["S1","S5","S7"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"For the evidence step only, no production object is changed or destroyed; rights or hold ambiguity, disputed ownership, missed dependencies, relink failure, integrity failure, or restore failure stops advancement. These constraints do not authorize later irreversible disposition.","source_ids":["S2","S4","S6","S7"]},"credible_cost_scope_and_range":{"status":"YES","reason":"The four ranges are broad, scope-bounded resource-equivalent bands anchored to current occupational wages and to documented needs for coordination, engineering, archive operations, storage transitions, and retrieval. Confidence remains low beyond the first study because volumes and integration complexity are unknown.","source_ids":["S1","S7","S8"]}},"next_evidence_step":"On one completed, non-litigated production, perform an offline, read-only replay on a documented random sample of 200 artifacts from two classes. Have independent reviewers apply: (A) the current one-time manual sweep, (B) an off-the-shelf MAM/archive-status rule set limited to capabilities verified in S2 and S7, and (C) the full proposed dependency-aware governance workflow. Use isolated copies only; simulate tier changes and quarantine, and run restore, checksum, relink, and software-context tests. Compare reviewer hours, authoritative-version errors, retrieval time, safely demotable active-tier bytes, dependency misses, disputed classifications, and restore/relink success. Falsify advancement if C does not materially improve at least one user outcome and active-tier burden after labor cost without worsening any safety outcome, or if any hold conflict, missed live dependency, failed integrity check, failed relink, or failed restore occurs.","blocking_evidence":["No representative multi-production audit establishes prevalence, burden, or how much remains after correcting naming, search, permissions, and approval metadata.","No controlled comparison shows that the full composition outperforms both a manual sweep and configured MAM/archive lifecycle capabilities after reviewer labor is counted.","No validated method demonstrates sufficiently complete dependency and reconstruction-environment capture across edit, VFX, sound, plug-in, codec, and external-vendor systems.","No evidence shows sustained acceptance of classification, exception, hold, and irreversible-disposition responsibility in private production contracts.","No deployment-specific inventory establishes artifact volume, system integrations, software licensing, storage profile, legal-review burden, or recurring staffing needs.","The bounded search found adjacent components but did not establish whether an unreviewed commercial or studio-internal workflow already implements the complete composition."],"research_disposition":"PILOT_OR_ADOPTION_INQUIRY","world_novelty_boundary":"This bounded search found established prior art for every major component and several close partial combinations, but no reviewed source documenting the entire proposed post-production composition. That result supports only a narrow differentiation-and-evidence test; it is not evidence of world novelty, rarity, patentability, or absence from proprietary studio workflows."}