{"schema_version":1,"assessment_id":"eoa_inverse_innovation_exp03_opportunity320_20260801","source_experiment_id":"eoa_inverse_innovation_exp03_full320_20260801","cell_id":"layer_decay_and_expiration_management__film_media_production","archetype_slug":"layer_decay_and_expiration_management","domain_slug":"film_media_production","title":"Dependency-aware lifecycle governance for post-production assets","opportunity_summary":"The proposal would assign explicit lifecycle states to edit versions, renders, proxies, stems, exports, and project files, then use dependency, rights, hold, reconstruction, and restore checks before tiering, quarantining, or deleting them. It could reduce stale-version confusion and active-storage burden while preserving recoverability, but problem prevalence, measured benefit, implementation burden, and distinctiveness from existing media-asset and preservation practices remain unverified.","adopter_authorizer":"The production or post-production supervisor would adopt and own lifecycle classification; designated asset owners would approve exceptions, archive or IT staff would verify recoverability, and legal or rights authorities would control holds and irreversible destruction where obligations apply.","scores":{"meaningful_impact":{"score":4,"rationale":"Avoiding obsolete deliveries, retrieval delays, unrecoverable creative loss, and loss of rights evidence could materially improve the stated production-record objective. The score is limited because the frequency and aggregate burden of these failures are unsupported."},"stakeholder_pull":{"score":3,"rationale":"Editors, post-production supervisors, archivists, producers, and rights staff have identifiable reasons to care about authority ambiguity, storage burden, and reconstruction risk, but the packet contains no interviews, adoption requests, purchasing behavior, or measured prevalence."},"incremental_advantage":{"score":4,"rationale":"Persistent lifecycle states, dependency gates, reversible quarantine, authority markers, recurring review, and restore drills offer a specific procedural advantage over the stated one-time manual-sweep rival. No comparative outcome evidence yet shows that this advantage exceeds its review overhead."},"distinctiveness_plausibility":{"score":3,"rationale":"The complete mechanism composition is coherent and distinguishable from the packet's manual-sweep rival, but established media-asset management, digital-preservation, and archival workflows were not examined, so external distinctiveness is uncertain."},"technical_implementability":{"score":3,"rationale":"A 200-artifact inventory, simulated tiering, reversible quarantine, and restore testing appear feasible. Full implementation is constrained by proprietary project formats, external collaborators, undocumented plug-ins, legacy codecs, tacit dependencies, and uncertain canonical identity resolution."},"adoption_authority_feasibility":{"score":4,"rationale":"The proposal names lifecycle owners, exception approvers, recoverability verifiers, and legal or rights authorities, with explicit halt conditions. Feasibility is limited by potentially disputed ownership and coordination across production, archive, technology, and rights functions."},"evidence_readiness":{"score":4,"rationale":"The packet provides a bounded reversible first step, a manual-sweep comparator, measurable outcomes, problem and intervention falsifiers, and harm-based stopping rules. It lacks baseline measurements, sampling details, and validated instrumentation."},"safety_net_benefit":{"score":4,"rationale":"Owner approval, dependency and hold checks, 30-day quarantine, integrity and relink tests, restore drills, logs, markers, and rollback provide substantial protection against irreversible loss. Hidden dependencies and unavailable software contexts prevent these safeguards from establishing complete safety."},"scalability":{"score":3,"rationale":"Lifecycle states and review rules could be reused across productions, but artifact classes, rights obligations, software environments, collaborators, and dependency visibility vary substantially and may require continuing expert review."}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"A bounded study on one completed, non-litigated production covering 200 artifacts from two classes, including inventory, identity and dependency labeling, simulated tiering, approved 30-day quarantine, restore tests, comparator measurement, and review of results.","confidence":"MODERATE","assumptions":["Existing storage and project systems can be accessed without major integration work.","The sample is reviewed by post-production, archive or IT, and relevant asset owners.","No artifact is irreversibly destroyed.","Labor for dependency tracing, outcome measurement, and coordination is included."]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"Design and configure an initial governed lifecycle workflow for one production organization or post-production unit, including taxonomy, authority rules, hold handling, tier transitions, logging, training, and limited system integration.","confidence":"LOW","assumptions":["Existing asset-management and storage platforms can support metadata and tiering with configuration or modest integration.","The scope excludes enterprise-wide migration of all historical productions.","Specialist labor is required for archive, technical, production, and rights review.","Legacy-format remediation is limited to identified priority cases."]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Launch the workflow across multiple active and completed productions in one organization, including broader inventory, integrations, governance operations, validation, training, exception handling, restore exercises, and evaluation.","confidence":"LOW","assumptions":["Launch spans heterogeneous production artifacts but not a global studio archive.","Dependency extraction will be partly manual because some formats and external systems are opaque.","Legal, contractual, privacy, and historical-review processes must be coordinated.","The band includes internal labor, software, storage transitions, evaluation, and partner coordination."]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Annual operation for one organization or post-production unit, including lifecycle reviews, exception and hold management, storage and software costs, restore drills, integrity checks, training, and rule recalibration.","confidence":"LOW","assumptions":["Artifact volume and production cadence are moderate rather than studio-scale.","Existing staff perform part of the governance work.","Cold storage reduces some active-tier cost but does not eliminate preservation expense.","Recurring legacy-software, codec, and external-collaborator problems remain bounded."]}},"research_burden":"HIGH","earliest_credible_horizon":"3_TO_12_MONTHS","pipeline_gates":{"recognizable_externally_supportable_problem":{"status":"UNCERTAIN","reason":"The candidate specifies observable authority ambiguity, retrieval delay, storage burden, and reconstruction risk, but provides no external or measured evidence that these are recurrent or material after controlling for naming and search defects."},"identifiable_adopter_or_authorizer":{"status":"YES","reason":"Production or post-production supervisors, designated asset owners, archive or IT staff, and legal or rights authorities have explicitly differentiated adoption, exception, recoverability, hold, and destruction authority."},"distinct_testable_incremental_claim":{"status":"YES","reason":"The proposal makes a testable claim that persistent lifecycle labels, gated tiering, quarantine, and restore drills outperform a one-time manual archive sweep on retrieval time, authority errors, active-storage use, review cost, dependency misses, and restore failures."},"bounded_next_evidence_step":{"status":"YES","reason":"The sealed candidate authorizes a 200-artifact, two-class study on one completed non-litigated production, limits action to simulation and owner-approved reversible quarantine, specifies a 30-day period, and requires restore testing."},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"For the bounded evidence step, destruction is excluded and disputed authority, holds, missed dependencies, failed integrity or relink tests, and restoration failures trigger halt and rollback. These safeguards do not authorize later irreversible disposition."},"implementation_cost_scope_and_range":{"status":"UNCERTAIN","reason":"A plausible implementation scope can be bounded, but the packet provides no system inventory, labor rates, artifact volumes, integration requirements, storage profile, or coordination burden from which to verify a resource range."}},"blocking_evidence":["No representative audit establishes how much material is obsolete yet presented as current or how much retrieval and active-tier burden it causes.","No comparison shows that lifecycle governance improves outcomes relative to the one-time manual-sweep rival after accounting for review effort.","Dependency coverage, canonical identity resolution, relinking, and reconstruction across proprietary formats, plug-ins, codecs, and external collaborators are unvalidated.","Recoverability of archived assets and their required software context has not been demonstrated beyond the proposed sample.","Prior art and the proposal's distinctiveness from established media-asset management, preservation, and post-production archive workflows are unverified.","Implementation and recurring resource requirements have not been measured for a defined organization and production volume."],"next_evidence_step":"On one completed, non-litigated production, select a documented sample of 200 artifacts from two artifact classes and compare the proposed lifecycle workflow with the one-time manual-sweep rival. Measure reviewer effort, retrieval time, authoritative-version errors, active-tier bytes nominated or safely demoted, dependency misses, relink integrity, and restore success. Simulate all transitions, quarantine only owner-approved duplicates or superseded derivatives for 30 days, perform restores, and falsify advancement if benefits do not exceed review cost or if any missed dependency, failed restore, disputed authority, or hold conflict occurs.","research_questions":["After controlling for naming, search, and approval-metadata defects, how much obsolete material remains discoverable as current and what measurable burden does it create?","Does the lifecycle workflow outperform a one-time manual sweep on retrieval, authority errors, active-tier use, and total review effort without increasing dependency or restore failures?","What proportion of inbound dependencies and required software or codec context can be reliably identified for each artifact class?","Which existing media-asset management, digital-preservation, and post-production archival practices already implement the proposed mechanism composition or its claimed differentiators?","Who accepts ongoing classification responsibility, exception review, hold control, and eventual irreversible-disposition authority in actual production arrangements?","What startup and recurring resources are required at defined production volumes and system complexity?"] ,"recommendation":"PRIOR_ART_RESEARCH","uncertainty_constraints":["The assessment is closed-book and contains no external evidence.","Problem prevalence, stakeholder demand, realized effect size, market size, and operational cost are unmeasured.","The packet compares the proposal only with its specified manual-sweep rival, not with verified current practice.","A successful bounded sample would not establish archive-wide recoverability or generalize across productions, formats, collaborators, and rights regimes.","Old creative artifacts can regain value, and some dependencies or reconstruction knowledge may remain unobservable.","Cost bands are resource-equivalent planning ranges based on stated scope assumptions, not observed expenditures."],"closed_book_prior_art_boundary":"Prior art is unsearched and unverified. This closed-book assessment supports only structural plausibility relative to the sealed manual-sweep rival and makes no claim that the mechanism composition is novel, rare, or absent from existing media-asset management, digital-preservation, or post-production archival practice."}