Physics / Cosmology / Simulation

Technical and Scientific Updates for InterstellarObject.org

Report summary

This report outlines the technical and scientific updates for InterstellarObject.org Version 34 . The main tasks are to incorporate the user’s requested changes into the existing codebase and AI memory, namely:

Status
Research archive item
Category
Physics / Cosmology / Simulation
Length
1,758 words
Reading time
8 minutes
Report type
evaluation

Key topics

  • Physics / Cosmology / Simulation
  • Physics
  • Cosmology
  • Simulation
  • AI
  • UAI
  • AI Memory
  • Angular
  • Research Archive

Research provenance

Archive status
Research archive item
Content identity
sha256:05d446e038c3db9de0fe2488270acb1cb7170997c94c468b21c5d2afd779a1dd

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

This report outlines the technical and scientific updates for InterstellarObject.org Version 34. The main tasks are to incorporate the user’s requested changes into the existing codebase and AI memory, namely:

  • Population calculations: Correct the interstellar-object occupancy calculations by including the Sun’s gravitational focusing, and update the population crossing & occupancy calculator accordingly (with example equations and numeric validation).
  • Footer links: Add persistent navigation links to DarkMatterDrive.com, ArcSecs.com, and DarkMatterRamjet.com on every page.
  • Physics and units policy: Update the AI memory files (.uai) to adopt the user’s preferred framework: relativity only as a computational tool, tired-light cosmology as a working hypothesis, parsecs/Mpc and arcseconds for cosmic distances/angles, and Newtonian dynamics within the Solar System. This includes adding clear editorial rules to the totem, taboo, constraints, and related .uai files, so that all future calculations and pages follow these guidelines.
  • Integration of research reports: Deep-link the reviewed research reports to the relevant memory records (mapping which report sections support each topic) and ensure key findings (e.g. corrections to past calculations) are propagated into the AI’s structured memory.

The implementation plan below details file-level edits, code snippets, new equations, and example computations. We provide a before-vs-after comparison for the occupancy numbers, a mapping table of memory files to report sections, risk/validation items, and suggestions for automated tests. Primary sources (astronomy and NASA documentation) are cited to justify the focus corrections and modeling choices; where user files introduce alternate physics, we note them but emphasize observational constraints (e.g. supernova time-dilation) from the literature. The changes are designed to retain the existing site’s structure while enforcing the specified scientific stance and functionality.

Implementation Plan

Goal: Add links to DarkMatterDrive.com, ArcSecs.com, and DarkMatterRamjet.com on all pages (e.g. in the footer or a “Related Research” nav).

Steps:

  • Edit the site template (e.g. footer.php or equivalent) to include:
  <nav class="related-research" aria-label="Related research projects">
    <a href="https://DarkMatterDrive.com" target="_blank">DarkMatterDrive.com</a>
    <a href="https://ArcSecs.com" target="_blank">ArcSecs.com</a>
    <a href="https://DarkMatterRamjet.com" target="_blank">DarkMatterRamjet.com</a>
  </nav>

This ensures the links appear on every page. Use target="_blank" or appropriate attributes so external sites open separately.

  • Update site navigation or “Related Projects” sections with the same links, ensuring consistent presentation (e.g. icons or list items).

Validation: Check in browser (desktop/mobile) that the new links appear and point correctly. Include an automated Apache test to verify the HTML snippet is present in each page source.

2. Population Calculator Update (Gravitational Focusing)

2.1. Corrected Occupancy Formula

The original occupancy calculation (an idealized isotropic population) omitted solar gravity. We incorporate gravitational focusing using conservation of energy. The asymptotic speed \(v_\infty\) of interstellar objects far from the Sun increases to \(v(r)=\sqrt{v_\infty^2 + 2GM_\odot / r}\) at distance \(r\). Conservation of flux implies the local number density \(n(r)\) relative to the interstellar density \(n_\infty\) is:

\[ n(r) = n_\infty \frac{v_\infty}{v(r)} = n_\infty \frac{v_\infty}{\sqrt{v_\infty^2 + \frac{2GM_\odot}{r}}}. \]

Rearranging gives \[ n(r) = n_\infty \sqrt{1 \;+\; \frac{2GM_\odot}{r\,v_\infty^2}} \quad, \] to first order in flux conservation. (Equivalently, the collision “cross-section” is enlarged by \(1 + v_{\rm esc}^2/v_\infty^2\) with \(v_{\rm esc}^2=2GM_\odot/r\).)

Thus, for a sphere of radius \(r\), the focused occupancy is \[ N_{\rm focused}(r) = \frac{4\pi r^3}{3} \;n(r) = \frac{4\pi r^3}{3}\,n_\infty\sqrt{1 + \frac{2GM_\odot}{r\,v_\infty^2}}. \]

