ArcSecs Research Framework

Measuring the Universe Without Lightyears or Local Clocks

A speculative research visualization for distance, universal progression, gravity-wave baselines, and degraded electromagnetic light.

ArcSecs is building a speculative research visualization that tests whether cosmic distance and universal progression can be modeled without making lightyears, invariant electromagnetic light speed, physical spacetime, literal time dilation, or local atomic clocks foundational.

Speculative boundary: this page explains a research visualization and falsification framework. It is not presented as proof of replacement physics or settled cosmology.

Open Physics Engine Demo Open Dark Matter Drive Simulator What this demonstrates

Source Observer

GravityWavefront baseline

PhotonWavefront delayed / faded

Theme preview only. The plugin owns the live viewport and event theater.

Distance: Parallax, parsecs, arcseconds, angular geometry, proper motion, gravitational-wave standard sirens, and dark standard-siren matching.
Progression: Relational/global measures instead of local oscillator clocks.
Baseline: Gravity-wave propagation marks the deep-event baseline.
Optical channel: Light can lag, fade, stretch, red-shift, degrade, become uncertain, or disappear.

Page-ready nowReadable public framework, source links, SEO/schema, and speculative boundary.

Plugin-ready hooksKernel, Claim Map, Event Theater, validation, and exports stay plugin-owned.

Before live launchConfirm screenshots for desktop, tablet, mobile, footer density, and CTA hierarchy.

Core idea

Relations first. Then test it.

ArcSecs starts with relations. Distance begins with geometry: parallax, parsecs, arcseconds, angular separation, proper motion, and gravitational-wave baselines. Universal progression begins with global and relational structure: deterministic simulation ticks, aggregate change, Janus-style complexity, CMB cooling markers, gravitational-wave-background synchronization, and other whole-system indicators.

Light remains useful evidence. It can identify objects, carry spectra, and reveal what happened along an optical path. But in ArcSecs, light is not the ruler. Electromagnetic propagation is modeled as a secondary observation channel that can carry path damage.

Gravity-wave propagation is treated as the cleaner baseline messenger for deep events. The simulator direction is to make that comparison visible: gravity arrives first, light arrives later, and the delay is broken into source, propagation, environmental, and detection-threshold layers.

Distance without lightyears

Why ArcSecs does not start with lightyears.

A lightyear sounds like a distance unit, but it depends on a stable electromagnetic light speed and a trusted time measurement. That is useful in standard astronomy, but ArcSecs is testing a different foundation. If electromagnetic propagation can vary with distance, medium density, energy degeneration, or path conditions, then light travel distance should not be the primary ruler.

ArcSecs treats lightyears as legacy comparison labels only. The preferred distance foundation is geometric and relational: parallax, parsecs, arcseconds, angular geometry, proper motion, gravitational-wave standard sirens, and dark standard-siren matching.

Parallax

Use apparent angular shift instead of light travel time.

Parsecs

Use arcsecond geometry and baseline distance as the local anchor.

Arcseconds

Represent tiny angular separations as the precision language of the framework.

Angular geometry

Build relational node distances from angles and baselines.

Proper motion

Track movement through angular change and parsec distance.

Gravity-wave standard sirens

Use gravity-wave events as deep-distance anchors independent of optical travel time.

Clockless universal progression

Why local clocks are treated as probes.

A cesium clock, atomic oscillator, particle decay process, or local timing device may be extremely precise, but it is still made from matter. If local conditions change the behavior of the particles inside that device, ArcSecs treats the device as changed.

The framework does not need to say universal time itself stretched. Instead, it models the clock as a probe while universal progression is explored through relational and global measures. Local clocks may remain useful, but they should not silently become the master timeline of the simulator.

Relational simulation tick

A deterministic engine tick that tracks state transition rather than local clock behavior.

York-time-style progression

A global progression placeholder for whole-system evolution.

GLET-style aggregate change

A relational change metric inspired by Jacobi-Barbour-Bertotti-style progression.

Janus Point complexity

A structural complexity score that changes as the simulated universe organizes.

CMB cooling marker

A global epoch marker that can be compared against relational progression.

Gravitational-wave-background synchronizer

