{"schema_version":1,"research_id":"eoa_inverse_innovation_exp06_external_evaluation_20260803","source_assessment_id":"representation_independent_interface_contract__film_media_production:P3:v0","cell_id":"representation_independent_interface_contract__film_media_production","search_queries":["site:tsp.esta.org ANSI E1.11 DMX512-A standard scope lighting control official","site:gdtf-share.com GDTF official standard fixture data exchange MVR","site:openlighting.org Open Lighting Architecture API plugins official","cinematic lighting console interoperability cue show file standard research","site:tsp.esta.org lighting control interoperability standard cue semantic behavior","site:etnow.com lighting console show file exchange interoperability GDTF MVR","site:etcconnect.com Eos show file import ASCII export cue official documentation","LED stage lighting spectral output camera metamerism research paper fixture color matching","site:tsp.esta.org E1.69 tagging vocabulary semantic model lighting interoperability PDF","site:gdtf-share.com GDTF founders MA Lighting Robe Vectorworks official interoperability","site:vectorworks.net GDTF MVR interoperability lighting consoles open standard official","site:etcconnect.com lighting console GDTF MVR support official Eos","GDTF specification DMX channel logical channel attribute physical emitter color space function sets official","MVR specification cues lighting scene show file cue list official","lighting semantic cue interoperability contract research conformance testing DMX","ANSI E1.17 ACN device description language semantic interoperability lighting official PDF"],"sources":[{"source_id":"S1","title":"Importing Show Files","publisher":"Electronic Theatre Controls, Inc.","url":"https://www.etcconnect.com/webdocs/Controls/IonOnlineHelp/en-us/Content/04_Managing_Show_Files/04_Importing_Show_Files/About_Importing_Show_Files.htm","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"n.d.","accessed_at":"2026-08-03","claims_supported":["Eos imports USITT ASCII and other show-data formats from several console families.","ETC warns that consoles store and use data differently, imported playback may not match, and effects or macros may be omitted.","Current migration is therefore format- and product-dependent rather than behavioral-conformance based."]},{"source_id":"S2","title":"GDTF FAQ","publisher":"GDTF Development Group / GDTF Share","url":"https://gdtf-share.com/landing/pages/faq.php","source_class":"OFFICIAL_ORGANIZATION_DATA","publication_date":"n.d.","accessed_at":"2026-08-03","claims_supported":["Vectorworks, MA Lighting, and Robe jointly developed GDTF to provide a unified, manufacturer-supported definition for intelligent-luminaire operation.","The stated goal is consistent and dependable exchange among control, CAD, and previsualization tools.","The FAQ identifies active implementers and maintainers, including console and visualization vendors, establishing credible potential adopters and standards stewards.","GDTF is DIN SPEC 15800:2022, while MVR packages stage, patch, location, and GDTF data."]},{"source_id":"S3","title":"GDTF & MVR Help Pages","publisher":"GDTF Development Group / GDTF Share","url":"https://gdtf-share.com/help/","source_class":"OFFICIAL_GUIDANCE","publication_date":"n.d.","accessed_at":"2026-08-03","claims_supported":["GDTF is an open standard for describing entertainment devices.","MVR is an open standard for sharing entertainment-scene data and geometry.","The respective specifications are DIN SPEC 15800:2022-02 and DIN SPEC 15801:2023-12.","Their documented scope is device and scene representation, not a complete cross-console cue lifecycle and trajectory-conformance oracle."]},{"source_id":"S4","title":"ANSI E1.11-2024: USITT DMX512-A Asynchronous Serial Digital Data Transmission Standard for Controlling Lighting Equipment and Accessories","publisher":"Entertainment Services and Technology Association","url":"https://tsp.esta.org/tsp/documents/docs/ANSI%20E1.11%20-%202024.pdf","source_class":"STANDARD","publication_date":"2024","accessed_at":"2026-08-03","claims_supported":["DMX512-A standardizes electrical characteristics, packet format, protocol, and connectors for interoperating controllers and lighting equipment.","Its primary stream is an untyped byte stream and its interoperability is chiefly at communication and mechanical levels.","It does not ensure delivery of every packet and is explicitly inappropriate for hazardous applications.","It therefore supplies transport prior art but not the proposed semantic cue state machine, reliable abort guarantee, or emitted-light equivalence."]},{"source_id":"S5","title":"ANSI E1.17-2015 (R2025): Entertainment Technology—Architecture for Control Networks (ACN)","publisher":"ANSI Webstore / Entertainment Services and Technology Association","url":"https://webstore.ansi.org/standards/esta/ansie1172015r2025","source_class":"STANDARD","publication_date":"2025","accessed_at":"2026-08-03","claims_supported":["ACN defines a configurable protocol-and-language architecture for networked lighting, audio, and other control systems.","It is close prior art for implementation-independent network control architecture.","The public scope description does not establish the candidate's cinematography-approved cue trajectories, hold/conflict/abort laws, or shared black-box substitution test."]},{"source_id":"S6","title":"Open Lighting Architecture Developer Documentation","publisher":"Open Lighting Project","url":"https://docs.openlighting.org/ola/doc/latest/index.html","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2023-01-02","accessed_at":"2026-08-03","claims_supported":["OLA already provides a common framework, APIs, and gateway conversion across DMX512, sACN, Art-Net, OSC, USB interfaces, and other transports.","Existing open-source components make a simulator and protocol-adapter prototype technically plausible.","OLA abstracts communication but does not itself provide the proposed cue semantics, photographic oracle, lifecycle rules, or safety authorization."]},{"source_id":"S7","title":"General Device Type Format (GDTF) Fixture Import for Eos Family","publisher":"Electronic Theatre Controls, Inc.","url":"https://support.etcconnect.com/ETC/Consoles/Eos_Family/Software_and_Programming/GDTF","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"n.d.","accessed_at":"2026-08-03","claims_supported":["Eos v3.2.4 imports GDTF definitions into console-specific fixture profiles.","ETC documents missing color-calibration import, unsupported lamp controls and multi-cell fixtures, absent virtual parameters, and possible parameter-name mismatches.","ETC instructs users to verify imported definitions on real fixtures and correct them manually, demonstrating both practical feasibility and unresolved semantic/physical translation gaps."]},{"source_id":"S8","title":"Color Reproduction in LED Wall Virtual Production Stages","publisher":"Society for Imaging Science and Technology","url":"https://library.imaging.org/admin/apis/public/api/ist/website/downloadArticle/cic/30/1/21","source_class":"PRIMARY_RESEARCH","publication_date":"2022","accessed_at":"2026-08-03","claims_supported":["Motion-picture cameras and human observers have different spectral sensitivities, making device-specific calibration necessary.","LED spectra can cause unnatural object-color reproduction, and objects can appear different under an LED wall and supplemental film lighting.","Equivalent abstract color coordinates or console values therefore cannot by themselves establish photographed-light equivalence.","Spectral measurements, camera characterization, and multi-channel-light optimization provide technically credible measurement approaches for a bounded physical trial."]}],"problem_evidence":{"support":"STRONG","rationale":"The problem is directly visible in first-party console documentation: ETC states that imported show data may play differently because consoles store and use data differently, and some effects or macros may not transfer. ETC's GDTF importer also omits color calibration and several fixture features and requires real-fixture verification. The camera study shows why steady-state command equivalence can still fail photographically. The evidence establishes existence and technical consequence, but not prevalence, incident frequency, labor loss, or monetary magnitude across film productions.","source_ids":["S1","S7","S8"]},"stakeholder_evidence":{"support":"MODERATE","rationale":"The GDTF group identifies MA Lighting, Robe, Vectorworks, ETC-adjacent console workflows, and other manufacturers as active adopters of unified lighting descriptions and explicitly states a need for dependable interoperability. These are credible potential implementers or standards stewards. However, no source expresses a commitment to adopt this stronger semantic cue-lifecycle contract, fund it, or accept its conformance oracle. Production-specific approval would still require the director of photography, gaffer, stage electrical supervisor, and safety representative.","source_ids":["S2","S3","S7"]},"prior_art":{"proximity":"ADJACENT_PRIOR_ART","closest_analogues":[{"name":"GDTF and MVR","similarity":"Open, manufacturer-supported representations separate fixture and scene information from individual applications and are implemented by multiple console, CAD, and visualization vendors.","remaining_difference":"They standardize device descriptions, physical/DMX attributes, patches, and scene exchange; the reviewed sources do not show a representation-independent cue state machine covering arm, trigger, hold, resume, conflict, cancel, freeze, abort, output confinement, and trajectory conformance.","source_ids":["S2","S3","S7"]},{"name":"USITT ASCII show-file interchange in ETC Eos","similarity":"Transfers cues and show data between console families and is a current alternative to rebuilding everything manually.","remaining_difference":"It is representation interchange rather than behavioral substitution; ETC explicitly warns of differing playback and omitted effects or macros, and no reusable black-box oracle is provided.","source_ids":["S1"]},{"name":"ANSI E1.11 DMX512-A and ANSI E1.17 ACN","similarity":"Established cross-manufacturer transport and network-control standards for entertainment lighting systems.","remaining_difference":"They govern communication architecture and protocol, not cinematographic meaning, emitted-light trajectories, lifecycle errors, reliable abort semantics, or adapter acceptance against a shared observational oracle.","source_ids":["S4","S5"]},{"name":"Open Lighting Architecture","similarity":"A practical implementation-independent API and gateway layer spanning multiple lighting protocols and hardware interfaces.","remaining_difference":"It abstracts protocol access but leaves cue semantics, physical equivalence, version governance, enrolled-output boundaries, and safety authority to applications.","source_ids":["S6"]},{"name":"Eos GDTF fixture-profile import","similarity":"Maps a portable device description into a console-native fixture profile and permits physical fixture verification.","remaining_difference":"It remains an import-and-correct workflow; documented omissions include color calibration and fixture behaviors, and it supplies neither cue-program substitutability nor cross-adapter trajectory tests.","source_ids":["S7"]}],"distinctive_claim_remaining":"For one predeclared cue program and event sequence, two independently implemented console-and-rig adapters can hide raw addressing yet produce equivalent semantic and photographed lighting trajectories, identical lifecycle/error behavior, zero unenrolled outputs, and an authority-approved abort-to-safe transition within tolerances fixed before testing; they must continue to do so after address renumbering, registration reordering, and capability-equivalent fixture reallocation. The claim fails if existing interchange already achieves this, if console-native escape hatches are required, if conformance-passing outputs remain materially different to the accountable cinematography team, or if physical fixture differences dominate representation effects.","confidence":"MODERATE"},"implementation_evidence":{"support":"MODERATE","rationale":"GDTF supplies portable device descriptions, OLA supplies multi-protocol APIs and gateways, and ETC demonstrates that GDTF can be mapped into a production console. These make a disconnected reference player plus one adapter feasible. Important gaps remain: ETC documents incomplete semantic translation; DMX does not guarantee delivery and is unsuitable for hazardous control; and photographed equivalence requires device- and camera-specific measurement. Production integration, timing under load, safe-state enforcement, adapter independence, and authority acceptance are untested.","source_ids":["S2","S4","S5","S6","S7","S8"]},"scores":{"meaningful_impact":{"score":4,"rationale":"If validated, the contract could reduce cue reconstruction, preserve approved looks during rig changes, and prevent unintended lighting outputs. Impact remains conditional because prevalence and realized production savings were not measured.","source_ids":["S1","S7","S8"]},"stakeholder_pull":{"score":3,"rationale":"Manufacturers and tool vendors visibly support lighting interoperability, but no identified party has requested or committed to this stronger cue-behavior contract.","source_ids":["S2","S3"]},"incremental_advantage":{"score":3,"rationale":"A shared behavioral oracle could improve on show-file import, GDTF/MVR exchange, transport standards, and manual verification, but superiority in migration time, defect detection, or photographed fidelity requires comparative testing.","source_ids":["S1","S3","S4","S7"]},"distinctiveness_plausibility":{"score":3,"rationale":"The cue-lifecycle, side-effect, and emitted-trajectory oracle was not found in the reviewed prior art, but many enabling layers are established and the bounded search cannot establish world novelty.","source_ids":["S2","S3","S4","S5","S6","S7"]},"technical_implementability":{"score":3,"rationale":"Open APIs, gateways, standard device descriptions, and console imports support a prototype; complete semantics, reliable timing, calibration, and physical equivalence remain material engineering risks.","source_ids":["S4","S6","S7","S8"]},"adoption_authority_feasibility":{"score":3,"rationale":"Credible vendor stewards and production authorities are identifiable, but decision rights are split among creative, electrical, safety, and production roles and no authorization was observed.","source_ids":["S2","S4","S7"]},"evidence_readiness":{"score":4,"rationale":"A small simulator test has explicit operations, comparators, representation transformations, and falsifiers and can be run before physical output. The decisive evidence still requires proprietary console access and an isolated physical trial.","source_ids":["S6","S7","S8"]},"safety_net_benefit":{"score":3,"rationale":"Output enrollment, unchanged-output rules, and abort precedence could add protection, but DMX delivery is not guaranteed and an abstraction defect could create new failure modes. It cannot be a hazardous-effects safety system.","source_ids":["S4","S7"]},"scalability":{"score":3,"rationale":"One reusable contract and suite could scale across adapters, but fixture calibration, console-specific features, physical placement, spectral response, and version stewardship create substantial per-rig work.","source_ids":["S2","S6","S7","S8"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"10K_TO_50K","scope":"Draft the fixed semantic contract and tolerances; build a simple reference player and one adapter; run disconnected exact-trace, generated-sequence, address-renumbering, registration-reordering, conflict, hold/resume, and abort tests.","confidence":"LOW","assumptions":["Approximately 3-8 specialist person-weeks across a lighting programmer, software engineer, and part-time cinematography/safety reviewers.","Existing OLA/GDTF components and an available console simulator are reused.","No physical rig, production shoot, or hazardous system is connected.","This is a resource-equivalent estimate; no buyer-specific labor-rate source was obtained."],"source_ids":["S2","S6","S7"]},"initial_deployment_startup":{"band_2026_usd":"50K_TO_250K","scope":"Harden two adapters, add instrumentation and camera/spectral calibration, conduct isolated-bay verification, document read-only diagnostics, and complete creative/electrical/safety review.","confidence":"LOW","assumptions":["Two console/rig implementations and one short cue program are in scope.","A prelight bay, fixtures, camera, photometric or spectral instrumentation, and operators are available rather than purchased.","Work excludes production automation, pyrotechnics, machinery, and formal certification of a safety-rated controller."],"source_ids":["S4","S7","S8"]},"operational_launch":{"band_2026_usd":"250K_TO_1M","scope":"Production-grade adapter packaging, redundancy and monitoring, expanded conformance coverage, integration with rehearsal and cue-calling workflows, training, staged acceptance across multiple rigs, and rollback procedures.","confidence":"LOW","assumptions":["Launch covers two console families and several fixture classes at one production organization.","Production approval requires additional rehearsals and engineering review.","A separate approved safety layer remains responsible for hazardous functions.","Patentability, licensing negotiations, and freedom-to-operate work are excluded."],"source_ids":["S2","S4","S5","S7","S8"]},"annual_recurring":{"band_2026_usd":"50K_TO_250K","scope":"Maintain adapters and the contract suite, qualify console/fixture firmware updates, curate calibration data, investigate divergences, and govern versions and deprecations.","confidence":"LOW","assumptions":["A small fractional engineering and lighting-operations team supports a limited adapter portfolio.","Major new console families, custom fixture characterization, and on-set support surges are excluded.","Costs vary strongly with the number of certified rigs and firmware releases."],"source_ids":["S2","S6","S7","S8"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"First-party console documentation directly records cross-console playback differences, omitted show data, incomplete GDTF translation, and the need for real-fixture correction; primary research establishes camera-specific physical divergence.","source_ids":["S1","S7","S8"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"MA Lighting, Robe, Vectorworks, the GDTF development group, and participating console/visualization vendors are identifiable interoperability stewards and implementers. For a trial, the production's DP/gaffer and electrical/safety representatives are identifiable authorizers, though their commitment has not been obtained.","source_ids":["S2","S3","S7"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"The remaining claim compares cue trajectories, lifecycle semantics, errors, enrolled-output confinement, and abort behavior across independent adapters under specified representation transformations and against current import/manual workflows.","source_ids":["S1","S3","S4","S6","S7"]},"bounded_next_evidence_step":{"status":"YES","reason":"A disconnected test with one short fixed program, one reference player, one console adapter, predeclared tolerances, explicit comparators, and representation transformations is bounded and reversible; only a separately authorized isolated-bay repeat follows.","source_ids":["S6","S7","S8"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The first test can remain disconnected. Any physical repeat is expressly conditional on DP/gaffer and electrical/safety approval, limited to enrolled non-hazardous lighting outputs, and stopped on divergence. DMX must not control hazardous effects or serve as the sole safety layer.","source_ids":["S4","S7"]},"credible_cost_scope_and_range":{"status":"UNCERTAIN","reason":"The work packages are bounded and grounded in available adapter, console, and measurement capabilities, but no buyer-specific rates, rig inventory, integration assessment, or vendor quotation was obtained; ranges are low-confidence resource-equivalent estimates.","source_ids":["S6","S7","S8"]}},"next_evidence_step":"Obtain written approval from the DP/gaffer and stage electrical/safety authorities for one disconnected program containing arm, timed fade, two concurrent semantic endpoints, hold/resume, a conflicting trigger, rejection while unarmed, and abort-to-safe. Before implementation, freeze expected state trajectories, error codes, enrolled endpoints, camera/photometric tolerances, timing tolerances, and abort deadline. Implement a deliberately simple reference player and one console adapter using GDTF/OLA where useful. Compare: (A) the reference player, (B) the adapter, and (C) the incumbent ASCII/GDTF-import-plus-manual-rebuild workflow. Run the same suite after address renumbering, registration reordering, and one capability-equivalent fixture reallocation. Require zero commands to unenrolled outputs, zero output change after rejected commands, complete lifecycle agreement, and trajectory differences within the frozen tolerances. Falsify the incremental claim if the incumbent already satisfies all criteria at equal or lower effort, representation changes produce no measurable divergence, the adapter needs raw-address or console-native escape hatches, or two implementations pass yet the accountable cinematography team finds the photographed result materially different. Only after simulator success and separate authorization should the test be repeated in an isolated prelight bay with approved instrumentation and an immediate de-energization rollback.","blocking_evidence":["No production, studio, console vendor, or standards body has committed to sponsor or adopt the proposed cue contract.","The prevalence and cost of cross-console cue reconstruction in film production are unmeasured.","No independent reference player or console adapter has been implemented or tested.","No predeclared cinematographic, spectral, timing, conflict, or abort tolerances have been approved.","It is unknown whether GDTF physical descriptions are sufficiently complete and accurate for the selected fixtures and cameras.","Reliable production behavior under packet loss, latency, concurrency, firmware changes, and resource contention is untested.","The authority and integration path for any production deployment have not been documented.","Legal terms for console APIs, show-file access, fixture data, and adapter distribution were not reviewed.","Buyer-specific resource estimates, vendor quotes, market size, realized impact, patentability, and freedom to operate remain unmeasured."],"research_disposition":"PARTNERED_RESEARCH_PROGRAM","world_novelty_boundary":"The eight-source bounded review found established transport standards, network-control architecture, fixture/scene interchange standards, protocol gateways, and console-specific import workflows, but did not find the complete cinematography-approved cue lifecycle plus emitted-trajectory conformance oracle described here. This is only a contrastive prior-art result: world novelty, patents, patentability, freedom to operate, market size, and realized impact were not measured.","arm":"COMPLETE_PROPOSAL_PORTFOLIO","candidate_version":0,"controller_recommendation":{"action":"STOP_EMPIRICAL_RESEARCH_NEEDED","repairable":false,"material_progress_observed":true,"progress_targets":["Secure a named production or vendor partner and written DP/gaffer/electrical/safety approval for the bounded disconnected trial.","Freeze the semantic endpoint model, lifecycle laws, error semantics, enrolled-output boundary, photographic tolerances, and abort deadline before observing results.","Implement an independent simple reference player and at least one console adapter without raw-address access from ordinary clients.","Run the blinded comparator against the incumbent import/manual-rebuild workflow and all three representation transformations.","Report conformance failures, false equivalence judgments, implementation effort, migration time, and photographed-output differences rather than only pass rates.","Obtain buyer-specific engineering, equipment, facility, and maintenance estimates before any adoption decision."],"reason":"Web evidence establishes the interoperability problem, credible enabling technology, adjacent standards, and a distinct falsifiable claim. It cannot determine whether semantic trajectories are sufficient, whether adapters preserve photographed behavior, whether the approach beats current workflows, or whether authorities will accept it. Those questions require proprietary console access, implementation, expert judgment, and controlled live measurement; under the controller rule, the evaluation therefore stops for empirical research."},"proposal_index":3}