Parsec / parallax
The parsec is defined geometrically from parallax: one astronomical-unit baseline subtending one arcsecond. That definition does not depend on electromagnetic travel time.
Parsec-first metrology
A public DarkMatterDrive / ArcSecs page built from the Parsecs for Speed and Area report. It explains why the project demotes lightyears to optical telemetry and uses parsecs, parallax, arcseconds, proper motion, and parsec-native area and volume units as the geometry-first measurement stack.

Direct answer
This page is written as project architecture and simulator framing. It is not presented as settled mainstream cosmology.
The ArcSecs distance stack should use parsecs, parallax, angular geometry, proper motion, and gravitational baselines as measurement primitives. Lightyears should be treated as optical telemetry because the framework is explicitly testing whether electromagnetic propagation is path-dependent.
That means the simulator should not calculate truth distance from how far light travels in a local clock interval. It should calculate spatial relations from geometry first, then compare delayed, redshifted, weakened, or stretched photon data against that baseline.
Measurement stack
The report turns the distance problem into a practical set of units the engine can compute without treating light speed as the ruler.
The parsec is defined geometrically from parallax: one astronomical-unit baseline subtending one arcsecond. That definition does not depend on electromagnetic travel time.
Arcseconds give the engine a gridless angular coordinate system. The visible sky becomes a relational angle map rather than a light-travel ruler.
Proper motion in arcseconds per year combines with parsec distance to compute tangential velocity. This turns observed angular drift into parsec-native kinematics.
The report highlights the practical near-alignment between kilometers per second and parsecs per million years for deep-time stellar motion, letting the simulator talk in galaxy-scale units.
Surface density, brightness, extinction, and star-formation regions can be modeled in square parsecs instead of logarithmic optical-only descriptions.
Nebulae, clusters, voids, superclusters, and observable-universe scale volumes can be expressed in cubic parsecs, megaparsecs, and gigaparsecs.
Why this matters
The framework is not debating whether standard astronomy uses lightyears. It is defining what the ArcSecs simulator should use internally.
Distance truth should come from parsec/parallax geometry, standard-siren baselines, and relational node positions.
Photon arrival, redshift, color, attenuation, stretch, and delay should be recorded as optical messenger telemetry.
If parsec/gravity baselines and optical history cannot be reconciled, the simulator should show the residual instead of forcing every observation into the preferred model.
Simulator contract
The same kernel is embedded here so the public framework page maps directly into engine systems instead of remaining article copy.
distance primitive
Near and middle-distance geometry should be calculated from angular parallax and parsecs instead of light travel time.
deep-distance primitive
For cosmological distance, use gravitational-wave strain and chirp behavior as the clean baseline before treating electromagnetic redshift as distance truth.
universal progression primitive
Global simulation order should be calculated from relational state change and universal synchronizers rather than from local atomic oscillators.
messenger propagation primitive
Gravity waves and electromagnetic light should be modeled as separate messengers, with light carrying source delay, environmental diffusion, velocity attenuation, and energy degeneration.
falsification pressure-test primitive
Supernova light-curve stretching is the hard tired-light pressure test and must be reproduced as photon-arrival distortion without claiming literal time dilation.
population comparison primitive
Hubble tension should be exposed as a comparison between optical propagation history and geometry/gravitational baselines.
Open distance-time-kernel.json for the machine-readable engine contract.
Claim map
The same claim-map component is reused here so multi-messenger event interpretation stays connected to the broader time-and-distance framework.
Project hypothesis / geometry-first implementation
Do not use lightyears as the primary distance primitive when light speed is treated as a variable messenger. Use parsec/parallax geometry, angular coordinates, proper motion, and gravitational-wave standard sirens instead.
Add parsec/parallax distance mode, angular-node coordinates, proper-motion velocity calculation, and standard-siren distance telemetry to the ArcSecs physics engine.
Demo behavior:Expose a distance-mode selector that shows parsec/parallax and gravitational-wave standard-siren distances beside any optical-light estimate.
Project hypothesis / geometry-first metrology
Treat parsecs, arcseconds, parallax, proper motion, square parsecs, cubic parsecs, megaparsecs, and gigaparsecs as the native distance and density stack instead of using lightyears as the truth unit.
Add parsec-native distance, area, and volume telemetry to the Distance-Time Kernel and ensure optical light-travel estimates remain secondary messenger fields.
Demo behavior:Show a distance-without-lightyears panel that converts angular geometry into parsecs, velocity into parsecs per million years, and regions into square/cubic parsec densities.
Project hypothesis / simulator clock architecture
Do not treat local atomic clocks as the fundamental universal clock when local particles and clock mechanisms may be affected by gravity or substrate conditions. Use global relational state progression instead.
Add engine time modes for York-time-style global state, GLET/Jacobi-Barbour-Bertotti relational change, Janus Point complexity, CMB cooling, and gravitational-wave-background synchronization.
Demo behavior:Replace a single clock readout with a Universal Chronology panel that compares relational tick, complexity index, background synchronizer, and local clock drift.
Project hypothesis / multi-messenger pressure test
Use gravitational waves as the clean arrival baseline while modeling electromagnetic radiation as a secondary messenger that may carry source delay, environmental delay, velocity attenuation, and energy degeneration.
Keep separate GravityWavefront and PhotonWavefront entities, then compute arrival residuals after subtracting intrinsic source and environmental terms.
Demo behavior:Visualize gravity arrival first, electromagnetic arrival later, and a residual lane that distinguishes source mechanics from possible propagation history.
Reference point / calibration caution
GW170817 should be used as the benchmark because it has gravitational-wave detection followed by a gamma-ray/kilonova counterpart, but its observed electromagnetic delay should not be collapsed into pure vacuum propagation delay.
Seed the simulator with an event card that separates observed delay into source term, environment term, and residual propagation term.
Demo behavior:Add GW170817 as the default tutorial event for explaining why source delay and propagation delay must be separated before fitting light-slowing constants.
Reference point / debated association
GW150914 is useful because the gravitational-wave detection is historic while the proposed gamma-ray association is debated, making it a test case for false-positive and counterpart-quality labels.
Attach confidence labels to every electromagnetic counterpart before the propagation model is allowed to learn from the event.
Demo behavior:Show GW150914 with a disputed-counterpart badge so users understand why event quality matters as much as delay magnitude.
Reference point / environmental separation
GW190521 is useful because a possible optical flare in an AGN environment makes the local environment a dominant candidate delay term before any universal light-slowing term is inferred.
Model AGN/environment diffusion as a separate term so the engine does not mistake dense local astrophysics for universal propagation history.
Demo behavior:Show GW190521 as the tutorial event for environmental opacity, diffusion, and delayed optical flare interpretation.
Project hypothesis / hard pressure test
Treat supernova light-curve stretching as the key historical weakness that any tired-light or light-slowing model must reproduce without invoking literal time dilation.
Add a supernova-light-curve mode that stretches photon arrival intervals through path-dependent electromagnetic velocity and energy history while keeping the relational simulation clock global.
Demo behavior:Give users a slider that compares standard expansion-style stretching against ArcSecs messenger-distortion stretching and highlights residuals.
Project hypothesis / research program
Frame Hubble tension as a possible mismatch between optical propagation history and distance/chronology baselines, not only as a question of pure metric expansion.
Compare gravitational-wave standard-siren distances, parsec/geometry anchors, redshift-derived optical distances, and simulated light-energy history in the same telemetry panel.
Demo behavior:Add a Hubble Tension lab card that lets users compare optical redshift history against gravitational/geometry baselines.
Project hypothesis / plugin implementation contract
The ArcSecs plugin should calculate distance through parsec geometry and gravitational-wave anchors, calculate chronology through invariant relational ticks, and treat optical light and local clocks as secondary telemetry.
Bind /distance-time-kernel.json, /framework-event-lab.json, /multi-messenger-event-theater.json, and assets/ts/arcsecs-physics-engine source contracts into the plugin agent for the ArcSecs demo and Dark Matter Drive simulator.
Demo behavior:Add a source-contract panel that shows which TypeScript system, kernel layer, event scene, and fail condition drive the current demo mode.
Project hypothesis / calibration detail
GW170817 should not be reduced to a raw 1.7-second light delay. The report separates the delay into a small modeled vacuum latency and a dominant source-delay term.
Add default telemetry fields for observed delay, modeled vacuum latency, source delay, attenuation coefficient, and inclusion/exclusion from global light-slowing fits.
Demo behavior:Show GW170817 with observed delay near 1.7 seconds, modeled vacuum latency near 0.020 seconds, and source delay near 1.68 seconds so the user can see the subtraction.
Project hypothesis / simulator clock model
The simulator should model cesium-clock differences as local atomic-oscillator behavior affected by gravity/substrate conditions rather than literal slowing of universal time.
Add AtomicOscillatorSystem telemetry that samples local gravity/substrate density and reports oscillator drift beside the invariant global tick.
Demo behavior:Show local clock drift as a physical oscillator readout while the universal chronology lane remains stable.
Project hypothesis / framework support
Model gravity as a flat/torsion-style relational force lane rather than as literal curvature of material spacetime.
Keep simulator language aligned with torsion, translational gauge force, relational graph edges, and non-spacetime force visualization rather than metric-fabric deformation.
Demo behavior:Use this as the source claim for viewport labels, gravity vector overlays, and plugin caution language when comparing standard curvature explanations to ArcSecs torsion-style behavior.
Project hypothesis / photon-lane support
Treat electromagnetic light as a path-dependent Proca-style messenger whose propagation can vary by frequency, energy, and medium history instead of using light as the universal ruler.
Bind photon rest-mass, wavelength-dependent delay, energy degeneration, and finite telemetry guards into PhotonWavefront and export payload caveats.
Demo behavior:Use this to support redder/weaker/later photon-lane visuals in the Event Theater and Distance-Time Kernel.
Project hypothesis / medium-interaction support
Use Mass-Polariton and Abraham-Minkowski momentum-transfer framing to explain why light-medium interaction can be treated as mechanical substrate exchange in the simulator.
Use source-linked caveats for Proca substrate drag, ramscoop intake, density-field fuel interaction, and optical medium effects.
Demo behavior:Support propulsion and ramscoop explanatory cards that show energy/momentum transfer without claiming laboratory validation of the full drive concept.
Project hypothesis / dark-sector reinterpretation
Frame the dark-sector substrate as a speculative freeze-out endpoint of degraded massive light, producing optically invisible slow quanta or graviball condensate.
Tie dark-sector metrology, ship fuel density, dark matter drive intake, and tired-light energy ledgers to explicit source links and falsification cautions.
Demo behavior:Show substrate-density and fuel-availability overlays as simulator hypotheses rather than proof of a real dark matter composition.
Project hypothesis / analogy support
Use stationary-light and dark-state-polariton ideas as analogy support for delayed, trapped, or converted light-energy behavior, with clear boundaries between analogy and drive validation.
Add source-linked analogy warnings wherever the site uses stopped-light, trapped-light, EIT, or ramscoop fuel-conversion language.
Demo behavior:Support educational annotations for ramscoop and propulsion pages while keeping speculative-boundary language visible.
Simulator contract
The page is also a build note for integration reviewers that will wire this into the live simulator.
Add parsec, arcsecond, parallax angle, proper motion, tangential velocity, square-parsec, cubic-parsec, megaparsec, and gigaparsec fields. Do not create a lightyear truth primitive.
Keep light travel time, redshift, arrival stretch, energy degeneration, and frequency-dependent delay in the photon lane as path-dependent observations.
Pair geometry-first distance with gravitational-wave standard-siren distance where parallax is unavailable, then compare optical estimates against both.
Benchmark JSON, Calibration Certificate, Quality Gate, Operator Runbook, Evidence Packet, Research Bundle, and Scene JSON should expose parsec baselines and optical residuals separately.
Source trail
The source report is included both as long-term Markdown memory and as a PDF research-library asset.
docs/report-parsecs-for-speed-and-area.md stores the report source in the package /docs/ folder.
docs/parsecs-for-speed-and-area-claim-support.md maps the report to distance-without-lightyears, parsec-native kinematics, and simulator-export requirements.