Files
settled-reach/wiki/technology/meridian.md
T
jpmschweitzerandClaude Opus 4.7 25eb8bd096 content(wiki): purge v0.1 Sova/Van Maanen residue (#865)
Spring-cleaning accumulated v0.1 vertical-slice residue across the
wiki. Scope per Jeroen's pre-decisions on 2026-04-21:

- Delete outright: wiki/star-systems/GJ-35/sova/ subtree (5 files +
  2 dirs) — v0.1 Station Sova / Transit District content.
- Strip example blocks in authoring guides and _templates/ that
  cited dropped v0.1 NPCs (Kael Davan, Sera Venn, Nils Davan, Devra,
  Torek, Renn, Pell, Tav, Lera Sessik, Sabel). Replaced with short
  "v0.1 examples removed — D-122" notes pointing authors to the
  active NPC roster.
- Rewrite canonical-lore references file-by-file: faction pages,
  technology pages, contraband pages, concepts pages, corp pages
  that cited v0.1 names/places. Preserve institutional/structural
  content, drop specific-name citations.
- Commission name drift: replace "Concord Commission" and "Assembly
  Commission" with "the Lattice Commission" (D-193) throughout.
- Van Maanen's Star cultural references: the canonical in-game name
  is Vuurkloof. "Van Maanen's Star" is retained only as an
  astronomical designation (glossary + GJ-35 Calibration Note).
  All cultural/system references converted to Vuurkloof across
  culture-authoring-guide, cultural-generation-guide, founder-gates,
  and star-system adjacent-system descriptions.
- Strip `v0.1` from faction/triangle frontmatter tags (8 files).
- wiki/triangles/hub-power.md and wiki/factions/the-ring.md:
  rewritten using role-name exemplars (Ring Coordinator / Shift
  Supervisor / THE FRIEND) instead of named v0.1 NPCs. Triangle
  pattern preserved as a structural reference.

Also applies drive-by Commission drift fixes and minor cross-ref
updates to canonical corps (gate-corporation, mastroianni-vehicle-group,
stalownia-kowalski, prometheus-labs, ferreira-monteiro, vins-de-grand-vide,
and 13 others).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-22 10:26:45 +02:00

9.0 KiB

title, description, slug, category, status, created, updated, prevalence, tags, decision_refs, cross_refs
title description slug category status created updated prevalence tags decision_refs cross_refs
Meridian Ubiquitous information network — communications, location tracking, institutional systems, and the surveillance infrastructure the ring operates around meridian technology canonical 2026-02-12 2026-02-13 universal

Meridian

Type: Infrastructure Technology Status: Canonical Scope: Station-wide / system-wide information network Access: Via neural lattice (universal)


Overview

The Meridian is the ubiquitous information network of the Settled Reach — the data layer that connects people, systems, and institutions. Every neural lattice interfaces with the Meridian. It carries communications, provides location services, streams institutional data, hosts professional toolkits, and mediates most of the information flow in civilized space.

Think of it as the nervous system of a station. The lattice is the individual's interface; the Meridian is the network everything connects to.


What the Meridian Provides

Communication: Person-to-person messaging, group channels, institutional notifications. The primary way people coordinate across a station. Faster than walking, less personal than conversation.

Location Services: Lattice-to-Meridian pings allow tracking of individuals (with appropriate access). Law enforcement and Commission personnel can query locations of active lattice signatures. Civilians see friend/colleague locations if mutually opted in.

Institutional Systems: Freight manifests, shift schedules, compliance records, Commission databases, station administration — all run through Meridian infrastructure. A freight scheduler's professional toolkit connects to Meridian to pull container data. A Commission liaison queries Meridian for lattice compliance records.

Environmental Data: Station status, atmosphere readings, power grid status, gate cycle schedules. Background information that most people ignore until something goes wrong.

Entertainment & Social: Music feeds, news tickers, social channels. The ambient hum of connected life. The district bar runs Meridian music feeds. The news ticker that delivers wow moment #5 runs through Meridian.


Coverage Gradients

Meridian coverage is not uniform. This is load-bearing for gameplay.

Zone Coverage Level What Works What Doesn't
Logistics Hub Comprehensive Real-time tracking, manifest systems, full surveillance, professional toolkits Nothing — full coverage
Bar District Strong Standard social monitoring, Meridian feeds, communication, music Fine-grained tracking may lag
Residential Pods Standard Personal lattice connectivity, messaging, basic services Professional toolkits may not stream smoothly
Maintenance Corridors Degraded Intermittent connectivity, delayed messages, patchy location data Real-time tracking unreliable, professional toolkits offline
Between-Wall Spaces Minimal or Absent Little to nothing Everything — effectively off-grid

Why the gaps exist: A working freight station is 100+ years old with layered construction. Meridian infrastructure was installed for the station as designed, not as it was subsequently retrofitted. Older sections between construction eras were never properly wired. Maintenance corridors have basic repeaters that degrade over time and get low priority for replacement.

Why the gaps matter: The smuggling ring operates in Meridian dead spots. Restricted maintenance corridors have zero Meridian signal — no tracking, no surveillance, no logged communications. When NPCs need to discuss something they don't want recorded, they go for a walk to the "quiet spots." The ring's entire operational infrastructure depends on these coverage gaps.


Meridian and Surveillance

The Meridian is, among other things, a surveillance system. Not a secret one — everyone knows their lattice pings their location, that communications are logged, that institutional queries leave traces. This is accepted infrastructure, not conspiracy.

What the Meridian records:

  • Lattice location pings (periodic, not continuous — enough for general tracking, not step-by-step)
  • Communication metadata (who contacted whom, when, duration — not content for civilian channels)
  • Institutional system access logs (who queried what manifest, who accessed what database)
  • Environmental sensor data (motion, temperature, atmosphere — infrastructure monitoring, not surveillance per se)

What the Meridian doesn't record:

  • Conversations held in person (no ambient audio capture in civilian areas)
  • Physical movements in degraded coverage zones
  • Lattice-to-lattice direct connections (peer-to-peer, off-Meridian, short range)

The surveillance paradox: The Meridian makes institutional oversight possible but not automatic. The data exists — but someone has to look at it, query it, cross-reference it. The detective can query Meridian logs to track NPC movements. But the detective has to know what to look for. The data doesn't investigate itself.

This is why the detective's Analytical lattice matters: it automates some of the cross-referencing that would otherwise require manual queries. And it's why Severance technology is so threatening to institutions — it creates zones where the Meridian's passive data collection simply stops working.


Meridian and the Three-Range Sound Model

The Meridian connects to the game's three-range information model:

Range Meridian Role Trust Level
Close (in/near LOS) Not involved — raw sensory data High — your own perception
Medium (outside LOS, nearby) Partial — lattice processes ambient data Moderate — sensory impression augmented by lattice
Long (across map) Primary — insert notifications, location alerts, text messages Low — network-dependent, spoofable, manipulable

Long-range information flows through the Meridian. This means it can be intercepted, delayed, falsified, or blocked. An NPC sending you a tip via Meridian messaging is using a channel that someone else could monitor. A location ping could be masked. A news ticker update runs through Meridian infrastructure that has its own editorial filters.

The further information travels from direct perception, the more the Meridian mediates it — and the less you should trust it.


Dual-Lens Significance

The smuggler uses the Meridian the way everyone does — messaging, navigation, checking shift schedules. They know where the dead spots are from years of living here. Meridian gaps aren't mysterious to the smuggler; they're just the parts of the station where your messages don't send and you learn to have conversations in person. The smuggler navigates Meridian coverage intuitively.

The detective uses the Meridian as an investigative instrument. Querying location logs, cross-referencing communication metadata, mapping coverage gaps as potential operational infrastructure. The detective sees dead spots as evidence — if someone consistently moves through degraded-coverage zones, that's a data point. The Meridian is a forensic tool, not just an amenity.

The tension: The smuggler knows the social geography of Meridian coverage — who goes where and why. The detective knows the data geography — what's logged and what's not. Both are right. Neither has the complete map.


Mechanical Integration

Knowledge Graph:

  • location.surveillance_gaps — Meridian coverage gaps as discoverable knowledge (detective: KnowsOf when augmented lattice detects gaps; smuggler: KnowsDetails from operational experience)
  • location.restricted_corridor — Direct confidence gates monologue: "Zero Meridian signal in this section"

Perception System:

  • Meridian feeds are one input to the insert minimap (D-013)
  • Camera feed perception mode (D-017, Enhanced tier+) accesses Meridian-connected surveillance
  • Meridian tracking mode (D-017, Enhanced tier+) queries lattice location pings
  • Coverage degradation affects which perception modes function in a given area

Information Boundaries:

  • Meridian coverage level determines what long-range information is available in a zone
  • Dead spots are zones where information boundary queries return nothing — even for characters with Enhanced lattices
  • This maps directly to D-010's principle: information boundaries are universal

Cross-References:

  • Neural Lattice — Individual interface to the Meridian
  • Severance Technology — Technology that blocks Meridian functions
  • D-017: Perception modes (camera feeds, tracking via Meridian)
  • D-018: Three-range sound model (long range = Meridian-mediated)
  • D-013: Diegetic insert navigation (Meridian-fed waypoints)

Status: Canonical — station-wide information infrastructure Created: 2026-02-12 Updated: 2026-02-12