Interdimensional
Transit

Section 01

Executive Summary

through.co is a transit infrastructure operator. We design, certify and operate the controlled apertures through which authorised travellers move between coordinates in space, time, or — in approved cases — adjacent layers of reality.

This white paper describes how we make that movement repeatable, predictable, and safe enough to be put on an invoice.

The document is intended for three audiences:

• Cleared programs evaluating through.co as an operator
• Oversight bodies assessing our compliance posture
• Academic researchers seeking a technical reference under NDA

It does not contain classified material. Specifications relating to sovereign engagements, restricted destinations and exit-vector cryptography are published only in the sealed appendix circulated to verified parties.

Key facts as of Q2 2060

through.co has operated continuously since first cleared crossing in 2055. Our charter is published, our oversight board is independent, and the work we do is, by design, ordinary.

Section 02

The Transit Problem

2.1 What "transit" means here

In the through.co fiction layer, transit is the structured displacement of matter — typically a credentialed traveller — from one validated coordinate to another, via a sustained, instrumented aperture.

It is not teleportation. It is not flight. The traveller crosses the aperture in finite, bounded time, and arrives at a coordinate whose vibrational signature was locked before the crossing began.

2.2 Why earlier attempts failed

Before 2055, transit was attempted by at least four research consortia. The failure modes shared a small number of root causes:

1. Unstable phase lock. Apertures held briefly but drifted off-signature mid-transit, producing arrival coordinates that did not match the intended destination.
2. Field decoherence. The structural integrity field around the aperture could not be maintained long enough to commit a full traveller mass.
3. No return vector. Once a traveller crossed, the originating field collapsed faster than a stable inverse could be opened. Return was either impossible or stochastic.
4. Inadequate continuity controls. Travellers arrived with measurable drift in identity, memory or biometric signature, with no protocol for detection or recovery.

These were not minor engineering bugs. Together, they made transit a one-way, low-confidence, high-cost operation suitable only for unmanned probes.

2.3 What changed

The Aperture Engine — described in Section 3 — addresses the four failure modes simultaneously. It does not produce a faster or cheaper transit. It produces a transit that is bounded, monitored and reversible.

Section 03

The Aperture Engine

The Aperture Engine is the coordinated system that creates and sustains a transit window. It is composed of three subsystems that operate in lock-step. None of them is novel in isolation. The novelty is their coordination.

3.1 Quantum-phase alignment

The first subsystem locks the local aperture to the vibrational signature of the destination. Signature acquisition is performed through a long-baseline interferometric array distributed across the operator's facility.

Phase lock is non-destructive. If acquisition fails, no aperture forms and the traveller remains in the staging cell.

3.2 Stability field

Once phase lock is acquired, the second subsystem projects a structural-integrity field around the forming aperture. This field has two functions:

1. Hold the aperture geometry within commit tolerance.
2. Protect the traveller's material continuity from local-frame distortion during the crossing.

The stability field is the most energy-intensive part of the Aperture Engine. It is also where the bulk of our safety logic lives, because most failure modes are detected first as field variance.

3.3 Exit-vector control

The third subsystem commits the traveller to a specific arrival coordinate and arms a corresponding return path.

Exit-vector control is the difference between transit and gambling. A vector is selected from the certified atlas (Section 6), bound to the active aperture, and validated against the destination signature acquired in step 3.1. Only when the three values match within tolerance does the system permit commit.

Exit-vector control is what makes through.co's transit reversible. Every committed vector carries its inverse in the active manifest, opened on the return-side aperture before the outbound is closed.

3.4 Cycle summary

The full operational cycle of a transit looks like this:

T-180 min   Pre-flight: traveller continuity baseline captured
T-90  min   Staging: clearance verified, vector pre-loaded
T-15  min   Aperture warm-up
T-0         Phase lock acquired
T+5  s      Stability field projected
T+7  s      Exit vector matched and armed
T+9  s      Commit
T+12 s      Aperture sustained / traveller in transit
T+22 s      Aperture closed, return-side opened
T+90 min    Post-flight continuity verification

Approximate. Sovereign engagements add roughly 40 minutes of additional verification on either side.

Section 04

Safety Framework

Safety is not a section in a marketing deck. For through.co it is the part of the system that determines whether we are allowed to operate at all.