A baseline signal layer for comparing deep cosmic progression without local clocks.

Plugin-owned simulator layer

The Distance-Time Kernel.

The Distance-Time Kernel is the simulator layer that unifies distance, progression, gravity-wave baseline propagation, and photon degradation. It belongs in the ArcSecs TypeScript plugin, not in theme logic.

RelationalDistanceEstimate

Distance estimate that does not depend on electromagnetic travel time. Expected channels include parallax, angular separation, proper motion, standard sirens, and dark standard-siren catalog matching.

UniversalProgressionEstimate

Progression estimate that does not depend on a local oscillator. Expected channels include relational ticks, global progression, aggregate structural change, Janus complexity, CMB cooling, and gravitational-wave-background synchronizers.

GravityWavefront

Baseline messenger: blue-white, clean, structurally stable, and shown arriving first.

PhotonWavefront

Secondary electromagnetic messenger: red-gold, delayed, attenuated, red-shifted, uncertain, or missing depending on distance and medium density.

Messenger separation

Gravity waves versus degraded electromagnetic light.

The Distance-Time Kernel separates messenger channels. Gravity-wave propagation is treated as the clean baseline for deep events. Electromagnetic light remains valuable evidence, but it is modeled as an observation channel that can carry path damage.

Gravity-wave channel

Baseline messenger
Clean event marker
Standard-siren distance anchor
Expected to arrive first in the simulator view
Rendered as a blue-white GravityWavefront

Electromagnetic channel

Observation channel
Can lag behind gravity
Can weaken, stretch, red-shift, fade, or disappear
Affected by distance and medium-density assumptions
Rendered as a red-gold PhotonWavefront

Gravity marks the event. Light tells the optical story of the path it traveled.

Framework Claim Map

What this demonstrates.

The plugin-owned Framework Claim Map should connect each simulator claim to a visual demo, telemetry, validation, export data, and falsification path. The public version below mirrors the interactive “What This Demonstrates” component.

Claim → Visual demo → Telemetry → Validation → Export → Falsification path

Claim 1

Distance Without Lightyears

Distance should start with parallax, parsecs, arcseconds, angular geometry, proper motion, and gravitational-wave distance anchors.

Visitor should see: a geometric distance demonstration that does not depend on light travel time.

Failure path: the simulator falls back to lightyears or electromagnetic travel time.

Claim 2

Clockless Universal Progression

Local atomic clocks should be treated as physical probes, not universal time.

Visitor should see: relational/global progression with local oscillator drift shown as a probe layer.

Failure path: stable progression requires local atomic clock assumptions.

Claim 3

Gravity-Wave Baseline

For deep events, gravity-wave propagation should act as the cleaner baseline messenger.

Visitor should see: a blue-white gravity wavefront reaching the observer first.

Failure path: gravity arrival cannot be separated cleanly from electromagnetic arrival.

Claim 4

Electromagnetic Light as Secondary Messenger

Light remains useful evidence, but it should not be the ruler or the clock.

Visitor should see: a red-gold photon wavefront arriving later, weaker, redder, stretched, faded, uncertain, or missing.

Failure path: photon delay, attenuation, or redshift does not respond to distance or medium density.

Claim 5

Multi-Messenger Event Testing

Known and synthetic events can separate source delay, propagation delay, environmental diffusion, and missing-counterpart status.

Visitor should see: event selection updates wavefronts, telemetry, claims, validations, and evidence exports.

Failure path: every delay collapses into one vague explanation.

Claim 6

No-Spacetime Foundation Language

Spacetime, metric expansion, literal time dilation, invariant light speed, local atomic clocks, and warp bubbles may appear only as comparison concepts, not ArcSecs foundations.

Visitor should see: clear speculative-boundary language and comparison labeling.

Failure path: public text overclaims proof or quietly reintroduces rejected constructs as foundations.

Multi-Messenger Event Theater

Gravity first. Light later. Then explain the delay.

The Event Theater is the public demonstration layer for the Distance-Time Kernel. It should make the multi-messenger idea visible: gravity arrives first; light arrives later, weaker, redder, stretched, faded, uncertain, or missing; and the observed delay is split into meaningful layers.

GW170817