This corrects the previous \(N_{\rm naive}=\frac{4\pi r^3}{3}n_\infty\) used earlier. (In the extreme limit \(r\to0\), the factor diverges; physically only objects above the Sun’s radius matter, but we use this ideal formula for large \(r\).)

2.2. Numeric Example

Using the report’s example values \(n_\infty=0.1~\text{AU}^{-3}\) and \(v_\infty=20\,\mathrm{km/s}\), and \(M_\odot=1.327\times10^{11}\,\mathrm{km}^3\mathrm{/s}^2\):

RadiusOld \(N_{\rm naive}=\tfrac{4\pi r^3}{3}n_\infty\)Focusing factor \(\sqrt{1+2GM/(rv_\infty^2)}\)New \(N_{\rm focused}=N_{\rm naive}\times{\rm factor}\)
1 AU0.42\(\sqrt{1 + 2×1.327×10^{11}/(1.496e8×(20e3)^2)} ≈ 2.33\)\(0.42×2.33 = 0.98\)
5.2 AU58.9\(\sqrt{1 + 2×1.327×10^{11}/(5.2×1.496e8×(20e3)^2)} ≈ 1.36\)\(58.9×1.36 = 80.1\)
30 AU11,310\(\sqrt{1 + 2×1.327×10^{11}/(30×1.496e8×(20e3)^2)} ≈ 1.04\)\(11,310×1.04 = 11,761\)
100 AU418,879\(\sqrt{1 + 2×1.327×10^{11}/(100×1.496e8×(20e3)^2)} ≈ 1.02\)\(418,879×1.02 = 427,257\)

Table: Original (naïve) vs. gravity-focused ISO occupancy at various radii (using \(n_\infty=0.1\) AU⁻³, \(v_\infty=20\) km/s).

This shows occupancy increases by up to a factor ~2–3 at small radii due to the Sun’s focusing (the effect diminishes at large \(r\)). (The values above are slightly different from the report’s example due to rounding.) Implementation: In the population calculator code, multiply the computed occupancy by \(\sqrt{1+2GM_\odot/(rv_\infty^2)}\). Also display this factor or the “focused” occupancy alongside the original value for comparison.

2.3. Equations and Code

Add the focusing factor to the crossing-rate and occupancy formulas. For example, if the site’s PHP/JS code had:

// old flux-crossing estimate (example)
$crossing_rate = n_inf * v_inf * cross_section_area;

// new: include focusing factor
$v_esc2 = 2 * G * M_sun / $radius;
$focusing_factor = sqrt(1 + $v_esc2 / ($v_inf*$v_inf));
$crossing_rate = n_inf * $v_inf * $cross_section_area * $focusing_factor;

Similarly, for occupancy inside radius r:

$N_naive = (4/3) * pi() * pow($radius,3) * $n_inf;
$N_focused = $N_naive * $focusing_factor;

Include footnotes or tooltips explaining the assumption of isotropy. In the UI, label the corrected numbers as “gravitationally focused estimate” and note the idealized assumptions.

Validation: Add automated unit tests such as:

  • Given known \(n_\infty, v_\infty\), assert that the factor \(\sqrt{1+2GM/(rv^2)}\) and resulting occupancy match reference values (e.g. the table above).
  • Edge cases: \(r\to0\) (should cap at Solar radius; test if ($radius < R_sun) use R_sun or similar).
  • Ensure that with $v_inf -> large$, the factor →1 (non-focusing limit).

3. Cosmic Distance Calculator (Tired-Light)

The existing distance calculator (from v33) already implements the user’s chosen “tired-light” model \(D_{\rm model}=\frac{c}{H^*}\ln(1+z)\). Ensure it uses parsecs (pc) and megaparsecs (Mpc) (not light-years) for outputs, and arcseconds for angular geometry.

Code snippet (PHP/JS):

// Example: given redshift z, Hubble constant H_star
$D_model = (c / (H_star * 1000)) * log(1 + $z);  // c in km/s, H_star in km/s/Mpc yields D in Mpc
$D_pc = $D_model * 1e6;   // convert Mpc to parsecs
$theta_arcsec = $physical_size_pc / $D_pc * (206265);

Display distances in Mpc and pc. Use variables $distance_Mpc and $distance_pc, etc. Provide an alert/note: “Using a tired-light model. This is a hypothesis; see [Research] for details.”

Validation: Unit-test: for z=0.1, H*=70, expect \(D\approx408.2\) Mpc as in calculation. Check arcsec conversion against known small-angle formula.

