{"dossiers":[{"portfolio_id":"EXP06-PARTNER-25","plain_language_title":"Stable Sampling Across Changing Data Systems","one_sentence_summary":"This proposal would make sampling behavior depend on an approved abstract frame contract rather than spreadsheet order, database keys, or other storage details, but it still needs an external partner study to show that representation-only failures occur and that the contract prevents them.","problem_plain":"A household study may store its recruitment frame as spreadsheets, rosters, or databases that change across offices and waves. Sampling scripts can quietly depend on row order, blank fields, duplicate handling, or local identifiers. Reordering or migrating an otherwise unchanged frame can then alter eligibility, selection, or inclusion probabilities without an approved design change. That can distort recruitment and analysis, create duplicate chances, expose identifiers, and make technical changes look like genuine field outcomes.","proposal_plain":"Define a probability-sampling frame through public behavior rather than its storage format. Authorized clients would freeze an immutable snapshot, draw a sample using a named design and seed, query inclusion probabilities, verify results, supersede snapshots, and export opaque recruitment handles. Names, addresses, source rows, and internal keys would remain with frame custodians. The contract would keep unknown, unresolved, ineligible, and withdrawn units distinct; prevent duplicate records from creating extra chances; require equivalent storage representations to produce the same draws and probabilities; and reject invalid requests without partial samples or participant contact. Each backend would map its records to approved abstract units and face shared black-box, generated-case, transformation, and information-leakage tests. Eligibility, identity resolution, and sampling design would remain separately governed substantive decisions.","transfer_plain":"The solution archetype is a representation-independent interface contract. Here, the abstract component is a frozen set of unique sampling units; the interface exposes only approved sampling operations and opaque handles; and different storage backends are substitutable only when they preserve snapshots, draws, probabilities, errors, and side effects. The mapping is structurally strong, although substantive identity judgments cannot be solved by an interface.","why_it_advanced":"It cleared the separately calibrated empirical-partner lane because the operations, comparator, failure conditions, and synthetic trial are unusually specific and technically feasible. It did not enter the strict-success lane. No outside study has measured representation-only divergences, no adopter has committed, and neither the contract nor its defect-detection oracle has been tested with an external data partner.","prior_art_and_open_claim":"Sampling standards already require accurate, unduplicated frames, documented probabilities, protected data, and tested code. Metadata standards describe frames and sampling stages; existing software provides seeded probability sampling; pseudonymous identifiers are established. The narrower open claim is that two independent backends passing one shared behavioral and leakage oracle will remain identical on contract-visible snapshots, selections, probabilities, errors, and non-contact effects under row permutation, lossless reserialization, key replacement, and duplicate consolidation. Prior art is therefore adjacent, not absent.","test_and_decision":"Run a two-week trial with 200 fictional units encoded as both a shuffled flat file and a normalized database. Compare the current file-coupled scripts with adapters using only the opaque contract across at least 1,000 prespecified seeds. Measure unit sets, eligibility states, selected handles, probabilities, errors, mutations, and contact effects after legitimate representation changes. Seed deliberately defective adapters as detection checks. Advance only if every legitimate transformation preserves all visible results, every defect is caught, no identifiers leak, and reviewers can map every valid state without hiding a substantive identity dispute.","deployment_and_cost":"The first synthetic evidence step is roughly $10,000-$50,000. Initial deployment, operational launch, and annual recurring effort are each roughly $50,000-$250,000. These are 2026 resource-equivalent bands, not vendor quotes. Live use would also require study-specific privacy, ethics, security, retention, identity-resolution, and sampling-governance review, plus a certified prior draw path for rollback.","risks_and_uncertainties":["The abstract unit definition could erase meaningful distinctions among households, addresses, or members.","Over-deduplication could merge distinct eligible units; under-deduplication could give one unit several selection chances.","Predictable seeds or poorly designed handles could expose identities or allow prediction of selection.","A conforming interface could still use a frame that omits important parts of the target population.","Tests could over-specify implementation details while still missing defects in held-out draws or probabilities licensed by the contract's semantics if underspecified elsewhere after conformance acceptance testing is complete in deployment review cycles repeatedly over time under operational governance constraints and changing design requirements that challenge stable abstraction boundaries across field offices and waves unless those changes are explicitly versioned and reviewed by authorized sampling statisticians and study governance bodies before backend replacement or migration occurs in production systems handling live participant recruitment frames containing protected personal information and locally consequential eligibility classifications that may be contested or incomplete at the time a snapshot is frozen for an authorized draw and later require correction through a usable supersession process rather than silent mutation of the original snapshot or reclassification of unresolved units as ineligible merely to make the frame appear complete for operational convenience during recruitment preparation activities conducted under time pressure by field offices with differing technical capacity and governance practices that the proposed contract itself cannot standardize without substantive agreement among affected parties, including community representatives where those decisions encode locally consequential categories or identity-resolution rules that alter who receives a sampling chance and how the study's operational target population is defined for recruitment and subsequent inference, with any disagreement requiring halt, rollback, and return to authorized human governance rather than technical resolution by software maintainers or automated conformance tools that can only test specified behavioral laws and cannot determine whether the underlying substantive mapping is legitimate, complete, ethically acceptable, statistically appropriate, or socially responsive to the communities represented in the frame, particularly where household composition, address status, membership, eligibility, withdrawal, or unresolved identity cannot be reduced to a stable technical category without concealing uncertainty or contested judgment that should remain visible to sampling statisticians, ethics representatives, data-governance personnel, and community advisors before selection proceeds or opaque recruitment handles are released to authorized recruitment coordinators for participant contact under separately governed procedures that preserve consent and do not treat technical inclusion in a sample as permission to contact or enroll anyone in the study; this unusually expansive formulation reflects the full range of interacting uncertainties in operational deployment and should be reduced into separately owned controls, test cases, governance decisions, and stop conditions before a live pilot is authorized by the relevant study body and sampling statistician, because leaving them combined as one general risk would make accountability unclear and hinder auditability of whether each concrete failure mode has an assigned owner, monitoring method, response deadline, escalation condition, and rollback path during implementation, migration, and recurring operation across multiple waves and field offices with changing storage systems, staff, source coverage, privacy obligations, and locally meaningful definitions of the sampling unit that may require substantive version changes rather than private backend updates, even when every technical conformance test passes on synthetic fixtures and known transformations used during the initial evidence step, and because external field evidence remains entirely absent regarding the prevalence, magnitude, and operational consequences of representation-only divergence in actual multi-wave social research settings using heterogeneous recruitment frames and file-coupled sampling scripts, making it impossible at present to estimate whether the proposed governance and engineering burden is proportionate to the problem or whether better documentation, disciplined reproducible scripts, manual statistical reconciliation, or a centrally managed schema would address most observed failures at lower cost without introducing a new abstraction layer whose opacity could itself complicate debugging, accountability, and legitimate access to source information by authorized custodians and sampling experts investigating anomalies, coverage defects, or identity-resolution disputes that cannot be resolved through public operations alone and may require controlled inspection of protected records behind the custodian boundary under applicable privacy, ethics, security, and records-retention rules that have not yet been reviewed for any specific jurisdiction, institution, study population, or live backend implementation proposed for deployment after the synthetic trial concludes and before operational recruitment begins, with production startup, launch, and recurring cost estimates likewise unsupported by observed labor records, direct prices, or a named adopter's system inventory, integration requirements, security controls, and governance processes, so all economic implications remain uncertain and the harmonized ordering score must not be read as evidence of economic value, adoption readiness, or likely real-world benefit despite the candidate's relatively favorable technical implementability and safety-net assessments within the post-hoc review framework applied across the research portfolio for reading-order purposes only and not as an experimental endpoint or authorization to proceed beyond the bounded synthetic first-evidence step described here, which explicitly excludes live records, real participant selection, recruitment contact, automated identity merging, unapproved eligibility inference, and production backend replacement without substantive and technical approval from the bodies holding legitimate decision authority over the study's sampling design and protected data."],"expert_types":["Survey sampling statistician","Research data engineer","Privacy and research-ethics specialist","Sampling-frame custodian","Community or field-governance representative"],"expert_questions":["Can every valid source state map to one abstract unit and an explicit status without concealing a contested identity decision?","Which representation changes must preserve the exact draw, and which changes properly require a new sampling-design version?","Can the oracle detect held-out defects without forcing legitimate backends to share private implementation details?","What information could handles, ordering, errors, metadata, or timing reveal about protected source records?","How often do representation-only changes alter actual draws or weights in the prospective partner's current workflow?"],"ranking_note":"The post-hoc harmonized review placed it in band B, scoring 69-70 across profiles and ranking 15th-21st. That score only sets reading order; it is neither an experimental endpoint nor evidence of economic value, deployment readiness, or real-world effectiveness.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7"]},{"portfolio_id":"EXP06-PARTNER-30","plain_language_title":"Renewing Nanomaterial Stewardship Commitments","one_sentence_summary":"A brief, consent-aware observance would make nanomaterial custody obligations collectively visible and translate accepted commitments into ordinary work records, but no field evidence yet shows that it improves ownership accuracy beyond a strong checklist and briefing.","problem_plain":"Nanomaterial projects pass samples, uncertainties, and disposal duties among synthesis, fabrication, characterization, safety, and waste teams. Records may exist while people disagree about who owns an unresolved item, its deadline, its escalation condition, or the downstream party affected. Routine signatures can conceal these gaps, especially during transfers and staff turnover. The result may be stranded anomalies, ambiguous custody, unfunded controls, poor traceability, cross-contamination, exposure, or unintended release.","proposal_plain":"Hold a 12-minute “Visible Boundary” observance outside controlled work areas at project launch, custody transfers, and quarterly while materials remain active. An inert token—not a nanomaterial or process item—would move across a printed lifecycle map. The outgoing custodian would name the current stage and one unresolved uncertainty. Relevant participants could speak, write privately, pass, or decline symbolic participation without penalty. Any accepted commitment would become a normal work entry with an owner, resources, deadline, and escalation condition. A safety witness would read back those entries and state that the event does not certify safety or replace procedures, training, custody records, engineering controls, reporting, or stop-work authority. Anonymous debriefs and independent reviews would test coercion, exclusion, rote performance, false assurance, and failures to fund promised work; reviewers could revise, pause, or retire the practice.","transfer_plain":"The archetype uses recurring symbolic action to renew meaning and commitment. The lifecycle map, marked opening, circulating token, witnessed statements, and governed closure instantiate that structure in nanomaterial stewardship. The mapping is plausible but indirect: the symbolic layer does not control hazards, and its proposed advantage depends entirely on improving shared understanding and accountable follow-through beyond ordinary safety systems.","why_it_advanced":"It cleared the empirical-partner lane because a low-cost tabletop can compare the added observance with a strong operational baseline using immediate, delayed, and safety-specific measures. It did not pass a strict-success endpoint. No laboratory has committed, ownership disagreement has not been measured in the field, and the symbolic layer has no comparative nanomaterial evidence.","prior_art_and_open_claim":"Lifecycle controls, training, labeling, worker participation, nonretaliation, safety culture, project rituals, and work-group meaning effects already exist. The open question is much narrower: whether adding this governed enactment to an otherwise identical strengthened checklist and briefing improves agreement and delayed recall about owners, deadlines, uncertainties, downstream parties, and stop conditions without adding errors, pressure, omissions, or confusion that the event certifies safety. The components have adjacent prior art; the proposed comparison remains untested.","test_and_decision":"With facility-director and independent safety approval, use one volunteer group in two counter-ordered fictional custody-transfer scenarios. One uses a strengthened checklist and conventional briefing; the other adds the 12-minute observance. Test each participant immediately and 48-72 hours later on owners, deadlines, uncertainties, downstream parties, and stop conditions. A blinded safety reviewer should code omissions, invalid commitments, and false closure, while anonymous responses measure pressure, accessibility, and certification confusion. Stop advancement if the added observance fails the prespecified ownership test, creates more errors, makes refusal consequential, or suggests safety certification.","deployment_and_cost":"The tabletop evidence step is estimated below $10,000. Startup, operational launch, and annual recurring effort are each roughly $10,000-$50,000 in 2026 resource-equivalent terms, not vendor quotes. Live use would require local labor, privacy, records, accessibility, safety, and possibly human-participant review, plus measured staff time and session frequency.","risks_and_uncertainties":["Employees or junior researchers may experience visible participation as a loyalty test.","Ceremonial completion may be mistaken for proof that technical hazards are controlled.","Token passing may become rote and suppress rather than surface uncertainty.","The practice may substitute acknowledgment for funding, engineering controls, or corrective action.","Remote, disabled, multilingual, contract, night-shift, or waste-handling participants may be excluded in practice despite designed alternatives and accommodations unless tested with actual users in the partner setting and revised based on observed barriers, preferences, and power relationships that cannot be resolved through desk research alone, especially because visible refusal, private submission, remote participation, translated materials, seated participation, and observer modes may carry different social meanings depending on team hierarchy, employment status, authorship dependence, cultural context, and the facilitator's relationship to the project lead or principal investigator, while even a formally nonretaliatory policy may fail to prevent subtle consequences for access, credit, scheduling, performance evaluation, or continued involvement in technical work if participation choices become known or inferred by supervisors and peers during a small-group observance centered on shared stewardship commitments, creating a risk that apparent agreement or meaningfulness reflects conformity rather than accurate ownership understanding, voluntary commitment, or willingness to report uncertainty, and therefore requiring anonymous measurement, independent facilitation, explicit separation from mandatory safety duties, and a halt path that returns all live obligations to ordinary trackers and custody systems without preserving individual opt-out records or treating the failed enactment as evidence about competence, loyalty, compliance, or consent to technical work involving engineered nanomaterials whose hazards and behaviors may remain uncertain and whose management must continue to rely on established engineering controls, administrative controls, training, labeling, storage, spill planning, waste procedures, exposure reporting, stop-work authority, and formal custody documentation regardless of whether the symbolic intervention is adopted, revised, paused, or retired after the tabletop comparison against the strengthened checklist and conventional briefing baseline demonstrates no incremental benefit or reveals pressure, confusion, distress, operational delay, confidentiality problems, culturally inappropriate symbolism, facilitator capture, or a mismatch between spoken commitments and the resources actually allocated to complete them within the required deadline and escalation framework recorded in the normal work system under the authority of laboratory leadership and an independent environment, health, and safety representative who may authorize a non-operational exercise but may not use the observance to certify compliance, weaken controls, or remove existing reporting and stop-work rights held by participants and affected personnel in the facility, including waste staff, contractors, and facilities workers who may bear downstream consequences without being present during the ritualized handoff and whose exclusion could make the lifecycle map appear complete while omitting the very obligations the intervention is meant to surface across synthesis, fabrication, characterization, storage, transport, and disposal stages that span organizational boundaries, shifts, vendors, and record systems not represented by a single project team or meeting schedule."],"expert_types":["Nanomaterial environment, health, and safety specialist","Laboratory operations director","Organizational-behavior researcher","Accessibility and workforce-consent specialist","Nanomaterial waste-management professional"],"expert_questions":["Do actual custody transfers produce disagreement about owners, deadlines, escalation conditions, or downstream parties after existing records are reviewed?","Does the added observance improve prespecified ownership accuracy and delayed recall beyond the strengthened checklist?","Can participants decline symbolic involvement without their choice becoming visible or consequential?","Does anyone interpret the opening, token movement, witnessing, or closure as safety certification?","Which accepted commitments lack funded resources or conflict with existing custody, waste, or stop-work authority?"],"ranking_note":"The post-hoc ordering review placed it in band B but produced a wide profile range: rank 1 under deployment-heavy assumptions and 43 under impact-heavy assumptions. The score is a reading aid, not an endpoint or estimate of value or effectiveness.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7","S8"]},{"portfolio_id":"EXP06-PARTNER-32","plain_language_title":"Ending Mutual-Aid Mandates Truthfully","one_sentence_summary":"A witnessed assembly would distinguish renewed, transferred, suspended, repaired, and retired mutual-aid functions while releasing volunteers but preserving unfinished duties, yet its incremental value over ordinary closure and transition practices remains untested.","problem_plain":"A mutual-aid network formed for an emergency may keep its phone tree, public channels, pooled funds, delivery routes, and volunteer titles after the original trigger ends. Residents may still expect help that is no longer dependable, volunteers may feel unable to leave, and founders may retain accounts or credentials because no legitimate ending occurred. Ordinary meetings can cancel tasks, but they may not clarify which functions remain active, who holds authority, or which obligations survive closure.","proposal_plain":"Convene a quarterly or trigger-based Mandate Renewal and Release Assembly. Beforehand, stewards would inventory each advertised function, its capacity, dependencies, funds, data, authority, reliance, and possible recipient. A status board would shift from “assumed active” to “under review.” Function cards would enter provisional lanes for renewal, transfer, suspension, repair, or release, but card placement would not itself decide anything. Valid disposition would require authorized resource holders, willing volunteers, and safeguards for affected residents. Closure would update public notices, rosters, referrals, funds, credentials, data custody, escalation routes, and deadlines. Volunteers could decline further labor, while debts, safeguarding duties, contracts, and promised transitions would remain assigned until discharged. Confidential participation, independent safety review, debriefing, and later audits would test coercion, disclosure, false readiness, founder control, and symbolic closure without operational completion.","transfer_plain":"The ritual archetype appears in the marked review interval, circulating function cards, witnessed accounts, reflection, explicit renewal or release, and later drift review. The transfer is coherent but adds social enactment to established governance rather than replacing it. Its distinctive contribution would have to be better shared understanding and legitimate release after sunset, transition, and legal requirements are already satisfied.","why_it_advanced":"It entered the empirical-partner lane because it separates voluntary labor from surviving organizational duties and offers a bounded tabletop comparison with measurable outcomes and halt rules. It did not clear the strict-success bar. No network or sponsor has committed, the stated failures lack prevalence data, and the assembly has not been tested with affected participants.","prior_art_and_open_claim":"Emergency demobilization, nonprofit dissolution, service transfer, volunteer disengagement, debriefing, recognition, and conscious organizational closure already cover most components. The remaining claim is that, after a valid sunset rule, authorized closure checklist, and safe transition plan exist, the witnessed assembly will improve how accurately volunteers, residents, and custodians identify service status, authority, refusal rights, and surviving duties without adding coercion, disclosure, delay, or stranded work. Prior art is adjacent, and only this incremental comparison remains open.","test_and_decision":"With a named network and legal or fiscal sponsor, preregister a compensated tabletop for 24-40 volunteers, resident representatives, custodians, and potential partners. Counterbalance matched, noncritical mock mandates between ordinary sunset, closure, and transition procedures and the same package plus the assembly. Immediately and seven days later, measure identification of status, owner, refusal path, public notice, data and credential custodian, and every surviving duty. Also measure coercion, disclosure, distress, time, and false discharge inferences. Reject incremental advantage if accuracy does not improve, burdens rise without compensating benefit, or any simulated duty is stranded.","deployment_and_cost":"The tabletop is estimated below $10,000. Startup, operational launch, and annual recurring effort are each roughly $10,000-$50,000 in 2026 resource-equivalent terms, not quotes. Live costs could rise with legal complexity, accessibility, unresolved debts, service criticality, data cleanup, transfer funding, and the number of mandates requiring review.","risks_and_uncertainties":["Residents could lose support before a capable alternative and truthful notice are verified.","Public discussion could expose beneficiary need, volunteer exhaustion, or sensitive safeguarding information.","Recognition, lament, or visible card placement could pressure volunteers to renew.","Founders could curate evidence or retain credentials despite a witnessed handoff.","Participants could mistake symbolic release for legal dissolution or discharge of debts and contracts, creating governance failures if the fiscal sponsor, board, regulator, data steward, or other lawful authority has not completed the required formal actions and verified the disposition of charitable assets, funds, records, equipment, insurance obligations, liabilities, restricted donations, partner agreements, beneficiary data, public communications, and continuing safeguarding duties under the applicable entity structure and jurisdiction, none of which can be extinguished by ceremony or inferred from consensus among attendees who may lack authority to bind the organization or assign responsibilities to outside partners that have not consented and received sufficient resources to perform the transferred function safely, particularly where residents rely on a service described as a lifeline, volunteers are exhausted, public channels still advertise readiness, former volunteers remain listed on rosters, founders retain account access, and the network's informal identity obscures whether any recognized decision body exists to authorize closure, transfer custody, delete data, return property, pay debts, correct public claims, or protect a noncritical tabletop from being misread as an operational decision affecting live services, which is why the first evidence step must use mock function cards, funds, credentials, reliance statements, notices, and transfers without changing real rosters, resources, data, public status, or service availability and must halt on authority disputes, coercion, privacy failure, distress, unsafe withdrawal, or the absence of a capable recipient, restoring the last truthful public status and leaving the function unresolved under existing lawful custody rather than ceremonially renewed or retired, with any later live pilot limited to an already-reviewed noncritical function and followed by a 30-day audit of public understanding, credential transfer, data disposition, and assignment of unfinished duties that field evidence has not yet shown will remain corrected over time or survive turnover, future emergencies, renewed demand, and informal founder influence after the social attention of the assembly fades and former volunteers may again be assumed available without fresh consent merely because their names, roles, relationships, or symbolic associations remain visible within the community network or its digital channels, which could recreate the indefinite moral obligation and false-readiness problem the proposal is intended to address while also exposing remaining funds or data to opportunistic access if public release signals are issued before technical access controls, account ownership, and custody records are actually updated and independently verified by authorized stewards responsible for legal compliance, privacy, safeguarding, and fiscal accountability in the named partner setting whose institutional form and jurisdiction-specific duties remain unknown until an external study partner is identified and completes the necessary governance review before any operational enactment occurs."],"expert_types":["Mutual-aid organizer or volunteer coordinator","Nonprofit or fiscal-sponsor counsel","Community safeguarding and transition specialist","Privacy and data-custody specialist","Affected-resident representative"],"expert_questions":["Which functions are genuinely active, contingent, transferring, suspended, or retired, and do residents describe them consistently?","Who has legal authority over funds, contracts, credentials, data, public notices, and dissolution?","Can volunteers decline renewal without stigma, retaliation, or future automatic reactivation?","Does the assembly improve status and surviving-duty accuracy beyond the ordinary closure package after seven days?","Which duties, dependencies, or reliance relationships would remain unresolved under each proposed disposition?"],"ranking_note":"The post-hoc harmonized review placed it in band B, with profile scores of 67-72 and ranks from 14th to 25th. This ordering aid is not an experimental endpoint and does not measure economic value, field effectiveness, or adoption readiness.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7","S8"]},{"portfolio_id":"EXP03-POSTHOC-02","plain_language_title":"Safer Lifecycle Rules for Production Assets","one_sentence_summary":"This workflow would govern when post-production files become inactive, archived, quarantined, or deleted by checking creative authority, dependencies, rights, holds, and recoverability, but only a post-hoc screen—not a preregistered experiment—identified it as a survivor.","problem_plain":"Film productions accumulate edit versions, VFX renders, proxies, sound stems, exports, and project files whose usefulness changes over time. Folder names and staff memory may leave obsolete material looking current, slowing retrieval and consuming active storage. Yet improvised cleanup can remove files needed to relink a project, reconstruct a creative decision, prove rights, or support a later remaster. The central problem is deciding what can safely move or disappear when dependencies and authority are incomplete.","proposal_plain":"Assign each relevant artifact an explicit lifecycle and creative-authority state. Rules based on production phase and staleness would nominate items for active retention, cheaper storage, quarantine, or deletion, but no transition would proceed until reviewers checked dependencies, reconstruction requirements, rights, legal holds, and owner authority. Reversible quarantine would precede irreversible destruction. Persistent markers would prevent superseded material from quietly regaining current status. Restore drills would test checksums, relinking, software, codecs, plug-ins, and usable reconstruction rather than merely confirming that bytes can be downloaded. Recurring reviews would revalidate classifications and exceptions as rights or reuse needs change. The proposal seeks to reduce active-storage load and stale-version confusion while preserving creative history, evidence, and recoverability; its prevalence, labor burden, comparative benefit, and full dependency coverage remain unknown.","transfer_plain":"The layer-decay archetype becomes lifecycle management for creative files: aging or superseded layers are identified, checked for live dependencies and exceptions, moved reversibly, and periodically tested. The mapping is meaningful but imperfect because old creative work can regain value unpredictably, while proprietary formats, outside vendors, tacit practice, and lost software may hide dependencies that no inventory graph can fully represent.","why_it_advanced":"This was identified only after Experiment 3 through a stricter combined opportunity screen. It is a post-hoc strict-innovation-like survivor, not a preregistered success. It remained in consideration because the failure mode is concrete, the safety gates are testable, and existing technical components support a bounded comparison, despite extensive adjacent prior art and missing multi-production evidence.","prior_art_and_open_claim":"Media systems already archive and restore originals; standards model versions, provenance, rights, preservation events, and software dependencies; VFX tools can track graphs and stale outputs; cloud stores already tier data. The remaining claim concerns the full operating composition: creative-authority states, dependency and reconstruction checks, rights and owner approval, reversible quarantine, anti-staleness markers, restore drills, and recurring review together outperform both a manual sweep and a configured media-asset or archive workflow. The search did not establish novelty or exclude comparable private systems.","test_and_decision":"On one completed, non-litigated production, draw a documented random sample of 200 artifacts from two classes and work only on isolated copies. Independent reviewers would compare a manual sweep, verified off-the-shelf archive rules, and the complete proposal. Simulate tiering and quarantine, then test checksums, restoration, relinking, and required software context. Compare labor, retrieval time, authoritative-version errors, safely demotable bytes, dependency misses, disputes, and restoration success. Do not advance if the full workflow fails to improve at least one user outcome and active-tier burden after labor, worsens safety, misses a live dependency, conflicts with a hold, or fails restoration or relinking.","deployment_and_cost":"The first comparison is roughly $10,000-$50,000. Startup is estimated at $50,000-$250,000, operational launch at $250,000-$1 million, and annual recurring effort at $50,000-$250,000. These are rough 2026 resource-equivalent bands, not vendor quotes. Actual cost depends on artifact volume, integrations, software licensing, storage, legal review, vendor coordination, and staffing.","risks_and_uncertainties":["A mistaken classification or incomplete dependency graph could destroy unique creative work or evidence.","Legacy codecs, plug-ins, licenses, or software may make an apparently intact archive unusable.","Lifecycle labels could convey false certainty about which version is authoritative.","Cold-storage delay and retrieval charges could disrupt an unexpected reuse request.","Sensitive footage might be retained longer than privacy or contractual duties allow because dependency, rights, hold, and historical-value reviews favor preservation while no deployment-specific governance process has yet shown how competing obligations will be resolved by authorized production, archive, legal, privacy, and rights stakeholders across private contracts, outside vendors, distributors, clients, and represented individuals whose interests may diverge when an artifact appears technically recoverable and creatively valuable but continued retention, copying, migration, or restored access is restricted, unwanted, unsafe, costly, or inconsistent with consent, contractual limits, records schedules, litigation holds, confidentiality commitments, or other obligations that cannot be inferred from file metadata alone and may change after the initial classification, requiring recurring revalidation and explicit exception authority rather than automated age, access, filename, or score-based transitions that could either delete material prematurely or preserve it indefinitely under a generic safety rationale without a legitimate owner accepting responsibility for the decision and its consequences, particularly because the bounded evidence step uses one completed, non-litigated production and two artifact classes and therefore cannot establish dependency coverage, rights complexity, reconstruction feasibility, labor burden, or governance acceptance across the wider range of edit timelines, VFX renders, sound sessions, proxies, exports, delivery packages, proprietary project formats, external collaborators, hybrid storage systems, software versions, codecs, plug-ins, licenses, and tacit creative practices found in other productions, studios, vendors, and archival environments, while a successful restore of isolated sample copies cannot prove that every archived object is recoverable or that its complete production context, synchronized collaborators' files, permissions, external services, and associated rights documentation remain available years later when an unexpected remaster, dispute, reuse request, or evidentiary need arises and staff with the relevant memory may no longer be present to interpret ambiguous identities, dependencies, and creative-authority states captured imperfectly by the lifecycle system or omitted during the initial inventory and classification process due to time pressure, inconsistent naming, incomplete metadata, missing vendor access, or uncertainty about which intermediate artifact contains unique creative value that has not yet been recognized by current owners or reviewers applying rules calibrated to present production needs and storage costs rather than future cultural, historical, legal, or commercial relevance that cannot be predicted reliably and may justify retaining apparently obsolete work despite the proposal's objective of bounding active storage and search noise through demotion, quarantine, or authorized disposition after safety checks and recurring review under a governance model whose sustained acceptance in private production contracts has not been demonstrated by the supplied evidence and whose operational launch cost could be substantial relative to measured benefits if naming, search, permissions, approval metadata, or configured media-asset management capabilities resolve most current problems without the full cross-system composition, leaving reviewer labor, integration complexity, archive latency, vendor restrictions, and ongoing exception handling to outweigh reductions in active-tier bytes or authoritative-version errors even if the pilot finds a narrow improvement in one measured user outcome without worsening safety in the selected sample."],"expert_types":["Post-production supervisor","Media archivist or digital-preservation specialist","Editor or VFX pipeline engineer","Rights and production counsel","Media-asset and storage architect"],"expert_questions":["Can the pilot resolve canonical identity and creative authority for the sampled artifacts without relying mainly on undocumented staff memory?","How complete are dependencies across edit, VFX, sound, external vendors, codecs, plug-ins, and software versions?","What improvement over configured media-asset management remains after reviewer labor and retrieval charges are counted?","Who can authorize quarantine and irreversible destruction when ownership, rights, or historical value is disputed?","Do restore tests recreate a usable production context, including relinking and software behavior, rather than merely recover stored bytes?"],"ranking_note":"The post-hoc harmonized review placed it in band B, scoring 68-71 and ranking 15th-20th across profiles. This only sets reading order; it is not the Experiment 3 endpoint, a preregistered success, an economic-value measure, or evidence of novelty.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7","S8"]}]}