Clean benchmark event. Gravity arrives first, light arrives shortly after, and most delay is presented as source/jet-breakout delay.

GW150914

Debated-counterpart caution event. The electromagnetic layer can be marked uncertain instead of being forced into a clean counterpart.

GW190521

Dense-environment / AGN-disk diffusion event. Gravity exits cleanly while light may be heavily delayed by environmental diffusion.

Supernova Light-Curve Stretch

A pressure-test for whether optical stretch can be modeled as photon propagation/degradation rather than foundational time dilation.

Hubble Tension

A comparison case for optical-distance history versus gravity/geometric baseline measurements.

GW190814

Missing-counterpart / attenuation-threshold event. Gravity is visible while the electromagnetic counterpart may be absent.

Synthetic Nearby Binary Neutron Star

Short-distance event where light lag is small and source delay dominates.

Synthetic Void-Line-of-Sight Event

Lower medium density, less photon degradation, and better electromagnetic visibility.

Synthetic Dense-Filament Event

Stronger density-dependent attenuation, stronger red-shifting, and larger photon lag.

Synthetic AGN-Disk Diffusion Event

Environmental delay dominates the observed delay.

Synthetic Missing-Counterpart Event

Gravity arrival appears with no visible photon arrival because electromagnetic energy falls below detection threshold.

Event decomposition

What caused the delay?

ArcSecs should not force every delay into one explanation. A serious event model should separate what happened at the source, what happened during propagation, what happened in the surrounding environment, and what happened at the detection threshold.

Gravity baseline arrival

The structural event marker used as the baseline.

Photon arrival

The electromagnetic arrival when the light channel remains visible.

Source delay

Delay caused by the event mechanism itself, such as jet breakout or source emission timing.

Propagation delay

Delay caused by the modeled travel path between source and observer.

Environmental diffusion

Delay caused by dense media, local surrounding material, or AGN-disk-style diffusion.

Detection threshold

The missing-counterpart layer where electromagnetic evidence becomes too weak, shifted, or uncertain to observe.

Exportable evidence packets

What the plugin exports for reviewers and other AI agents.

The live export builders belong in the ArcSecs TypeScript plugin. This theme page explains the expected evidence products so visitors understand that the simulator is meant to produce reviewable data, not just a visual animation.

Live run → Telemetry snapshot → Validation result → Evidence export → Falsification path

Benchmark JSON

Machine-readable run metadata, active scenario, kernel telemetry, event-theater state, claim-map status, validation summary, quality-gate summary, caveats, and speculative-boundary text.

Calibration Certificate

Human-readable run certificate with UTC timestamp, scenario/event context, distance estimates, universal progression summary, wavefront ordering, source documents, validation result, and falsification notes.

Quality Gate

Pass/fail state for finite telemetry, export completeness, speculative-boundary wording, claim traceability, blocking failures, warnings, and validation checks.

Operator Runbook

Step-by-step operator guidance for the selected scenario, guided story path, event-theater controls, telemetry to watch, validation meaning, caveats, and failure interpretation.

Evidence Packet

The core reviewer packet: claim traceability, active event, delay decomposition, telemetry snapshots, validation snapshots, quality-gate result, source references, caveats, and speculative boundary.

Research Bundle

Complete handoff bundle for outside review or AI-agent continuation, including scenario/event/story state, kernel, claim map, event theater, validation, quality gate, sources, caveats, and falsification notes.

Scene JSON

Viewport state for source/observer positions, GravityWavefront, PhotonWavefront, medium-density path, delay markers, active claim highlight, story step, telemetry, and validation/evidence markers.

Theme boundary: this section documents the expected export products. The actual export builders, payload validation, finite telemetry guards, and download actions remain plugin-owned.

Guided story

How to Measure the Universe Without Lightyears.

The guided story should be interactive in the simulator. Each step should activate visible viewport behavior, telemetry, a claim card, validation checks, and export/evidence status.

