How to Write a Source-Linked Launch Evidence Brief

An editor asks, “What can we responsibly report from this launch evidence?” A folder of screenshots and links leaves the hardest work unfinished: deciding which sentence each source actually supports.

A useful brief starts with a bounded claim, separates observation from interpretation, and gives the next reader a short path back to the source. It also says what has not been established. The aim is an accountable handoff that another person can inspect without rebuilding your research from scratch.

Below is a proposed brief format and a completed source-reading example. The example reports what identified sources say. It does not claim that the author of this guide independently reprocessed satellite frames or ran a detector validation.

Lead with a reportable statement and its boundary

Write two sentences before collecting more material. The first should say what the strongest appropriate source establishes. The second should identify the limitation most likely to change the reader’s interpretation.

For a historical Artemis I source-reading brief, the opening could be:

“NASA reported that Artemis I launched from Kennedy Space Center’s Launch Pad 39B on November 16, 2022 at 1:47 a.m. EST. A separate CIMSS article interprets satellite imagery of the launch; this brief summarizes those sources without independently reprocessing their imagery.”

Link the NASA launch release and CIMSS analysis at the corresponding statements. This opening is deliberately specific about who reported what. It avoids converting a source-reading exercise into an original detection claim.

Give the brief an identity

Record a brief ID, title, author or responsible desk, preparation time, and version. Include the question the brief answers and the intended use. A background explainer, a breaking-news alert, and an image caption can require different levels of evidence and review.

List the exact source URLs and their access times. Add a stable event or record ID when available. Preserve snapshots where permitted, with filenames or hashes in your research record. This allows a later reviewer to distinguish a changed source from a changed interpretation.

Do not fill in a reviewer or approval time until that action has happened. “Prepared,” “checked,” and “approved for publication” describe different work. A template should not manufacture authority through prefilled status fields.

Build the claim table before polishing the prose

Every important factual sentence should have a row. Keep the claim narrow enough that its source and limitation can be stated plainly.

The last two rows are template prompts, not facts established for the Artemis example. Omit a claim you cannot support; keep it in the open-questions section if it matters to the assignment.

A completed source-reading brief

Question: What do two identified public sources establish about Artemis I and its satellite imagery?

Event statement: NASA’s release reports the launch of SLS carrying Orion from Pad 39B at 1:47 a.m. EST on November 16, 2022. Keep that stated precision. If the desk converts it to 06:47 UTC, identify the conversion and do not add seconds.

Imagery statement: Scott Bachmeier’s CIMSS article, dated November 16, 2022, describes visible and thermal signatures in GOES-16 ABI imagery, including the booster and launch condensation cloud. Attribute the interpretation to the article. Link the original material so a reader can inspect the images and captions in their source context.

What this brief does not establish: It contains no independently measured pixel values, a fresh attribution analysis, a LaunchDetect publication delay, or a detector-accuracy estimate. The two articles have publication dates; those dates do not establish when each image or claim first became available to every reader.

Use: A source-linked historical explanation or an editor’s starting point for additional reporting. Any stronger scientific or timeliness claim requires the corresponding evidence and review.

Assets: Textual references to the original pages. No third-party satellite frames are reproduced in this brief. If an image is later added, verify its particular credit, reuse conditions, caption, and processing history rather than assuming a page-wide permission.

Keep time and location labels attached to their meanings

For a LaunchDetect-based brief, use the API field definitions alongside the record. The public fields distinguish scheduled launch time, recorded detection time, and feed publication time. Record your own retrieval time separately.

A fresh download does not prove a fresh launch. A detectedAt value does not establish the initial publication time. If a requested sentence needs a timestamp that the evidence does not expose, write “not established in the sources reviewed” and identify the source that would resolve it.

Carry geographic meaning into the caption too. A site marker can locate the launch site without identifying the plume’s pixel position. Coordinates copied into a briefing map do not acquire a more precise meaning merely because the map has a close zoom level.

Treat observed and modeled content separately

The public USSF-385 evidence page provides a useful page-structure example. It distinguishes observed imagery from modeled object paths and areas, and cautions that imagery alone does not establish a detection. This government-mission record is separate from the historical Artemis example.

In a brief, give modeled context its own label and source. State what the model estimates and which inputs or uncertainty notes are available. If those details are missing, preserve that limitation. A polished composite image can make layers look equally certain even when they represent different types of evidence.

Finish the handoff with three practical checks

First, read every caption without the surrounding article. Would the words still make the observed, attributed, and modeled elements clear? Include source, acquisition label if supported, processing description, and the relevant limitation.

Second, assign the unresolved questions. “Verify imagery” is too broad. “Find the original scene identifier and acquisition interval for the displayed frame” gives the next person a concrete task and completion condition.

Third, keep a correction log with version, changed statement, reason, supporting source, and publication locations affected. If an upstream record changes, you should be able to locate every sentence and figure that depended on it.

Use the editable brief template to prepare your own handoff, then inspect a source-linked evidence page. A good brief lets the next reader quickly see what is established, whose interpretation is being repeated, and what still needs work.