{"id":"5ec4b526-9051-4a97-b09c-8827efc5685d","arxiv_id":"1908.11417","paper_version":1,"verdict":"UNVERDICTED","confidence":"HIGH","novelty_score":3.0,"correctness_risk":"low","formal_verification":"none","parameter_count":0,"one_line_summary":"A community white paper proposing a funded, coordinated follow-up network of brokers, TOMs, schedulers, and data reduction tools for the LSST alert era.","lead":"This white paper recommends a coordinated infrastructure of alert brokers, target observation managers, observatory scheduling interfaces, and data pipelines for time-domain and multi-messenger astronomy. It summarizes current projects and asks for under $20 million over ten years to complete and maintain them.","discovery_kind":"review","skeptic_critique":{"model":"deepseek-v4-flash","headline":"The load-bearing assumption is that observatories' institutional, policy, and scheduling differences can be resolved into a functioning real-time follow-up network; Section 2 itself calls this 'the larger challenge,' and only engineering tests, not routine operations, support it.","rationale":"The reader's weakest assumption matches the main load-bearing risk: institutional and policy differences among observatories must be resolved enough for a common follow-up network to function. The paper is a white paper without a falsifiable measurement, so UNVERDICTED is appropriate. The self-identified institutional challenge in Section 2 is precisely where the central claim is least secure: the architecture is described from workshops and supported by early AEON engineering, but not by operational multi-facility integration. A live-fire interoperability drill is the concrete test that would settle whether the concern lands. Separately, the Section 6 cost line items sum to more than the stated '<$20 million' if read literally (broker ~$16M, TOM $0.75M, coordination $0.5M, scheduler ~$1.0M, data reduction $3M), giving roughly $21M; this discrepancy is minor relative to the main concern and does not change the verdict, but it is an internal inconsistency worth correcting. No ad hominem or theatrical framing is warranted: the paper is transparent about its limitations and presents a coherent, well-referenced state-of-the-profession case.","tokens_in":8936,"tokens_out":6134,"duration_ms":62250,"concrete_test":"Run a full end-to-end interoperability drill under AEON: inject a simulated LIGO/Virgo alert (or LSST alert) into the TOM Toolkit and require programmatic triggering, dynamic scheduling, observation execution, automated data reduction, and feedback to the TOM at all three facilities (LCO, SOAR, Gemini) within a defined latency budget. Repeat the drill across semesters and report the fraction of leg failures and end-to-end latency; if the network cannot complete all legs reliably in regular operations, the feasibility assumption underlying the imperative is not met.","verdict_should_be":"UNCHANGED","load_bearing_attack":"The central claim is that a broker-TOM-API-scheduler-pipeline network is imperative and needs continued community support and funding. For that claim to hold, the components must actually integrate across facilities with different observing styles, allocation processes, and policies. The paper's Figure 1 architecture is plausible, and AEON has demonstrable pieces: the TOM Toolkit is used to trigger Gemini and Las Cumbres, Las Cumbres scheduler plans have been executed on SOAR engineering nights, and a SOAR Goodman reduction pipeline exists. But the only direct evidence of cross-facility integration is an engineering test on SOAR, not routine operations. Section 2 explicitly acknowledges that 'the larger challenge is negotiating the politics and sociology of the different organizations' and describes unresolved differences among SOAR/CTIO fixed-block scheduling, Gemini/LCO queue mode, and time-allocation options still under discussion. The funding recommendation therefore rests on an unproven feasibility assumption: that organizations can agree on APIs, ToO and duplication policies, shared TAC mechanics, and dynamic scheduling well enough that a single TOM can trigger and coordinate observations in real time. If that socio-technical integration stalls, the network does not function regardless of funding. This is a self-identified limitation, not a hidden flaw, but it is load-bearing because the 'imperative' is stated unconditionally.","agreement_with_reader":"agree"},"referee_report":{"model":"deepseek-v4-flash","summary":"This Astro2020 white paper argues that a functioning follow-up network—composed of alert brokers, Target Observation Managers (TOMs), observatory APIs and dynamic schedulers, automated data reduction pipelines, and archives—is imperative for LSST-era time-domain and multi-messenger astrophysics, and that these efforts require continued community support and funding. It presents a system architecture (Figure 1), reviews ongoing efforts such as AEON, the TOM Toolkit, and broker development, discusses policy and scheduling challenges, proposes a schedule tied to LSST's start of survey, and gives rough cost estimates. The paper is explicitly an advocacy document rather than a technical research paper, and it draws heavily on workshop reports and prior community recommendations.","tokens_in":9152,"tokens_out":4114,"duration_ms":40552,"significance":"If the proposed network is realized, it would allow the community to convert LSST's ~10 million nightly alerts into scientifically organized follow-up observations, enabling a broad range of time-domain and multi-messenger science. The paper's key strengths are its clear architectural overview, its grounding in a substantial number of related community efforts and white papers, its honest acknowledgment of the institutional and sociological challenges (Section 2), and its transparently rough cost estimate (Section 6). It also identifies concrete existing components, including the TOM Toolkit, the Las Cumbres scheduler executed on SOAR engineering nights, the SOAR Goodman reduction pipeline, and AMON, which lend credibility to the proposed system's partial feasibility. As a state-of-the-profession white paper, the bar for evidence is appropriately lower than for a technical paper, and the central argument is coherent and reasonably supported.","major_comments":[{"comment":"The listed line items do not sum to the stated total. Broker development is $16M/10yr; TOM Toolkit is $75k/yr, or $0.75M/10yr; observation coordination is $0.5M/3yr; scheduler toolkit is $0.5M/3yr plus $75k/yr maintenance, or at least $1.025M/10yr; and data reduction tools are \"at least $300k/yr\", or at least $3M/10yr. These items sum to at least $21.275M over ten years, which is inconsistent with the sentence \"total estimated cost over ten years is less than $20 million.\" Because the recommendation explicitly relies on the effort being a small project, this arithmetic discrepancy is load-bearing and should be corrected, with the scope of included items stated precisely.","section":"Section 6"},{"comment":"The paper acknowledges in Section 2 that \"the larger challenge is negotiating the politics and sociology of the different organizations\" and describes unresolved differences among SOAR/CTIO fixed-block scheduling, Gemini/LCO queue mode, and time-allocation options still under discussion. Yet Section 7 states the funding imperative unconditionally. The functional network on which the recommendation rests cannot operate if these governance and policy differences are not resolved. The paper should either qualify the imperative (e.g., conditional on a successful coordination process) or propose a concrete governance mechanism, with milestones and decision points, to de-risk the investment. As written, the unconditional recommendation rests on an assumption the paper itself identifies as unresolved.","section":"Sections 2 and 7"}],"minor_comments":[{"comment":"The title \"Infrastructure and Strategies for Time Domain and MMA and Follow-Up\" is grammatically awkward; \"Time Domain and Multi-Messenger Astrophysics Follow-Up\" would be clearer. The abstract repeats the same phrasing.","section":"Title and Abstract"},{"comment":"The text contains \"the astronomical community?s best interest\" with a question mark in place of an apostrophe, presumably a LaTeX encoding error. Also, the phrase \"the technology drivers listed in § 3\" should read \"listed in Sec. 3\" for consistency.","section":"Section 2"},{"comment":"The sentence \"The LSST will generate∼ 10 million alerts per night\" has a missing space or a typographical issue around the approximate sign; it should read \"generate ~10 million alerts per night.\"","section":"Section 4"},{"comment":"The cost list is presented as bullet points without a breakdown of the assumed duration for each item; adding a small table with annual and total costs would improve transparency and prevent the arithmetic issue noted above.","section":"Section 6"},{"comment":"A few references are incomplete or inconsistently formatted, e.g., \"Reichart, D., et al. 2005, arXiv:0502429\" lacks the usual four-digit year format and the `arXiv` identifier style; the Bellm LDM reference would benefit from a document number or access date.","section":"References"}],"recommendation":"major_revision","confidential_remarks":"This is a community white paper, and I have judged it accordingly: the absence of a derivation or data analysis is not a flaw. The two major comments are both fixable within the scope of the manuscript: correcting the cost arithmetic and qualifying or de-risking the unconditional imperative. The paper's extensive list of related white papers and its honest treatment of the institutional challenge are notable strengths. I see no reason to reject, but the internal cost inconsistency and the gap between the acknowledged governance challenge and the unconditional recommendation should be addressed before acceptance."},"author_rebuttal":null,"desk_editor":{"model":"deepseek-v4-flash","letter":"Colleague,\n\nThis is a white paper, not a research paper, and the right way to read it is as a state-of-the-profession argument for funding a follow-up network for LSST-era and multi-messenger astronomy. It has no new data or derivations, but it does something useful: it pulls together the architecture (brokers, TOMs, observatory APIs/schedulers, pipelines) from the earlier Najita report and 2017 NOAO workshop, and adds a current-status report on real pieces—TOM Toolkit with Gemini triggers, LCO scheduler tests on SOAR engineering nights, a SOAR Goodman reduction pipeline, and AEON's plans. The cost estimate is explicitly rough and lands under $20M over 10 years. The paper is clear, honestly flags its own uncertainties, and cites the relevant prior work. No red flags.\n\nThe soft spot is one the authors themselves point to. In Section 2 they say the larger challenge is 'negotiating the politics and sociology of the different organizations'—and that is the load-bearing assumption. The only direct cross-facility integration shown is an engineering test, not routine operations. If the institutions don't actually align their policies, TACs, and scheduling, the technical pieces won't form a functioning network even with funding. The word 'imperative' in the abstract is therefore a bit stronger than the evidence currently supports. That said, this is not a hidden flaw; it's an honest limitation, and for a white paper it's acceptable.\n\nThe citation pattern is fine. The list of 40+ related white papers is a useful resource. There is no math or data to check, so 'soundness' here is about whether the argument is coherent and the facts are referenced. They are.\n\nMy recommendation: engage with it. If you're writing anything about time-domain infrastructure or LSST follow-up, this is a citable, sober summary. For peer review, I'd send it to a referee with knowledge of the observatory landscape; it deserves serious consideration rather than desk rejection, because it's a planning document the community can use. Just don't expect a scientific breakthrough—it's not trying to be one.","headline":"A clear, honest state-of-the-profession white paper that consolidates the case for a follow-up network; its main soft spot is the unproven assumption that institutions will cooperate, which the authors themselves flag.","tokens_in":10050,"tokens_out":2576,"would_cite":true,"duration_ms":25967,"reading_group":"maybe","serious_thinker":"yes","would_accept_peer_review":true},"rs_alignment":null,"lean_confirmation":null,"pith_extraction":{"msc":[],"pacs":[],"model":"deepseek-v4-flash","headline":"The paper argues that the value of LSST and multi-messenger astronomy depends on completing an automated follow-up network of brokers, target managers, schedulers, and pipelines.","keywords":["time-domain astronomy","multi-messenger astrophysics","alert brokers","target observation managers","dynamic scheduling","observatory APIs","LSST follow-up","transient follow-up networks"],"falsifier":"Measure on a live engineering night the end-to-end latency from an LSST-style alert to a successfully executed observation and reduced spectrum on an AEON telescope; if by the 2023 survey start that chain cannot run without human intervention at typical target-of-opportunity cadence, the paper's central claim fails.","tokens_in":8730,"feed_emoji":"🔭","tokens_out":6378,"duration_ms":60672,"temperature":0.7,"pith_summary":"This paper argues that the success of time-domain and multi-messenger astronomy in the 2020s depends on completing a community-wide follow-up network that turns survey alerts into observations automatically. The authors describe a three-stage system: alert brokers that aggregate and classify events, Target Observation Managers (TOMs) that prioritize targets and track data, and observatory interfaces with dynamic schedulers, data reduction pipelines, and archives. They estimate that building and maintaining these components for the decade of the LSST survey would cost less than $20 million, and they recommend that national observatories or a new institute coordinate the effort with professional software developers leading open-source projects. The paper's central claim is that this infrastructure is both necessary and achievable if institutions cooperate.","feed_headline":"LSST alert floods need a shared follow-up network","feed_subtitle":"Brokers, observation managers, and schedulers must link by 2023 or transients go unstudied.","key_machinery":"The load-bearing mechanism is the alert-to-data pipeline diagram: brokers classify and filter raw alert streams into science-ready event lists; TOMs let teams match those events to telescopes, manage priorities, and ingest reduced data; observatory APIs and dynamic schedulers accept programmatic observation requests; and automated reduction pipelines plus archives close the loop by returning rapid feedback that updates priorities. The paper treats this as one integrated system rather than separate tools, and it points to the TOM Toolkit, the AEON APIs, and queue schedulers as working seeds of that system. The identity doing the work is the network itself: each stage reduces human effort so that the roughly ten million alerts per night from LSST can be reduced to the small number of targets worth interrupting telescopes.","core_discovery":"The paper's central claim is that the floods of alerts from LSST and the time-critical needs of multi-messenger events such as neutron-star mergers and interstellar objects cannot be handled by human review and ad hoc phone calls; they require a programmatic network of brokers, TOMs, observatory APIs, schedulers, and reduction pipelines. It asserts that these components already exist in pilot form—ZTF alert processing, the TOM Toolkit, AMON, and the AEON initiative coupling Las Cumbres, SOAR, and Gemini—and that the main remaining work is integration, completion, and sustained maintenance. Following earlier community recommendations, it concludes that a minimally functioning system should be in place when the LSST main survey begins in 2023, with ongoing funding below $20 million over ten years. The authors state that the technical interfaces are relatively straightforward; the decisive barrier is negotiating the politics and sociology of different observatories.","pith_inferences":["A natural extension of the proposed architecture is that space-based missions with low-latency alerts could join the same broker-TOM-API chain if they adopt common alert standards, broadening the network beyond ground-based observatories.","If the paper's cost estimates hold, the entire follow-up network is within reach of a single small ground-based project budget, which makes the policy and institutional coordination rather than money the likely bottleneck.","A testable corollary is that end-to-end follow-up latency, from alert to reduced spectrum, will become the key performance metric for the network; publishing such latencies across facilities would make the system's readiness measurable."],"forward_implications":["By 2023 a minimally functioning broker–TOM–observatory chain should be operational, with early versions of every component.","If funded, the network should let a single proposal request time on multiple facilities and let telescopes refuse redundant observations using explicit duplication policies.","The same tools will improve efficiency for static-source surveys, multi-wavelength campaigns, and queue observing, not just rapid transients.","Responsibility for completing and maintaining the system must sit with an institution involved in follow-up, such as the future national observatory center or a new multi-messenger institute.","Without continued funding for maintenance, the system will degrade over the roughly ten-year LSST survey and the lifetime of multi-messenger facilities."],"supporting_citations":[{"why":"Defines LSST and its alert production, establishing the scale the follow-up network must handle.","marker":"Ivezić et al., 2008"},{"why":"Documents ZTF alert experiences and LSST alert distribution plans that set the input rate for brokers.","marker":"Bellm et al., 2019"},{"why":"Reports the GW170817 gravitational-wave electromagnetic campaign, the multi-messenger case the network must support.","marker":"Abbott et al., 2017"},{"why":"Provides the neutrino-blazar association motivating multi-messenger follow-up from a second messenger.","marker":"IceCube Collaboration et al., 2018"},{"why":"Describes the 'Oumuamua follow-up campaign, an example of rapid multi-facility response to a newly discovered object.","marker":"Meech et al., 2017"},{"why":"National Academies recommendation that NSF facilities coordinate to optimize LSST follow-up.","marker":"Elmegreen et al., 2015"},{"why":"Community workshop report defining the follow-up system concept and science requirements.","marker":"Najita et al., 2016"},{"why":"Describes the TOM Toolkit software that provides the common target-management layer.","marker":"Street et al., 2018"},{"why":"Presents AMON, an operating broker/TOM system for multi-messenger alerts and triggers.","marker":"Ayala Solares et al., 2019"},{"why":"Provides an example duplication policy used to reduce redundant follow-up observations.","marker":"Gemini Observatory, 2019"}],"fun_headline_variants":["Alert floods demand a network, not phone trees","Time-domain and MMA need linked brokers and TOMs","By 2023, follow-up must be programmatic or lose transients","Follow-up bottleneck: observatory politics, not code"],"cache_read_input_tokens":3200,"weakest_assumption_plain":"The load-bearing premise is that the involved observatories can settle their differences in policy, scheduling culture, and time-allocation rules well enough to cooperate as one network; the paper itself says the larger challenge is negotiating the politics and sociology of the different organizations.","fun_headline_variants_meta":{"raw":{"variants":["Alert floods demand a network, not phone trees","Time-domain and MMA need linked brokers and TOMs","By 2023, follow-up must be programmatic or lose transients","Follow-up bottleneck: observatory politics, not code"]},"model":"deepseek-v4-flash","effort":"low","cost_usd":0.000407,"raw_usage":{"total_tokens":2104,"prompt_tokens":926,"completion_tokens":1178,"prompt_tokens_details":{"cached_tokens":384},"prompt_cache_hit_tokens":384,"prompt_cache_miss_tokens":542,"completion_tokens_details":{"reasoning_tokens":1110}},"tokens_in":542,"tokens_out":1178,"duration_ms":11392,"temperature":1.0,"reasoning_tokens":1110,"cache_read_input_tokens":384,"cache_creation_input_tokens":0},"cache_creation_input_tokens":0},"created_at":"2026-08-14T10:14:32.090682+00:00","model_set":{"reader":"deepseek-v4-flash"},"falsifier":"Measure on a live engineering night the end-to-end latency from an LSST-style alert to a successfully executed observation and reduced spectrum on an AEON telescope; if by the 2023 survey start that chain cannot run without human intervention at typical target-of-opportunity cadence, the paper's central claim fails.","supporting_citations":[{"cited_title":"P., et al","cited_arxiv_id":null,"evidence_quote":"Reports the GW170817 gravitational-wave electromagnetic campaign, the multi-messenger case the network must support."},{"cited_title":"J., et al","cited_arxiv_id":null,"evidence_quote":"Describes the 'Oumuamua follow-up campaign, an example of rapid multi-facility response to a newly discovered object."},{"cited_title":"General-Purpose Software for Managing Astronomical Observing Programs in the LSST Era","cited_arxiv_id":"1806.09557","evidence_quote":"Describes the TOM Toolkit software that provides the common target-management layer."}],"review_version":1}