Do not start with light. Begin with geometry instead of electromagnetic travel time.
Use angle first. Show a parallax or angular baseline.
Calculate parsecs from parallax. Display distance in parsecs and arcseconds.
Use angular separation and proper motion. Calculate movement relationally.
Use gravity-wave baseline propagation for deep events. Make the GravityWavefront the event marker.
Treat light as evidence, not the ruler. Render PhotonWavefront as delayed/degraded evidence.
Treat local clocks as probes, not universal time. Separate local oscillator drift from global progression.
Use relational/global progression. Show whole-system progression markers.
Compare the messengers. Event Theater selection updates arrivals and delay decomposition.
Show the falsification path. Explain what would weaken the model.

Perspective research report

Additional project-source support for the ArcSecs framework.

The uploaded ArcSecs Perspective Research Report has been preserved in /docs/ as long-term framework material. This section summarizes how it supports the public argument while keeping the speculative boundary visible.

Teleparallel gravity instead of physical spacetime curvature

The report frames TEGR, tetrads, the Weitzenböck connection, zero curvature, non-zero torsion, and axial-vector torsion as a simulation-friendly way to model gravity as a relational/gauge-force behavior rather than a bent physical fabric.

Massive Proca electrodynamics

The report supports the ArcSecs light model through finite photon-mass hypotheses, longitudinal electromagnetic modes, radiation-pressure changes, optomechanical effects, vacuum dispersion, and path-dependent photon propagation.

Mass-polariton momentum transfer

The report uses the Abraham-Minkowski momentum-transfer problem and mass-polariton theory to explain why light moving through media may carry coupled electromagnetic and material momentum, supporting density-dependent attenuation and drag modeling.

Tired light, slow quanta, and dark-sector reinterpretation

The report connects kinetic photon degradation, redshift, freeze-out, graviball/slow-quanta condensates, and invisible halo-like behavior to the ArcSecs dark-sector hypothesis.

CCC+TL and covarying constants

The report adds a public explanation path for static/non-expanding cosmology arguments using covarying coupling constants, tired-light behavior, mass-boom framing, and dual redshift mechanisms.

Stationary light and Dark Matter Drive analogs

The report links dark-state polariton / stationary-light analogs with Dark Matter Drive concepts such as relational kinetics, photon/medium coupling, ramscoop-style collection, and propulsion thought experiments.

Speculative boundary: these are ArcSecs project-source arguments and simulator design prompts. They are not presented as peer-reviewed proof, and every claim should remain tied to validation checks, falsification paths, and exportable evidence.

Failure path

How this could fail.

A framework is only useful if it can fail. ArcSecs should look serious by showing what would weaken or falsify its assumptions.

Photon lag does not scale with distance.
Photon attenuation does not respond to medium density.
Gravity-wave and electromagnetic event timing cannot be separated cleanly.
Source delay, propagation delay, and environmental delay collapse into one vague explanation.
Distance calculations quietly fall back to lightyears.
Universal progression cannot be modeled without local clock assumptions.
Missing-counterpart events break the telemetry model.
Public claims become stronger than the evidence.
Validation checks become decorative rather than deterministic.
Exports omit the evidence needed to reproduce or challenge the run.

A framework is only useful if it can fail.

Source framework documents

Project sources preserved in `/docs/`.

The ArcSecs framework is based on project-source research documents preserved in /docs/. These are simulation design sources and hypothesis-framing documents, not peer-reviewed proof.

New Universe Framework Time and Distance
Rethinking Light Time and Spacetime
Modeling Light Slowing and Energy Degeneration Multi-Messenger Events
Rethinking Cosmic Measurement Framework
ArcSecs Perspective Research Report

Open Research Library Compare Standard Cosmology vs ArcSecs Open Cosmic Anomalies Tracker Read Multi-Messenger Timing

Evidence & Sources

Source trail: what supports the pressure points, and what it does not prove.

This source layer separates observations, mainstream constraints, alternative ideas, ArcSecs simulation prompts, and engineering analogies. The goal is credibility, not link dumping.

5 sources

Multi-messenger timing

Gravitational-wave detections and electromagnetic counterparts provide a timing laboratory for separating source delay, environment delay, and any speculative propagation effect.

Mainstream observational source GW170817: A Short Review of the First Multimessenger Event in Gravitational Astronomy What this source supports

GW170817 is the benchmark event where gravitational waves were detected before the gamma-ray and optical counterpart, making it the cleanest local timing anchor.