We treat transit infrastructure the way critical national infrastructure operators treat their networks: with layered controls, independent oversight, and a default-deny posture.

4.1 The four protocols

All operations run under four binding protocols. Each is auditable. None of them is optional.

PROTOCOL · 01 — Continuity Monitoring

Identity, memory and biometric drift are sampled before, during and after each passage. A baseline is captured at T-180 minutes and compared against post-transit values.

PROTOCOL · 02 — Fail-safe Closure

The Aperture Engine is wired to collapse the aperture inward when field variance exceeds approved thresholds. Closure is unconditional, irreversible and prioritised over any commit-in-progress.

Operationally, this means: if the system has any reason to doubt that a clean transit is possible, the system removes the option. It does not pass the decision to the operator.

PROTOCOL · 03 — Return Vector

No route is ever certified without a validated return path. The return-side aperture is opened at T+22 s — before the outbound aperture has fully collapsed — and held until traveller continuity at the destination is confirmed.

PROTOCOL · 04 — Independent Audit

Operations are audited quarterly by the Meridian/9 oversight board. Audit reports are published in summary form and available in full to cleared programs and to academic researchers under NDA.

The board has, by charter, the authority to halt operations. It has used this authority twice since 2055 (incidents OS-2056-04 and OS-2058-11).

4.2 Failure modes and recovery

A small number of named failure modes account for ~96 % of all incidents recorded since 2055. Each has a documented recovery procedure.

4.3 The zero standard

If an unrecovered incident were ever to occur, the published response procedure is full halt of all transit operations pending root-cause investigation and oversight-board re-certification.

Section 05

Operational Architecture

5.1 The aperture network

through.co operates twelve apertures across three facilities:

Pier C is the only facility with Tier C clearance. Tier C transits are operated jointly with Pier C Command under sovereign protocol.

5.2 Transit lifecycle

A booked transit moves through five phases. Each phase has a defined handover and a verifiable artifact.

The full lifecycle from request to verified return is typically four to six weeks. Sovereign engagements take longer because of additional treaty-level provisions.

5.3 Capacity and concurrency

Each aperture supports a single concurrent transit. Stacked transits across multiple apertures at the same facility are supported up to a concurrency limit of three, with the cap driven by stability-field interference rather than scheduling.

Aggregate network capacity is currently ~52 transits per 24 hours, sustained.

Section 06

The Destination Atlas

through.co maintains a curated atlas of verified destination signatures. The atlas is the canonical source of truth for what may be lawfully transited to and from.

6.1 Destination classes

6.2 Current public registry

The following destinations are catalogued as of Q2 2060. Speculative destinations and sovereign-restricted entries are listed in the sealed addendum.

6.3 Certification of new destinations

A new destination signature enters the atlas only after a sustained certification campaign:

1. Probe certification (unmanned, 24 cycles minimum)
2. Continuity certification (controlled biological proxy, 12 cycles)
3. Crew certification (full traveller protocol, 6 cycles, no incidents)
4. Oversight ratification by Meridian/9

The process takes 18 to 30 months. We have abandoned three candidate destinations since 2055 because they could not be sustained to certification standards.

Section 07

Commercial Model

through.co operates as a premium institutional service. Access is offered under three tiers, all of which require vetting by the Meridian/9 board before contract.

7.1 Access tiers

Pricing reflects transit volume, destination clearance and isolation requirements. It does not reflect negotiation: tiers are published, fixed, and applied uniformly within their bracket.

7.2 Service-level commitments

7.3 Sovereign engagements

Sovereign Tier engagements are quoted individually because they incorporate treaty-level provisions, dedicated aperture allocation, and embedded oversight with the Meridian/9 board. We do not publish sovereign pricing.

through.co has six sovereign engagements active as of Q2 2060. Five are governmental; one is intergovernmental.

7.4 What we will not do

The following are not commercially available, irrespective of tier or budget:

• Transit to unverified destinations.
• Transit with no return vector.
• Anonymous transit (all travellers are credentialed).
• Transit for the purpose of circumventing legal jurisdiction.
• Transit of hazardous materials as defined under the Meridian/9 schedule.

We have declined twenty-three commercial offers since 2055 because they fell into one of these categories. None has been escalated to litigation.

