Physics / Cosmology / Simulation
ISO\Research\07\Orbit\Data\Provenance.md
Report summary
The standalone scientific data-provenance specification herein establishes the rigorous authentication, curation, and traceability requirements for visualizing the confirmed interstellar objects (ISOs) 1I/ʻOumuamua, 2I/Borisov, and 3I/ATLAS. Designed specifically for the curation and engineering tea
Key topics
- Physics / Cosmology / Simulation
- Physics
- Cosmology
- Simulation
- .NET
- SQL
- Privacy
- Research Archive
- Audit
Research provenance
For citation, use the report title and canonical URL. Archival presence does not establish authorship or promote report statements into portfolio evidence.
This page renders the archived Markdown as safe, formatted HTML. It is background research and does not become a portfolio claim without evidence review.
Full report
On this page
Executive Summary
The standalone scientific data-provenance specification herein establishes the rigorous authentication, curation, and traceability requirements for visualizing the confirmed interstellar objects (ISOs) 1I/ʻOumuamua, 2I/Borisov, and 3I/ATLAS. Designed specifically for the curation and engineering teams at InterstellarObject.org, this report defines the necessary evidence gates that must be cleared before any published orbit snapshot, Jet Propulsion Laboratory (JPL) Horizons vector file, Minor Planet Center (MPC) orbit record, or literature-derived parameter set can safely appear in a public 3D reconstruction. The visualization of celestial mechanics is uniquely vulnerable to silent data corruption, coordinate frame mismatches, and the misapplication of dynamical models. The reconstruction of ISO trajectories demands extreme precision, as their hyperbolic orbits are highly sensitive to non-gravitational accelerations (such as cometary outgassing) and complex n-body gravitational perturbations. Furthermore, the ingestion of astronomical data is governed by strict intellectual property and licensing restrictions, particularly from the MPC, alongside emerging academic standards for data citation as defined by the FORCE11 Joint Declaration of Data Citation Principles1. This document provides exhaustive analysis of the official JPL Horizons API parameters, the MPC's data distribution policies, the physical limitations of reconstructing Sun-only conics from single osculating-element snapshots, and the cryptographic limitations of hashing for source authentication. It concludes with a testable implementation schema, preflight checklists, and a supersession design to ensure that all visualizations remain scientifically accurate, legally compliant, and chronologically reproducible. Note: As an independent analysis, this report is based on documentation available up to November 7, 2026\. Real-time, automated API execution was not conducted; the findings rely on the provided official documentation and programmatic schemas, and this restriction must be noted for any operational deployment.
1. Authoritative Sourcing and Data Retrieval Specifications
The acquisition of orbital parameters and state vectors relies on three primary authorities: the JPL Horizons system, the Minor Planet Center (MPC) Small-Body Database, and peer-reviewed literature. Each source utilizes distinct formatting, coordinate definitions, and licensing agreements that must be explicitly managed to ensure reproducibility and legal compliance.
The JPL Horizons Ephemeris System
\[OFFICIAL DOCUMENTATION\] The JPL Horizons system, maintained by the Solar System Dynamics (SSD) group, provides high-precision ephemerides for solar system bodies and ISOs. Access to this data programmatically is typically achieved via the Horizons API (Version 1.3, updated June 2025\)3. For 3D reconstructions, Cartesian state vectors are strictly preferred over osculating orbital elements to avoid singularity errors and to natively incorporate n-body perturbations over the course of the trajectory. The API exposes multiple variables that fundamentally alter the geometric and physical meaning of the output bytes. A visualizer must explicitly define and record the following parameters to ensure reproducibility:
- Ephemeris Type (EPHEM\_TYPE): Must be set to VECTORS (Cartesian state vectors) rather than OBSERVER (plane-of-sky observables) or ELEMENTS (osculating Keplerian elements)3.
- Vector Table Format (VEC\_TABLE): The system offers formats 1 through 6\. The default is 3, which returns the state vector ([Figure omitted from source export]), 1-way light-time, range, and range-rate3. For pure spatial reconstructions in a 3D engine, setting VEC\_TABLE=2 (state vector only) is often sufficient and reduces parsing overhead, but the inclusion of light-time can be critical for synchronizing visualizations with historical telescope observations5.
- Coordinate Center (CENTER): Determines the origin of the coordinate system. To visualize an ISO passing through the solar system, the origin must be deliberately chosen between the Solar System Barycenter (@0) and the Sun's center (@10)3. Using a geocentric origin (@399 or 500\) will result in a highly complex, apparent spiral trajectory that is visually incompatible with standard solar system models.
- Reference Plane (REF\_PLANE): Specifies whether the coordinates are aligned with the Ecliptic (ECLIPTIC) or the Earth's mean equator (FRAME)3. A mismatch here results in an approximate 23.5-degree axial tilt error in the 3D visualization, displacing the interloper's apparent entry and exit vectors relative to the planetary orbits.
- Vector Corrections (VEC\_CORR): Specifies the application of light-time and stellar aberration corrections. Options include NONE (geometric states, representing the actual physical location of the body at the timestamp), LT (astrometric light-time corrected), and LT+S (corrected for stellar aberration)3. For a true 3D spatial simulation, NONE is strictly required, as the visualization engine itself should dynamically calculate light-travel delays to the virtual camera if necessary. Pre-correcting the vectors will result in double-application of relativistic delays.
NAIF SPICE SPK Binary Trajectories
\[OFFICIAL DOCUMENTATION\] As an alternative to discrete ASCII vector tables, the Navigation and Ancillary Information Facility (NAIF) SPICE toolkit supports the generation of SPK (Spacecraft and Planet Kernel) binary files for small bodies and comets3. SPK files utilize the Double Precision Array File (DAF) architecture, allowing for continuous temporal interpolation of a trajectory rather than relying on discrete time steps7. However, SPK files require the integration of secondary kernels, specifically Leap Second Kernels (LSK), to properly resolve time scales across epochs9. While highly accurate, the SPK format introduces significant overhead for lightweight web-based 3D visualizers, which typically prefer parsing standardized JSON or CSV geometric vectors. If InterstellarObject.org opts for SPK files, the provenance specification must document the exact version of the LSK used alongside the SPK binary, as changes in terrestrial leap seconds will shift the interpolation output.
IAU Minor Planet Center (MPC) Licensing and Usage
\[OFFICIAL DOCUMENTATION\] The Minor Planet Center serves as the global clearinghouse for minor body astrometry. The MPC provides orbital element datasets such as MPCORB.DAT for asteroids and CometEls.txt for comets, the latter of which includes interstellar comets like 2I/Borisov and 3I/ATLAS11. The automated retrieval and redistribution of MPC data is heavily encumbered by licensing policies, which often conflict with the open-source ethos of many web visualizers. The MPC's World Wide Web Policy explicitly states: "Copyright exists in all original material... MPC publications are for personal scientific use only. Redistribution of material posted on this website is not permitted in any form"13. The policy further specifies that blanket extraction or inline framing of the data is prohibited, and the automated scraping of their communal bandwidth can lead to severe IP blocking resulting in connection timeouts13. \[PROPOSED WORKFLOW\]: To comply with MPC licensing while visualizing ISOs, InterstellarObject.org must not distribute raw MPC files (such as CometEls.txt) within the application's source code or asset bundles. Instead, the curation team must manually or through highly rate-limited local scripts extract the specific, isolated orbital parameters for 1I, 2I, and 3I, transform them into a proprietary internal JSON format, and explicitly cite the MPC as the underlying source of the derived parameters, adhering to the FORCE11 Data Citation Principles1.
Scientific Literature and Peer-Reviewed Models
\[MEASURED OR FITTED RECORD\] When official JPL or MPC data lack the most recent non-gravitational models, parameters must be sourced directly from the scientific literature (e.g., Micheli et al. 2018 for 1I/ʻOumuamua, or Thoss et al. 2026 for 3I/ATLAS)15. Literature-derived parameters require rigorous bibliographic tracking, including DOIs, specific table references, and active codebase identification to maintain provenance17. Incorporating these solutions often requires custom numerical integration by the visualization engineer, placing the burden of reproducing the author's dynamical environment directly onto the application.
2. Astronomical Coordinate and Temporal Ambiguities
A standalone provenance specification must explicitly forbid assumptions regarding coordinate systems and temporal epochs. The silent conversion of these variables is the leading cause of visualization drift and scientific irreproducibility in rendering engines.
Reference Frames and Spatial Orientation
\[MEASURED OR FITTED RECORD\] Astronomical reference systems evolve, and failing to track these evolutions introduces systemic bias into visual data. The transition from the B1950.0 system (based on the FK4 catalog) to the J2000.0 system (based on FK5), and subsequently to the International Celestial Reference Frame (ICRF), introduced subtle but critical coordinate shifts. The Horizons API defaults to ICRF, which is quasar-aligned and decoupled from the Earth's precise equinox dynamics, though it aligns closely with J2000.0 equatorial coordinates3. If a 3D visualization engine uses a generic "Ecliptic" plane, the provenance record must specify whether this is the Mean Ecliptic of J2000.0 or the true ecliptic of the date. Mixing an ICRF equatorial state vector with a rendering engine that natively expects an ecliptic coordinate system without applying the necessary rotational matrices will misplace the ISO's trajectory relative to the planetary orbits, completely distorting the geometry of close approaches.
Time Scales, Leap Seconds, and Relativistic Offsets
\[MEASURED OR FITTED RECORD\] Time specification is deeply ambiguous in computer science. Standard Unix time operates on Coordinated Universal Time (UTC), which incorporates discontinuous leap seconds to remain synchronized with Earth's irregular rotation (UT1)5. Conversely, orbital mechanics calculations demand continuous, relativistic time scales. Horizons API element tables default to Barycentric Dynamical Time (TDB), whereas vector tables can be queried in TDB, Terrestrial Time (TT), or UT3. A critical provenance failure occurs when a TDB epoch is silently ingested as a standard UTC timestamp into a web-based rendering engine (like Three.js or Babylon.js) that relies on native JavaScript Date objects. As of the early 21st century, TT runs ahead of UTC by exactly 69.184 seconds (a combination of the fixed 32.184-second offset between International Atomic Time and TT, plus 37 accumulated leap seconds)5. TDB is essentially parallel to TT, fluctuating by only a few milliseconds due to relativistic effects. While a [Figure omitted from source export]\-second discrepancy may seem negligible to a casual observer, the velocity of an ISO makes this temporal misalignment catastrophic. For example, 3I/ATLAS possesses a velocity at infinity ([Figure omitted from source export]) of approximately 58.0 km/s, accelerating significantly as it drops into the solar gravity well toward its 1.36 AU perihelion16. If a TDB vector is read as a UTC vector, the visualization will place the comet approximately 4,000 kilometers away from its true physical location along the velocity vector. In the context of 1I/ʻOumuamua, a 4,000-kilometer drift fundamentally alters the visual narrative of its scattering trajectory. The provenance specification dictates that every timestamp must explicitly declare its time scale (UTC, TDB, TT). TDB dates must not be silently cast to standard ISO 8601 UTC strings without applying the mathematically rigorous leap-second and relativistic transformations required by the International Astronomical Union.
3. Dynamical Limitations of Single-Snapshot Conics
A fundamental error in educational visualizations is the assumption that an object's trajectory can be flawlessly reconstructed indefinitely by mathematically propagating a single set of six Keplerian osculating elements (eccentricity, semi-major axis, inclination, longitude of the ascending node, argument of periapsis, and mean anomaly).
N-Body Gravitational Perturbations
\[INFERRED\] An osculating element set represents the exact, unperturbed, two-body (Sun-object) conic section that the object would follow if all other masses in the universe were instantly removed at that specific moment (the epoch). In reality, the gravity of Jupiter, Saturn, and the inner planets constantly perturbs the ISO. Over a span of months or years, the true path of the ISO diverges significantly from the ideal Keplerian hyperbola defined at the epoch. Consequently, extracting a single CometEls.txt record for 2I/Borisov and using standard two-body equations to draw its entire path through the inner solar system will result in a visual trajectory that fails to cross the correct spatial coordinates at the correct times14. To mitigate this, visualizers must rely on a dense series of Cartesian state vectors queried over the time-span of interest, ensuring that n-body gravitational perturbations are baked into the geometric data prior to rendering.
The Physics of Non-Gravitational Accelerations (NGA)
\[MEASURED OR FITTED RECORD\] For ISOs, pure gravitational models are entirely insufficient. As cometary bodies approach the Sun, the sublimation of volatiles creates localized jets that act as thrusters, introducing continuous non-gravitational acceleration (NGA)16. The standard empirical model for NGA is the Marsden-Sekanina (1973) formulation, which decomposes the acceleration into three orthogonal components relative to the orbit: [Figure omitted from source export] (radial, directed outward away from the Sun), [Figure omitted from source export] (transverse, perpendicular to the radial vector within the orbital plane), and [Figure omitted from source export] (normal, perpendicular to the orbital plane)15. The magnitude of these forces scales with a purely empirical function [Figure omitted from source export], originally derived for water-ice sublimation, which drops off steeply beyond 2.8 AU. For 1I/ʻOumuamua, a highly anomalous radial acceleration ([Figure omitted from source export]) of approximately [Figure omitted from source export] m/s\$^2\$ was detected at a [Figure omitted from source export] significance level by Micheli et al.15. Notably, this acceleration did not strictly follow the standard water-ice [Figure omitted from source export] curve, favoring a scaling closer to [Figure omitted from source export] or [Figure omitted from source export] based on the decrease in solar flux15. The failure of standard gravitational fitting for 1I/ʻOumuamua highlighted the necessity of non-gravitational parameters for accurate historical reproduction. For 3I/ATLAS, which was discovered in July 2025 and reached perihelion around October 30, 2025, significant NGA was also detected27. The NGA of 3I/ATLAS is modeled exceptionally well by Carbon Monoxide (CO) and Carbon Dioxide (CO\$\_2\$) outgassing, generating recoil forces that deviate its trajectory16. Because CO and CO\$\_2\$ have lower sublimation temperatures than H\$\_2\$O, their respective [Figure omitted from source export] scaling functions remain active at much greater heliocentric distances, altering the interloper's path far beyond the traditional water-ice line23. JPL Horizons solutions (e.g., solution \#51 and \#54) explicitly fit these [Figure omitted from source export] parameters16. \[PROPOSED WORKFLOW\]: A single snapshot of osculating elements cannot capture these dynamic, continuously varying forces. If a 3D visualization relies on elements rather than pre-calculated vectors, the rendering engine must explicitly incorporate a numerical integrator (e.g., a Runge-Kutta 4th order solver) that actively applies the [Figure omitted from source export] parameters and the specific [Figure omitted from source export] function associated with the target's primary volatile (e.g., CO for 3I/ATLAS, rather than H\$\_2\$O) across the temporal domain of the simulation.
4. FORCE11 Data Citation Principles and Academic Rigor
\[OFFICIAL DOCUMENTATION\] To elevate the educational portal from a mere graphical demonstration to a scientifically reproducible platform, InterstellarObject.org must adopt the FORCE11 Joint Declaration of Data Citation Principles1. The FORCE11 guidelines stipulate that data must be considered a legitimate, citable product of research, requiring persistent identification, specificity, and verifiability2. When deriving orbit paths, the platform must transition away from vague attributions such as "Data Source: NASA." Instead, the curation pipeline must capture DOIs, exact publication versions, and the specific subsets of data utilized29. If an orbit solution is derived from a GitHub repository or an Astrophysics Source Code Library (ASCL) record, the citation must reference the exact CITATION.cff or Zenodo DOI associated with the code execution18. The provenance specification dictates that every published orbit must programmatically render a front-facing citation block that fulfills the FORCE11 criteria for Credit, Attribution, and Evidence.
5. Cryptographic Authentication vs. Source Origin Evidence
To ensure reproducibility, data provenance must be verifiable. However, common software engineering practices for file verification are insufficient for scientific data provenance. \[INFERRED\] A common misconception in pipeline engineering is that storing a SHA-256 hash of a downloaded JPL Horizons text file or an MPC CometEls.txt payload guarantees its authenticity. This is cryptographically false in the context of origin verification. A cryptographic hash (like SHA-256) guarantees fixity and data integrity at rest. It proves that the file has not been altered since the moment the hash was locally generated by the pipeline2. It does not prove where the file came from. If a malicious actor or a faulty script modifies a Horizons text file to alter 3I/ATLAS's eccentricity from its true hyperbolic value of 6.12 to an elliptical 0.95, and then generates a SHA-256 hash of that manipulated file, the hash will perfectly validate the corrupted data. Furthermore, two identical downloads by independent researchers only prove that the server served the same file twice; it does not independently authenticate the scientific validity of the orbital solution contained within. True origin evidence requires one of the following mechanisms:
1. Digital Signatures: Cryptographic signing of the payload by the issuing authority's private key (a service neither JPL nor MPC currently provides for public text payloads).
2. Verifiable Custody Chains: A logged, timestamped, and reproducible query string (e.g., the exact API URL) accompanied by the institutional metadata (solution number, date of computation, active data arc).
3. Scientific Peer Review: The ultimate authentication is cross-referencing the orbital parameters against published, peer-reviewed literature (e.g., comparing a JPL solution to the kinematic age and non-gravitational parameters published in leading astrophysical journals).
6. Traceability and Supersession Design
\[PROPOSED WORKFLOW\] Orbital parameters are not static historical facts; they are statistical models fitted to observational astrometry. As more observations of an ISO are gathered, the orbital solution is iteratively recalculated, reducing the covariance (uncertainty) ellipsoid. JPL tracks these iterations via "Solution Numbers" (e.g., JPL solution \#16, JPL solution \#51, JPL solution \#54)16. An updated solution completely supersedes the prior solution. To maintain provenance, it is insufficient to simply state "Source: JPL Horizons." The data manifest must record the specific orbital solution number, the data arc (the date of the first observation and the date of the last observation used in the fit), and the number of observations. When an astronomical authority publishes a new orbital solution, the visualization platform must gracefully deprecate the old data to preserve the integrity of historical educational material.
- Immutability: Once an orbit manifest clears the internal publication gates, it becomes immutable. It cannot be edited, only superseded.
- Supersession Pointer: A new manifest is created for Solution \#54. The old manifest for Solution \#51 receives a metadata tag: superseded\_by: \<manifest\_uuid\>.
- Frontend Resolution: By default, the 3D visualizer always queries the database for the active manifest where superseded\_by \== null.
- Historical Access: Users reading an archived blog post from late 2025 regarding 3I/ATLAS must be able to load the visualizer with a specific URL parameter (e.g., ?solution=51). The engine will retrieve the deprecated manifest, display the historical orbit, and flag the UI with a persistent warning: "Viewing Historical Orbit Solution \#51. A newer, superseding solution is available."
7. Recommended Orbital Dataset Manifest Schema
\[PROPOSED WORKFLOW\] To safely serialize and publish orbital data, InterstellarObject.org must adopt a standardized JSON-based manifest. Below is the field-by-field recommended schema.
| Field Name | Meaning | Units | Source Authority | Required / Conditional | Validation Rule |
|---|---|---|---|---|---|
| iso\_id | Standard IAU designation (e.g., 1I/2017 U1) | String | IAU / MPC | Required | Must match regex for IAU formal ISO designations. |
| source\_authority | The institution providing the data | Enum | JPL/MPC/Lit | Required | Must be an approved list of authorities. |
| solution\_id | Specific iteration of the model | String | JPL / Literature | Required | Cannot be null. If MPC, use the file timestamp. |
| data\_arc\_start | First observation used in the orbit fit | ISO 8601 UTC | Origin Source | Conditional | Required for fitted records, validated as a past date. |
| data\_arc\_end | Last observation used in the orbit fit | ISO 8601 UTC | Origin Source | Conditional | Must be [Figure omitted from source export] data\_arc\_start. |
| reference\_frame | Kinematic reference frame (e.g., ICRF) | Enum | JPL / MPC | Required | Must explicitly state equatorial vs ecliptic. |
| origin\_center | The barycenter or physical body used | Enum | JPL (e.g., @0) | Required | Strict enforcement to prevent geocentric drift. |
| time\_scale | Temporal framework of the epoch/vectors | Enum | JPL / MPC | Required | Must be TDB, TT, or UTC. |
| epoch | The specific moment the elements osculate | Float | Origin Source | Conditional | Required if providing Keplerian elements. |
| elements\_keplerian | Object containing [Figure omitted from source export] | Object | Origin Source | Conditional | Inclination [Figure omitted from source export]; Eccentricity [Figure omitted from source export] for ISOs. |
| elements\_nongrav | Object containing [Figure omitted from source export], and [Figure omitted from source export] | Object | Literature / JPL | Conditional | Required if ISO exhibits cometary outgassing. |
| state\_vectors | Array of Cartesian vectors over time | Array | JPL Horizons | Conditional | Arrays of [Figure omitted from source export]. [Figure omitted from source export] must match time\_scale. |
| light\_time\_corr | Boolean flag indicating LT application | Boolean | JPL Horizons | Required | Must be false for raw spatial engine rendering. |
| retrieval\_timestamp | Exact time the payload was queried | ISO 8601 UTC | System Local | Required | Used to cross-reference transient API states. |
| query\_uri | The exact API endpoint and parameters | String / URI | System Local | Required | Must encode all parameters (e.g., VEC\_TABLE). |
| payload\_sha256 | Hash of the raw returned byte payload | String (Hex) | System Local | Required | 64-character hexadecimal constraint. |
8. Source Comparison Table
\[INFERRED\] To assist the curation team in selecting the appropriate primary source for a given visualization scenario, the following table contrasts the strengths and limitations of the three primary authorities.
| Attribute | JPL Horizons | IAU Minor Planet Center | Scientific Literature |
|---|---|---|---|
| Primary Format | Vector Tables & Elements | Osculating Elements (CometEls.txt) | Fitted parameters & Covariance |
| Time Scale | TDB (default) or UT | TT / TDB (implied by epoch) | TDB (standard in dynamics) |
| Non-Grav Model | Natively integrates [Figure omitted from source export] | Generally omitted in bulk text feeds | Exhaustively modeled (e.g., varying [Figure omitted from source export]) |
| Perturbations | Highly accurate N-body | Base elements represent 2-body | High precision N-body \+ Thermal |
| Licensing | Public Domain (US Govt) | Restrictive ("Personal scientific use") | Journal-dependent (often CC-BY) |
| Optimal Use Case | Dynamic 3D plotting via Vectors | Initial discovery alerts / Cross-checks | Physical modeling and origin theories |
9. Publication Evidence Gates
\[PROPOSED WORKFLOW\] Before any ISO orbit is pushed to the public production server for rendering, it must pass through a strict, four-stage evidence gate pipeline to ensure scientific integrity.
1. Format Checked: The incoming data (JSON/Text) is parsed by the automated ingestion script. The schema validation ensures that variables like time\_scale and reference\_frame are explicitly defined and that no null values exist in mandatory fields.
2. Source-Claimed: The data must be bound to a specific origin authority via the query\_uri and solution\_id. The hash (payload\_sha256) is generated locally and logged to prevent internal database corruption or accidental mutation during database migrations.
3. Independently Reviewed: A human curator or an automated secondary validation script verifies the orbital parameters against a secondary source. (e.g., Does the JPL Horizons solution roughly match the MPC semi-major axis? Do the non-gravitational parameters align with recent literature?).
4. Published (With Approval): The manifest is cryptographically signed by the lead curator's internal key and locked in the database. The frontend engine is now cleared to request and render the dataset.
10. Textual Example of a Correctly Qualified Public Orbit Disclaimer
\[PROPOSED WORKFLOW\] To comply with scientific integrity and the FORCE11 Data Citation Principles, every 3D visualization must prominently feature a disclaimer and citation module accessible to the end user: Data Provenance & Disclaimer: The 3D trajectory of interstellar object 3I/ATLAS presented in this visualization is a modeled reconstruction based on Cartesian state vectors generated by the JPL Horizons Ephemeris System (Solution \#54, Data Arc: 2025-07-01 to 2026-01-15). Coordinate Framework: International Celestial Reference Frame (ICRF), Solar System Barycenter origin. Dynamical Model: Incorporates n-body planetary perturbations and non-gravitational accelerations ([Figure omitted from source export]) consistent with Carbon Monoxide outgassing. Disclaimer: Interstellar trajectories are statistical models derived from astrometric observations. Small uncertainties in non-gravitational forces can lead to significant spatial deviations over time. This visualization is interpolated from discrete data points and is intended for educational purposes. Citation: This research has made use of data provided by the Jet Propulsion Laboratory's Horizons system and the International Astronomical Union's Minor Planet Center.
11. Preflight Review Checklist
\[PROPOSED WORKFLOW\] Prior to deploying a new ISO visualization, the curation team must verify the following:
| Verification Step | Description | Status |
|---|---|---|
| API Parameters Logged | Is the exact JPL Horizons GET/POST query string or MPC retrieval script recorded in the manifest? | \[ \] |
| Time Scale Verified | Are the vector timestamps explicitly recorded as TDB, TT, or UTC? Has the rendering engine been calibrated to accept this specific time scale? | \[ \] |
| Origin Verified | Is the reference center set to Barycentric (@0) or Heliocentric (@10), and strictly NOT Geocentric (@399 or 500)? | \[ \] |
| Corrections Disabled | Are light-time and stellar aberration corrections disabled (VEC\_CORR=NONE) in the spatial vectors to prevent double-correction in the 3D engine? | \[ \] |
| Licensing Cleared | If MPC data is referenced, has it been transformed to avoid violating the bulk-redistribution clause, and has proper attribution been provided? | \[ \] |
| Non-Gravitational Forces | For 1I and 3I, does the visualization rely on an N-body vector table rather than a raw, unperturbed Keplerian conic? | \[ \] |
| Supersession Updated | Have previous orbital solutions for this object been correctly flagged as superseded in the database? | \[ \] |
12. Security and Privacy Notes
\[PROPOSED WORKFLOW\]
- Confidential Data: The MPC and JPL occasionally embargo pre-discovery astrometry or sensitive satellite orbital elements. InterstellarObject.org scripts must never attempt to scrape or publish restricted endpoints or unpublished observations11.
- Denial of Service (DoS): The MPC explicitly blocks IP addresses that aggressively scrape their communal bandwidth, resulting in connection timeouts that can break automated pipelines14. Automated systems must adhere to strict rate limiting (e.g., one query per day for CometEls.txt) and rely on local caching.
- Data Injection: Because hashes do not prove origin, all API responses must be parsed through strict regex boundaries before database insertion. For example, ensuring eccentricity is parsed strictly as a float prevents malicious SQL injection or cross-site scripting (XSS) payloads from being hidden within unverified text fields.
13. Testable Requirements for Future Implementation Engineers
\[PROPOSED WORKFLOW\] To bridge the gap between this specification and the software engineering team, the following requirements must be implemented in the curation pipeline's unit tests:
1. REQ-001 (Time Scale Enforcement): The ingestion script SHALL throw a fatal error if the input temporal array lacks a defined time\_scale metadata flag (TDB, TT, UTC).
2. REQ-002 (Barycentric Origin Enforcement): The ingestion script SHALL reject any JPL Horizons payload where the Target body name or Center body name indicates a topocentric or geocentric origin, unless explicitly flagged for Earth close-approach analysis.
3. REQ-003 (Keplerian Fallback Warning): If the visualization engine is fed elements\_keplerian without accompanying state\_vectors, it SHALL generate an internal warning log indicating that the visual trajectory will drift from reality over multi-year spans due to the omission of perturbations.
4. REQ-004 (Immutable Hashes): The database schema SHALL prevent UPDATE commands on the payload\_sha256 and state\_vectors columns once a manifest achieves "Published" status.
5. REQ-005 (Citation Rendering): The frontend UI SHALL dynamically generate a citation string matching FORCE11 standards using the source\_authority, solution\_id, and query\_uri fields of the active manifest.
14. Bibliographic References and Documentation-Access Log
Documentation-Access Log:
- Date of Access: November 7, 2026\.
- Location: Cicero, Illinois, United States.
- Method: Programmatic review of cached official documentation snippets. Real-time API execution was restricted.
Bibliographic References:
1. JPL Horizons API Documentation: Jet Propulsion Laboratory, Solar System Dynamics. (2025). Version 1.3. URL: https\://ssd-api.jpl.nasa.gov/doc/horizons.html3.
2. JPL Horizons Manual: Jet Propulsion Laboratory, Solar System Dynamics. URL: https\://ssd.jpl.nasa.gov/horizons/manual.html4.
3. Minor Planet Center Data Policies: International Astronomical Union. URL: https\://www\.minorplanetcenter.net/iau/WWWPolicy.html13.
4. Extended MPCORB Data Format Manual: Minor Planet Center. (2026). URL: https\://www\.minorplanetcenter.net/data11.
5. FORCE11 Joint Declaration of Data Citation Principles: Data Citation Synthesis Group. (2014). San Diego CA: FORCE11. URL: https\://force11.org/info/endorse-the-data-citation-principles/1.
6. Non-Gravitational Acceleration Modeling (1I/ʻOumuamua): Micheli, M., et al. (2018). Nature. URL: https\://www\.eso.org/public/archives/releases/sciencepapers/eso1820/eso1820a.pdf15.
7. Marsden-Sekanina NGA Parameters: Marsden, B. G., Sekanina, Z., & Yeomans, D. K. (1973). Astronomical Journal, 78, 211-225. URL: https\://adsabs.harvard.edu/pdf/1974AJ.....79..413M15.
8. Non-Gravitational Acceleration (3I/ATLAS): Thoss, V., Loeb, A., Burkert, A. (2026). Inferring the mass and size of 3I/ATLAS from its non-gravitational acceleration. arXiv:2603.15735. URL: https\://arxiv.org/abs/2603.1573516.
9. JPL Vector Parsing Parameters: Phun-ky Interstellar Tools API. (2026). URL: https\://phun-ky.net/interstellar-tools/api/@interstellar-tools/tracking/functions/parseHorizonsVectors5.
Works cited
1. Endorse the Data Citation Principles \- FORCE11, https\://force11.org/info/endorse-the-data-citation-principles/
2. The Ongoing Challenges of Citing the Results of Scholarly Research, https\://www\.niso.org/niso-io/2015/09/ongoing-challenges-citing-results-scholarly-research
3. Horizon API \- nasa ssd/cneos, https\://ssd-api.jpl.nasa.gov/doc/horizons.html
4. JPL Horizons manual \- Horizons System \- NASA, https\://ssd.jpl.nasa.gov/horizons/manual.html
5. Function: parseHorizonsVectors() \| Interstellar Tools, https\://phun-ky.net/interstellar-tools/api/@interstellar-tools/tracking/functions/parseHorizonsVectors
6. Getting state vectors from JPL Horizons ephemerides, https\://space.stackexchange.com/questions/25256/getting-state-vectors-from-jpl-horizons-ephemerides
7. SPK Required Reading \- FTP Directory Listing, https\://naif.jpl.nasa.gov/pub/naif/toolkit\_docs/C/req/spk.html
8. MKSPK User's Guide \- FTP Directory Listing, https\://naif.jpl.nasa.gov/pub/naif/toolkit\_docs/FORTRAN/ug/mkspk.html
9. SPKDIFF User's Guide \- FTP Directory Listing, https\://naif.jpl.nasa.gov/pub/naif/toolkit\_docs/C/ug/spkdiff.html
10. \[Spice\_discussion\] OEM files \- NASA, https\://naif.jpl.nasa.gov/pipermail/spice\_discussion/2010-April/000293.html
11. Data Available from the Minor Planet Center, https\://www\.minorplanetcenter.net/data
12. Kepler Orbits — Skyfield documentation \- Rhodes Mill, https\://rhodesmill.org/skyfield/kepler-orbits.html
13. Website Use Policy \- IAU Minor Planet Center, https\://www\.minorplanetcenter.net/iau/WWWPolicy.html
14. When the Orbitals Plugin Stops Loading MPC Comet Data \- Svenesis, https\://www\.svenesis.org/blog/2026-08-orbitals-mpc-workaround\_en.html
15. Non-Gravitational Acceleration in the Trajectory of 1I/2017 U1, https\://www\.eso.org/public/archives/releases/sciencepapers/eso1820/eso1820a.pdf
16. Inferring the mass and size of 3I/ATLAS from its non-gravitational, https\://arxiv.org/html/2603.15735v1
17. August Muench's research works \| American Astronomical Society, https\://www\.researchgate.net/scientific-contributions/August-Muench-2166105067
18. arXiv:2212.12683v1 \[astro-ph.IM\] 24 Dec 2022, https\://arxiv.org/pdf/2212.12683
19. Open Science in Astrophysics: Citation Benefits of Open Code, https\://arxiv.org/pdf/2607.00546
20. How We Know 3I/ATLAS Is Interstellar: Orbit Math \- The Science 360, https\://thescience360.com/3i-atlas-interstellar-comet-hyperbolic-orbit/
21. Is the interstellar object 3I/ATLAS alien technology? \- arXiv, https\://arxiv.org/pdf/2507.12213
22. astrometrica@groups.io \| Messages, https\://groups.io/g/astrometrica/messages?expanded=1\&msgnum=7175
23. Non-Gravitational Acceleration in 3I ATLAS \- arXiv, https\://arxiv.org/pdf/2511.07450
24. Revisiting the orbit OF 153P/Ikeya–Zhang \- RiuNet, https\://riunet.upv.es/bitstreams/54e60f24-c39c-4882-98a7-3ab308f588c4/download
25. 1974AJ 79\. . 413M \- Astrophysics Data System, https\://adsabs.harvard.edu/pdf/1974AJ.....79..413M
26. NON-GRAVITATIONAL ACCELERATION IN THE ORBIT OF 1I/2017, https\://esahubble.org/static/archives/releases/science\_papers/heic1813/heic1813a.pdf
28. Constraints on Exotic Volatile Outgassing in Interstellar Comets \- arXiv, https\://arxiv.org/html/2511.07450v1
29. Recommended practices to promote scholarly data citation and, https\://cci.drexel.edu/mrc/wp-content/uploads/2018/05/MeganForcePaper.pdf
30. Software Citation Implementation in Astronomy: An Update \- Slides, https\://slides.com/dbouquin/aas\_233
31. Tracking Software and Data Citations to Zenodo DOIs \- arXiv, https\://arxiv.org/html/1911.00295v1
32. Perez Hourglass inside Cuboctahedral Crystal: m \= 6 ⊕ 12 Fractal, https\://www\.researchgate.net/publication/416024652\_Perez\_Hourglass\_inside\_Cuboctahedral\_Crystal\_m\_6\_12\_Fractal\_Topology\_and\_Counter-Rotating\_Vacuum\_Bowls\_in\_the\_Macroscopic\_Solar\_System\_The\_IT\_3\_Framework\_v20\_Ironclad\_Visual-Rhyme\_Edition\_-Universal\_T
33. ORIGINAL UNEDITED MANUSCRIPT \- Oxford Academic, https\://academic.oup.com/mnras/advance-article-pdf/doi/10.1093/mnras/stag1866/71532295/stag1866.pdf
34. Horizons Lookup API \- nasa ssd/cneos, https\://ssd-api.jpl.nasa.gov/doc/horizons\_lookup.html
35. Data Available from the Minor Planet Center, http\://mpcweb1.cfa.harvard.edu/data
36. Orbits for current comets in the MPC database, https\://data.smartidf.services/explore/dataset/orbits-for-current-comets-in-the-mpc-database/
37. Principles of Biochemistry \- DOKUMEN.PUB, https\://dokumen.pub/principles-of-biochemistry-i-6498768.html
38. Inferring the mass and size of 3I/ATLAS from its non-gravitational, https\://arxiv.org/abs/2603.15735