{"dossiers":[{"portfolio_id":"EXP06-PARTNER-25","plain_language_title":"Stable Sampling Across Changing Data Systems","one_sentence_summary":"This external-partner study candidate would test whether an opaque sampling contract can preserve eligible units, seeded selections, and inclusion probabilities when the same approved household frame is stored differently; no field study or adopter commitment yet supports it.","problem_plain":"A household study may store its recruitment frame as spreadsheets, rosters, or databases that use different ordering, identifiers, and blank-value conventions. Sampling scripts can quietly depend on those details. Reordering or migrating an otherwise unchanged frame may then alter eligibility, give duplicate records extra selection chances, change a seeded draw, or assign different inclusion probabilities. Researchers could mistake those technical effects for genuine field outcomes or an authorized change in sampling design.","proposal_plain":"Define the sampling frame through public behavior rather than a particular table. Custodians would map source records to unique abstract sampling units, keep direct identifiers behind a protected boundary, and freeze an immutable snapshot with explicit eligible, ineligible, unresolved, unknown, and withdrawn states. Authorized clients could draw a sample, query probabilities, verify a draw, supersede a snapshot, or export opaque recruitment handles. The contract would require identical results for the same snapshot, design version, and seed despite row permutation, lossless reserialization, or replacement of internal keys. Duplicate physical records could not create extra chances, invalid requests could not return partial samples, and drawing could never initiate contact. Shared black-box, generated-case, transformation, and leakage tests would gate backend replacement.","transfer_plain":"The transferred archetype is a representation-independent interface contract: multiple storage systems must expose the same abstract units and observable sampling behavior while hiding their internal representation. The structural mapping is strong, although the difficult mapping from real records to unique people, households, or addresses remains a substantive governance decision rather than a software detail.","why_it_advanced":"It cleared the separately calibrated external-partner lane because the operations, comparator, failure conditions, and synthetic test are unusually specific, and mature sampling and metadata tools make a prototype feasible. It did not enter strict success: representation-caused frame divergence has not been quantified, and no study or field office has offered data or committed to evaluation.","prior_art_and_open_claim":"Sampling standards already require accurate, unduplicated frames, retained design information, testing, documentation, and protection of restricted data. Metadata standards and sampling products already represent frames, selection probabilities, seeds, and reproducible draws. The narrower open claim is that independently built backends passing one opaque behavioral oracle will preserve abstract snapshots, selections, probabilities, errors, and non-contact side effects across representation-only changes. This is adjacent prior art, not a novelty finding.","test_and_decision":"Run a two-week trial with 200 fictional units encoded independently in a shuffled flat file and normalized database. Compare the current file-coupled scripts with both adapters used only through the contract across at least 1,000 prespecified seeds. Apply row permutations, reserialization, key replacement, ineligible-record insertion, and duplicate consolidation; also insert deliberately defective adapters. Advance only if every legitimate transformation preserves all specified outputs, every mutant is caught, no source information leaks, and reviewers can map every valid state without hiding an identity judgment. Any changed draw or probability defeats the claim.","deployment_and_cost":"The first synthetic evidence step is assessed at roughly $10,000-$50,000. Startup, operational launch, and annual recurring work are each roughly $50,000-$250,000 in 2026 resource-equivalent terms, not vendor quotes. Live deployment would additionally require approved identity rules, privacy and ethics review, security controls, version governance, training, and a certified rollback path.","risks_and_uncertainties":["The abstract unit model could erase meaningful distinctions among households, addresses, or memberships.","Incorrect deduplication could merge distinct eligible units; insufficient deduplication could create extra selection chances.","Predictable seeds, handles, output order, or error details could expose identities or reveal selection.","A technically conforming frame could still omit important parts of the intended population.","Immutable snapshots could preserve known mistakes if supersession is too difficult to use promptly."],"expert_types":["Survey sampling statistician","Social-research data engineer","Frame custodian or field-operations lead","Research ethics and privacy specialist","Community or participant-governance representative"],"expert_questions":["Can every valid source state map to a unique abstract unit without concealing a disputed identity or eligibility judgment?","Which draw outputs must be bit-for-bit identical across backends, and which implementation differences may legitimately vary?","Do current migrations or reorderings measurably change units, selections, or weights after authorized design changes are excluded?","Could opaque handles, deterministic seeds, ordering, errors, or timing permit reidentification or prediction?","Who may approve eligibility, deduplication, design-version, and live-backend changes?"] ,"ranking_note":"The post-hoc harmonized ordering placed it between ranks 15 and 21, in band B. That score only sets reading order, uses affordability as a pilot-speed proxy, and measures neither experimental success nor economic value; its endpoint remains EMPIRICAL_PARTNER_CANDIDATE.","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":"This external-partner study candidate adds a brief, consent-governed stewardship observance to ordinary nanomaterial custody controls, but no participant study yet shows that it improves ownership accuracy beyond a strong checklist and briefing.","problem_plain":"Nanomaterials and related duties pass among synthesis, fabrication, measurement, safety, storage, and waste teams. Records may exist while people disagree about who owns an unresolved containment, labeling, transport, or disposal task, when it is due, or when to escalate it. Routine signatures can conceal that gap, especially after turnover. The result may be stranded anomalies, unfunded controls, ambiguous custody, poor traceability, or avoidable exposure and contamination risks.","proposal_plain":"At project launch, each custody transfer, and quarterly thereafter, hold a 12-minute “Visible Boundary” observance outside controlled work areas. An inert token moves along a printed lifecycle map from synthesis through disposal; no real material enters the session. Relevant participants may speak, write privately, observe, or pass without explanation. They identify the current stage and unresolved uncertainties, then propose, revise, or decline symbolic commitments. An accepted commitment counts only after the normal action system records an owner, resources, deadline, and escalation condition. A safety witness reads those entries back and states that the event does not certify safety or replace procedures, training, stop-work rights, custody records, or engineering controls. Anonymous feedback and independent reviews can revise, pause, or retire the practice.","transfer_plain":"The archetype transfers recurring ritualized meaning and commitment into a technical custody setting. The marked time, lifecycle symbol, witnessing, renewal, debrief, and retirement paths map clearly. The proposed effect, however, depends on a social mechanism—shared enactment improving accurate recall and ownership—that has not been demonstrated in nanomaterial work.","why_it_advanced":"It cleared the external-partner lane because a low-cost tabletop can compare the symbolic layer directly with a strengthened checklist and briefing, using delayed individual measurements and explicit safety failures. It did not meet strict success: no facility has committed, the proposed ownership problem lacks prevalence evidence, and the central comparative effect remains untested.","prior_art_and_open_claim":"Lifecycle controls, training, labeling, waste procedures, worker participation, action tracking, project rituals, and safety-culture programs already exist. Research suggests group rituals can increase perceived meaning, but it does not establish better safety-relevant recall or voluntary participation under laboratory hierarchies. The remaining claim is narrower: adding this governed enactment to the same strong checklist and briefing improves agreement about owners, deadlines, uncertainties, downstream parties, and stop conditions without pressure, added errors, or false safety assurance.","test_and_decision":"With facility and independent safety approval, counter-order two fictitious custody-transfer scenarios for one volunteer cross-functional group. Condition A uses a strengthened checklist and conventional briefing; condition B adds the observance. Measure each participant’s answers about ownership, deadlines, uncertainty, downstream parties, and stop conditions immediately and 48-72 hours later. A blinded safety reviewer should code omissions, invalid commitments, and false closure, while anonymous responses assess accessibility, pressure, and certification confusion. Do not advance if B lacks the prespecified accuracy gain, creates more errors, makes refusal consequential, or is mistaken for safety certification.","deployment_and_cost":"The tabletop is assessed below $10,000. Startup, launch, and annual recurring effort are each roughly $10,000-$50,000 in 2026 resource-equivalent terms, not vendor quotes. Any operational use would require local labor, accessibility, privacy, records, and safety review, trained independent facilitation, protected opt-outs, and continued funding for the actual controls and commitments.","risks_and_uncertainties":["Employees or junior researchers could experience visible participation as a loyalty test.","Ceremonial completion could be mistaken for evidence that a material or process is safe.","Token passing could become rote and suppress uncertainty instead of surfacing it.","The session could substitute recognition for money, staff, engineering controls, or corrective action.","Remote, disabled, multilingual, contract, night-shift, or waste-handling workers could be excluded from the shared account."],"expert_types":["Nanomaterial laboratory scientist","Environment, health, and safety professional","Human-factors or organizational-behavior researcher","Labor and research-ethics specialist","Waste-management or downstream custody representative"],"expert_questions":["Do actual transfers produce disagreement about owners, deadlines, escalation conditions, or downstream effects after current records are reviewed?","What accuracy improvement over a strengthened checklist would justify the additional social and time burden?","Can people decline every symbolic act without their refusal becoming visible or consequential?","Which wording and facilitation practices best prevent ceremonial closure from being interpreted as safety certification?","Who can independently halt or retire the practice if commitments remain unfunded or participants report pressure?"] ,"ranking_note":"The post-hoc ordering ranged from rank 1 under deployment-heavy weights to 43 under impact-heavy weights, placing it in band B. This volatility reflects weighting and a cost proxy, not experimental success or economic value; the endpoint remains EMPIRICAL_PARTNER_CANDIDATE.","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":"This external-partner study candidate would add a witnessed renewal-and-release assembly to lawful closure and transition procedures, while prominently requiring evidence that the ritual layer improves shared understanding without coercing volunteers or stranding residents.","problem_plain":"A neighborhood mutual-aid network may outlive the emergency that created it. Public channels, volunteer titles, pooled funds, routes, and phone trees can still signal readiness even when capacity and authority are unclear. Residents may rely on services that no longer operate; volunteers may feel unable to leave; and founders may retain accounts after nominal handoffs. Ordinary meetings can cancel tasks but may not create a legitimate, witnessed separation between ending volunteer roles and completing remaining duties.","proposal_plain":"Hold a quarterly and trigger-based Mandate Renewal and Release Assembly while any function remains open. Beforehand, stewards inventory advertised services, capacity, dependencies, funds, data, decision authority, reliance, and possible recipients. A status board marks each function as under review, and function cards enter provisional lanes: renew, transfer, suspend, repair, or release. Card placement is not a decision. Willing volunteers, lawful resource holders, and safeguards for affected residents must support the operational disposition. Closure then updates notices, rosters, escalation paths, funds, credentials, data, referrals, and deadlines. Participants may speak, submit privately, remain silent, delegate, or leave. Retiring a role never extinguishes debts, safeguarding duties, contracts, or promised transitions, and later audits compare public claims with actual capacity and custody.","transfer_plain":"The ritualized commitment archetype becomes a recurring, witnessed review of collective mandates, using marked time, function cards, reflection, renewed consent, release, handoff, debrief, and later audit. The mapping is coherent, but the distinct contribution of ceremony is uncertain because sunset rules, transition plans, demobilization, closure checklists, and volunteer recognition already perform much of the work.","why_it_advanced":"It entered the external-partner lane because it separates voluntary labor from surviving legal and service duties, names the necessary authorities, and offers a bounded comparator study. It did not enter strict success: no network has committed, stale-capacity prevalence is unknown, and there is no evidence that the assembly outperforms ordinary closure and transition practice.","prior_art_and_open_claim":"Emergency demobilization, nonprofit dissolution, service transfer, volunteer disengagement, debriefing, recognition, and care-oriented organizational closure are established. The open comparison begins only after a valid sunset rule, authorized closure checklist, and safe transition plan exist. The question is whether the witnessed assembly further improves volunteers’, residents’, and custodians’ accuracy about service status, authority, refusal rights, and unfinished duties without added coercion, disclosure, delay, or stranded work. It is a combination-level claim amid adjacent prior art.","test_and_decision":"With a named network and legal or fiscal sponsor, run a compensated, preregistered tabletop with 24-40 volunteers, resident representatives, custodians, and potential partners. Counterbalance matched, noncritical mock mandates between ordinary sunset, checklist, and transition procedures and the same package plus the assembly. Measure service status, authority, refusal paths, notices, custody, and unfinished duties immediately and seven days later, alongside pressure, disclosure, distress, time, and false-closure beliefs. Reject incremental advantage if accuracy does not materially improve, burdens rise without compensating benefit, or any simulated duty is stranded. Halt for pressure, distress, privacy failure, or disputed authority.","deployment_and_cost":"The tabletop is assessed below $10,000; startup, launch, and annual recurring effort are each roughly $10,000-$50,000 in 2026 resource-equivalent terms, not vendor quotes. Live costs could rise with legal complexity, critical services, debts, accessibility needs, data cleanup, and funded transitions. Ordinary legal and operational authority remains mandatory.","risks_and_uncertainties":["Residents could lose needed support before a capable alternative and truthful notice are in place.","Public discussion could expose a resident’s need or a volunteer’s exhaustion.","Recognition, gratitude, or lament could pressure volunteers to renew their labor.","Founders could curate the evidence or retain credentials despite a witnessed handoff.","Symbolic release could be misused to avoid debts, delete data improperly, or leave contracts and safeguarding duties incomplete."],"expert_types":["Mutual-aid organizer or former volunteer","Affected-resident representative","Nonprofit or fiscal-sponsor lawyer","Data-protection and safeguarding specialist","Service-transition or emergency-demobilization practitioner"],"expert_questions":["Which functions are legally controlled, informally controlled, safety-critical, or dependent on outside partners?","Can volunteers withdraw immediately while residents still receive a safe and truthful transition?","What evidence would show that the assembly adds understanding beyond a sunset clause, closure checklist, and facilitated transition meeting?","How will private reliance statements and participation choices be protected from founders, employers, or public records?","Who verifies that credentials, funds, notices, data, property, and surviving duties actually moved after the witnessed decision?"] ,"ranking_note":"The post-hoc harmonized reading order placed it between ranks 14 and 25, in band B. The calculation uses affordability as a pilot-speed proxy and does not establish experimental success, deployment merit, or economic value; its endpoint remains EMPIRICAL_PARTNER_CANDIDATE.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7","S8"]},{"portfolio_id":"EXP03-POSTHOC-02","plain_language_title":"Safer Cleanup of Post-Production Assets","one_sentence_summary":"This post-hoc survivor proposes dependency-aware lifecycle rules for media-production files, but every major component has adjacent prior art and the complete workflow has not been compared with a manual sweep or configured asset-management system.","problem_plain":"A production accumulates edit versions, visual-effects renders, proxies, sound stems, exports, and project files whose usefulness changes over time. Old artifacts can remain visible as if current, consume active storage, and slow retrieval. Yet deleting them by age, name, or staff intuition can break project relinking, reconstruction, rights evidence, or future remastering. The core tension is distinguishing safely demotable clutter from creative or evidentiary material whose future dependencies are incomplete or hidden.","proposal_plain":"Assign each artifact an explicit lifecycle and creative-authority state, then assess dependencies, rights, legal holds, ownership, reconstruction needs, and restoration context before moving or deleting anything. Approved artifacts could move to cheaper storage or reversible quarantine; persistent markers would prevent restored or superseded files from silently appearing current again. Restore drills would test checksums, relinking, codecs, plug-ins, and software context, while recurring reviews would revisit earlier classifications. Owners would approve exceptions, archive or IT staff would verify recoverability, and legal or rights staff would control relevant holds and irreversible destruction. The proposal aims to bound active storage and search noise without silently sacrificing usable production history, but automatic deletion based only on age, access, score, or filename is excluded.","transfer_plain":"The layer-decay archetype maps to media files whose authority and usefulness expire at different rates. Lifecycle states nominate refresh, demotion, quarantine, or deletion, while dependency and restoration checks prevent unsafe transitions. The analogy is imperfect because dormant creative work can regain value years later and may depend on proprietary tools, external vendors, or undocumented practice.","why_it_advanced":"After Experiment 3, the candidate survived a stricter combined opportunity screen because the problem is concrete, existing technical primitives permit a bounded replay, and safety outcomes are measurable. This was a post-hoc result, not a preregistered success. Prevalence, net benefit, complete dependency capture, and adopter acceptance remain unestablished.","prior_art_and_open_claim":"Media-asset systems already archive and restore files with permissions; media ontologies represent versions and provenance; preservation standards cover rights, events, relationships, and technical dependencies; workflow tools track stale data; and cloud systems automate storage tiers. The only remaining contrast is the operating-policy combination: creative-authority state, dependency and reconstruction coverage, rights and owner gates, reversible quarantine, anti-staleness markers, restore drills, and recurring revalidation. The search did not establish novelty or superiority over a configured media-asset and archive workflow.","test_and_decision":"On one completed, non-litigated production, conduct a read-only replay using a documented random sample of 200 artifacts from two classes. Independent reviewers compare a manual sweep, verified off-the-shelf asset-management rules, and the full proposal. Using isolated copies, simulate tiering and quarantine and test checksums, restoration, relinking, and software context. Compare labor, retrieval time, authoritative-version errors, safely demotable bytes, disputed labels, dependency misses, and restore success. Do not advance unless the full workflow materially improves a user outcome and active-tier burden after labor without worsening safety. Any missed live dependency, hold conflict, failed integrity check, relink, or restore defeats advancement.","deployment_and_cost":"First evidence is assessed at roughly $10,000-$50,000. Startup is roughly $50,000-$250,000, operational launch $250,000-$1 million, and annual recurring work $50,000-$250,000 in 2026 resource-equivalent terms, not vendor quotes. Actual costs depend on artifact volume, integrations, storage, licensing, legal review, vendor access, and recurring classification labor.","risks_and_uncertainties":["The workflow could destroy unique creative work, contractual evidence, or material needed for a later reconstruction.","Dependency graphs may omit external vendors, proprietary project formats, plug-ins, codecs, fonts, licenses, or tacit creative steps.","Lifecycle labels could falsely imply that authority or disposal eligibility is settled.","Archive latency and retrieval charges could disrupt an unexpected reuse request.","Quarantine records and anti-staleness markers could themselves become another unmanaged layer."],"expert_types":["Post-production supervisor or assistant editor","Media archivist or preservation engineer","VFX and sound pipeline engineer","Production IT or media-asset-management administrator","Entertainment rights, contracts, or records counsel"],"expert_questions":["Can the production identify a canonical artifact and its authoritative status across edit, VFX, sound, and delivery systems?","How complete are dependency records for external vendors, software versions, plug-ins, codecs, fonts, and licenses?","Which outcomes would justify the added review labor compared with a configured media-asset system?","Who has authority to approve demotion, quarantine, exceptions, holds, and irreversible destruction for each artifact class?","What restore and relink failures are acceptable, if any, before all destructive transitions must stop?"] ,"ranking_note":"The post-hoc harmonized reading order placed it between ranks 15 and 20, in band B. This ordering is not an experimental endpoint or economic-value measure. Its endpoint remains POST_HOC_STRICT_INNOVATION_LIKE_SURVIVOR, not a preregistered success.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7","S8"]}]}