Section 08

Governance & Oversight

8.1 The charter

through.co operates under a public charter. The charter is the only contractual document that takes precedence over commercial agreements. Its core provisions are:

1. Operations are governed by the Meridian/9 oversight board, an independent body.
2. The board has the authority to halt operations at any time, without notice.
3. Quarterly audits are mandatory. Findings are publishable.
4. Continuity incidents trigger automatic disclosure to the board.
5. No commercial pressure may override safety protocols.

The charter is amendable only by joint vote of through.co's executive committee and the full Meridian/9 board, with public ratification.

8.2 The Meridian/9 board

The board comprises eleven members:

• Three from academic transit research
• Three from regulatory bodies
• Two from independent safety institutes
• Two rotating sovereign-program representatives
• One chair (currently Dr. Iris Vall, since 2057)

Members serve four-year terms, non-renewable consecutively. Conflicts of interest are declared publicly and recorded in the board's annual transparency report.

8.3 Disclosure policy

through.co publishes:

• Quarterly audit summaries
• Annual transparency reports
• Incident summaries within 30 days of root-cause confirmation
• Annual atlas changes
• This white paper

We do not publish:

• Specifications relating to exit-vector cryptography
• Sovereign engagement details
• Customer-identifiable transit logs
• Speculative destination coordinates

The boundary between the two lists is set by the board, not by through.co. Movements across that boundary are themselves audit findings.

Section 09

Roadmap 2060–2064

This roadmap is published in summary. Detailed milestones are circulated to cleared programs under NDA.

2060 (current)

• TH-13 candidate destination enters Stage 2 certification
• Quiet Meridian facility expansion to 6 apertures
• Updated continuity baseline protocol (CB-3) rolled out

2061

• Helios Anchorage facility Tier B upgrade
• TH-13 expected to enter atlas (subject to certification)
• Joint protocol with Orion Institute on memory-drift research

2062

• Fourth facility evaluation (location pending board approval)
• Aperture Engine v4 sustained-window upgrade (target 18.0 s mean)
• First public academic transit program (limited)

2063

• Aperture network capacity ≥ 100 transits / 24 h
• Multi-aperture parallel commit pilot (Pier C only)
• Expanded archival access program

2064

• Full charter review and ratification vote
• Atlas review across all certifications

Section 10

Glossary

Aperture — A sustained, instrumented transit window between two coordinates.

Aperture Engine — The coordinated three-subsystem apparatus that creates, sustains and closes apertures.

Atlas — The canonical, audited registry of verified destination signatures.

Continuity — The traveller's preserved identity, memory and biometric integrity across a transit.

Coordinate — An addressable location, in space, time, or — in approved cases — an adjacent layer of reality.

Drift — Measurable deviation of any tracked value (phase, vector, continuity) from its baseline.

Phase lock — Acquisition of the destination's vibrational signature by the local aperture array.

Return vector — The pre-validated inverse path from a destination back to the originating coordinate.

Signature — A unique vibrational identifier associated with a coordinate.

Stability field — The structural-integrity field projected around a forming aperture during a transit.

Tier — A class of commercial access (I Research, II Enterprise, III Sovereign).

Transit — The structured displacement of an authorised traveller through an aperture.

Vector commit — The irreversible point at which the system binds a traveller to a specific arrival coordinate.

Section 11

References

This is a public document. The references that appear below are themselves publicly available; restricted references appear only in the sealed addendum.

1. Charter of through.co. through.co Executive Committee & Meridian/9 Oversight Board. 2055, ratified 2057, amended 2059.
2. Aperture Engine — Technical Specification, v3.4. through.co Engineering, 2059. Reference: TH-ENG-045-014.
3. Continuity Baseline Protocol (CB-3). Joint publication, through.co & Northwell Archive, 2060.
4. Independent Audit Findings, 2055–2059. Meridian/9 Oversight Board, annual cumulative report.
5. On the failure modes of pre-2055 transit attempts. Vall, I. Journal of Applied Transit Research, 12 (3), 2057, pp. 411–438.
6. The Pier C protocol: a case study in joint sovereign operations. Pier C Command, restricted briefing, 2058.
7. Atlas changes, 2055–2060. through.co Atlas Committee. Quarterly bulletin.