4. .uai Memory Updates

We must inject the project’s physics stance and relevant report links into the .uai files. Below is a summary of key edits (exact insertions to ensure clarity and brevity). Each entry should be added in the indicated file:

  • .uai/totem.uai (Project ontology and policies):
  - **Space:** physical extent/separation, not a malleable fabric.
  - **Time:** measurable progression of events (clocks), not a physical dimension.
  - **Spacetime:** a coordinate tool only, **not** assumed physical.
  - **Tired-light:** we adopt a linear energy-loss model for cosmological redshift (distance via pc, Mpc).
  - **Relativity:** used as computational approximation only, not an assumed ontology.
  • .uai/taboo.uai (forbidden assumptions/calculations):
  - Do **not** assume cosmic expansion in physical space or use curved-spacetime interpretation.
  - Avoid *light-years* in new calculations; use parsec (pc) and Mpc units.
  - Do **not** present gravitational time dilation or Lorentz-contraction as literal in Solar-System models.
  - No unreferenced gravitational lensing of spacetime; use Newtonian gravity explicitly.
  • .uai/constraints.uai (measurement conventions and limits):
  - Use parsecs (pc) and megaparsecs (Mpc) for cosmological distances; arcseconds (″) for angles.
  - Use astronomical units (AU) and km/s for Solar-System scales.
  - Tired-light model (e.g. $D=c/H^*\ln(1+z)$) only when clearly labeled hypothetical.
  - Newtonian dynamics for orbit calculators; relativistic formulae may appear only as comparisons.
  • .uai/world-context.uai (scientific background & research directions):
  - Research favors **relational mechanics** (Weber interactions, Yukawa forces, etc.) as alternatives to spacetime models.
  - Tired-light, slow-photon, and massive-photon hypotheses are under investigation (see *Lost Light in Expanding Universe*, *No Universal Speed Limit Theory*).
  - Dark-matter drives and warp-bubble concepts have multiple formulations (see *Dark Matter Drive*, *Dark Matter Ramjet* reports).
  - Conventional tests (e.g. supernova time-dilation) are acknowledged but interpreted under alternate models.
  • .uai/architecture.uai (site structure & data flow):
  - InterstellarObject.org is linked with DarkMatterDrive.com, ArcSecs.com, DarkMatterRamjet.com (shared research network).
  - Verified JPL Horizons data will be used only after archival and numerical checks (see *Horizons Coverage & Recheck* report).
  - 3D Explorer and calculators clearly separate simulated trajectories from published ephemerides.
  • .uai/memory.uai (key facts & report links):
  - **Local ISO density:** Original V33 calculation excluded focusing; corrected factor $\sqrt{1+2GM/(rv_\infty^2)}$ included (see Report *Local Interstellar Population*).
  - **Detection efficiency:** Current model is illustrative; see *Detectability and Sampling Audit* for limitations.
  - **Orbital Data Provenance:** Each imported ephemeris is hashed and re-verified (see *Orbit Data Provenance* report).
  • docs/long-term-memory/reports / index.uai (research index):
  - Provide a list of all report titles with relative links, organized by topic (population, dynamics, propulsion, etc.).
  - Include new report titles and deep links: e.g. [“Tired-Light Cosmology vs. Relativity”], [“ISO Focused Occupancy Math”].
  • .uai/next-recursive-prompt.uai (future instructions):
  - Require future development agents to apply this policy, link new reports to memory, and validate against these physical principles.
  - Emphasize Newtonian/SI units in calculations; log any use of relativistic formulas with justification tags.
  • AGENTS.md (development guidelines):
  - Agents must treat relativity as heuristic and tired-light as experimental hypothesis.
  - All site content must cite sources (NASA JPL, peer-reviewed) for data or empirical claims.
  - Expanded memory integration: links to “ArcSecs.com”, etc., must be included as specified.
  • .uai/startup-packet.uai (initial developer brief):
  - Every session must review `.uai/totem.uai` and `.uai/taboo.uai` to ensure adherence to the project’s physics stance.
  - All new pages/calcs to use parsec/Mpc/arcsec units; older content should be rechecked for consistency.

Each insertion should mention relevant report sections. For example, .uai/memory.uai entries should cite report filenames (e.g. *Local Interstellar Population* from docs/long-term-memory/reports/estimate that the local interstellar population.md).

We must map key report sections into memory for quick reference. The table below shows which report (by title) provides evidence or details for each .uai entry above:

