Glossary · TH-GL-046

Plain language. Same protocol.

Every code, classification and technical term used across the site, the white paper and the public log — explained the way we'd explain it to a new operator on day one. No marketing tone. No filler.

Aperture window

Operations

The brief, instrumented period during which a portal holds stable enough for transit. Averages 12.4 seconds at our facilities. Pre- and post-transit protocol adds roughly 90 minutes on either side.

See also: Phase lock · Vector

Phase lock

Operations

The stabilisation step that precedes every commit. The aperture must hold within 0.05 % of nominal for a sustained interval before the outbound traveller is cleared. Any drift beyond tolerance triggers an automatic holding action.

See also: Holding action · Drift

Vector · Return vector

Operations

The instrumented direction of a transit. Every outbound vector carries its inverse (the return vector) in the active manifest. The return aperture is opened and armed before the outbound is closed — this is what makes every passage reversible by design.

See also: CB-3 · Continuity

Holding action

Operations

The automatic safety hold initiated when aperture parameters drift beyond tolerance during phase lock or transit. The traveller remains in a supervised safe zone while recalibration runs. Holding actions are logged but are not, in themselves, incidents.

See also: Hold · Drift

Drift

Operations

Any measurable deviation of aperture parameters from nominal. Below 0.05 % is absorbed silently; above triggers a phase-lock reattempt or a holding action. Drift events are recorded continuously and reviewed in the quarterly audit.

See also: OS-codes · Holding action

Aperture Engine

Operations

Our proprietary control stack — sensing, stabilisation, commit logic and emergency return. Current generation is v3.4. The v3.2 revision shipped after the OS-2056-04 incident at Pier C.

See also: White paper · TH-ENG-045-014

Atlas

Catalogue

The publicly listed set of verified destinations. Governed by Article §4.2 of the operating charter. The atlas does not list what it cannot vouch for; the journal does not name what is sealed.

See also: Article §4.2 · Tier

Black Level

Catalogue

The highest classification a route can receive. Existence is acknowledged in the atlas. Stability and return vector are sealed. No civilian transit is cleared. Currently held by one signature: Nocturne Gate (NGT-07).

See also: Meridian/9 · Sealed

Restricted · Supervised

Catalogue

Restricted routes are open only to cleared programs under NDA briefings. Supervised routes are open to civilian transit but require sustained human supervision and mandatory pre-transit briefings.

See also: Tier · Access

Archived

Catalogue

A route removed from the active schedule following sustained stability issues or an unexplained event. The route stays catalogued and monitored but no transit is scheduled until cause is determined. Currently held by Lagrange Cathedral (LGC-06).

See also: TJ-007 · Meridian/9

Tier (I · II · III)

Catalogue

The three access programs. Tier I Research is for academic and continuity programs. Tier II Enterprise is for corporations and institutional consortia. Tier III Sovereign is for governments and treaty-based operations.

See also: Pricing · CLR codes

Meridian/9

Governance

The independent oversight board, established in 2055 alongside the company. Has charter authority to halt any operation. Seven members, six-year terms. Currently chaired by Dr. Iris Vall (since 2057).

See also: Charter · Article §4.2

Article §4.2

Governance

The charter article that formalises the three-commitment catalogue policy: we publish routes we are prepared to vouch for, we confirm restricted corridors without describing their operation, we seal archived and black-level signatures. Ratified May 2059.

See also: Atlas · TH-CH-046

Operating Charter

Governance

The public document that defines the company's mandate, oversight authority, classification system and acceptable operations. Reference TH-CH-046. First ratified 2055, amended 2057 and 2059.

See also: Meridian/9 · §4.2

TH- document codes

Codes

Reference prefix for any published ThroughPortal.com document. TH-WP white paper · TH-CH charter · TH-ENG engineering specification · TH-JL journal · TH-GL glossary (this page).

See also: OS-codes · TR-codes

OS- incident codes

Codes

Format OS-YYYY-NN. Year of the event, sequential incident number. OS-2056-04 Pier C aperture lock anomaly (Class B, contained). OS-2058-11 Helios drift during commit (Class C, monitored). Both closed, both published in full on the journal.

See also: Journal · Severity classes

TR- traveller codes

Codes

Format TR-YYYY-NNN. Assigned to every confirmed transit, used in audit, recovery and continuity records. TR-2055-001 identifies the first supervised crossing — Helios Anchorage, September 2055.

See also: TJ-001 · Continuity

Pier C

Partners

The North Atlantic operational hub — physical headquarters of the company, location of the primary commit floor and home of the Pier C atmospheric stack. Operated jointly with Pier C Command under treaty.

See also: Pier C Adjacent (PCA-03)

Northwell Archive · CB-3

Partners

Northwell Archive holds the certified continuity records for archive-class destinations. The Continuity Baseline Protocol 3 (CB-3), signed in 2060, defines the shared standard for return-vector preservation. Applies to all transit to and from Verdant Archive (VDA-04).

See also: TJ-008 · Return vector