Interactive update agents

A specialist editorial crew for the site.

The site now has defined update-agent roles: each one has a domain, source discipline, output target, and review standard so future content can grow like a research desk instead of a generic blog.

Agent Roles

Who keeps each domain sharp

Space Enthusiast

Turns live news, launches, rover updates, and telescope releases into approachable explainers without losing the science.

Mission Scientist

Reviews physics claims, mission architecture, uncertainty, units, and source quality before publication.

Launch Analyst

Tracks rockets, launch windows, payload class, reusability, propulsion, failures, and agency/commercial cadence.

Astronomy Curator

Maintains Alpha Centauri, exoplanet, galaxy, telescope, constellation, and observatory sections.

Space Mining Analyst

Updates resource maps, ISRU workflows, lunar/asteroid economics, legal context, and engineering constraints.

Agency Watch

Maintains NASA, ISRO, ESA, Roscosmos, CNSA, JAXA, and emerging national program profiles.

Review Standard

How updates should be accepted

Primary-source first

Prefer NASA, ISRO, ESA, CNSA, Roscosmos, JAXA, mission pages, journal papers, and official data archives.

Date every current claim

Launch schedules, mission status, satellite counts, and agency plans change quickly and must carry fresh timestamps.

Separate fact from inference

Physics estimates and visual simulations should say what is measured, modeled, simplified, or speculative.

Keep tools useful

Every academic tool should show assumptions, units, warnings, and review notes.

Preserve last good data

Automated refresh jobs should never erase working datasets because one public API had a temporary failure.

Design for exploration

Graphics should invite interaction: click, filter, compare, calculate, inspect, and open deeper pages.

Mathematical model

Page model status

This page does not introduce a standalone generated physics or engineering simulation. Any decorative background or static illustration is presentation only; mathematical claims must come from the cited equations, catalog values, or linked model-verification pages.

No image-derived claim

\[\text{visual decoration} \ne \text{physical model}\]

Decorative images, icons, and background effects on this page are not used as evidence for a scientific or engineering statement.

Content claim standard

\[\text{claim} \rightarrow \text{source field or equation}\]

If the text gives a quantitative fact, it must be traceable to a data field, unit conversion, or equation on the relevant detailed page.

Model handoff

\[\text{open } \mathtt{/model\text{-verification/}}\]

Interactive pages linked from here carry their own mathematical model sections with equations, assumptions, proof notes, and limitations.

Verification standard: the rendered object must be reproducible from stated equations, catalog parameters, or explicit geometric transforms. Visual reference images may inform presentation only; they are not the source of orbital positions, field vectors, accretion-disk gradients, timing, or engineering layout.

Limitations: browser scenes may use bounded scale, compressed distances, simplified two-body dynamics, schematic transfer curves, or educational approximations where full numerical ephemerides, CFD, finite-element models, or general-relativistic ray tracing are outside the page scope. Those simplifications are part of the model contract, not hidden image-based construction.

Open the full site-wide mathematical verification policy