Stable interfaces
The TypeScript source file isolates public data contracts from implementation utilities. Exported interfaces include JSDoc comments and explicit field names.
Developer contracts
TypeScript Schema Hub
Stable public interfaces are presented beside runtime JSON examples so reviewers can understand the Distance-Time Kernel, event theater, claim map, evidence ledger, quality gate, mission replay, and source-reference contracts without reading random internal utility code.
Progressive disclosure
Contracts first, runtime examples beside them
This page is intentionally not a raw file dump. It shows only stable public shapes that help reviewers compare browser output, JSON endpoints, and exported evidence bundles.
Runtime JSON
Every interface section points to a JSON endpoint or sample payload that external reviewers can parse and compare.
Caveated use
The contracts describe speculative research visualization data. They do not claim that a physical dark matter propulsion system has been proven.
Public contract examples
TypeScript and JSON in one place
These snippets are intentionally compact; open the full source file for the complete public contract deck.
TypeScript interfaces
/**
* Review payload for a DarkMatterDrive.com Distance-Time Kernel scenario.
*/
export interface DistanceTimeKernelContract {
/** Stable identifier for the public contract section. */
contractId: 'distance-time-kernel-contract';
/** Human-readable scenario selected by the reviewer or simulator. */
activeScenario: string;
/** Distance model used by the page or exported bundle. */
distanceModel: 'parsec-native' | 'standard-siren-comparison' | 'optical-comparison';
/** Baseline distance expressed in parsecs. */
distanceParsecs: number;
/** Gravitational-wave timing baseline in seconds. */
gravityBaselineSeconds: number;
/** Electromagnetic or optical messenger delay in seconds. */
opticalDelaySeconds: number;
/** Current claim status for the reviewed interpretation. */
claimStatus: 'background' | 'site-hypothesis' | 'visual-simulation' | 'pressure-test' | 'needs-validation';
/** Observation or source conflict that would weaken the interpretation. */
falsificationPath: string;
}
/**
* Source reference used by evidence maps, source matrices, and export bundles.
*/
export interface SourceReferenceContract {
/** Topic group used for source clustering. */
topic: string;
/** Public source or page title. */
title: string;
/** How the source supports, limits, or pressures the framework. */
relationToFramework: string;
/** Important limitation that prevents overclaiming. */
limitations: string;
/** Current claim or review status. */
claimStatus: string;
/** Public URL for the source or related site page. */
url: string;
}JSON payload examples
{
"distance_time_kernel": {
"contractId": "distance-time-kernel-contract",
"activeScenario": "gw170817-like-review",
"distanceModel": "parsec-native",
"distanceParsecs": 40000000,
"gravityBaselineSeconds": 0,
"opticalDelaySeconds": 1.74,
"claimStatus": "site-hypothesis",
"falsificationPath": "Downgrade the propagation claim if source and environment delay explain the residual."
},
"source_reference": {
"topic": "multi-messenger gravitational-wave events",
"title": "GW170817 teaching anchor",
"relationToFramework": "Used to separate source delay, environment delay, and any remaining propagation residual.",
"limitations": "The observed lag is not proof that light dramatically slows in vacuum.",
"claimStatus": "pressure-test",
"url": "https://darkmatterdrive.com/multi-messenger-propagation/"
}
}Schema groups
What is covered
The hub groups public contracts by reviewer task instead of exposing every internal helper.
Distance-Time Kernel contract
Defines the minimum review payload for parsec-native distance, relational progression, gravity-baseline timing, and optical messenger telemetry.
Open JSON endpoint
Multi-Messenger Event contract
Defines event anchors, observed channels, delay decomposition, caveats, and falsification notes.
Open JSON endpoint
Framework Claim Map contract
Defines claim status, source references, caveats, and related routes for reviewer scanability.
Open JSON endpoint
Export Builder contract
Defines expected export bundle fields: active scenario, event, telemetry, validation rows, quality gate, source references, caveats, falsification paths, and UTC timestamp.
Open JSON endpoint
Source Reference contract
Defines source topic, relation to the framework, limitations, claim status, and external or internal reference URL.
Open JSON endpoint
Evidence & Sources
How to read the evidence trail
This shared component keeps claims, sources, caveats, and next review links together so research pages stay externally understandable.
Claim status
Each concept should be labeled as background, site hypothesis, visual simulation, speculative engineering, pressure test, or needs validation.
Source topic
Sources are grouped by Hubble tension, JWST early galaxies, SPARC rotation curves, El Gordo, Lithium-7, Proca photon bounds, tired-light criticism, and multi-messenger events when relevant.
Caveats
Every strong page should state what the source does not prove, where the model is speculative, and what external evidence would reduce confidence.
Falsification path
A claim becomes more useful when the page says what observation, export failure, or source conflict would weaken it.
Open Source Matrix
Review topic groups, source quality, limitations, and framework relationships.
Open Evidence MapMove from claims to source-backed evidence trails and known limitations.
Open Claim StatusSeparate background science, site hypotheses, visual simulations, and claims needing validation.
Open Schema HubInspect public TypeScript contracts beside runtime JSON examples.