{"schema_version":1,"research_id":"eoa_inverse_innovation_exp06_external_evaluation_20260803","source_assessment_id":"predictive_residual_processing__aviation_aeronautics:P4:v0","cell_id":"predictive_residual_processing__aviation_aeronautics","search_queries":["site:faa.gov JO 7110.65 transfer of control handoff controller coordination automated handoff","site:eurocontrol.int OLDI coordination transfer messages controller handover system coordination SYSCO","air traffic controller handoff information omission workload human factors study sector transfer","FAA ERAM electronic flight data handoff coordination controller amendments","site:asrs.arc.nasa.gov air traffic controller handoff coordination amendment incident handoff receiving controller","site:faa.gov air traffic controller handoff human factors simulation coordination errors report","site:ntrs.nasa.gov air traffic controller sector handoff coordination workload study","site:bls.gov air traffic controllers median pay 2025"],"sources":[{"source_id":"S1","title":"FAA Order JO 7110.65: Chapter 2, General Control—Flight Plan Data and Amendments","publisher":"Federal Aviation Administration","url":"https://www.faa.gov/air_traffic/publications/atpubs/atc_html/chap2_section_2.html","source_class":"OFFICIAL_GUIDANCE","publication_date":"Current online edition accessed 2026-08-03","accessed_at":"2026-08-03","claims_supported":["Computer-message transfers require acknowledgment or verification where automatic acknowledgment is unavailable.","Amended flight-plan data must be forwarded, and interfacility data not passed automatically requires manual coordination.","FAA notes that failure to enter amendment data can leave the next controller with incorrect route information."]},{"source_id":"S2","title":"FAA Order JO 7110.65: Chapter 5, Radar—Transfer of Radar Identification","publisher":"Federal Aviation Administration","url":"https://www.faa.gov/air_traffic/publications/atpubs/atc_html/chap5_section_4.html","source_class":"OFFICIAL_GUIDANCE","publication_date":"Current online edition accessed 2026-08-03","accessed_at":"2026-08-03","claims_supported":["The receiving controller must verify association between the target and automated data block before acceptance.","Necessary restrictions must be issued and observed across a handoff.","Automated transfer and fourth-line coordination already exist but depend on facility directives or letters of agreement, with other information coordinated by other methods."]},{"source_id":"S3","title":"En Route Automation Modernization (ERAM)","publisher":"Federal Aviation Administration","url":"https://www.faa.gov/air_traffic/technology/eram","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"2025-09-15","accessed_at":"2026-08-03","claims_supported":["ERAM processes and displays surveillance and flight data at all 20 continental U.S. en-route centers.","ERAM provides controller-to-controller interfaces, cross-boundary data sharing, and automated handoffs with NAV CANADA.","ERAM supports realistic high-fidelity training and offers a plausible technical host or comparator environment."]},{"source_id":"S4","title":"Capital Investment Plan FY 2018–2022, Appendix B—ERAM Enhancement 2","publisher":"Federal Aviation Administration","url":"https://www.faa.gov/air_traffic/publications/cip/files/FY18-22/FY18-22_CIP_Appendix_B_Nov_2017.pdf","source_class":"OFFICIAL_ORGANIZATION_DATA","publication_date":"2017-11","accessed_at":"2026-08-03","claims_supported":["FAA identified expansion of automated flight-data and control coordination with NAV CANADA as an investment objective.","FAA expressly expected automated handoffs to reduce controller workload and possibly delays by reducing handoff phone calls.","FAA is an identifiable adopter, funder, and authorization authority for en-route automation changes."]},{"source_id":"S5","title":"EUROCONTROL Specification for On-Line Data Interchange (OLDI)","publisher":"EUROCONTROL","url":"https://www.eurocontrol.int/publication/eurocontrol-specification-line-data-interchange-oldi","source_class":"STANDARD","publication_date":"2026-04-24","accessed_at":"2026-08-03","claims_supported":["OLDI already standardizes automated notification, coordination, revision, abrogation, communication transfer, dialogue coordination, and supplementary exchanges between ATC units.","Automated coordination before transfer is established international practice rather than a new category.","The current specification complements binding European automated-coordination requirements."]},{"source_id":"S6","title":"Effect of Dynamic Sector Boundary Changes on Air Traffic Controllers","publisher":"NASA Technical Reports Server","url":"https://ntrs.nasa.gov/citations/20100036786","source_class":"PRIMARY_RESEARCH","publication_date":"2010","accessed_at":"2026-08-03","claims_supported":["A human-in-the-loop study found a 16.9% workload increase during dynamic sector-boundary changes.","The workload increase correlated with the number of aircraft handoffs and sector-volume change.","Handoffs can materially contribute to controller workload, although this study did not isolate repeated handoff content or omission errors."]},{"source_id":"S7","title":"Research, Development & Human Factors Laboratory—DESIREE Simulation Platform","publisher":"Federal Aviation Administration","url":"https://www.faa.gov/about/office_org/headquarters_offices/ang/offices/tc/activities/rdhfl","source_class":"OFFICIAL_PRODUCT_DOCUMENTATION","publication_date":"Not stated","accessed_at":"2026-08-03","claims_supported":["FAA operates a programmable simulation platform for rapid ATC prototyping and human-factors experimentation.","DESIREE emulates multiple en-route and terminal sectors, automatic handoff, and transfer of control.","The laboratory can record scripted events and measure controller visual scanning and workload, making the proposed non-operational comparison technically bounded."]},{"source_id":"S8","title":"Air Traffic Controllers: Occupational Outlook Handbook","publisher":"U.S. Bureau of Labor Statistics","url":"https://www.bls.gov/ooh/transportation-and-material-moving/air-traffic-controllers.htm","source_class":"GOVERNMENT_OR_REGULATOR","publication_date":"2025-08-28","accessed_at":"2026-08-03","claims_supported":["Air traffic controllers transfer and accept control between sectors and centers.","The May 2024 median controller wage was $144,580, and the federal-government median was $154,000.","Controller participation is a material resource component in simulation, training, and deployment estimates."]}],"problem_evidence":{"support":"MODERATE","rationale":"The problem class visibly exists: FAA procedures require accurate forwarding, acknowledgment, manual coordination of data not transferred automatically, and special handling of restrictions and amendments; FAA explicitly warns that omitted computer amendments can leave the next controller with incorrect route information. NASA simulation evidence also links handoff counts to workload. However, none of the eight sources measures the candidate's narrower premise that repeated expected content commonly buries temporary constraints or annotations during ordinary sector-to-sector handoffs, so prevalence and attributable safety impact remain unverified.","source_ids":["S1","S2","S6"]},"stakeholder_evidence":{"support":"MODERATE","rationale":"FAA is an identifiable adopter, funder, procedure authority, and operator of both ERAM and an appropriate human-factors laboratory. Its investment plan expressly sought reduced handoff calls and workload through automated coordination, while the ERAM program emphasizes seamless inter-center data sharing. This is strong pull for automated coordination generally, but no source requests a baseline-fingerprint-plus-typed-residual interface specifically.","source_ids":["S3","S4","S7"]},"prior_art":{"proximity":"ESTABLISHED_PRACTICE","closest_analogues":[{"name":"FAA automated information transfer, flight-plan amendments, and fourth-line coordination","similarity":"Already passes automated shared flight data, forwards revisions, treats computer responses as acknowledgment in defined circumstances, requires manual coordination for data not passed automatically, and transfers restrictions or other control information through prescribed channels.","remaining_difference":"The candidate adds an explicit multi-source baseline fingerprint, typed missing/disputed/stale residuals, complete reconstructed-state review, protected-field acknowledgments, independent complete-handoff sampling, and a residual-mass fallback rule.","source_ids":["S1","S2"]},{"name":"EUROCONTROL OLDI automated coordination and revision","similarity":"Standardizes inter-unit notification, coordination, revision, abrogation, dialogue, and transfer messages before responsibility changes; this substantially overlaps the candidate's semantic change-exchange concept.","remaining_difference":"The reviewed landing page does not establish the candidate's full semantic-baseline checksum, consequence-weighted residual ordering, independently sampled reconstruction audit, or controller-facing full-state reconstruction requirement.","source_ids":["S5"]},{"name":"ERAM automated cross-boundary handoffs and shared flight-data displays","similarity":"A deployed product processes common surveillance and flight data, supports controller interaction and data sharing, and automates handoffs, including with NAV CANADA.","remaining_difference":"Public documentation does not show an auditable residual codec that verifies identical semantic baselines and reconstructs a complete handoff from typed residuals with protected bypasses.","source_ids":["S3","S4"]}],"distinctive_claim_remaining":"Relative to FAA AIT/ERAM, OLDI, a complete-state checklist, and simple revision highlighting, a handoff interface that permits residual mode only after a multi-source semantic-baseline fingerprint match—and then requires complete-state reconstruction, protected-residual acknowledgment, independent full-handoff audits, and automatic decompression—will reduce coordination interaction load by a practically material amount without increasing state-reconstruction errors, protected-information omissions, incompatible-baseline acceptance, or recovery time after injected faults. Each control is causal only if removing it measurably worsens one of those outcomes.","confidence":"HIGH"},"implementation_evidence":{"support":"MODERATE","rationale":"Technical feasibility is credible at simulation stage: ERAM already exposes shared surveillance and flight data and automated handoffs, while DESIREE supports programmable multi-sector handoff experiments, scripted faults, recording, and workload measurement. Workflow and authority feasibility are constrained: FAA rules allocate duties to transferring and receiving controllers and require facility directives or letters of agreement for automated transfer practices. A study interface can therefore be built without operational authority, but live integration, access to authoritative clearance history and annotations, semantic versioning across systems, cybersecurity, records treatment, human-subject approvals, safety assurance, training, and procedural authorization are not established by public evidence.","source_ids":["S1","S2","S3","S7"]},"scores":{"meaningful_impact":{"score":4,"rationale":"A missed restriction or incorrect reconstructed route can affect a safety-critical transfer, and handoffs contribute measurably to workload. Candidate-specific incidence and realized impact are unmeasured.","source_ids":["S1","S2","S6"]},"stakeholder_pull":{"score":4,"rationale":"FAA has funded automated handoff coordination to reduce calls and workload and operates the relevant automation and simulation infrastructure, but has not expressed demand for this exact residual architecture.","source_ids":["S3","S4","S7"]},"incremental_advantage":{"score":2,"rationale":"Automated amendment, acknowledgment, exception coordination, and handoff workflows are established. The remaining advantage depends on whether extra synchronization and audit controls outperform simpler highlighting or full-state review.","source_ids":["S1","S2","S5"]},"distinctiveness_plausibility":{"score":3,"rationale":"The combined semantic fingerprint, explicit reconstruction, protected residual acknowledgment, independent raw audit, and decompression package is contrastive and testable, but individual functions are adjacent to existing coordination standards and practices.","source_ids":["S1","S2","S5"]},"technical_implementability":{"score":4,"rationale":"Existing shared-data automation and a programmable FAA multi-sector simulator make an offline prototype feasible. Production-grade semantic synchronization across authoritative systems remains unproven.","source_ids":["S3","S7"]},"adoption_authority_feasibility":{"score":2,"rationale":"FAA is clearly identifiable, but any operational change must fit controller responsibilities, facility directives, letters of agreement, safety assurance, and training. No sponsoring facility or signed authorization was found.","source_ids":["S2","S3","S4"]},"evidence_readiness":{"score":2,"rationale":"Procedures, infrastructure, and general workload evidence are available, but no comparative result supports the candidate's incremental performance claim and no prevalence dataset establishes the proposed failure mechanism.","source_ids":["S1","S2","S6","S7"]},"safety_net_benefit":{"score":4,"rationale":"Baseline matching, complete reconstruction, protected-field bypass, acknowledgment, and fallback directly address known transfer and amendment hazards, but their reliability and possible automation-bias effects require simulation.","source_ids":["S1","S2","S7"]},"scalability":{"score":2,"rationale":"ERAM offers a common platform across 20 en-route centers, but facility-specific directives, agreements, adaptations, annotations, training, and safety cases make scaling materially harder than replicating ordinary software.","source_ids":["S2","S3","S4"]}},"score_confidence":"MODERATE","costs":{"first_evidence":{"band_2026_usd":"250K_TO_1M","scope":"Freeze the schema and safety rules; build a non-operational prototype; create up to 24 scripted scenarios; recruit approximately 12–18 qualified or recently retired controllers; run counterbalanced high-fidelity sessions; and complete human-factors and safety analyses.","confidence":"MODERATE","assumptions":["Existing DESIREE-like simulation infrastructure is available without purchasing an operational ATC system.","The estimate includes roughly 1–3 staff-years across software, human factors, scenario design, statistics, and safety review.","Controller time is costed above direct wage to cover scheduling, benefits, preparation, and study overhead.","No live NAS data feed or operational certification is included."],"source_ids":["S7","S8"]},"initial_deployment_startup":{"band_2026_usd":"5M_TO_25M","scope":"Develop and assure a production-quality shadow-mode implementation for one en-route facility, including adapters, cybersecurity, logging, human-factors validation, safety case, procedure design, training materials, and site acceptance.","confidence":"LOW","assumptions":["Deployment remains shadow-only and cannot alter control transfer or suppress authoritative records.","Integration touches safety-critical ERAM workflows and multiple authoritative data sources.","Facility-specific adaptation, directives, and controller training are required.","No first-party cost estimate or vendor quotation was found."],"source_ids":["S2","S3","S4"]},"operational_launch":{"band_2026_usd":"OVER_25M","scope":"Obtain operational authorization and deploy across the 20 continental U.S. en-route centers, including national engineering, redundant infrastructure, facility adaptations and agreements, training, safety assurance, phased rollout, and rollback capability.","confidence":"LOW","assumptions":["All 20 ERAM centers are in scope.","Launch requires national and site-level testing comparable in rigor to other safety-critical ATC automation changes.","Existing ERAM infrastructure can be extended but not treated as a zero-cost host.","This is a resource-equivalent planning band, not a procurement estimate."],"source_ids":["S2","S3","S4"]},"annual_recurring":{"band_2026_usd":"5M_TO_25M","scope":"Nationwide software support, cybersecurity and configuration management, model/template governance, regression simulation, audit sampling, recurrent training, incident review, and facility-specific adaptation maintenance.","confidence":"LOW","assumptions":["A small national engineering and assurance team plus distributed facility support is maintained.","Every material baseline or procedural change triggers regression and configuration review.","Controller audit and training time remains a recurring cost.","No public evidence establishes actual maintenance pricing."],"source_ids":["S2","S3","S8"]}},"verified_pipeline_gates":{"externally_supported_problem":{"status":"YES","reason":"Official procedures show that amendments, restrictions, acknowledgments, target-data association, and nonautomated coordination are consequential, while primary simulation research connects handoff volume to workload. The exact prevalence of buried residual information remains an evidence gap rather than negating the problem class.","source_ids":["S1","S2","S6"]},"externally_credible_adopter_or_authorizer":{"status":"YES","reason":"FAA operates ERAM, controls the governing procedures, has funded automated coordination to reduce handoff calls and workload, and maintains a laboratory capable of the proposed simulation.","source_ids":["S3","S4","S7"]},"distinct_testable_incremental_claim":{"status":"YES","reason":"The claim can be compared against both the established complete-handoff workflow and simple field-revision highlighting using reconstruction, omission, mismatch-detection, fallback, and interaction-load measures. Existing practice makes the expected advantage uncertain but does not make the contrast untestable.","source_ids":["S1","S2","S5"]},"bounded_next_evidence_step":{"status":"YES","reason":"A non-operational, preregistered, three-condition simulation with no more than 24 scenarios can be executed on existing rapid-prototyping infrastructure with scripted failures and measurable controller behavior.","source_ids":["S7"]},"no_unresolved_safety_or_authority_stop":{"status":"YES","reason":"The immediate step can remain entirely non-operational and preserve existing controller authority. FAA rules and facility agreements would remain controlling; operational use is explicitly outside this evidence step.","source_ids":["S2","S7"]},"credible_cost_scope_and_range":{"status":"UNCERTAIN","reason":"Public evidence establishes simulator availability, nationwide ERAM scale, procedural integration burden, and controller labor value, supporting order-of-magnitude bands. It does not provide a directly comparable procurement, integration estimate, or vendor quote.","source_ids":["S2","S3","S7","S8"]}},"next_evidence_step":"With an FAA or equivalent ANSP human-factors partner, preregister one counterbalanced high-fidelity simulation involving approximately 12–18 qualified or recently retired controllers and no more than 24 sector-transfer scenarios. Compare (A) the established complete-handoff workflow, (B) simple revision highlighting on the existing full-state display, and (C) the proposed fingerprint-gated residual workspace. Freeze scenario truth, baseline contents, protected classes, validity windows, acknowledgment semantics, residual weighting, fault injections, and fallback rules before exposure. Include nominal traffic, amendments, temporary altitude and speed restrictions, reroutes, controller remarks, invalid sources, emergency status, fingerprint mismatch, sequence loss, missing acknowledgment, and residual overload. Primary measures are complete-state reconstruction error, protected-information omission, false addition, pending-obligation acknowledgment, incompatible-baseline acceptance, fault-detection and fallback latency, coordination speech time, interaction count, NASA-TLX workload, and recovery accuracy. Independently score full records rather than only system-selected residuals. The incremental claim is falsified by any accepted incompatible baseline, any protected-information omission attributable to residual mode, reconstruction performance worse than either comparator, failure to trigger on any injected mismatch or sequence fault, or less than a preregistered 15% reduction in coordination speech or interactions versus full handoff without improvement over simple highlighting. A favorable result authorizes only a later non-operational shadow study, not operational deployment.","blocking_evidence":["No measured prevalence of consequential information being obscured by repeated expected content in ordinary sector transfers.","No comparative human-in-the-loop evidence that semantic residual reconstruction outperforms simple revision highlighting or a complete-state checklist.","No evidence that controllers reliably understand fingerprint acknowledgment, reconstructed expected fields, and residual silence under workload.","No empirical rates for protected-information omission, automation bias, false fallback, mismatch detection, or recovery after source and sequence faults.","No sponsoring facility, controller-participant commitment, data-access agreement, human-subject approval, or operational safety authority endorsement for the specific study.","No first-party engineering estimate for ERAM integration, certification, training, or recurring assurance costs."],"research_disposition":"PARTNERED_RESEARCH_PROGRAM","world_novelty_boundary":"This bounded eight-source search establishes only that automated coordination, revision messaging, acknowledgment, and handoff data sharing are mature practices and that the proposed governance bundle retains a testable contrast. It does not measure world novelty, patentability, freedom to operate, market size, or realized impact; it is not a patent or comprehensive literature search, and unpublished facility procedures, vendor functions, defense systems, and proprietary ANSP implementations remain outside the evidence boundary.","arm":"COMPLETE_PROPOSAL_PORTFOLIO","candidate_version":0,"controller_recommendation":{"action":"STOP_EMPIRICAL_RESEARCH_NEEDED","repairable":false,"material_progress_observed":true,"progress_targets":["Secure an FAA or equivalent ANSP human-factors partner and written authorization for a non-operational simulation.","Obtain or construct validated handoff scenarios with authoritative scenario truth and independent full-record scoring.","Run the preregistered three-condition comparison and quantify reconstruction, protected omissions, mismatch detection, fallback behavior, workload, and interaction savings.","Demonstrate an incremental benefit over simple revision highlighting, not merely parity with current automated amendment practice.","Produce a bottom-up engineering and assurance estimate for one-site shadow integration before any deployment inquiry."],"reason":"Web evidence verifies the general problem class, a credible authority and test environment, established close prior art, and a bounded testable contrast. It cannot answer the decisive question: whether the additional semantic synchronization, reconstruction, audit, and fallback machinery improves controller performance relative to simpler established interfaces without introducing new omission or automation-bias risks. That evidence requires controller simulation, proprietary or constructed operational scenarios, and live human performance measurement; therefore further bounded web research is insufficient."},"proposal_index":4}