{"dossiers":[{"portfolio_id":"EXP06-PARTNER-11","plain_language_title":"Send Raman Surprises, Preserve Full Evidence","one_sentence_summary":"A shadow study would test whether transmitting reconstructable differences from predicted Raman spectra can reduce data and review burdens without hiding consequential chemical or instrument changes.","problem_plain":"Remote reaction monitoring can produce a dense stream of Raman spectra. Most of each spectrum may reflect predictable solvent bands, baseline behavior, or gradual temperature effects, yet every spectrum still consumes transmission, storage, and chemist attention. A small unexpected peak, shifted band, or changed intensity may therefore be reviewed late. Simply sending selected peaks or anomaly labels is also risky because it can hide unfamiliar changes and deny the chemist enough context to reconstruct or challenge the result.","proposal_plain":"Before each acquisition, matched, versioned models at the instrument and review station would predict the next wavelength-aligned spectrum from accepted prior data and declared reaction conditions. The instrument computer would subtract that frozen prediction from the complete observation and transmit the signed correction, uncertainty, context, heartbeat, and model checksum. The receiver could reconstruct the spectrum by adding the correction to its synchronized prediction. Reliable, persistent, or consequential differences would bring the corresponding full spectral window to a named chemist. Random complete spectra and scheduled full-state anchors would provide independent checks. Missing heartbeats, incompatible versions, poor detector quality, stale calibration, structured errors, excessive reconstruction error, or protected safety conditions would restore full-spectrum transmission. Independent safety instruments and the original reaction controls would remain outside this system.","transfer_plain":"The predictive-residual archetype maps directly onto the spectral stream: predict one complete spectrum, compare it with the actual detector output, communicate the signed mismatch, and reconstruct the observation at the receiver. Version checks, raw audits, full anchors, and automatic decompression address the central danger that both endpoints could share the same wrong expectation.","why_it_advanced":"This is an empirical-partner candidate, not a strict success or real-world validation. Real-time Raman acquisition and spectral compression already exist, and the proposed shadow comparison is technically bounded. It advanced because its measurements and rejection rules are unusually concrete, despite having no field evidence that the target workflow suffers a binding bandwidth or attention constraint.","prior_art_and_open_claim":"Adjacent prior art includes commercial real-time Raman systems with multivariate predictors, compressive Raman acquisition, and standardized lossless or near-lossless spectral compression. The open claim is narrower: for one instrument, probe, reaction family, and one-scan horizon, a checksum-gated reconstructive residual stream with raw audits, heartbeats, full anchors, protected bypasses, and forced fallback would use fewer total resources than both full-spectrum streaming and ordinary lossless compression while preserving blinded decisions, protected perturbations, and regional error limits.","test_and_decision":"A laboratory partner would run twelve non-hazard-escalating reactions: eight ordinary runs and four containing approved spectral, calibration, detector, heartbeat, and version challenges. Every raw spectrum would remain authoritative. Blinded chemists would compare full streaming, lossless compression, and the frozen residual path on total bytes, storage, computation, audit and fallback traffic, review minutes, decisions, reconstruction error, and protected-event capture. Reject the claim if any protected challenge is missed, reconstruction changes a material decision, a heartbeat or checksum fault fails to force raw mode, an error limit is exceeded, or net savings are absent.","deployment_and_cost":"The first shadow study requires instrument and API access plus bench-chemist, instrumentation-owner, safety, and information-security approval. Its rough first-evidence band is $10,000–$50,000 in 2026 resource equivalents. Estimated startup is $50,000–$250,000; operational launch $250,000–$1 million; and annual recurring work $50,000–$250,000. These are assessment bands, not vendor quotes.","risks_and_uncertainties":["A shared wrong predictor could suppress an unexpected low-amplitude peak at both endpoints while producing a plausible reconstruction.","Instrument fouling or changing chemistry could gradually be treated as normal rather than as evidence of a new regime.","Alignment error, quantization, or lost corrections could distort later reconstructed spectral shapes.","A chemist-approved consequence table could still privilege anticipated bands and discount unfamiliar features.","Random raw audits may miss rare failures; a clean small sample cannot demonstrate completeness or justify later raw-data deletion."],"expert_types":["Raman spectroscopy and chemometrics specialist","Reaction or process chemist","Laboratory instrumentation engineer","Laboratory safety and data-integrity specialist","Statistical audit-sampling expert"],"expert_questions":["Which low-amplitude or unfamiliar spectral changes must always bypass suppression for the selected reaction family?","What regional and cumulative reconstruction limits would preserve the chemist's actual reaction-state decisions?","Does the intended workflow have measured transmission, storage, queue-delay, or review burdens that ordinary lossless compression cannot address?","What random-audit size and stratification would have adequate power to reveal rare suppressed changes?","Which instrument faults and calibration conditions can be injected safely without changing the controlling record?"],"ranking_note":"The harmonized scores place this candidate between ranks 12 and 39, in ordering band B. That range is only a post-hoc reading aid using an affordability proxy; it is not an experimental endpoint, economic-value estimate, or change to partner-candidate status.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7","S8"]},{"portfolio_id":"EXP06-PARTNER-12","plain_language_title":"Review Materials Results by Model Mismatch","one_sentence_summary":"A blinded partner study would test whether scientists can review model-relative characterization differences instead of every complete package while preserving protected findings and scientific decisions.","problem_plain":"A materials campaign may generate a large characterization package for every composition and processing condition. When scientists review all packages equally, routine confirmations consume the same attention as results that contradict predicted phases, structures, or properties. Fixed features and anomaly labels can shorten the queue, but they may erase unfamiliar peaks, minority phases, or small reliable contradictions. The actual field gap is fundamental: no evidence yet shows that a target laboratory's full-package queue is overloaded or delays important discrepancies.","proposal_plain":"For each candidate, a versioned campaign model would freeze predicted phase, structure, and property outputs before measurements are revealed. The system would compare those predictions with standardized results and preserve signed property errors, categorical disagreements, missing observations, unpredicted peaks or phases, uncertainty, and provenance. Reliable or consequential discrepancies would enter a primary queue with a named reviewer and possible actions such as replication, an orthogonal assay, or a model-scope review. Expected results would remain reconstructable and complete raw files available on demand. Random candidates, protected classes, and risk-selected cases would still receive full-package review. New chemical classes, incompatible versions, invalid measurements, safety flags, stale models, structured residuals, or excessive reconstruction error would suspend triage. Scientists—not the queue—would authorize experiments and model changes.","transfer_plain":"The residual-processing archetype becomes a scarce-attention system rather than a data link. A model predicts each candidate's standardized characterization; measured-minus-predicted differences become the review message and later learning signal. The mapping is strong for numerical properties but weaker for images, peaks, phases, and unfamiliar features, which cannot always be reconstructed additively and must remain accessible in full.","why_it_advanced":"This candidate cleared only the separately calibrated empirical-partner lane. Autonomous laboratories, active learning, human-guided phase mapping, and large provenance systems make its components plausible. It did not reach strict success because no paired field trial shows that residual presentations reduce total work without changing scientific actions, and the target queue constraint remains unmeasured.","prior_art_and_open_claim":"Adjacent systems already use Bayesian optimization, uncertainty-guided measurement selection, automated phase analysis, anomaly detection, and human model updates. The narrower open comparison is an audited review interface: frozen multimodal predictions plus numerical, categorical, missingness, and unfamiliar-feature residuals, with protected and sampled full-package review. On one material family, it claims at least 30% less total reviewer time, at least 95% action concordance, complete capture of protected challenges, no acceptance of missing or incompatible results, and no increase in follow-up demand.","test_and_decision":"A partner laboratory would conduct a paired, blinded shadow study on 60–150 already authorized candidates from one family and fixed assay suite. It would compare complete packages, uncertainty-only ordering, fixed anomaly or feature thresholds, and the frozen residual presentation. Concealed challenges would include small property shifts, phase conflicts, unfamiliar peaks, bad assays, missing data, version mismatches, and out-of-scope chemistry. Reject operational adoption if workload falls less than 30% after audits and fallbacks, concordance is below 95%, any protected case is missed, an incompatible or missing package passes, or one discrepancy class is systematically lost.","deployment_and_cost":"A shadow trial needs laboratory leadership, characterization, model, safety, and data-steward authorization, plus review of trade-secret, export-control, retention, and publication rules. Rough 2026 resource-equivalent bands are $50,000–$250,000 for first evidence, $250,000–$1 million for startup, $1–$5 million for operational launch, and $250,000–$1 million annually. No vendor quote supports them.","risks_and_uncertainties":["Standardization may remove an unfamiliar peak, morphology, or minority phase before the residual is calculated.","A confident but misspecified campaign model may classify informative chemistry as routine.","Underestimated assay uncertainty may give noisy results excessive influence over routing and model updates.","Audits may miss rare discrepancies, especially when risk sampling reflects only anticipated failure modes.","Routine packages removed from the main queue may contain context needed to recognize a later campaign-wide pattern."],"expert_types":["Materials discovery scientist","X-ray diffraction or multimodal characterization specialist","Bayesian modeling and active-learning researcher","Scientific data-governance specialist","Experimental-design statistician"],"expert_questions":["Is complete-package review currently exceeding a declared capacity or delaying model-relevant discrepancies in the proposed campaign?","Which raw or standardized observations cannot be represented safely as model-relative residuals?","What protected challenge set would cover unfamiliar peaks, minority phases, specimen errors, and out-of-scope chemistry?","How should audit size and sampling be powered for rare but decision-changing discrepancies?","Can independent reviewers reliably classify each mismatch as chemical evidence, measurement failure, specimen error, or model-scope failure?"],"ranking_note":"Post-hoc harmonized profiles place this candidate from rank 10 to 36, in ordering band C. The spread is a reading-order aid, not a preregistered outcome or estimate of economic value, and it does not remove the need for field evidence.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7","S8"]},{"portfolio_id":"EXP06-PARTNER-21","plain_language_title":"A Common Contract for Synchronized Takes","one_sentence_summary":"A read-only pilot would test whether different picture-and-sound synchronizers can expose the same take membership, timing, gaps, and conflicts without clients depending on filenames or vendor internals.","problem_plain":"Dailies systems often decide which picture and sound files form a take by using filenames, folder order, embedded timecode, recorder labels, sidecars, or one algorithm's behavior. A camera, recorder, metadata carrier, file split, or synchronization tool can therefore change grouping and frame-to-sample alignment even when the intended take is unchanged. Existing pipelines lack a shared behavioral test for deciding whether a replacement synchronizer truly preserves membership, timing, channel roles, gaps, conflicts, and ambiguity.","proposal_plain":"An opaque SynchronizedTake component would register picture and sound streams by semantic role, accept clock or slate observations, resolve alignment under an explicit policy, map stream positions into common take time, report shared coverage, validate completeness, freeze a resolved version, and create superseding versions. Its contract would require monotonic mapping within continuous segments, one public correspondence for every resolved position, explicit gaps and discontinuities, declared ambiguity and conflict errors, immutability after freezing, and no state change after rejection. Filenames, folders, metadata locations, waveform features, caches, databases, and matching algorithms would remain private. The same black-box fixtures, generated sequences, and representation-change tests would judge manual-anchor, timecode, waveform-assisted, and device-specific implementations. The component could not rewrite, delete, or silently relabel source media.","transfer_plain":"The interface-contract archetype maps cleanly to dailies: define a synchronized take by observable behavior and invariants, not by its file layout or synchronization algorithm. Each implementation translates private evidence into the same semantic streams and common-time mappings. Substitution depends on passing one oracle, although narrowly authorized diagnostic access may still be needed for physical clock provenance.","why_it_advanced":"This is an empirical-partner candidate, not a strict-success result. Existing synchronization products, timecode and audio standards, interchange schemas, and implementation-neutral timeline models support feasibility. It advanced because a copied-media, read-only comparison is bounded and reversible, while real failure prevalence, operator acceptance, independent implementations, and production authorization remain absent.","prior_art_and_open_claim":"Premiere and Resolve already synchronize multicamera material; FCPXML represents synchronized clips; BWF and SMPTE timecode standardize important carriers; and OpenTimelineIO separates timelines from proprietary files. The remaining claim is narrower than a new format: two independent resolvers would return equivalent semantic membership, covered intervals, mappings, gaps, conflicts, and lifecycle outcomes after renaming, relocation, registration reordering, clock-origin shifts, and lossless segmentation—and would outperform a metadata-schema-only approach without exposing private implementation details.","test_and_decision":"With written production approval, duplicate one short, non-live take containing two picture streams, separate sound, aligned coverage, and a known gap or conflict. Freeze expected membership, mappings, errors, positional tolerance, and the no-write rule. Compare the incumbent result, a simple manual-anchor model, one adapter, and a schema-only baseline where possible. Rename and relocate files, reorder registration, shift the clock origin with compensation, and split a continuous stream losslessly. Reject the claim if independent resolvers diverge beyond tolerance, silently resolve conflicts, mutate after rejection, require private fields for ordinary work, or the schema baseline matches them with materially less effort.","deployment_and_cost":"A pilot requires post-production, sound, camera or data, dailies, editorial, rights, and security approval. It must use copied media and leave the active pipeline unchanged. Rough 2026 bands are $10,000–$50,000 for first evidence, $50,000–$250,000 for startup, $250,000–$1 million for launch, and $50,000–$250,000 annually; no measured effort or quote confirms them.","risks_and_uncertainties":["The common-time model may omit drift, variable rates, discontinuities, or corrupted-clock behavior found in production media.","Clock provenance or recorder-specific channel facts may be necessary production information rather than accidental representation.","A shared test fixture may encode the same mistaken synchronization assumptions as the reference implementation.","Opacity may make failures difficult to diagnose unless a narrowly governed read-only diagnostic surface is defined.","Two mappings within a numerical tolerance may still differ in ways assistant editors or sound staff consider operationally unacceptable."],"expert_types":["Dailies pipeline engineer","Production sound mixer or synchronization specialist","Assistant editor","Media interchange and timecode standards expert","Post-production security and rights specialist"],"expert_questions":["Which device-specific facts must remain visible for authorized diagnosis, and which are accidental client dependencies?","What frame or sample tolerance is acceptable for each downstream viewing, logging, and editorial task?","How must the abstract model represent drift, discontinuities, variable frame rates, missing coverage, and multichannel sound?","Can a canonical metadata baseline provide the same invariance and usability with less integration work?","What production-derived fixtures would adequately represent actual synchronization failures without exposing protected media?"],"ranking_note":"The post-hoc harmonized review places this candidate between ranks 18 and 32, in ordering band C. This is only a reading-order aid based partly on an affordability proxy; it is neither a preregistered success nor evidence of production benefit.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7","S8"]},{"portfolio_id":"EXP06-PARTNER-22","plain_language_title":"Portable Lighting Cues With Behavioral Tests","one_sentence_summary":"An isolated trial would test whether different lighting controllers and fixture allocations can reproduce an approved cue trajectory and safe lifecycle without exposing raw console addresses.","problem_plain":"Film lighting cues are often encoded through one console's channels, fixture profiles, addresses, show-file structure, macros, and transition rules. Moving a scene, changing a console, or reallocating fixtures can alter fades, colors, holds, conflicts, or emergency transitions even when the intended look has not changed. File import and transport standards help move data or commands, but the production still lacks a shared test for whether another controller preserves both the photographed cue behavior and its output boundaries.","proposal_plain":"An opaque LightingCueProgram would expose semantic operations: validate a rig, arm without changing output, trigger, sample declared state, hold, resume, cancel, abort to a safe state, report status, freeze, and supersede. Its abstract model would name lighting roles, targets, timed trajectories, interpolation, concurrency and conflict rules, enrolled outputs, a safe state, and version history. Valid event sequences would have deterministic abstract trajectories; rejected or unarmed commands would leave output unchanged; abort would take precedence; and commands could reach only enrolled endpoints. Console syntax, channels, addresses, universes, profiles, show files, and drivers would remain private. A shared black-box suite would compare a reference player and console adapters after address renumbering, registration reordering, and capability-equivalent fixture reallocation, using visual, camera, photometric, timing, and safety tolerances fixed by accountable staff beforehand.","transfer_plain":"The representation-independent-contract archetype is instantiated as a semantic lighting state machine separated from console and rig details. Adapters translate the same cue operations into different physical implementations, and one conformance oracle governs substitution. The mapping is incomplete unless it captures photographed light: equal console values do not guarantee equal spectra, flicker, optics, placement, or camera response.","why_it_advanced":"This candidate entered only the empirical-partner lane. Show-file import, GDTF/MVR, DMX, ACN, and open control gateways establish adjacent technical pieces, while a simulator test is small and reversible. It lacks measured production prevalence, an independent implementation, approved visual tolerances, vendor or production commitment, and evidence that physical fixture differences will not dominate representation effects.","prior_art_and_open_claim":"Current prior art standardizes show-data import, device and scene descriptions, transport, and cross-protocol control. It does not establish a cinematographer-approved cue lifecycle and emitted-light substitution test. The remaining claim is that two independent adapters can hide addressing yet deliver equivalent semantic and photographed trajectories, identical errors and lifecycle behavior, no unenrolled output, and an approved abort transition after representation changes. Existing interchange matching those results at equal or lower effort would defeat the incremental claim.","test_and_decision":"With DP, gaffer, electrical, and safety approval, test one disconnected cue containing arming, a timed fade, concurrent endpoints, hold and resume, a conflict, an unarmed rejection, and abort-to-safe. Freeze expected trajectories, error codes, enrolled outputs, camera and photometric tolerances, timing limits, and abort deadline. Compare a reference player, one console adapter, and the incumbent import-and-rebuild workflow, then repeat after address, registration, and fixture-allocation changes. Reject the claim for any unenrolled command, rejected-command output, lifecycle disagreement, tolerance failure, required console-native escape hatch, cheaper equivalent incumbent performance, or materially different photographed result despite nominal conformance.","deployment_and_cost":"The first test must remain on a simulator or isolated prelight bay with no performers, shooting rig, hazardous effects, machinery, or production automation attached. Rough 2026 resource-equivalent bands are $10,000–$50,000 for first evidence, $50,000–$250,000 for startup, $250,000–$1 million for launch, and $50,000–$250,000 annually. They are not quotes.","risks_and_uncertainties":["Normalized semantic values may produce different perceived and photographed light across fixture technologies.","The contract may omit spectral output, flicker, optics, spatial placement, latency, or resource contention important to the scene.","Console telemetry may conform even while the emitted light falls outside the approved camera or photometric tolerance.","A software-defined safe state may conflict with stage electrical procedure or fail over an unreliable lighting transport.","The contract may accidentally preserve the incumbent console's interpolation or tie-breaking behavior instead of the cinematographer's intent."],"expert_types":["Director of photography or imaging scientist","Gaffer and lighting console programmer","Stage electrical and entertainment-control safety specialist","Fixture calibration and spectral-measurement specialist","Lighting-control standards and adapter engineer"],"expert_questions":["Which semantic endpoint properties and photographed-light measurements define equivalence for the selected cue?","What tolerances for spectrum, exposure, color, flicker, trajectory timing, and abort completion must be frozen before testing?","Can the chosen GDTF descriptions represent the relevant fixtures accurately, including unsupported or vendor-specific features?","Which abort behavior is safe under actual electrical procedure, and what can be guaranteed over a transport that may lose packets?","Does the incumbent import-and-manual-rebuild workflow already meet the same criteria with equal or lower effort?"],"ranking_note":"Post-hoc harmonized profiles place this candidate from rank 23 to 30, in ordering band C. The ranking is a reading-order aid using an affordability proxy, not a preregistered endpoint, deployment authorization, novelty determination, or measure of economic value.","source_ids_used":["S1","S2","S3","S4","S5","S6","S7","S8"]}]}