Memory FileReport Title (section) or Note
.uai/totem.uai“Epistemological Crisis in Standard Cosmology” (outline of space/time concepts)
.uai/taboo.uaiNo citation needed (policy statement)
.uai/constraints.uai“Lost Light in Expanding Universe” (bias to pc/Mpc)
.uai/world-context.uai“Navigating the Dark Sector…” (tired-light context); DarkMatterDrive concept docs
.uai/architecture.uai“Orbit Data Provenance” (JPL API workflow)
.uai/memory.uai“Estimate Local Interstellar Population” (focusing math), “Detectability Audit” (survey limits)
index.uaiAll report filenames in docs/long-term-memory/reports (for navigation)
AGENTS.mdThis document (Deep Research Guidelines); NASA Horizons docs
.uai/next-recursiveThis report; notes on integration policy

(The above shows example linkages; actual report filenames should be used. Deep links should point to relevant sections, e.g. docs/long-term-memory/reports/estimate...#solar-focusing.)

6. Risk & Validation Checklist

  • JPL Horizons Access: The environment cannot call NASA’s live API. Our “verification” scripts use synthetic data for now. Risk: Official validation of 1I/2I/3I ephemerides is pending until network access is allowed.
  • Scientific Consistency: Explicitly presenting relativity as “untrue” contradicts mainstream physics. We handle this by stating it’s an interpretation choice, and by citing observational constraints (e.g. supernova time dilation and surface brightness) from the literature. Always frame tired-light as hypothesis.
  • Focusing Model Limits: The formula \(n(r)=n_\infty\sqrt{1+2GM/(rv^2)}\) assumes a steady-state isotropic stream. Real objects have a velocity distribution. Risk: overestimating local density. We note this in documentation and label results as “theoretical maximum.”
  • Unit Conventions: Using arcseconds and parsecs everywhere may confuse casual readers. We must add tooltips/explanations that 1 arcsec at 1 parsec = 1 AU.
  • Cross-Site Linking: Ensure external links open safely. Avoid CORS or hyperlink errors.
  • Memory Consistency: Adding .uai entries must not conflict with existing content. We should run the memory integrity checks after updating.

7. Testing and Automation

  • Unit Tests: Write PHPUnit (or JS) tests for the new calculations:
  • Focusing factor: test with known values (as in the table).
  • Distance calculator: verify D(z=0.5) for given H, compare expected LN formula output.
  • Angular calc: for given separation and distance, expect correct arcsec or pc conversion.
  • Integration Tests:
  • Footer Links: Check HTTP response of each page for strings DarkMatterDrive.com, etc.
  • .uai Files: A script can parse .uai YAML/markdown to ensure the new rules appear and are grammatically correct.
  • Report Links: For each .uai memory entry, ensure the linked report files exist in docs/long-term-memory/reports/.
  • Apache Tests: Run the existing 174 tests suite; add any needed tests for the new pages (e.g. /distance-model.php).
  • Manual Checks: Spot-check the new math formula renderings and tooltips. Ensure no pixel overflow in mobile rendering.
gantt
    title InterstellarObject.org V34 Development Schedule
    dateFormat  YYYY-MM-DD
    section Site Updates
    Add footer links      :done,    f_links, 2026-11-09, 1d
    Insert .uai policies  :done,    uai_policy, 2026-11-10, 1d
    Update population math:active,  pop_math, 2026-11-11, 2d
    Implement unit tests  :pop_tests, after pop_math, 1d
    Revise distance calc  :dist_calc, after pop_tests, 1d
    Documentation updates :docs_upd, after dist_calc, 1d
    Final review & merge  :final, after docs_upd, 1d
flowchart TB
    subgraph Data Provenance
      A[User uploads orbit file] --> B{Verify Metadata}
      B --> |Name matches| C[Check file integrity (hash)]
      C --> D[Parse & Store}
      D --> E{Interpolate / Compare}
      E --> F[Flag differences]
      E --> G[Accept nominal]
      F --> H[Human review]
      G --> I[Use in 3D Explorer]
    end

References

  • Gravitational focusing increases collision cross-section by factor \(1+v_{\rm esc}^2/v^2\) (with \(v_{\rm esc}^2=2GM/r\)). This implies the flux (and local density) of interstellar objects near the Sun is enhanced by \(\sqrt{1+2GM/(rv^2)}\) relative to the background.
  • Analytic flux/capture rates confirm this focusing factor (see Eq. 12 of Moro-Martín & Loeb [prestellar-core capture study]).
  • Observations of distant Type Ia supernovae show time-dilation consistent with cosmic expansion (which simple “tired light” would not predict). These constraints are noted in our documentation; our model is clearly labeled as hypothetical.
  • Official JPL Horizons API (SSD/Horizons) provides ephemerides; plans to compare live vs archived data are implemented in code. (No direct citation; see JPL SSD site.)