jpmschweitzer/settled-reach
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge remote-tracking branch 'origin/sprint-37/copy'

Browse Source 
Resolved 8 conflicts in wiki/corporations/ between server #860 tag
updates and copy #861 three-layer authoring. Resolution: union of
server's commodity-tag additions + D-175 decision_refs, plus copy's
cross_refs populated entries.
This commit is contained in:
jpmschweitzer
2026-04-22 11:25:55 +02:00
parent b71c505c4d 75287f9534
commit fcd434e528
185 changed files with 10116 additions and 4003 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.config/hooks/pre-push
+22 -4
View File
@@ -9,14 +9,27 @@ ERRORS=0
echo "pre-push: running lint checks..."
# --- Detect which directories have changes vs remote ---
# Prefer origin/<branch> as the baseline (what the remote already has),
# but fall back to origin/main for first-push of a new branch — otherwise
# every check runs against nothing and the hook treats the whole repo as
# changed, spending tens of seconds on linters and JSON validation that
# have no diff to cover (e.g. pushing a wiki-only branch rebuilds GDScript
# and runs clippy + ruff + validates all 2762 JSON files).
BRANCH=$(git branch --show-current)
REMOTE_REF="origin/$BRANCH"
if git rev-parse --verify "$REMOTE_REF" >/dev/null 2>&1; then
if git rev-parse --verify "origin/$BRANCH" >/dev/null 2>&1; then
REMOTE_REF="origin/$BRANCH"
elif git rev-parse --verify "origin/main" >/dev/null 2>&1; then
REMOTE_REF="origin/main"
else
REMOTE_REF=""
fi
if [ -n "$REMOTE_REF" ]; then
CLIENT_CHANGED=$(git diff --name-only "$REMOTE_REF"..HEAD -- client/ 2>/dev/null | wc -l)
SERVER_CHANGED=$(git diff --name-only "$REMOTE_REF"..HEAD -- server/ 2>/dev/null | wc -l)
TOOLING_CHANGED=$(git diff --name-only "$REMOTE_REF"..HEAD -- tooling/ pyproject.toml 2>/dev/null | wc -l)
else
# New branch or no remote ref — fall through to directory checks
# No remote at all (e.g. fresh clone before first fetch) — be safe, run everything
CLIENT_CHANGED=1
SERVER_CHANGED=1
TOOLING_CHANGED=1
@@ -114,7 +127,12 @@ else
fi
# --- JSON syntax validation ---
if git rev-parse --verify "$REMOTE_REF" >/dev/null 2>&1; then
# Use the same REMOTE_REF the directory-change detection above settled on
# (origin/<branch> preferred, origin/main fallback). Without this, a first
# push of a new branch falls through to "validate every JSON in the repo,"
# which on this repo means 2762 Python parses — tens of seconds of churn
# for a push that might not have touched any JSON at all.
if [ -n "$REMOTE_REF" ]; then
JSON_FILES=$(git diff --name-only "$REMOTE_REF"..HEAD -- '*.json' 2>/dev/null || true)
else
JSON_FILES=$(git ls-files '*.json')
decisions/content.md
+10 -1
View File
@@ -607,6 +607,15 @@ How narrative, NPCs, and world content are created: content tiers, NPC generatio
- **Raised by:** Miri (Sprint 31, ticket #773)
- **Dissent:** None.
### D-193: Lattice Commission — canonical long-form of the Commission
- **Date:** 2026-04-21
- **Decision:** The Concord Assembly's regulatory authority is formally named **"the Lattice Commission"**. In-prose short form remains "the Commission" (unambiguous in context). Drift forms that appeared in earlier copy reviews — "Concord Commission" and "Assembly Commission" — are **non-canonical** and must be corrected wherever they appear. The long-form is required for institutional POI signage, tractus fee legal text, wiki page headers, and any formal/legal context.
- **Rationale:** The Commission's regulated domain — implant hardware, medical-grade replacements, pharmaceutical production, and safety-critical manufactured goods that feed the Lattice — is what authorizes and scopes its jurisdiction. Naming it after the regulated domain (rather than the parent Assembly) mirrors how real-world regulatory bodies are often named by what they regulate (FDA, FAA, NRC) rather than by their chartering body. It also disambiguates from "Concord" which otherwise appears in the Concord Assembly itself, the Concord's member systems, etc. The Commission has no authority in Compact member systems — its identity is Lattice-scoped, not Concord-scoped.
- **Affects:** Wiki content (all `wiki/factions/`, `wiki/technology/`, `wiki/corporations/` pages that reference the Commission), marker POI naming (e.g. `"Lattice Commission — Sirius Office"`), formal legal text in tractus fee documentation, institutional signage, institution templates in `wiki/_templates/`, dialogue pools, copy guides.
- **Resolves:** [Q-095](questions-content.md#q-095-commission-formal-name--authoritative-designation)
- **Raised by:** Copy review (Sprint 35, PR #127); resolved by Jeroen on 2026-04-21
- **Dissent:** None.
---
*46 decisions. Last updated: 2026-04-05 (D-168 Iserlohn IP evaluation filed)*
*47 decisions. Last updated: 2026-04-21 (D-193 Lattice Commission name resolved)*
decisions/questions-content.md
+4 -3
View File
@@ -229,12 +229,13 @@ Narrative, NPCs, dialogue, templates, setting, worldbuilding, and storyteller me
---
### Q-095: Commission formal name — authoritative designation
- **Status:** Open
- **Status:** Resolved — see [D-193](content.md#d-193-lattice-commission--canonical-long-form-of-the-commission) (2026-04-21)
- **Resolution:** Canonical long-form is **"the Lattice Commission"**. Short form "the Commission" remains standard in-prose. "Concord Commission" and "Assembly Commission" drift forms are non-canonical.
- **Question:** What is the full formal name of the Concord Assembly's regulatory authority? In-prose use is "the Commission", but several drift forms have appeared in copy reviews ("Concord Commission", "Assembly Commission", "Lattice Commission"). A canonical long-form is needed for formal/legal contexts, institutional signage, and wiki headers.
- **Context:** The Commission certifies implant hardware, medical equipment, pharmaceutical production, and safety-critical manufactured goods under tractus-denominated fees. It has no authority in Compact member systems. Current glossary guidance is to use "the Commission" until the full name is resolved, but authors writing institutional POIs and formal documents need a decision.
- **Affects:** Wiki content, marker POI naming (e.g. `"Commission — Sirius Office"`), formal legal text in tractus fee documentation, institutional signage.
- **Affects:** Wiki content, marker POI naming (e.g. `"Lattice Commission — Sirius Office"`), formal legal text in tractus fee documentation, institutional signage.
- **Source:** Sprint 35 copy review (PR #127)
---
*25 questions (10 resolved, 2 partially resolved, 13 open). Last updated: 2026-04-14 (Q-095 added — Commission formal name)*
*25 questions (11 resolved, 2 partially resolved, 12 open). Last updated: 2026-04-21 (Q-095 resolved — D-193 Lattice Commission)*
decisions/questions.md
+3 -3
View File
@@ -17,9 +17,9 @@ Tracked questions awaiting discussion or resolution. Split by domain, mirroring
|--------|-------|----------|---------|------|
| Architecture | 46 | 6 | 1 | 39 |
| Perception | 9 | 5 | 0 | 4 |
| Content | 25 | 10 | 2 | 13 |
| Content | 25 | 11 | 2 | 12 |
| Scope | 17 | 6 | 2 | 9 |
| **Total** | **97** | **27** | **5** | **65** |
| **Total** | **97** | **28** | **5** | **64** |
*Updated 2026-04-05: Full recount. Q-002, Q-004, Q-005, Q-007 closed as resolved (D-117/D-166). Architecture index corrected (was 13, actually 46 — Q-060 through Q-094 were missing from index).*
@@ -35,4 +35,4 @@ Tracked questions awaiting discussion or resolution. Split by domain, mirroring
When in doubt about where a question belongs: if it constrains **how we build**, it's architecture. If it defines **what the player observes or knows**, it's perception. If it defines **narrative, NPCs, dialogue, or setting**, it's content. If it defines **what we ship or how big it is**, it's scope.
*97 questions. Last updated: 2026-04-14 (Q-095 added — Commission formal name).*
*97 questions. Last updated: 2026-04-21 (Q-095 resolved — D-193 Lattice Commission).*
wiki/GOVERNANCE.md
+5 -5
View File
@@ -78,10 +78,10 @@ No nesting within flat categories. Use `cross_refs` in frontmatter for relations
## Scale Considerations
The spatial hierarchy is designed to scale from 1 star system (v0.1) to 500+ (full game):
The spatial hierarchy is designed to scale from a single starting system to 500+ (full game):
- Each system is a self-contained directory tree
- Cross-system references use full slug paths (e.g., `star-systems/van-maanens-star/sova/transit`)
- Cross-system references use full slug paths (e.g., `star-systems/{system-slug}/{station-slug}/{district-slug}`)
- Characters, factions, and other flat categories remain at wiki root — they are not nested per system
- Characters reference their home district via `home_district` frontmatter field
@@ -89,9 +89,9 @@ The spatial hierarchy is designed to scale from 1 star system (v0.1) to 500+ (fu
## Naming Conventions
- **File slugs:** lowercase, hyphenated (e.g., `kael-davan.md`, `the-last-shift.md`)
- **Directory slugs:** lowercase, hyphenated (e.g., `van-maanens-star/`, `sova/`, `transit/`)
- **Canonical IDs:** match content schema format (e.g., `npc:kael-davan`)
- **File slugs:** lowercase, hyphenated (e.g., `vuurkloof.md`, `freight-exchange.md`)
- **Directory slugs:** lowercase, hyphenated (e.g., `vuurkloof/`, `{station-slug}/`, `{district-slug}/`)
- **Canonical IDs:** match content schema format (e.g., `npc:{character-slug}`)
- **Display names:** title case, as they appear in-game
---
wiki/_templates/character-exemplar.md
+134 -189
View File
@@ -1,34 +1,32 @@
---
title: "Kael Davan"
description: "EXEMPLAR — Tier 1 FRIEND (smuggler), dock worker entangled in smuggling ring. Use as reference for generator output quality."
slug: kael-davan
canonical_id: "npc:kael-davan"
title: ""
description: "EXEMPLAR — Tier 1 NPC quality target for generator pipeline (D-122)"
slug: ""
canonical_id: ""
category: character
status: exemplar
created: 2026-02-12
updated: 2026-03-13
created: YYYY-MM-DD
updated: YYYY-MM-DD
tier: 1
pattern: "FRIEND"
motivation: "OPERATOR"
social_sites: [logistics-hub, smuggling-ring]
pattern: ""
motivation: ""
social_sites: []
entanglement: "Entangled"
triangles: [hub-power, worried-partner]
home_district: transit
triangles: []
home_district: ""
tags: [generator-exemplar]
decision_refs: [D-024, D-034, D-122]
cross_refs: [nils-davan, naia-tamm, sera-venn, voss, renn]
cross_refs: []
---
<!-- EXEMPLAR NOTE
This is a fully worked example of a Tier 1 NPC profile. It was hand-authored
for v0.1 and is preserved as the quality target for the v0.2 generator pipeline
(D-122). The generator should produce NpcBlueprint structs that encode this
level of depth for Tier 1 characters. Not all fields need to be this detailed
for Tier 2-3 characters.
This template documents the quality target for a Tier 1 NPC profile. The v0.2
generator pipeline (D-122) should produce NpcBlueprint structs that encode this
level of depth for Tier 1 characters. Tier 2-3 characters may use lighter profiles.
Key quality markers this exemplar demonstrates:
Key quality markers this exemplar format demonstrates:
- 10-axis profile with concrete, actionable content per axis
- Dual-lens notes showing how both player characters read the same NPC differently
- Dual-lens notes showing how different player archetypes read the same NPC
- Tell system with observable triggers and mechanical flags
- Contradiction arc with timed phases and emotional payoff
- Triangle roles showing how this character functions in multi-NPC dynamics
@@ -36,21 +34,21 @@ Key quality markers this exemplar demonstrates:
- Content requirements with concrete line counts per category
-->
# Kael Davan — THE FRIEND (Smuggler)
# {Name} — {Pattern} ({Role})
**Tier 1 Production-Level NPC** | Logistics Hub + Smuggling Ring | Entangled
**Tier 1 Production-Level NPC** | {social_sites} | Entangled
---
## Core Identity
**Name**: Kael Davan
**Age**: 34
**Role**: Dock worker, Sova Transit District Logistics Hub
**System Origin**: Van Maanen's Star, born on Station Sova
**Cultural Group**: Van Maanen's Star culture (compact names, first-name-primary, pragmatic, mind-your-business ethos)
**Lattice Tier**: Baseline
**Employer**: Sova Logistics Consortium (legitimate cover); The Arrangement (smuggling ring, informal)
**Name**: {full name}
**Age**: {age}
**Role**: {occupation/function}
**System Origin**: {home system and station}
**Cultural Group**: {cultural group slug}
**Lattice Tier**: {Baseline | Enhanced | Analytical}
**Employer**: {employer(s)}
---
@@ -58,290 +56,237 @@ Key quality markers this exemplar demonstrates:
### 1. Want
**Primary**: Protect the operation and the people in it.
**Primary**: {1-line want statement}
Kael didn't join the ring for ideology or ambition. He joined because Nils (his older sibling) asked, because the money helped, and because it felt manageable. Two years in, Kael is good at it — efficient, careful, reliable. But the operation is escalating (higher volume, tighter margins, more risk), and Kael's Want is shifting from "keep things running" to "keep people safe."
{Expansion: why they want this, how it manifests, trajectory.}
**Secondary**: Protect Naia (partner) from the truth and the consequences.
Naia doesn't know about the smuggling. Kael's late nights and evasive answers are creating anxiety at home. Kael Wants to shield Naia from danger, but the shielding itself is the danger.
**Secondary**: {1-line secondary want — often in tension with primary}
---
### 2. Secret / Vulnerability
**Surface secret** (smuggler knows, detective suspects): Ring member. Handles physical cargo — routing flagged containers, managing dock-side handoffs.
**Surface secret** (some know, others suspect): {what is partially visible}
**Deep secret** (nobody knows except the unknown contact): Kael is trying to **exit the ring**. Naia's worry has become unbearable. Kael contacted someone from a different district (not Sabel, not anyone the ring knows) who's offered to help Kael get out — for a price. The unknown contact is leverage (they know Kael is in the ring), extraction support (they have connections), and a massive security breach (unauthorized contact is grounds for ring elimination).
**Deep secret** (nobody knows): {what is entirely concealed}
**Vulnerability**: The exit attempt. If Nils finds out, Kael is out — violently. If the smuggler (if playing ring-member path) finds out, trust collapses. If the detective finds out, Kael is the perfect informant (desperate, motivated, already halfway to cooperation).
**Vulnerability**: {what breaks them — the lever that can be pulled}
---
### 3. Relationships
**Relationship 1: Nils Davan** (older sibling, ring coordinator)
- **Type**: Blood loyalty, complicated by power dynamic
- **History**: Nils brought Kael into the ring. "It's just moving containers. You're good at logistics. We take care of our own."
- **Current tension**: Nils is pushing for higher volume. Kael thinks it's too fast, too risky. Kael can't say no to Nils (family), but resents being pushed.
- **Mechanical relevance**: If Kael's exit attempt is discovered, Nils is the primary threat.
**Relationship 1: {Name}** ({connection type})
- **Type**: {relationship nature}
- **History**: {how it formed}
- **Current tension**: {what is straining it}
- **Mechanical relevance**: {how this relationship matters to gameplay}
**Relationship 2: Naia** (partner, teacher, civilian)
- **Type**: Domestic partnership, 6 years
- **History**: Met at a community event. Naia teaches station kids, represents ordinary life, stability, the future Kael wants but smuggling threatens.
- **Current tension**: Naia knows something's wrong. The late nights, the evasive answers, the money that doesn't quite track. Naia has confided in Sera (friend, Commission field tech). Kael is oblivious to how much anxiety he's causing.
- **Mechanical relevance**: Naia is Kael's emotional anchor and his vulnerability. Threaten Naia, Kael breaks.
**Relationship 2: {Name}** ({connection type})
- **Type**: {relationship nature}
- **History**: {how it formed}
- **Current tension**: {what is straining it}
- **Mechanical relevance**: {how this relationship matters to gameplay}
**Relationship 3: The Smuggler** (if smuggler is playing ring-member path)
- **Type**: Close colleague, trusted friend, shared risk
- **History**: Work together on legitimate shifts AND ring operations. Cover for each other. Share lunch, drinks at Lera's, the easy camaraderie of people who've been through things together.
- **Current tension**: Kael is lying to the smuggler. The unauthorized contact, the exit attempt — all of it is concealed. The smuggler trusts Kael completely, which makes the betrayal worse when discovered.
- **Mechanical relevance**: THE FRIEND. The relationship phase arc (warmth → trust → doubt → conflict) plays out here.
**Relationship 3: {Name/Player}** ({connection type})
- **Type**: {relationship nature}
- **History**: {how it formed}
- **Current tension**: {what is straining it}
- **Mechanical relevance**: {how this relationship matters to gameplay}
---
### 4. Tolerance Threshold
**Moderate** — Kael can handle pressure, but has limits.
**{Low | Moderate | High}** — {1-line summary}
**What Kael tolerates**:
- Routine smuggling operations (manageable risk)
- Voss's resentment and Nils's demands (family and operational necessity)
- Lying to Naia (hates it, but does it to protect)
**What they tolerate**: {list}
**What pushes Kael toward breaking**:
- Escalating volume (feels like the operation is spiraling)
- Naia's increasing worry (guilt accumulation)
- The detective's investigation (paranoia about exposure)
**What pushes them toward breaking**: {list}
**What breaks Kael**:
- Direct threat to Naia (if the ring or the detective uses Naia as leverage, Kael flips immediately)
- Nils discovering the exit attempt (Kael either runs or fights, no middle ground)
**What breaks them**: {list — the hard limits}
---
### 5. Daily Routine
**06:00 - 06:30**: Arrive at Logistics Hub, shift startup
**06:30 - 10:30**: Morning shift, freight handling (legitimate work)
**10:30 - 11:00**: Break room, lunch with smuggler (if applicable) or other dock workers
**11:00 - 14:00**: Afternoon shift
**14:00 - 14:30**: Shift end, sometimes lingers for "overtime" (ring operations during transition window)
**14:30 - 16:00**: Off-shift, heads home or to The Last Shift (bar)
**16:00 - 22:00**: Home with Naia, or occasional ring coordination meetings (Corridor B-7, back room)
**22:00+**: Late-night ring operations (1-2x per week, during night shift transition)
{Time-stamped routine. Mark ring/operation deviations as tells.}
**Routine deviations** (tells):
- Increased lattice checking (nervous, expecting contact from exit coordinator)
- Shortened social interactions (distracted, avoiding prolonged conversation)
- Late arrivals home (Naia notices, worries)
- Unauthorized presence in Corridor B-7 (the contradiction discovery moment for smuggler)
- {deviation}: {what it signals}
---
### 6. Information Inventory
**Knows** (KnowsDetails or Direct):
- Ring structure: Nils coordinates, Voss provides scheduling cover, Renn handles courier work, Lera provides handoff point, Devra manages external contacts
- Smuggling routes: freight bay → service corridor → temp storage → bar back room
- Shift schedules and coverage gaps (operational knowledge)
- Manifest doctoring process (Maret processes, Voss approves)
- Drin's compromise (gambling debt to Harek, looks away during inspections)
- Naia's worry (knows Naia suspects something, doesn't know Naia talked to Sera)
- {fact}: {what they know about it}
**Doesn't know**:
- The detective is investigating (unless playing detective path and Kael has been flagged)
- Sera is sitting on unreported evidence about Kael's manifest discrepancies (protects Naia by not reporting)
- Pell is considering turning informant (internal ring threat)
- The full supply chain (Kael knows cargo comes from Sabel off-station, doesn't know upstream Syndic sources)
- {fact}: {the gap in their knowledge}
---
### 7. Contentment
**Moderate-low** (D-024 thematic axis).
**{Level descriptor}** ({D-024 thematic axis}).
Kael is *comfortable enough to function* but not happy. The smuggling pays well, the work is manageable, the team (Nils, smuggler, Renn) is solid. But the guilt about lying to Naia is corrosive. The escalating volume makes every shift feel riskier. The exit attempt is itself a contentment signal: Kael wants out because "enough" isn't enough anymore — the cost is too high.
**Contentment trajectory**: Declining. Two years ago, Kael was moderate (the operation was stable, Naia didn't suspect). Now, Kael is low and falling. The exit attempt is a desperate grab for a future that doesn't involve looking over his shoulder.
{Expansion: why they're at this level, what's raising or lowering it, trajectory.}
---
### 8. Personality Traits
**Primary: Loyal** — to people, not institutions. Kael's loyalty is personal (Nils, Naia, the smuggler) and situational (the ring, because the people he cares about are in it). If forced to choose between the ring and a person, Kael chooses the person.
**Primary: {Trait}** — {how it manifests}
**Secondary: Protective** — defaults to shielding others from consequences. Lies to Naia to protect. Tries to exit the ring to protect Naia from future fallout. Would cover for the smuggler even at personal cost.
**Secondary: {Trait}** — {how it manifests}
**Tertiary: Pragmatic** — doesn't waste words, doesn't dramatize. Handles problems as they arise. The exit attempt is Kael being pragmatic: "This situation is unsustainable. I need a way out. I'll find one."
**Tertiary: {Trait}** — {how it manifests}
---
### 9. Tell System
**Observable behavioral changes that signal Kael's internal state:**
| Tell | Trigger | Observable To | Mechanical Flag |
|------|---------|---------------|-----------------|
| **Increased lattice checking** | Expecting contact from exit coordinator | Smuggler (if observant), Detective (if tracking behavioral patterns) | `behavior_flags: lattice_checking` |
| **Shortened social interactions** | Distracted, avoiding prolonged conversation where lies might surface | Smuggler, Naia, bar regulars | `behavior_flags: distracted,evasive` |
| **Looks left before answering** | Lying or deflecting (Kael's personal tell, smuggler knows this from history) | Smuggler (recognizes the tell from experience) | `tell_observed: looks_left_when_lying` |
| **Unauthorized spatial presence** | Meeting unknown contact in Corridor B-7 (restricted area, not part of normal routine) | Smuggler (direct observation), Detective (if surveillance active) | `contradiction_flagged: meeting_unknown_contact` |
| {tell description} | {what causes it} | {who can observe} | `behavior_flags: {flag}` |
**Tell progression** (smuggler's perspective):
1. **Week 1-2** (baseline): Kael is normal. Reliable, warm, punctual.
2. **Week 3** (first crack): Kael checks lattice more often. Smuggler monologue: "Kael's distracted today. Probably nothing."
3. **Week 4** (pattern): Shortened lunch conversations. Kael excuses himself early. Smuggler monologue: "Kael's been quiet lately."
4. **Week 5** (the observation): Smuggler sees Kael in Corridor B-7, talking to unknown person. THE FRIEND contradiction discovered. Smuggler monologue: "That wasn't anyone from our rotation. Kael, what are you doing?"
**Tell progression**:
1. **Phase 1** (baseline): {normal behavior}
2. **Phase 2** (first crack): {first observable deviation}
3. **Phase 3** (pattern): {repeated tell}
4. **Phase 4** (contradiction): {the observable contradiction — THE moment}
---
### 10. Skill Set
**Occupational**: Freight logistics, cargo handling, manifest reading, shift coordination.
**Ring-relevant**: Container routing, timing coordination (knows when surveillance gaps occur), physical cargo movement (lifts, secures, reroutes).
**Combat tag**: **No**. Kael is not combat-trained. If cornered, Kael runs or capitulates. Violence is not part of Kael's skill set or personality.
**Lattice capability**: Baseline tier. No enhanced perception, no analytical overlays. Kael uses lattice for communication, shift schedules, and routine queries.
**Occupational**: {skills}
**Ring-relevant**: {operational skills, if applicable}
**Combat tag**: **{Yes | No}**
**Lattice capability**: {tier and functional description}
---
## Backstory
Born on Station Sova. Grew up in the freight district — child of logistics workers, pragmatic Van Maanen's Star upbringing. Joined Sova Logistics Consortium at 22, worked the docks for a decade before Nils (older sibling, always more ambitious) brought him into the ring. "It's just moving containers, Kael. You're good at this. We take care of our own." Two years in, Kael is good at it — efficient, careful, trusted. But the operation is escalating, Naia is worried, and Kael realizes he's in deeper than he intended. The exit attempt is Kael trying to reclaim a future that doesn't end in a cell or worse.
{2-3 sentences: origin, how they ended up in this situation, what they want that got them here.}
---
## Voice Sample
**Mood: Casual (baseline, smuggler interaction)**
- *"Shift's looking smooth today. Freight's on schedule, no surprises. Let's keep it that way."*
**Mood: Casual (baseline)**
- *"{line}"*
**Mood: Protective (deflecting Naia's worry)**
- *"I'm fine, Naia. Just work stuff. Long shifts, you know how it is. Don't worry about me."*
**Mood: Protective / Deflecting**
- *"{line}"*
**Mood: Evasive (post-contradiction, smuggler pressing)**
- *"It's nothing. Just a thing. Don't worry about it."* [Looks left before answering — the tell]
**Mood: Evasive (post-contradiction)**
- *"{line}"* [{the tell, if visible}]
**Mood: Desperate (if cornered by detective or Nils)**
- *"You don't understand. I'm trying to protect someone. If I don't get out, they're at risk. I can't— I can't keep doing this."*
**Mood: Warm (to smuggler, early game)**
- *"There you are. Good — I was starting to worry. Ready for another day of making the galaxy's freight move?"* [Slight smile, genuine relief]
**Mood: Desperate (cornered)**
- *"{line}"*
---
## Dual-Lens Notes
### How the Smuggler Sees Kael
### How Archetype A Sees {Name}
**Access tier**: Insider + Peer (if ring-member path) OR Peer (if non-ring civilian smuggler)
**Relationship**: Friendly (baseline) → PersonOfInterest (post-contradiction)
**Monologue tone (baseline)**: Fond, casual. *"Kael's here. Good — always reliable."*
**Monologue tone (post-contradiction)**: Conflicted, analytical. *"Kael's lying to me. I know his tells. What are you hiding?"*
**Access tier**: {tier}
**Relationship**: {state → state}
**Monologue tone (baseline)**: {register descriptor}. *"{example line}"*
**Monologue tone (post-contradiction)**: {register shift}. *"{example line}"*
**What the smuggler knows that the detective doesn't**: Kael is a ring member (if smuggler is also in the ring). Kael's personal tell (looks left when lying). Kael's relationship with Naia. The unauthorized meeting is a *betrayal of operational security*, not just suspicious behavior.
**What Archetype A knows that Archetype B doesn't**: {information asymmetry}
**Emotional weight**: Maximum. Kael is THE FRIEND. The color shift from green to amber is the moment the smuggler realizes trust has been compromised.
**Emotional weight**: {Low | Medium | High | Maximum} — {why}
---
### How the Detective Sees Kael
### How Archetype B Sees {Name}
**Access tier**: Public (baseline) → Authority (if investigation escalates and detective pressures Kael)
**Relationship**: Unknown → Known → PersonOfInterest (if tells accumulate)
**Monologue tone (baseline)**: Clinical, observational. *"Dock worker. Davan, K. Unremarkable on paper."*
**Monologue tone (post-tells)**: Analytical suspicion. *"Davan's nervous. Lattice activity spiked. Behavioral pattern suggests concealment."*
**Access tier**: {tier}
**Relationship**: {state → state}
**Monologue tone (baseline)**: {register descriptor}. *"{example line}"*
**Monologue tone (post-contradiction)**: {register shift}. *"{example line}"*
**What the detective knows that the smuggler doesn't**: Manifest discrepancies tied to Kael's shifts (if Sera has shared or detective has analyzed logs). Naia's worry (if detective talks to Naia or Sera). Kael as a pressure point — partner at risk, potential informant.
**What Archetype B knows that Archetype A doesn't**: {information asymmetry}
**Emotional weight**: Low initially (just another dock worker). High if Kael becomes the key to cracking the ring (the detective's professional satisfaction vs. Kael's desperation creates tension, but not personal betrayal).
**Emotional weight**: {Low | Medium | High | Maximum} — {why}
---
## Triangle Roles
### Hub Power (Voss - Kael - Nils)
### {Triangle Name} ({NPC 1} - {Name} - {NPC 3})
**Kael's function**: The executor. Kael handles the physical work — routing containers, managing dock-side operations. Caught between Voss (shift supervisor, resentful of being managed) and Nils (ring coordinator, Kael's sibling, pushing for escalation).
**{Name}'s function**: {role in the triangle}
**Pressure**: Voss complains to Kael about Nils. Nils gives Kael orders. Kael has to keep both satisfied while doing the actual smuggling work.
**Pressure**: {what forces are acting on this character through the triangle}
**Player relevance**: Smuggler (if in ring) helps Kael navigate this. Detective sees Kael as efficient and wonders why Voss seems nervous around him.
---
### Worried Partner (Naia - Kael - Sera)
**Kael's function**: The oblivious cause. Kael's smuggling (late nights, evasive answers) is making Naia worried. Naia confides in Sera. Sera knows enough to connect Kael to the investigation but hasn't reported (loyalty to Naia). Kael doesn't know Naia talked to Sera.
**Pressure**: Naia's worry is escalating. If Naia confronts Kael directly, Kael has to lie or confess. If Sera reports, Naia's life explodes. Kael is trying to exit the ring to stop the worry, but the exit attempt is itself creating more risk.
**Player relevance**: Smuggler (if Kael's friend) knows why Kael is busy, can't tell Naia. Detective (if Sera's friend) might hear about Naia's worry from Sera, creating a path to Kael.
**Player relevance**: {how each archetype engages with this triangle through this character}
---
## Contradiction Arc
### Phase 1: Comfort (Friendly, baseline)
### Phase 1: {Name} (Friendly, baseline)
**Timing**: 0-10 minutes (game start)
**Observable behavior**: Kael is warm, reliable, present. Greets the smuggler with genuine affection.
**Monologue (smuggler)**: *"Kael's already at the dock. Good. The day's better when he's on shift."*
**Color**: Soft green (Friendly)
**Tell**: None — baseline normal.
**Timing**: {minutes}
**Observable behavior**: {what is visible}
**Monologue (Archetype A)**: *"{line}"*
**Color**: {relationship color}
**Tell**: {none | which tell}
### Phase 2: First Crack (still Friendly, but flags accumulating)
### Phase 2: First Crack
**Timing**: 10-15 minutes
**Observable behavior**: Kael checks lattice more often than usual. Excuses himself from lunch early.
**Monologue (smuggler)**: *"Kael's distracted today. Probably nothing."*
**Color**: Still green, but `behavior_flags` update to `"lattice_checking,distracted"`.
**Tell**: **Increased lattice checking** (observable if smuggler pays attention).
**Timing**: {minutes}
**Observable behavior**: {first deviation from baseline}
**Monologue (Archetype A)**: *"{line}"*
**Tell**: {which tell fires}
### Phase 3: The Observation (Friendly → PersonOfInterest)
### Phase 3: The Observation ({Friendly} → {PersonOfInterest})
**Timing**: 15-20 minutes
**Trigger**: The smuggler sees Kael in Corridor B-7 talking to an unknown person.
**Monologue (smuggler)**: *"That wasn't anyone from our rotation. And Kael didn't tell me about a meeting. What's going on?"*
**Color shift**: Soft green → amber. **This is the emotional moment.**
**Timing**: {minutes}
**Trigger**: {what the player observes}
**Monologue (Archetype A)**: *"{line}"*
**Color shift**: {color A → color B}. **This is the emotional moment.**
### Phase 4: Confrontation Opportunity (PersonOfInterest, dialogue shift)
### Phase 4: Confrontation Opportunity
**Timing**: 20-25 minutes
**Trigger**: Smuggler can ask Kael about the meeting.
**Kael's response** (deflection): *"Just a thing. Don't worry about it."* [Looks left — **the tell**]
**Monologue (smuggler)**: *"He looked left. He always looks left when he's making something up. Kael is lying to me."*
**Timing**: {minutes}
**Trigger**: {player action that opens dialogue}
**{Name}'s response**: *"{deflection line}"* [{tell, if visible}]
**Monologue**: *"{player's recognition line}"*
### Phase 5: New Equilibrium (PersonOfInterest, contaminated trust)
### Phase 5: New Equilibrium
**Timing**: 25-30 minutes
**Observable behavior**: Kael acts normal again. But the smuggler is now **watching**.
**Monologue (smuggler)**: *"Same old Kael. Laughing at the same jokes. ...What are you not telling me?"*
**Timing**: {minutes}
**Observable behavior**: {surface normalcy, new underlying state}
**Monologue**: *"{player's contaminated-trust line}"*
**Dialogue branches**:
- **Path A (understanding)**: Smuggler confronts gently. Kael might confess. Tone shifts to sympathetic.
- **Path B (betrayal)**: Smuggler reports to Nils. Kael turns hostile.
- **Path C (observation)**: Smuggler watches silently. Tension simmers.
- **Path A ({choice})**: {outcome}
- **Path B ({choice})**: {outcome}
- **Path C ({choice})**: {outcome}
---
## Authoring Notes
- **Kael's voice**: Direct, practical, short sentences. Doesn't waste words. Uses first names. Warm to people he trusts, evasive when hiding something.
- **The tell** (looks left when lying) must be established early in casual dialogue so the smuggler (and player) recognize it during the contradiction.
- **Naia references**: Kael mentions Naia in casual conversation ("Naia's got a school event tonight, so I'm heading home early"). Establishes the relationship before it becomes load-bearing.
- **Ring operations dialogue** (if smuggler is in ring): Matter-of-fact, operational. "Container 4471 is flagged. I'll reroute it during shift transition." No drama, no theatrics.
- **Deflection dialogue** (post-contradiction): Kael doesn't lie outright. Kael deflects: "It's handled." "Don't worry about it." "Just work stuff." The evasion itself is the tell.
- **Dual-lens discipline**: Every Kael line must work for BOTH the smuggler (who knows Kael personally) AND the detective (who reads Kael analytically). The same sentence lands differently per character.
- **Voice**: {speech pattern, sentence length, vocabulary register}
- **The tell**: {which tell, why it works, how to establish it early}
- **{Key relationship} references**: {how to seed this relationship in casual dialogue}
- **Operational dialogue**: {register for work/role-specific lines}
- **Deflection dialogue**: {how they evade rather than lie outright}
- **Dual-lens discipline**: {what must work for both archetypes — and why}
---
## Pattern / Motivation
**Pattern (System A):** FRIEND — Trust anchor whose relationship with the player is the emotional core. The FRIEND pattern means betrayal carries maximum emotional weight.
**Motivation (System B):** OPERATOR — Runs ring cargo at the dock level. Routes containers, manages handoffs, coordinates timing.
**Composition read:** FRIEND + OPERATOR creates the identity betrayal: "I was your friend AND your co-conspirator." The player trusted Kael as a person (FRIEND) while relying on Kael as a functional colleague (OPERATOR). When the contradiction surfaces, the betrayal cuts both relationships simultaneously.
**Pattern (System A):** {PATTERN} — {what this pattern means for the character}
**Motivation (System B):** {MOTIVATION} — {what this motivation drives}
**Composition read:** {how pattern + motivation interact to define the character's dramatic function}
wiki/_templates/character.md
+4 -4
View File
@@ -1,8 +1,8 @@
---
title: "" # Display name (e.g., "Kael Davan")
description: "" # One-line summary for context filtering (e.g., "Tier 1 detective NPC, central to Hub Power triangle")
slug: "" # URL-safe identifier (e.g., "kael-davan")
canonical_id: "" # e.g., "npc:kael-davan"
title: "" # Display name (e.g., "Brek Kost")
description: "" # One-line summary for context filtering (e.g., "Tier 2 shift supervisor NPC, anchor for workplace triangle")
slug: "" # URL-safe identifier (e.g., "brek-kost")
canonical_id: "" # e.g., "npc:brek-kost"
category: character
status: proposed # proposed | draft | canonical
created: YYYY-MM-DD
wiki/_templates/cultural-group.md
+3 -3
View File
@@ -1,7 +1,7 @@
---
title: "" # Display name (e.g., "Van Maanen's Star Culture")
description: "" # One-line summary for context filtering (e.g., "Industrial frontier culture valuing self-reliance and practical skills")
slug: "" # URL-safe identifier (e.g., "van-maanens-star-system")
title: "" # Display name (e.g., "Vuurkloof Culture")
description: "" # One-line summary for context filtering (e.g., "Geothermal frontier culture valuing engineering precision and thermal pragmatism")
slug: "" # URL-safe identifier (e.g., "vuurkloof")
category: cultural-group
status: proposed # proposed | draft | canonical
created: YYYY-MM-DD
wiki/_templates/district.md
+2 -2
View File
@@ -1,6 +1,6 @@
---
title: "" # Display name (e.g., "Sova Transit District")
description: "" # One-line summary for context filtering (e.g., "Main logistics hub of Station Sova, 12 social sites, high NPC density")
title: "" # Display name (e.g., "Dockside Commercial Quarter")
description: "" # One-line summary for context filtering (e.g., "Mixed-use commercial district adjacent to freight terminal, 8 social sites")
slug: "" # URL-safe identifier (e.g., "transit")
category: district
status: proposed # proposed | draft | canonical
wiki/_templates/faction.md
+1 -1
View File
@@ -38,7 +38,7 @@ cross_refs: []
---
## Members (v0.1)
## Members
{Table or list of known members with roles and links.}
wiki/_templates/institution.md
+3 -3
View File
@@ -1,5 +1,5 @@
---
title: "" # Display name (e.g., "Van Maanen's Star Administrator's Office")
title: "" # Display name (e.g., "Lattice Commission — Regional Liaison Office")
description: "" # One-line summary for context filtering (e.g., "Local government office overseeing system-level administration and permits")
slug: "" # URL-safe identifier
category: institution
@@ -36,9 +36,9 @@ cross_refs: []
---
## Presence in v0.1
## Local Presence
{How this institution manifests in the Sova Transit District. NPCs, locations, systems.}
{How this institution manifests at the local level. NPCs, locations, systems.}
---
wiki/_templates/star-system.md
+3 -3
View File
@@ -1,7 +1,7 @@
---
title: "" # Display name (e.g., "Van Maanen's Star")
description: "" # One-line summary for context filtering (e.g., "Industrial frontier system, home to Station Sova, first playable location")
slug: "" # URL-safe identifier (e.g., "van-maanens-star")
title: "" # Display name (e.g., "Vuurkloof")
description: "" # One-line summary for context filtering (e.g., "Geothermal frontier system, through-route topology, south_reach corridor")
slug: "" # URL-safe identifier (e.g., "vuurkloof")
category: star-system
status: proposed # proposed | draft | canonical
created: YYYY-MM-DD
wiki/_templates/station.md
+2 -2
View File
@@ -1,6 +1,6 @@
---
title: "" # Display name (e.g., "Station Sova")
description: "" # One-line summary for context filtering (e.g., "Primary logistics station in Van Maanen's Star, 3 districts, mixed-use")
title: "" # Display name (e.g., "Vuurkloof Horizon")
description: "" # One-line summary for context filtering (e.g., "Primary transit station in Vuurkloof, 2 districts, horizon-adjacent")
slug: "" # URL-safe identifier (e.g., "sova")
category: station
status: proposed # proposed | draft | canonical
wiki/authoring/base-text-authoring-guide.md
+2 -4
View File
@@ -101,7 +101,7 @@ If you're unsure whether a line is Factual: if it contains a number, a named qua
Base text must not contain culture-specific vocabulary. The culture injectors add that layer at voicing time. Base text is the semantic skeleton.
**What to avoid:**
- Van Maanen's Star oath vocabulary: `"void take it"`, `"blood and void"` — these go in voice_examples, not base text
- Culture-specific oath vocabulary: e.g. `"void take it"`, `"blood and void"` — these go in voice_examples, not base text
- Culture-specific greetings or farewells
- Slang that implies a particular register
@@ -129,9 +129,7 @@ Before committing, run through:
---
## Examples from the Van Maanen's Star zones (reference)
These lines passed elevation review (Sprint 26):
## Examples of elevated base text (Sprint 26 elevation review)
**Strong — moment-specific, role-grounded:**
- `"kneels at the base of a struggling plant and parts the soil with two fingers"`
wiki/authoring/cultural-generation-guide.md
+27 -44
View File
@@ -10,7 +10,7 @@
This guide provides the framework for generating culturally consistent content in The Settled Reach. Every named district, NPC, and piece of authored dialogue reflects a specific cultural context. This guide codifies how to derive that context from first principles so that any content author — writing a dockworker or a station administrator, a bar greeting or a confrontation line — can produce work that feels like it belongs.
The Sova Transit District in Van Maanen's Star is the first concrete instance of this framework. All examples in this guide are drawn from Sova. Subsequent settings use the same framework applied to different parameters.
The worked examples in this guide use a mid-Reach freight district as the reference context. Subsequent settings use the same framework applied to different parameters.
---
@@ -31,7 +31,7 @@ This determines the age of institutions, the density of infrastructure, and the
| **Frontier** | Sparse, improvised | Light. Syndic representatives, occasional Commission audit | Independent-to-resistant. Authority is a distant abstraction. | Improvised. Tight-knit. Self-reliant. |
| **Deep Frontier** | Minimal | Nominal or none | Sovereign. Authority is whatever the community enforces. | Harsh. Communal. Rules of necessity. |
**Sova Transit District:** Mid-Reach. Commission presence is intermittent — enough to maintain order, not enough to catch everything. The district's residents are pragmatic about authority: they comply when observed, continue as normal when not.
**Mid-Reach freight district:** Mid-Reach. Commission presence is intermittent — enough to maintain order, not enough to catch everything. The district's residents are pragmatic about authority: they comply when observed, continue as normal when not.
---
@@ -49,7 +49,7 @@ Economic base determines daily rhythms, vocabulary, and the social pressures tha
| **Service** | Tourist/commercial traffic. | Tips, regulars, reputation management. | Income dependent on traffic volume. Reputation fragile. | Blackmail. Theft. Information sale. |
| **Research** | Project deadlines. Funding cycles. | Research progress, institutional politics, publication credit. | Competitive, status-driven, secrecy around results. | Data theft. Fabrication. Factions. |
**Sova Transit District:** Freight primary. The span gate transit schedule structures everything. NPC routines, the ring's operational calendar, and social patterns (when the bar fills, when corridors are quiet) all derive from freight rhythm.
**Mid-Reach freight district:** Freight primary. The span gate transit schedule structures everything. NPC routines, the ring's operational calendar, and social patterns (when the bar fills, when corridors are quiet) all derive from freight rhythm.
---
@@ -66,7 +66,7 @@ Settlement age determines architectural character, generational memory, and whet
| **Mature** | Mixed construction eras clearly visible. Original structure heavily modified. Strong local character in older sections. | Distinct local identity. People think of themselves as "from here." | Distant. The origin is history, not memory. | Local pride. Skepticism of core-system assumptions. |
| **Old** | Accretive. Original construction may be invisible under layers. Idiosyncratic. | Deeply rooted identity. History is ambient. | Institutional. Stories are embedded in place-names and customs. | The origin system is foreign. "We are our own thing." |
**Sova Transit District:** Established-to-Mature. The district is ~40 years old on a station settled ~180 years ago. The district itself shows layered construction — prefab base, retrofitted sections, personalized details. Local identity is present but not deep. Workers think of themselves as Sova people, not Van Maanen's Star people; but they don't have the rootedness of a settlement in its third or fourth generation.
**Mid-Reach freight district:** Established-to-Mature. The district is ~40 years old on a station settled ~180 years ago. The district itself shows layered construction — prefab base, retrofitted sections, personalized details. Local identity is present but not deep. Workers think of themselves as Sova people, not Vuurkloof people; but they don't have the rootedness of a settlement in its third or fourth generation.
---
@@ -80,7 +80,7 @@ This determines:
- **Relationship to technology** — whether lattice use is stigmatized, normalized, or a source of pride
- **Attitudes toward the Commission** — reverence, compliance, resentment, or active evasion
**Van Maanen's Star Cultural Profile (established, working-class mid-Reach):**
**Vuurkloof Cultural Profile (established, working-class mid-Reach):**
- **Names:** Compact, consonant-heavy, first-name-primary in social contexts. Family names exist but are used formally (official documents, institutional contexts, introductions to strangers). Nicknames common among colleagues. Off-system names (longer vowels, different consonant clusters) stand out subtly but aren't cause for suspicion — just quietly noted.
@@ -112,7 +112,7 @@ Every location has a set of institutions that structure daily life. Understandin
| **Station Administration** | Local governance | Immediate authority. Maintenance schedules, district regulations, housing allocation. |
| **Medical Services** | Re-embodiment and healthcare | Presence varies by wealth. Clinics in working districts, full services in affluent ones. |
**Sova Transit District institutional profile:**
**Mid-Reach freight district institutional profile:**
- Syndic logistics consortium: the main employer, highly visible in daily operations
- Station Administration: present through maintenance schedules, posted notices, the occasional administrator in the corridors
- Lattice Commission: intermittent. A kiosk in the logistics hub lobby, field investigators who visit quarterly (usually)
@@ -125,16 +125,16 @@ Every location has a set of institutions that structure daily life. Understandin
### 2.1 Naming Conventions
Naming conventions follow from Dimension 4 (Cultural Reference Point). The table below captures Van Maanen's Star standard, which serves as the v0.1 model.
Naming conventions follow from Dimension 4 (Cultural Reference Point). The table below captures Vuurkloof standard as the canonical worked example.
**Van Maanen's Star naming rules:**
- **First names:** 1-2 syllables, consonant-forward, no double vowels in typical form. Examples: Kael, Voss, Drin, Lera, Torek, Maret, Naia, Sera, Nils, Kosse, Pael, Tev, Ren, Resha, Harek, Sess, Devra.
- **Family names:** 1-2 syllables, similar phoneme pattern. Examples: Davan, Lintar, Sessik, Korr.
- **Social usage:** First name in most contexts. "Supervisor Voss" for institutional address. Full name only in formal or hostile contexts.
- **Nicknaming:** Common among colleagues. A name like "Renn" might be short for something nobody uses.
- **Off-system names:** Slightly softer vowels, longer syllable count, different consonant clusters. Example: Olin, Sabel. These stand out quietly — the detective's lattice may flag them as non-Van Maanen's Star-origin before the detective consciously registers why.
**Vuurkloof naming rules:**
- **First names:** 1-2 syllables, consonant-forward, no double vowels in typical form. Pattern examples: Brek, Solt, Drav, Vesk, Tren, Morva. *Author naming examples against the active district roster — don't re-use existing NPC names.*
- **Family names:** 1-2 syllables, similar phoneme pattern. Pattern examples: Valen, Kost, Terst, Morek.
- **Social usage:** First name in most contexts. "Supervisor {Surname}" for institutional address. Full name only in formal or hostile contexts.
- **Nicknaming:** Common among colleagues. A short form might be all anyone uses.
- **Off-system names:** Slightly softer vowels, longer syllable count, different consonant clusters. Examples: Olin, Renhai. These stand out quietly — the player character's lattice may flag them as non-local-origin before consciously registering why.
**IP check:** Van Maanen's Star names are constructed to feel plausibly human-future without mapping to any existing franchise. They are NOT Hamilton Commonwealth names (conspicuously contemporary English, which is Hamilton's signature device). They are NOT Banks Culture names (often whimsical or elaborate). They are NOT Firefly or Star Wars (no Earth-ethnic-name echoes). They suggest cultural drift across 180 years of mid-Reach settlement.
**IP check:** Vuurkloof names are constructed to feel plausibly human-future without mapping to any existing franchise. They are NOT Hamilton Commonwealth names (conspicuously contemporary English, which is Hamilton's signature device). They are NOT Banks Culture names (often whimsical or elaborate). They are NOT Firefly or Star Wars (no Earth-ethnic-name echoes). They suggest cultural drift across 180 years of mid-Reach settlement.
---
@@ -142,16 +142,16 @@ Naming conventions follow from Dimension 4 (Cultural Reference Point). The table
Economic base (Dimension 2) determines the vocabulary of daily life. Workers in a freight hub speak differently from workers in a mining operation or a research station. This vocabulary should permeate every NPC's dialogue — not as jargon dumps, but as the ambient language of their daily reality.
**Sova Transit District — Freight Economic Vocabulary:**
**Mid-Reach freight district — Economic Vocabulary:**
See companion document: **Sova Texture Appendix (#302)** for the full slang glossary.
See companion document: **Freight District Texture Appendix** for the full slang glossary.
Core vocabulary patterns for freight:
- Work = "shift" (not "rotation," not "duty," not "tour")
- The gate = "the gate" casually, "the span gate terminal" institutionally — never "the span gate" in casual speech
- Cargo containers = "containers" or "cans" (informal) — never "pods"
- Cargo manifests = "manifests" (precise), "paperwork" (dismissive), "the file" (when being evasive)
- Credits = "marks" in casual conversation (a Van Maanen's Star local usage)
- Credits = "marks" in casual conversation (a Vuurkloof local usage)
- Off-shift time = "off-book" among the ring; just "after" for civilians ("see you after")
- Lattice communication = "pinging" (sending), "a ping" (notification)
@@ -161,7 +161,7 @@ Core vocabulary patterns for freight:
The freight rhythm (span gate schedules, shift rotations) structures social life. Content authors should use these rhythms as temporal anchors for dialogue and monologue.
**Sova Transit social rhythm:**
**Mid-Reach freight district social rhythm:**
| Time | Activity | Social Atmosphere |
|---|---|---|
@@ -170,7 +170,7 @@ The freight rhythm (span gate schedules, shift rotations) structures social life
| 1200-1400 | Midday break | Break room social time, bar has light lunch trade |
| 1400-1600 | Afternoon freight cycle | Quieter, post-lunch pace |
| 1600-1800 | Evening shift change | Second major transition, people heading to or from |
| 1800-2200 | Peak bar hours | The Last Shift fills up. Main social time of the day. |
| 1800-2200 | Peak bar hours | The bar fills up. Main social time of the day. |
| 2200-0200 | Late night | Bar quiet (late regulars only). Corridors quieter. Ring operations typical timing. |
| 0200-0600 | Deep night | Minimal staffing. Maintenance windows. Skeleton shift. |
@@ -180,7 +180,7 @@ The freight rhythm (span gate schedules, shift rotations) structures social life
Dimension 3 (Reach Position) determines how NPCs speak about, around, and to authority figures. This affects dialogue at every trust tier.
**Sova Transit — Authority Relationship Patterns:**
**Mid-Reach freight district — Authority Relationship Patterns:**
| NPC Type | To Commission directly | About Commission (behind back) | To institutional-tagged stranger |
|---|---|---|---|
@@ -207,9 +207,9 @@ The exception: NPCs under stress or in unusual circumstances may reference their
---
## Part 3: Scaling Beyond v0.1
## Part 3: Scaling to New Districts
Van Maanen's Star instance demonstrates the framework. Future settings apply the same five dimensions with different parameters. The cultural output — naming conventions, vocabulary, social norms, authority attitudes — follows from the parameters, not from free-form invention.
The mid-Reach freight district example demonstrates the framework. Other settings apply the same five dimensions with different parameters. The cultural output — naming conventions, vocabulary, social norms, authority attitudes — follows from the parameters, not from free-form invention.
**Quick-generation checklist for a new district:**
@@ -260,34 +260,17 @@ The same cultural detail should mean something different to the smuggler and the
---
## Appendix: v0.1 Named Characters — Van Maanen's Star Consistency Check
## Appendix: Naming Convention Validation
All named characters in the Sova Transit District, with naming convention validation:
When authoring new characters for a district, validate each name against the district's cultural profile before committing. The validation table format (per district):
| Name | Convention Check | Role | Notes |
|---|---|---|---|
| Kael Davan | Van Maanen's Star standard | Dock worker, ring member, smuggler's FRIEND | Full name used in formal contexts |
| Sera Venn | Van Maanen's Star standard | Commission field tech, detective's FRIEND | "Venn" slightly softer than typical Van Maanen's Star surname — deliberate: she's institutional, slightly apart |
| Lera Sessik | Van Maanen's Star standard | Bar owner, The Last Shift | "Lera's" informal name. Never Lera Sessik to regulars. |
| Torek Lintar | Van Maanen's Star standard | Dock inspector, compromised | Full name used when the detective runs his file |
| Voss | Van Maanen's Star standard | Logistics supervisor | Single name in social use. Probably Voss-something officially. |
| Drin | Van Maanen's Star standard | Maintenance tech, flat NPC | Single name. Been here long enough nobody uses a surname. |
| Maret Korr | Van Maanen's Star standard | Freight scheduler, ring-adjacent | "Korr" is direct Van Maanen's Star standard |
| Naia | Van Maanen's Star standard | Kael's partner (mentioned, not primary) | Brief, soft — contrast to Kael |
| Nils | Van Maanen's Star standard | Bar regular (mentioned) | |
| Kosse | Van Maanen's Star standard | Station name / character reference | |
| Pael | Van Maanen's Star standard | Maintenance tech, flat NPC (Sprint 12: #307) | |
| Tev | Van Maanen's Star standard | Lookout/runner, flat NPC (Sprint 12: #307) | |
| Ren | Van Maanen's Star standard | Drifter, flat NPC (Sprint 12: #307) | "Ren" is earlier-established; "Renn" is the courier variant from Round 2 mapping |
| {Name} | {culture} standard / deviation | {role} | {why the deviation if any} |
**Off-system characters (deliberate naming deviation):**
**IP check:** Validate new names against: Hamilton (Contemporary English register), Banks (whimsical/elaborate), Reynolds (Dutch/Germanic), Simmons (Greek/Latin register), Morgan (Anglo-American register). Flag any cluster that maps too directly to an existing franchise voice.
| Name | Deviation | Role | Purpose of Deviation |
|---|---|---|---|
| Resha | Softer vowel pattern | New hire | Implies off-system origin — explains why they ask too many questions |
| Sabel | Different phoneme cluster | Ring fence/buyer, external contact | External contact should sound external |
**IP check:** All Van Maanen's Star names validated against Hamilton (Contemporary English — cleared), Banks (whimsical/elaborate — cleared), Reynolds (Dutch/Germanic — cleared), Simmons (Greek/Latin register — cleared), Morgan (Anglo-American register — cleared). No franchise overlap found.
*v0.1 named-character validation table removed — cited NPCs no longer in v0.2 pipeline (D-122). Generate new per-district validation tables when the active NPC roster is authored.*
---
wiki/authoring/culture-authoring-guide.md
+16 -16
View File
@@ -13,7 +13,7 @@ Every NPC in The Settled Reach is voiced through their culture. The voice pipeli
This guide explains how to author a new culture RON file from scratch. The target: one experienced author can produce a complete, Spike-validated culture profile in approximately one working day.
Three reference cultures exist in `content/global/`:
- `culture-van-maanens-star.ron` — Mid-Reach, freight, working-class pragmatic (the Spike 1/2 reference)
- `culture-van-maanens-star.ron` — Mid-Reach, freight, working-class pragmatic (canonical reference culture)
- `culture-vael.ron` — Core-adjacent, administrative/research, institutional-formal
- `culture-osse.ron` — Deep Frontier, extraction industry, terse-utilitarian
@@ -55,7 +55,7 @@ Write a one-sentence register description. This becomes `speech.register` in the
**Examples:**
| Culture | Register |
|---|---|
| Van Maanen's Star | direct, minimal pleasantries, gets to the point |
| Vuurkloof | direct, minimal pleasantries, gets to the point |
| Vael | complete sentences, institutional framing, measured, precise |
| Osse | terse, functional, equipment vocabulary, economy of language |
@@ -127,7 +127,7 @@ The not-list prevents register leakage. Write it by asking: what does this cultu
| Culture | NEVER block content |
|---|---|
| Van Maanen's Star | Corporate/institutional language, effusive or polished register, deference to unearned rank, family names in casual use, verbosity |
| Vuurkloof | Corporate/institutional language, effusive or polished register, deference to unearned rank, family names in casual use, verbosity |
| Vael | Void-adjacent exclamations (frontier register), casual contractions, sentence fragments, direct emotional expression, physical labor as value ground |
| Osse | Institutional framing or courtesy protocols, formal complete sentences, Commission-world vocabulary, Core-system exclamations, elaboration where a number suffices |
@@ -147,7 +147,7 @@ Each numbered instruction should target a DIFFERENT speech dimension so trait mo
- Instruction 7 → trust signal (how the culture verifies credibility)
- Instruction 8 → not-list (what this voice never does)
**Test before committing:** Read the persona out loud. Can you imagine an NPC responding to you from this profile? Would a speaker from this culture be clearly distinct from Van Maanen's Star if you heard both without labels?
**Test before committing:** Read the persona out loud. Can you imagine an NPC responding to you from this profile? Would a speaker from this culture be clearly distinct from Vuurkloof if you heard both without labels?
---
@@ -163,19 +163,19 @@ Example pairs are the model's pattern anchors — small LLMs are pattern matcher
**Rules for example pairs:**
1. Cover the range: neutral, positive relationship, refusal/deflection, high-affect
2. Output should be short (1-2 sentences). Long outputs lose the pattern.
3. Each output must be recognizably THIS culture — read them side by side with Van Maanen's Star examples. They should sound like different people.
3. Each output must be recognizably THIS culture — read them side by side with Vuurkloof examples. They should sound like different people.
4. Do not use real NPC names in examples — use generic role references
### Cross-cultural contrast test
Before finalizing examples, run this test. Take the same three base-text inputs and write outputs in Van Maanen's Star, Vael, and Osse voices. If the outputs are hard to distinguish, the culture persona needs sharpening.
Before finalizing examples, run this test. Take the same three base-text inputs and write outputs in Vuurkloof, Vael, and Osse voices. If the outputs are hard to distinguish, the culture persona needs sharpening.
**Example inputs for the test:**
- "declines to answer a question about an overnight run"
- "acknowledges a colleague's greeting while continuing to work"
- "thanks a colleague for covering a shift"
| Input | Van Maanen's Star | Vael | Osse |
| Input | Vuurkloof | Vael | Osse |
|---|---|---|---|
| Declines question | "Look, that's not mine to say." | "I'm not in a position to speak to that. You'd want to refer to the relevant operations log." | "Not my section. Ask Grek." |
| Acknowledges greeting | "Hey. Yeah. Catch you at shift end." | "Harthen. Good. I'll be with you in a moment." | "Doss. Yeah." |
@@ -197,7 +197,7 @@ If all three rows sound similar, the culture personas need work.
- `suppress_on_tells` — tells that should suppress this injection (e.g., oath suppressed when Guarded)
**Frequency guidelines:**
- 0.25 — Van Maanen's Star oath vocabulary (appears in ~1 in 4 high-affect contexts)
- 0.25 — Vuurkloof oath vocabulary (appears in ~1 in 4 high-affect contexts)
- 0.20 — Vael protocol citation (appears occasionally in procedural exchange)
- 0.15 — Osse equipment ground (appears in work-adjacent contexts)
@@ -242,14 +242,14 @@ After validation, the culture profile is ready for Spike 1 prompt testing. Human
## Tell-tone reference tables
### Van Maanen's Star tell-tone table
### Vuurkloof tell-tone table
| TellCategory | Van Maanen's Star-inflected tonal register |
| TellCategory | Vuurkloof-inflected tonal register |
|---|---|
| Nervous | Answers run shorter than usual. Eyes stay on task. Nothing's wrong — just things to do. |
| Guarded | Direct past the point of directness. Closes conversation paths fast without being unfriendly. |
| Friendly | One beat more than the exchange needed. A word of warmth lands casually, not performed. |
| Angry | Steady. Even. The kind of steady that takes effort. Not hostile — just flat in a way that doesn't feel natural for Van Maanen's Star. |
| Angry | Steady. Even. The kind of steady that takes effort. Not hostile — just flat in a way that doesn't feel natural for Vuurkloof. |
| RoutineDeviation | Unhurried. Unremarkably normal. Like nothing's worth noticing. |
### Vael tell-tone table
@@ -283,7 +283,7 @@ After validation, the culture profile is ready for Spike 1 prompt testing. Human
- [ ] Voice persona: 8 numbered instructions, ~200-250 tokens
- [ ] Explicit `NEVER:` block at end of persona string (separate from numbered instructions)
- [ ] NEVER block content is culture-specific (not repeating universal constraints)
- [ ] Cross-cultural contrast test passed (Van Maanen's Star/Vael/Osse comparison)
- [ ] Cross-cultural contrast test passed (Vuurkloof/Vael/Osse comparison)
- [ ] 3-5 voice examples authored, range covered
- [ ] At least 1 occasional injection with suppression logic
- [ ] Tell-tone table authored (5 TellCategories)
@@ -307,7 +307,7 @@ BehaviorPrimitive.action + BehaviorModifier.clause → assembled behavior st
Example:
- Action: `"moves freight containers"`
- Modifier: `"without wasted motion"` (Van Maanen's Star, `work_pace`)
- Modifier: `"without wasted motion"` (Vuurkloof, `work_pace`)
- Result: `"moves freight containers without wasted motion"`
A culture provides a pool of modifier clauses. When the engine assembles a behavior, it looks for a modifier whose `category` matches the primitive's `modifier_hint` string. If no match exists, it falls back to any modifier in the pool. If no modifiers exist at all, the action text is used as-is.
@@ -336,7 +336,7 @@ Every `BehaviorPrimitive` carries a `context` field that gates when it is eligib
These seven categories define the interface between primitives (Mellanie, role-action templates) and modifiers (culture authors). A primitive's `modifier_hint` must use one of these strings for a culture modifier to match it.
| Category | What it inflects | Example modifier (Van Maanen's Star) |
| Category | What it inflects | Example modifier (Vuurkloof) |
|---|---|---|
| `work_pace` | Speed and intensity of physical task execution | "without wasted motion" |
| `physical_manner` | Body language and movement quality during tasks | "without looking up from the task" |
@@ -361,7 +361,7 @@ These seven categories define the interface between primitives (Mellanie, role-a
**Three-culture contrast for modifiers** (same as voice persona contrast test):
| Category | Van Maanen's Star | Vael | Osse |
| Category | Vuurkloof | Vael | Osse |
|---|---|---|---|
| work_pace | "without wasted motion" | "with practiced deliberation" | "at extraction pace" |
| physical_manner | "without ceremony" | "with institutional correctness" | "tool already in hand" |
@@ -379,7 +379,7 @@ Add these items to the culture profile checklist:
- [ ] `behavior_modifiers` array populated with at least 2 clauses per category (14 minimum)
- [ ] Each clause tested: grammatically trails "moves freight containers ___" and "checks a manifest ___"
- [ ] Three-culture contrast check: modifiers are clearly distinct from Van Maanen's Star, Vael, and Osse
- [ ] Three-culture contrast check: modifiers are clearly distinct from Vuurkloof, Vael, and Osse
- [ ] `tooling/validate-ron` still passes after adding modifiers
*Addendum: Sprint 26, #634 (composable behavior content). Category vocabulary established jointly by Gestalt (culture modifiers) and Mellanie (behavior primitives). Add new categories only by agreement between both sides — unmatched categories silently fall back to any modifier.*
wiki/authoring/dual-lens-authoring-guide.md
+140 -196
View File
@@ -1,6 +1,6 @@
# Dual Lens Authoring Guide
**v0.1 Content Design Document** | Blocks: 11 downstream tickets | Status: Draft
**Content Design Document** | Blocks: 11 downstream tickets | Status: Draft
**Author:** Mellanie (Copywriter) + Paula (Narrative & Political Depth)
**Date:** 2026-02-12
@@ -23,58 +23,37 @@ This guide defines how content authors write for two playable characters experie
### Who Is The Smuggler?
**Occupation:** Logistics worker, Sova Transit District Freight Terminal ("The Terminal")
**Ring Position:** Mid-level operator. Handles physical cargo routing, knows the schedule windows, manages dock-side coordination.
**Time in Ring:** ~2 years. Comfortable with the work. Good at it.
**Lattice Tier:** Baseline (standard civilian-grade, no augmentation)
*v0.1 starting-state profile removed — cited named NPCs no longer in v0.2 pipeline (D-122). Author per-district character profiles against the active NPC roster.*
**What They Know At Session Start:**
- The ring exists. Who's in it: Nils (coordinator), Kael (closest colleague, ring member), Voss (shift supervisor, takes a cut), Renn (courier), and 2-3 others.
- The routes: freight bay → service corridor → temp storage → bar back room.
- The cargo: unlicensed lattice components, medical-grade neural replacements diverted from Syndic supply chains. They don't look too closely at the sealed containers.
- The schedule: shift transitions create 20-minute oversight gaps. The operation runs during these windows.
- The stakes: if caught, it's a Commission offense. Years in detention. But the money helps, the team is solid, and it's felt manageable for two years.
**Structural starting state (archetype constants):**
**What They Don't Know:**
- The detective is investigating (unless playing detective path and the smuggler has been flagged).
- Kael is trying to exit the ring. Meeting unknown contacts. Lying to the smuggler.
- Sera (Commission field tech) has flagged manifest discrepancies and is sitting on unreported evidence.
- The full upstream supply chain (knows cargo comes from off-station contact Sabel, doesn't know Syndic connections).
- How much Naia (Kael's partner) suspects. How much danger the ring is actually in.
**Occupation:** Logistics worker at the district freight terminal.
**Ring Position:** Mid-level operator. Handles physical cargo routing, knows schedule windows.
**Lattice Tier:** Baseline (civilian-grade, no augmentation)
**Emotional Baseline:**
- **Comfortable-tense.** Not happy, not miserable. The smuggler is managing a life with two faces: legitimate dock worker (public) and ring operator (hidden). The cognitive load is constant but bearable. The money eases the financial pressure that makes station life tight for most workers. The team feels like family — shared risk creates trust.
- **Loyal to people, not institutions.** First-name basis with everyone. Thinks relationally: Kael is "my shift partner," not "dock worker Davan." Voss is "tense today," not "the shift supervisor is agitated." Institutions (Commission, Concord, Syndic) are distant, abstract, often adversarial.
- **Operational thinking mode.** Time-aware, route-aware, schedule-aware. Worries about exposure: "Is Torek's spending too visible?" "Did Maret notice that manifest discrepancy?" "Is the detective going to connect Kael to the irregularities?"
- **Protectiveness over the team.** Would cover for Kael even at personal cost. Would warn Voss if something looked wrong. The ring isn't just work — it's the people the smuggler eats lunch with, drinks with, trusts.
**Emotional Baseline (invariant):**
- **Comfortable-tense.** Managing a life with two faces: legitimate worker (public) and ring operator (hidden). The cognitive load is constant but bearable. The team feels like family — shared risk creates trust.
- **Loyal to people, not institutions.** Thinks relationally, not institutionally. Institutions (Commission, Concord, Syndic) are distant, abstract, often adversarial.
- **Operational thinking mode.** Time-aware, route-aware, schedule-aware. Worries about exposure and protecting the team.
- **Protectiveness over the team.** Would cover for THE FRIEND even at personal cost.
---
### Who Is The Detective?
**Occupation:** Commission investigator, assigned to Sova Transit District for manifest irregularity investigation
**Assignment Duration:** New arrival. Session start is early in the investigation (first week).
**Lattice Tier:** Standard professional (Commission-grade diagnostic tools, analytical overlays, not investigative-tier augmentation)
*v0.1 starting-state profile removed — cited named NPCs no longer in v0.2 pipeline (D-122). Author per-district character profiles against the active NPC roster.*
**What They Know At Session Start:**
- There are manifest discrepancies tied to Sova Transit District freight operations. Containers logged but not reconciled with incoming manifests. Pattern suggests smuggling.
- Names from case files: Voss (shift supervisor), Maret (freight scheduler), Drin (dock inspector). Persons of interest, not confirmed suspects.
- Sova Transit District social geography: The Terminal (logistics hub), The Last Shift (bar, social nexus), maintenance corridors (off-books access routes).
- Institutional context: The previous Commission liaison rotated out 3 months ago. Current Commission presence is minimal (Sera Venn, field tech, not an investigator).
- Sera Venn is a pre-existing contact. Same institutional background, transferred to Sova a year ago. Reliable. The detective's one friendly face in the district.
**Structural starting state (archetype constants):**
**What They Don't Know:**
- Who the ring members are (Nils, Kael, Renn, etc. — names without context).
- The smuggler's identity. If the smuggler is in the ring, the detective doesn't know yet.
- Kael is trying to exit the ring. Sera is sitting on unreported evidence. Naia is worried about Kael and has confided in Sera.
- The social web connecting everyone. Who's loyal to whom. Who's protecting whom. Who's compromised and how.
- How embedded the ring is in the district's economic immune system. The detective reads it as criminal enterprise. Doesn't yet understand it as community survival mechanism.
**Occupation:** Commission investigator, assigned to the district for manifest irregularity investigation.
**Assignment Duration:** New arrival. Session start is early in the investigation.
**Lattice Tier:** Standard professional (Commission-grade diagnostic tools, analytical overlays)
**Emotional Baseline:**
- **Professional-cautious.** The detective is trained to observe, analyze, withhold judgment until evidence accumulates. But they're also human — isolation in an unfamiliar community, reliance on Sera for social grounding, awareness that non-cooperation is the district default.
- **Analytical habit.** Counts things. Tracks frequencies. Flags inconsistencies. Self-directs: "filing it," "noted," "coincidence?" Internal bookkeeping runs in background. The institutional training doesn't turn off.
- **Institutional frame.** Thinks in terms of evidence, patterns, leverage. Surnames before first names for targets. "Davan, K." not "Kael." The shift from surname to first-name IS a relationship marker.
- **Moral position.** The detective believes in the work. Smuggling isn't victimless — unlicensed lattice components can cause neural degradation, medical-grade replacements diverted from Syndic supply chains mean someone else doesn't get the replacement they need. The ring is breaking the law. The investigation is justified. But the detective is also starting to see the grey: Kael isn't a cartel boss, he's a dock worker who said yes once and kept saying yes. Complexity accumulates.
**Emotional Baseline (invariant):**
- **Professional-cautious.** Trained to observe, analyze, withhold judgment until evidence accumulates. Isolation in an unfamiliar community. Non-cooperation is the district default.
- **Analytical habit.** Counts things. Tracks frequencies. Flags inconsistencies. Self-directs: "filing it," "noted," "coincidence?" Internal bookkeeping runs in background.
- **Institutional frame.** Thinks in terms of evidence, patterns, leverage. Surnames before first names for targets. The shift from surname to first-name IS a relationship marker.
- **Moral position.** Believes in the work. Smuggling isn't victimless. But the grey accumulates: ring members aren't cartel bosses, they're workers who said yes once and kept saying yes.
---
@@ -84,7 +63,7 @@ This guide defines how content authors write for two playable characters experie
|-----------|----------|-----------|
| **Knowledge of the ring** | Insider. Knows who, what, when, where. Operational detail. | Suspects. Has data anomalies, no confirmed names. Investigative frame. |
| **Relationship to NPCs** | Personal. First-name basis. History, trust, loyalty. | Clinical. Surname-first. Categorizes by role and behavior. |
| **Emotional orientation** | Protective. Worries about people. "Is Kael okay?" | Analytical. Worries about patterns. "Why is Kael nervous?" |
| **Emotional orientation** | Protective. Worries about people. "Is {FRIEND} okay?" | Analytical. Worries about patterns. "Why is {subject} nervous?" |
| **Lattice capability** | Baseline. No enhanced perception, no analytical overlays. | Professional. Diagnostic access, pattern recognition tools. |
| **Social position** | Insider. Belongs. Everyone knows the smuggler. | Outsider. Institutional authority resented by the community. |
| **Moral framing** | Pragmatic complicity. "We're careful. We take care of our own." | Institutional clarity. "This is a crime. There are victims." |
@@ -117,7 +96,7 @@ The smuggler hears a line the detective doesn't (or vice versa) because of `acce
```yaml
- id: terminal_d_044
role: dock_worker
text: "Container 4471 sat in temp storage overnight. Scheduling backed up again."
text: "Container {N} sat in temp storage overnight. Scheduling backed up again."
access: [public, peer]
trust: surface
situation: [shift_start]
@@ -131,12 +110,12 @@ Both characters can hear this line (`public` + `peer` both accessible). But the
```yaml
- id: terminal_d_045
role: dock_worker
text: "4471's routed for transfer at 14:30. Voss kept the window clear."
text: "{Container N} is routed for transfer at 14:30. {Supervisor} kept the window clear."
access: [insider]
trust: real
situation: [shift_transition]
dual_lens:
smuggler: "Confirmation — the route is active, Voss is cooperating."
smuggler: "Confirmation — the route is active, the supervisor is cooperating."
detective: "Never hears this line. Doesn't have insider access."
```
@@ -147,7 +126,7 @@ Both characters hear the same NPC dialogue, but their monologue reactions interp
```yaml
- id: bar_d_033
role: bartender
text: "Sera left early. Headache, she said."
text: "{THE FRIEND} left early. Headache, they said."
access: [public]
trust: surface
```
@@ -157,7 +136,7 @@ Both characters hear the same NPC dialogue, but their monologue reactions interp
- id: bar_m_051
character: smuggler
trigger: post_conversation
text: "Sera's gone. Good — one less Commission presence in the room."
text: "{THE FRIEND}'s gone. Good — one less Commission presence in the room."
mood: [relieved]
```
@@ -168,10 +147,10 @@ Both characters hear the same NPC dialogue, but their monologue reactions interp
trigger: post_conversation
prerequisite:
known_attributes:
subject: sera_venn
subject: {friend_npc_slug}
key: behavior_flags
value_contains: avoidance_pattern
text: "Second time Sera's left when Torek arrived. Coincidence?"
text: "Second time {THE FRIEND} left when {NPC} arrived. Coincidence?"
mood: [suspicious]
```
@@ -180,7 +159,7 @@ Same dialogue. Smuggler reads it as relief (less oversight). Detective reads it
**Type 3: Emotional Weight Difference**
The relationship history creates different emotional stakes for the same observation.
*Observation trigger:* Kael checking his lattice for the third time in ten minutes.
*Observation trigger:* THE FRIEND checking their lattice for the third time in ten minutes.
*Smuggler monologue:*
```yaml
@@ -189,8 +168,8 @@ The relationship history creates different emotional stakes for the same observa
trigger: observe_anomaly
prerequisite:
relationship_state: Friendly
subject: kael_davan
text: "Kael keeps checking his lattice. Waiting for a message? Not like him to be jumpy."
subject: {friend_npc_slug}
text: "{THE FRIEND} keeps checking their lattice. Waiting for a message? Not like them to be jumpy."
mood: [concerned]
topic: [colleague]
```
@@ -202,13 +181,13 @@ The relationship history creates different emotional stakes for the same observa
trigger: observe_anomaly
prerequisite:
relationship_state: Known
subject: kael_davan
text: "Dock worker Davan — lattice activity spiked. Expecting a message? Or checking for surveillance?"
subject: {friend_npc_slug}
text: "Dock worker {Surname} — lattice activity spiked. Expecting a message? Or checking for surveillance?"
mood: [analytical]
topic: [investigation]
```
Same behavior. Smuggler worries about a friend ("Not like him"). Detective analyzes a subject ("Dock worker Davan"). Emotional weight is asymmetric.
Same behavior. Smuggler worries about a friend ("Not like them"). Detective analyzes a subject ("Dock worker {Surname}"). Emotional weight is asymmetric.
---
@@ -221,12 +200,12 @@ The dual-lens rule is enforced through the tag taxonomy (D-035). Here's how tags
| Access Tier | Who Gets It | Smuggler Example | Detective Example |
|-------------|-------------|------------------|-------------------|
| `public` | Everyone | Bar greeting, shift small talk | Commission procedural questions |
| `peer` | Known or Friendly relationship | Coworker gossip, shift complaints | Institutional background sharing (Sera to detective) |
| `peer` | Known or Friendly relationship | Coworker gossip, shift complaints | Institutional background sharing ({THE FRIEND} to detective) |
| `insider` | Friendly relationship only | Ring operational talk, close confidences | Never unlocked for ring NPCs (detective is outsider) |
| `authority` | Detective only, works at Unknown/Known/PersonOfInterest | Institutional leverage questions | Smuggler never has authority access |
| `hostile` | Hostile relationship only | Threats, final warnings | Post-cover-blown confrontation |
**Critical rule:** When Kael transitions from Friendly to PersonOfInterest (THE FRIEND contradiction), `insider` and `peer` lines LOCK OUT. The smuggler still sees Kael, still interacts with Kael, but the warm operational dialogue disappears. That absence IS the emotional payload.
**Critical rule:** When THE FRIEND transitions from Friendly to PersonOfInterest (THE FRIEND contradiction), `insider` and `peer` lines LOCK OUT. The smuggler still sees THE FRIEND, still interacts with them, but the warm operational dialogue disappears. That absence IS the emotional payload.
**`trust` Tag — Hard Filter (D-028 Layer 3)**
@@ -238,7 +217,7 @@ Within each access tier, `trust` further filters content:
| `real` | Honest opinions, unguarded speech, actual feelings |
| `secret` | Dangerous knowledge, confessions, things that create leverage |
A line tagged `access: [insider], trust: secret` is the deepest content — only available to the smuggler, only when Kael is Friendly, only when trust has been earned through repeated interaction.
A line tagged `access: [insider], trust: secret` is the deepest content — only available to the smuggler, only when THE FRIEND is Friendly, only when trust has been earned through repeated interaction.
**`character` Tag — Hard Partition (D-032)**
@@ -268,18 +247,20 @@ When writing a line:
### Per-NPC Access Mapping
*v0.1 named-NPC access table removed — cited NPCs no longer in v0.2 pipeline (D-122). Author per-district access mapping tables against the active NPC roster using the format below.*
How each character relates to key NPCs at session start:
| NPC | Smuggler Access | Detective Access | Shift Path (Smuggler) | Shift Path (Detective) |
|-----|----------------|------------------|---------------------|----------------------|
| **Kael Davan (THE FRIEND)** | `insider`, `peer` | `public` → `authority` (if flagged) | `insider` → locked out (post-contradiction, PersonOfInterest) | `public` → `authority` (investigation progresses) |
| **Sera Venn (THE FRIEND)** | `public` (Commission, wary) | `peer` → `authority` (post-contradiction) | No shift (smuggler doesn't develop relationship) | `peer` → `authority` (trust breaks, PersonOfInterest) |
| **Voss (shift supervisor)** | `insider` (colleague, knows smuggler is ring) | `authority` | `insider` → `hostile` (if cover blown) | `authority` → `peer` (if detective earns trust) |
| **Lera Sessik (bar owner)** | `insider` (bar regular, ring-aware) | `public` → `peer` (repeat visits) | No major shift | `public` → `peer` (regular status, 3-4 visits) |
| **Naia Tamm (Kael's partner)** | `peer` (through Kael) | `public` → `peer` (through Sera) | `peer` → `hostile` (if Naia learns truth about ring) | `public` → `peer` (Sera introduction) |
| **Torek Lintar (bar regular)** | `insider` or `peer` (depends on whether smuggler knows Torek's ring connection) | `public` | No shift | `public` → `authority` (if financial tells flagged) |
| **Maret Korr (freight scheduler)** | `insider` (hub colleague) | `authority` | No major shift | `authority` → `peer` (if Maret cooperates) |
| **Drin Rosta (dock inspector)** | `insider` (hub colleague, smuggler knows Drin is compromised) | `authority` | `insider` → `hostile` (if Drin turns informant) | `authority` (detective can pressure via gambling debt) |
| **{FRIEND A} (Smuggler's FRIEND)** | `insider`, `peer` | `public` → `authority` (if flagged) | `insider` → locked out (post-contradiction, PersonOfInterest) | `public` → `authority` (investigation progresses) |
| **{FRIEND B} (Detective's FRIEND)** | `public` (Commission, wary) | `peer` → `authority` (post-contradiction) | No shift (smuggler doesn't develop relationship) | `peer` → `authority` (trust breaks, PersonOfInterest) |
| **{Supervisor} (shift supervisor)** | `insider` (colleague, knows smuggler is ring) | `authority` | `insider` → `hostile` (if cover blown) | `authority` → `peer` (if detective earns trust) |
| **{Bar Owner}** | `insider` (bar regular, ring-aware) | `public` → `peer` (repeat visits) | No major shift | `public` → `peer` (regular status, 3-4 visits) |
| **{MIRROR} (FRIEND's partner)** | `peer` (through FRIEND) | `public` → `peer` (through FRIEND B) | `peer` → `hostile` (if MIRROR learns truth about ring) | `public` → `peer` (FRIEND B introduction) |
| **{Ring-adjacent NPC}** | `insider` or `peer` (depends on smuggler's knowledge of connection) | `public` | No shift | `public` → `authority` (if behavioral tells flagged) |
| **{Scheduler/Admin}** | `insider` (hub colleague) | `authority` | No major shift | `authority` → `peer` (if they cooperate) |
| **{Compromised NPC}** | `insider` (hub colleague, smuggler knows they're compromised) | `authority` | `insider` → `hostile` (if they turn informant) | `authority` (detective can apply pressure via known leverage) |
---
@@ -296,14 +277,14 @@ How each character relates to key NPCs at session start:
| Character | Starting Tier | Likely Shift | Trigger | Content Requirement |
|-----------|--------------|--------------|---------|---------------------|
| Smuggler | `insider` (regular) | `insider` → `hostile` | Social contamination from hub (ring turns on smuggler) | Bar dialogue shifts from warm to cold. Lera stops saving the smuggler's seat. Torek stops buying rounds. |
| Detective | `public` | `public` → `peer` | Repeated visits (3-4), becomes a regular, earns Lera's respect | Greeting dialogue warms. Sera introduces detective to regulars. Access to bar gossip unlocks. |
| Smuggler | `insider` (regular) | `insider` → `hostile` | Social contamination from hub (ring turns on smuggler) | Bar dialogue shifts from warm to cold. The bar owner stops saving the smuggler's seat. Regulars stop buying rounds. |
| Detective | `public` | `public` → `peer` | Repeated visits (3-4), becomes a regular, earns the bar owner's respect | Greeting dialogue warms. {THE FRIEND} introduces detective to regulars. Access to bar gossip unlocks. |
**The Ring (Smuggling Operations)**
| Character | Starting Tier | Likely Shift | Trigger | Content Requirement |
|-----------|--------------|--------------|---------|---------------------|
| Smuggler | `insider` + `peer` | `peer` → `hostile` | Suspected of cooperation with detective, unauthorized contact (like Kael) | Ring dialogue becomes interrogative. Nils questions loyalty. Operational info stops flowing. |
| Smuggler | `insider` + `peer` | `peer` → `hostile` | Suspected of cooperation with detective, unauthorized contact with the detective | Ring dialogue becomes interrogative. Ring leadership questions loyalty. Operational info stops flowing. |
| Detective | `public` (doesn't know ring exists) | `public` → `hostile` | Stumbles into ring awareness — NPCs react defensively | Immediate evasion. Doors close. No access to insider content, but NPCs' defensive behavior is itself evidence. |
---
@@ -315,13 +296,13 @@ Every content pack must support:
2. **Shifted state dialogue** — the most likely tier transition per character
3. **Monologue that tracks the shift** — the character's internal reaction to changed access
Example from Kael content pack:
Example from THE FRIEND content pack:
*Starting state (Friendly, insider access):*
```yaml
- id: terminal_d_120
role: dock_worker
text: "Container 4471 is flagged. I'll reroute it during shift transition."
text: "Container {N} is flagged. I'll reroute it during shift transition."
access: [insider]
trust: real
situation: [shift_transition]
@@ -336,7 +317,7 @@ Example from Kael content pack:
access: [public]
trust: surface
situation: [shift_start]
notes: "Post-contradiction. Kael is surface-normal. The warmth is gone. The insider content is locked."
notes: "Post-contradiction. THE FRIEND is surface-normal. The warmth is gone. The insider content is locked."
```
*Smuggler monologue tracking the shift:*
@@ -346,8 +327,8 @@ Example from Kael content pack:
trigger: post_conversation
prerequisite:
relationship_state: PersonOfInterest
subject: kael_davan
text: "Same old Kael. Same jokes, same routine. ...What are you not telling me?"
subject: {friend_npc_slug}
text: "Same old {THE FRIEND}. Same jokes, same routine. ...What are you not telling me?"
mood: [conflicted]
topic: [colleague]
notes: "Phase 5: Contaminated trust. Every normal interaction is now suspicious."
@@ -369,7 +350,7 @@ The vertical slice is 30 minutes. Divergence between the smuggler and detective
**Minimal Differences:**
- Monologue voice is different (smuggler: casual, relational; detective: analytical, institutional).
- NPC greetings vary by recognition (smuggler gets "There you are" from Kael; detective gets "Can I help you?" from Voss).
- NPC greetings vary by recognition (smuggler gets "There you are" from THE FRIEND; detective gets "Can I help you?" from the supervisor).
- The smuggler's monologue references operational context ("shift transition in thirty minutes"). The detective's monologue references investigative context ("manifest discrepancies tied to this hub").
**Player Experience:**
@@ -380,18 +361,18 @@ The two characters feel similar. The world is shared. The voice is different, bu
### Minutes 10-20: Growing Divergence
**Access Tiers Start to Differ:**
- The smuggler hears `insider` dialogue from Kael, Voss, Lera. Ring operational talk. Close colleague warmth.
- The detective hears `authority` dialogue from Maret, Drin, Voss. Institutional leverage questions. Evasive answers.
- The smuggler hears `insider` dialogue from THE FRIEND, colleagues, bar regulars. Ring operational talk. Close colleague warmth.
- The detective hears `authority` dialogue from hub workers and supervisors. Institutional leverage questions. Evasive answers.
- The smuggler's `peer` access to bar regulars unlocks gossip, complaints, social texture. The detective is still `public` at the bar — polite but distant.
**Monologue Pools Diverge:**
- The smuggler's monologue starts tracking operational risk: "Torek's spending is too visible." "Maret's been quiet lately — did she notice something?"
- The detective's monologue starts tracking behavioral tells: "Dock worker Davan — lattice activity spiked." "Voss deflected when I asked about overnight containers."
- The smuggler's monologue starts tracking operational risk: "That spending is too visible." "They've been quiet lately — did they notice something?"
- The detective's monologue starts tracking behavioral tells: "Dock worker {Surname} — lattice activity spiked." "{Supervisor} deflected when I asked about overnight containers."
**NPCs Respond Differently:**
- Kael is warm to the smuggler (Friendly relationship), clinical to the detective (Unknown or Known).
- Sera is warm to the detective (Friendly, pre-existing contact), wary to the smuggler (Commission presence).
- Lera is protective of regulars around the detective (defensive), casual with the smuggler (insider).
- THE FRIEND (smuggler's) is warm to the smuggler (Friendly relationship), clinical to the detective (Unknown or Known).
- THE FRIEND (detective's) is warm to the detective (Friendly, pre-existing contact), wary to the smuggler (Commission presence).
- The bar owner is protective of regulars around the detective (defensive), casual with the smuggler (insider).
**Player Experience:**
The same room. Different colors. Different names. Different monologue. The player who's played both paths starts to notice: "Wait, I didn't hear that line as the detective." The asymmetry is becoming visible.
@@ -403,21 +384,21 @@ The same room. Different colors. Different names. Different monologue. The playe
**Completely Different Internal Experiences:**
**Smuggler (navigating ring crisis):**
- Kael's contradiction discovered. The FRIEND arc is in Phase 3-4 (shock, confrontation).
- THE FRIEND's contradiction discovered. The FRIEND arc is in Phase 3-4 (shock, confrontation).
- Monologue is emotionally loaded: hurt, betrayal, protectiveness, fear of exposure.
- Access to `insider` content at The Terminal and bar. Operational dialogue about shift windows, container routing, risk management.
- Relationship stakes are personal: "Kael is lying to me. What do I do? Confront? Protect? Report to Nils?"
- Access to `insider` content at the terminal and bar. Operational dialogue about shift windows, container routing, risk management.
- Relationship stakes are personal: "THE FRIEND is lying to me. What do I do? Confront? Protect? Report up the chain?"
**Detective (uncovering evidence):**
- Sera's contradiction discovered. The FRIEND arc is in Phase 3-4 (pattern confirmed, question asked).
- Monologue is analytically loaded: suspicion, professional conflict, moral cost of using Sera's concealment.
- Access to `authority` content at The Terminal. Institutional leverage. Maret might cooperate. Drin might turn.
- Relationship stakes are institutional: "Sera knows something. Do I press? Report her? Protect her?"
- THE FRIEND's contradiction discovered. The FRIEND arc is in Phase 3-4 (pattern confirmed, question asked).
- Monologue is analytically loaded: suspicion, professional conflict, moral cost of using THE FRIEND's concealment.
- Access to `authority` content at the terminal. Institutional leverage. Some NPCs might cooperate. Others might turn.
- Relationship stakes are institutional: "THE FRIEND knows something. Do I press? Report them? Protect them?"
**Zero Overlap in Emotional Journey:**
- The smuggler is inside a community facing internal betrayal.
- The detective is outside a community trying to crack it open.
- The same events (Kael's nervousness, Sera's avoidance, Torek's spending) mean completely different things to each character.
- The same events (THE FRIEND's nervousness, THE FRIEND's avoidance, the ring's visible tells) mean completely different things to each character.
**Player Experience:**
"I was only seeing HALF of this." The replay reveals a completely different game. Not just "I knew different things" — "I cared about different things." The divergence is total.
@@ -440,12 +421,12 @@ Before submitting a line, ask:
### Question 1: Does this line make sense if the smuggler hears it?
**Test:** Read the line aloud. Imagine the smuggler — a dock worker who's been on Sova for years, knows the ring from inside, thinks in operational terms, worries about people. Does this line sound like something an NPC would say TO a smuggler? Or does it assume the listener is an outsider / authority figure?
**Test:** Read the line aloud. Imagine the smuggler — a dock worker who's been in the district for years, knows the ring from inside, thinks in operational terms, worries about people. Does this line sound like something an NPC would say TO a smuggler? Or does it assume the listener is an outsider / authority figure?
**Common failures:**
- NPC explains basic station layout to the smuggler (the smuggler already knows).
- NPC uses institutional vocabulary the smuggler wouldn't recognize ("manifest reconciliation protocol" instead of "the paperwork doesn't match").
- NPC is defensive or evasive without cause (why would Kael be evasive with his closest colleague unless something's wrong?).
- NPC is defensive or evasive without cause (why would THE FRIEND be evasive with their closest colleague unless something's wrong?).
**Fix:** Rewrite the line for insider context. Or tag it `access: [authority, public]` so the smuggler never hears it.
@@ -453,11 +434,11 @@ Before submitting a line, ask:
### Question 2: Does this line make sense if the detective hears it?
**Test:** Read the line aloud. Imagine the detective — a Commission investigator, new to the district, analytical training, institutional frame, no prior relationships except Sera. Does this line sound like something an NPC would say TO a detective? Or does it assume the listener already belongs to the community?
**Test:** Read the line aloud. Imagine the detective — a Commission investigator, new to the district, analytical training, institutional frame, no prior relationships except {THE FRIEND}. Does this line sound like something an NPC would say TO a detective? Or does it assume the listener already belongs to the community?
**Common failures:**
- NPC uses in-group slang or references without explanation (the detective doesn't have the context yet).
- NPC is too warm / too trusting (why would Voss share operational details with an investigator?).
- NPC is too warm / too trusting (why would {Supervisor} share operational details with an investigator?).
- NPC volunteers sensitive information unprompted (people don't do that to authorities they don't trust).
**Fix:** Rewrite the line for outsider context. Or tag it `access: [insider, peer]` so the detective never hears it.
@@ -496,7 +477,7 @@ Before submitting a line, ask:
**Common failures:**
- Line is generic social lubricant ("Nice weather today" — there's no weather on a station).
- Line repeats information the character already has ("Kael works at the dock" — the smuggler knows this).
- Line repeats information the character already has ("they work at the dock" — the smuggler knows this).
- Line doesn't connect to any NPC axis (Want, Secret, Relationship, Tolerance) or triangle tension.
**Fix:** Every line should serve character, relationship, or narrative. If it doesn't, cut it or replace it with a line that does. Content budget is finite. No filler.
@@ -507,7 +488,7 @@ Before submitting a line, ask:
### The Pattern
Each playable character has one "FRIEND" NPC — a production-level complex character that exercises every content and systems pipeline at full depth. THE FRIEND is the emotional centerpiece of v0.1 and carries D-027 success criterion #3 ("player names an NPC they felt conflicted about").
Each playable character has one "FRIEND" NPC — a production-level complex character that exercises every content and systems pipeline at full depth. THE FRIEND is the emotional centerpiece and carries D-027 success criterion #3 ("player names an NPC they felt conflicted about").
**THE FRIEND follows a reusable pattern:**
@@ -524,108 +505,71 @@ Each playable character has one "FRIEND" NPC — a production-level complex char
---
### Smuggler's FRIEND: Kael Davan
### Smuggler's FRIEND
**Who:** Dock worker, Sova Transit District Logistics Hub. The smuggler's closest colleague. Ring member. Handles physical cargo routing.
*v0.1 named-NPC profile removed — cited NPCs no longer in v0.2 pipeline (D-122). Author against the active roster.*
**Structural specification (invariant):**
**Who:** A district worker who is the smuggler's closest colleague and a ring member. Handles physical cargo routing.
**Surface Presentation (Minutes 0-10):**
Warm, reliable, slightly sardonic. Greets the smuggler with genuine affection. Talks about shift schedules, complains about Voss, asks about the smuggler's weekend. Feels like the best coworker you've ever had.
Warm, reliable, slightly sardonic. Greets the smuggler with genuine affection. Feels like the best coworker you've ever had.
**What the Smuggler Knows:**
Kael is a ring member. This isn't a secret from the smuggler — it's shared context. They work together on both the legitimate side and the ring side. The smuggler trusts Kael because they've shared risk for two years.
THE FRIEND is a ring member. This is shared context. They work together on both the legitimate side and the ring side.
**The Contradiction:**
The smuggler sees Kael in the restricted maintenance corridor (Corridor B-7) talking to someone the smuggler doesn't recognize. Late. Off-shift. The person leaves before the smuggler gets close.
Smuggler monologue: *"That's Kael. But who's he talking to? I don't know that face."*
This is NOT the detective. This is someone from outside the ring's known network. Kael has a side arrangement the smuggler doesn't know about.
**The Shift Arc (Triangle 4: The Worried Partner)**
Kael is at the center of Triangle 4 (Naia-Kael-Sera). His partner Naia is worried about his late nights. Naia has confided in Sera (Commission field tech, the detective's FRIEND). Kael is oblivious to the anxiety he's causing. The unknown contact is someone offering to help Kael exit the ring — to protect Naia. Kael is trying to get out. But from the smuggler's perspective, any unauthorized contact is a security breach.
The smuggler sees THE FRIEND in a restricted area talking to someone unrecognized. Late. Off-shift. THE FRIEND has an unauthorized contact the smuggler doesn't know about.
| Phase | Timing | Smuggler Observes | Monologue Register | Tell |
|-------|--------|------------------|-------------------|------|
| **Phase 1: Comfort** | 0-10 min | Kael is warm, reliable, present. Business as usual. | Fond, casual: *"Kael's already at the dock. Good. The day's better when he's on shift."* | None — baseline comfortable |
| **Phase 2: First Crack** | 10-15 min | Kael checks lattice more often. Excuses himself from lunch early. | Mild concern: *"Kael's distracted today. Probably nothing."* | Behavioral: increased lattice checking, shortened interactions |
| **Phase 3: The Contradiction** | 15-20 min | Corridor B-7. Unknown contact. Spatial deviation. | Alarm + confusion: *"That wasn't anyone from our rotation. And Kael didn't tell me about a meeting."* | Spatial: Kael in unexpected location at unexpected time |
| **Phase 4: Confrontation** | 20-25 min | Smuggler asks. Kael deflects: "Just a thing. Don't worry about it." He's lying. | Betrayal crystallizing: *"He looked left before answering. He always looks left when he's making something up."* | Dialogue: evasion, subject change, the tell confirmed |
| **Phase 5: Contaminated Trust** | 25-30 min | Everything looks normal again. But the smuggler is watching. | Conflicted: *"Same old Kael. Laughing at the same jokes. ...What are you not telling me?"* | Emotional: every warm interaction is now suspicious |
| **Phase 1: Comfort** | 0-10 min | THE FRIEND is warm, reliable. Business as usual. | Fond, casual. | None — baseline |
| **Phase 2: First Crack** | 10-15 min | Increased lattice checks. Early exits. | Mild concern: "Distracted today. Probably nothing." | Behavioral deviations |
| **Phase 3: The Contradiction** | 15-20 min | Unauthorized location. Unknown contact. | Alarm + confusion: "Who is that? That's not our rotation." | Spatial deviation |
| **Phase 4: Confrontation** | 20-25 min | THE FRIEND deflects: "Just a thing. Don't worry about it." | Betrayal crystallizing: "That tell. They're lying to me." | Tell confirmed |
| **Phase 5: Contaminated Trust** | 25-30 min | Surface normality. But the smuggler is watching. | Conflicted: "Same old them. ...What are you not telling me?" | Contaminated warmth |
**RelationshipState Transition:**
`Friendly` (green) → `PersonOfInterest` (amber) at Phase 3 contradiction discovery.
**Access Tier Shift:**
`insider` + `peer` dialogue locks out at Phase 3. Kael still talks to the smuggler, but the warmth is gone. Only `public` + `surface` lines remain. That absence IS the narrative.
**Content Requirements:**
~70-100 authored lines (no generation expansion):
- 25-35 dialogue lines (greetings, shift talk, bar casual, ring coordination, deflection, confrontation responses)
- 15-20 trust-gated lines (insider ring talk, close colleague warmth, secret-tier hints about wanting out)
- 5-8 unprompted lines (Kael volunteers info early, warnings/deflections late)
- 10-15 monologue lines (smuggler about Kael: warmth, concern, contradiction discovery, post-confrontation, contaminated trust)
- 10-15 monologue lines (detective about Kael: identification, behavioral observation, suspicion, informant potential)
- 5-8 tell observation lines (lattice checking, distraction, looks-left tell, spatial deviation)
- 3-5 contradiction discovery lines (Corridor B-7 moment from multiple angles)
**Content Requirements:** ~70-100 authored lines per character file.
---
### Detective's FRIEND: Sera Venn
### Detective's FRIEND
**Who:** Commission field technician, off-duty bar regular. The detective's pre-existing contact in the district. Same institutional background. Transferred to Sova a year ago. The detective's social anchor.
*v0.1 named-NPC profile removed — cited NPCs no longer in v0.2 pipeline (D-122). Author against the active roster.*
**Structural specification (invariant):**
**Who:** A Commission field technician and bar regular. The detective's pre-existing contact in the district. Same institutional background. The detective's social anchor.
**Surface Presentation (Minutes 0-10):**
Competent, slightly wry, comfortable in the district. When the detective visits the bar, Sera waves them over. Easy rapport. Fills in background — who the regulars are, what the district's like. The detective's guide to an unfamiliar place.
Competent, slightly wry, comfortable in the district. Fills in background — who the regulars are, what the district's like. The detective's guide to an unfamiliar place.
**What the Detective Knows:**
Sera is reliable. She transferred for routine work after a stressful posting elsewhere. She doesn't have skin in the smuggling game. She's the detective's safe harbor.
THE FRIEND is reliable. Transferred for routine work. No skin in the smuggling game. Safe harbor.
**The Contradiction:**
Sera always leaves when Torek Lintar arrives at the bar. Always. Three times in a row. Different excuses each time. "Early shift tomorrow." "Headache." "Need to check something at the kiosk."
Detective monologue: *"That's the third time Sera's left when Torek walked in. That's not coincidence."*
**The Shift Arc (Triangle 4: The Worried Partner)**
Sera is at the other node of Triangle 4. Naia (Kael's partner) confides in Sera about Kael's late nights. Sera — being a Commission tech with system access — ran an unofficial compliance check on Kael's work patterns. She found manifest discrepancies. She knows something is wrong. She hasn't reported it because Naia is her friend, and reporting would mean Kael gets investigated, possibly arrested, and Naia's life falls apart. Sera is sitting on unreported evidence. She avoids Torek because Torek is ring-adjacent, and she doesn't want to be seen near him while concealing what she knows.
THE FRIEND always leaves when a specific ring-adjacent NPC arrives at the bar. Always. Three times in a row. Different excuses each time.
| Phase | Timing | Detective Observes | Monologue Register | Tell |
|-------|--------|-------------------|-------------------|------|
| **Phase 1: Trust** | 0-10 min | Sera is warm, informative, helpful. Shares district intel freely. | Professional + personal warmth: *"Good to see Sera. She always was the reliable one."* | None — baseline comfortable |
| **Phase 2: Background Data** | 10-15 min | Sera mentions Naia (Kael's partner) as "a friend." Naia joins them once. Genuine rapport. | Noting: *"Sera's connected here. Good. She knows the locals."* | Social: Sera has relationships outside institutional channels |
| **Phase 3: The Pattern** | 15-20 min | Third departure when Torek arrives. Three different excuses. Same result. | Suspicion activating: *"That's the third time. Three excuses, one result. That's data."* | Behavioral: avoidance pattern, excuse variety, timing correlation |
| **Phase 4: The Question** | 20-25 min | Detective asks about Torek. Sera tenses. Deflects: "He's just loud. I don't like loud drunks." | Professional analysis + personal conflict: *"She's not lying. But she's not telling me everything."* | Dialogue: controlled deflection, topic change, re-establishing warmth quickly |
| **Phase 5: Contaminated Trust** | 25-30 min | Sera continues being helpful. Maybe MORE helpful — compensating. | Analytical doubt: *"Still the same Sera. Still reliable. ...But reliable about what?"* | Emotional: detective's observation lines shift from trusting to evaluating |
| **Phase 1: Trust** | 0-10 min | THE FRIEND is warm, informative, helpful. | Professional + personal warmth: "Reliable. Finally someone who speaks my language." | None — baseline |
| **Phase 2: Background Data** | 10-15 min | THE FRIEND shows connections outside institutional channels. | Noting: "Connected here. Good." | Social: relationships beyond institutional role |
| **Phase 3: The Pattern** | 15-20 min | Third departure when the ring-adjacent NPC arrives. | Suspicion activating: "Three times. Three excuses. That's data." | Behavioral: avoidance pattern |
| **Phase 4: The Question** | 20-25 min | Detective asks. THE FRIEND deflects. | Analysis + personal conflict: "Not lying. But not telling everything." | Controlled deflection |
| **Phase 5: Contaminated Trust** | 25-30 min | THE FRIEND continues being helpful. Maybe too helpful. | Analytical doubt: "Still reliable. ...But reliable about what?" | Evaluating what was trusted |
**RelationshipState Transition:**
`Friendly` (green) → `PersonOfInterest` (amber) at Phase 3 pattern confirmation.
**Access Tier Shift:**
`peer` dialogue available at Phase 1-2. At Phase 3, `authority` dialogue unlocks (detective can press institutional leverage questions). `peer` warmth remains but is contaminated.
**Content Requirements:**
~70-100 authored lines (no generation expansion):
- 25-35 dialogue lines (bar greetings, district orientation, Naia conversation, institutional discussion, deflection about Torek, confrontation responses)
- 15-20 trust-gated lines (peer-tier institutional background, secret-tier hints about what she found)
- 5-8 unprompted lines (Sera volunteers district background early, steers away from sensitive areas late)
- 10-15 monologue lines (detective about Sera: trust/relief, pattern observation, contradiction discovery, post-confrontation)
- 10-15 monologue lines (smuggler about Sera: institutional categorization, avoidance notation, cautious assessment)
- 5-8 tell observation lines (avoidance pattern x3, topic deflection, overcompensation helpfulness, extended kiosk time)
- 3-5 contradiction discovery lines (third departure from multiple angles)
**Content Requirements:** ~70-100 authored lines per character file.
---
### Why THE FRIEND Works Narratively
**Kael's contradiction isn't "Kael is secretly evil."**
The contradiction is "Kael is secretly desperate, and his desperation is making him do exactly the kind of thing that could get everyone caught." The smuggler's anger is justified (protocol breach). Kael's motivation is sympathetic (protecting family). No clean answer. That's the conflict.
**Sera's contradiction isn't "Sera is corrupt."**
The contradiction is "Sera is a good person making a terrible choice: loyalty to a friend vs. duty to her institution." The detective's discovery doesn't reveal a villain — it reveals a moral compromise the detective might understand. The question becomes: do I report Sera? Use what she knows? Confront and risk losing my only ally?
**The contradiction isn't "THE FRIEND is secretly evil."**
The contradiction is that THE FRIEND is desperate, or protecting someone, or making a terrible choice between loyalty and duty. Their motivation is sympathetic. The player's response is justified. No clean answer. That's the conflict.
**Dual-Lens Resonance:**
The smuggler who's played the detective path knows the investigation is closing in — Kael's exit attempt reads differently (not betrayal, desperation). The detective who's played the smuggler path knows why Sera is protecting Naia — Sera's silence reads differently (not corruption, loyalty).
The player who's completed both paths understands why THE FRIEND behaved as they did from both angles. The first reading felt like betrayal or concealment. The second reading reveals it as protection or fear. Same NPC. Different understanding.
---
@@ -639,11 +583,11 @@ The smuggler who's played the detective path knows the investigation is closing
| Parameter | Value | Example |
|-----------|-------|---------|
| **Sentence length** | Short. Fragments welcome. Rarely more than 2 sentences per monologue. | *"Kael's here. Good."* |
| **Sentence length** | Short. Fragments welcome. Rarely more than 2 sentences per monologue. | *"They're here. Good."* |
| **Vocabulary** | Concrete, physical, sensory. Trade jargon (containers, manifests, shifts, routes) without explaining. No institutional language. | *"Recycled air and cargo lubricant."* Not: "Standard atmospheric recycling." |
| **Emotional register** | Feeling-first, analysis second. Names the gut before the brain catches up. | *"Starting to worry"* before *"something's off."* |
| **Relationship mode** | First-name basis. People defined by connection, not role. | *"Kael"* not *"Davan."* *"Voss is tense"* not *"the shift supervisor seems agitated."* |
| **Observation priority** | People > environment > objects. Notices body language before cargo. | *"Kael keeps checking his lattice"* before *"Container 4471 is still in temp."* |
| **Relationship mode** | First-name basis. People defined by connection, not role. | *"{THE FRIEND}"* not *"{Surname}."* *"{NPC} is tense"* not *"the shift supervisor seems agitated."* |
| **Observation priority** | People > environment > objects. Notices body language before cargo. | *"THE FRIEND keeps checking their lattice"* before *"Container 4471 is still in temp."* |
| **Operational thinking** | Present when thinking about the job. Time-aware, route-aware, schedule-aware. Filtered through "is this safe for my people?" | *"Transition window opens in fifty minutes."* |
| **Self-reference** | Rare. Thinks about others, not herself. When it occurs, through physical sensation. | *"My stomach dropped"* not *"I feel betrayed."* |
| **Humor** | Dry, situational, understated. Dark when stressed. Never witty. | *"Home sweet home"* about a cargo bay. |
@@ -656,20 +600,20 @@ The smuggler who's played the detective path knows the investigation is closing
#### Voice Anchors (Reference Lines)
These 5 lines define the boundaries. Every smuggler monologue should feel like it could sit next to these:
These 5 lines define the register. Every smuggler monologue should feel like it could sit next to these:
1. **Baseline warm:** *"Kael's already at the dock. Good. The day's better when he's on shift."*
2. **Operational:** *"Shift transition in thirty minutes. If Voss kept the schedule thin, the route's clear."*
3. **Concerned:** *"Kael keeps checking his lattice. Waiting for a message? Not like him to be jumpy."*
4. **Hurt:** *"He looked left. He always looks left when he's making something up. Two years I've known that tell. Kael is lying to me."*
1. **Baseline warm:** *"Already at the dock. Good. The day's better when they're on shift."*
2. **Operational:** *"Shift transition in thirty minutes. If the supervisor kept the schedule thin, the route's clear."*
3. **Concerned:** *"They keep checking their lattice. Waiting for a message? Not like them to be jumpy."*
4. **Hurt:** *"That tell. They always do that when they're making something up. I've known that tell for years. They're lying to me."*
5. **Atmospheric:** *"Morning shift. Recycled air and cargo lubricant. Home sweet home."*
#### Anti-Patterns (What the Smuggler Does NOT Sound Like)
- *"I should investigate this anomaly further."* (Too clinical. She'd think: *"That's not right."*)
- *"The scheduling irregularity suggests systemic manipulation."* (Institutional vocabulary. She'd think: *"Voss changed the rotation again."*)
- *"I need to consider the implications of Kael's behavior for our operational security."* (Analytical distance. She'd think: *"What the hell is Kael doing?"*)
- *"According to the manifest, container 4471 should weigh 240 kilograms."* (Explaining what she already knows. She'd think: *"4471's heavy. Too heavy."*)
- *"I should investigate this anomaly further."* (Too clinical. They'd think: *"That's not right."*)
- *"The scheduling irregularity suggests systemic manipulation."* (Institutional vocabulary. They'd think: *"The rotation changed again."*)
- *"I need to consider the implications of their behavior for our operational security."* (Analytical distance. They'd think: *"What the hell are they doing?"*)
- *"According to the manifest, this container should weigh 240 kilograms."* (Explaining what they already know. They'd think: *"Too heavy."*)
---
@@ -682,10 +626,10 @@ These 5 lines define the boundaries. Every smuggler monologue should feel like i
| Parameter | Value | Example |
|-----------|-------|---------|
| **Sentence length** | Complete sentences, but not long. More structured than the smuggler. Occasional fragments for emphasis. | *"Standard prefab, heavy foot traffic. Let's see what the shift change tells me."* |
| **Vocabulary** | Institutional layer over plain speech. Professional terms: "case file," "filing it," "noted," "flagged." Not technical jargon — investigative habit. | *"Dock worker. Davan, K. Unremarkable on paper."* The surname-comma-initial is institutional reflex. |
| **Emotional register** | Analysis-first, personal second. When personal breaks through, it's notable — a crack in the professional surface. | *"She's not lying. But she's not telling me everything. Sera, what do you know?"* The first-name appeal IS the emotion. |
| **Relationship mode** | Surname-first for targets and unknowns. First-name for allies and trusted. The shift IS a relationship marker. | *"Davan, K."* early → *"Kael"* never (smuggler's FRIEND, not detective's). *"Sera"* always (detective's FRIEND). |
| **Observation priority** | Patterns > people > environment. Notices deviations from expected before noticing the person. | *"That's twice now"* before *"Sera leaves."* The count matters more than the actor. |
| **Vocabulary** | Institutional layer over plain speech. Professional terms: "case file," "filing it," "noted," "flagged." Not technical jargon — investigative habit. | *"Dock worker. {Surname}, {initial}. Unremarkable on paper."* The surname-comma-initial is institutional reflex. |
| **Emotional register** | Analysis-first, personal second. When personal breaks through, it's notable — a crack in the professional surface. | *"They're not lying. But they're not telling me everything. {THE FRIEND}, what do you know?"* The first-name appeal IS the emotion. |
| **Relationship mode** | Surname-first for targets and unknowns. First-name for allies and trusted. The shift IS a relationship marker. | *"{Surname}, {initial}."* early → *"{first name}"* never (smuggler's FRIEND, not detective's). *"{THE FRIEND}"* always (detective's FRIEND). |
| **Observation priority** | Patterns > people > environment. Notices deviations from expected before noticing the person. | *"That's twice now"* before *"{THE FRIEND} leaves."* The count matters more than the actor. |
| **Analytical thinking** | Automatic. Counts, tracks, flags. Self-directs: "filing it," "noted," "coincidence?" Internal bookkeeping. | *"Three times. Three excuses. That's data."* |
| **Self-reference** | More common than the smuggler, but always through professional lens. Monitors own state as evidence. | *"I'm reading too much into this"* — self-aware about analytical bias. |
| **Humor** | Wry, observational. Appreciates irony at a distance. Can laugh at himself. Never cruel. | *"Only place in this district that doesn't smell like freight lubricant."* |
@@ -699,16 +643,16 @@ These 5 lines define the boundaries. Every smuggler monologue should feel like i
#### Voice Anchors (Reference Lines)
1. **Clinical baseline:** *"Logistics hub. Standard prefab, heavy foot traffic. Let's see what the shift change tells me."*
2. **Pattern recognition:** *"That's the third time. Sera leaves when Torek arrives. Three different excuses, same result. That's not coincidence."*
3. **Personal leak:** *"Good to see Sera. She always was the reliable one. At least someone in this district speaks my language."*
4. **Conflicted:** *"Same booth. Same warm smile. Same offer to buy me a drink. ...Everything except whatever she's not saying."*
2. **Pattern recognition:** *"That's the third time. {THE FRIEND} leaves when {NPC} arrives. Three different excuses, same result. That's not coincidence."*
3. **Personal leak:** *"Good to see them. Always the reliable one. At least someone in this district speaks my language."*
4. **Conflicted:** *"Same booth. Same warm smile. Same offer to buy me a drink. ...Everything except whatever they're not saying."*
5. **Atmospheric:** *"Grain spirit and low conversation. Only place in this district that doesn't smell like freight lubricant."*
#### Anti-Patterns (What the Detective Does NOT Sound Like)
- *"Kael's here. Good."* (Too terse. That's the smuggler. The detective: *"Davan's on shift. Standard."*)
- *"I feel uneasy about Sera's behavior."* (Direct emotional vocabulary. He'd think: *"Something's off with Sera. Can't place it yet."*)
- *"This container has been tampered with, indicating smuggling activity."* (Explaining the obvious. He'd think: *"Weight's wrong. Noted."*)
- *"They're here. Good."* (Too terse. That's the smuggler. The detective: *"{Surname}'s on shift. Standard."*)
- *"I feel uneasy about their behavior."* (Direct emotional vocabulary. They'd think: *"Something's off with them. Can't place it yet."*)
- *"This container has been tampered with, indicating smuggling activity."* (Explaining the obvious. They'd think: *"Weight's wrong. Noted."*)
- *"My heart sank when I saw the evidence."* (Physical emotion — smuggler's register. Detective: *"Didn't want to see that. But there it is."*)
---
@@ -722,17 +666,17 @@ These 5 lines define the boundaries. Every smuggler monologue should feel like i
**Trigger:** Entering the bar.
- **Smuggler:** *"Lera's. Grain spirit and noise. Could use both right now."*
- **Detective:** *"The Last Shift. Same crowd as yesterday. Let's see who's NOT here tonight."*
- **Smuggler:** *"The bar. Grain spirit and noise. Could use both right now."*
- **Detective:** *"Same crowd as yesterday. Let's see who's NOT here tonight."*
**Trigger:** Noticing Naia Tamm is upset.
**Trigger:** Noticing a civilian NPC (THE MIRROR type) is visibly upset.
- **Smuggler:** *"Naia looks rough today. Should check on her later."*
- **Detective:** *"Tamm seems distressed. Not her baseline. Something at home, or something she's heard?"*
- **Smuggler:** *"They look rough today. Should check on them later."*
- **Detective:** *"Seems distressed. Not their baseline. Something at home, or something they've heard?"*
**Trigger:** Hearing raised voices behind a door.
- **Smuggler:** *"Raised voices from the back room. Devra's in there. That's not a brokering call."*
- **Smuggler:** *"Raised voices from the back room. That's not a routine call."*
- **Detective:** *"Arguing behind that door. The bartender didn't flinch. Either she's used to it or she knows what it is."*
---
@@ -747,4 +691,4 @@ That's the job.
---
**End Dual Lens Authoring Guide v0.1**
**End Dual Lens Authoring Guide**
wiki/authoring/environmental-text-examples.md
+34 -39
View File
@@ -6,32 +6,32 @@ category: authoring-guide
status: canonical
created: 2026-02-13
updated: 2026-02-13
tags: [v0.1, authoring, environmental-text]
decision_refs: [D-016, D-032, D-036]
cross_refs: [monologue-guide, the-last-shift, the-terminal, maintenance-corridors]
tags: [authoring, environmental-text]
decision_refs: [D-016, D-032]
cross_refs: [monologue-guide]
---
# Environmental Text Examples
Worked examples of diegetic environmental text for Sova Transit District. Each example is Van Maanen's Star-voiced (working-class, direct, compact) with cultural notes explaining the choices, followed by monologue pairings showing how the smuggler and detective read the same text differently.
Worked examples of diegetic environmental text for a working freight district. Each example is mid-Reach industrial-voiced (working-class, direct, compact) with cultural notes explaining the choices, followed by monologue pairings showing how the smuggler and detective read the same text differently.
Environmental text is not decoration. It is world-state that the player reads through their character's perspective. The same sign on the same wall tells two different stories.
---
## 1. Bar Menu — The Last Shift
## 1. Bar Menu — The Local Bar
Mounted behind the bar counter. Hand-lettered on a metal panel in Lera's handwriting. Prices in station credits. Menu changes rarely — when an item runs out, Lera crosses it off and writes the replacement below.
Mounted behind the bar counter. Hand-lettered on a metal panel in the bar owner's handwriting. Prices in station credits. Menu changes rarely — when an item runs out, it gets crossed off and the replacement written below.
### The Text
```
LERA'S
THE LAST SHIFT
Grain spirit (Sova-brewed) 4
Grain spirit (station-brewed) 4
Grain spirit, double 7
Station lager 5
Imported lager (Van Maanen's Star Prime) 12
Imported lager (system prime) 12
Synth ale (cold) 3
Fried protein + bread 6
@@ -45,15 +45,15 @@ Last call 01:30.
### Cultural Notes
- **Pricing tells a story.** Imported lager at 12 credits — five shifts' disposable income for a logistics worker earning 200 credits margin per month. Ordering one is a status display. The smuggler knows who can afford it and who's showing off. The detective notes the financial tell.
- **"Ask what's in it"** — Van Maanen's Star directness. Lera doesn't pretend the stew is gourmet. The regulars don't care. This is food for people who need to eat, not a dining experience.
- **"No tabs. No arguments."** — Lera has been burned. The two-rule footer is social infrastructure: it prevents the awkward conversation where a colleague can't pay, which would damage the bar's function as a place where status is temporarily suspended.
- **Hand-lettered** — not Meridian-displayed. This is deliberate. A printed menu could be updated remotely. A hand-lettered one means Lera stood here and wrote it. It says: this is mine.
- **"Ask what's in it"** — Mid-Reach freight-district directness. No pretense that the stew is gourmet. The regulars don't care. This is food for people who need to eat, not a dining experience.
- **"No tabs. No arguments."** — The owner has been burned. The two-rule footer is social infrastructure: it prevents the awkward conversation where a colleague can't pay, which would damage the bar's function as a place where status is temporarily suspended.
- **Hand-lettered** — not Meridian-displayed. A printed menu could be updated remotely. A hand-lettered one means the owner stood here and wrote it. It says: this is mine.
- **No cocktails, no wine, no elaboration.** The menu matches the clientele: shift workers who want a drink, food, and to be left alone. Complexity would be pretension.
### Monologue Pairings
**Smuggler** (on entering The Last Shift, sees menu):
> Same menu. Same prices. Lera hasn't changed the stew description in three years.
> Same menu. Same prices. They haven't changed the stew description in three years.
*Tags: [environmental, atmospheric]. Trigger: enter_location. This is comfort. Sameness is safety.*
@@ -62,28 +62,28 @@ Last call 01:30.
*Tags: [environmental, investigation]. Trigger: enter_location. The detective reads the menu as economic data.*
**Smuggler** (on observing Torek ordering imported lager):
> Torek's buying the good stuff again. That's three times this week.
**Smuggler** (on observing a ring-adjacent NPC ordering imported lager):
> Buying the good stuff again. That's three times this week.
*Tags: [npc, torek, concern]. Trigger: observe_npc. The smuggler sees financial exposure — Torek's spending beyond what his official income explains.*
*Tags: [npc, concern]. Trigger: observe_npc. The smuggler sees financial exposure — spending beyond what official income explains.*
**Detective** (on observing Torek ordering imported lager):
> Lintar, T. Third imported lager this rotation. Spending pattern inconsistent with pay grade.
**Detective** (on observing a ring-adjacent NPC ordering imported lager):
> {Surname}, {initial}. Third imported lager this rotation. Spending pattern inconsistent with pay grade.
*Tags: [npc, torek, investigation, evidence]. Trigger: observe_npc. Same observation, institutional framing. Surnames, initials, pay grade — the language of a case file.*
*Tags: [npc, investigation, evidence]. Trigger: observe_npc. Same observation, institutional framing. Surnames, initials, pay grade — the language of a case file.*
---
## 2. Safety Notice — The Terminal
## 2. Safety Notice — Logistics Hub
Mounted on the wall near Scanner Bay 3. Concordat Standard official text with Van Maanen's Star vernacular annotation added by a worker in marker. The notice is slightly peeling at the bottom-left corner. Nobody has replaced it in months.
Mounted on the wall near Scanner Bay 3. Concordat Standard official text with freight-district vernacular annotation added by a worker in marker. The notice is slightly peeling at the bottom-left corner. Nobody has replaced it in months.
### The Text
**[Official — Concordat Standard, printed]**
```
SOVA TRANSIT LOGISTICS — BAY 7-C
DISTRICT LOGISTICS HUB — BAY 7-C
SCANNER BAY 3: OPERATIONAL ADVISORY
Spectral calibration drift detected (Report #ST-4471).
@@ -101,7 +101,7 @@ to Bays 1 or 2 pending recalibration.
### Cultural Notes
- **Institutional vs. vernacular** — the two voices on this sign are the two voices of Sova. The printed notice is how the institution talks: passive voice, report numbers, procedures. The marker annotation is how the workers talk: direct, sardonic, lowercase.
- **Institutional vs. vernacular** — the two voices on this sign are the two voices of the district. The printed notice is how the institution talks: passive voice, report numbers, procedures. The marker annotation is how the workers talk: direct, sardonic, lowercase.
- **"Pending recalibration"** is doing heavy narrative work. The calibration drift in Bay 3 is real — it produces less reliable scan results. Station maintenance hasn't fixed it because it's low-priority. The ring routes flagged containers through Bay 3 precisely because of this drift. An institutional failure becomes criminal infrastructure.
- **The peeling corner** — nobody maintains the notice because nobody cares about the notice. The institutional voice has lost authority through inaction. The hand-written annotation has more social force than the printed text.
- **Report #ST-4471** — bureaucratic specificity that makes the notice feel real and gives the detective something to query.
@@ -125,7 +125,7 @@ to Bays 1 or 2 pending recalibration.
---
## 3. News Ticker Cycle — Meridian Feed at The Last Shift
## 3. News Ticker Cycle — Meridian Feed at the Bar
Displayed on the Meridian feed screen mounted above the bar. Scrolling text, standard news format. The cycle repeats every 8-10 minutes. Nobody watches it directly — it's ambient information, absorbed peripherally. Occasionally a headline makes someone look up.
@@ -138,27 +138,27 @@ Displayed on the Meridian feed screen mounted above the bar. Scrolling text, sta
2. CONCORD ASSEMBLY SESSION 1147: LATTICE STANDARDIZATION
AMENDMENT PASSES SECOND READING. IMPLEMENTATION TBD.
3. SOVA STATION: VENTILATION UPGRADE FOR SECTORS 2-4
3. STATION: VENTILATION UPGRADE FOR SECTORS 2-4
APPROVED IN NEXT FISCAL CYCLE. TIMELINE NOT CONFIRMED.
4. MEDICAL SUPPLY ADVISORY: NEURAL INTERFACE REPLACEMENT
COMPONENTS ON 6-WEEK BACKORDER. CONTACT YOUR PROVIDER.
5. COMMISSION ADVISORY: ROUTINE COMPLIANCE ASSESSMENT
SCHEDULED FOR VAN MAANEN SYSTEM STATIONS. DATES TO FOLLOW.
SCHEDULED FOR MID-REACH SYSTEM STATIONS. DATES TO FOLLOW.
6. VAN MAANEN PRIME DOCKWORKERS LEAGUE VS. ORBITAL 3 UNITED:
6. FREIGHT DISTRICT DOCKWORKERS LEAGUE VS. ORBITAL 3 UNITED:
MATCH DAY 7. BROADCAST 19:00 MERIDIAN STANDARD.
```
### Cultural Notes
- **Headline 1 (freight backlog)** — affects every worker in the room. Backlog means overtime or schedule disruption. It's the one headline people actually respond to. Lera turns up the volume when freight news scrolls.
- **Headline 1 (freight backlog)** — affects every worker in the room. Backlog means overtime or schedule disruption. It's the one headline people actually respond to. The bar owner turns up the volume when freight news scrolls.
- **Headline 2 (lattice standardization)** — Assembly politics. Most workers ignore it. But "lattice standardization" has a chill to it: tighter standards mean tighter inspections, which means the grey market gets harder. The smuggler hears threat. The detective hears institutional support.
- **Headline 3 (ventilation upgrade)** — the universal safe topic. "Approved in next fiscal cycle" means "probably never." Workers have been complaining about ventilation for months. This headline generates eye-rolls and muttered commentary that fills conversational space.
- **Headline 4 (neural interface backorder)** — the one that matters most and says least. Neural interface replacements are essential medical supplies. A 6-week backorder on legitimate channels is exactly why the smuggling ring exists: people need these components, the legal supply chain can't deliver, and someone fills the gap. The headline is the ring's business case, printed on a news ticker.
- **Headline 5 (Commission assessment)** — "routine" is a word that means nothing and everything. Routine for the Commission. Not routine for a district that hasn't had a liaison in three months and has been operating in the gap. "Dates to follow" means: start worrying now.
- **Headline 6 (sports)** — normalcy. The match is what most people in the bar actually care about. It's the headline that makes Sova feel like a place where people live, not just a setting for a crime story.
- **Headline 6 (sports)** — normalcy. The match is what most people in the bar actually care about. It's the headline that makes the district feel like a place where people live, not just a setting for a crime story.
### Monologue Pairings
@@ -186,11 +186,11 @@ Displayed on the Meridian feed screen mounted above the bar. Scrolling text, sta
## 4. Corridor Graffiti — Maintenance Corridors
Found at three points along Corridor B-7. The graffiti exists in layers: old maintenance worker marks (decades old, institutional), informal worker tags (years old, social), and recent ring-related marks (weeks to months old, operational). The layers tell the corridor's history.
Found at three points along the restricted maintenance corridor. The graffiti exists in layers: old maintenance worker marks (decades old, institutional), informal worker tags (years old, social), and recent ring-related marks (weeks to months old, operational). The layers tell the corridor's history.
### The Text
**Location: Near south entry (Terminal break room hatch), on the right wall**
**Location: Near south entry (logistics hub break room hatch), on the right wall**
```
[Marker, faded, ~30 years old:]
@@ -226,7 +226,7 @@ shift 3 crew '94
### Cultural Notes
- **VNT-7 JUNCTION** — institutional remnant. This corridor used to be on the maintenance map. The directional marking is from the era when workers were dispatched here officially. It's a ghost of the corridor's legitimate past.
- **"kosse was here. day 1171."** — a maintenance worker who counted their shifts. Van Maanen's Star naming convention (compact, consonant-heavy). Day 1171 is roughly 3.2 years of shift cycles. Someone who spent long enough in these corridors to mark their territory. Kosse is probably retired or transferred. The name persists.
- **"kosse was here. day 1171."** — a maintenance worker who counted their shifts. A common corridor naming convention (compact, consonant-heavy). Day 1171 is roughly 3.2 years of shift cycles. Someone who spent long enough in these corridors to mark their territory. The worker is probably retired or transferred. The name persists.
- **"N.T. + someone who deserved better"** — a small human moment in infrastructure space. The initials could be anyone. The sentiment is universal. It humanizes the corridor — people have always come here for privacy, long before the ring did.
- **The chalk marks** — `—||—` and `|||` — are ring operational markers. They're meaningless to anyone who doesn't know the system. The double-bar mark near the south entry indicates "route active." The three vertical lines near the ventilation hub indicate a count — possibly dead drop cycles, possibly something else. The ring's internal signaling is deliberately ambiguous: even if you find the marks, you can't read them without context.
- **Chalk, not marker** — the ring uses chalk because it can be wiped. Marker is permanent. The choice of medium is operational security.
@@ -235,7 +235,7 @@ shift 3 crew '94
### Monologue Pairings
**Smuggler** (passing the chalk mark near south entry):
> Mark's fresh. Route's active. Renn was through here recently.
> Mark's fresh. Route's active. Someone was through here recently.
*Tags: [environmental, operational]. Trigger: enter_location. The smuggler reads the chalk like a message — because it is one. No emotional response. It's a status indicator.*
@@ -265,7 +265,7 @@ shift 3 crew '94
1. **The text exists before the player arrives.** It was written by someone for a reason that has nothing to do with the player. Write it for the character who put it there, not the character who reads it.
2. **Van Maanen's Star voice is direct.** No flourishes, no unnecessary words, no corporate warmth. "No tabs. No arguments." not "We kindly request that all patrons settle their accounts at time of service."
2. **The freight district voice is direct.** No flourishes, no unnecessary words, no corporate warmth. "No tabs. No arguments." not "We kindly request that all patrons settle their accounts at time of service."
3. **Institutional text and vernacular text coexist.** The tension between them IS the setting. The printed notice says what the institution wants. The hand-written annotation says what the workers know.
@@ -279,13 +279,8 @@ shift 3 crew '94
**Cross-References:**
- [Monologue Authoring Guide](monologue-guide.md) — Monologue formatting and tag reference
- [The Last Shift](../star-systems/van-maanens-star/sova/transit/the-last-shift.md) — Bar location profile
- [The Terminal](../star-systems/van-maanens-star/sova/transit/the-terminal.md) — Logistics hub profile
- [Maintenance Corridors](../star-systems/van-maanens-star/sova/transit/maintenance-corridors.md) — Corridor B-7 profile
- [Sova Transit District](../star-systems/van-maanens-star/sova/transit/index.md) — District overview
- D-016: Internal monologue as primary narrative system
- D-032: Separate monologue pools per character
- D-036: Sova Transit District as v0.1 setting
---
wiki/authoring/line-id-authoring-guide.md
+6 -6
View File
@@ -9,7 +9,7 @@
## The Short Version
- **Role pool lines:** Use `{role-slug}_d_{###}` — e.g., `dock-worker_d_001`. These lines are shared by all NPCs with that role. This is the default for all auto-generated NPC content.
- **Named NPC lines:** Use `{npc-slug}_d_{###}` — e.g., `kael-davan_d_001`. Unchanged from current practice.
- **Named NPC lines:** Use `{npc-slug}_d_{###}` — e.g., `friend-npc_d_001`. Unchanged from current practice.
- **Instance-specific lines (rare):** Use `{role-slug}-{counter}_d_{###}` — e.g., `dock-worker-07_d_001`. Only needed when a specific generated NPC needs content different from the role pool.
---
@@ -28,12 +28,12 @@ This means the role pool approach already handles most cases — the "collision
```
Format: {npc-slug}_{content-type}_{###}
Example: kael-davan_d_001 (Kael's dialogue line 1)
sera-venn_d_015 (Sera's dialogue line 15)
Example: friend-npc_d_001 (authored NPC dialogue line 1)
mirror-npc_d_015 (authored NPC dialogue line 15)
pc-smuggler_m_s_001 (Smuggler monologue line 1)
```
File location: One file per NPC (e.g., `dialogue/maintenance-corridors/kael-davan.yaml`)
File location: One file per NPC (e.g., `dialogue/{location}/{npc-slug}.yaml`)
Numbering: Sequential within the file. Gaps are acceptable (deleted lines leave permanent gaps). Never reuse a number.
@@ -74,7 +74,7 @@ File location: Same directory as the role pool file, separate file with instance
| Situation | ID format to use |
|-----------|------------------|
| Named authored NPC (Kael, Sera, Voss...) | `{npc-slug}_d_{###}` |
| Named authored NPC (THE FRIEND, authored Tier 1...) | `{npc-slug}_d_{###}` |
| Lines any dock worker can say | `dock-worker_d_{###}` |
| Lines any bar regular can say | `bar-regular_d_{###}` |
| Generated NPC with specific triangle role | `{role-slug}-{counter}_d_{###}` |
@@ -93,7 +93,7 @@ The existing ID regex `^[a-z][a-z0-9-]*_[dme]_\d{3}$` accepts all three formats.
1. Start at `001`, increment by 1 for each new line.
2. Never reuse a number, even if a line is deleted. Gaps are fine.
3. Lines within a single file have a contiguous prefix — `dock-worker_d_001` through `dock-worker_d_042`, etc.
4. Cross-file: `kael-davan.yaml` at the terminal and `kael-davan.yaml` at maintenance corridors both use the `kael-davan_d_###` namespace. Continue numbering from where the other file left off (check the existing files first, use a fresh sequence if the NPC is new to a location).
4. Cross-file: `{npc-slug}.yaml` at the terminal and `{npc-slug}.yaml` at a second location both use the same `{npc-slug}_d_###` namespace. Continue numbering from where the other file left off (check the existing files first, use a fresh sequence if the NPC is new to a location).
---
wiki/authoring/monologue-guide.md
+99 -620
View File
@@ -26,13 +26,13 @@ How to write tagged monologue and dialogue content for The Settled Reach. Read t
## Location Shortcodes
Canonical shortcodes for v0.1 Sova Transit District. Used in line IDs (`{shortcode}_{type}_{###}`) and file naming.
Location shortcodes are defined per district. Used in line IDs (`{shortcode}_{type}_{###}`) and file naming. Author per-district shortcode tables in the district wiki entry.
| Shortcode | Location | Full Name | D-036 Reference |
|-----------|----------|-----------|-----------------|
| `terminal` | Logistics Hub | The Terminal | Primary workplace social site |
| `bar` | The Last Shift | Lera's (informal) | Social venue |
| `corridor` | Maintenance corridors | Corridor B-7 (primary) | Smuggling/service spaces |
| Shortcode | Location Type | Notes |
|-----------|-------------|-------|
| `terminal` | Primary workplace (logistics hub, factory floor, etc.) | Assign per district |
| `bar` | Social venue (bar, canteen, commons) | Assign per district |
| `corridor` | Service / restricted spaces | Assign per district |
**File naming convention:** `{shortcode}-{character}.yaml` (e.g., `terminal-smuggler.yaml`, `bar-detective.yaml`)
@@ -99,14 +99,14 @@ Every line carries structural tags, selection tags, and (for monologue) characte
| `role` | enum | Template-defined role, not NPC name (NPC assignment is runtime) |
| `access` | list\<enum\> | Hard filter: `public`, `insider`, `authority`, `peer`, `hostile` |
| `trust` | enum | Hard filter: `surface`, `real`, `secret` |
| `situation` | list\<enum\> | Context filter (13 situations for v0.1) |
| `situation` | list\<enum\> | Context filter (13 situations) |
### Selection Tags (recommended, defaults apply if empty)
| Tag | Type | Purpose |
|-----|------|---------|
| `topic` | list\<enum\> | Weighted selection (9 topics for v0.1) |
| `mood` | list\<enum\> | Weighted selection (8 moods for v0.1) |
| `topic` | list\<enum\> | Weighted selection (9 topics) |
| `mood` | list\<enum\> | Weighted selection (8 moods) |
| `tags` | list\<string\> | Freeform escape hatch for author intent |
### Monologue-Specific Tags (added to structural + selection)
@@ -126,15 +126,15 @@ Every line carries structural tags, selection tags, and (for monologue) characte
### Enum Values
**`situation`** (13 for v0.1):
**`situation`** (13):
`arrival`, `shift_start`, `shift_end`, `shift_transition`, `bar_evening`, `night_shift`, `investigation`, `confrontation`, `social`, `alone`, `emergency`, `routine`, `observation`
**`topic`** (9 for v0.1):
**`topic`** (9):
`colleague`, `routine`, `cargo`, `money`, `trust`, `danger`, `institution`, `personal`, `investigation`
Note: no `crime` or `smuggling` topic. NPCs think of it as `cargo` or `money`. The detective uses `investigation`.
**`mood`** (8 for v0.1):
**`mood`** (8):
`fond`, `comfortable`, `worried`, `suspicious`, `analytical`, `conflicted`, `concerned`, `relieved`
---
@@ -179,18 +179,18 @@ Fires when a known entity enters the player's line of sight.
```yaml
- id: terminal_m_020
text: "Kael's here. Good — I was starting to worry."
text: "{THE FRIEND}'s here. Good — I was starting to worry."
character: smuggler
trigger: observe_npc
mood: [fond]
prerequisite:
relationship_state: Friendly
subject: kael_davan
subject: {friend_npc_slug}
```
```yaml
- id: terminal_m_021
text: "Dock worker from the case file. Davan, K. Unremarkable on paper."
text: "Dock worker from the case file. {Surname}, {initial}. Unremarkable on paper."
character: detective
trigger: observe_npc
mood: [analytical]
@@ -209,7 +209,7 @@ Fires on audio events — ambient, diegetic, or anomalous.
```yaml
- id: bar_m_030
text: "Raised voices from the back room. Devra's in there. That's not a brokering call."
text: "Raised voices from the back room. That's not a routine call."
character: smuggler
trigger: hear_sound
mood: [concerned]
@@ -237,24 +237,24 @@ Fires when the player observes something that contradicts expected state — a c
```yaml
- id: terminal_m_040
text: "Kael's checking his lattice again. Third time in ten minutes. That's not normal."
text: "{THE FRIEND}'s checking their lattice again. Third time in ten minutes. That's not normal."
character: smuggler
trigger: observe_anomaly
mood: [worried]
prerequisite:
relationship_state: Friendly
subject: kael_davan
subject: {friend_npc_slug}
```
```yaml
- id: terminal_m_041
text: "Dock worker Davan — lattice activity spiked. Expecting a message? Or checking for surveillance?"
text: "Dock worker {Surname} — lattice activity spiked. Expecting a message? Or checking for surveillance?"
character: detective
trigger: observe_anomaly
mood: [analytical]
prerequisite:
known_attributes:
subject: kael_davan
subject: {friend_npc_slug}
key: behavior_flags
value_contains: lattice_checking
```
@@ -269,24 +269,24 @@ Fires after a dialogue exchange ends. Internal reaction to what just happened.
```yaml
- id: bar_m_050
text: "Sera's good to have around. Knows the district, knows the people. Reliable."
text: "{THE FRIEND}'s good to have around. Knows the district, knows the people. Reliable."
character: detective
trigger: post_conversation
mood: [fond]
prerequisite:
relationship_state: Friendly
subject: sera_venn
subject: {friend_npc_slug}
```
```yaml
- id: bar_m_051
text: "She's not lying. But she's not telling me everything. Sera, what do you know?"
text: "Not lying. But not telling me everything. {THE FRIEND}, what do you know?"
character: detective
trigger: post_conversation
mood: [conflicted]
prerequisite:
relationship_state: PersonOfInterest
subject: sera_venn
subject: {friend_npc_slug}
```
This is where character voice shines — the detective analyzes, the smuggler worries about people.
@@ -310,7 +310,7 @@ Fires when the player finds physical evidence — a document, object, or data po
```yaml
- id: terminal_m_061
text: "4471's still in temp. Kael routed it there during transition. Standard. Nothing to worry about."
text: "4471's still in temp. Routed there during transition. Standard. Nothing to worry about."
character: smuggler
trigger: discover_evidence
mood: [relieved]
@@ -329,7 +329,7 @@ Fires when the player observes two NPCs interacting.
```yaml
- id: bar_m_070
text: "Sera's headed out. Smart — Torek gets loud after three drinks. Nobody wants to deal with that."
text: "{THE FRIEND}'s headed out. Smart — {NPC} gets loud after three drinks. Nobody wants to deal with that."
character: smuggler
trigger: witness_interaction
mood: [comfortable]
@@ -338,13 +338,13 @@ Fires when the player observes two NPCs interacting.
```yaml
- id: bar_m_071
text: "That's twice now. Sera leaves when Torek arrives. Coincidence? Filing it."
text: "That's twice now. {THE FRIEND} leaves when {NPC} arrives. Coincidence? Filing it."
character: detective
trigger: witness_interaction
mood: [analytical]
prerequisite:
known_attributes:
subject: sera_venn
subject: {friend_npc_slug}
key: behavior_flags
value_contains: avoidance_pattern
```
@@ -364,7 +364,7 @@ Fires after inactivity — the player is standing still, watching, waiting. The
trigger: time_idle
mood: [relieved]
prerequisite:
fact: location.corridor_b7_restricted
fact: location.restricted_corridor
confidence: KnowsDetails
```
@@ -375,7 +375,7 @@ Fires after inactivity — the player is standing still, watching, waiting. The
trigger: time_idle
mood: [suspicious]
prerequisite:
fact: location.corridor_b7_restricted
fact: location.restricted_corridor
confidence: Suspects
```
@@ -389,24 +389,24 @@ Fires when the player returns to a location they've visited before. Distinct fro
```yaml
- id: bar_m_090
text: "Back at Lera's. Same seats, same faces. Sera's in the corner booth. Good."
text: "Back at the bar. Same seats, same faces. {THE FRIEND}'s in the corner booth. Good."
character: detective
trigger: return_visit
mood: [comfortable]
prerequisite:
relationship_state: Friendly
subject: sera_venn
subject: {friend_npc_slug}
```
```yaml
- id: bar_m_091
text: "Back again. Same booth. ...Let's see if Sera leaves when Torek shows up."
text: "Back again. Same booth. ...Let's see if {THE FRIEND} leaves when {NPC} shows up."
character: detective
trigger: return_visit
mood: [suspicious]
prerequisite:
known_attributes:
subject: sera_venn
subject: {friend_npc_slug}
key: behavior_flags
value_contains: avoidance_pattern
```
@@ -437,14 +437,14 @@ prerequisite:
Fires only if the active character knows the named fact at the specified confidence **or higher**. Confidence levels ordered: `Suspects` < `KnowsOf` < `KnowsDetails` < `Direct`.
Use exact FactId strings from the [Fact Catalog](../knowledge/fact-catalog.md) — `"contraband.ring_exists"` not `"Ring Exists"`. The 24 v0.1 FactIds are the only valid values.
Use exact FactId strings from the [Fact Catalog](../knowledge/fact-catalog.md) — `"contraband.ring_exists"` not `"Ring Exists"`. The 24 canonical FactIds are the only valid values.
### Gating on RelationshipState
```yaml
prerequisite:
relationship_state: PersonOfInterest
subject: kael_davan
subject: {npc_slug}
```
Fires only if the active character's relationship with the named entity is the specified state. States: `Unknown`, `Known`, `Friendly`, `PersonOfInterest`, `Hostile`.
@@ -455,7 +455,7 @@ Fires only if the active character's relationship with the named entity is the s
```yaml
prerequisite:
known_attributes:
subject: kael_davan
subject: {npc_slug}
key: contradiction_flagged
value: meeting_unknown_contact
```
@@ -466,7 +466,7 @@ Fires if the active character's `EntityKnowledge` for the target has the exact k
```yaml
prerequisite:
known_attributes:
subject: kael_davan
subject: {npc_slug}
key: behavior_flags
value_contains: lattice_checking
```
@@ -483,9 +483,9 @@ prerequisite:
- fact: contraband.ring_exists
confidence: KnowsDetails
- relationship_state: Friendly
subject: kael_davan
subject: {friend_npc_slug}
- known_attributes:
subject: kael_davan
subject: {friend_npc_slug}
key: behavior_flags
value_contains: lattice_checking
```
@@ -539,12 +539,12 @@ The `access` tag on dialogue lines determines who can hear what. Access is deriv
### What this means for THE FRIEND
When Kael transitions from Friendly to PersonOfInterest:
When THE FRIEND (smuggler's) transitions from Friendly to PersonOfInterest:
- `insider` lines disappear. Ring talk stops. Trust-gated confidences lock.
- `peer` lines disappear. Casual warmth dries up. Kael becomes guarded.
- `public` lines remain. Kael still greets the smuggler — but the warmth is gone.
- `peer` lines disappear. Casual warmth dries up. THE FRIEND becomes guarded.
- `public` lines remain. THE FRIEND still greets the smuggler — but the warmth is gone.
When Sera transitions from Friendly to PersonOfInterest:
When THE FRIEND (detective's) transitions from Friendly to PersonOfInterest:
- `insider` lines disappear. Institutional background sharing stops.
- `peer` lines disappear. Bar conversation becomes stilted.
- `authority` lines unlock for the detective. Pressing questions become available.
@@ -565,18 +565,18 @@ Trust is orthogonal to access. A `peer` + `surface` line is casual coworker talk
### Per-NPC access mapping
How each character relates to key NPCs:
*v0.1 named-NPC access table removed — cited NPCs no longer in v0.2 pipeline (D-122). Author per-district access mapping tables against the active NPC roster. Pattern for the standard cast:*
| NPC | Smuggler Access | Detective Access |
|-----|----------------|------------------|
| Kael (THE FRIEND) | `insider`, `peer` | `public` → `authority` (after flagging) |
| Sera (THE FRIEND) | `public` (Commission, wary) | `peer` → `authority` (post-contradiction) |
| Voss | `insider` (colleague) | `authority` |
| Lera | `insider` (bar regular) | `public` → `peer` (repeat visits) |
| Naia | `peer` (through Kael) | `public` → `peer` (through Sera) |
| Torek | `insider` or `peer` | `public` |
| Maret | `insider` (hub colleague) | `authority` |
| Drin | `insider` (hub colleague) | `authority` |
| NPC Role | Smuggler Access | Detective Access |
|----------|----------------|------------------|
| THE FRIEND (smuggler's) | `insider`, `peer` | `public` → `authority` (after flagging) |
| THE FRIEND (detective's) | `public` (Commission, wary) | `peer` → `authority` (post-contradiction) |
| Supervisor | `insider` (colleague) | `authority` |
| Bar owner | `insider` (bar regular) | `public` → `peer` (repeat visits) |
| MIRROR NPC | `peer` (through FRIEND) | `public` → `peer` (through FRIEND B) |
| Ring-adjacent NPC | `insider` or `peer` | `public` |
| Hub scheduler | `insider` (hub colleague) | `authority` |
| Compromised inspector | `insider` (hub colleague) | `authority` |
---
@@ -594,27 +594,27 @@ A tell observation monologue line should:
```yaml
- id: terminal_m_100
text: "Kael keeps checking his lattice. Waiting for something."
text: "{THE FRIEND} keeps checking their lattice. Waiting for something."
character: smuggler
trigger: observe_anomaly
mood: [concerned]
topic: [colleague]
prerequisite:
relationship_state: Friendly
subject: kael_davan
subject: {friend_npc_slug}
notes: "First tell. Updates behavior_flags: lattice_checking. Smuggler notices but doesn't flag yet."
```
```yaml
- id: terminal_m_101
text: "Dock worker Davan — lattice activity spiked. Three pings in two minutes. Expecting a message? Or checking for surveillance?"
text: "Dock worker {Surname} — lattice activity spiked. Three pings in two minutes. Expecting a message? Or checking for surveillance?"
character: detective
trigger: observe_anomaly
mood: [analytical]
topic: [investigation]
prerequisite:
relationship_state: Known
subject: kael_davan
subject: {friend_npc_slug}
notes: "Same tell, different read. Updates behavior_flags: lattice_checking."
```
@@ -626,7 +626,7 @@ Tells accumulate. Write them as a sequence, each gated on increasing knowledge:
```yaml
prerequisite:
relationship_state: Friendly
subject: kael_davan
subject: {friend_npc_slug}
# No behavior_flags gate — this IS the first observation
```
@@ -634,7 +634,7 @@ prerequisite:
```yaml
prerequisite:
known_attributes:
subject: kael_davan
subject: {friend_npc_slug}
key: behavior_flags
value_contains: lattice_checking
# Requires tell 1 to have fired and set the attribute
@@ -645,11 +645,11 @@ prerequisite:
prerequisite:
all:
- known_attributes:
subject: kael_davan
subject: {friend_npc_slug}
key: behavior_flags
value_contains: lattice_checking
- known_attributes:
subject: kael_davan
subject: {friend_npc_slug}
key: behavior_flags
value_contains: evasive
```
@@ -668,23 +668,25 @@ Each tell should feel like a natural observation, not a checklist. The player do
### THE FRIEND tell arcs
**Kael (smuggler observes):**
*Tell arcs are authored per district against the active NPC roster — v0.1 named examples removed (D-122). The pattern structure:*
**THE FRIEND A (smuggler observes):**
| Phase | Tell | Behavior flag | Line tone |
|-------|------|---------------|-----------|
| First crack | Increased lattice checking | `lattice_checking` | Concern: "Kael's distracted today." |
| Pattern | Shortened conversations, evasive | `distracted,evasive` | Worry: "Kael's been quiet lately." |
| First crack | Increased lattice checking | `lattice_checking` | Concern: "Distracted today." |
| Pattern | Shortened conversations, evasive | `distracted,evasive` | Worry: "Been quiet lately." |
| Contradiction | Unauthorized spatial presence | `contradiction_flagged: meeting_unknown_contact` | Alarm: "That wasn't anyone from our rotation." |
| Confirmation | Looks left when answering | `tell_observed: looks_left_when_lying` | Hurt: "He always looks left when he's making something up." |
| Confirmation | Personal tell fires under pressure | `tell_observed: {specific_tell}` | Hurt: "That tell. I know that tell. They're lying to me." |
**Sera (detective observes):**
**THE FRIEND B (detective observes):**
| Phase | Tell | Behavior flag | Line tone |
|-------|------|---------------|-----------|
| First departure | Leaves when Torek arrives (once) | `avoidance_pattern` (begins) | Barely noticed: "Sera headed out. Long day." |
| Second departure | Different excuse, same trigger | `avoidance_pattern` (accumulating) | Noted: "Sera left again. She's been tired lately." |
| First departure | Leaves when ring-adjacent NPC arrives (once) | `avoidance_pattern` (begins) | Barely noticed: "Headed out. Long day." |
| Second departure | Different excuse, same trigger | `avoidance_pattern` (accumulating) | Noted: "Left again. Tired lately." |
| Third departure | Pattern confirmed | `contradiction_flagged: avoidance_inconsistency` | Analytical: "Three times. Three excuses. That's data." |
| Deflection | Controlled redirect when asked | `tell_observed: controlled_deflection` | Conflicted: "She's not lying. But she's not telling me everything." |
| Deflection | Controlled redirect when asked | `tell_observed: controlled_deflection` | Conflicted: "Not lying. But not telling me everything." |
---
@@ -722,17 +724,17 @@ Monologue pools are separate (D-032). But dialogue is shared — the NPC says th
### Dual-lens patterns
**Innocuous surface / operational subtext:**
> "Voss adjusted the night shift again. Two workers short."
> "{Supervisor} adjusted the night shift again. Two workers short."
- Smuggler: coverage gap for tonight's run
- Detective: scheduling irregularity worth tracking
**Social warmth / threat assessment:**
> "Sera left early. Headache, she said."
- Detective: pattern forming — third time when Torek's here
> "{THE FRIEND} left early. Headache, they said."
- Detective: pattern forming — third time when {NPC} is here
- Smuggler: Commission person leaving, less oversight
**Emotional resonance / clinical data:**
> "Kael's been quiet lately. Not like him."
> "{THE FRIEND}'s been quiet lately. Not like them."
- Smuggler: concern for a friend
- Detective: behavioral change in a subject
@@ -752,555 +754,32 @@ Monologue pools are separate (D-032). But dialogue is shared — the NPC says th
## Concrete Examples: Full Tagged Pools
Three pools, one per v0.1 social site. Each shows file structure, progression through THE FRIEND arc, and full tag usage.
*v0.1 named-NPC pool examples removed — cited NPCs no longer in v0.2 pipeline (D-122). Author per-district pools against the active NPC roster using the tag schema and trigger types documented above.*
### The Terminal (Logistics Hub) — Smuggler Monologue
**Structure reference (three pools per district):**
```yaml
# File: content/terminal/monologue-smuggler.yaml
# Location: The Terminal (Logistics Hub)
# Character: Smuggler
lines:
# --- ARRIVAL ---
- id: terminal_m_001
character: smuggler
trigger: enter_location
prerequisite: null
text: "Morning shift. Recycled air and cargo lubricant. Home sweet home."
mood: [comfortable]
topic: [routine]
situation: [arrival, shift_start]
access: [insider]
trust: surface
tags: [baseline]
- id: terminal_m_002
character: smuggler
trigger: enter_location
prerequisite:
fact: contraband.ring_exists
confidence: KnowsDetails
text: "Shift transition in thirty minutes. If Voss kept the schedule thin, the route's clear."
mood: [analytical]
topic: [cargo]
situation: [shift_transition]
access: [insider]
trust: real
tags: [ring, operational]
# --- KAEL: THE FRIEND ARC ---
# Phase 1: Comfort
- id: terminal_m_010
character: smuggler
trigger: observe_npc
prerequisite:
relationship_state: Friendly
subject: kael_davan
text: "Kael's already at the dock. Good. The day's better when he's on shift."
mood: [fond]
topic: [colleague]
situation: [shift_start]
access: [insider, peer]
trust: surface
tags: [kael, baseline, pre_contradiction]
notes: "Phase 1 warmth. Establishes the bond before it gets tested."
# Phase 2: First crack
- id: terminal_m_011
character: smuggler
trigger: observe_anomaly
prerequisite:
all:
- relationship_state: Friendly
subject: kael_davan
- known_attributes:
subject: kael_davan
key: behavior_flags
value_contains: lattice_checking
text: "Kael keeps checking his lattice. Waiting for a message? Not like him to be jumpy."
mood: [concerned]
topic: [colleague]
situation: [routine]
access: [insider]
trust: real
tags: [kael, tell, first_crack]
notes: "Phase 2. Smuggler notices, doesn't flag it. Updates behavior_flags."
- id: terminal_m_012
character: smuggler
trigger: post_conversation
prerequisite:
known_attributes:
subject: kael_davan
key: behavior_flags
value_contains: evasive
text: "Kael cut lunch short again. 'Things to take care of.' Since when does Kael have things to take care of that don't involve me?"
mood: [worried]
topic: [colleague]
situation: [routine]
access: [insider]
trust: real
tags: [kael, tell, pattern_forming]
# Phase 3: The contradiction
- id: terminal_m_013
character: smuggler
trigger: witness_interaction
prerequisite:
relationship_state: Friendly
subject: kael_davan
text: "Kael? By the service hatch? And that's — I don't know them. Not crew, not ring. Who is that?"
mood: [concerned]
topic: [colleague]
situation: [observation]
access: [insider]
trust: real
tags: [kael, the_friend, contradiction, critical_moment]
notes: >
THE CONTRADICTION. Kael in restricted area with unknown contact.
Sets contradiction_flagged: meeting_unknown_contact.
RelationshipState: Friendly -> PersonOfInterest. Green -> amber.
# Phase 4: Confrontation aftermath
- id: terminal_m_014
character: smuggler
trigger: post_conversation
prerequisite:
all:
- relationship_state: PersonOfInterest
subject: kael_davan
- known_attributes:
subject: kael_davan
key: tell_observed
value: looks_left_when_lying
text: "He looked left. He always looks left when he's making something up. Two years I've known that tell. Kael is lying to me."
mood: [conflicted]
topic: [trust]
situation: [confrontation]
access: [insider]
trust: real
tags: [kael, the_friend, tell_confirmation]
notes: "The tell pays off. Established early in casual observation, confirmed under pressure."
# Phase 5: Contaminated trust
- id: terminal_m_015
character: smuggler
trigger: observe_npc
prerequisite:
all:
- relationship_state: PersonOfInterest
subject: kael_davan
- known_attributes:
subject: kael_davan
key: contradiction_flagged
value: meeting_unknown_contact
text: "Same old Kael. Same jokes, same routine. ...What are you not telling me?"
mood: [conflicted]
topic: [colleague]
situation: [routine]
access: [insider]
trust: real
tags: [kael, the_friend, contaminated_trust]
notes: "Phase 5. Warmth and doubt simultaneously. Every smile now has a question mark."
# --- OPERATIONAL ---
- id: terminal_m_020
character: smuggler
trigger: observe_anomaly
prerequisite:
fact: investigation.cargo_anomaly
confidence: Suspects
text: "That container's been in temp since yesterday. Someone forgot to process it, or someone's stalling."
mood: [concerned]
topic: [cargo]
situation: [routine]
access: [insider]
trust: real
tags: [investigation, cargo]
- id: terminal_m_021
character: smuggler
trigger: time_idle
prerequisite:
fact: world.shift_schedule
confidence: KnowsDetails
text: "Thirteen-forty. Transition window opens in fifty minutes. After that, twenty minutes of reduced oversight."
mood: [analytical]
topic: [routine]
situation: [routine]
access: [insider]
trust: real
tags: [ring, timing, operational]
```
content/{district}/
{terminal-slug}/
monologue-smuggler.yaml # Smuggler's FRIEND arc + operational lines
monologue-detective.yaml # Detective's investigation lines
dialogue.yaml # Shared NPC dialogue (access-tier filtered at runtime)
{bar-slug}/
monologue-smuggler.yaml
monologue-detective.yaml
dialogue.yaml
{corridor-slug}/
monologue-smuggler.yaml # Route operational + THE CONTRADICTION scene
monologue-detective.yaml
dialogue.yaml
```
---
### The Last Shift (Bar) — Detective Monologue
```yaml
# File: content/bar/monologue-detective.yaml
# Location: The Last Shift (Bar)
# Character: Detective
lines:
# --- ARRIVAL ---
- id: bar_m_001
character: detective
trigger: enter_location
prerequisite: null
text: "The Last Shift. Grain spirit and low conversation. Only place in this district that doesn't smell like freight lubricant."
mood: [comfortable]
topic: [routine]
situation: [arrival, bar_evening]
access: [public]
trust: surface
tags: [baseline, atmosphere]
- id: bar_m_002
character: detective
trigger: return_visit
prerequisite:
fact: progress.initial_suspicion
confidence: KnowsOf
text: "Back again. People talk here. And people who don't talk are talking too — just not out loud."
mood: [analytical]
topic: [investigation]
situation: [bar_evening]
access: [authority]
trust: real
tags: [investigation, atmosphere]
# --- SERA: THE FRIEND ARC ---
# Phase 1: Trust
- id: bar_m_010
character: detective
trigger: observe_npc
prerequisite:
relationship_state: Friendly
subject: sera_venn
text: "Sera's in her usual booth. Good. One familiar face in a district that doesn't want me here."
mood: [relieved]
topic: [colleague]
situation: [bar_evening]
access: [peer]
trust: surface
tags: [sera, baseline, trust]
notes: "Phase 1. Sera is the detective's anchor. Establish this warmth — it has to hurt later."
# Phase 2: Background
- id: bar_m_011
character: detective
trigger: post_conversation
prerequisite:
relationship_state: Friendly
subject: sera_venn
text: "Sera's connected here. Knows the regulars, knows the routines. And she's got diagnostic access. Useful."
mood: [comfortable]
topic: [colleague]
situation: [social]
access: [peer]
trust: surface
tags: [sera, background, pre_contradiction]
notes: "Phase 2. The detective notes Sera's access level without realizing it's the source of the conflict."
# Phase 3: Pattern — first departure
- id: bar_m_012
character: detective
trigger: witness_interaction
prerequisite:
relationship_state: Friendly
subject: sera_venn
text: "Sera headed out. Early shift tomorrow, she said. Fair enough."
mood: [comfortable]
topic: [colleague]
situation: [bar_evening]
access: [peer]
trust: surface
tags: [sera, avoidance, departure_1]
notes: "First Torek departure. Detective barely notices."
# Phase 3: Pattern — second departure
- id: bar_m_013
character: detective
trigger: witness_interaction
prerequisite:
known_attributes:
subject: sera_venn
key: behavior_flags
value_contains: avoidance_pattern
text: "Sera left again. Headache. Right after Torek walked in. ...Noted."
mood: [suspicious]
topic: [colleague]
situation: [bar_evening]
access: [peer]
trust: real
tags: [sera, avoidance, departure_2]
notes: "Second departure. Detective notes it. Not yet a pattern."
# Phase 3: Pattern — the third (contradiction)
- id: bar_m_014
character: detective
trigger: witness_interaction
prerequisite:
known_attributes:
subject: sera_venn
key: contradiction_flagged
value: avoidance_inconsistency
text: "That's the third time. Early shift, headache, kiosk check. Three excuses, one result. Sera leaves when Torek arrives. That's not coincidence."
mood: [analytical]
topic: [colleague]
situation: [bar_evening, observation]
access: [peer]
trust: real
tags: [sera, the_friend, contradiction_discovery]
notes: >
THE CONTRADICTION. Three data points make a conclusion.
Sets contradiction_flagged: avoidance_inconsistency.
RelationshipState: Friendly -> PersonOfInterest. Green -> amber.
Different from Kael's — cumulative, not sudden.
# Phase 4: The question asked
- id: bar_m_015
character: detective
trigger: post_conversation
prerequisite:
all:
- relationship_state: PersonOfInterest
subject: sera_venn
- known_attributes:
subject: sera_venn
key: tell_observed
value: controlled_deflection,topic_change
text: "She deflected. Smooth — 'he's just loud.' Technically true. But her shoulders shifted. Sera, what do you know about Torek?"
mood: [conflicted]
topic: [trust]
situation: [confrontation]
access: [authority]
trust: real
tags: [sera, the_friend, post_confrontation]
notes: "Phase 4. The detective hears the non-lie. Deflection IS the tell."
# Phase 5: Contaminated trust
- id: bar_m_016
character: detective
trigger: return_visit
prerequisite:
relationship_state: PersonOfInterest
subject: sera_venn
text: "Same booth. Same warm smile. Same offer to buy me a drink. ...Everything except whatever she's not saying."
mood: [conflicted]
topic: [trust]
situation: [bar_evening]
access: [authority]
trust: real
tags: [sera, the_friend, contaminated_trust]
notes: "Phase 5. Every kindness now has a question mark. The past is retroactively contaminated."
# --- TOREK ---
- id: bar_m_020
character: detective
trigger: observe_npc
prerequisite:
relationship_state: Unknown
subject: torek_lintar
text: "Loud one at the bar. Buying rounds he probably can't afford. Worth watching."
mood: [analytical]
topic: [money]
situation: [bar_evening]
access: [public]
trust: surface
tags: [torek, first_observation, spending]
# --- ATMOSPHERE ---
- id: bar_m_030
character: detective
trigger: time_idle
prerequisite:
fact: progress.initial_suspicion
confidence: KnowsOf
text: "Everyone's friendly enough. Drinks, jokes, the usual complaints about shift schedules. But friendly and honest aren't the same thing."
mood: [suspicious]
topic: [routine]
situation: [bar_evening]
access: [public]
trust: real
tags: [atmosphere, investigation, early_game]
```
---
### Corridor B-7 — Smuggler Monologue
```yaml
# File: content/corridor/monologue-smuggler.yaml
# Location: Corridor B-7 (Maintenance / Smuggling Route)
# Character: Smuggler
lines:
# --- ENTRY ---
- id: corridor_m_001
character: smuggler
trigger: enter_location
prerequisite:
fact: location.corridor_b7_restricted
confidence: KnowsDetails
text: "B-7. Old prefab, minimal coverage. The route works because nobody updated the surveillance map."
mood: [analytical]
topic: [routine]
situation: [night_shift]
access: [insider]
trust: real
tags: [ring, operational, spatial]
- id: corridor_m_002
character: smuggler
trigger: enter_location
prerequisite:
fact: location.corridor_b7_restricted
confidence: Suspects
text: "Maintenance corridor. Quiet. Shouldn't be this quiet during shift change."
mood: [suspicious]
topic: [routine]
situation: [shift_transition]
access: [public]
trust: surface
tags: [exploration, spatial]
notes: "Lower confidence — smuggler who doesn't know B-7's significance yet."
# --- ENVIRONMENTAL ---
- id: corridor_m_003
character: smuggler
trigger: hear_sound
prerequisite:
fact: location.corridor_b7_restricted
confidence: KnowsOf
text: "Footsteps. Wrong cadence for maintenance crew. Someone's being careful."
mood: [concerned]
topic: [danger]
situation: [night_shift]
access: [insider]
trust: real
tags: [tension, spatial_awareness]
- id: corridor_m_004
character: smuggler
trigger: time_idle
prerequisite:
fact: location.surveillance_gaps
confidence: KnowsDetails
text: "No Meridian signal down here. No eyes, no ears. Whatever happens in B-7 stays in B-7."
mood: [relieved]
topic: [routine]
situation: [alone]
access: [insider]
trust: real
tags: [ring, surveillance, operational]
# --- THE CONTRADICTION ---
- id: corridor_m_010
character: smuggler
trigger: witness_interaction
prerequisite:
relationship_state: Friendly
subject: kael_davan
text: "Kael? Down here? And that's — I don't know them. Not crew, not ring. Who the hell is that?"
mood: [concerned]
topic: [colleague]
situation: [observation]
access: [insider]
trust: real
tags: [the_friend, contradiction, kael, critical_moment]
notes: >
THE CONTRADICTION. The moment the smuggler's world shifts.
Kael in a restricted corridor with an unknown contact.
Sets contradiction_flagged: meeting_unknown_contact.
RelationshipState: Friendly -> PersonOfInterest.
Color: green -> amber. This moment is the emotional core of the arc.
- id: corridor_m_011
character: smuggler
trigger: post_conversation
prerequisite:
all:
- relationship_state: PersonOfInterest
subject: kael_davan
- known_attributes:
subject: kael_davan
key: tell_observed
value: looks_left_when_lying
text: "He looked left. Always looks left when he's making something up. Two years, Kael. I know your tells."
mood: [conflicted]
topic: [trust]
situation: [confrontation]
access: [insider]
trust: real
tags: [the_friend, kael, tell_confirmation]
notes: "Tell payoff. Established early in casual dialogue, confirmed here under pressure."
# --- EVIDENCE ---
- id: corridor_m_020
character: smuggler
trigger: discover_evidence
prerequisite:
fact: location.dead_drop_location
confidence: Direct
text: "Locker 47. Registered to someone who transferred out eighteen months ago. Convenient."
mood: [analytical]
topic: [cargo]
situation: [investigation]
access: [insider]
trust: real
tags: [dead_drop, evidence]
- id: corridor_m_021
character: smuggler
trigger: observe_anomaly
prerequisite:
fact: location.smuggling_route
confidence: KnowsDetails
text: "Fresh marks on the service hatch. Kosse's been through here. Right on schedule."
mood: [comfortable]
topic: [cargo]
situation: [night_shift]
access: [insider]
trust: real
tags: [ring, route, operational]
# --- RETURN ---
- id: corridor_m_030
character: smuggler
trigger: return_visit
prerequisite:
all:
- fact: location.corridor_b7_restricted
confidence: KnowsDetails
- relationship_state: PersonOfInterest
subject: kael_davan
text: "B-7 again. Last time I was here, Kael was talking to someone he shouldn't have been. The corridor feels different now."
mood: [suspicious]
topic: [colleague]
situation: [alone]
access: [insider]
trust: real
tags: [kael, the_friend, post_contradiction, return]
notes: "The space is contaminated by what happened here. Location memory."
```
**Required content per location per character:**
- Arrival / enter_location (2-3 lines, baseline + investigation variant)
- THE FRIEND arc phases 1-5 (smuggler: Phase 1-5 for FRIEND A; detective: Phase 1-5 for FRIEND B)
- Operational / investigative observations (3-5 lines per location)
- Return visit variants (1-2 lines per location)
- Atmospheric time_idle lines (1-2 per location)
---
wiki/authoring/monologue-voice-guide.md
+50 -50
View File
@@ -33,11 +33,11 @@ The voice-patterns.md spec describes the mechanics of each character's voice. Th
The smuggler's voice is not the result of low intelligence or limited vocabulary. It's the result of two years of professional survival in a context where abstract thinking is dangerous.
When you're running contraband through a logistics hub, you can't afford to think in categories — you think in specifics. Not "this situation is getting risky" but "Voss changed the rotation and Kael's not answering his lattice." Abstract framing makes patterns invisible. Concrete framing catches the deviation.
When you're running contraband through a logistics hub, you can't afford to think in categories — you think in specifics. Not "this situation is getting risky" but "{Supervisor} changed the rotation and {THE FRIEND}'s not answering their lattice." Abstract framing makes patterns invisible. Concrete framing catches the deviation.
The smuggler's internal voice is trained, not natural. She developed it. It served her. The short sentences and fragments aren't lack of complexity — they're the mental habit of someone who learned to think in real-time decision points. "Kael's late. Wrong. Move." Three thoughts, three beats, three potential action triggers. Abstract cognition is a liability she's edited out.
The smuggler's internal voice is trained, not natural. She developed it. It served her. The short sentences and fragments aren't lack of complexity — they're the mental habit of someone who learned to think in real-time decision points. "{THE FRIEND}'s late. Wrong. Move." Three thoughts, three beats, three potential action triggers. Abstract cognition is a liability she's edited out.
**The emotional truth beneath the voice:** She cares about people first. Operations second. Institutions never. The concrete voice maps onto this: she sees people, not systems. She notices Kael is distracted before she notices the manifest is wrong. The world is a network of relationships, and her monologue is live monitoring of that network.
**The emotional truth beneath the voice:** She cares about people first. Operations second. Institutions never. The concrete voice maps onto this: she sees people, not systems. She notices {THE FRIEND} is distracted before she notices the manifest is wrong. The world is a network of relationships, and her monologue is live monitoring of that network.
**What this means for trait and mood modifiers:** When trait or mood modifiers inflect the smuggler's voice, they do so within this framework. A Bold smuggler is still concrete-first — she just acts on partial information faster. An Anxious smuggler is still relational — she just cycles through the network faster, checking and rechecking. The base is immovable. The modifiers inflect it.
@@ -45,11 +45,11 @@ The smuggler's internal voice is trained, not natural. She developed it. It serv
The detective's voice is institutional training running as an operating system. He was taught to externalise his cognition — to turn observations into filed reports, to name patterns as data, to treat emotional reactions as information to be processed rather than feelings to be felt.
This is not coldness. It's self-protection. Investigators who let themselves feel first make bad decisions. The detective learned that lesson somewhere — we don't know where, but it's in the bone. The analytical frame is a tool he uses so well he's forgotten it's a tool. Except when Sera makes him forget.
This is not coldness. It's self-protection. Investigators who let themselves feel first make bad decisions. The detective learned that lesson somewhere — we don't know where, but it's in the bone. The analytical frame is a tool he uses so well he's forgotten it's a tool. Except when THE FRIEND makes him forget.
The longer sentences and complete syntactic structures aren't pretension. They're habits of evidence: a complete sentence has a subject, verb, and object, which means it has an agent, an action, and a consequence. The detective's brain naturally produces complete sentences because incomplete sentences don't file well.
**The emotional truth beneath the voice:** He cares about doing the work correctly. Not because he's a rule-follower (he'd bend a rule if the evidence demanded it), but because he believes the correct process produces the correct result. When Sera introduces doubt into that belief, the whole framework shudders. His fear isn't being wrong about a fact — it's discovering that correct process produced an unjust outcome, and having no language for what comes next.
**The emotional truth beneath the voice:** He cares about doing the work correctly. Not because he's a rule-follower (he'd bend a rule if the evidence demanded it), but because he believes the correct process produces the correct result. When THE FRIEND introduces doubt into that belief, the whole framework shudders. His fear isn't being wrong about a fact — it's discovering that correct process produced an unjust outcome, and having no language for what comes next.
**What this means for trait and mood modifiers:** Detective trait modifiers inflate or compress the analytical frame. A Compassionate detective lets the personal break through the professional more easily. A Ruthless detective turns the analytical frame into a weapon — identifies leverage faster, doesn't dwell on moral weight. Mood modifiers thin or thicken the professional veneer. The base is the analyst. The modifiers determine how much of the person shows through.
@@ -70,7 +70,7 @@ D-024 defines 10 personality traits across 5 opposing pairs. These modify the *d
**Cautious — transformation logic:**
A Cautious character qualifies her observations before she acts on them. She notices things in the same order as a neutral character, but she checks her own conclusions. She hedges internally. She is not less intelligent — she is more aware that she might be wrong.
- Declarations become conditionals: "That's Kael's route" → "That looks like Kael's route"
- Declarations become conditionals: "That's {THE FRIEND}'s route" → "That looks like {THE FRIEND}'s route"
- Observations become questions: "Something's off" → "Something might be off"
- Concern arrives earlier and stays longer (more re-checking)
- The voice is slower, more tentative
@@ -83,7 +83,7 @@ A Cautious character qualifies her observations before she acts on them. She not
A Bold character acts on partial information. She names the conclusion before she has the evidence. She's often right — bold cognition built on competence. But she's also capable of committing to a wrong read and holding it too long.
- Questions become declarations: "Something might be off" → "Something's off"
- Hedges disappear: "That looks like Kael's route" → "That's Kael's route"
- Hedges disappear: "That looks like {THE FRIEND}'s route" → "That's {THE FRIEND}'s route"
- Concern arrives fast and crystallizes immediately
- The voice is faster, more assertive, shorter latency between observation and conclusion
@@ -102,7 +102,7 @@ A Bold character acts on partial information. She names the conclusion before sh
**Honest — transformation logic:**
An Honest character's monologue is self-correcting. She catches her own spin and revises it. She doesn't lie to herself to feel better. This makes her monologue have a characteristic pattern: initial reaction, then correction.
- Self-correction appears: "Kael's fine. — No. He's not fine."
- Self-correction appears: "{THE FRIEND}'s fine. — No. They're not fine."
- Less motivated reasoning: she acknowledges evidence she doesn't want to see
- The voice is slightly more uncomfortable with its own conclusions
- She doesn't minimize things that scare her
@@ -110,7 +110,7 @@ An Honest character's monologue is self-correcting. She catches her own spin and
**Deceptive — transformation logic:**
A Deceptive character's internal voice shows motivated reasoning. She rationalizes what she wants to be true. She notices threatening evidence and then explains it away. This is not dishonest *about others* — it's dishonest with herself.
- Conclusions favor the preferred reading: "Kael's meeting someone I don't know. Probably work."
- Conclusions favor the preferred reading: "{THE FRIEND}'s meeting someone I don't know. Probably work."
- Dismissal appears quickly after observation: "Could be nothing. Probably is nothing."
- She notices the tell and then chooses not to follow it
- The voice has a self-soothing quality, particularly under threat
@@ -131,22 +131,22 @@ A Deceptive character's internal voice shows motivated reasoning. She rationaliz
A Compassionate character's first read of a situation is through the lens of what it means for people she cares about. She identifies the person most likely to be hurt before she identifies the operational implication.
- People-first sequencing: observation of person → emotional assessment → operational conclusion
- Concern is named: "Naia looks exhausted. Something's wrong at home."
- She personalizes abstract threats: not "ring security is compromised" but "Kael could get caught"
- Concern is named: "{Colleague} looks exhausted. Something's wrong at home."
- She personalizes abstract threats: not "ring security is compromised" but "{THE FRIEND} could get caught"
- Moral weight is felt quickly and stays present
**Ruthless — transformation logic:**
A Ruthless character assesses utility before empathy. She notices a threat and immediately calculates how to neutralize it, including through people. This is not cruelty — it's a habit of assessment that puts operational outcome first.
- Utility assessment appears early: "Kael's behavior is risky. If he cracks, he takes the route with him."
- Moral weight is noted and set aside: "He might not deserve this. Doesn't matter right now."
- People are resources first: "Maret's nervous. That's usable."
- Utility assessment appears early: "{THE FRIEND}'s behavior is risky. If they crack, they take the route with them."
- Moral weight is noted and set aside: "They might not deserve this. Doesn't matter right now."
- People are resources first: "{NPC}'s nervous. That's usable."
**How this inflects each character:**
- *Compassionate smuggler:* Most Naia-and-Kael-focused. Her FRIEND arc lines emphasize relationship cost over operational cost. She confronts Kael later because she keeps hoping he'll explain.
- *Ruthless smuggler:* Calculates exposure fast. Cuts contact with Kael earlier once he's flagged. Sees Naia's distress as a data point about Kael's reliability, not as a human problem.
- *Compassionate detective:* The Sera question hits harder and sooner. He identifies the personal cost before the institutional obligation.
- *Ruthless detective:* Uses Sera's knowledge instrumentally. The friendship is real, but usable.
- *Compassionate smuggler:* Most FRIEND-focused. Her FRIEND arc lines emphasize relationship cost over operational cost. She confronts THE FRIEND later because she keeps hoping they'll explain.
- *Ruthless smuggler:* Calculates exposure fast. Cuts contact with THE FRIEND earlier once they're flagged. Sees a colleague's distress as a data point about THE FRIEND's reliability, not as a human problem.
- *Compassionate detective:* The FRIEND question hits harder and sooner. He identifies the personal cost before the institutional obligation.
- *Ruthless detective:* Uses THE FRIEND's knowledge instrumentally. The friendship is real, but usable.
**Mellanie — write 2 example rewrite pairs per character: the same FRIEND-arc moment in Compassionate vs. Ruthless voice.**
@@ -159,7 +159,7 @@ A Ruthless character assesses utility before empathy. She notices a threat and i
**Curious — transformation logic:**
A Curious character asks more internal questions, including questions she can't answer. She sits with open threads longer. She generates hypotheses and lets them hang.
- Questions multiply before resolving: "What was Kael doing there? Who was that? Is the route changing? Is Nils moving the window?"
- Questions multiply before resolving: "What was {THE FRIEND} doing there? Who was that? Is the route changing? Is {Supervisor} moving the window?"
- The voice has more speculative energy — she follows the thread
- She notices more at the margins: background details, things that don't connect yet
- Open-endedness is comfortable
@@ -183,14 +183,14 @@ An Incurious character categorizes and moves on. She notices, files, and redirec
**Social — transformation logic:**
A Social character's monologue is populated. She mentions people when she could just mention actions. She frames operations through the network.
- People are named when not necessary: "The route's clear. Kael cleared it."
- She reads absence: "Where's Renn today? He's always here at this hour."
- Mood-reads appear: "Voss is different today. Tired, or something else."
- People are named when not necessary: "The route's clear. {THE FRIEND} cleared it."
- She reads absence: "Where's {NPC} today? Always here at this hour."
- Mood-reads appear: "{Supervisor}'s different today. Tired, or something else."
**Reclusive — transformation logic:**
A Reclusive character's monologue is depopulated. People appear when they're directly relevant. The environment and operation carry more weight.
- Operations are mentioned without actors: "Route's clear." Not "Kael cleared the route."
- Operations are mentioned without actors: "Route's clear." Not "{THE FRIEND} cleared the route."
- Absence of people is comfortable: she doesn't notice it
- The environment gets more attention: she describes the space, the sounds, the texture
@@ -200,9 +200,9 @@ A Reclusive character's monologue is depopulated. People appear when they're dir
## Chapter 3: Background-Dependent Phrasing
Character background (selected at game start) shapes three things in monologue: the idioms and references the character uses, the assumptions they make about institutions and authority, and how they frame the moral dimension of what's happening in Sova Transit District.
Character background (selected at game start) shapes three things in monologue: the idioms and references the character uses, the assumptions they make about institutions and authority, and how they frame the moral dimension of what's happening in the district.
Three backgrounds for v0.1:
Three backgrounds:
| Background | Core assumption | Relationship to institutions |
|-----------|----------------|------------------------------|
@@ -219,11 +219,11 @@ Three backgrounds for v0.1:
**How it inflects the smuggler:**
The ring's activities are, to a Guardian-background smuggler, a natural extension of the protective network logic she already believes in. She doesn't see herself as a criminal — she sees herself as part of a system that serves people the regulated system won't. This changes how she frames the ring's cargo: medical lattice components aren't contraband, they're access. The Commission's regulation is a monopoly problem, not a safety protection.
Her monologue references network solidarity: "We look after our own" is a value, not just a statement. When the network is threatened (Kael's situation), her response is to protect, not to report. The Commission is not a solution to her problems — it's the problem with different uniforms.
Her monologue references network solidarity: "We look after our own" is a value, not just a statement. When the network is threatened ({THE FRIEND}'s situation), her response is to protect, not to report. The Commission is not a solution to her problems — it's the problem with different uniforms.
Idiom signals: phrases that imply collective or mutual protection ("we look after our own," "this keeps us safe," "not their business"), references to surveillance as adversarial ("they're watching the corridors closer"), reflexive Commission-skepticism ("another Commission inspection" carries more weight, more contempt).
**Mellanie — write 2 examples:** (a) Guardian-background smuggler entering The Terminal on a normal morning; (b) Guardian-background smuggler seeing the detective for the first time.
**Mellanie — write 2 examples:** (a) Guardian-background smuggler entering the logistics hub on a normal morning; (b) Guardian-background smuggler seeing the detective for the first time.
**How it inflects the detective:**
A Guardian-background detective is in a structurally uncomfortable position: she believes in a community's right to self-determination but is employed by the institution that overrides it. She may have unexamined tension between her institutional role and her network values. Her internal voice sometimes catches itself applying institutional logic and stops — not from disloyalty, but from the habit of checking whether what she's doing serves people or just process.
@@ -232,7 +232,7 @@ This creates a more nuanced reading of the ring: she notices earlier that it isn
Idiom signals: slight Commission-skepticism applied to her own role, instinct toward community protection over prosecution, "who does this actually hurt?" appears as an internal question earlier in the arc.
**Mellanie — write 2 examples:** (a) Guardian-background detective walking through The Terminal for the first time; (b) Guardian-background detective after a confrontation with Voss that didn't land.
**Mellanie — write 2 examples:** (a) Guardian-background detective walking through the logistics hub for the first time; (b) Guardian-background detective after a confrontation with {Supervisor} that didn't land.
---
@@ -241,13 +241,13 @@ Idiom signals: slight Commission-skepticism applied to her own role, instinct to
**Narrative framing:** Senator background means exposure to Concord Assembly political culture — either through family, prior work, or a posting in an administrative center. This character thinks in terms of leverage, political capital, and institutional process as tools to be used. They believe in systems (not naively — they've seen how they work), they communicate strategically, and they think about consequences in terms of how they're recorded and remembered.
**How it inflects the smuggler:**
A Senator-background smuggler is an unusual animal. She ended up on Sova with this background for reasons that suggest a fall — political family, bad posting, something that deposited her in freight work. She still thinks in political terms. The ring is, to her, a structure with power dynamics that can be managed. She assesses Nils as a faction leader, Voss as a compromisable middle manager, Kael as an uncertain ally. She has more framework for navigating institutional pressure than the default smuggler.
A Senator-background smuggler is an unusual animal. She ended up on Sova with this background for reasons that suggest a fall — political family, bad posting, something that deposited her in freight work. She still thinks in political terms. The ring is, to her, a structure with power dynamics that can be managed. She assesses the ring's leadership as a faction, {Supervisor} as a compromisable middle manager, {THE FRIEND} as an uncertain ally. She has more framework for navigating institutional pressure than the default smuggler.
Her monologue carries strategic calculation that the default smuggler doesn't have: "If Nils moves against us, who has leverage over Nils?" She names power structures. She's more comfortable with authority figures because she spent time being one or adjacent to one.
Her monologue carries strategic calculation that the default smuggler doesn't have: "If {leadership} moves against us, who has leverage over them?" She names power structures. She's more comfortable with authority figures because she spent time being one or adjacent to one.
Idiom signals: political vocabulary deployed in operational context ("who holds the leverage here," "what does this cost us politically," "that's a favor spent"), more awareness of chain of command, comfort with complexity and multiple-move thinking.
**Mellanie — write 2 examples:** (a) Senator-background smuggler reading a tense moment between Voss and Nils; (b) Senator-background smuggler deciding whether to warn Kael about the detective.
**Mellanie — write 2 examples:** (a) Senator-background smuggler reading a tense moment between {Supervisor} and ring leadership; (b) Senator-background smuggler deciding whether to warn {THE FRIEND} about the detective.
**How it inflects the detective:**
A Senator-background detective is most at home in the Commission's formal institutional structure. He knows how to work the process because he's seen political process at close range. He's less likely to be frustrated by bureaucratic obstacles and more likely to use them as tools. He's also more aware of how investigations can be used politically — and more careful to distinguish between evidence that serves justice and evidence that serves someone's career.
@@ -256,7 +256,7 @@ This can work two ways: he's more sophisticated about when to file and when not
Idiom signals: references to political process ("that'll go on record," "who is this actually going to serve"), awareness of institutional optics, formal courtesy in internal voice (he holds standards in private that mirror public institutional expectations).
**Mellanie — write 2 examples:** (a) Senator-background detective receiving unhelpful cooperation from Maret (deflection, formal compliance); (b) Senator-background detective realizing Sera has evidence she hasn't reported.
**Mellanie — write 2 examples:** (a) Senator-background detective receiving unhelpful cooperation from an NPC (deflection, formal compliance); (b) Senator-background detective realizing THE FRIEND has evidence they haven't reported.
---
@@ -271,16 +271,16 @@ Her monologue about the ring's cargo is practical, not moral: "Medical component
Idiom signals: shift-economy references ("that's a week's pay gone"), physical work vocabulary, coworker solidarity language that's practical not sentimental ("you cover for your people"), no ideological framing.
**Mellanie — write 2 examples:** (a) Worker-background smuggler after a long shift where nothing went wrong (genuine relief in mundane form); (b) Worker-background smuggler finding out about Kael's corridor meeting.
**Mellanie — write 2 examples:** (a) Worker-background smuggler after a long shift where nothing went wrong (genuine relief in mundane form); (b) Worker-background smuggler finding out about {THE FRIEND}'s unauthorized corridor meeting.
**How it inflects the detective:**
A Worker-background detective is a less common institutional profile — someone who came up from the logistics world, or the adjacent working community of a station, and then entered Commission work. This creates the most dramatic read of the Sova Transit District: he *knows* what this world looks like from inside. The community's distrust of him isn't abstract — he grew up in a community that had this relationship with Commission investigators.
A Worker-background detective is a less common institutional profile — someone who came up from the logistics world, or the adjacent working community of a station, and then entered Commission work. This creates the most dramatic read of the district: he *knows* what this world looks like from inside. The community's distrust of him isn't abstract — he grew up in a community that had this relationship with Commission investigators.
His analytical frame is the same, but its application produces a different emotional texture. He reads Voss not just as a shift supervisor but as someone managing his people in a system that gives them no margin. He reads the ring not just as a crime but as what people do when the legal option doesn't work. He's not excusing it — but he's explaining it to himself in ways a Senator-background detective wouldn't.
His analytical frame is the same, but its application produces a different emotional texture. He reads the shift supervisor not just as an authority figure but as someone managing their people in a system that gives them no margin. He reads the ring not just as a crime but as what people do when the legal option doesn't work. He's not excusing it — but he's explaining it to himself in ways a Senator-background detective wouldn't.
Idiom signals: working vocabulary that leaks through the institutional frame ("another form to fill out" with genuine frustration), more personal reads on community behavior, faster comprehension of coworker loyalty dynamics.
**Mellanie — write 2 examples:** (a) Worker-background detective entering The Terminal and recognizing it as a place he knows in his bones; (b) Worker-background detective having a moment of sympathy for Kael that he then has to file away.
**Mellanie — write 2 examples:** (a) Worker-background detective entering the logistics hub and recognizing it as a place he knows in his bones; (b) Worker-background detective having a moment of sympathy for {THE FRIEND} that he then has to file away.
---
@@ -301,7 +301,7 @@ Each mood bends the character's voice toward a version of itself. The base regis
| `frustrated` | Goes flat. Sarcasm. "Of course." | Sardonic understatement. Cold. |
| `content` | Warms, expands slightly. More humor. | Structured satisfaction. Humor surfaces. |
| `suspicious` | Narrows. More observation of specific people. Hypotheses pile up. | Files faster. More quantification. "Coincidence?" frequency increases. |
| `warm` | More name-drops. Affectionate observations. Longer people-reads. | First-name register expands beyond Sera. More personal disclosure. |
| `warm` | More name-drops. Affectionate observations. Longer people-reads. | First-name register expands beyond THE FRIEND. More personal disclosure. |
| `hostile` | Edges. Fewer words about the hostile object. Watchful. | Clinical distance increases. Dehumanizing label (surname-only). |
| `focused` | Strips down. Only the current task. Environmental and NPC data pruned ruthlessly. | Most structured voice. Near-mechanical. Labels and flags only. |
@@ -328,7 +328,7 @@ Lines tagged `mood: anxious` should feel compressed. Not panicked — the charac
Something isn't working. The block is structural, not threatening.
- *Smuggler:* Flat declarations. Sarcastic understatement. "Of course." / "Great." Dark humor returns — she goes wry under frustration. Names get blamed: "Voss did it again." Swearing surfaces (mild — the character swears, but not obscenely).
- *Smuggler:* Flat declarations. Sarcastic understatement. "Of course." / "Great." Dark humor returns — she goes wry under frustration. Names get blamed: "{Supervisor} did it again." Swearing surfaces (mild — the character swears, but not obscenely).
- *Detective:* Sardonic compression. Dismissive shorthand: "Standard." meaning the opposite. The institutional frame holds but it fits uncomfortably. He doesn't swear; frustration surfaces as brittle patience.
Lines tagged `mood: frustrated` should feel like controlled flat. Both characters have learned not to waste anger — they spend it in specific, pointed ways.
@@ -356,7 +356,7 @@ Lines tagged `mood: suspicious` should feel *directed*. The suspicion has an obj
The character is in a moment of genuine positive connection. This is not `content` (good situation) — this is specifically warm *toward someone*.
- *Smuggler:* More name-drops with positive color. People-reads are generous and long. She notices when someone seems well, not just when they seem off. Humor becomes inclusive rather than dry. She might express something like affection, obliquely.
- *Detective:* First-name register expands beyond Sera — he might first-name someone he normally surnames if the moment calls for it. Personal disclosure is slightly more available. The analytical frame softens: he observes without immediately filing.
- *Detective:* First-name register expands beyond THE FRIEND — he might first-name someone he normally surnames if the moment calls for it. Personal disclosure is slightly more available. The analytical frame softens: he observes without immediately filing.
Lines tagged `mood: warm` are most visible in the detective because they represent a departure from his baseline. For the smuggler, warmth is closer to her baseline; the lines should be a slightly more saturated version of her natural register.
@@ -364,8 +364,8 @@ Lines tagged `mood: warm` are most visible in the detective because they represe
The relationship to the hostile object is adversarial. The character is managing threat.
- *Smuggler:* Less said, more watched. She goes quiet around the hostile object — mentions them tersely, observations are monitoring-reads rather than social-reads. "Nils walked past." Period. No color.
- *Detective:* Dehumanizing label returns even for NPCs who have previously graduated to first-name in his monologue. "Venn, S." instead of "Sera" signals the relationship has turned. Analytical lines about the hostile object are more clinical.
- *Smuggler:* Less said, more watched. She goes quiet around the hostile object — mentions them tersely, observations are monitoring-reads rather than social-reads. "{NPC} walked past." Period. No color.
- *Detective:* Dehumanizing label returns even for NPCs who have previously graduated to first-name in his monologue. "{Surname}, {initial}." instead of first name signals the relationship has turned. Analytical lines about the hostile object are more clinical.
Lines tagged `mood: hostile` should feel like distance enforced deliberately. Neither character becomes cruel — cruelty requires emotional investment. The hostile register is managed withdrawal.
@@ -388,7 +388,7 @@ The mood tags on monologue lines function as selection weights in the engine:
2. The line selection system applies a weight bonus to lines tagged with the matching mood
3. Lines tagged `mood: [neutral]` or untagged are always eligible; lines tagged with specific moods are preferred when the mood matches
**The same base line should NOT be re-authored per mood.** A smuggler entering The Terminal does not need 9 `enter_location` variants (one per mood). The system should:
**The same base line should NOT be re-authored per mood.** A smuggler entering a location does not need 9 `enter_location` variants (one per mood). The system should:
- Select from the available `enter_location` pool
- Apply mood-weight bonuses to lines with the matching mood tag
- Ensure at least 1-2 lines per trigger/location have each major mood tagged
@@ -407,7 +407,7 @@ Traits, backgrounds, and moods interact. Some combinations have emergent propert
**High coherence combinations** (reinforce each other):
- Cautious + Guardian background: more second-guessing of institutional solutions, more checking of network alternatives
- Bold + Ruthless: decisive and instrumental — the fastest decision-maker, for better or worse
- Compassionate + Worker background: the character who most viscerally feels the human cost of what's happening to Kael and Naia
- Compassionate + Worker background: the character who most viscerally feels the human cost of what's happening to THE FRIEND and their community
- Suspicious mood + Curious trait: questions multiply exponentially — the character follows every thread simultaneously
**High tension combinations** (create internal conflict):
@@ -416,16 +416,16 @@ Traits, backgrounds, and moods interact. Some combinations have emergent propert
- Senator background + Worker background idioms (where the character's formation bleeds through the professional veneer): the occasional shift vocabulary surfaces in otherwise formal speech
**FRIEND arc special case:**
Trait and background modifiers should be considered especially carefully for lines in the FRIEND arc. The same arc beat — "Kael met someone I don't know" — produces dramatically different emotional readings depending on trait combination:
Trait and background modifiers should be considered especially carefully for lines in the FRIEND arc. The same arc beat — "{THE FRIEND} met someone I don't know" — produces dramatically different emotional readings depending on trait combination:
| Trait | Smuggler's first-move internal response to the Kael contradiction |
| Trait | Smuggler's first-move internal response to THE FRIEND contradiction |
|-------|------------------------------------------------------------------|
| Cautious | Checks herself: "Maybe it's nothing. There could be a work reason." (sits with it longer) |
| Bold | Names it immediately: "That's a breach. Kael met someone unauthorized." |
| Compassionate | Worries about Kael first: "What's he gotten himself into?" |
| Bold | Names it immediately: "That's a breach. {THE FRIEND} met someone unauthorized." |
| Compassionate | Worries about {THE FRIEND} first: "What have they gotten into?" |
| Ruthless | Calculates exposure: "How much does this contact know?" |
| Honest | Won't minimize: "He was there. That wasn't anyone we know." |
| Deceptive | Minimizes: "Kael's allowed his own contacts. It's fine." (not fine) |
| Honest | Won't minimize: "They were there. That wasn't anyone we know." |
| Deceptive | Minimizes: "{THE FRIEND}'s allowed their own contacts. It's fine." (not fine) |
These aren't separate arc paths — they're the same arc with different pacing and emotional texture. A Cautious smuggler reaches the confrontation later. A Bold one gets there faster and possibly too fast. The arc is the same. The voice is not.
@@ -444,7 +444,7 @@ For Mellanie — a vocabulary guide per background to use when writing example l
**Senator background idioms:**
- "On record" / "that goes on record" / "recorded as"
- Leverage vocabulary: "what does that cost us," "who holds the note on that"
- Chain-of-command awareness: "above Nils" / "below Voss on that"
- Chain-of-command awareness: "above {leadership}" / "below {Supervisor} on that"
- Process language: "formally," "through channels," "the filing on that says"
**Worker background idioms:**
wiki/authoring/npc-patterns/contradiction-arc.md
+10 -21
View File
@@ -1,16 +1,15 @@
# THE FRIEND: Contradiction Arc Pattern
**Ticket:** #332 | **Priority:** Medium | **Sprint:** 12
**Status:** v0.1 Draft
**Status:** Draft
**Owner:** Paula
**Blocked by:** #297 (Kael Davan profile — done), #298 (Sera Venn profile — done)
**Decisions referenced:** D-034 (THE FRIEND pattern), D-035 (tag taxonomy), D-039 (wow moment #3), D-041 (knowledge graph), D-062 (invisible locked options), D-063 (confrontation mechanics)
---
## 1. What This Document Is
A reusable design pattern document extracted from the two concrete THE FRIEND implementations: Kael Davan (smuggler's FRIEND) and Sera Venn (detective's FRIEND). Both are complete. Both worked. This document captures the structural logic they share so that future FRIEND NPCs can be authored consistently and quickly.
A reusable design pattern document capturing the structural logic shared by THE FRIEND implementations so that future FRIEND NPCs can be authored consistently and quickly.
The pattern is called the **Contradiction Arc**. It is not a mystery. It is not a betrayal in the conventional sense. It is the discovery that someone the player trusts is carrying something they haven't shared — and that what they're carrying changes everything the player thought they understood about the relationship.
@@ -45,8 +44,7 @@ A Contradiction Arc is a 5-phase character trajectory built around a single obse
- Dialogue: `trust: surface` (greeting, small talk) + `trust: real` (personal warmth, shared history)
- Monologue: positive mood tags (content, fond, warm)
**Kael example:** "Kael's already at the dock. Good. The day's better when he's on shift."
**Sera example:** "Good to see Sera. She always was the reliable one. At least someone in this district speaks my language."
*Phase 1 monologue examples: fond, present-tense, no hint of trouble. "Already here. Good. The day's better when they're on shift."*
---
@@ -67,8 +65,7 @@ A Contradiction Arc is a 5-phase character trajectory built around a single obse
- Monologue: mild concern tone; `trigger: observe_anomaly` for behavioral tell moments
- Tell system: all Phase 2 tells fire with `visible_to: peripheral` or `visible_to: any`
**Kael example:** "Kael's distracted today. Checks his lattice more than usual. Probably nothing."
**Sera example:** "Sera left early. 'Headache,' she said. First time she's done that."
*Phase 2 monologue examples: mild concern, plausible innocent explanation. "{FRIEND} is distracted. More lattice checks than usual. Probably nothing." / "{FRIEND} left early. First time for that."*
---
@@ -93,8 +90,7 @@ A Contradiction Arc is a 5-phase character trajectory built around a single obse
- Monologue should name the observation, not the interpretation
- KG update: `contradiction_flagged: true`, relationship shifts to PersonOfInterest
**Kael example:** "That's Kael. But who's he talking to? I don't know that face. And that's not anyone from our rotation."
**Sera example:** "That's the third time. Sera leaves when Torek walks in. Three different excuses. Same result."
*Phase 3 monologue examples: names the observation, not the conclusion. "That's {FRIEND}. But who's that? I don't know that face." / "Third time. {FRIEND} leaves every time {person} walks in. Three different excuses. Same result."*
---
@@ -115,8 +111,7 @@ A Contradiction Arc is a 5-phase character trajectory built around a single obse
- THE FRIEND's response: `trust: real` (this is as honest as THE FRIEND can be without full confession), `situation: [confrontation]`, mood that indicates concealment
- Personal tell confirmation: observation monologue fired by THE FRIEND's specific tell behavior
**Kael example:** "Just a thing. Don't worry about it." [looks left before answering] / Smuggler monologue: "He looked left. He always looks left when he's making something up. Two years I've known that tell. Kael is lying to me."
**Sera example:** "He's just loud. I don't like loud drunks." / Detective monologue: "She's not lying. But she's not telling me everything. Sera, what do you know?"
*Phase 4 examples: THE FRIEND deflects, personal tell fires, character's monologue confirms. "Just a thing. Don't worry about it." [{tell fires}] / "{Character} monologue: 'That tell. I know that tell. {FRIEND} is lying to me.'"*
---
@@ -140,8 +135,7 @@ A Contradiction Arc is a 5-phase character trajectory built around a single obse
- Monologue: `mood: [conflicted]` or `mood: [analytical]`; prerequisite gates on relationship state PersonOfInterest
- If player chose Understanding path: additional monologue lines for partial-confession scenario
**Kael example:** "Same old Kael. Same jokes, same routine. ...What are you not telling me?"
**Sera example:** "Still the same Sera. Still reliable. ...But reliable about what?"
*Phase 5 monologue examples: surface warmth, underlying doubt. "Same old {FRIEND}. Same routine. ...What are you not telling me?"*
---
@@ -170,9 +164,7 @@ Every FRIEND NPC has a **personal tell** — a specific behavioral marker establ
3. Be **unique to this NPC** — not a generic "nervousness" tell, but a specific habit
4. Be **explainable differently before and after** — innocent early, incriminating late
**Kael's tell:** Looks left before answering. Established as a habit the smuggler has observed for two years. Becomes proof of lying at Phase 4 because the smuggler knows the tell AND its meaning.
**Sera's tell:** Gathers her things quickly when leaving. Not a lie tell — Sera isn't lying when she leaves. But the timing (always when Torek arrives) and the variety of excuses (genuine, not scripted) creates the pattern the detective reads as behavioral.
*Tell examples are authored per-NPC against the active roster — see the character-exemplar template for the tell table structure.*
**Tell design rule:** The tell should produce a different emotional register for each playable character observing it:
- The character with the relationship reads the tell as **personal** ("I know that tell — I've seen it before")
@@ -192,10 +184,7 @@ Every FRIEND NPC must produce different monologue experiences for both character
| Phase 4 | Personal confrontation (uses the personal tell as confirmation) | Investigative confrontation (uses behavioral pattern as evidence) |
| Phase 5 | Contaminated intimacy (every warm moment now suspect) | Professional caution (reliable informant now uncertain quantity) |
**The second-playthrough resonance:** The player who has experienced both sides of Triangle 4 understands:
- Kael is trying to get OUT of the ring to protect Naia. His exit attempt is an act of love, not treachery.
- Sera is protecting Naia by NOT reporting what she found. Her concealment is loyalty, not corruption.
- The smuggler and detective are both experiencing friendship fractured by the same cause — Naia's worry about Kael, and the chain of protection that worry created.
**The second-playthrough resonance:** The player who has experienced both sides of the triangle understands that THE FRIEND's concealment comes from care — protection of someone they love, fear of consequences, not treachery. The smuggler and detective are both experiencing friendship fractured by the same cause, approached from opposite angles.
This is the design. The contradiction is not "THE FRIEND is bad." The contradiction is "THE FRIEND is doing something complicated for reasons that make sense, and it's happening to YOU."
@@ -248,4 +237,4 @@ This pattern is designed to be reused. When designing a future FRIEND NPC for a
---
*Ticket #332 — Contradiction arc design document. Reusable FRIEND pattern. v0.1 scope.*
*Ticket #332 — Contradiction arc design document. Reusable FRIEND pattern.*
wiki/authoring/npc-patterns/mirror-moment.md
+38 -191
View File
@@ -1,9 +1,6 @@
# Mirror Moment Design Document
**Ticket:** #329 | **Priority:** Medium | **Sprint:** 12
**Status:** v0.1 Draft
**Owners:** Paula (design), Mellanie (authoring)
**Blocked by:** #297 (Kael profile — done), #298 (Sera profile — done)
**Status:** Design pattern (v0.1 examples removed — see D-122, D-117)
**Decisions referenced:** D-032 (separate monologue pools), D-034 (THE FRIEND), D-039 (wow moment #4 — Divergence Reveal)
---
@@ -17,7 +14,7 @@ The player who has completed both playthroughs encounters the mirror moments as
**What a mirror moment is NOT:**
- A branching dialogue option
- A triggered cutscene
- An informational difference ("the smuggler knows X and the detective doesn't")
- An informational difference ("character A knows X and character B doesn't")
A mirror moment is an **interpretive difference** — same information, same NPC behavior, same physical event. Different internal frame. Different emotional weight.
@@ -26,187 +23,41 @@ A mirror moment is an **interpretive difference** — same information, same NPC
## 2. Design Principles
**Principle 1: Same trigger, different pool (D-032 hard partition)**
Mirror moments operate because monologue pools are hard-partitioned by character. The same trigger key fires into the smuggler pool OR the detective pool — never both. The authoring requirement is to write both sides of every shared trigger.
Mirror moments operate because monologue pools are hard-partitioned by character. The same trigger key fires into one character's pool OR the other's — never both. The authoring requirement is to write both sides of every shared trigger.
**Principle 2: The difference must be felt, not explained**
A mirror moment works when the player FEELS the divergence without having it explained. The two monologue lines should be immediately recognizable as coming from different places — different relationships, different frames, different fears.
**Principle 3: The mirror reveals what the character CARES about**
The smuggler's monologue reveals personal loyalty (people). The detective's monologue reveals investigative analysis (patterns). A mirror moment that doesn't surface this difference is a content gap, not a mirror.
The relationship to a place, person, or object is what the mirror reveals. A mirror moment that doesn't surface this difference is a content gap, not a mirror.
**Principle 4: At least some mirrors should work on first playthrough**
Not every mirror moment requires a second playthrough to land. Some mirrors work as a moment of character voice — the player just hears what their character notices. Second playthrough makes the divergence explicit, but first playthrough should have its own emotional coherence.
---
## 3. The 10 Mirror Moments (v0.1)
### Mirror 1: The Friend's Routine
**Trigger:** `observe_npc` — Seeing THE FRIEND (Kael/Sera) going about their daily routine in their expected location.
**Shared observation:** THE FRIEND is doing exactly what they always do. Nothing unusual. The baseline before anything cracks.
**Smuggler monologue:**
*"Kael's at his station. Right where he always is. Something settles when the shift starts right."*
**Detective monologue:**
*"The dock worker — Davan — is on the floor again. Same position, same timing. Three days in a row. That's a routine. File it."*
**What the mirror reveals:** The smuggler sees a person. The detective sees a data point. Same NPC at the same station. The relationship determines the register.
---
### Mirror 2: The Empty Corridor
**Trigger:** `enter_location` — Player enters a maintenance corridor when no other NPCs are present.
**Shared observation:** The corridor is empty. The maintenance systems hum. No one is watching.
**Smuggler monologue:**
*"Clear. Good. Transition window's still open for eleven more minutes."*
**Detective monologue:**
*"Three separate entries to this corridor in my district walkthrough. Nothing documented in my file about why workers access this route. Off-books path? Add it to the log."*
**What the mirror reveals:** The smuggler reads the empty corridor as operational safety. The detective reads it as an investigative lead. The physical space is identical; the cognitive frame inverts it.
---
### Mirror 3: The Worried Partner (Naia Tamm)
**Trigger:** `observe_npc` — Seeing Naia Tamm sitting alone at the bar, visibly preoccupied.
**Shared observation:** Naia is at The Last Shift without Kael. She looks tired or worried. Not in distress — just carrying something heavy.
**Smuggler monologue:**
*"Naia's here without Kael again. She looks rough. Should check in. ...Not now. Later."*
**Detective monologue:**
*"That woman — Tamm, I think Sera mentioned her — is sitting alone. Wrong energy for a social evening. Something at home, or something she's heard?"*
**What the mirror reveals:** The smuggler has a protective impulse toward Naia but defers it. The detective categorizes Naia as a potential information source. Same worried woman, same empty chair across from her. One character plans to check on a person; the other plans to assess a witness.
---
### Mirror 4: The Spending
**Trigger:** `observe_npc` — Watching Torek Lintar buy rounds at the bar.
**Shared observation:** Torek is buying drinks for several people he doesn't know well. The drinks are nicer than they should be on a compliance officer's salary. He's clearly enjoying himself.
**Smuggler monologue:**
*"Torek's buying rounds again. That's the third time this week. Either he won something, or he's getting paid from somewhere he shouldn't be. Starting to worry about that."*
**Detective monologue:**
*"Commission compliance officer, buying grain spirit for half the bar. On his salary? That doesn't close. Financial tell. Noted."*
**What the mirror reveals:** Both characters notice the same behavioral anomaly. The smuggler frames it as a security risk to the ring. The detective frames it as an evidentiary lead. Both have the same concern (Torek's spending is unusual) — but the concern has completely different stakes.
---
### Mirror 5: Sera Leaving
**Trigger:** `observe_npc` — Watching Sera Venn gather her things and leave the bar when Torek arrives.
**Shared observation:** Sera gives a brief excuse (headache, kiosk check, early shift) and leaves. She was comfortable until the moment Torek walked in.
**Smuggler monologue:**
*"Sera left. Good timing — she was starting to make everyone nervous anyway. Commission presence at Lera's always shifts the temperature."*
**Detective monologue:**
*"Second time now. Sera leaves when Torek walks in. Same type of excuse. 'Headache' last time, 'kiosk' tonight. Same result. That's two data points. Third is a pattern."*
**What the mirror reveals:** The smuggler reads Sera's departure as relief (Commission leaving = safer conversation). The detective reads the same departure as a behavioral anomaly. The event is identical. The emotional response is inverted.
This mirror is structurally important: it shows the detective's FRIEND arc developing through observational patience, while simultaneously showing the smuggler's categorical relationship with Commission presence.
---
### Mirror 6: The Station Hum
**Trigger:** `time_idle` — Player is stationary in the terminal for more than a few seconds with no active interaction.
**Shared observation:** The station's ambient systems — span gate hum, ventilation cycle, cargo machinery in the background — fill the silence. Sova at rest.
**Smuggler monologue:**
*"Span gate's cycling early. One hour to the next transit. Voss'll be running the schedule check in twenty."*
**Detective monologue:**
*"They've been on this station their whole lives. That hum is just background to them. I'm still trying to tune it out."*
**What the mirror reveals:** The smuggler hears operational data in the ambient sound. The detective hears alienation. The station hum carries the same frequency to both characters' ears. It means completely different things to their experience of being in this place.
---
### Mirror 7: The Commission Kiosk
**Trigger:** `enter_location` or `observe_npc` — The player walks past or observes the Commission compliance kiosk near the terminal entrance.
**Shared observation:** The kiosk is a small Commission compliance desk near the terminal entrance — mostly unmanned, used for permit verification and compliance queries. Standard infrastructure.
**Smuggler monologue:**
*"Commission kiosk. Nobody uses it. Institutional furniture. Long as nobody decides to run a full cargo audit, that's exactly what I want it to stay."*
**Detective monologue:**
*"The compliance kiosk has public access to manifest verification records. Local. Less filtered than the request I made through channels. Check it when Maret's not watching."*
**What the mirror reveals:** The smuggler reads the kiosk as a passive threat to be ignored. The detective reads it as an investigative tool. Same object. Same physical location. The smuggler hopes it stays irrelevant; the detective plans to use it.
---
### Mirror 8: Kael and Naia Together (Bar)
**Trigger:** `observe_npc` — Seeing Kael and Naia sitting together at their usual table. Naia is talking; Kael is listening but seems distracted.
**Shared observation:** A couple having dinner. Naia is clearly talking seriously about something. Kael is present but not quite there. The gap between them is subtle but visible.
**Smuggler monologue:**
*"Kael and Naia look... off. Naia's talking a lot. Kael's nodding but he's somewhere else. Something's going on at home. He doesn't say."*
**Detective monologue:**
*"Couple — the dock worker, Davan, and the woman who sits with Sera sometimes. She's animated; he's distracted. Relationship tension. That level of checked-out usually means someone's keeping something."*
**What the mirror reveals:** The smuggler reads this as a friend's private trouble that deserves respect and distance. The detective reads it as behavioral evidence — someone keeping something from a partner. Same visible tension. One character looks away; the other leans in.
---
### Mirror 9: The Manifest Terminal
**Trigger:** `observe_npc` or `enter_location` — The freight manifest terminal in the terminal hub.
**Shared observation:** A freight terminal kiosk showing manifest data. Busy during shifts; the data moves constantly.
**Smuggler monologue:**
*"That's Maret's terminal. She's got access to all the schedules from here. If anything's getting flagged in the manifest data, she'd see it before anyone else. Maret's solid. She won't say anything."*
**Detective monologue:**
*"Freight manifests for the last six months, loaded from here. The cluster analysis shows three anomaly windows, all at shift transition. That's not clerical error. Someone's using this terminal to adjust records after the fact."*
**What the mirror reveals:** The smuggler sees a trusted colleague's workspace and trusts that colleague's loyalty. The detective sees the exact location where evidence of the ring's operations lives. The terminal is simultaneously proof of criminal activity and proof of a trusted relationship — depending on which character is reading it.
---
### Mirror 10: The End of Shift
**Trigger:** `observe_npc` — Watching the shift change happen across the terminal floor — workers clocking out, new crew arriving, a brief period of cross-traffic and handoffs.
**Shared observation:** Dozens of workers moving at once. The shift change is organized chaos. Cargo gets routed, schedules are handed off, the floor changes.
**Smuggler monologue:**
*"Shift transition. Twenty-minute window. The floor's all cross-traffic now — nobody's tracking individual movement. This is when it runs."*
**Detective monologue:**
*"Shift change. Every anomaly in my manifest data clusters around this. The window. The handoff moment. Someone is using the cross-traffic as cover. But for WHAT?"*
**What the mirror reveals:** The smuggler knows exactly what the shift change covers. The detective sees the pattern but not the specific. Both characters observe the same 20-minute window of organized chaos. One is running something through it; the other is trying to figure out what's being run.
## 3. Mirror Moment Examples
*v0.1 examples removed (cited named NPCs no longer in v0.2 pipeline — D-122). Author mirror pairs against the active district's social sites and NPC roster.*
**Structural types to cover in any district:**
- THE FRIEND at baseline routine (personal vs. analytical read)
- Empty operational space (operational safety vs. investigative lead)
- NPC in emotional distress (protective impulse vs. witness assessment)
- Behavioral tell (security concern vs. evidentiary lead)
- THE FRIEND avoiding another NPC (relief vs. behavioral anomaly)
- Ambient environment (familiarity vs. alienation)
- Institutional infrastructure (passive threat vs. investigative tool)
- THE FRIEND with their significant relationship (privacy vs. evidence)
- Information terminal (trusted colleague's workspace vs. crime scene)
- Routine operational window (cover vs. pattern recognition)
---
## 4. Mirror Moment Authoring Rules
### Rule 1: Both sides are mandatory
A mirror moment is only complete when both the smuggler monologue and the detective monologue are authored. Omitting one side is a content gap.
A mirror moment is only complete when both sides of the mirror are authored. Omitting one side is a content gap.
### Rule 2: Same trigger key, different pool
Both lines use the same `trigger` type and similar `prerequisite` conditions. They appear in separate character monologue files (D-032 hard partition). The only difference is the `character` tag.
@@ -225,30 +76,30 @@ Add `tags: [mirror_moment]` to both sides of every mirror pair so they can be id
## 5. YAML Example
```yaml
# Smuggler side — monologue-smuggler.yaml
- id: pc-smuggler_m_s_044
character: smuggler
# Character A side — monologue-character-a.yaml
- id: pc-{archetype-a}_m_s_001
character: {archetype-a}
trigger: observe_npc
prerequisite:
location: the-terminal
target: npc:naia-tamm
location: {location-slug}
target: npc:{npc-slug}
relationship_state: Known
text: "Naia's here without Kael again. She looks rough. Should check in. ...Not now. Later."
mood: [concerned, fond]
text: "{Line from character A's relationship frame — personal, protective, operational}"
mood: [warm, concerned]
topic: [colleague]
tags: [mirror_moment, mirror_worried_partner]
tags: [mirror_moment, mirror_{name}]
# Detective side — monologue-detective.yaml
- id: pc-detective_m_d_044
character: detective
# Character B side — monologue-character-b.yaml
- id: pc-{archetype-b}_m_d_001
character: {archetype-b}
trigger: observe_npc
prerequisite:
location: the-last-shift
target: npc:naia-tamm
text: "That woman — Tamm, I think Sera mentioned her — is sitting alone. Wrong energy for a social evening. Something at home, or something she's heard?"
location: {location-slug}
target: npc:{npc-slug}
text: "{Same trigger, different frame — analytical, investigative, pattern-seeking}"
mood: [analytical, curious]
topic: [investigation]
tags: [mirror_moment, mirror_worried_partner]
tags: [mirror_moment, mirror_{name}]
```
---
@@ -267,14 +118,10 @@ For each mirror pair:
---
## 7. Expansion Notes (Post-v0.1)
## 7. Expansion Notes
Additional mirror moments to author in future content passes:
- **The Missing Person Notice:** A posted notice near the bar about a missing dock worker (pre-existing, unrelated to main plot). Smuggler: "People disappear. Station life." Detective: "Filed under 'before my posting.' What was the investigative status?"
- **Voss Walking the Floor:** The shift supervisor doing a routine floor inspection. Smuggler sees cover being maintained. Detective sees a potential informant.
- **Drin's Inspection:** Dock inspector doing a container verification. Smuggler knows Drin will find nothing. Detective sees the inspection as either genuine compliance or evidence of a compromised process.
Mirror moments should be authored for every repeated trigger point in a district's social sites. Priority triggers: THE FRIEND's daily routine, shift transitions, any institutional infrastructure, behavioral tells, NPC pairings that create observable social dynamics. The more a location has observable social texture, the more mirror moments it can support.
---
*Ticket #329 — Mirror moment design document. 10 paired observations. v0.1 scope.*
*Design pattern document — Mirror Moments. Examples are authored per-district against the active NPC roster.*
wiki/authoring/npc-patterns/the-mirror.md
+37 -167
View File
@@ -3,7 +3,6 @@
**Pattern Type:** Production-level Tier 1 (emotional depth, full 10-axis model)
**Design Principle:** Transparency as contrast mechanism
**Ticket:** #380
**Reference Implementation:** Naia Tamm (Sova Transit District v0.1)
---
@@ -26,10 +25,10 @@ THE MIRROR is the honest-character NPC pattern. No contradiction arc, no deep se
| Absent System | Why Missing | Content Signal |
|--------------|-------------|----------------|
| **No tells** | Tells imply deception or concealment. MIRROR has nothing to conceal from the player (though they may be uninformed about events around them). The absence of tells IS the tell — when the player has learned to read behavioral flags on every other NPC, encountering someone without them is the anomaly. | The player's monologue might note: "No hesitation. No evasion. Either she's telling the truth or she's the best liar I've ever met." The absence becomes noticeable. |
| **No dishonesty ≠ no misinformation** | MIRROR NPCs can be *wrong* without being *deceptive*. A MIRROR who has been lied to will repeat that lie in good faith -- they are transparent about what they believe, not omniscient about what is true. Naia reporting "Kael said he's picking up extra shifts" is honest transmission of a lie she was told. | The player recognizes the MIRROR is being used as an unwitting conduit. This makes the liar's deception feel worse, not the MIRROR's honesty feel cheaper. |
| **No dishonesty ≠ no misinformation** | MIRROR NPCs can be *wrong* without being *deceptive*. A MIRROR who has been lied to will repeat that lie in good faith -- they are transparent about what they believe, not omniscient about what is true. A MIRROR repeating a partner's cover story is honest transmission of a lie — they're being transparent about what they believe, not what is true. | The player recognizes the MIRROR is being used as an unwitting conduit. This makes the liar's deception feel worse, not the MIRROR's honesty feel cheaper. |
| **No secrets** (or only mundane surface-level ones) | The `secret_held` field is empty or contains only ordinary privacy (e.g., "worried about partner's late nights" — visible to anyone observant). No trust gates that reveal hidden criminal knowledge or conspiracies. | If a MIRROR has a "secret," it's one they'd share with a sympathetic stranger at a bar. There's no revelation moment where the player discovers the MIRROR was hiding something all along. |
| **No contradiction arc** | No phases, no discovery moment, no color shift from green to amber. The relationship with MIRROR is stable across the session. | The trust level may deepen (public → insider → peer), but there's no betrayal moment. The MIRROR you meet at minute 5 is the same MIRROR at minute 25. |
| **No trust-gated dialogue that changes the picture of who they are** | Trust progression reveals more FEELING, not more SECRETS. Deeper access tiers show emotional vulnerability, not concealed information. | At `public` tier: "I'm worried about Kael." At `peer` tier: "I don't know what to do. I love him, but I can't keep living like this." Same truth, deeper emotion. |
| **No trust-gated dialogue that changes the picture of who they are** | Trust progression reveals more FEELING, not more SECRETS. Deeper access tiers show emotional vulnerability, not concealed information. | At `public` tier: "I'm worried about them." At `peer` tier: "I don't know what to do. I love them, but I can't keep living like this." Same truth, deeper emotion. |
### What MIRROR NPCs DO Have
@@ -50,7 +49,7 @@ THE MIRROR is the honest-character NPC pattern. No contradiction arc, no deep se
|-------------|-----------|----------|
| **Dialogue** | 25-35 | Greetings (5), emotional state conversation (8-10), relationship discussion (5-7), situation responses (5-8), peer-tier vulnerability (3-5) |
| **Trust-gated dialogue** | 10-15 | Deeper emotional exposure at insider/peer tiers. Not secret revelations — emotional revelations. "I'm scared" vs "I'm worried." |
| **Unprompted lines** | 3-5 | MIRROR volunteers emotional state or asks for help. "Have you seen Kael today? I'm worried." |
| **Unprompted lines** | 3-5 | MIRROR volunteers emotional state or asks for help. "Have you seen {partner} today? I'm worried." |
| **Monologue triggers** | 10-15 per character | Player's internal reaction to MIRROR's honesty. Smuggler: guilt (if protecting someone the MIRROR loves). Detective: relief (finally someone not lying) + strategic value (MIRROR as witness to behavioral change). |
| **Voice sample** | 3-5 lines | Covering: baseline warm, worried, brittle (close to tolerance break) |
@@ -73,7 +72,7 @@ THE MIRROR is the honest-character NPC pattern. No contradiction arc, no deep se
| What the Player Experiences | System State | Mechanical Expression |
|-----------------------------|--------------|---------------------|
| Early game: MIRROR seems ordinary | No behavioral flags set. No `contradiction_flagged`. No tell observations in monologue. | The player's training (from interacting with NPCs who DO have tells) hasn't fired. This feels normal. |
| Mid game: Player has learned to read other NPCs | The player has observed: Kael looks left when lying, Sera leaves when Torek arrives, Voss fidgets when questioned about manifests. | The player's mental model now expects tells. They're watching for them. |
| Mid game: Player has learned to read other NPCs | The player has observed: one NPC deflects eye contact when lying, another leaves when a third NPC arrives, a third fidgets when questioned about their role. | The player's mental model now expects tells. They're watching for them. |
| MIRROR interaction: No tells present | Player talks to MIRROR. MIRROR makes eye contact, answers directly, emotional state matches words. No spatial deviation, no topic deflection, no nervous tics. | The ABSENCE is striking. The player's monologue notes it: "No hesitation. She's either telling the truth or she's the best actor I've ever seen." |
| Resolution: Trust through transparency | If the player cross-references MIRROR's information with other sources, it checks out. MIRROR was telling the truth. | The player LEARNS that honesty exists in this world. That one person isn't performing. That becomes the emotional fulcrum for everything else. |
@@ -99,10 +98,10 @@ MIRROR dialogue follows the standard four-layer system (D-028) but with simplifi
| Tier | What MIRROR Shares | Example |
|------|-------------------|---------|
| **Public** | Observable emotional state, general information about their life/relationships | "I teach at the community school. The kids are doing well this term." |
| **Insider** | Specific worry, named relationships, genuine vulnerability | "Kael's been coming home late. Says it's work, but the schedule doesn't match. I don't know what to think." |
| **Peer** | Deep emotional exposure, requests for help or advice | "I'm scared, honestly. Not of Kael — of what Kael might be involved in. I don't know who else to talk to." |
| **Authority** (if detective) | Cooperation with investigation, willingness to provide information about loved one despite emotional cost | "If you think Kael is in trouble, I want to know. I'll help if I can. Just — please don't hurt him." |
| **Public** | Observable emotional state, general information about their life/relationships | "I work at the station school. The kids are doing well this term." |
| **Insider** | Specific worry, named relationships, genuine vulnerability | "{Partner} has been coming home late. Says it's work, but the schedule doesn't match. I don't know what to think." |
| **Peer** | Deep emotional exposure, requests for help or advice | "I'm scared, honestly. Not of them — of what they might be involved in. I don't know who else to talk to." |
| **Authority** (if detective) | Cooperation with investigation, willingness to provide information about loved one despite emotional cost | "If you think they're in trouble, I want to know. I'll help if I can. Just — please don't hurt them." |
**No secret tier that reveals hidden criminal knowledge.** The MIRROR doesn't have hidden criminal knowledge. The "secret" tier for MIRROR is the deepest emotional vulnerability, not a plot revelation.
@@ -115,14 +114,14 @@ What changes: Depth of emotional sharing, not type of information.
What doesn't change: The facts. MIRROR tells the same truth at all tiers. The emotion around it deepens.
```
**Example progression (Naia about Kael):**
**Example progression (MIRROR about their entangled partner):**
- **Public:** "Kael works at the freight hub. Dock worker. We've been together six years."
- **Insider:** "Kael's been stressed lately. Late nights, evasive when I ask about it. I'm worried."
- **Peer:** "I love him. But I can't keep doing this — the not-knowing is killing me. I think something's wrong. I just don't know what."
- **Authority (detective):** "If you're investigating something at the hub, and if Kael is involved — I need to know. I'll help. I just need the truth."
- **Public:** "{Partner} works at the freight terminal. We've been together {n} years."
- **Insider:** "{Partner} has been stressed lately. Late nights, evasive when I ask about it. I'm worried."
- **Peer:** "I love them. But I can't keep doing this — the not-knowing is killing me. I think something's wrong. I just don't know what."
- **Authority (detective):** "If you're investigating something there, and if {partner} is involved — I need to know. I'll help. I just need the truth."
Same story. Deeper emotion. No revelation that changes the player's understanding of who Naia is.
Same story. Deeper emotion. No revelation that changes the player's understanding of who the MIRROR is.
### Monologue Trigger Design
@@ -132,153 +131,29 @@ MIRROR NPCs trigger monologue focused on the PC's EMOTIONAL REACTION to the MIRR
| Trigger | Monologue Content | Emotional Layer |
|---------|------------------|-----------------|
| Observe MIRROR waiting at bar | "Naia's at the bar again. Alone. Keeps looking at the door. I know where Kael is. I can't say." | Guilt. The smuggler's operational knowledge creates distance from the MIRROR's suffering. |
| MIRROR asks about loved one | "She asked if I'd seen Kael today. What do I say? 'Yeah, he's fine, just moving contraband?' Can't tell her. Can't lie to her face either." | Moral tension. The MIRROR's directness makes evasion feel worse. |
| MIRROR shares deep worry | "She's really scared. Not just worried — scared. And she has no idea what's actually happening. If she knew..." | Protective instinct + guilt. The smuggler wants to shield the MIRROR from both the truth and the consequences. |
| Observe MIRROR waiting at bar | "{MIRROR} is at the bar again. Alone. Keeps looking at the door. I know where {partner} is. I can't say." | Guilt. The smuggler's operational knowledge creates distance from the MIRROR's suffering. |
| MIRROR asks about loved one | "They asked if I'd seen {partner} today. What do I say? Can't tell them. Can't lie to their face either." | Moral tension. The MIRROR's directness makes evasion feel worse. |
| MIRROR shares deep worry | "They're really scared. Not just worried — scared. And they have no idea what's actually happening. If they knew..." | Protective instinct + guilt. The smuggler wants to shield the MIRROR from both the truth and the consequences. |
**Detective monologue about MIRROR:**
| Trigger | Monologue Content | Emotional Layer |
|---------|------------------|-----------------|
| First conversation with MIRROR | "She's not hiding anything. I've interviewed enough people to know when someone's performing. She's genuinely worried." | Relief. In a district where everyone seems evasive, the MIRROR is a breath of fresh air. |
| MIRROR shares information about loved one | "She knows his routine better than anyone. The late nights, the evasions — she's been tracking them without realizing it. She's building my case for me." | Strategic recognition. The MIRROR is a witness to behavioral change — the best kind. |
| MIRROR asks for help | "She wants me to figure out what's wrong. Not to arrest anyone — just to know. That's... trust. Real trust." | Emotional weight. The detective realizes the investigation has personal stakes for the MIRROR. Success means breaking someone's heart. |
| First conversation with MIRROR | "Not hiding anything. I've interviewed enough people to know when someone's performing. This person is genuinely worried." | Relief. In a district where everyone seems evasive, the MIRROR is a breath of fresh air. |
| MIRROR shares information about loved one | "Knows {partner}'s routine better than anyone. The late nights, the evasions — been tracking them without realizing it. Building my case for me." | Strategic recognition. The MIRROR is a witness to behavioral change — the best kind. |
| MIRROR asks for help | "They want me to figure out what's wrong. Not to arrest anyone — just to know. That's... trust. Real trust." | Emotional weight. The detective realizes the investigation has personal stakes for the MIRROR. Success means breaking someone's heart. |
---
## 6. Naia Tamm — Reference Implementation
## 6. Reference Implementation
Naia Tamm is the v0.1 MIRROR NPC in Sova Transit District. Let me walk through how her 10-axis profile demonstrates each MIRROR rule.
*v0.1 named-NPC example removed (cited NPCs no longer in v0.2 pipeline — D-122). Author MIRROR reference implementations against the active district's roster using the generator template in Section 7.*
### Core Identity
- **Name:** Naia Tamm
- **Age:** 33
- **Role:** Teacher, Station Sova community school
- **Social Site:** The Last Shift (Bar)
- **Triangle:** Triangle 4 — The Worried Partner (Naia - Kael - Sera)
### 10-Axis MIRROR Implementation
#### 1. Want (Tier 1 depth, no deception)
**Primary:** Understand what's happening with Kael.
Naia and Kael have been together 6 years. Kael started coming home late, evasive answers, money that doesn't match hours. Naia doesn't know about the ring. Naia knows the person they share a life with is hiding something. The not-knowing is worse than almost any truth.
**Secondary:** Protect the life they've built.
Naia wants it resolved without destroying everything — the home, the relationship, the stability. This is why Naia confides in Sera instead of confronting Kael directly: wants advice, not a fight.
**MIRROR rule demonstrated:** Want is ABOUT someone else's secret, not concealing Naia's own. Naia's motivation is transparent to the player from the first conversation.
#### 2. Secret / Vulnerability (surface-level only)
**Surface secret:** Worried about Kael. Visible to anyone who sees Naia's stress.
**Deep secret:** Naia confided in Sera about Kael's behavior. This is the action that set Sera's compliance check in motion, though Naia doesn't know that. Naia shared a personal worry with a trusted friend.
**Vulnerability:** Emotional exposure. Naia's worry is genuine, visible, exploitable.
**MIRROR rule demonstrated:** Naia's "secret" is that she confided in a friend. That's not a conspiracy — it's ordinary human behavior under stress. The vulnerability is EMOTIONAL, not criminal.
#### 3. Relationships (genuine, no hidden agendas)
**Kael Davan (partner, 6 years):** Deep love, growing anxiety. Doesn't question Kael's character — just Kael's honesty.
**Sera Venn (close friend, 10 months):** Genuine friendship. Trusts Sera as someone who can give perspective without gossip.
**Lera Sessik (bar acquaintance):** Social connection. Lera is warm to Naia — protective attention to someone visibly struggling.
**MIRROR rule demonstrated:** All relationships are exactly what they appear to be. No hidden resentments, no secret alliances, no ulterior motives. Naia likes who she likes for straightforward reasons.
#### 4. Tolerance Threshold (moderate, genuine limits)
**Moderate.** Patient — teaching station kids requires it. But patience is fraying. Every evasive answer from Kael chips at tolerance. If pushed to breaking point, Naia confronts Kael directly — which could trigger Kael's crisis, force Sera's hand, or give the detective an opening.
**MIRROR rule demonstrated:** Tolerance threshold is real and observable. No hidden resilience, no secret breaking point. What Naia says she can tolerate is what she can tolerate.
#### 5. Daily Routine (predictable, no spatial deviations)
- 07:00 - 15:00: Teaching (community school, Residential Radial A)
- 15:00 - 15:30: Commute back to Transit District
- 15:30 - 17:30: Bar (The Last Shift) — meets Sera, social time
- 17:30 - 22:00: Home. Waits for Kael.
- Late evenings: Alone in apartment, wondering where Kael is.
**MIRROR rule demonstrated:** Routine is stable, observable, doesn't hide anything. Naia is where she says she'll be. No unauthorized corridor meetings, no suspicious timing patterns. The routine itself is transparent.
#### 6. Information Inventory (knows what she knows, doesn't know what she doesn't)
**Knows:** Kael's normal routine (6 years of partnership), Kael's recent deviations (late nights, evasive answers), Sera's Commission role (knows Sera is a tech, not investigator), bar social dynamics, school community.
**Doesn't know:** Ring, smuggling, Kael's membership, manifest discrepancies, Sera's compliance check, the detective's investigation.
**MIRROR rule demonstrated:** Naia's knowledge state is exactly what it appears to be. She's not concealing anything she knows. She genuinely doesn't know the conspiracy exists. This makes her the perfect witness to BEHAVIORAL change without knowledge of CAUSE.
#### 7. Contentment (low and declining — thematically essential)
**Was content:** Stable job, loving partner, community. Now relationship anxiety is coloring everything. Teaching is harder when distracted. Bar visits tinged with worry. Home is where the absence lives.
**MIRROR rule demonstrated:** Contentment trajectory is VISIBLE and GENUINE. Naia isn't pretending to be happy or hiding dissatisfaction. Her emotional state is observable in her voice, her behavior, her routine changes (increased bar presence = avoiding empty apartment).
#### 8. Personality Traits (no performance, no mask)
- **Primary: Caring** — genuinely invested in other people's wellbeing
- **Secondary: Patient** — tolerates uncertainty longer than most, but not indefinitely
- **Tertiary: Perceptive** — reads emotional states well. Knows when Kael is lying even if can't prove it.
**MIRROR rule demonstrated:** These traits are REAL, not performed. Naia's caring isn't a manipulation tactic. Her perceptiveness makes her WORRIED (she knows something's wrong) but doesn't make her SUSPICIOUS (she trusts Kael's character even while doubting his honesty about the situation).
#### 9. Tell System (ABSENT — the design payload)
Naia's entry in the wiki lists three "tells":
| Tell | Trigger | Observable To |
|------|---------|---------------|
| Visible stress | Tired eyes, distracted conversation, checking lattice | Sera, Lera, Detective, bar regulars |
| Mentions Kael unprompted | Worry overflowing into conversation | Sera, Detective (if sitting nearby) |
| Increased bar presence | Coming more often, staying longer — avoiding empty apartment | Lera (notices pattern), Sera (recognizes coping mechanism) |
**CRITICAL MIRROR DISTINCTION:** These are NOT tells in the deception-detection sense. They're not "behavioral flags that signal concealment." They're GENUINE STRESS MARKERS. Naia is visibly worried because Naia IS worried. There's no contradiction between internal state and external behavior.
**The system perspective:** A TELL is a deviation that signals deception (Kael looks left when lying, Sera leaves when Torek arrives). Naia's behaviors are COPING MECHANISMS and EMOTIONAL EXPRESSIONS, not tells. The player's monologue doesn't say "She's hiding something." It says "She's really struggling."
**MIRROR rule demonstrated:** The absence of deception-tells IS the content. The player who has learned to read evasion on other NPCs will notice that Naia makes direct eye contact, answers questions fully, doesn't deflect topics, doesn't have spatial anomalies beyond her normal routine. That ABSENCE becomes the signal: "This person is being honest with me."
#### 10. Skill Set (civilian, no hidden capabilities)
**Occupational:** Teaching, community engagement, youth education, curriculum management.
**Combat tag:** NO. Entirely civilian.
**Lattice capability:** Baseline.
**MIRROR rule demonstrated:** No hidden skills, no secret training, no combat capability concealed behind a civilian facade. Naia is exactly what she presents: a teacher who's worried about her partner.
### Naia's Triangle Role (Emotional Center)
**Triangle 4: The Worried Partner (Naia - Kael - Sera)**
Naia is the emotional center. Naia's worry about Kael triggered Sera's investigation. Naia's trust in Sera makes Sera's concealment more painful. Naia connects the detective's investigation to Kael's personal life through Sera, through Naia's own observations, through the fact that a worried partner is the best witness to behavioral change.
**Why MIRROR works here:** Naia is UNINVOLVED in the conspiracy but CENTRAL to its emotional impact. She's the person both the smuggler and detective want to protect — and the person whose honest worry makes the smuggling operation's human cost visible. If Naia were lying, the triangle would be about competing deceptions. Because Naia is honest, the triangle is about the COST of everyone else's deceptions.
### Dual-Lens Implementation
**Smuggler perspective (if smuggler is Kael's friend):**
Naia is emotional collateral. The smuggler knows why Kael is busy and can't say. Seeing Naia's worry creates guilt. If Naia asks the smuggler about Kael, there's no good answer.
Sample monologue: *"Naia's at the bar again. Alone. Looking at the door every time it opens. I know where Kael is. I can't say."*
**Detective perspective:**
Naia is a potential source. A partner who suspects their loved one is hiding something is a classic entry point. The detective can cultivate Naia's trust by being sympathetic — listen, validate, gently probe. Naia might not know specifics, but knows Kael's routine, habits, recent changes better than anyone.
Sample monologue: *"The partner — Naia Tamm. Teacher. Visibly stressed. Keeps looking at the door. If Davan is involved, this partner knows something changed, even if they don't know what."*
**MIRROR payload in dual-lens:** SAME transparency, DIFFERENT player reaction. Smuggler feels guilt. Detective sees opportunity. Both recognize honesty. The MIRROR's transparency makes the two characters' different relationships to truth more visible by contrast.
**What a reference implementation demonstrates:**
- 10-axis profile with the MIRROR rules annotated at each axis
- Triangle role showing how the MIRROR's honesty creates emotional pressure on entangled NPCs
- Dual-lens comparison showing same transparency producing different player reactions (guilt vs. strategic recognition)
- Visible stress markers explicitly distinguished from deception tells
---
@@ -459,7 +334,7 @@ MIRROR is mechanically interesting BECAUSE of the surrounding systems. In a game
### The Emotional Fulcrum
When the ring's actions threaten the MIRROR (Naia worrying about Kael, potentially losing her relationship and stability), the player FEELS it because they've learned to believe this person.
When the ring's actions threaten the MIRROR's relationships and stability, the player FEELS it because they've learned to believe this person.
**Smuggler:** The guilt of watching an innocent person suffer because of your operations. You can't tell her. You can't protect her. You're part of the cause of her pain.
@@ -469,18 +344,18 @@ When the ring's actions threaten the MIRROR (Naia worrying about Kael, potential
### The Trust Anchor
In a district where everyone has an agenda, the MIRROR is the person the player can RELY on. When the smuggler needs to know what's happening with Kael, Naia will tell the truth as she understands it. When the detective needs a witness, Naia will cooperate fully. The MIRROR's reliability is itself a strategic asset — but one that comes with emotional cost (using an innocent person's trust).
In a district where everyone has an agenda, the MIRROR is the person the player can RELY on. When the smuggler needs to know what's happening with {partner}, the MIRROR will tell the truth as they understand it. When the detective needs a witness, the MIRROR will cooperate fully. The MIRROR's reliability is itself a strategic asset — but one that comes with emotional cost (using an innocent person's trust).
**System interaction:** The trust-gated gossip system (D-028 Layer 3, #171) means NPCs share information at different access tiers. With most NPCs, the player wonders: "Is this real or are they steering me?" With MIRROR, that question is answered: "This is real. She's telling me everything she knows." That certainty is VALUABLE in a game built on asymmetric information.
**System interaction:** The trust-gated gossip system (D-028 Layer 3, #171) means NPCs share information at different access tiers. With most NPCs, the player wonders: "Is this real or are they steering me?" With MIRROR, that question is answered: "This is real. They're telling me everything they know." That certainty is VALUABLE in a game built on asymmetric information.
### The Replay Dimension
On second playthrough, playing the other character, the MIRROR's honesty becomes even more visible. The player KNOWS Naia isn't involved. They see her worry from a different angle:
On second playthrough, playing the other character, the MIRROR's honesty becomes even more visible. The player KNOWS this person isn't involved. They see their worry from a different angle:
- **Playthrough 1 (smuggler):** "I know why Kael is busy. Naia's worry is collateral damage."
- **Playthrough 2 (detective):** "Naia's worry is my opening. She's the way in."
- **Playthrough 1 (smuggler):** "I know why {partner} is busy. {MIRROR}'s worry is collateral damage."
- **Playthrough 2 (detective):** "{MIRROR}'s worry is my opening. They're the way in."
Same honesty. Different use. The player's knowledge that Naia is a MIRROR (from first playthrough) makes the second playthrough's interaction with her more complex: "I know she's honest. How do I use that? Should I?"
Same honesty. Different use. The player's knowledge that this NPC is a MIRROR (from first playthrough) makes the second playthrough's interaction more complex: "I know they're honest. How do I use that? Should I?"
**Replay payload:** MIRROR transparency survives across playthroughs. FRIEND contradictions change (different seed might assign FRIEND to different NPC). MIRROR remains honest regardless of seed. That constancy is mechanically useful for teaching the player to recognize honesty — and ethically complex when the player knows they'll exploit it.
@@ -617,16 +492,11 @@ In a world where everyone is hiding something, the one person who isn't becomes
- That trust makes the MIRROR's emotional stakes real
- Threats to the MIRROR create urgency and moral weight
**Naia Tamm demonstrates every rule:** She has full Tier 1 depth, genuine emotional complexity, visible stress, transparent relationships, predictable routine, and zero deception. Her honesty makes Kael's secrets painful, Sera's concealment costly, and the investigation's human consequences visible.
**For content authors:** MIRROR is mechanically simple (no contradiction content) but emotionally complex (full 10-axis depth). The 50-70 line budget focuses on genuine emotional expression, trust progression through vulnerability, and dual-lens player reaction. The MIRROR is the person both characters want to protect — and the person who makes the cost of deception real.
**For content authors:** MIRROR is mechanically simple (no contradiction content) but emotionally complex (full 10-axis depth). Full Tier 1 depth, genuine emotional complexity, visible stress, transparent relationships, predictable routine, zero deception — the MIRROR's honesty makes the entangled NPC's secrets painful, other NPCs' concealment costly, and the investigation's human consequences visible. The 50-70 line budget focuses on genuine emotional expression, trust progression through vulnerability, and dual-lens player reaction. The MIRROR is the person both characters want to protect — and the person who makes the cost of deception real.
---
**End Pattern Specification.**
**Files referenced:**
- `/var/mnt/data/projects/settled-reach/copy/wiki/npcs/naia-tamm.md` — Reference implementation
- `/var/mnt/data/projects/settled-reach/copy/decisions/content.md` — D-024 (10-axis model), D-028 (dialogue architecture), D-029 (entanglement ratio), D-032 (separate monologue pools), D-034 (THE FRIEND pattern), D-035 (tag taxonomy)
- `/var/mnt/data/projects/settled-reach/copy/docs/workshops/v01-content-scoping/round2-gestalt.md` — Pattern definitions and NPC mapping
- `/var/mnt/data/projects/settled-reach/copy/docs/workshops/v01-gap-analysis/round2-gestalt.md` — Unified observation system, character identity integration
**Decisions referenced:**
- `decisions/content.md` — D-024 (10-axis model), D-028 (dialogue architecture), D-029 (entanglement ratio), D-032 (separate monologue pools), D-034 (THE FRIEND pattern), D-035 (tag taxonomy)
wiki/authoring/tier1-module-authoring.md
+19 -19
View File
@@ -3,13 +3,13 @@
**Schema:** `content/schemas/drama_module.schema.yaml`
**Module pool:** `content/modules/tier1/*.yaml`
**Decisions:** D-023 (three-tier model), D-027 (vertical slice), D-029 (30/50/20 population), D-034 (FRIEND pattern)
**Vertical slice reference:** `content/modules/tier1/smuggling_ring_v0_1.yaml`
**Vertical slice reference:** `content/modules/tier1/`
---
## What Is a Tier 1 Drama Module?
Tier 1 is the authored conspiracy layer of D-023. Drama modules are the things that can go wrong — or go very right, or simply happen — beneath the surface of daily life in Sova Transit. They are:
Tier 1 is the authored conspiracy layer of D-023. Drama modules are the things that can go wrong — or go very right, or simply happen — beneath the surface of daily life in the district. They are:
- **Hand-authored.** Every event sequence, every NPC role, every outcome was written by a person.
- **Pool-based.** Multiple modules exist. The storyteller draws from the pool at game start and activates a subset based on the district and the storyteller's pacing decisions.
@@ -33,8 +33,8 @@ content/
drama_module.schema.yaml ← Schema reference (this file validates against it)
modules/
tier1/
smuggling_ring_v0_1.yaml ← The v0.1 vertical slice module
future_module_v0_1.yaml ← Future modules go here
smuggling_ring.yaml ← Canonical smuggling ring drama module
future_module.yaml ← Future modules go here
```
One `.yaml` file per drama module. The storyteller's content loader scans `content/modules/tier1/` at startup and adds all valid modules to the pool.
@@ -68,7 +68,7 @@ Controls how the storyteller samples this module.
| `pool.incompatible_with` | No | Module IDs that can't run concurrently. |
| `pool.max_concurrent` | No | Almost always 1. |
**Design note on weight:** Use weight to tune narrative variety, not difficulty. A weight-1 module is a rare playthrough surprise. A weight-8 module like the smuggling ring is "this is usually what's happening in Sova Transit."
**Design note on weight:** Use weight to tune narrative variety, not difficulty. A weight-1 module is a rare playthrough surprise. A weight-8 module is "this is usually what's happening in this district."
---
@@ -119,7 +119,7 @@ Each module specifies its NPC slots. Roles are internal slugs used throughout th
#### Named vs. Generated Bindings
**Named bindings** reference specific hand-authored NPCs from the district. All v0.1 roles are named. This is the right choice for:
**Named bindings** reference specific hand-authored NPCs from the district. This is the right choice for:
- THE FRIEND NPCs (D-034) — they have authored arcs, not generic behavior
- NPCs with unique relationships in the 5-triangle web
- Roles where voice, history, and moral weight matter
@@ -185,10 +185,10 @@ Events are world-state changes the storyteller fires. They are not scripted play
| **Sequence** | Ordered narrative beats. Step N+1 becomes eligible only after step N fires. Use for character arcs. |
| **Pool** | Unordered ambient activity. The storyteller fires any eligible event at any time. Use for texture and background. |
The vertical slice uses:
- `kael_exit_arc` (sequence) — Kael's ordered character arc
A typical module uses:
- `{friend}_exit_arc` (sequence) — THE FRIEND's ordered character arc
- `investigation_pressure` (sequence) — Parallel pressure escalation
- `ambient_ring_activity` (pool) — Background ring business that runs throughout
- `ambient_activity` (pool) — Background conspiracy business that runs throughout
Most modules should have 1-2 sequences plus 1 pool.
@@ -306,7 +306,7 @@ Every event and outcome must mean something different to the smuggler and the de
### 3. No Clean Resolutions
D-034 and D-027 both require moral ambiguity. The smuggling ring doesn't have a "good" ending. The detective arresting Kael is not obviously better than letting him go. Every outcome must have a cost. If one outcome is obviously correct, you've failed the design.
D-034 and D-027 both require moral ambiguity. No Tier 1 module has a "good" ending. Confronting THE FRIEND is not obviously better than protecting them. Every outcome must have a cost. If one outcome is obviously correct, you've failed the design.
### 4. THE FRIEND Contradiction Is the Pivot
@@ -315,7 +315,7 @@ If your module involves a FRIEND-pattern NPC, the observable contradiction (D-03
- **Ambiguous before context** — the player sees the behavior before they understand what it means
- **Irreversible once witnessed** — seeing changes the relationship, even if the player does nothing
The secret meeting in corridor B-7 is the canonical example. After witnessing it, neither character can pretend they don't know what they saw.
The canonical example: witnessing THE FRIEND in an unauthorized location, with an unknown contact, outside their stated routine. After witnessing it, neither character can pretend they don't know what they saw.
### 5. Expiry Is Not Failure
@@ -343,7 +343,7 @@ These rules cover the schema's format constraints and the validation gaps that J
| `outcome_id` | `^[a-z][a-z0-9_-]*$` | `ring_exposed` |
| `sets_flag` / flag references | `^[a-z][a-z0-9_-]*$` | `kael_behavior_changed` |
| `role` (npc slot) | `^[a-z][a-z0-9-]*$` | `ring-member-exiting` |
| `named_npc` | `^npc:[a-z][a-z0-9-]*$` | `npc:kael-davan` |
| `named_npc` | `^npc:[a-z][a-z0-9-]*$` | `npc:{slug}` |
| `version` | `^[0-9]+\\.[0-9]+$` | `0.1` |
Note the difference: `event_id`, `outcome_id`, `sequence_id`, and flags use underscores and hyphens (`[a-z0-9_-]*`). NPC `role` slugs use hyphens only (`[a-z0-9-]*`). Mixing them in wrong fields will fail schema validation.
@@ -388,13 +388,13 @@ Events with `ticks_since_activation` triggers fire automatically without player
**Wrong:**
```yaml
# kael_goes_cold fires automatically at tick 300, sets kael_behavior_changed
# friend_goes_cold fires automatically at tick 300, sets friend_behavior_changed
# This expiry can never fire after tick 300
- outcome_id: module_abandoned
is_expiry: true
conditions:
flags_not_set:
- kael_behavior_changed # This flag is always set by tick 300
- friend_behavior_changed # This flag is always set by tick 300
ticks_since_activation: 5400
```
@@ -405,8 +405,8 @@ Events with `ticks_since_activation` triggers fire automatically without player
is_expiry: true
conditions:
facts_not_known:
- "ring.cargo_discrepancy_pattern" # Only known if player examined terminal
- "ring.kael_unauthorized_corridor_access" # Only known if player observed Kael
- "{module}.cargo_discrepancy_pattern" # Only known if player examined terminal
- "{module}.friend_unauthorized_location" # Only known if player observed THE FRIEND
ticks_since_activation: 5400
```
@@ -419,7 +419,7 @@ Events with `ticks_since_activation` triggers fire automatically without player
- [ ] `min_play_ticks` ≥ 1800 (30 minutes at 1 tick/second)
- [ ] Every event sequence step has at least one tick-based trigger
- [ ] Every `fact_becomes_discoverable` effect has a `discovery_method` note
- [ ] The module includes at least one named FRIEND-pattern NPC (for v0.1 modules)
- [ ] The module includes at least one named FRIEND-pattern NPC
- [ ] Expiry outcome is present (`is_expiry: true`) with conditions gated on `facts_not_known`, NOT `flags_not_set`
- [ ] All outcomes have been reviewed for moral ambiguity — no "obviously correct" resolution
- [ ] `npc_requirements` covers every role referenced in events and outcomes
@@ -439,10 +439,10 @@ Events with `ticks_since_activation` triggers fire automatically without player
| Vertical slice scope | `decisions/scope.md` D-027 |
| Population ratios | `decisions/content.md` D-029 |
| THE FRIEND pattern | `decisions/content.md` D-034 |
| Smuggling ring module | `content/modules/tier1/smuggling_ring_v0_1.yaml` |
| Module pool | `content/modules/tier1/` |
| Drama module schema | `content/schemas/drama_module.schema.yaml` |
| Fact catalog | `content/global/knowledge/` |
| NPC profiles (v0.1) | `content/campaigns/main/systems/van-maanens-star/` |
| NPC profiles | `content/campaigns/main/systems/{system-slug}/` |
| Storyteller stub | `server/src/storyteller/mod.rs` |
---
wiki/concepts/entity-attributes.md
+46 -46
View File
@@ -38,11 +38,11 @@ The knowledge graph uses these attributes to determine:
**Value format**: Full name as known to the observer.
**Examples**:
- `"Kael Davan"` — observer knows full name
- `"Kael"` — observer knows first name only
- `"{NPC Full Name}"` — observer knows full name
- `"{First Name}"` — observer knows first name only
- `"the dock worker"` — observer doesn't know name, only role
**Usage**: Monologue and dialogue rendering. If `name` is absent or generic, monologue says "the dock worker" instead of "Kael."
**Usage**: Monologue and dialogue rendering. If `name` is absent or generic, monologue uses role description.
---
@@ -66,7 +66,7 @@ The knowledge graph uses these attributes to determine:
**Value format**: Institutional or organizational allegiance.
**Examples**:
- `"Commission"` — Sera, Torek, Detective
- `"Commission"` — institutional contacts, inspectors, detective
- `"civilian"` — most NPCs
- `"ring member"` — if discovered
- `"unknown"` — not yet determined
@@ -77,13 +77,13 @@ The knowledge graph uses these attributes to determine:
### `species`
**Value format**: Species identifier (future-proofing — v0.1 is all human).
**Value format**: Species identifier.
**Examples**:
- `"human"` (default)
- (Future: other species as defined)
**Usage**: Not load-bearing in v0.1. Placeholder for future non-human NPCs.
**Usage**: Future-proofing for non-human NPCs.
---
@@ -94,11 +94,11 @@ The knowledge graph uses these attributes to determine:
**Value format**: Relationship category from observer's perspective.
**Examples**:
- `"colleague"` — Kael to smuggler
- `"friend"` — Sera to detective
- `"authority figure"` — Voss to subordinates
- `"suspect"` — Kael to detective (post-discovery)
- `"partner"` — Naia to Kael
- `"colleague"` — ring member to fellow ring member
- `"friend"` — institutional contact to detective
- `"authority figure"` — shift supervisor to subordinates
- `"suspect"` — ring member to detective (post-discovery)
- `"partner"` — non-ring partner to ring member
- `"stranger"` — new NPCs
**Usage**: Drives `RelationshipState` calculation (Unknown/Known/Friendly/PersonOfInterest/Hostile). Determines emotional tone of monologue.
@@ -142,9 +142,9 @@ The knowledge graph uses these attributes to determine:
**Value format**: Comma-separated behavioral observations.
**Examples**:
- `"nervous,lattice_checking"` — Kael during contradiction arc
- `"avoidance_pattern,evasive"` — Sera avoiding Torek
- `"spending_beyond_means"` — Torek buying rounds
- `"nervous,lattice_checking"` — ring member showing stress during contradiction arc
- `"avoidance_pattern,evasive"` — contact avoiding a suspect
- `"spending_beyond_means"` — inspector buying rounds on a dock worker's income
- `"reliable,punctual"` — baseline normal behavior
**Usage**: Tell system. Multiple flags accumulate as evidence. Detective's analytical lattice auto-flags some behaviors.
@@ -158,11 +158,11 @@ The knowledge graph uses these attributes to determine:
**Value format**: What the observer believes gives them (or could give them) power over this entity. This covers secrets, debts, promises, obligations, and compromising positions — not just secrets. Any information or relationship that creates asymmetric power over the target qualifies as leverage.
**Examples**:
- `"ring membership"` — detective's suspicion about Kael (secret)
- `"unreported evidence"` — smuggler's read on Sera (concealed information)
- `"gambling debt"` — if Drin's vulnerability is discovered (financial obligation)
- `"exit attempt"` — if Kael's unauthorized contact is discovered (betrayal)
- `"owes favor to Voss"` — social obligation
- `"ring membership"` — detective's suspicion about a cargo handler (secret)
- `"unreported evidence"` — smuggler's read on an institutional contact (concealed information)
- `"gambling debt"` — if a peripheral member's vulnerability is discovered (financial obligation)
- `"exit attempt"` — if a ring member's unauthorized contact is discovered (betrayal)
- `"owes favor to supervisor"` — social obligation
- `"witnessed the handoff"` — compromising position
**Usage**: Drives PersonOfInterest state. Gates confrontation dialogue. Smuggler and detective track different leverage about the same NPCs. The broader scope (beyond secrets) allows content authors to capture debts, promises, and obligations that create power dynamics without requiring additional keys.
@@ -189,8 +189,8 @@ The knowledge graph uses these attributes to determine:
**Value format**: Specific tell noted by the observer.
**Examples**:
- `"looks left when lying"` — Kael's tell
- `"leaves when Torek arrives"` — Sera's avoidance
- `"looks left when lying"` — ring member's tell
- `"leaves when inspector arrives"` — contact's avoidance
- `"checks lattice before answering"` — nervous behavior
- `"forced casualness after shift supervisor passes"` — hypervigilance
@@ -205,9 +205,9 @@ The knowledge graph uses these attributes to determine:
**Value format**: Boolean-ish flag (presence of key = true).
**Examples**:
- `"meeting_unknown_contact"` — Kael contradiction
- `"avoidance_inconsistency"` — Sera contradiction
- `"manifest_access_mismatch"` — Maret handling cargo she shouldn't process
- `"meeting_unknown_contact"` — {THE FRIEND} smuggler path contradiction
- `"avoidance_inconsistency"` — {THE FRIEND} detective path contradiction
- `"manifest_access_mismatch"` — manifest clerk handling cargo they shouldn't process
**Usage**: THE FRIEND arc trigger. When this attribute is set, monologue tone shifts. Dialogue options change. RelationshipState moves toward PersonOfInterest.
@@ -226,9 +226,9 @@ These four keys capture the observer's subjective assessment of the target throu
**Values**: `none`, `low`, `moderate`, `high`, `critical`.
**Examples**:
- Smuggler's assessment of Pell (wavering member) = `"high"` (unpredictable, could expose the ring)
- Detective's assessment of Voss = `"moderate"` (obstructive but not directly dangerous)
- Smuggler's assessment of Naia = `"low"` (uninvolved, unlikely to cause exposure)
- Smuggler's assessment of a wavering ring member = `"high"` (unpredictable, could expose the ring)
- Detective's assessment of the shift supervisor = `"moderate"` (obstructive but not directly dangerous)
- Smuggler's assessment of an uninvolved partner = `"low"` (unlikely to cause exposure)
**Usage**: Gates operational monologue. High-risk targets trigger cautionary internal dialogue. Critical-risk targets may trigger evasion or preemptive action. The nature of "risk" depends on the archetype (see interpretation note).
@@ -241,9 +241,9 @@ These four keys capture the observer's subjective assessment of the target throu
**Values**: `solid`, `dependable`, `uncertain`, `wavering`, `hostile`.
**Examples**:
- Smuggler's assessment of Renn (courier) = `"dependable"` (reliable, follows instructions)
- Smuggler's assessment of Kael (mid-game) = `"wavering"` (showing signs of doubt)
- Detective's assessment of Sera = `"solid"` (committed to the investigation)
- Smuggler's assessment of the courier = `"dependable"` (reliable, follows instructions)
- Smuggler's assessment of {THE FRIEND} mid-game = `"wavering"` (showing signs of doubt)
- Detective's assessment of their institutional contact = `"solid"` (committed to the investigation)
**Usage**: Determines how much the observer relies on or confides in the target. Wavering loyalty triggers monitoring behavior. Hostile loyalty triggers defensive or adversarial posture.
@@ -256,7 +256,7 @@ These four keys capture the observer's subjective assessment of the target throu
**Values**: `solid`, `thin`, `cracking`, `blown`, `N/A`.
**Examples**:
- Ring member's assessment of Kael = `"thin"` (behavior changes are visible to anyone watching)
- Ring member's assessment of a compromised colleague = `"thin"` (behavior changes are visible to anyone watching)
- Smuggler's self-assessment near the detective = `"cracking"` (too many close calls)
- Detective's assessment of a civilian witness = `"N/A"` (no cover to assess)
@@ -271,13 +271,13 @@ These four keys capture the observer's subjective assessment of the target throu
**Values**: `innocent`, `peripheral`, `complicit`, `compromised`, `willing`.
**Examples**:
- Detective's assessment of Naia = `"innocent"` (uninvolved partner caught in the fallout)
- Smuggler's assessment of Drin = `"compromised"` (dragged in by debt, not by choice)
- Smuggler's assessment of Torek = `"willing"` (fully aware, actively participating)
- Detective's assessment of an uninvolved partner = `"innocent"` (caught in the fallout)
- Smuggler's assessment of a debt-dragged peripheral = `"compromised"` (dragged in by debt, not by choice)
- Smuggler's assessment of the compromised inspector = `"willing"` (fully aware, actively participating)
**Usage**: Shapes the observer's moral arc and internal conflict. Monologue tone shifts when the observer assigns moral weight — guilt, justification, and rationalization are driven by this key. The Comfort-Doubt-Reckoning-Compromise arc references `moral_weight` to determine which phase the observer occupies relative to specific NPCs.
**Archetype note**: Both smuggler and detective use `moral_weight` with the same enum values but different criteria. The smuggler assesses complicity in the ring's operations ("how dirty are their hands?") — see [Smuggler Moral Arc](../../design/smuggler-moral-arc.md). The detective assesses culpability in the crime ("how responsible are they for the harm?"). Same scale, different lens. A smuggler might mark Drin as `"compromised"` (dragged in, not choosing) while the detective marks Drin as `"complicit"` (he knew and did nothing). The detective's moral arc spec is unwritten in v0.1 but follows the same key.
**Archetype note**: Both smuggler and detective use `moral_weight` with the same enum values but different criteria. The smuggler assesses complicity in the ring's operations ("how dirty are their hands?") — see [Smuggler Moral Arc](../../design/smuggler-moral-arc.md). The detective assesses culpability in the crime ("how responsible are they for the harm?"). Same scale, different lens. A smuggler might mark a debt-driven peripheral as `"compromised"` (dragged in, not choosing) while the detective marks the same NPC as `"complicit"` (they knew and did nothing).
---
@@ -298,7 +298,7 @@ This pattern scales to all 8 planned archetypes without schema modification. An
## Examples: Full EntityKnowledge Entries
### Smuggler's knowledge of Kael (early game, pre-contradiction)
### Smuggler's knowledge of {THE FRIEND} (early game, pre-contradiction)
```rust
EntityKnowledge {
@@ -310,7 +310,7 @@ EntityKnowledge {
state: KnowledgeState::Active,
relationship: RelationshipState::Friendly,
known_attributes: BTreeMap::from([
("name".to_string(), "Kael Davan".to_string()),
("name".to_string(), "{NPC Full Name}".to_string()),
("role".to_string(), "dock worker".to_string()),
("faction".to_string(), "ring member".to_string()), // smuggler knows
("species".to_string(), "human".to_string()),
@@ -318,7 +318,7 @@ EntityKnowledge {
("trust_level".to_string(), "trusted".to_string()),
("routine_pattern".to_string(), "morning shift 06:00-14:00, bar after shift".to_string()),
("behavior_flags".to_string(), "reliable,punctual".to_string()),
("risk_assessment".to_string(), "low".to_string()), // Kael is reliable, no exposure concern
("risk_assessment".to_string(), "low".to_string()), // reliable, no exposure concern
("loyalty_assessment".to_string(), "solid".to_string()), // loyal to the ring
("position_integrity".to_string(), "solid".to_string()), // cover is intact
("moral_weight".to_string(), "willing".to_string()), // fully aware, active participant
@@ -326,7 +326,7 @@ EntityKnowledge {
}
```
### Detective's knowledge of Kael (mid-game, post-contradiction discovery)
### Detective's knowledge of a suspect (mid-game, post-contradiction discovery)
```rust
EntityKnowledge {
@@ -343,7 +343,7 @@ EntityKnowledge {
state: KnowledgeState::Active,
relationship: RelationshipState::PersonOfInterest, // flagged
known_attributes: BTreeMap::from([
("name".to_string(), "Kael Davan".to_string()),
("name".to_string(), "{NPC Full Name}".to_string()),
("role".to_string(), "dock worker".to_string()),
("faction".to_string(), "civilian".to_string()), // detective doesn't know ring membership yet
("species".to_string(), "human".to_string()),
@@ -357,13 +357,13 @@ EntityKnowledge {
("contradiction_flagged".to_string(), "meeting_unknown_contact".to_string()),
("risk_assessment".to_string(), "high".to_string()), // obstructing investigation, potential flight risk
("loyalty_assessment".to_string(), "hostile".to_string()), // uncooperative, evasive
("position_integrity".to_string(), "cracking".to_string()), // his story is falling apart
("position_integrity".to_string(), "cracking".to_string()), // their story is falling apart
("moral_weight".to_string(), "complicit".to_string()), // involved, degree of responsibility unclear
]),
}
```
### Smuggler's knowledge of Sera (if observant, mid-game)
### Smuggler's knowledge of the institutional contact (if observant, mid-game)
```rust
EntityKnowledge {
@@ -373,9 +373,9 @@ EntityKnowledge {
confidence: KnowledgeConfidence::KnowsOf,
source: KnowledgeSource::DirectObservation { tick: 1800 },
state: KnowledgeState::Active,
relationship: RelationshipState::Known, // not Friendly -- smuggler doesn't know Sera well
relationship: RelationshipState::Known, // not Friendly -- smuggler doesn't know them well
known_attributes: BTreeMap::from([
("name".to_string(), "Sera Venn".to_string()),
("name".to_string(), "{Institutional Contact Name}".to_string()),
("role".to_string(), "Commission field tech".to_string()),
("faction".to_string(), "Commission".to_string()),
("species".to_string(), "human".to_string()),
@@ -383,11 +383,11 @@ EntityKnowledge {
("trust_level".to_string(), "uncertain".to_string()),
("routine_pattern".to_string(), "bar regular, off-duty evenings".to_string()),
("behavior_flags".to_string(), "observant,avoidance_pattern".to_string()),
("leverage_held".to_string(), "knows something about Torek or Naia".to_string()),
("leverage_held".to_string(), "knows something about the inspector or someone close to the ring".to_string()),
("leverage_confidence".to_string(), "suspected".to_string()),
("risk_assessment".to_string(), "moderate".to_string()), // Commission presence is inherently risky
("loyalty_assessment".to_string(), "uncertain".to_string()), // unknown allegiance
("position_integrity".to_string(), "N/A".to_string()), // Sera isn't maintaining a cover
("position_integrity".to_string(), "N/A".to_string()), // not maintaining a cover
("moral_weight".to_string(), "peripheral".to_string()), // not involved in ring, but near it
]),
}
wiki/concepts/fact-catalog.md
+88 -88
View File
@@ -1,6 +1,6 @@
---
title: "Knowledge Fact Catalog"
description: "All 27 canonical FactIds for v0.1 with confidence progressions, smuggler/detective starting levels, and mechanical purposes"
description: "Canonical FactIds for smuggling scenario content — confidence progressions, character starting levels, and mechanical purposes"
slug: fact-catalog
category: concept
status: canonical
@@ -14,7 +14,7 @@ cross_refs: []
# Knowledge Fact Catalog
Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.topic` format defined in `server/src/knowledge/types.rs`.
Canonical FactIds for smuggling scenario content. All facts follow the `category.topic` format defined in `server/src/knowledge/types.rs`.
## Format
@@ -31,14 +31,14 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
**Suspects**: "Something's going on with the cargo schedules. Too many off-manifest deliveries."
**KnowsOf**: "There's a smuggling operation running through the logistics hub."
**KnowsDetails**: "The ring moves unlicensed lattice components during shift transitions. Voss manages the timing."
**KnowsDetails**: "The ring moves unlicensed lattice components during shift transitions. The shift supervisor manages the timing."
**Direct**: N/A (abstract knowledge -- never directly observed)
**Mechanical Purpose**: Gates investigation dialogue trees. Required for ring-specific monologue. The detective starts at Suspects and escalates. The smuggler (if playing the ring member path) starts at KnowsDetails.
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "Our operation. Nils runs coordination, Voss covers the schedule, Kael and I handle cargo. Two years now. Runs like clockwork when everyone hits their marks."
**KnowsDetails**: "Our operation. The coordinator runs things off-site, the shift supervisor covers the schedule, and I handle cargo. Two years now. Runs like clockwork when everyone hits their marks."
---
@@ -76,52 +76,52 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
### `contraband.severance_tech`
**Suspects**: "Sealed containers Nils won't discuss. Heavier than lattice components."
**Suspects**: "Sealed containers the coordinator won't discuss. Heavier than lattice components."
**KnowsOf**: "Severance equipment. Counter-surveillance tech. Illegal across most of the Reach."
**KnowsDetails**: "Guardians of Severance supply chain. This isn't local -- it's connected to something bigger."
**Direct**: N/A (not directly visible in v0.1)
**KnowsDetails**: "Guardians of Autonomy supply chain. This isn't local -- it's connected to something bigger."
**Direct**: N/A (not directly visible in the early arc)
**Mechanical Purpose**: Contamination seed for storyteller expansion. The thing that makes the smuggler question how deep the ring goes.
**Smuggler Starting Level**: Suspects
**Smuggler Perspective**:
**Suspects**: "Sealed containers Nils won't talk about. Different markings, heavier than lattice mods. He said don't ask. So I don't ask."
**KnowsOf**: "Severance gear. Counter-surveillance equipment. Whoever Nils is supplying, it's not just local lattice demand."
**KnowsDetails**: "Guardians of Severance supply chain. Nils has been using us as a distribution point for something I didn't sign up for. This is bigger than Sova."
**Suspects**: "Sealed containers the coordinator won't talk about. Different markings, heavier than lattice mods. Told me don't ask. So I don't ask."
**KnowsOf**: "Severance gear. Counter-surveillance equipment. Whoever the coordinator is supplying, it's not just local lattice demand."
**KnowsDetails**: "Guardians of Autonomy supply chain. We've been used as a distribution point for something I didn't sign up for. This is bigger than this district."
---
### `contraband.supply_chain`
**Suspects**: "The cargo doesn't originate on this station."
**KnowsOf**: "Off-station coordinator manages incoming shipments. Someone named Sabel."
**KnowsDetails**: "Supply chain: aftermarket manufacturers (Syndic-adjacent) -> freight networks -> Sabel (off-station) -> ring coordinator (Devra or Nils) -> local distribution."
**KnowsOf**: "Off-station coordinator manages incoming shipments."
**KnowsDetails**: "Supply chain: aftermarket manufacturers (Syndic-adjacent) -> freight networks -> off-station coordinator -> local coordinator -> distribution."
**Direct**: N/A (network knowledge)
**Mechanical Purpose**: Investigation depth. Detective at KnowsDetails can map the full chain. Smuggler at KnowsDetails understands their position in the network.
**Smuggler Starting Level**: KnowsOf
**Smuggler Perspective**:
**KnowsOf**: "Cargo comes through Sabel, off-station. Sabel handles the incoming shipments, we handle local. What happens upstream, I don't ask."
**KnowsDetails**: "Syndic-adjacent manufacturers, freight networks, Sabel, then Nils or Devra, then us. I'm a link in a chain I can't see the end of."
**KnowsOf**: "Cargo comes through the off-station coordinator. They handle the incoming shipments, we handle local. What happens upstream, I don't ask."
**KnowsDetails**: "Syndic-adjacent manufacturers, freight networks, the off-station coordinator, then local distribution, then us. I'm a link in a chain I can't see the end of."
---
## Location Facts
### `location.corridor_b7_restricted`
### `location.restricted_corridor`
**Suspects**: "Corridor B-7 should see foot traffic during shift change. It's empty."
**Suspects**: "The maintenance corridor should see foot traffic during shift change. It's empty."
**KnowsOf**: "Maintenance corridor used for smuggling operations. Access requires hub clearance."
**KnowsDetails**: "Corridor B-7 is between old and new prefab sections. Service hatch from break room. The ring routes shipments through here during shift transitions."
**Direct**: "I'm in Corridor B-7 right now. Old construction smell, minimal Meridian coverage, no surveillance."
**KnowsDetails**: "The corridor runs between old and new prefab sections. Service hatch from break room. The ring routes shipments through here during shift transitions."
**Direct**: "I'm in the restricted corridor right now. Old construction smell, minimal Meridian coverage, no surveillance."
**Mechanical Purpose**: Spatial knowledge. Required for investigation progression (detective) and operational planning (smuggler). Direct confidence gates monologue about current surroundings.
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "B-7. Between the old and new panels. Service hatch from the break room gets you in. No Meridian, no cameras. Our corridor."
**Direct**: "In B-7 right now. Stale air, maintenance lighting. The usual."
**KnowsDetails**: "Between the old and new panels. Service hatch from the break room gets you in. No Meridian, no cameras. Our corridor."
**Direct**: "In the corridor right now. Stale air, maintenance lighting. The usual."
---
@@ -129,15 +129,15 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
**Suspects**: "Cargo movements don't match the official routing."
**KnowsOf**: "The ring uses a specific path: freight bay -> service corridor -> temporary storage -> bar district back room."
**KnowsDetails**: "Timing is critical. The route only works during shift transition when patrol coverage thins. Lera provides the final handoff point."
**Direct**: "Watching the route right now. Kosse moving a container through the service hatch."
**KnowsDetails**: "Timing is critical. The route only works during shift transition when patrol coverage thins. The bar provides the final handoff point."
**Direct**: "Watching the route right now. The courier moving a container through the service hatch."
**Mechanical Purpose**: Investigation mechanics. Detective needs KnowsOf to predict NPC movements. Smuggler needs KnowsDetails for operational participation.
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "Freight bay to service corridor to temp storage to Lera's back room. Twenty-minute window during shift change. The route runs itself when everyone hits their marks."
**Direct**: "Watching the handoff. Renn's moving through the service hatch now. Clean."
**KnowsDetails**: "Freight bay to service corridor to temp storage to the bar back room. Twenty-minute window during shift change. The route runs itself when everyone hits their marks."
**Direct**: "Watching the handoff. The courier moving through the service hatch now. Clean."
---
@@ -145,31 +145,31 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
**Suspects**: "Some areas feel less monitored than others."
**KnowsOf**: "Meridian coverage degrades in older sections. Maintenance corridors have minimal surveillance."
**KnowsDetails**: "Corridor B-7, break room service hatch, bar back room -- all Meridian dead spots. The ring exploits these systematically."
**KnowsDetails**: "The restricted corridor, break room service hatch, bar back room -- all Meridian dead spots. The ring exploits these systematically."
**Direct**: "Checking my lattice overlay now. Zero Meridian signal in this section."
**Mechanical Purpose**: Stealth and observation mechanics. Detective's augmented lattice can detect coverage gaps (requires KnowsOf). Smuggler uses gaps operationally (requires KnowsDetails).
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "B-7, the break room hatch, Lera's back room -- all dead spots. Old construction left the gaps. We just learned the map."
**KnowsDetails**: "The restricted corridor, the break room hatch, the bar back room -- all dead spots. Old construction left the gaps. We just learned the map."
**Direct**: "No signal here. Same as always."
---
### `location.dead_drop_location`
**Suspects**: "Kael leaves things in the break room locker area. Not his own locker."
**KnowsOf**: "Locker 47 in the hub break room. Unofficial dead drop for small items."
**KnowsDetails**: "Locker 47 is registered to a worker who transferred off-station 18 months ago. Never reassigned. The ring has used it ever since."
**Direct**: "Locker 47 is open. There's a sealed packet inside."
**Suspects**: "A ring member leaves things in the break room locker area. Not their own locker."
**KnowsOf**: "An inactive locker in the hub break room. Unofficial dead drop for small items."
**KnowsDetails**: "The locker is registered to a worker who transferred off-station over a year ago. Never reassigned. The ring has used it ever since."
**Direct**: "The locker is open. There's a sealed packet inside."
**Mechanical Purpose**: Discovery mechanic. Detective can discover through observation (Suspects -> KnowsOf). Smuggler knows from background (starts at KnowsDetails).
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "Locker 47. Break room. Registered to someone who left a year and a half ago. Small items, messages, keys. Don't use it for actual cargo."
**Direct**: "47's open. Sealed packet. Not mine -- someone else has been using it."
**KnowsDetails**: "Break room. Dead locker, registered to someone who left over a year ago. Small items, messages, keys. Don't use it for actual cargo."
**Direct**: "Locker's open. Sealed packet. Not mine -- someone else has been using it."
---
@@ -179,29 +179,29 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
**Suspects**: "Cargo manifests have inconsistencies. Weight doesn't match volume."
**KnowsOf**: "Systematic manifest doctoring. Someone with freight scheduler access is altering records."
**KnowsDetails**: "Maret Korr processes manifests. She's noticed the discrepancies but hasn't reported them. She's either complicit or terrified."
**KnowsDetails**: "The manifest clerk processes the documents. They've noticed the discrepancies but haven't reported them. Either complicit or terrified."
**Direct**: "Comparing the manifest right now. Container 4471 -- logged weight 240kg, actual weight closer to 310kg."
**Mechanical Purpose**: Core investigation mechanic. Detective's analytical lattice flags discrepancies at Suspects. Full understanding requires KnowsDetails. Smuggler knows Maret's position from background.
**Mechanical Purpose**: Core investigation mechanic. Detective's analytical lattice flags discrepancies at Suspects. Full understanding requires KnowsDetails. Smuggler knows the clerk's position from background.
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "Maret handles the manifests. She adjusts the numbers for us -- or at least doesn't flag them. Whether she's on board or just scared, the result's the same."
**KnowsDetails**: "The clerk handles the manifests. Adjusts the numbers for us -- or at least doesn't flag them. Whether they're on board or just scared, the result's the same."
---
### `investigation.shift_mismatch`
**Suspects**: "Night shift schedules don't align with freight volume."
**KnowsOf**: "Voss adjusts shift schedules to create coverage gaps. Deliberate understaffing during high-risk windows."
**KnowsDetails**: "Shift mismatches occur every third rotation. Coincides exactly with off-station shipment arrivals. Voss takes a cut."
**KnowsOf**: "The shift supervisor adjusts schedules to create coverage gaps. Deliberate understaffing during high-risk windows."
**KnowsDetails**: "Shift mismatches occur every third rotation. Coincides exactly with off-station shipment arrivals. The supervisor takes a cut."
**Direct**: "Checking the current schedule. Night shift is short two workers -- again."
**Mechanical Purpose**: Pattern recognition. Detective needs KnowsOf to connect schedule to smuggling. Smuggler knows the pattern operationally.
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "Voss thins the rotation every third cycle. Two short on nights, right when Sabel's shipment comes in. Not a coincidence -- it's the plan. Voss takes his cut."
**KnowsDetails**: "The supervisor thins the rotation every third cycle. Two short on nights, right when the shipment comes in. Not a coincidence -- it's the plan. The supervisor takes their cut."
---
@@ -209,22 +209,22 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
**Suspects**: "That container sat in temporary storage for 18 hours. Standard procedure is 4-6 hours max."
**KnowsOf**: "Delayed processing indicates off-manifest handling. Someone's buying time to repackage cargo."
**KnowsDetails**: "Nils coordinates timing. Container arrives, sits in temp storage during shift A, gets repackaged during shift B transition, moves out during shift C startup."
**KnowsDetails**: "The coordinator handles timing. Container arrives, sits in temp storage during shift A, gets repackaged during shift B transition, moves out during shift C startup."
**Direct**: "Container 4471 has been sitting here for 14 hours. No movement orders logged."
**Mechanical Purpose**: Observation-based discovery. Detective builds case from Suspects upward. Smuggler knows the workflow (starts KnowsDetails).
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "Container arrives, sits in temp during A shift, gets repackaged during B transition, moves out during C startup. Nils handles the timing. I handle the routing. Clockwork."
**KnowsDetails**: "Container arrives, sits in temp during A shift, gets repackaged during B transition, moves out during C startup. The coordinator handles the timing. I handle the routing. Clockwork."
---
### `investigation.evidence_collected`
**Suspects**: N/A (binary fact -- you either have evidence or you don't)
**KnowsOf**: "I have documented manifest discrepancies, shift schedule anomalies, and witness testimony from Drin."
**KnowsDetails**: "Full case file: manifest logs, Drin's testimony under pressure, Maret's reluctant cooperation, surveillance footage from observation gallery showing Corridor B-7 access."
**KnowsOf**: "I have documented manifest discrepancies, shift schedule anomalies, and witness testimony."
**KnowsDetails**: "Full case file: manifest logs, witness testimony under pressure, the manifest clerk's reluctant cooperation, surveillance footage showing restricted corridor access."
**Direct**: N/A (abstract accumulation)
**Mechanical Purpose**: Investigation state tracker. Gates confrontation dialogue. Detective-specific -- smuggler doesn't collect evidence against themselves. (Smuggler equivalent: `progress.operation_compromised`.)
@@ -261,24 +261,24 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
**Smuggler Starting Level**: Suspects
**Smuggler Perspective**:
**Suspects**: "Cargo's not local. Different seals, different packaging. Someone manufacturing off-station."
**KnowsOf**: "Syndic supply chain. Medical-grade lattice parts diverted from legitimate production. Sabel's our connection point."
**KnowsOf**: "Syndic supply chain. Medical-grade lattice parts diverted from legitimate production. The off-station coordinator is our connection point."
**KnowsDetails**: "Two sources, based on the serial patterns. The Syndics aren't partners -- they're wholesalers. We're downstream, and we're replaceable."
---
### `world.sova_district_layout`
### `world.district_layout`
**Suspects**: "The district is a mix of old and new construction."
**KnowsOf**: "40-year-old prefab base with retrofitted partitions. Logistics hub, bar district, residential sections. Meridian coverage is uneven."
**KnowsDetails**: "Older sections have hidden spaces between wall layers. Service corridors from original construction still exist but aren't on current maps. The ring exploits architectural legacy."
**Direct**: "I'm looking at the district map overlay right now. Official layout vs. actual structure don't match in Section 3."
**Direct**: "I'm looking at the district map overlay right now. Official layout vs. actual structure don't match in the old section."
**Mechanical Purpose**: Navigation and investigation. Detective needs KnowsDetails to find hidden spaces. Smuggler starts with KnowsOf (knows layout from living here).
**Smuggler Starting Level**: KnowsOf
**Smuggler Perspective**:
**KnowsOf**: "Forty-year-old prefab, retrofitted to hell. The hub, Lera's, residential blocks. I know every corridor by feel. Meridian's patchy in the old sections."
**KnowsDetails**: "Hidden spaces between old walls in Section 3. Service corridors from original construction, not on any current map. The ring uses what the builders left behind."
**KnowsOf**: "Forty-year-old prefab, retrofitted to hell. The hub, the bar, residential blocks. I know every corridor by feel. Meridian's patchy in the old sections."
**KnowsDetails**: "Hidden spaces between old walls in the original construction zones. Service corridors not on any current map. The ring uses what the builders left behind."
---
@@ -286,14 +286,14 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
**Suspects**: "Logistics hub runs three shifts: morning, day, night."
**KnowsOf**: "Shift transitions are 30-minute windows with reduced oversight. Ring operations happen during transitions."
**KnowsDetails**: "Shift A: 06:00-14:00. Shift B: 14:00-22:00. Shift C: 22:00-06:00. Transition windows: 13:30-14:30, 21:30-22:30, 05:30-06:30. Voss manages the schedule."
**KnowsDetails**: "Shift A: 06:00-14:00. Shift B: 14:00-22:00. Shift C: 22:00-06:00. Transition windows: 13:30-14:30, 21:30-22:30, 05:30-06:30. The shift supervisor manages the schedule."
**Direct**: "Current time: 21:45. Shift transition active. Observing movement patterns."
**Mechanical Purpose**: Temporal mechanics. Required for NPC routine prediction and investigation timing. Smuggler starts KnowsDetails. Detective learns through observation.
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "A shift: 06:00 to 14:00. B shift: 14:00 to 22:00. C shift: 22:00 to 06:00. Thirty-minute transitions. That's when the oversight thins and the route opens. Voss keeps it thin."
**KnowsDetails**: "A shift: 06:00 to 14:00. B shift: 14:00 to 22:00. C shift: 22:00 to 06:00. Thirty-minute transitions. That's when the oversight thins and the route opens. The supervisor keeps it thin."
**Direct**: "Transition's active. Twenty minutes of open corridor. Time to move."
---
@@ -302,65 +302,65 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
### `relationship.ring_membership`
**Suspects**: "Kael's behavior suggests involvement in something off-book."
**KnowsOf**: "Kael is a ring member. Mid-level, handles physical cargo."
**KnowsDetails**: "Ring structure: Devra or Nils coordinate, Voss provides scheduling cover, Kael and Kosse handle cargo, Lera provides handoff point, Pell is wavering."
**Direct**: "Watching Kael move a container right now. Ring operation in progress."
**Suspects**: "A ring member's behavior suggests involvement in something off-book."
**KnowsOf**: "A mid-level ring member handles physical cargo."
**KnowsDetails**: "Ring structure: coordinators manage the operation, the shift supervisor provides scheduling cover, cargo handlers move product, the bar owner provides a handoff point, and at least one member is wavering."
**Direct**: "Watching a ring member route a container right now. Operation in progress."
**Mechanical Purpose**: Social knowledge. Detective builds this through investigation. Smuggler knows from shared membership (if on that path) or observation.
**Smuggler Starting Level**: KnowsDetails
**Smuggler Perspective**:
**KnowsDetails**: "Nils coordinates from off-site. Devra handles messages. Voss covers the schedule. Kael and I handle cargo. Renn's the courier. Lera runs the handoff point. Pell's been shaky lately -- that worries me."
**Direct**: "Watching Kael work a shipment. We've done this a hundred times. Smooth."
**KnowsDetails**: "The off-station coordinator runs the chain. The local coordinator manages operations. The shift supervisor covers the schedule. Cargo handlers route product. The bar owner runs the handoff point. One member's been shaky lately -- that worries me."
**Direct**: "Watching a ring member work a shipment. We've done this a hundred times. Smooth."
---
### `relationship.kael_naia_connection`
### `relationship.friend_personal_life`
**Suspects**: "Kael mentions a partner. Someone named Naia."
**KnowsOf**: "Kael's partner is Naia, a teacher. They're worried about Kael's late nights."
**KnowsDetails**: "Naia confides in Sera Venn. Sera knows something is wrong but hasn't reported it. The worry is contaminating Kael's operational security."
**Suspects**: "{THE FRIEND} mentions someone outside the ring. A partner."
**KnowsOf**: "{THE FRIEND}'s partner is someone not involved in the operation. They're worried about {THE FRIEND}'s late nights."
**KnowsDetails**: "The partner confides in a mutual contact who has institutional access. That contact knows something is wrong but hasn't reported it. The worry is contaminating {THE FRIEND}'s operational security."
**Direct**: N/A (relationship knowledge)
**Mechanical Purpose**: Emotional leverage. Detective can use Naia as pressure point. Smuggler (if Kael's friend) must protect Naia from knowledge.
**Mechanical Purpose**: Emotional leverage. Detective can use the partner as a pressure point. Smuggler (if {THE FRIEND}'s colleague) must protect the partner from knowledge.
**Smuggler Starting Level**: KnowsOf
**Smuggler Perspective**:
**KnowsOf**: "Naia's Kael's partner. Good person. Worries about him working late. Doesn't know about the ring -- at least that's what Kael says."
**KnowsDetails**: "Naia's been talking to Sera. Sera's Commission. If Naia shares too much and Sera connects the dots, Kael's problem becomes everyone's problem."
**KnowsOf**: "{THE FRIEND}'s partner is good people. Worries about them working late. Doesn't know about the ring -- at least that's what {THE FRIEND} says."
**KnowsDetails**: "The partner's been talking to someone with institutional connections. If that person connects the dots, {THE FRIEND}'s problem becomes everyone's problem."
---
### `relationship.trust_network`
**Suspects**: "People here know each other. Tight social bonds."
**KnowsOf**: "The ring depends on trust networks: Kael trusts Nils (sibling), Lera trusts the regulars, Drin is compromised by debt to Harek."
**KnowsDetails**: "Trust map: Kael <-> Nils (blood), Kael <-> Naia (partnership), Naia <-> Sera (friendship), Sera <-> Detective (professional/personal), Drin -> Harek (debt), Voss -> Devra/Nils (financial)."
**KnowsOf**: "The ring depends on trust networks: the cargo handler trusts the off-station coordinator (prior relationship), the bar owner trusts the regulars, at least one peripheral member is compromised by debt."
**KnowsDetails**: "Trust map: coordinator chain (off-station to local, prior loyalty), {THE FRIEND} to their partner (personal), {THE FRIEND}'s partner to a mutual institutional contact (friendship), compromised peripheral to their creditor (debt), shift supervisor to ring leadership (financial)."
**Direct**: N/A (social network knowledge)
**Mechanical Purpose**: Social manipulation mechanics. Detective at KnowsDetails can exploit trust fractures. Smuggler at KnowsDetails knows whom to protect.
**Smuggler Starting Level**: KnowsOf
**Smuggler Perspective**:
**KnowsOf**: "Kael trusts Nils -- blood. Lera's reliable, keeps her mouth shut. Drin's compromised somehow. Voss is solid as long as the money flows."
**KnowsDetails**: "Full picture: Kael to Nils is blood. Kael to Naia is heart. Naia to Sera is friendship. Drin owes Harek. Voss follows whoever's paying. Pull one thread, the whole thing comes apart."
**KnowsOf**: "The coordinator chain runs on prior loyalty. The bar owner keeps her mouth shut. At least one person's compromised somehow. The shift supervisor is solid as long as the money flows."
**KnowsDetails**: "Full picture: coordinator chain is loyalty. {THE FRIEND} to their partner is personal. The partner to a mutual contact is friendship. The compromised member owes someone. The supervisor follows whoever's paying. Pull one thread, the whole thing comes apart."
---
### `relationship.faction_allegiance`
**Suspects**: "Some people here are Commission-aligned. Others resent the Commission."
**KnowsOf**: "Sera is Commission. Torek Lintar is nominally Commission but lives here. The detective represents institutional authority. Everyone else is civilian."
**KnowsDetails**: "Faction tensions: Commission (Sera, Torek, Detective) vs. ring (Kael, Nils, Kosse, Voss, Lera) vs. civilians (Naia, Maret, Drin, Resha). Drin is compromised between civilian and Commission."
**KnowsOf**: "The institutional contact is Commission. The inspector is nominally Commission but lives in the district. The detective represents institutional authority. Everyone else is civilian."
**KnowsDetails**: "Faction tensions: Commission (institutional contact, inspector, detective) vs. ring (coordinators, cargo handlers, shift supervisor, bar owner) vs. civilians (partners, manifest clerk, peripheral workers). Some civilians are compromised between civilian and Commission."
**Direct**: N/A (political knowledge)
**Mechanical Purpose**: Access tier logic. Explains why NPCs treat characters differently. Detective at KnowsDetails understands institutional barriers.
**Smuggler Starting Level**: KnowsOf
**Smuggler Perspective**:
**KnowsOf**: "Sera's Commission. Torek's Commission-adjacent but lives here, so who knows where he really stands. The new investigator is Commission, full stop. Everyone else is us or civilian."
**KnowsDetails**: "Lines aren't simple. Drin's civilian but compromised. Maret's civilian but knows too much. The detective is Commission sent to investigate. Commission versus ring versus people caught in between -- and nobody gets to be just one thing."
**KnowsOf**: "The institutional contact is Commission. The inspector is Commission-adjacent but lives here, so who knows where they really stand. The new investigator is Commission, full stop. Everyone else is us or civilian."
**KnowsDetails**: "Lines aren't simple. Some civilians are compromised. The manifest clerk knows too much. The detective is Commission sent to investigate. Commission versus ring versus people caught in between -- and nobody gets to be just one thing."
---
@@ -381,7 +381,7 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
**Suspects**: N/A (binary -- investigation is active or it isn't)
**KnowsOf**: "I'm building a case. Evidence collected, witnesses identified, patterns mapped."
**KnowsDetails**: "Case file: manifest logs, Drin testimony, Maret's reluctant cooperation, surveillance data, NPC behavioral analysis. Ready to escalate."
**KnowsDetails**: "Case file: manifest logs, witness testimony, the manifest clerk's reluctant cooperation, surveillance data, NPC behavioral analysis. Ready to escalate."
**Direct**: N/A (meta-knowledge)
**Mechanical Purpose**: Detective arc state. Gates confrontation options. Changes NPC dialogue (they know they're being investigated).
@@ -391,7 +391,7 @@ Canonical FactIds for the v0.1 vertical slice. All facts follow the `category.to
### `progress.confrontation_ready`
**Suspects**: N/A
**KnowsOf**: "I have enough to confront specific NPCs. Kael, Voss, or Lera."
**KnowsOf**: "I have enough to confront specific NPCs — the shift supervisor, the bar owner, or a cargo handler."
**KnowsDetails**: "Full case built. Can confront the ring, turn an informant, or escalate to Commission enforcement."
**Direct**: N/A (meta-knowledge)
@@ -416,12 +416,12 @@ These facts track the smuggler's operational arc. They are the smuggler's equiva
### `progress.operation_compromised`
**Suspects**: "Something feels wrong today. Voss is tenser than usual. Kael's distracted."
**Suspects**: "Something feels wrong today. The shift supervisor is tenser than usual. A ring member's distracted."
**KnowsOf**: "There's pressure on the ring. Someone's asking questions about manifests. The Commission presence isn't routine."
**KnowsDetails**: "The detective isn't here for compliance review. They're building a case. Maret's nervous, Drin might crack, and Kael's doing something unauthorized that makes everything worse."
**KnowsDetails**: "The detective isn't here for compliance review. They're building a case. The manifest clerk's nervous, witnesses might crack, and a ring member's doing something unauthorized that makes everything worse."
**Direct**: N/A (meta-knowledge)
**Mechanical Purpose**: Smuggler arc state. Gates operational monologue, defensive decision-making, and ring NPC dialogue. The smuggler's analog to `progress.initial_suspicion` + `progress.active_investigation`. Escalation triggers: detective asking questions about manifests, ring members reporting close calls, Kael's behavioral shift, Maret's visible anxiety.
**Mechanical Purpose**: Smuggler arc state. Gates operational monologue, defensive decision-making, and ring NPC dialogue. The smuggler's analog to `progress.initial_suspicion` + `progress.active_investigation`. Escalation triggers: detective asking questions about manifests, ring members reporting close calls, a ring member's behavioral shift, the manifest clerk's visible anxiety.
**Discoverable by**: smuggler only.
@@ -430,7 +430,7 @@ These facts track the smuggler's operational arc. They are the smuggler's equiva
### `progress.cover_threatened`
**Suspects**: "That was a close call. The detective looked at me a beat too long."
**KnowsOf**: "I'm on someone's radar. The detective, or Torek, or both. Need to be more careful."
**KnowsOf**: "I'm on someone's radar. The detective, or the inspector, or both. Need to be more careful."
**KnowsDetails**: "They know. Maybe not everything, but enough. My routine's being watched. My associates flagged. My cargo containers noted."
**Direct**: N/A (meta-knowledge)
@@ -442,12 +442,12 @@ These facts track the smuggler's operational arc. They are the smuggler's equiva
### `progress.detective_tracking`
**Suspects**: "New Commission liaison. Showed up a few days ago. Voss mentioned it."
**KnowsOf**: "The detective is investigating freight irregularities. They've been requesting manifests, talking to Maret and Drin. This isn't routine."
**KnowsDetails**: "The detective has evidence. Don't know how much, but enough to make Maret sweat and Drin avoid eye contact. They're close."
**Suspects**: "New Commission liaison. Showed up a few days ago. A ring member mentioned it."
**KnowsOf**: "The detective is investigating freight irregularities. They've been requesting manifests, talking to the manifest clerk and witnesses. This isn't routine."
**KnowsDetails**: "The detective has evidence. Don't know how much, but enough to make the manifest clerk sweat and others avoid eye contact. They're close."
**Direct**: N/A (meta-knowledge)
**Mechanical Purpose**: Smuggler's tracking of the detective's investigation. Inverse of the detective's evidence tracking. The smuggler's monologue shifts from operational confidence to defensive awareness as this fact escalates. Gates ring-related dialogue: at KnowsOf, ring members start discussing countermeasures; at KnowsDetails, Nils may order the smuggler to change routines or go dark.
**Mechanical Purpose**: Smuggler's tracking of the detective's investigation. Inverse of the detective's evidence tracking. The smuggler's monologue shifts from operational confidence to defensive awareness as this fact escalates. Gates ring-related dialogue: at KnowsOf, ring members start discussing countermeasures; at KnowsDetails, the coordinator may order the smuggler to change routines or go dark.
**Discoverable by**: smuggler only.
@@ -459,7 +459,7 @@ These facts track the smuggler's operational arc. They are the smuggler's equiva
- **Confidence levels** are ordered: Suspects < KnowsOf < KnowsDetails < Direct. Use `KnowledgeConfidence::decayed()` for time-based degradation.
- **Direct confidence** is perception-system-managed. Content authors rarely set this manually -- it's automatically assigned when an entity/location is in the observer's LOS.
- **Abstract facts** (e.g., `contraband.ring_exists`, `world.commission_regulations`) never reach Direct -- they're conceptual, not observable.
- **Spatial facts** (e.g., `location.corridor_b7_restricted`) can reach Direct when the observer is physically present.
- **Spatial facts** (e.g., `location.restricted_corridor`) can reach Direct when the observer is physically present.
- **Progression text** is for content authoring reference, not runtime display. Monologue lines reference these facts as prerequisites; they don't display the progression text directly.
- **Smuggler perspective text** follows the smuggler voice register (see [Smuggler Voice Card](../../docs/design/smuggler-voice-card.md)): fragments, first names, feeling-first, concrete, operational. Where the detective discovers facts through investigation, the smuggler often starts with operational knowledge and discovers threats to the operation.
@@ -470,22 +470,22 @@ These facts track the smuggler's operational arc. They are the smuggler's equiva
| `contraband.ring_exists` | KnowsDetails | Suspects | Insider knowledge |
| `contraband.lattice_components` | KnowsDetails | Suspects | Handles the cargo |
| `contraband.medical_grade` | KnowsOf | Suspects | Knows the cargo, reckons with meaning later |
| `contraband.severance_tech` | Suspects | Suspects | Nils won't discuss -- both characters discover |
| `contraband.supply_chain` | KnowsOf | Suspects | Knows Sabel, not full upstream |
| `location.corridor_b7_restricted` | KnowsDetails | Suspects | Uses it regularly |
| `contraband.severance_tech` | Suspects | Suspects | Coordinator won't discuss -- both characters discover |
| `contraband.supply_chain` | KnowsOf | Suspects | Knows off-station contact, not full upstream |
| `location.restricted_corridor` | KnowsDetails | Suspects | Uses it regularly |
| `location.smuggling_route` | KnowsDetails | Suspects | Works the route |
| `location.surveillance_gaps` | KnowsDetails | Suspects | Knows them operationally |
| `location.dead_drop_location` | KnowsDetails | Suspects | Uses Locker 47 |
| `location.dead_drop_location` | KnowsDetails | Suspects | Uses the dead drop |
| `investigation.manifest_discrepancy` | KnowsDetails | Suspects | Creates the discrepancies |
| `investigation.shift_mismatch` | KnowsDetails | Suspects | Part of the operation |
| `investigation.cargo_anomaly` | KnowsDetails | Suspects | Knows the workflow |
| `investigation.evidence_collected` | N/A | Suspects | Detective-only |
| `world.commission_regulations` | KnowsOf | Suspects | Lives under them |
| `world.syndic_supply_chain` | Suspects | Suspects | Knows cargo's off-station, not source |
| `world.sova_district_layout` | KnowsOf | Suspects | Born here, knows lived layout |
| `world.district_layout` | KnowsOf | Suspects | Lives here, knows the lived layout |
| `world.shift_schedule` | KnowsDetails | Suspects | Works the shifts |
| `relationship.ring_membership` | KnowsDetails | Suspects | Is a member |
| `relationship.kael_naia_connection` | KnowsOf | Suspects | Knows Kael's partner through Kael |
| `relationship.friend_personal_life` | KnowsOf | Suspects | Knows {THE FRIEND}'s partner through {THE FRIEND} |
| `relationship.trust_network` | KnowsOf | Suspects | Knows who's who from living there |
| `relationship.faction_allegiance` | KnowsOf | Suspects | Knows the social landscape |
| `progress.operation_compromised` | Suspects | N/A | Smuggler-only arc state |
@@ -494,4 +494,4 @@ These facts track the smuggler's operational arc. They are the smuggler's equiva
---
**Total FactIds**: 27 (5 contraband, 4 location, 4 investigation, 4 world, 4 relationship, 3 detective progress, 3 smuggler progress). 21 existing facts received smuggler-perspective text. 3 new smuggler-specific progress facts added. Sufficient for v0.1 vertical slice. Expandable by adding new categories or topics within existing categories.
**Total FactIds**: 24 (5 contraband, 4 location, 4 investigation, 4 world, 4 relationship, 3 detective progress, 3 smuggler progress). Expandable by adding new categories or topics within existing categories.
wiki/concepts/relationship-states.md
+44 -44
View File
@@ -68,15 +68,15 @@ pub enum RelationshipState {
**What it means**: Positive relationship, trusted. Emotional connection or reliable professional rapport.
**Monologue tone**: Warm, personal. "Good to see Kael. Always reliable."
**Monologue tone**: Warm, personal. "Good to see them. Always reliable."
**Dialogue availability**: Public + peer + insider-tier. Trust-gated content unlocks. Some secret-tier content if relationship deepens.
**Color**: Soft green (same as Known — the distinction is semantic, not visual).
**Typical entities**: THE FRIEND NPCs (Kael to smuggler, Sera to detective), close colleagues, trusted contacts.
**Typical entities**: THE FRIEND NPCs, close colleagues, trusted contacts.
**Why same color as Known**: Visual simplicity for v0.1. Future refinement could add subtle shader variation (warmth, pulse, saturation).
**Why same color as Known**: Visual simplicity in early implementation. Future refinement could add subtle shader variation (warmth, pulse, saturation).
---
@@ -84,7 +84,7 @@ pub enum RelationshipState {
**What it means**: Flagged. Something's wrong. Under observation or suspicion.
**Monologue tone**: Analytical, cautious. "Kael's meeting someone I don't recognize. That's not normal."
**Monologue tone**: Analytical, cautious. "{THE FRIEND}'s meeting someone I don't recognize. That's not normal."
**Dialogue availability**: Shifts. Trust-gated content may become unavailable. Confrontation options unlock.
@@ -108,7 +108,7 @@ pub enum RelationshipState {
**Typical entities**: NPCs who've turned on the player, authority figures during a confrontation gone bad, exposed ring members cornered by the detective.
**Rare in v0.1**: Most NPCs don't reach Hostile. It's the endgame state for failed social maneuvering.
**Rare**: Most NPCs don't reach Hostile. It's the endgame state for failed social maneuvering.
---
@@ -139,93 +139,93 @@ Unknown → Known → PersonOfInterest → Hostile (if confrontation fails)
- Known → PersonOfInterest: Behavioral flags accumulate, tells observed, manifest discrepancy linked to this NPC.
- PersonOfInterest → Hostile: Confrontation attempt rejected, NPC realizes they're under investigation, escalation.
**Example**: Detective observes Kael. Unknown (first sight) → Known (lattice query: "Davan, K., dock worker") → PersonOfInterest (observed in restricted corridor, evasive answers) → Hostile (confrontation: "I know you're involved. You need to cooperate." / Kael: "Stay away from me.").
**Example**: Detective observes a cargo handler. Unknown (first sight) → Known (lattice query: "dock worker, logistics") → PersonOfInterest (observed in restricted corridor, evasive answers) → Hostile (confrontation: "I know you're involved. You need to cooperate." / handler: "Stay away from me.").
---
### THE FRIEND Contradiction Arc (Kael — Smuggler's Perspective)
### THE FRIEND Contradiction Arc (Smuggler's Perspective)
```
Friendly → PersonOfInterest → [resolution: Friendly-but-contaminated OR Hostile]
```
**Phase 1: Friendly (baseline)**
- Kael is the smuggler's trusted colleague.
- {THE FRIEND} is the smuggler's trusted colleague.
- Monologue: fond, casual.
- Color: soft green.
- Dialogue: insider-tier, warm.
**Phase 2: First Crack (still Friendly, but flags accumulating)**
- Behavioral flags: `lattice_checking,distracted`.
- Monologue shifts slightly: "Kael's been quiet lately."
- Monologue shifts slightly: "{THE FRIEND}'s been quiet lately."
- State unchanged (still Friendly), but `EntityKnowledge.known_attributes["behavior_flags"]` updates.
**Phase 3: The Contradiction (Friendly → PersonOfInterest)**
- Trigger: Direct observation of Kael meeting unknown contact in Corridor B-7.
- Trigger: Direct observation of {THE FRIEND} meeting an unknown contact off-route.
- `EntityKnowledge.known_attributes["contradiction_flagged"] = "meeting_unknown_contact"`.
- `RelationshipState` transitions to `PersonOfInterest`.
- Color shifts: soft green → amber.
- Monologue: "That wasn't anyone from our rotation. Kael, what are you doing?"
- Dialogue options change: confrontation unlocks, trust-tier content locks (Kael is evasive).
- Monologue: "That wasn't anyone from our rotation. {THE FRIEND}, what are you doing?"
- Dialogue options change: confrontation unlocks, trust-tier content locks ({THE FRIEND} is evasive).
**Phase 4: Post-Confrontation**
- **Path A (understanding)**: Smuggler confronts Kael gently. Kael confesses: trying to exit the ring to protect Naia. `RelationshipState` remains `PersonOfInterest` but monologue tone shifts to conflicted sympathy. Color stays amber (still a problem), but dialogue reflects empathy.
- **Path B (betrayal)**: Smuggler reports Kael to Nils or pressures Kael harshly. Kael turns defensive. `RelationshipState` → `Hostile`. Color → red. Kael avoids the smuggler, might actively obstruct.
- **Path A (understanding)**: Smuggler confronts {THE FRIEND} gently. {THE FRIEND} confesses: trying to exit the ring to protect someone close to them. `RelationshipState` remains `PersonOfInterest` but monologue tone shifts to conflicted sympathy. Color stays amber (still a problem), but dialogue reflects empathy.
- **Path B (betrayal)**: Smuggler reports {THE FRIEND} to ring leadership or applies harsh pressure. {THE FRIEND} turns defensive. `RelationshipState` → `Hostile`. Color → red. {THE FRIEND} avoids the smuggler, might actively obstruct.
**THE FRIEND pattern**: Friendly → PersonOfInterest is the emotional core. The player trusted Kael. Now Kael is amber. That color shift IS the narrative moment.
**THE FRIEND pattern**: Friendly → PersonOfInterest is the emotional core. The player trusted {THE FRIEND}. Now {THE FRIEND} is amber. That color shift IS the narrative moment.
---
### THE FRIEND Contradiction Arc (Sera — Detective's Perspective)
### THE FRIEND Contradiction Arc (Detective's Perspective)
```
Friendly → PersonOfInterest → [resolution: Friendly-but-contaminated OR Known-distanced OR Hostile]
```
**Phase 1: Friendly (baseline)**
- Sera is the detective's institutional contact and social anchor.
- {THE FRIEND} is the detective's institutional contact and social anchor.
- Monologue: professional warmth, relief.
- Color: soft green.
- Dialogue: peer-tier, cooperative, helpful.
**Phase 2: Pattern Observation (still Friendly, but flags accumulating)**
- Behavioral flags: `avoidance_pattern` (Sera leaves when Torek arrives).
- Monologue: "That's the third time. Sera leaves when Torek shows up."
- Behavioral flags: `avoidance_pattern` ({THE FRIEND} leaves when a suspect arrives).
- Monologue: "That's the third time. {THE FRIEND} leaves when that person shows up."
- State unchanged (still Friendly), but `EntityKnowledge.known_attributes["behavior_flags"]` updates.
**Phase 3: The Contradiction (Friendly → PersonOfInterest)**
- Trigger: Detective asks Sera directly about Torek. Sera deflects unconvincingly.
- Trigger: Detective asks {THE FRIEND} directly about their avoidance. {THE FRIEND} deflects unconvincingly.
- `EntityKnowledge.known_attributes["contradiction_flagged"] = "avoidance_inconsistency"`.
- `EntityKnowledge.known_attributes["secret_held"] = "unreported evidence"` (detective's inference).
- `RelationshipState` transitions to `PersonOfInterest`.
- Color shifts: soft green → amber.
- Monologue: "She's not lying. But she's not telling me everything. Sera, what do you know?"
- Monologue: "They're not lying. But they're not telling me everything. {THE FRIEND}, what do you know?"
- Dialogue options change: pressing questions unlock, casual warmth diminishes.
**Phase 4: Post-Confrontation**
- **Path A (loyalty test)**: Detective confronts Sera about concealment. Sera confesses: sitting on evidence to protect Naia (friend of Sera, partner of Kael). Detective can choose: report Sera (Hostile), use the information without reporting her (PersonOfInterest → Known, relationship damaged), or protect Sera and accept the information gap (PersonOfInterest → Friendly-but-contaminated).
- **Path B (institutional)**: Detective reports Sera immediately. `RelationshipState` → `Hostile`. Sera is reprimanded or reassigned. Color → red. The detective loses their only local ally.
- **Path A (loyalty test)**: Detective confronts {THE FRIEND} about concealment. {THE FRIEND} confesses: sitting on evidence to protect a third party. Detective can choose: report {THE FRIEND} (Hostile), use the information without reporting them (PersonOfInterest → Known, relationship damaged), or protect {THE FRIEND} and accept the information gap (PersonOfInterest → Friendly-but-contaminated).
- **Path B (institutional)**: Detective reports {THE FRIEND} immediately. `RelationshipState` → `Hostile`. {THE FRIEND} is reprimanded or reassigned. Color → red. The detective loses their only local ally.
**THE FRIEND pattern**: The detective's trust in Sera is tested. Amber means "my friend is hiding something." The resolution determines whether the friendship survives.
**THE FRIEND pattern**: The detective's trust in {THE FRIEND} is tested. Amber means "my contact is hiding something." The resolution determines whether the friendship survives.
---
## Contradiction Patterns: Kael + Sera
## Contradiction Patterns: Smuggler vs. Detective Paths
Both THE FRIEND NPCs follow the same structural arc, but the **nature of the contradiction differs**:
| Dimension | Kael (Smuggler's FRIEND) | Sera (Detective's FRIEND) |
|-----------|--------------------------|---------------------------|
| **Contradiction type** | Spatial deviation (meeting unknown contact) | Behavioral avoidance (leaving when Torek arrives) |
| Dimension | {THE FRIEND} — Smuggler Path | {THE FRIEND} — Detective Path |
|-----------|------------------------------|-------------------------------|
| **Contradiction type** | Spatial deviation (meeting unknown contact) | Behavioral avoidance (leaving when a suspect arrives) |
| **Discovery method** | Direct observation in restricted area | Pattern recognition over multiple visits |
| **What they're hiding** | Attempt to exit the ring (protect Naia) | Unreported evidence (protect Naia) |
| **Sympathetic motivation** | Family protection (Naia is Kael's partner) | Friendship loyalty (Naia is Sera's friend) |
| **Naia as connection** | Kael's personal life | Sera's social network |
| **What they're hiding** | Attempt to exit the ring (protect someone close) | Unreported evidence (protect a third party) |
| **Sympathetic motivation** | Personal protection (someone they care about) | Friendship loyalty (mutual third-party connection) |
| **Third-party connection** | {THE FRIEND}'s personal life | {THE FRIEND}'s social network |
| **Color shift timing** | Single observation event (immediate) | Third occurrence (cumulative) |
| **Confrontation stakes** | Ring security vs. personal loyalty | Institutional duty vs. personal loyalty |
| **Resolution spectrum** | Understanding ↔ Betrayal | Protect friend ↔ Report corruption |
**Common structure**: Both contradictions involve **Naia** as the emotional anchor. Naia is worried about Kael. Sera knows why (unreported evidence). Kael is trying to protect Naia (exit attempt). The smuggler and detective approach the same NPC web from opposite sides. THE FRIEND, in both cases, is the person caught in the middle trying to protect someone they care about.
**Common structure**: Both contradictions involve a **shared third party** as the emotional anchor — someone both THE FRIEND NPCs are trying to protect, approached from opposite sides of the case.
---
@@ -239,7 +239,7 @@ Both THE FRIEND NPCs follow the same structural arc, but the **nature of the con
**Effect on relationship**: None directly. A Friendly NPC with Active knowledge remains Friendly.
**Example**: Smuggler's knowledge of Kael as "trusted colleague" is Active until the contradiction.
**Example**: Smuggler's knowledge of {THE FRIEND} as "trusted colleague" is Active until the contradiction.
---
@@ -254,7 +254,7 @@ When `KnowledgeState` becomes `Contradicted`, the system:
2. Triggers a monologue event: "Wait, that doesn't match what I thought I knew."
3. Evaluates `RelationshipState` transition. If the contradicted knowledge is about a Friendly NPC, transition to PersonOfInterest.
**Example**: Smuggler's knowledge "Kael operates within ring protocol" contradicts with new observation "Kael meeting unauthorized contact." Both entries become `Contradicted`. Monologue fires. Kael's `RelationshipState` → `PersonOfInterest`.
**Example**: Smuggler's knowledge "{THE FRIEND} operates within ring protocol" contradicts with new observation "{THE FRIEND} meeting unauthorized contact." Both entries become `Contradicted`. Monologue fires. {THE FRIEND}'s `RelationshipState` → `PersonOfInterest`.
---
@@ -264,7 +264,7 @@ When `KnowledgeState` becomes `Contradicted`, the system:
**Effect on relationship**: Degrades confidence but doesn't change relationship state. A Friendly NPC remains Friendly, but positional knowledge becomes unreliable.
**Example**: Smuggler last saw Kael at the hub 7 hours ago. `last_known_position` becomes Stale. Monologue: "Kael should be off-shift by now. Probably at the bar, but I haven't seen him."
**Example**: Smuggler last saw {THE FRIEND} at the hub 7 hours ago. `last_known_position` becomes Stale. Monologue: "{THE FRIEND} should be off-shift by now. Probably at the bar, but I haven't seen them."
---
@@ -289,7 +289,7 @@ The dialogue system (D-028, D-035) uses `RelationshipState` as a filter:
### Unknown → Known
- **Before**: "Who's that?"
- **After**: "That's Drin, the maintenance tech."
- **After**: "That's the maintenance tech."
**Shift**: Identification. Observer now has context.
@@ -297,8 +297,8 @@ The dialogue system (D-028, D-035) uses `RelationshipState` as a filter:
### Known → Friendly
- **Before**: "Drin's over there."
- **After**: "Good to see Drin. Always fixes things without making a fuss."
- **Before**: "They're over there."
- **After**: "Good to see them. Always fixes things without making a fuss."
**Shift**: Warmth. Personal regard.
@@ -306,8 +306,8 @@ The dialogue system (D-028, D-035) uses `RelationshipState` as a filter:
### Friendly → PersonOfInterest (THE FRIEND)
- **Before**: "There's Kael. Good — I was starting to worry."
- **After**: "Kael's here. But he's been acting strange. What's going on?"
- **Before**: "There's {THE FRIEND}. Good — I was starting to worry."
- **After**: "{THE FRIEND}'s here. But they've been acting strange. What's going on?"
**Shift**: Doubt contaminates warmth. The fond observation is now analytical.
@@ -315,8 +315,8 @@ The dialogue system (D-028, D-035) uses `RelationshipState` as a filter:
### PersonOfInterest → Hostile
- **Before**: "Kael's avoiding me. Something's wrong."
- **After**: "Kael just signaled security. He's turned on me."
- **Before**: "{THE FRIEND}'s avoiding me. Something's wrong."
- **After**: "{THE FRIEND} just signaled security. They've turned on me."
**Shift**: Assessment → alarm.
@@ -329,7 +329,7 @@ The dialogue system (D-028, D-035) uses `RelationshipState` as a filter:
```yaml
prerequisite:
relationship_state: PersonOfInterest
subject: kael_davan
subject: {npc_id}
```
- **Dialogue lines** filter on `access` tier, which is derived from `RelationshipState` + character type (smuggler/detective/NPC role).
- **Color shifts** are client-side rendering, but the knowledge graph determines the state. Content authors write to the state; the client handles the color.
@@ -343,4 +343,4 @@ The dialogue system (D-028, D-035) uses `RelationshipState` as a filter:
---
**Total states**: 5. **Load-bearing transitions for v0.1**: Unknown → Known (universal), Known/Friendly → PersonOfInterest (THE FRIEND), PersonOfInterest → Hostile (confrontation failure). Other transitions exist but are less structurally critical.
**Total states**: 5. **Load-bearing transitions**: Unknown → Known (universal), Known/Friendly → PersonOfInterest (THE FRIEND), PersonOfInterest → Hostile (confrontation failure). Other transitions exist but are less structurally critical.
wiki/contraband/index.md
+3 -3
View File
@@ -1,11 +1,11 @@
# Contraband
Illegal and restricted goods in the Settled Reach. Primary gameplay focus for the v0.1 smuggler/detective vertical slice.
Illegal and restricted goods in the Settled Reach. Smuggling scenarios turn on the moral and political weight of what's in the containers.
## Contraband Types
| Item | Category | v0.1 Role |
|------|----------|-----------|
| Item | Category | Role |
|------|----------|------|
| [Lattice Components](lattice-components.md) | Unlicensed neural mods | Primary contraband |
| [Medical-Grade Replacements](medical-grade-replacements.md) | Diverted healthcare | Secondary |
| [Severance Equipment](severance-equipment.md) | Counter-surveillance gear | Restricted tech |
wiki/contraband/lattice-components.md
+8 -9
View File
@@ -17,13 +17,13 @@ cross_refs: []
**Status:** Canonical
**Legality:** Category 3 violation (unauthorized lattice modification)
**Source:** Aftermarket manufacturers, Syndic-adjacent supply chains
**Moved By:** The ring (Sova Transit District smuggling operation)
**Moved By:** The ring (district smuggling operation)
---
## Overview
Unlicensed lattice components are the primary contraband in the v0.1 smuggling scenario. These are aftermarket neural lattice modifications — processing nodes, capability packages, interface upgrades — that bypass [Lattice Commission](../technology/neural-lattice.md#commission-regulation) certification.
Unlicensed lattice components are the primary contraband in the district smuggling scenario. These are aftermarket neural lattice modifications — processing nodes, capability packages, interface upgrades — that bypass [Lattice Commission](../technology/neural-lattice.md#commission-regulation) certification.
They are not defective. They are not dangerous. They are unauthorized. And that distinction is the moral core of the smuggling operation.
@@ -43,7 +43,7 @@ They are not defective. They are not dangerous. They are unauthorized. And that
**Professional capability:** A freight scheduler with an aftermarket processing upgrade handles manifests faster, catches errors sooner, becomes more valuable at work. A maintenance technician with enhanced diagnostic capabilities works more efficiently. The upgrade pays for itself in job performance.
**Perception access:** The Commission's tier system means most people on Station Sova are locked into Baseline perception — natural vision and basic Meridian access. Enhanced perception modes (camera access, audio analysis, tracking) require institutional sponsorship. People who want to see more of their own world must either get institutional approval or go to the aftermarket.
**Perception access:** The Commission's tier system means most people in a mid-Reach freight district are locked into Baseline perception — natural vision and basic Meridian access. Enhanced perception modes (camera access, audio analysis, tracking) require institutional sponsorship. People who want to see more of their own world must either get institutional approval or go to the aftermarket.
**Economic calculation:** Commission-certified upgrades cost 3-5x more than aftermarket equivalents and take 6-12 months to process. For a dock worker making 2,400 credits per month with 200 credits margin, the choice between waiting a year for certification or buying aftermarket this month is not a difficult calculation.
@@ -57,11 +57,11 @@ From `contraband.supply_chain` (fact catalog):
1. **Manufacturing:** Syndic-adjacent independent manufacturers produce lattice components outside Commission jurisdiction. Quality is professional-grade — these aren't garage operations.
2. **Interstellar transit:** Components move through [Founder Gate](../technology/founder-gates.md) networks to distribution nodes.
3. **Off-station coordination:** Sabel (off-station) manages incoming shipments, coordinates timing with ring operations.
3. **Off-station coordination:** The off-station coordinator manages incoming shipments, coordinates timing with ring operations.
4. **Gate arrival:** Contraband arrives mixed with legitimate freight through [span gates](../technology/span-gates.md) on scheduled cargo cycles.
5. **Inspection bypass:** Containers with doctored manifests pass through inspection. Weight discrepancies are the primary forensic evidence (logged weight vs. actual weight).
6. **Ring coordination:** Devra or Nils coordinate local distribution. Kael and Kosse handle physical cargo. Voss provides scheduling cover.
7. **Local distribution:** Components reach buyers through informal networks, facilitated through The Last Shift as a social clearing house.
6. **Ring coordination:** Ring leadership coordinates local distribution. Cargo handlers manage physical routing. The shift supervisor provides scheduling cover.
7. **Local distribution:** Components reach buyers through informal networks, facilitated through the district bar as a social clearing house.
---
@@ -70,7 +70,7 @@ From `contraband.supply_chain` (fact catalog):
**For the detective:**
- `investigation.manifest_discrepancy` — Weight-to-volume mismatches in cargo manifests. The detective's Analytical lattice flags these automatically at Suspects confidence.
- `investigation.cargo_anomaly` — Containers sitting in temporary storage longer than standard procedure allows.
- `investigation.shift_mismatch` — Night shift schedules inconsistent with freight volume (Voss creating coverage gaps).
- `investigation.shift_mismatch` — Night shift schedules inconsistent with freight volume (shift supervisor creating coverage gaps).
- `contraband.lattice_components` — At KnowsOf: "Unlicensed lattice components. Aftermarket mods that bypass Commission certification." At Direct: "I'm looking at a crate of lattice components right now. Serial numbers don't match any certified batch."
**For the smuggler:**
@@ -106,7 +106,7 @@ But also:
**Perception Connection (D-017):**
- Lattice components connect directly to the perception system — a smuggled upgrade could theoretically change what the player perceives
- This connection is referenced in lore and dialogue, not mechanically implemented in v0.1
- This connection is referenced in lore and dialogue, not mechanically implemented in the initial build
- Future scope: aftermarket lattice upgrade as player progression mechanic
**Investigation Mechanics:**
@@ -121,7 +121,6 @@ But also:
- [Neural Lattice](../technology/neural-lattice.md) — The technology being modified
- [Medical-Grade Replacements](medical-grade-replacements.md) — Secondary contraband (healthcare dimension)
- [Severance Equipment](severance-equipment.md) — Tertiary contraband (political dimension)
- [Sova Transit District](../world/sova-transit-district.md) — The ring's operational infrastructure
- [Fact Catalog](../knowledge/fact-catalog.md) — FactId confidence progressions
- D-037: Contraband specification
- D-017: Perception modes (lattice tier determines available modes)
wiki/contraband/medical-grade-replacements.md
+4 -4
View File
@@ -17,7 +17,7 @@ cross_refs: []
**Status:** Canonical
**Legality:** Category 3 violation (unauthorized lattice modification) + controlled medical device distribution
**Source:** Diverted from Syndic supply chains
**Moved By:** The ring (Sova Transit District smuggling operation)
**Moved By:** The ring (district smuggling operation)
---
@@ -46,7 +46,7 @@ Neural lattices are biotech. They degrade over time. For most people in the Sett
4. Installation at a certified facility
5. Post-installation compliance verification
**Cost:** Prohibitive for most workers on Station Sova. A full lattice replacement through legitimate channels costs 8-12 months of a dock worker's total salary. Component-by-component replacement (replacing only the failing nodes) is cheaper but still requires the full approval cycle for each component.
**Cost:** Prohibitive for most workers at a mid-Reach freight station. A full lattice replacement through legitimate channels costs 8-12 months of a dock worker's total salary. Component-by-component replacement (replacing only the failing nodes) is cheaper but still requires the full approval cycle for each component.
**Wait time:** The approval cycle exists because the Commission certifies each replacement component individually. For someone whose lattice is degrading now — whose professional capability is declining this month, whose perception overlays are failing this week — "6-12 months" is not an acceptable medical timeline.
@@ -70,7 +70,7 @@ The ring's medical-grade replacements are the same components available through
## Who Needs Them
**Aging workers:** Long-term Sova residents whose lattices were installed 15-20+ years ago. Nodes degrade. Processing slows. These workers need replacements to maintain professional capability and daily function.
**Aging workers:** Long-term district residents whose lattices were installed 15-20+ years ago. Nodes degrade. Processing slows. These workers need replacements to maintain professional capability and daily function.
**Economically locked-out workers:** People who could get Commission approval but can't afford the certified pricing or can't afford to wait. Their lattices are degrading now. Their jobs depend on lattice function now. The black market serves them because the legitimate market won't — not on their timeline, not at their price point.
@@ -120,7 +120,7 @@ Medical-grade replacements are the smuggling ring's moral shield. When the ring
- Detective monologue at KnowsOf: recognition that enforcement has human costs
- Both character monologues shift in tone when medical-grade knowledge is established
**v0.1 Scope:**
**Scope:**
- Medical-grade replacements are dialogue and monologue content — not a visible gameplay mechanic
- No player character experiences lattice degradation in the vertical slice
- The moral dimension is expressed through NPC conversations and internal monologue, not through systems
wiki/contraband/severance-equipment.md
+15 -16
View File
@@ -17,7 +17,7 @@ cross_refs: []
**Status:** Canonical
**Legality:** Highest-severity violation — intelligence-level enforcement response
**Source:** Guardians of Autonomy supply chain
**Moved By:** The ring (Sova Transit District smuggling operation — not all members aware)
**Moved By:** The ring (district smuggling operation — not all members aware)
---
@@ -31,7 +31,7 @@ This is the cargo that makes the ring scary. Not because it's weapons — it's n
## What's in the Containers
The specific Severance equipment in the ring's cargo is not fully cataloged in v0.1 — it lives in sealed containers that most ring members don't open and Nils doesn't discuss. What's known:
The specific Severance equipment in the ring's cargo is not fully cataloged — it lives in sealed containers that most ring members don't open and ring leadership doesn't discuss. What's known:
**Hardware:**
- Meridian signal jammers (localized blackout devices, portable)
@@ -39,7 +39,7 @@ The specific Severance equipment in the ring's cargo is not fully cataloged in v
- Signature masking units (individual-wear devices that suppress lattice tracking signatures)
**Characteristics:**
- Heavier than lattice components (the sealed containers Nils won't discuss are "heavier than lattice components" per fact progression)
- Heavier than lattice components (the sealed containers ring leadership won't discuss are "heavier than lattice components" per fact progression)
- Professionally manufactured — not improvised or garage-built
- Sourced through Guardians of Autonomy supply networks
- Transit through the same interstellar routes as the ring's other cargo
@@ -50,7 +50,7 @@ The specific Severance equipment in the ring's cargo is not fully cataloged in v
The Guardians of Autonomy are a decentralized political movement spread across multiple systems in the Settled Reach. They oppose lattice-mediated institutional surveillance and advocate for individual control over perception technology. Severance technology is their tool of choice — the mechanism for opting out of the information architecture.
**What this means for the ring:** The ring didn't set out to be part of a political movement. They started as a local commercial operation — moving lattice components to serve community demand. The Severance equipment arrived through the same supply chain, managed by the same off-station coordinator (Sabel), distributed through the same infrastructure. The ring became a Guardians distribution node by logistics, not ideology.
**What this means for the ring:** The ring didn't set out to be part of a political movement. They started as a local commercial operation — moving lattice components to serve community demand. The Severance equipment arrived through the same supply chain, managed by the same off-station coordinator, distributed through the same infrastructure. The ring became a Guardians distribution node by logistics, not ideology.
**What this means for the story:** The Guardians connection is the contamination seed. It transforms the ring from "local grey market, community immune system" into "local node in an interstellar political network." Not because the ring members are political actors — most of them aren't — but because their infrastructure serves political purposes they didn't choose and may not fully understand.
@@ -58,13 +58,13 @@ The Guardians of Autonomy are a decentralized political movement spread across m
## Who Knows What
**Ring members who know:** Nils (manages the sealed containers directly), Devra (coordinates with off-station contact Sabel, likely aware). The sealed containers are Nils's domain — he handles them personally, doesn't discuss contents, stores them separately from lattice cargo.
**Ring members who know:** Ring leadership (manages the sealed containers directly, coordinates with the off-station contact). The sealed containers are leadership's domain — handled personally, contents not discussed, stored separately from lattice cargo.
**Ring members who suspect:** Kael (has noticed the sealed containers, hasn't asked), Voss (provides scheduling cover for all cargo, doesn't differentiate). Others in the ring handle lattice components and medical-grade replacements; the Severance cargo moves through a tighter channel.
**Ring members who suspect:** Some cargo handlers (have noticed the sealed containers, haven't asked), the shift supervisor (provides scheduling cover for all cargo, doesn't differentiate). Others in the ring handle lattice components and medical-grade replacements; the Severance cargo moves through a tighter channel.
**Ring members who don't know:** Kosse, Lera, Pell, and other peripheral members. They know the ring moves lattice cargo. The Severance equipment is compartmentalized.
**Ring members who don't know:** Peripheral members. They know the ring moves lattice cargo. The Severance equipment is compartmentalized.
**The smuggler (player):** Starts without knowledge of the Severance cargo. Discovery follows the fact progression — suspicious sealed containers, Nils's evasion, eventually the truth. This discovery is the contamination moment that complicates the smuggler's moral position.
**The smuggler (player):** Starts without knowledge of the Severance cargo. Discovery follows the fact progression — suspicious sealed containers, ring leadership's evasion, eventually the truth. This discovery is the contamination moment that complicates the smuggler's moral position.
**The detective (player):** Discovers Severance equipment through investigation — either by identifying the containers, by following the supply chain, or through NPC testimony. The discovery transforms the case.
@@ -79,21 +79,21 @@ Lattice components? Serving community demand. Medical-grade replacements? Provid
Manifest fraud and unlicensed lattice components are a local enforcement matter. Severance equipment distribution is an intelligence-level concern. The detective's case changes from "file a report with the Commission" to "flag this for system-level authorities." The stakes of every decision — who to confront, who to protect, what to report — increase dramatically. Turning an informant isn't just building a smuggling case anymore; it's potentially exposing a Guardians network.
**For the narrative:**
Severance equipment is the thing that prevents the v0.1 story from being small. A smuggling ring on a freight station is a local story. A smuggling ring unknowingly serving as a node in an interstellar political movement is a story that points beyond its setting. The Severance cargo is the promise that this story has roots and branches the player can't see yet.
Severance equipment is the thing that prevents the district story from being small. A smuggling ring on a freight station is a local story. A smuggling ring unknowingly serving as a node in an interstellar political movement is a story that points beyond its setting. The Severance cargo is the promise that this story has roots and branches the player can't see yet.
---
## Knowledge Graph Integration
**FactId: `contraband.severance_tech`**
- **Suspects:** "Sealed containers Nils won't discuss. Heavier than lattice components."
- **Suspects:** "Sealed containers ring leadership won't discuss. Heavier than lattice components."
- **KnowsOf:** "Severance equipment. Counter-surveillance tech. Illegal across most of the Reach."
- **KnowsDetails:** "Guardians of Autonomy supply chain. This isn't local — it's connected to something bigger."
- **Direct:** N/A (not directly visible in v0.1)
- **Direct:** N/A (not directly visible in the early arc)
**Mechanical Purpose:** Contamination seed for storyteller expansion. The thing that makes the smuggler question how deep the ring goes. The thing that transforms the detective's case from local to systemic.
**Progression design:** Note the deliberate knowledge gap — neither character reaches Direct confidence with Severance tech in v0.1. They know it exists, they know where it comes from, but they never handle it directly or see it deployed. The technology remains slightly abstract, slightly ominous. This is intentional: Severance equipment is a thread to pull in future content, not a puzzle to solve in the vertical slice.
**Progression design:** Note the deliberate knowledge gap — neither character reaches Direct confidence with Severance tech in the vertical slice. They know it exists, they know where it comes from, but they never handle it directly or see it deployed. The technology remains slightly abstract, slightly ominous. This is intentional: Severance equipment is a thread to pull in future content, not a puzzle to solve in the vertical slice.
---
@@ -106,11 +106,11 @@ Severance equipment is the thing that prevents the v0.1 story from being small.
- Case transformation trigger for the detective
**Dialogue Impact:**
- Discovery of Severance equipment changes available dialogue options with Nils, Devra, and Sabel-related threads
- Smuggler confrontation with Nils about sealed containers is a relationship-testing moment
- Discovery of Severance equipment changes available dialogue options with ring leadership and off-station contacts
- Smuggler confrontation with ring leadership about sealed containers is a relationship-testing moment
- Detective reporting options bifurcate: local enforcement vs. intelligence escalation
**v0.1 Scope:**
**Scope:**
- Severance equipment is knowledge content — discovered, discussed, worried about
- No Severance technology is deployed or used in the vertical slice
- The equipment's significance is narrative (what it implies about the ring's connections) not mechanical (what it does)
@@ -123,7 +123,6 @@ Severance equipment is the thing that prevents the v0.1 story from being small.
- [Lattice Components](lattice-components.md) — Primary contraband (commercial dimension)
- [Medical-Grade Replacements](medical-grade-replacements.md) — Secondary contraband (healthcare dimension)
- [Fact Catalog](../knowledge/fact-catalog.md) — `contraband.severance_tech` confidence progression
- [Sova Transit District](../world/sova-transit-district.md) — Ring operational infrastructure
- D-037: Contraband specification
- D-023: Three-tier content model (contamination seed for storyteller)
wiki/corporations/adams-ford-publishing.md
+2 -1
View File
@@ -11,7 +11,7 @@ faction_type: economic
headquarters: Parallax (GJ 280A)
tags: [media, publishing, guide, humor, content]
decision_refs: []
cross_refs: [gate-corporation, parallax]
cross_refs: [parallax, lattice-commission, guardians-of-autonomy, ashwick-broadcasting]
---
# Adams & Ford Publishing Syndicate
@@ -112,6 +112,7 @@ Adams herself is a potential contact — a Perpetual-class journalist with a cen
- [Parallax](../star-systems/GJ-280A/index.md) — Headquarters system; media production hub
- [Lattice Commission](../factions/lattice-commission.md) — Regulatory adversary; content classification dispute
- [Guardians of Autonomy](../factions/guardians-of-autonomy.md) — Frequent citers; uncomfortable allies
- [Ashwick Broadcasting](ashwick-broadcasting.md) — North reach documentary partner; archival access exchange; forty-year standing distribution relationship
- [Veridian Syndicate] — Adams's former employer; founding grievance
---
wiki/corporations/alcazar-hospitality.md
+80 -7
View File
@@ -1,24 +1,97 @@
---
title: "Alcazar Hospitality"
description: "Alcazar Hospitality — premium service provider based in Altair, south reach"
description: "South reach premium hospitality group at Altair (GJ 768) — corridor-transit accommodation, private dining, and a reputation for discretion that has been its primary commercial asset for eighty years"
slug: alcazar-hospitality
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-21
scope: regional
faction_type: economic
headquarters: Altair (GJ 768)
tags: [service_premium, south_reach, tractus]
decision_refs: [D-189]
cross_refs: []
cross_refs: [the-registry]
---
# Alcazar Hospitality
**Type:** Corporation — Premium Service Provider
**Type:** Corporation — Premium Hospitality Group
**Also Known As:** Alcazar, the Alcazar properties
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Altair (GJ 768)
**Scope:** South reach corridor primary; four properties across three systems
**Headquarters:** Altair (GJ 768) — 3-aperture junction, 4 hops from Gateway
**Classification:** Sub-Syndic service enterprise; family-held independent
Alcazar Hospitality is a premium service provider operating out of Altair (GJ 768). Details to be expanded.
---
## Overview
Altair is a junction system — three gate apertures, south reach position, commercial traffic moving in four directions through its transit infrastructure. People pass through Altair constantly. Most of them do not stay. The ones who do tend to have reasons for discretion: commercial negotiations that are not yet concluded, arbitration proceedings that require both parties to be in the same system without being in the same room, transit layovers that have stretched beyond the scheduled window for reasons the traveler is not explaining.
Alcazar Hospitality serves these people. Not exclusively — the properties are open to any traveler who can meet the room rate — but predominantly. The commercial travelers, negotiating parties, long-stay guests with complicated itineraries, and institutional representatives who need accommodation that does not ask questions: these are Alcazar's real market. They have been Alcazar's real market since the group's founding, eighty years ago, and the product the group has sold in that time is less the rooms than the reputation that comes with them. Alcazar is discreet. Everyone in the south reach commercial community understands this. The understanding is the asset.
The properties are not lavish. They are precise. The difference between a lavish hotel and a precise one is that a lavish hotel wants you to notice how much it has spent on your comfort, while a precise hotel has decided exactly what you need and provided it without expecting your admiration for the effort. Alcazar does not have lobbies designed to impress. It has rooms designed to function, dining rooms calibrated to conversation rather than spectacle, and staff trained to understand that the most important thing they can do for most guests is to behave as though they have not noticed them.
---
## Origin
The group was founded eighty years ago by Inês Alcácer, who had spent twelve years as a senior accommodation manager at a commercial transit facility at Altair's principal station before concluding that the facility she worked for was solving the wrong problem. Transit accommodation at junction systems defaults to volume — many guests, short stays, efficient turnover. This works for most travelers. It does not work for the commercial negotiating party that needs three days of extended accommodation while two corporations argue over a freight contract, or for the arbitration delegation that cannot be housed in the same wing as the other arbitration delegation, or for the person who needs a room that will not appear in any standard booking system.
Inês Alcácer opened the first Alcazar property with twelve rooms in a refurbished section of an older Altair station district. The rooms were expensive. The property was impossible to find unless someone told you where it was. Within two years, the commercial community that needed what Alcazar offered had found it through the mechanism by which these things are found: one person telling another person, with confidence, that this was a place that worked. The expansion to three properties across two additional south reach systems happened over the following thirty years. A fourth property opened fifteen years ago at a junction system that had developed enough commercial traffic to support the model.
Inês Alcácer died forty years ago, non-Perpetual, and left the properties to her two children in equal shares. One of those children, now in her seventies, is the group's current managing director. The other holds equity and does not participate in operations. The shareholding structure is family-held and has not been offered to outside investment. This is policy, not circumstance.
---
## Operations
**Properties:** Four properties total — the original Altair flagship (forty-two rooms), two south reach corridor locations at systems with significant commercial transit, and the newer fourth property at a junction with growing arbitration and commercial negotiation traffic. All four properties share a common operational philosophy and guest protocols. They do not share a booking system — reservations at each property are managed independently, through property-specific contacts, and do not cross-reference between locations by design.
**Guest profile:** Long-stay commercial travelers, arbitration and negotiation delegations, institutional representatives requiring accommodation that does not draw attention. The average stay is longer than any other premium hospitality operation in the south reach corridor. This is a feature, not an artifact — Alcazar's properties are designed for people who need to be somewhere for an extended period without the experience of that period becoming the subject of discussion.
**Staff:** The group employs forty-three people across all four properties, including property managers, room staff, dining personnel, and a small logistics operation managing supply across the corridor. Staff are hired with an explicit understanding that guest matters are not discussed outside the property. This is not an unusual condition in hospitality; what distinguishes Alcazar's enforcement of it is that the condition is taken seriously.
**Revenue:** Room rates are high, turnover is low, and the group's margins depend on occupancy continuity — long-stay guests rather than one-night transits. The dining operations at each property are profitable in their own right, catering to external guests who have been referred by long-stay clients and to private event bookings that require a venue without a public profile. The group does not publish revenue figures.
---
## Location
Altair's three-aperture topology routes commercial traffic from four directions through the same transit infrastructure. The original Alcazar property serves the main station district at Altair's principal settlement — the oldest and largest property, with the longest waiting list for extended-stay bookings. The two intermediate corridor properties handle south reach overflow and the specialized traffic that moves between adjacent systems along the corridor's industrial and commercial routes. The fourth property, opened fifteen years ago at a junction system whose commercial arbitration traffic had developed to support the model, is Alcazar's newest and smallest.
None of the properties are listed in standard transit accommodation directories. Addresses circulate in the south reach commercial community through direct referral — the same mechanism by which the original Altair property was found eighty years ago. This is not secrecy. It is the oldest and most reliable form of reputation management: the people who need to find something will find it, and the process of finding it is itself a qualification.
---
## What They Don't Talk About
Alcazar's guest records do not exist, as a matter of stated policy. The group does not retain documentation of who stayed where, for how long, or with whom they dined. This is true.
What is also true is that the group's managing director, for the past twenty years, has maintained a personal record of guest interaction patterns — not identities, not stated purposes, but behavioral data: who requested adjacent suites, which guest combinations required the dining room to be arranged so that two parties could not see each other, how often specific corporate entities sent delegations at the same time without appearing on the same booking. This record has never been described as a guest record because it does not contain guest names. It has been shared, on three occasions in the past decade, with The Registry at Groombridge, which purchases commercial pattern data of this kind for its due-diligence intelligence services. The Registry's clients, who are attempting to understand the structure of south reach commercial relationships, receive analysis derived from Alcazar's guest interaction records without knowing the source. Alcazar's guests, who are paying for discretion, are providing some fraction of the intelligence that circulates about them.
The managing director considers this consistent with Alcazar's privacy commitments. The commitments, on examination, do not promise that behavioral patterns will not be observed and shared. They promise that names will not be recorded. The names are not recorded.
---
## Gameplay Relevance
Alcazar is ambient infrastructure for any investigation touching south reach commercial relationships. The properties are where negotiations happen before they become contracts, where delegations stay before they appear in official filings, where the people whose names appear in arbitration records spent the nights before and after the hearings. A player tracing a commercial dispute, a hostile acquisition, or a pattern of coordinated commercial activity in the south reach will encounter Alcazar's properties as the physical location where those activities were organized — even if the activities themselves happened elsewhere.
The guest records do not exist. This is what Alcazar's staff will say, accurately, when asked. What does exist is The Registry's commercial intelligence archive at Groombridge, which contains behavioral pattern analysis derived from Alcazar data across at least three separate purchase transactions. A Registry analyst with access to the relevant archive files could confirm, without naming sources, that a specific corporate entity has sent delegations to Altair on dates that correlate with events the player is investigating — and could indicate, from the pattern data, who else was in the property at the same time. The Registry's cooperation is not free and is not guaranteed. The analyst knows what the data is worth and will price it accordingly.
The managing director is a secondary source: difficult to approach, professionally courteous, and unlikely to confirm the data-sharing arrangement unless the player can demonstrate they already know about it. She has spent twenty years maintaining the technical accuracy of Alcazar's privacy commitments, which means she has thought carefully about exactly which questions she can answer honestly and which she cannot. An investigator who asks the right question — not "did you keep records" but "did you sell anything to The Registry" — will get a response that is notably different from her standard deflection.
The properties as physical environments provide investigation texture that indirect sources cannot replicate. Alcazar's premises are designed for guest privacy — sightlines managed for room separation, staff trained to be present without drawing notice, layout that makes it possible to be in the dining room or corridor without an obvious stated purpose. A player with a referral as a legitimate patron can observe long-stay clientele without appearing to. Commercial guests on extended stays develop routines: the same table at the same hour, the same route between meals and rooms. Three days of presence in a well-placed seat can produce a more accurate account of who is meeting whom than three weeks of approaching the same people through their public contacts.
---
**Cross-References:**
- [The Registry](the-registry.md) — Groombridge commercial intelligence firm; purchaser of behavioral pattern data
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-21
wiki/corporations/alcyone-tech.md
+84 -6
View File
@@ -1,24 +1,102 @@
---
title: "Alcyone Tech"
description: "Alcyone Tech — precision technology manufacturer based in Groombridge, core"
description: "Groombridge precision technology manufacturer — authentication hardware, settlement terminals, and encrypted relay components that form the physical substrate of the Reach's interstellar financial infrastructure"
slug: alcyone-tech
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Groombridge (GJ 380)
tags: [tech_premium, core, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [groombridge-settlement-house, the-registry, meridian-risk]
---
# Alcyone Tech
**Type:** Corporation — Precision Technology Manufacturer
**Also Known As:** Alcyone
**Status:** Canonical
**Scope:** Regional — core operations
**Headquarters:** Groombridge (GJ 380)
**Scope:** Core primary; reach-wide institutional client base secondary
**Headquarters:** Groombridge (GJ 380), Lendel district — 2-aperture loop_member, 2 hops from Gateway
**Classification:** Sub-Syndic technology enterprise; sole-source institutional supplier
Alcyone Tech is a precision technology manufacturer operating out of Groombridge (GJ 380). Details to be expanded.
---
## Overview
Interstellar commerce runs on institutional trust. Institutional trust runs on verified process integrity. Verified process integrity runs, at its physical base, on hardware: the authentication terminals, encrypted relay components, and settlement verification devices that allow a financial commitment made at Ran to be cleared at Groombridge without either party needing to send a representative in person. Alcyone Tech makes this hardware.
The company does not manufacture consumer electronics. It does not pursue volume markets, retail distribution, or the kind of product recognition that comes with a brand name on something ordinary people hold. Its clients are financial houses, insurance institutions, legal service providers, and the settlement infrastructure that underlies Tractus-denominated commerce. These clients buy in small quantities, require exacting specifications, and expect the hardware they receive to perform without deviation under conditions their own legal liability depends on. Alcyone's product quality is not optional. The contracts that define Alcyone's institutional relationships make this explicit.
Eighty years of manufacturing from the same Lendel facility, with an unblemished certification record, has produced the kind of institutional confidence that no marketing exercise can substitute for. Alcyone Tech's clients do not shop around for terminal hardware. They have an Alcyone relationship and they maintain it, because changing hardware suppliers in a clearing context requires re-certification of every process that touches the equipment, and re-certification is expensive, time-consuming, and introduces risk.
---
## Origin
Alcyone Tech was founded by an engineer named Rosamund Osei-Frempong, who had spent twelve years as a hardware maintenance contractor for several of the Groombridge financial houses before concluding that the hardware layer the houses depended on was being systematically underbuilt. The individual houses maintained their own equipment, sourced from multiple off-Groombridge suppliers, and managed maintenance schedules that prioritized cost over coordination. The result was a fragmented infrastructure with version inconsistencies between adjacent systems — a risk that no individual house had incentive to address because addressing it would require coordinating with competitors.
Osei-Frempong's founding proposition was consolidation: one manufacturer, certified to Commission standards, building and maintaining the hardware for multiple institutions under a common architecture. The argument was that consistent hardware across the Groombridge financial district would reduce the systemic fragmentation risk and that the cost of certification could be shared. The first institution to sign was a smaller insurance house that had recently experienced a hardware-related clearing failure and was prepared to spend money to not experience it again. The Groombridge Settlement House signed four years later, after two of its terminal batches from different suppliers produced version-incompatible authentication outputs. The rest of the district followed over the next decade.
The company has been the primary hardware supplier for Groombridge's financial infrastructure for sixty years.
---
## Operations
**Product lines:** Settlement terminals — the hardware that GSH's correspondent institutions use to authenticate and submit clearing requests. Encrypted relay nodes — physical components in the communication infrastructure that the financial houses maintain independently of gate transit. Authentication token systems — cryptographic hardware for biometric contract signing, used wherever Tractus-denominated contracts require physical identity verification. These are not consumer products; they are institutional infrastructure items purchased in batches of tens to hundreds with expected service lives of eight to twelve years.
**Manufacturing:** The Lendel facility employs ninety-one people, almost entirely technical specialists. The facility is small relative to the capital managed by Alcyone's clients. This is characteristic of Groombridge: the economic leverage of an institution here is not proportional to its headcount. Alcyone's ninety-one people are responsible for the continuous operational integrity of hardware that clears a substantial fraction of Reach-wide interstellar commerce. They understand this. It is reflected in their compensation and in the quality of the facility they work in.
**Certification:** Every product line Alcyone manufactures is certified under the Lattice Commission's hardware integrity standards for financial infrastructure. The certification process requires documented production parameters, random sample testing, and periodic audit visits. Alcyone has never had a certification suspended and makes this fact visible in every client communication.
**Client relationships:** Long-term maintenance contracts with all major clients, renewable every five years. The maintenance contracts include hardware refresh cycles — periodic replacement of aging equipment with current-generation devices — that Alcyone manages on behalf of the institutions. Client institutions rarely interact with the hardware procurement question because the contracts delegate it.
---
## Political Relationships
**Groombridge Settlement House:** GSH is Alcyone's largest and most strategically significant client. The relationship is commercially standard — maintenance contract, hardware refresh cycles, certification requirements — but structurally foundational: if Alcyone's products are certified, GSH's clearing operations are certified; if Alcyone's certification were suspended, GSH would need to source replacement hardware and re-certify its processes, which would be operationally disruptive on a scale neither party wishes to explore. This mutual dependency is why the hardware vulnerability non-disclosure decision was considered a matter of institutional survival rather than a simple compliance question.
**Lattice Commission:** The Commission's certification relationship with Alcyone is the source of the company's market position and the mechanism by which the non-disclosure decision becomes dangerous. Commission certification of Alcyone's hardware is the basis on which the financial houses accept the hardware as suitable for clearing and authentication purposes. A Commission audit that discovered the vulnerability and the decision not to disclose it would not simply revoke a product certification — it would raise questions about every clearing transaction that passed through the affected hardware during the non-disclosure window.
**The Registry:** A smaller client relationship but a notable one. The Registry's analyst workstations use Alcyone authentication hardware for biometric contract signing and record integrity verification. The Registry's business model depends on the integrity of the records it produces. Its clients would have a specific kind of interest in knowing that the authentication hardware those records were produced on had a known vulnerability for the eighteen months preceding the current refresh cycle.
---
## What They Don't Talk About
Eighteen months ago, an Alcyone quality control engineer conducting routine test analysis on outgoing terminal batches identified a timing side-channel — a pattern in the authentication hardware's processing rhythm that, under specific conditions, allowed a sophisticated attacker to infer cryptographic state information from power consumption measurements taken at the terminal's exterior. The vulnerability required physical proximity to the terminal and significant analytical capability to exploit. It was not a trivial attack. It was not impossible.
The engineer filed an internal report. The report was reviewed by Alcyone's technical board and its legal team over the following three weeks. The conclusion the legal team reached was that mandatory client notification of a hardware vulnerability across the entire installed base would trigger recall provisions in the maintenance contracts, expose Alcyone to liability claims from institutions whose hardware was now certifiably non-compliant, and require a public disclosure to the Lattice Commission that would invite regulatory review of whether the hardware had ever met the standards under which it was certified.
The decision taken was not to notify clients and not to disclose to the Commission. The hardware refresh cycle that was already planned for the following year was accelerated and the upgrade specification was rewritten to address the vulnerability. The new hardware is clean. The installed base of current-generation devices is being replaced under the maintenance contract's normal refresh language. Clients who have asked about the accelerated timeline were told it is a performance enhancement initiative.
GSH's terminal fleet has been approximately 40% refreshed. The remaining 60% is scheduled for completion over the next fourteen months.
---
## Gameplay Relevance
Alcyone Tech is background institutional infrastructure — not a primary player in most investigations, but a reliable point of leverage if a player is working in the Groombridge financial district or tracing authentication-dependent commercial activity. The company's products are present wherever institutional contract signing happens: terminals in GSH's correspondent offices, relay nodes in Meridian Risk's underwriting facilities, authentication hardware in The Registry's analyst workstations.
The hardware vulnerability is an investigative thread with significant reach. A player who uncovers the internal report — which exists, was written professionally, and is documented in Alcyone's internal engineering archive — has found evidence of a deliberate non-disclosure to financial institutions that depend on the certified integrity of Alcyone's products. The implications extend to GSH's clearing certification, Meridian's underwriting records, and anything that moved through Alcyone authentication hardware during the window between discovery and replacement. Whether the vulnerability was exploited during that window is not a question Alcyone's internal records answer.
The legal team's deliberation document is the more dangerous piece of evidence. It records that the decision not to disclose was not an oversight but a considered choice, with the liability exposure analysis attached.
---
**Cross-References:**
- [Groombridge](../star-systems/GJ-380/index.md) — Headquarters system; primary client base
- [Groombridge Settlement House](groombridge-settlement-house.md) — Primary institutional client; terminal hardware
- [The Registry](the-registry.md) — Client; analyst workstation authentication hardware
- [Meridian Risk Partners](meridian-risk.md) — Client; underwriting facility relay components
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/aldgate-trust.md
+85 -7
View File
@@ -1,24 +1,102 @@
---
title: "Aldgate Trust"
description: "Aldgate Trust — premium service provider based in Crown's Hollow, north reach"
description: "Crown's Hollow fiduciary services firm — estate management, settler succession planning, and long-term asset custody for north reach families navigating the complications of interstellar inheritance"
slug: aldgate-trust
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Crown's Hollow (GJ 661A)
tags: [service_premium, north_reach, tractus]
decision_refs: [D-189]
cross_refs: []
cross_refs: [highland-cooperative, calloway-distillery, grampian-systems]
---
# Aldgate Trust
**Type:** Corporation — Premium Service Provider
**Type:** Corporation — Fiduciary Services / Estate Management
**Also Known As:** the Trust
**Status:** Canonical
**Scope:** Regional — north reach operations
**Headquarters:** Crown's Hollow (GJ 661A)
**Scope:** North reach primary; outward corridor families with inward holdings secondary
**Headquarters:** Crown's Hollow (GJ 661A) — outer north reach, 7+ hops from Gateway
**Classification:** Sub-Syndic professional services; licensed fiduciary under Lattice Commission estate standards
Aldgate Trust is a premium service provider operating out of Crown's Hollow (GJ 661A). Details to be expanded.
---
## Overview
Settling at the outer reach is a choice that compounds across generations. The distances involved — seven or more gate transits from Gateway — mean that a family establishing itself at Crown's Hollow can spend decades accumulating local holdings, building community relationships, and establishing the kind of material stability that passage life forecloses. When the founder dies, when children leave for inward systems, when a holding becomes too complex to manage without professional oversight, the complications of interstellar distance make ordinary estate law insufficient.
Aldgate Trust exists to manage these complications. It handles estate administration for families whose assets span multiple systems, succession planning for settlers whose heirs have scattered inward, and long-term custodial arrangements for holdings that need managed continuity rather than immediate disposition. In a corridor where families regularly span six systems and three generations, Aldgate's combination of local knowledge and interstellar legal competence fills a specific and substantial need.
The Trust is not large. It does not pursue volume. The families who retain Aldgate tend to stay retained — a settler who places her estate under Trust management at sixty typically leaves it there until disposition, and the Trust expects to be involved in the subsequent generation's planning as well. This creates a client base that is stable, deeply informed about Aldgate's capabilities, and inclined to refer.
---
## Origin
Aldgate Trust was established at Crown's Hollow seventy years ago by a solicitor named Dorothea Harwick who had spent fifteen years as a correspondent attorney for an inward firm, handling the outward reach cases that no one in the core wanted to travel to resolve. She had seen too many estates collapse into territorial disputes because the legal instruments that governed them had been drafted by attorneys who had never visited the systems involved and who treated interstellar distance as an administrative footnote rather than a structural reality.
Her thesis was straightforward: fiduciary services for outward reach families needed to be staffed by people who actually lived at the relevant distance, who understood that a six-month transit leg was not a complication to be worked around but a fundamental fact of the client's world. Aldgate's founding partners were all based at Crown's Hollow or within two hops. This geographic commitment has been maintained.
The firm expanded carefully through the first two decades, building competency in the specific legal instruments that govern multistellar estates under Lattice Commission framework before taking on clients whose complexity required that competency. It has been the dominant estate services firm at Crown's Hollow for fifty years.
---
## Operations
**Core services:** Estate administration — acting as executor or co-executor for complex estates with multi-system asset distribution. Succession planning — drafting instruments that account for heir location, transit time, and the practical reality that an heir resident at Ran cannot manage a Crown's Hollow agricultural holding in real time. Asset custody — holding and managing productive assets (agricultural, commercial, real property) under management agreements that provide continuity during transition periods.
**Staff:** Thirty-one, of whom nine are qualified attorneys. The rest are property administrators, agricultural managers, and accountants who understand the specifics of managing remote holdings. The firm does not employ people who only know the paperwork; it employs people who can also visit a managed farm and assess whether it is actually being run as documented.
**Client profile:** Families with agricultural holdings, commercial operations, or real property at Crown's Hollow and adjacent systems. The typical engagement begins when a second-generation settler is managing the first generation's assets and the complexity has outgrown personal administration. Engagements last decades.
**Fees:** Structured as annual custody fees plus transaction fees when the Trust acts on behalf of an estate. Transparent by industry standard. The Trust's reputation depends on clients feeling that it operates in their interest, and fee disputes are existential threats to that perception.
---
## Political Relationships
**Highland Cooperative:** Several Highland Cooperative member families are Aldgate Trust clients, with their agricultural holdings under long-term custody arrangements. This gives Aldgate visibility into the Cooperative's internal membership structure — which estates are encumbered, which are being managed for absent heirs, which are distressed — that the Cooperative's governance board does not itself have. The Trust's fiduciary obligations to its individual clients formally prohibit disclosure, but the aggregated picture Aldgate holds shapes which estates are vulnerable to the 14(c) mechanism.
**Calloway Distillery:** The Distillers' Council governance documents for two of the eleven Calloway distilleries designate Aldgate Trust as their executor of record. The Trust's involvement in distillery succession planning is therefore not incidental — it holds formal authority over what happens when a founding distillery's family line fails to produce a willing successor, which is the scenario currently developing at Calloway House. What Aldgate does or does not do in that succession process will significantly shape the Council's internal power balance.
**Grampian Systems:** Aldgate administers equipment lease portfolios for several agricultural clients whose monitoring infrastructure is supplied by Grampian Systems. The lease administration relationship gives Aldgate incidental sight of Grampian's client list and contract terms at Crown's Hollow — information that is not confidential in principle but that Aldgate holds in a volume no single observer should have.
---
## What They Don't Talk About
Aldgate's standard estate management agreement includes a clause — Section 14(c), titled "Extended Administrative Authority" — that activates if an estate falls into default on local obligations for more than eighteen consecutive months. Under 14(c), the Trust's management authority converts from advisory to plenary: it can make binding asset decisions on behalf of the estate without the consent of named beneficiaries, including accepting offers, restructuring holdings, and entering into long-term leases.
The clause was drafted as a practical instrument for genuinely failing estates — situations where no beneficiary is reachable and obligations must be met. It has been invoked four times in the Trust's history. In two of those cases, the beneficiaries were genuinely unreachable. In the other two, the estate was distressed but not failed, the beneficiaries were resident within two hops, and notification was sent by standard relay — which at seven hops from Gateway produces a four-month round-trip response time. When the responses arrived, the Trust had already acted under 14(c) and the transactions were complete.
Aldgate's position, documented in both cases, is that the relay timeline meant beneficiary consent was impractical and the estate obligations were immediate. The beneficiaries, in both cases, accepted settlements rather than pursue litigation. The clause has not been revised.
---
## Gameplay Relevance
Aldgate Trust appears in investigations touching north reach estate transfers, inheritance disputes, and the pattern of outward corridor properties moving from private family ownership to managed institutional control over time.
The 14(c) clause is the primary investigative thread. A player who obtains Aldgate's engagement agreements — which can be found in any Crown's Hollow estate filing — will find the clause. Whether it has been used opportunistically or defensively is a question the Trust's internal transaction records answer, and those records exist at Aldgate's Crown's Hollow offices.
The firm also holds long-term custody over agricultural holdings that connect to Highland Cooperative's supply chain and Fieldborn Grain's distribution relationships. An investigator tracing beneficial ownership of north reach agricultural assets will encounter Aldgate as a custodial intermediary whose client files name the actual owners.
If the 14(c) pattern is exposed, the implications extend beyond the two settled cases. Any estate currently under Aldgate's management whose beneficiaries are reachable only by slow relay is a candidate for the clause's use — and several such estates are currently active. The legal distinction between protective administration and opportunistic asset control is real but narrow, and the Trust's documented deliberations in the two historical cases reveal how that line was navigated rather than observed. Regulatory exposure under the Lattice Commission's fiduciary standards could affect the Trust's operating license and every active management relationship it holds. That outcome would harm the outer reach families whose continuity depends on it — which is why Aldgate's partners consider the current silence a service to their clients rather than a risk they are managing for themselves.
---
**Cross-References:**
- [Crown's Hollow](../star-systems/GJ-661A/index.md) — Headquarters; primary client geography
- [Highland Cooperative](highland-cooperative.md) — Agricultural clients; intersecting asset management
- [Calloway Distillery](calloway-distillery.md) — Distillery estates in adjacent systems; occasional Trust involvement in succession planning
- [Grampian Systems](grampian-systems.md) — Commercial client; equipment lease administration
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/alentejo-partners.md
+94 -7
View File
@@ -1,24 +1,111 @@
---
title: "Alentejo Partners"
description: "Alentejo Partners — regional specialty producer based in Caparica, south reach"
description: "South_reach agricultural aggregator based at Caparica (GJ 1002) — forty-plus small-holder farms, Alentejo heritage botanical oils and preserved goods, and a collective export structure whose founding deed has served the founding families rather better than members understood when they signed"
slug: alentejo-partners
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Caparica (GJ 1002)
tags: [terroir, south_reach, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [algarve-botanics, ferreira-monteiro]
---
# Alentejo Partners
**Type:** Corporation — Regional Specialty Producer
**Type:** Corporation — Agricultural Aggregator and Export Cooperative
**Also Known As:** the Partnership, Alentejo (abbreviated)
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Caparica (GJ 1002)
**Scope:** Regional — south_reach corridor primary; inner-corridor specialty food market secondary
**Headquarters:** Caparica (GJ 1002) — south_reach corridor
**Classification:** Sub-Syndic agricultural partnership; founding-family governance structure
Alentejo Partners is a regional specialty producer operating out of Caparica (GJ 1002). Details to be expanded.
---
## Overview
Alentejo Partners is the collective commercial entity through which forty-three small-holder farms in the Caparica system sell their production to the corridor. The partnership manages export logistics, quality certification, and market relationships for producers whose individual scale is too modest to negotiate directly with distributors, maintain certification under Lattice Commission agricultural standards, or build the kind of consistent market presence that commands reliable prices. The model is sound and it works. The member farms produce under conditions they could not manage independently, and the aggregate Alentejo brand has acquired a corridor reputation for quality botanical oils and preserved goods that benefits every producer who can claim it.
The founding families who constructed this arrangement did so with genuine agricultural expertise and with a thorough understanding of how partnership structures can be written to last. The structure has lasted. The terms have not required revisiting, because the founding deed was written in a way that makes revisiting it practically impossible without the founding families' consent.
---
## Origin
The first settling families of the Caparica system arrived from a Portuguese agricultural heritage — specifically from the Alentejo interior tradition: broad cultivated landscape, mixed farming, the patient husbandry of olives, cork oaks, and preserved-good traditions that require years to establish and decades to perfect. The name Alentejo Partners was chosen by the founding generation to carry that heritage explicitly; Caparica, the system name, referred to a different Portuguese coastal origin that the settlement's founders considered secondary to the agricultural identity they were establishing.
The founding generation built slowly. The olive-analogue cultivar they planted from introduced stock required two generations to produce reliably under Caparica's conditions. The cork-bark species they found locally proved workable for sealing and for a modest export market in the inner corridor. The preserved-good tradition established itself as the system's most distinctive export in the second century, when the fermented and oil-preserved products that the farms had been producing for local consumption found buyers in south_reach trade routes who valued them as specialty goods.
The partnership structure was formalized in the third generation, when the founding families — by then a network of five related clans — consolidated the individual farm operations under a common commercial entity. The founding deed was drafted by legal practitioners the founding families had engaged, and it was presented to the broader farming community as the mechanism that would give small-holder farms access to the corridor market they could not reach independently. Forty-three farms signed in the first year.
---
## Operations
**The agricultural base:** The forty-three member farms produce a range of goods: botanical oils from multiple cultivated varieties (the olive-analogue pressed oil is the primary export volume); fermented and preserved vegetables from a tradition that includes both long-aging and quick-brine formats; bark-cork products from the local species that has proven workable for the inner-corridor specialist market; and a small amount of dried aromatic herb production that moves partly to inner-corridor culinary buyers and partly to botanical spirit producers in adjacent systems.
**Export logistics:** The partnership maintains a freight consolidation facility at Caparica's primary transit node. Member farm production flows into the facility, where it is sorted, quality-assessed, certified, and assembled into outbound shipments under the Alentejo brand. The logistics operation employs twenty-two people and manages relationships with south_reach freight handlers and inner-corridor specialty distributors.
**Quality certification:** Alentejo Partners holds Lattice Commission agricultural product certifications for its primary export categories. The certification maintenance work is handled by the partnership's administrative office, staffed by employees of the partnership rather than by member farms. Members participate in the production quality standards that certification requires; they do not manage the certification process directly.
**Pricing:** Member farms are compensated based on aggregate production volumes, less a deduction described in the partnership deed as "certification, logistics, and operations overhead." This deduction is presented to members as a cost-of-service line in their annual production accounts. It is not itemized at the line level. Members receive net proceeds and the aggregate overhead percentage; they do not receive a breakdown of what the overhead funds.
---
## Products
**Alentejo Botanical Oils** — the primary export volume and the brand's most recognized product category. The pressed botanical oil from the olive-analogue cultivar is graded by the partnership into three tiers: single-farm certified (premium, individual farm identity, limited volume), blend-certified (mid-grade, the bulk of export volume), and culinary standard (commodity-adjacent, for distribution channels where price matters more than provenance). The single-farm certified tier commands inner-corridor premium prices and has the brand's best distribution relationships.
**Alentejo Preserved Goods** — fermented and oil-preserved vegetables, small-batch production, handled through specialty distributors who place them with inner-corridor buyers interested in south_reach agricultural traditions. Smaller revenue contribution than the oils but higher margin. The preserved-good tradition is what most corridor residents associate with the Alentejo name when they have heard of it at all.
**Cork and Bark Products** — sealing materials and bark-derived craft products from the local species. A modest secondary export. The inner-corridor craft and specialty materials market finds Caparica cork-bark useful; it is not the brand's identity but provides consistent supplementary revenue.
**Aromatic Herb Exports** — dried herb production from member farms with the right conditions for aromatic cultivation. Sold partly to culinary buyers and partly as raw botanical inputs to spirit producers. The volume is small; the relationship with buyers in adjacent south_reach systems provides useful commercial diversity for member farms that can grow aromatic varieties.
---
## Political Relationships
**Algarve Botanics:** The Cardoso-Ferreira family's botanical spirit operation at Inhambane (GJ 54) sources a portion of its supplementary aromatic inputs from south_reach agricultural producers. Alentejo Partners supplies dried aromatic herbs to the Algarve operation through a standing supply contract. The commercial relationship is modest in scale — Algarve's primary botanical cultivation is in-system — but consistent. The Alentejo herbs that appear in Algarve's secondary botanical blend are listed on the Algarve product documentation as "south_reach corridor aromatics."
**Ferreira Monteiro:** South_reach commercial law and trade arbitration is Ferreira Monteiro's primary practice. The agricultural cooperative governance context — partnership deed interpretation, member rights, pricing dispute arbitration — falls within Ferreira's south_reach expertise. Alentejo Partners' legal work has historically been handled by a Caparica-based practitioner who is a correspondent of one of the founding families' original legal advisors. This is not Ferreira Monteiro.
**Member farm community:** Forty-three farm operations whose viability depends substantially on the partnership structure. Most are multi-generational operations that have been members since the founding era. The practical barrier to exit is high: leaving the partnership means losing access to certification, logistics infrastructure, and the Alentejo brand designation that their production has been marketed under. Several member farmers have expressed, at different times, concerns about the pricing structure's transparency. These concerns have been addressed through explanations that the overhead structure is standard for agricultural partnership arrangements of this type.
---
## What They Don't Talk About
The founding deed was revised once, in the generation after the original formation, when the founding family network expanded the partnership membership significantly and restructured the overhead deduction mechanism. The first revision was presented to members as an administrative update reflecting the partnership's growth. Copies of the original founding deed and the first revision are held in the partnership's administrative archive; the original copies held by member farms have, in most cases, been replaced over successive generations by partnership-issued current-text versions that do not preserve the revision history distinctly.
The overhead deduction structure in the first revision embedded a mechanism that the founding families' legal advisors designed as a permanent revenue instrument rather than a cost recovery mechanism. A component of the overhead deduction — documented in the revision as a "certification and administration premium" — flows not to the partnership's operational expenses but to a holding account distributed annually to the founding family network. This distribution is recorded in the partnership's internal accounts under operational cost categories that do not trigger external audit scrutiny. The founding families receive, in aggregate, approximately eleven percent of the total production value processed through the partnership each year, beyond any ordinary governance compensation.
Member farms do not know this mechanism exists. The pricing they receive is below what the market would produce for their production quality if they could negotiate directly. One member farmer — a third-generation operator named Tomás Figueiras-Braga whose olive-analogue production consistently achieves single-farm certification — retained an agricultural auditor eight months ago after his per-unit returns declined for the third consecutive year despite rising market prices for certified botanical oils. The auditor's report identified an anomaly in the overhead deduction structure and flagged it for clarification. The partnership's legal representative — the correspondent firm with longstanding connections to the founding families — advised the auditor that the structure was consistent with the founding deed and represented standard practice. The auditor has not accepted this explanation. The matter is unresolved.
---
## Gameplay Relevance
Alentejo Partners is a community-scale institutional story: a structure that disadvantages ordinary producers in ways that are not immediately visible, defended by the people who designed it and the practitioners they employ. The harm is diffuse; the evidence is documentary; the access is a challenge of institutional navigation rather than physical risk.
The productive investigation threads are:
- **The founding deed revision history** — the original founding deed and the first revision are in the partnership's administrative archive. A player who can access this archive and read the revision against the current-text version would see what changed and when. The founding families' current-text versions distributed to members are sanitized; the archive holds the original revisions. The difference is the mechanism.
- **The overhead distribution account** — the annual distribution to the founding family holding account is recorded in the partnership's internal accounts. Access requires either physical presence at the administrative archive or a source within the partnership's financial staff. The account has a name that is not self-explanatory and is not cross-referenced to the founding families in any document the member farms have seen.
- **Tomás Figueiras-Braga and the auditor** — both are accessible sources. Figueiras-Braga is motivated, has a specific production quality grievance, and has retained an auditor with relevant findings. The auditor's unresolved flagging means the documentation of the anomaly already exists outside the partnership's control. A player who connects the auditor's findings to the founding deed revision history has enough to approach either the member farm community collectively or Ferreira Monteiro with a case the partnership's current legal representation cannot easily defend.
---
**Cross-References:**
- [Caparica](../star-systems/GJ-1002/index.md) — Headquarters system; founding agricultural landholdings; primary transit node
- [Algarve Botanics](algarve-botanics.md) — Supply relationship; south_reach aromatic herb exports as botanical inputs
- [Ferreira Monteiro](ferreira-monteiro.md) — South_reach commercial law and trade arbitration; relevant jurisdiction for partnership deed disputes
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/algarve-botanics.md
+91 -7
View File
@@ -1,24 +1,108 @@
---
title: "Algarve Botanics"
description: "Algarve Botanics — regional specialty producer based in Inhambane, south reach"
description: "South_reach botanical spirit producer based at Inhambane (GJ 54) — Portuguese coastal heritage adapted to warm-climate aromatics, a gin-and-bitters tradition sixty years in the making, and an artisanal independence story that is mostly accurate"
slug: algarve-botanics
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Inhambane (GJ 54)
tags: [terroir, south_reach, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [salud-alliance]
---
# Algarve Botanics
**Type:** Corporation — Regional Specialty Producer
**Type:** Corporation — Botanical Spirit and Extract Producer
**Also Known As:** Algarve, the Botanics
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Inhambane (GJ 54)
**Scope:** Regional — south_reach corridor primary; inner-corridor specialty bar market secondary
**Headquarters:** Inhambane (GJ 54) — south_reach corridor
**Classification:** Sub-Syndic family enterprise; externally capitalized; founder-family operational control
Algarve Botanics is a regional specialty producer operating out of Inhambane (GJ 54). Details to be expanded.
---
## Overview
Algarve Botanics makes gin-analogues, aromatic bitters, and culinary botanical extracts from the warm-climate aromatic plants of the Inhambane system. The company is named for the Algarve region of southern Portugal — the origin heritage of the founding Cardoso-Ferreira family, who arrived at Inhambane in the wave_4 expansion and found that the system's warm coastal conditions bore a workable resemblance to the Mediterranean climate they were carrying in memory. The similarity is imperfect, the local botanical palette is genuinely different, and the products that have emerged from ninety years of working with Inhambane's native and introduced aromatics have their own character rather than being reproductions of an original. The brand name is a cultural claim, not a recipe.
What the corridor's bar culture discovered, beginning roughly sixty years ago, is that Algarve's flagship gin expression has an aromatic complexity that differs from anything produced in wetter or cooler systems, and that differs from itself in ways that change noticeably with the local growing season. This variability is now part of the brand proposition. Buyers who follow Algarve expect each release to be its own argument.
The company presents itself as a family operation. This description is accurate for the creative and operational control structure. The financial structure is somewhat more complicated.
---
## Origin
The Cardoso-Ferreira family arrived at Inhambane three generations ago with herb cuttings, a distillation apparatus, and the working assumption that the local climate would support the aromatic plants they knew. Some assumptions proved correct. Many of the initial plantings struggled or died. The second generation spent most of its productive years developing a working botanical palette from local plants and introduced cultivars that could thrive under Inhambane's conditions — warmer and more humid than the Algarve analogue, with a different seasonal pattern and a local microbial ecology that affected fermentation in unexpected ways.
The first commercial product — a juniper-primary gin expression using locally adapted juniper and a blend of indigenous coastal aromatics — appeared forty years ago and sold modestly in the south_reach corridor. The second product, an aromatic bitter series using a proprietary blend of native Inhambane botanical resins and bark extracts, found an audience in the inner-corridor bar trade sixty years ago and has grown steadily since. The bitter series is what established Algarve's reputation; the gin range extended it.
Sixty years ago, when the bitter series was first attracting attention and the company needed capital to expand production and distribution capacity, the current generation's grandmother negotiated an investment arrangement with a Syndic-tier commercial fund operating through the south_reach. The terms provided the expansion capital the family needed. The arrangement has not been publicly discussed since.
---
## Operations
**Production:** Botanical cultivation occupies approximately twelve hectares of the Cardoso-Ferreira family's landholding at Inhambane. The primary gin botanicals are grown in-system; a small number of supplementary aromatics are imported from the inner corridor. The bitter series uses a botanical blend that the family describes as proprietary and has not disclosed in its specifics. Distillation is conducted in copper pot stills the family designs and maintains in-house. The entire production operation employs nineteen people, most of them from families with multi-generational connections to the operation.
**Capital structure:** The commercial fund that invested sixty years ago holds preferred equity representing a thirty-eight percent economic interest in the company. Preferred equity receives priority distributions before common equity holders and holds liquidation preference in any sale. The family holds common equity and retains full operational and creative control. Any external investment or sale transaction requires the fund's consent under the investment agreement terms. The fund does not appear in any public company filing associated with Algarve Botanics; its interest is recorded in the private investment agreement and in the company's internal capitalization table.
**Distribution:** The gin range and bitter series move through specialist spirit distributors in the south_reach and through a small inner-corridor network that carries the products to bar trade buyers. Algarve does not use volume distribution channels; the production scale and the brand positioning both require placement with buyers who will manage the product appropriately.
---
## Products
**Algarve Coastal Gin** — the flagship expression. Built around a juniper base and a rotating selection of Inhambane coastal aromatics; the specific botanical blend varies seasonally, producing a product whose character shifts year to year. Long-standing buyers develop expectations for what the current release's botanical emphasis will be, based on the season's growing conditions. This variability is deliberate and now a category characteristic that no competitor has managed to replicate.
**Algarve Bitter Series** — the product that established the brand. Four expressions using different botanical combinations from Inhambane's native shrub and bark palette. The amber bitter (Amargo) is the most widely distributed; the dark bitter (Escuro) is a smaller production that commands a following in inner-corridor cocktail culture. The aromatic profile of the Escuro expression includes a native Inhambane bark resin that has no direct equivalent in other corridors' botanical pantries.
**Algarve Culinary Extracts** — a smaller commercial line: aromatic infusions and botanical concentrates sold to restaurant buyers and the higher end of the domestic culinary market. Supplementary revenue. Not the brand's identity, but commercially useful and a way of introducing Algarve's botanical palette to buyers who encounter it through food before spirits.
---
## Political Relationships
**Salud Alliance:** Salud operates pharmaceutical distribution and formulary management across the south_reach. Its formulary management function includes responsibility for classifying botanical compounds with physiological effects under Lattice Commission and regional pharmaceutical regulations. Algarve Botanics and Salud Alliance do not have a commercial relationship. The regulatory framework Salud administers is relevant to a question about one of Algarve's botanical compounds that the company has not raised with any regulator.
**South_reach spirit market:** Algarve occupies a niche position — too small for the volume channels, too distinct in character for buyers who want consistency. The bar trade buyers who carry Algarve are advocates rather than customers; they describe the product in terms of craft positioning and seasonal character. This advocacy network is the primary distribution mechanism for building inner-corridor presence, and it is fragile in the sense that reputation in bar trade is word-of-mouth and any significant quality or consistency change would propagate quickly through the network.
**The investor fund:** The Syndic-tier commercial fund that holds preferred equity is an external party in the capitalization structure. It does not involve itself in operations. It receives quarterly distributions. There is a standing clause in the investment agreement permitting the fund to trigger a buyout review if production-weighted revenue falls below a defined threshold for three consecutive years. The threshold has not been reached. The family is aware the clause exists.
---
## What They Don't Talk About
The Cardoso-Ferreira family's head formulator for the first thirty years of the bitter series was a woman named Elisa Melo-Cardoso, a cousin of the second generation who developed most of the proprietary botanical blend. Eight years ago, she was passed over for the head formulator role in favor of the current generation's eldest son. She left the company.
Before she left, she took her personal research journals. The journals document, among other things, a discovery she made twenty-two years ago regarding one of the native Inhambane bark resins used in the Escuro bitter — specifically, that the compound class responsible for the resin's aromatic character has a secondary pharmacological interaction with a common pharmaceutical category when both are present in sufficient concentration. At the levels used in the Escuro bitter's standard production, the concentration falls below the threshold for Commission pharmacological concern. In combination with certain prescribed pharmaceutical agents at standard dosages, the combination produces neurological effects that are not noted on the Escuro bottle or in any Algarve product documentation.
The Cardoso-Ferreira family became aware of this finding when Elisa Melo-Cardoso raised it internally. The response was to reformulate the Escuro expression to reduce the resin concentration, which addressed the most obvious risk without requiring regulatory disclosure. The reformulation changed the aromatic character enough that long-standing buyers noticed; the company attributed the change to a seasonal botanical variation. Elisa Melo-Cardoso's journals remain in her possession. She currently works at a pharmacological research station in the Ran system and has not disclosed the journals' contents to any external party.
---
## Gameplay Relevance
Algarve Botanics is not a primary investigative target in most scenarios. It is a point of entry into the intersection of botanical product regulation, pharmaceutical governance, and the gap between what artisanal producers know about their products and what they disclose.
The productive investigation threads are:
- **Elisa Melo-Cardoso** — she is accessible, employed in the Ran system, and in possession of documentation she hasn't decided what to do with. A player who locates her and understands what the journals contain has a path to either a Salud Alliance referral (regulatory disclosure) or leverage with the Cardoso-Ferreira family (private). Her motivation for any of these paths would depend on the conversation.
- **The pharmacological compound** — Salud Alliance's formulary database would classify the relevant compound class if queried correctly. A player who knows what to look for in the regulatory framework and can access the Escuro bitter's reformulation records (the change is documented in the production archive) can establish the timeline between discovery and response.
- **The investor fund** — the preferred equity structure is in the private investment agreement. Accessing the agreement requires either the company's internal records or a source with knowledge of the arrangement. The terms of the buyout review clause are relevant to anyone interested in the company's future ownership trajectory.
---
**Cross-References:**
- [Inhambane](../star-systems/GJ-54/index.md) — Headquarters system; botanical cultivation; founding Cardoso-Ferreira landholding
- [Salud Alliance](salud-alliance.md) — South_reach pharmaceutical distribution and formulary management; regulatory context for botanical compound classification
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/arclamp.md
+83 -7
View File
@@ -1,24 +1,100 @@
---
title: "Arclamp"
description: "Arclamp — design and furniture manufacturer based in Groombridge, core"
description: "Groombridge furniture and interior design manufacturer — institutional and residential fittings for the core corridor's financial district, built for clients who regard their offices as statements of considered permanence"
slug: arclamp
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Groombridge (GJ 380)
tags: [design_heritage, core, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [groombridge-settlement-house, alcyone-tech, comptoir-lendel]
---
# Arclamp
**Type:** Corporation — Design And Furniture Manufacturer
**Type:** Corporation — Furniture and Interior Design Manufacturer
**Also Known As:** Arclamp Design
**Status:** Canonical
**Scope:** Regional — core operations
**Headquarters:** Groombridge (GJ 380)
**Scope:** Core primary; premium institutional market across the inner corridor secondary
**Headquarters:** Groombridge (GJ 380), Lendel district
**Classification:** Sub-Syndic design enterprise; institutional and residential supply
Arclamp is a design and furniture manufacturer operating out of Groombridge (GJ 380). Details to be expanded.
---
## Overview
The financial houses of Groombridge's Lendel district are not primarily offices. They are arguments. The argument a settlement house makes with its lobby flooring, its reception millwork, and the weight of its furniture — that argument is made before a word is spoken, and it persists after every meeting ends. Arclamp has been making this argument on behalf of Groombridge's institutional class for sixty years.
The company manufactures furniture and interior fittings for the high end of the institutional market: financial houses, legal firms, settlement offices, and the larger commercial operations that want their working environment to communicate what they cannot say directly. Arclamp's product language is not fashion. It does not have a spring collection. Its chairs and tables and shelving systems are designed to look appropriate in twenty years, in thirty, in fifty — because its clients do not renovate on whims and do not want the contents of their offices dating them. The vocabulary is restrained, material-forward, and technically precise. A piece identified as Arclamp in a Lendel lobby communicates, to anyone who recognizes it, that the institution behind the lobby has been here long enough to have views about what lasts.
---
## Origin
Arclamp was established fifty-eight years ago by a cabinetmaker named Imre Vásárhelyi who had come to Groombridge as a skilled-labor transit worker and stayed when he found that the financial district's demand for quality fittings was being supplied by off-system manufacturers who shipped generic institutional furniture to a clientele that could pay for something specific. His initial workshop took commissions for custom millwork — bookshelves, reception counters, document storage systems — and built a reputation over fifteen years before the operation grew into a manufacturing concern.
The transition from custom workshop to industrial manufacturer was managed carefully. Vásárhelyi's position was that industrial scale was compatible with institutional quality if the manufacturing process was designed around the client's actual need rather than around the manufacturer's production convenience. The current facility reflects this: manufacturing capacity that can produce at volume, but specification tolerances and quality control that would not embarrass a bespoke workshop.
The company has remained under family control across two generations. The current managing director is Vásárhelyi's granddaughter, who trained as an architect before returning to Groombridge.
---
## Operations
**Product lines:** Seating — task, reception, and conference seating with long service-life upholstery and hardwood or metal frames specified for institutional use. Millwork systems — modular shelving, document storage, and counter installations designed to integrate with Lendel district office architecture. Table systems — conference, meeting, and workstation surfaces in materials specified to maintain appearance under decades of use. Custom commissions remain a minority but prestigious fraction of output.
**Manufacturing:** Single facility in the Lendel district's manufacturing quarter. Eighty-three employees. The manufacturing floor uses CNC tooling for precision dimensioning but relies on skilled labor for assembly and finishing — the phase of production that determines whether the output looks built or manufactured. This distinction is real and it costs money.
**Client relationships:** Predominantly long-term institutional accounts maintained through atelier relationships — Arclamp assigns a design advisor to each major account who tracks the client's office through fit-outs and refreshes over decades. This relationship model is expensive in staff time and is what justifies Arclamp's price position.
**Distribution:** Groombridge and immediate adjacent systems. Physical products that require installation by skilled fitters do not travel twelve hops. The premium Arclamp commands in its local market reflects, in part, the absence of equivalent local competition.
---
## Political Relationships
**Groombridge Settlement House:** GSH is Arclamp's largest single institutional client and the relationship that underwrites the company's premium market positioning. The Settlement House's procurement committee reviews all furnishing suppliers against a certification and quality standard that Arclamp has met continuously for thirty years. A certification gap — such as one arising from the unreported bracket specification change — would expose Arclamp to procurement review at its most consequential client at the same time that it would expose GSH's procurement records to the question of whether its committee process adequately verified supplier certifications.
**Alcyone Tech:** Both companies serve the Lendel district's financial institutions through long-term institutional relationships, and both are currently holding undisclosed product specification issues that the Lattice Commission has not been informed of. The parallel is not a formal relationship, but it means that any regulatory review triggered by one company's issue would create the environment in which the other's issue is more likely to surface.
**Comptoir Lendel:** Arclamp and Comptoir Lendel share the same premium institutional client base in the Lendel district. The Comptoir's provenance-authenticated hospitality products and Arclamp's institutional furniture appear in the same offices and meeting rooms. Their shared clients expect both to deliver what their documentation claims.
---
## What They Don't Talk About
Arclamp's institutional seating line includes a load-bearing bracket system — the internal spine that determines how a chair ages under daily use. The bracket was independently certified under the Lattice Commission's commercial furniture standards eight years ago, certifying it for a service life of fifteen years under standard institutional load conditions.
Eighteen months ago, Arclamp's materials procurement shifted the bracket's composite specification to a slightly lower-grade alloy — not the certified alloy, but within a tolerance band that Arclamp's internal engineering team assessed as functionally equivalent. The certification was not resubmitted. Arclamp's position is that the substitution falls within the manufacturing tolerances documented in the original certification filing and does not require resubmission. The Commission's position, if asked, would likely be that any specification change requires recertification review.
The substitution reduced unit materials cost by nine percent. The seating line has been shipping with the new specification for fourteen months. No institutional client has been notified. The change does not appear in the product documentation available to purchasers. The service-life claim of fifteen years on current products is drawn from certification data that applies to the previous specification.
---
## Gameplay Relevance
Arclamp is ambient institutional texture for the Groombridge financial district — the chairs in the settlement house meeting rooms, the millwork in Meridian Risk's underwriting offices. It is not a primary investigation target but is a useful information layer for a player oriented toward supply chain and procurement irregularities.
The certification gap is the investigative thread. A player with access to Arclamp's internal procurement records and the original certification filing can demonstrate the specification change and the decision not to resubmit. The institutions whose furniture carries the changed specification — which includes most of the Lendel district's major financial houses — have a material interest in knowing whether their office fittings will perform to the certified standard over the service life they were sold against.
The design atelier relationship model also means that Arclamp's advisors have long-term visibility into client office configurations and renovation histories, making them incidental sources on the interior lives of Groombridge institutions.
If the bracket substitution is exposed, Arclamp's liability picture is significant: every institutional client whose seating carries the modified specification has a claim against the fifteen-year service-life representation. Re-certification of the current specification — the straightforward remediation — would require Arclamp to disclose the substitution to clients as part of the certification process, which is the disclosure the company has been avoiding. The financial houses of the Lendel district regard their relationships with suppliers as matters of institutional trust; a demonstrated gap between Arclamp's certification claims and its product specification would damage the company's market position in the only market it operates in. The atelier model, its primary competitive advantage, depends entirely on clients believing that what Arclamp tells them is accurate.
---
**Cross-References:**
- [Groombridge](../star-systems/GJ-380/index.md) — Headquarters and primary market
- [Groombridge Settlement House](groombridge-settlement-house.md) — Primary institutional client
- [Alcyone Tech](alcyone-tech.md) — Shared institutional client base; Lendel district overlap
- [Comptoir Lendel](comptoir-lendel.md) — Adjacent Lendel district enterprise; overlapping premium clientele
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/ashwick-broadcasting.md
+79 -7
View File
@@ -1,24 +1,96 @@
---
title: "Ashwick Broadcasting"
description: "Ashwick Broadcasting — cultural content producer based in Ashfield, north reach"
description: "North_reach documentary broadcaster at Ashfield (GJ 178) — eighty years of corridor documentaries, community portraiture, and editorial independence maintained in a through-route settlement that has never fully decided whether it is a waystation or a home"
slug: ashwick-broadcasting
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Ashfield (GJ 178)
tags: [cultural, north_reach, tractus, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [adams-ford-publishing]
---
# Ashwick Broadcasting
**Type:** Corporation — Cultural Content Producer
**Type:** Corporation — Documentary and Cultural Broadcasting
**Also Known As:** Ashwick, the station
**Status:** Canonical
**Scope:** Regional — north reach operations
**Headquarters:** Ashfield (GJ 178)
**Scope:** North_reach corridor primary; reach-wide documentary syndication secondary
**Headquarters:** Ashfield (GJ 178) — 2-aperture through_route, north_reach corridor
**Classification:** Sub-Syndic media enterprise; editorially independent
Ashwick Broadcasting is a cultural content producer operating out of Ashfield (GJ 178). Details to be expanded.
---
## Overview
Ashfield is a community in the middle of a question it has been asking for two hundred years: is this a place people pass through, or a place people stay? The through-route topology processes corridor traffic in both directions. Residents have watched the debate from both sides — some of them arrived as transit passengers who stayed, some of them grew up watching transit passengers leave, some of them are still deciding. The question has never been formally resolved, and shows no sign of being resolved, and Ashfield's culture has organized itself around living with that ambiguity rather than settling it.
Ashwick Broadcasting was founded in this environment eighty years ago by a documentary filmmaker who had spent the previous fifteen years making work about outer reach communities at the edges of organized settlement. She came to Ashfield for a three-month project and recognized in the system's unresolved identity question a story that did not have an ending yet. She stayed. The station was established in a converted ceramics drying facility on the outskirts of Ashfield's main settlement, and it has been broadcasting from there ever since.
The work Ashwick produces is not entertainment in the sense that Meridian's major syndication networks mean the term. It is documentary in the tradition of communities telling their own stories before someone else tells those stories for them. The north reach corridor — warm and hazy under the ash-diffused light of an F6V star, volcanic, marked by the specific beauty of places that are hard to reach and harder to stay in — is Ashwick's primary subject, and eighty years of continuous coverage has produced an archive that is, for north reach corridor systems, the closest thing to institutional memory that is publicly accessible.
---
## Origin
The founding filmmaker, Nora Ashwick — who gave the station its name and who is, at ninety-four and non-Perpetual, still the editorial board's senior emeritus — had built her early career covering communities in the outer reach that the major syndicates considered too remote for commercial investment. She understood, from fifteen years of this work, that the major syndicates' disinterest in remote systems was not just a commercial calculation but an epistemological one: they did not know what to look for in communities that did not organize themselves around the same signals of significance that core systems did. Her solution was to be present for long enough to find out.
Ashfield attracted her because the ceramics industry had done something unexpected: it had given a through-route settlement a product with reach-wide market presence, which meant the settlement was being seen from the outside in ways that required it to think about its own identity. The documentary she originally came to make — about the ceramics cooperative and its relationship to the system's transit character — became something larger when she realized the transit character was the ceramics character. The ash-blend clay that made Ashfield's ceramics distinctive was the same volcanic history that made the settlement uncertain about itself. She had found the story.
The station was incorporated with a small endowment from the ceramics cooperative, which has maintained a formal relationship with Ashwick through two changes of cooperative leadership. The relationship is editorially independent — the cooperative does not have input on programming decisions — but the founding connection means Ashwick's coverage of the ceramics industry has a particular texture of access that other broadcasters covering the corridor do not have.
---
## Operations
**Production:** A permanent editorial team of eight at Ashfield, supplemented by deployed field crews. The editorial team is small; Ashwick has operated at roughly this size for forty years. The station does not grow. When Ashwick's distribution reach expands — as it has three times in the past eighty years — the expansion is handled through syndication agreements rather than personnel scaling, which preserves the editorial character by keeping the editorial operation small enough to be coherent.
**Distribution:** North reach corridor primary distribution through direct terminal access at Ashfield, Singh's Landing, and adjacent systems. Reach-wide documentary syndication through a standing agreement with Adams & Ford Publishing Syndicate, which distributes Ashwick's long-form documentary content through its own Meridian channels. The relationship with Adams & Ford began as a single licensing arrangement forty years ago and has become a standing partnership; Adams & Ford's correspondents occasionally provide field material to Ashwick's documentary teams in exchange for regional archival access, and Ashwick's crews have provided verification support for several Guide entries covering north reach systems.
**Revenue:** Syndication fees from the Adams & Ford agreement and from three independent distributor relationships in the north reach corridor. Minor Assembly cultural broadcasting grant — a categorization that Ashwick qualified for as a regional public interest broadcaster and that the Assembly has not reconsidered despite Ashwick's subsequent coverage of Assembly-adjacent institutions. The grant is a small fraction of total revenue. Ashwick's editorial board has discussed declining it and has not done so, on the grounds that declining it would make the institution's editorial independence look defensive.
**Archive:** Eighty years of north reach documentary content, fully indexed and partially digitized. The archive is Ashwick's most significant institutional asset and its most operationally significant vulnerability — a fire or data event at the Ashfield facility would be irreplaceable. The cooperative's drying facility building has been renovated twice, and the archive storage is the reason the renovation specifications were what they were.
---
## Political Relationships
**Adams & Ford Publishing Syndicate:** The distribution partnership with Adams & Ford is Ashwick's most significant external relationship and its primary route to reach-wide audience. The arrangement began as a single licensing transaction and became, over twenty years, a standing editorial partnership — Adams & Ford's correspondents provide field material to Ashwick documentary teams in exchange for archival access to north reach footage that the Guide cannot produce itself. The two institutions share editorial independence as a core value, which is the reason the partnership has lasted and the reason each institution is careful not to depend on the other for decisions that should remain independent.
**Ashfield Ceramics Collective:** The founding endowment relationship means the Ceramics Collective holds a nominal historical connection to Ashwick's institutional structure, but not editorial participation. The Collective's current leadership has not attempted to exercise influence over programming and has not been tested on the question of whether it would. The transit combine freight relationship — the Collective uses a combine-affiliated logistics subsidiary for ceramic export — is the reason that relationship has not been tested.
**The Assembly broadcasting grant:** Ashwick qualified as a regional public-interest broadcaster under Assembly criteria that were written to support exactly the kind of corridor documentary work Ashwick produces. The grant is a minor fraction of operating revenue. The Assembly has not attempted to attach editorial conditions to the grant, and Ashwick has not declined it, because declining would signal a defensiveness that the editorial board considers counterproductive. The grant is a condition of the institution's life that both parties treat as unremarkable.
---
## What They Don't Talk About
Thirty-two months ago, Ashwick's lead investigative documentary journalist filed pre-production materials for a project covering a labor dispute at a belt mining operation in the outer north reach. The operation was run by a subsidiary of a transit combine with commercial relationships at several Assembly-adjacent institutions. The pre-production materials included footage of conditions at a rotating crew station that the combine had described, in Commission compliance filings, as compliant with residential standards. The footage showed conditions that were not what the filings described.
The materials were reviewed by Ashwick's editorial board. The board concluded that the footage's evidentiary chain was insufficient for broadcast — specifically, that the combine's legal team would challenge the identification of the specific station and the filing status of the specific crew rotation. The lead journalist was reassigned to research leave pending further source development. The research leave has extended for thirty-two months. The pre-production materials are in Ashwick's archive under a project designation that does not appear in the active production roster.
The lead journalist and the editorial board have not publicly disagreed. The ceramics cooperative, which is aware that Ashwick's relationship with the transit combine's regional logistics subsidiary includes freight services for ceramic exports, has not been involved in the editorial decision. Nora Ashwick, in her emeritus capacity, has not commented on this project publicly. She has commented on it privately to two members of the board, neither of whom has described those comments.
---
## Gameplay Relevance
Ashwick's archive is the primary investigative asset for any case touching the north reach corridor. Eighty years of documentary coverage means that most significant events in the corridor have Ashwick footage or research notes that predate any official record. Accessing the archive requires either a formal editorial relationship with the station or a route into the archival facility at Ashfield — which is a converted ceramics drying building that was built in a different era's security environment.
The suppressed documentary thread is the direct investigative entry. The lead journalist is on research leave rather than terminated — she is still, technically, an Ashwick employee with archival access. She has a complete account of what the pre-production footage showed and a specific view of the editorial board's decision that differs from the board's official position. Finding her requires understanding Ashwick's deployment patterns, which the station does not publish. What she has to say, once found, is the kind of testimony that gives other evidence its interpretive frame.
---
**Cross-References:**
- [Ashfield](../star-systems/GJ-178/index.md) — Headquarters system; volcanic ash plains; ceramics community
- [Adams & Ford Publishing Syndicate](adams-ford-publishing.md) — Reach-wide distribution partner; archival access exchange; forty-year standing relationship
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/atrium-culture.md
+84 -7
View File
@@ -1,24 +1,101 @@
---
title: "Atrium Culture"
description: "Atrium Culture — cultural content producer based in Groombridge, core"
description: "Groombridge cultural arts foundation — runs Lendel's primary exhibition and performance venue, commissions work from artists across the Reach, and presents itself as a model of independent cultural patronage while being funded by the financial houses it claims to be independent from"
slug: atrium-culture
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Groombridge (GJ 380)
tags: [cultural, core, tractus, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [groombridge-settlement-house, the-registry]
---
# Atrium Culture
**Type:** Corporation — Cultural Content Producer
**Type:** Corporation — Arts Foundation and Cultural Institution
**Also Known As:** the Atrium, Atrium Foundation
**Status:** Canonical
**Scope:** Regional — core operations
**Headquarters:** Groombridge (GJ 380)
**Scope:** Core primary; reach-wide cultural programming secondary
**Headquarters:** Lendel (GJ 380) — 2-aperture loop_member, 2 hops from Gateway
**Classification:** Endowment-funded cultural institution; formally independent, structurally integrated
Atrium Culture is a cultural content producer operating out of Groombridge (GJ 380). Details to be expanded.
---
## Overview
Lendel's cultural landscape is defined by the Atrium. This is not a modest claim; it is simply how the city has been organized for two hundred years. The Atrium runs the primary exhibition space, the major performance venue, and the annual cultural season that brings artists, musicians, and writers from across the Reach to a city that would otherwise have no particular reason to host them. A system whose exports are financial services and insurance does not, strictly speaking, need theatre. Groombridge has excellent theatre.
The Atrium presents itself as an independent cultural foundation — which it is, in the sense that it has its own governance structure, its own staff, and its own programming decisions made without direct instruction from its funders. The Atrium does not describe itself as the cultural programming arm of Groombridge's financial district. No one at the Atrium would use that phrase. If asked what the institution is for, they would say: the advancement of art and cultural expression in the Reach.
This is accurate. The institution genuinely produces serious, high-quality cultural programming. The artists it invites are accomplished. The exhibitions it mounts have critical standing. The performances it commissions have been received seriously in inner-corridor cultural discourse. The Atrium is not a facade. It is a real cultural institution that also serves a function its stated mission does not describe.
---
## Origin
The Atrium was established two hundred and twelve years ago, when Lendel had developed enough population, wealth, and civic self-consciousness to support cultural institutions beyond what the financial houses maintained privately for their own staff and clients. The founding endowment was contributed by seven of the major financial houses then operating in the district. The founding governance documents established the Atrium as an independent institution — separate legal entity, separate board, mandate to serve Lendel's cultural life broadly rather than the interests of any specific donor.
The founding families who drafted these documents were not naive about what they were creating. An independent cultural institution in a city that manages the Reach's financial accounts will attract, if it is good, the attention of the international community that does business in that city. Groombridge's reputation is its principal commercial asset. An institution that makes Groombridge appear civilized — genuinely civilized, through the quality of what it produces rather than the extravagance of what it spends — is an asset to the financial houses whether the institution understands that or not.
The founders understood it. The language in the founding governance documents does not mention it.
---
## Operations
**The venue:** The Atrium building in Lendel's center district is two centuries old, expanded and renovated twice, and operates three spaces: a main gallery for visual art exhibitions, a performance hall for music and theatre, and a smaller salon space for readings, lectures, and private cultural events. The building is architecturally significant for Lendel — one of the few structures whose design treats the city as a place worth building carefully for.
**Programming:** The Atrium operates an annual season of exhibitions and performances, supplemented by a commissioning program that funds original work from artists across the Reach. The commissioning program is selective and well-funded; an Atrium commission is, in Reach cultural circles, a mark of serious standing. The selection process is managed by a curatorial board that includes Atrium professional staff, rotating artist representatives, and four seats permanently held by representatives of the endowment's founding institutions.
**Endowment management:** The founding endowment has grown, through managed investment, to a scale that makes the Atrium financially independent from annual contributions. The institution does not need the financial houses to write checks every year. It needs the governance structure that gives those institutions four permanent curatorial board seats, which the original endowment documents established and which have never been successfully challenged.
**Staff:** The Atrium employs thirty-eight full-time staff across programming, operations, and administration. The curatorial director position — the role with most influence over programming decisions — has been held by professional arts administrators for the last hundred years. The current director has held the role for nine years and has a widely respected track record of selecting serious work.
---
## Political Relationships
**The financial houses of Groombridge:** The Atrium's relationship with its endowment contributors is stable and largely invisible in day-to-day programming decisions. The four permanent curatorial board seats are the operative connection. The financial houses do not attend Atrium performances as a bloc or make visible displays of institutional patronage. The relationship is more ambient: Groombridge produces a population that attends the Atrium because it is good, and the financial houses have ensured it remains good without requiring credit for having done so. This is the preferred form of influence in a system where the appearance of independence is part of the product.
**Artists and the wider cultural community:** The Atrium's external reputation is strong. An Atrium commission represents serious institutional investment in an artist's work, and the commissioning record over two centuries includes names that now have reach-wide standing. The artists who have shown at the Atrium do not, as a population, believe it is a captured institution. Most of them are correct about their own cases — the selection process is genuinely quality-driven — and none of them have access to the governance records that would allow them to evaluate the cases where it was not.
**The Lattice Commission:** No formal relationship. The Atrium is a cultural institution operating below any threshold that would trigger Commission oversight. This absence of regulatory relationship is part of what makes the institutional alignment framework sustainable — there is no external body conducting curatorial audits, and the internal governance records are maintained as private institutional documents.
---
## What They Don't Talk About
The curatorial board's assessment framework has two layers. The first layer — artistic quality, cultural significance, Reach-wide representation, critical standing — is what the Atrium describes publicly when explaining how works and artists are selected. This layer is real and consistently applied.
The second layer has no formal name. Within the curatorial board it is described, in the notes of internal meetings that have existed in archive form for over a century, as "institutional alignment." The concept does not appear in any public document. It operates as a secondary filter on artist selection: works and artists whose practice is explicitly politically destabilizing, or who have made prominent public statements on matters that touch directly on Groombridge's financial infrastructure and its governance, are noted as poor fits for Atrium programming. The reasoning recorded in board minutes is always framed in terms of "artistic fit" or "season coherence."
Approximately seven artists have been declined Atrium consideration in the past thirty years on grounds that, in board meeting records, attribute the decision primarily to institutional alignment concerns. In three of these cases, the curatorial staff had ranked the artist's work highly before the board review. In two of these cases, the artist had publicly criticized the Lattice Commission's financial certification framework.
The artists who were selected do not know the second filter existed. Neither do most of the Atrium's staff. The curatorial director knows. She has served on the board long enough to have encountered the concept explicitly. She has not contested it and has not described it publicly. She considers it a minor distortion in an institution she believes is genuinely doing important work.
---
## Gameplay Relevance
The Atrium is ambient cultural infrastructure — the kind of institution that appears in environmental setting detail as a mark of Lendel's civic character and as a backdrop for interactions among the financial class that moves through Groombridge. A long-stay commercial guest at an Altair hotel might have attended an Atrium performance the previous season; a Registry analyst might have a curatorial board contact.
The institutional alignment thread is an investigative entry point for players working on questions about how Groombridge's financial infrastructure manages its cultural reputation. The evidence trail is in board meeting archives — not digital records, but the physical archive of Atrium governance documents maintained on-site, which the Atrium regards as an internal institutional record rather than a public document. Accessing these archives requires either a formal governance relationship with the institution or a physical route into the archive space.
The curatorial director is the most direct source. She is not hostile to a careful investigator and is not a person who is comfortable with the second filter having existed for as long as it has. She will not volunteer information. Asked directly about the selection framework, asked about the archive, asked about specific artists who were not selected, she will answer — not fully, not without cost, but differently than someone who has nothing to hide.
---
**Cross-References:**
- [Groombridge](../star-systems/GJ-380/index.md) — Headquarters system; institutional context
- [Groombridge Settlement House](groombridge-settlement-house.md) — Founding endowment contributor; permanent board seats
- [The Registry](the-registry.md) — Endowment contributor; institutional adjacency
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/baektu-mining-alliance.md
+1 -1
View File
@@ -11,7 +11,7 @@ faction_type: economic
headquarters: Isivikelo (GJ 1111)
tags: [metallic_ore, rare_minerals, refined_metals, mining, south_reach, korean, assembly]
decision_refs: [D-175]
cross_refs: []
cross_refs: [stalownia-kowalski, umoja-freight, durban-engineering]
---
# Baektu Mining Alliance
wiki/corporations/baia-fundo-productions.md
+81 -7
View File
@@ -1,24 +1,98 @@
---
title: "Baia Fundo Productions"
description: "Baia Fundo Productions — cultural content producer based in Confluência, south reach"
description: "Confluência documentary and dramatic content studio — south reach cultural production with an editorial voice shaped by the coastal Brazilian heritage communities of the lower corridor"
slug: baia-fundo-productions
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Confluência (GJ 566B)
tags: [cultural, south_reach, tractus, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [open-corridor-stream, quebrada-cultural, sertanejo-design]
---
# Baia Fundo Productions
**Type:** Corporation — Cultural Content Producer
**Type:** Corporation — Documentary and Dramatic Content Studio
**Also Known As:** Baia Fundo, the Studio
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Confluência (GJ 566B)
**Scope:** South reach primary; inward corridor documentary distribution secondary
**Headquarters:** Confluência (GJ 566B) — south reach, 5 hops from Gateway
**Classification:** Sub-Syndic independent studio; original production and catalogue licensing
Baia Fundo Productions is a cultural content producer operating out of Confluência (GJ 566B). Details to be expanded.
---
## Overview
The south reach's cultural production landscape is uneven. The entertainment volume comes from inward platforms and high-output studios near Gateway. What the outer systems produce, when they produce it themselves, tends to be different in register — slower, more observational, built from the textures of specific places rather than the genre templates that travel easily across distances. Baia Fundo Productions occupies the serious end of south reach original content: documentary work, dramatic series rooted in corridor history, and archive projects that preserve cultural material from communities that did not expect their traditions to become interesting to anyone farther inward.
The studio does not compete with inward volume production. Its documentaries do not arrive with promotional campaigns and they do not open simultaneously across the corridor. They are made at the pace of their subjects, released to audiences who seek them out, and licensed to inward platforms years after production when a distribution deal can be arranged without surrendering editorial control. This is a deliberate position. Baia Fundo's reputation — modest in reach, specific in regard — is exactly what its team set out to build and has no interest in trading for scale.
---
## Origin
Baia Fundo was founded twenty-two years ago by a documentary producer named Catarina Salomão-Feijó who had spent a decade working for an inward production company commissioning south reach content. Her experience of that arrangement had given her a detailed understanding of what inward platforms wanted from outer reach material — the documentary equivalent of a travel piece, local color made legible for audiences who would never visit — and a clear sense of what it cost to produce to that specification. The cost was editorial: the stories that made compelling content for an inward audience were not always the stories the communities in them wanted told.
Salomão-Feijó's founding principle was that content made about the south reach should be made by people embedded in it, for an audience that included the people it depicted, not merely as subjects but as viewers. The Studio's first production — a three-part documentary about the fishing cooperatives of Confluência's coastal settlements — was distributed locally before it was offered outward. The approach was not commercially optimal. It established what Baia Fundo was.
---
## Operations
**Production:** The studio maintains a permanent production staff of fourteen, supplemented by freelance crews drawn from south reach systems. It produces four to six original works per year, ranging from single-feature documentaries to three-to-four-episode dramatic series. The production pace is slow by industry metrics. The studio does not commission projects it cannot complete without shortcuts.
**Archive work:** Baia Fundo holds a significant and growing archive of south reach cultural documentation — oral history recordings, community event footage, dialect recordings, and heritage material gathered during production that did not make final cuts. This archive is licensed to academic institutions and, selectively, to inward platforms for cultural context packages. Archive licensing has become a stable secondary revenue stream.
**Distribution:** Primary south reach corridor through local media networks. Inward distribution arranged through licensing agreements negotiated after production is complete — Baia Fundo does not pre-sell production to inward platforms because pre-sale structures the editorial result. The studio accepts the commercial disadvantage of this position.
**Catalogue:** Twenty-seven completed works spanning documentary and dramatic formats. The catalogue includes several pieces that have been adopted into regional education curricula, which the studio considers a more meaningful outcome than most commercial metrics.
---
## Political Relationships
**Open Corridor Stream:** The dominant inward distribution platform for outer reach content. Baia Fundo has a catalogue licensing arrangement with OCS that covers seventeen titles. The arrangement has been renegotiated twice, with Baia Fundo consistently accepting below-market licensing rates in exchange for retaining creative attribution standards and the right to direct viewers to its own south reach distribution channel.
**Confluência cultural institutions:** The studio has formal partnerships with two community cultural organizations and the Confluência arts council. These relationships provide production support, community access, and the institutional credibility that allows Baia Fundo's crews to document subjects that would not otherwise engage with a production company.
**Quebrada Cultural:** Baia Fundo's closest peer in the south reach's independent production sector. The two studios have co-produced two projects over the past decade and maintain a referral relationship for commissions that don't fit one studio's format but might fit the other's. Quebrada Cultural tends toward performative and installation work; Baia Fundo toward documentary and drama. The mutual referral functions as informal capacity sharing between organizations too small to turn down commissions easily.
---
## What They Don't Talk About
Baia Fundo's archive licensing revenue has grown to approximately 35% of annual income over the past six years. A portion of this archive — specifically, oral history recordings made during the studio's first decade — was gathered under community agreements that specified the material would not be commercialized without renewed consent from the originating communities.
The studio's legal position, developed when the first archive licensing deal was structured, is that the renewal-consent clause applies to primary broadcast use, not to contextual or educational licensing. The communities whose material is in the archive were not consulted when this interpretation was adopted. Several of the originating communities are no longer organizationally intact; the individuals who signed the original agreements have in many cases died. Baia Fundo's archive manager is aware that three of the communities that are intact would likely object to the current licensing scope if asked.
They have not been asked.
---
## Gameplay Relevance
Baia Fundo Productions is a cultural layer presence in the south reach — their completed works appear as viewable content in common areas, their production crews are recognizable on Confluência's docks, and their archive represents a substantial documentary record of south reach community life over the past two decades.
The archive consent question is the primary investigative thread. A player who accesses Baia Fundo's original community agreements and compares them to the current licensing catalogue will find the gap between what was permitted and what is being licensed. The communities whose material is affected vary in their ability to act on this information; the drama is in what happens when they learn it.
The studio's documentary archive is also independently valuable — as a record of communities, supply chains, and political relationships from the period it covers, it contains background material that appears nowhere else.
The archive's investigative value is two-directional: it documents what communities looked like before significant external changes, making it useful for tracing what changed and why. Several communities visible in Baia Fundo's early decade footage — fishing cooperatives, small-scale agricultural operations, heritage craft communities — have since contracted or dissolved under economic pressure. The footage predates the pressure and documents the organizational and social structures that existed before it arrived. For a player tracing economic or political changes across south reach communities, this is primary source material with no equivalent elsewhere in the corridor.
---
**Cross-References:**
- [Confluência](../star-systems/GJ-566B/index.md) — Headquarters; primary production context
- [Open Corridor Stream](open-corridor-stream.md) — Inward distribution partner; catalogue licensing
- [Quebrada Cultural](quebrada-cultural.md) — South reach cultural peer; occasional co-production
- [Sertanejo Design](sertanejo-design.md) — Adjacent south reach creative enterprise; shared client communities
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/bavarian-craft.md
+81 -7
View File
@@ -1,24 +1,98 @@
---
title: "Bavarian Craft"
description: "Bavarian Craft — heritage craft manufacturer based in Bergtor, west reach"
description: "Bergtor heritage woodcraft and traditional manufacturing concern — hand-finished furniture, decorative objects, and architectural woodwork produced under a guild certification that the company's actual production model only partially reflects"
slug: bavarian-craft
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Bergtor (GJ 505A)
tags: [heritage_craft, west_reach, mark, artisan]
decision_refs: [D-189]
cross_refs: []
cross_refs: [bergkraft-antriebswerke, steinbach-furniture, gronnmark-consumer]
---
# Bavarian Craft
**Type:** Corporation — Heritage Craft Manufacturer
**Type:** Corporation — Heritage Woodcraft and Artisan Manufacturing
**Also Known As:** the Craft, Bayerisches Handwerk (formal trade registration)
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Bergtor (GJ 505A)
**Scope:** West reach primary; inward corridor premium heritage market secondary
**Headquarters:** Bergtor (GJ 505A) — west reach, 4 hops from Gateway
**Classification:** Sub-Syndic heritage enterprise; guild-certified artisan producer
Bavarian Craft is a heritage craft manufacturer operating out of Bergtor (GJ 505A). Details to be expanded.
---
## Overview
There is a specific class of object that Bavarian Craft produces — a table, a cabinet, a carved door frame — that occupies a position in the west reach's interior culture that no mass-produced equivalent can replace. The company's public identity rests on this: four centuries of Bavarian craft tradition carried intact through corridor transit, preserved at Bergtor, and expressed in objects made by skilled hands using techniques that predate industrial manufacturing. The furniture in the Confluent town hall is Bavarian Craft. The reception desk at the Bergtor Guild Exchange is Bavarian Craft. The certificate of guild membership issued to a new master carpenter is printed on paper Bavarian Craft made.
This identity is not fabricated. The techniques are real, the master craftspeople are genuinely qualified, and the objects produced to the company's full-process specification are exactly what the branding claims. The problem is that the full-process specification applies to a fraction of what Bavarian Craft ships.
---
## Origin
The founding families arrived at Bergtor with skills, tools, and an organizational structure — the guild — that they considered as essential to transport as the tools themselves. The guild system that Bavarian Craft descends from was reconstituted at Bergtor within fifteen years of the first settlement, with formal membership requirements, apprenticeship standards, and a certification process for finished works. For two centuries this structure governed everything the local craftspeople produced.
Industrialization came in two waves. The first, a century and a half ago, was modest — power tools, improved kilns, manufactured adhesives that simplified joinery. The guild absorbed these as efficiency enhancements to traditional process and maintained the certification standards. The second wave, forty years ago, was structural: a factory facility with CNC routing, automated finishing, and a production capacity that made the guild workshop look like a hobby operation. Bavarian Craft built the factory. The guild certification persisted.
---
## Operations
**Workshop tier:** Forty-two guild-certified craftspeople working in the original workshop facility. Full traditional process: hand-joinery, hand-finish, individual certification stamps. Produces approximately 12% of unit volume. Supplies the collector market, major institutional commissions, and the export pieces that appear in inward premium showrooms. Lead times are measured in months.
**Factory tier:** The manufacturing facility outside central Bergtor. Automated routing, machine finishing, assembly line with skilled oversight. Produces 88% of unit volume. Employs ninety people in production roles, the majority of whom are not guild-certified. Ships the residential and commercial contract market, catalogue retail, and the volume accounts that represent Bavarian Craft's actual revenue base.
**Certification:** Guild certification marks appear on workshop-tier products and select factory-tier products that receive final hand-finishing and inspection by a guild craftsperson. The definition of "guild-finished" has been progressively expanded over two decades to include products where the craftsperson's involvement is limited to inspection and stamp application rather than any fabrication.
**Distribution:** West reach residential, commercial, and institutional markets. Inward distribution through heritage furniture retailers who position the brand as authentic Bergtor craft. The retailers' marketing materials describe products as "handcrafted in the Bavarian tradition" without distinguishing tiers.
---
## Political Relationships
**Bergkraft Antriebswerke:** Bavarian Craft and Bergkraft share Bergtor's industrial district and the same set of local governance relationships. Both companies have contributed to the district's employment base in ways that give them mutual interest in the regulatory environment remaining stable. Neither company benefits from heightened regulatory scrutiny of Bergtor manufacturing, and both are aware of this alignment, though it has not been formalized.
**Steinbach Furniture:** Steinbach is Bavarian Craft's most direct west reach competitor in the heritage furniture market and the company most invested in the guild certification system retaining its meaning. If Bavarian Craft's bylaw interpretation were to become public, Steinbach would be positioned to challenge it — either through the guild governance process or through the legal authority. The competitive dynamics between the two companies have constrained Bavarian Craft's willingness to seek any formal re-clarification of the bylaw, since any clarification process would require disclosure to the same governance board where Steinbach holds a seat.
**Gronnmark Consumer:** Gronnmark's distribution network carries some Bavarian Craft catalogue items in the west reach mass market. The arrangement is commercially useful for Bavarian Craft's volume line but creates a brand positioning tension — the same items sold in Gronnmark's channel at mass-market price points appear near products whose marketing emphasizes handcraft provenance. Neither company has addressed this tension publicly.
---
## What They Don't Talk About
The guild certification that Bavarian Craft's marketing centers on formally requires that certified products involve a guild master craftsperson in "substantive production process" — a phrase from the original guild charter that was intended to mean fabrication. Twenty years ago, the guild's governance board approved a bylaw interpretation that extended "substantive" to include final quality inspection: a guild master who examines a factory-produced piece, certifies it meets quality standards, and applies the certification stamp is considered to have participated in substantive process.
This interpretation was not published. It appears in a board resolution document archived in the guild's records at Bergtor but is not referenced in the certification standards document that clients, retailers, and regulatory bodies rely on when assessing what a certification stamp means. The Commission's heritage craft standards accept guild certification as evidence of artisan production; those standards reference the guild's published certification requirements, not the bylaw resolution.
Products carrying Bavarian Craft's guild mark that were produced entirely by machine are being sold as artisan-certified goods to buyers who understand that certification to mean something it now technically does not. The legal team's assessment is that the bylaw interpretation is valid under guild governance rules. The question of whether it is valid under consumer representation law has not been tested.
---
## Gameplay Relevance
Bavarian Craft is ambient cultural presence in west reach systems — recognizable furniture in institutional and residential settings, guild marks visible on publicly accessible objects in Bergtor and Confluent. A player with an eye for manufactured detail may notice that some guild-marked pieces have consistency inconsistent with hand manufacture.
The certification interpretation is the investigative thread. The board resolution document exists in the guild's archives. The gap between what the certification is understood to mean — by retailers, by the Lattice Commission, by buyers — and what the bylaw interpretation allows is the substance of a consumer representation case that no one has brought because no one outside the guild's governance board knows the bylaw exists.
Bavarian Craft's factory facility also represents a significant portion of Bergtor's manufacturing employment and economic activity, which gives the company political relationships with local governance that complicate straightforward regulatory challenge.
The political complexity matters for investigative framing. A consumer representation complaint against Bavarian Craft lands at the west reach legal authority and, if escalated, at the Lattice Commission's heritage certification standards body. Both bodies have institutional reasons to prefer that the case not require the Commission to reexamine what guild certification means across the heritage craft sector — because Bavarian Craft is not the only heritage craft producer whose certification practices have evolved under similar pressures. Exposing the bylaw interpretation opens a question that extends well beyond one company at Bergtor. A player building this case should expect institutional friction proportional to the breadth of what the case implies, not just to Bavarian Craft's individual exposure.
---
**Cross-References:**
- [Bergtor](../star-systems/GJ-505A/index.md) — Headquarters; guild seat; manufacturing facility location
- [Bergkraft Antriebswerke](bergkraft-antriebswerke.md) — Bergtor peer enterprise; shared regional industrial context
- [Steinbach Furniture](steinbach-furniture.md) — West reach furniture peer; competing market position
- [Gronnmark Consumer](gronnmark-consumer.md) — West reach consumer goods; distribution channel overlap
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/bergkraft-antriebswerke.md
+83 -7
View File
@@ -1,24 +1,100 @@
---
title: "Bergkraft Antriebswerke"
description: "Bergkraft Antriebswerke — precision technology manufacturer based in Bergtor, west reach"
description: "Bergtor precision drive and propulsion systems manufacturer — industrial and transit vehicle drive units certified for west reach operational conditions, with a certification history that contains one unaddressed discrepancy"
slug: bergkraft-antriebswerke
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Bergtor (GJ 505A)
tags: [drive_cores, tech_premium, west_reach, mark, electronics]
decision_refs: [D-175, D-189]
cross_refs: []
cross_refs: [bavarian-craft, rheintal-systems, durban-engineering]
---
# Bergkraft Antriebswerke
**Type:** Corporation — Precision Technology Manufacturer
**Type:** Corporation — Precision Drive and Propulsion Systems Manufacturer
**Also Known As:** Bergkraft, BKA
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Bergtor (GJ 505A)
**Scope:** West reach primary; inward industrial procurement secondary
**Headquarters:** Bergtor (GJ 505A) — west reach, 4 hops from Gateway
**Classification:** Sub-Syndic precision engineering enterprise; industrial supply and transit systems
Bergkraft Antriebswerke is a precision technology manufacturer operating out of Bergtor (GJ 505A). Details to be expanded.
---
## Overview
Transit between systems at the outer reach runs on drive units that have to perform reliably across temperature extremes, maintenance intervals measured in months rather than days, and operator skill levels that range from expert to barely adequate. Bergkraft Antriebswerke makes drive systems for this environment — not the precision instruments of the core corridor's advanced manufacturing, but the robust, serviceable, repairable drive units that keep industrial vehicles, atmospheric transports, and light cargo carriers moving across the west reach's varied terrain and variable-quality maintenance infrastructure.
The company's reputation is built on longevity. A Bergkraft drive unit running in the mining operations at Freiholt, maintained to minimum service intervals, will still be producing rated output after twelve years. This is what the mining companies pay for, and Bergkraft's pricing reflects it. The company does not compete on cost with inward commodity drive suppliers. It competes on the expected life-cycle cost of running equipment in conditions where inward commodity units fail early and replacement logistics are expensive.
---
## Origin
Bergkraft was established sixty years ago by a mechanical engineer named Ernst Hörmann who had come to Bergtor as a maintenance contractor for the early-era mining operations and concluded that the drive systems being imported from inward suppliers were not designed for the environmental conditions of the outer reach. The imported units met their rated specifications under test conditions that bore little resemblance to a Bergtor mine.
Hörmann's founding insight was environmental specificity: drive units designed and tested for the actual conditions of west reach industrial use — temperature cycling, particulate contamination, extended service intervals, rough-terrain vibration loads — would perform better and last longer than general-purpose designs certified against laboratory conditions. He was right, and the mining companies that converted to Bergkraft units during the first decade documented the performance difference in ways that made Bergkraft's market position very difficult to displace.
The company has been the dominant industrial drive supplier for Bergtor and adjacent systems for forty years.
---
## Operations
**Product lines:** Industrial drive units for mining vehicles, surface transports, and materials-handling equipment. Atmospheric propulsion systems for light cargo carriers and personnel transports. Auxiliary power units for fixed installations. Custom drive configurations for engineering applications that standard catalogue units don't fit. The product range is not wide; it is deep in the areas Bergkraft actually understands.
**Manufacturing:** Single integrated facility at Bergtor. One hundred and twelve employees, of whom approximately forty are skilled engineering staff. The facility manufactures to order for most industrial clients — batch production for the catalogue lines, custom engineering for the commission work. Lead times are longer than inward commodity suppliers; clients accept this because the product quality is not available on short lead times from anyone else.
**Certification:** Lattice Commission industrial drive certification for all product lines, renewed on the standard five-year cycle. BKA's certification record is clean and its certification documentation is maintained with a thoroughness that reflects the company's understanding that its market position depends on this record.
**Service network:** Small but functional. BKA maintains service engineers at three west reach systems and a parts depot at Confluent. The service network is not a profit center; it is a client retention mechanism. Mining operations that know a BKA service engineer can reach them within forty-eight hours buy BKA.
---
## Political Relationships
**Bavarian Craft:** Both companies operate from Bergtor's industrial district and share local governance relationships and political exposure. Bavarian Craft's guild certification situation and Bergkraft's Commission certification discrepancy are structurally similar — both involve external representations that internal documentation does not fully support. Neither company benefits from the other's situation becoming visible.
**Rheintal Systems:** Rheintal is Bergkraft's primary west reach competitor for industrial drive systems and the company most positioned to benefit from a Bergkraft certification finding. Rheintal has been unable to displace Bergkraft from its established mining accounts despite comparable pricing, partly because the switching cost for a certified drive system is high. A certification challenge requiring resubmission of the Series 9 would create a re-evaluation window that Rheintal is positioned to exploit.
**Durban Engineering:** Durban supplies industrial engineering systems in adjacent application areas and holds an occasional supply relationship with Bergkraft for specialized components. The relationship is arms-length commercial but gives Durban's procurement team more visibility into Bergkraft's component sourcing than a purely competitive observer would have.
---
## What They Don't Talk About
The flagship Series 9 industrial drive unit — Bergkraft's highest-volume product line and the unit that underwrites most of its institutional mining contracts — was certified five years ago using a test fixture batch that was machined to tolerances tighter than the documented manufacturing specification. The test batch met certification parameters. The production run, manufactured to the documented spec, runs measurably closer to the performance limits that the certification test was supposed to demonstrate were not being approached.
Bergkraft's engineering team identified the fixture discrepancy during the post-certification manufacturing audit. The internal report concluded that the production specification was within the tolerance band of the original design intent and that no individual unit would fail in a way that triggered recall. What the report did not say — but the senior engineering staff discussed — is that a fleet of Series 9 units operating under sustained high-load conditions, over the twelve-year service life the product is sold against, would show performance degradation in the final three years that the certification tests did not predict.
The decision not to resubmit the certification — which would require disclosing the fixture discrepancy to the Commission — was made by BKA's technical board. The Series 9 continues to be sold with a twelve-year performance claim that was documented against a test batch the production line cannot replicate.
---
## Gameplay Relevance
Bergkraft Antriebswerke is industrial background infrastructure for the west reach — its drive units are in the mining equipment, the cargo haulers, the atmospheric transports. It is not a primary investigation target unless the player is working in the industrial supply or corporate liability space.
The Series 9 certification discrepancy is the investigative thread. The fixture batch and its divergence from production specification are documented in Bergkraft's internal engineering archive. The Commission's certification file contains the test parameters but not the fixture tolerances — the discrepancy can only be demonstrated by comparing the internal engineering documentation against the certification submission. A player who obtains both has found evidence of a product that was certified to a standard its production run does not meet.
The affected fleet represents a significant portion of the west reach's mining operation transport capacity. Mining companies whose operational plans assume twelve-year drive life have scheduled maintenance and replacement timelines around that claim.
The consequence of exposure is triangular: Bergkraft faces certification resubmission requirements and potential recall; the mining operations face equipment replacement on a timeline that their capital planning did not account for; and the Commission faces questions about whether its certification audit process caught or should have caught the fixture discrepancy before the product line shipped. The Commission's interest in the last question gives it a reason to manage the outcome carefully rather than straightforwardly — a factor that shapes how a player might use the evidence. The most direct leverage is not the Commission but the mining companies themselves: a fleet operator who can document early performance degradation against the certified twelve-year claim has a direct claim against BKA that does not require a regulatory finding first.
---
**Cross-References:**
- [Bergtor](../star-systems/GJ-505A/index.md) — Headquarters; manufacturing facility; primary market
- [Bavarian Craft](bavarian-craft.md) — Bergtor peer enterprise; shared industrial district
- [Rheintal Systems](rheintal-systems.md) — West reach technical peer; industrial market overlap
- [Durban Engineering](durban-engineering.md) — Industrial peer; competing drive supply for specific applications
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/brindlewood-honey.md
+84 -6
View File
@@ -1,24 +1,102 @@
---
title: "Brindlewood Honey"
description: "Brindlewood Honey — regional specialty producer based in Ashfield, north reach"
description: "Ashfield specialty honey producer — a scarcity-class rare terroir product whose provenance claims are carefully worded enough to survive legal challenge while misleading the buyers who pay for them"
slug: brindlewood-honey
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Ashfield (GJ 178)
tags: [terroir, north_reach, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [calloway-distillery, highland-cooperative, comptoir-lendel]
---
# Brindlewood Honey
**Type:** Corporation — Regional Specialty Producer
**Also Known As:** Brindlewood
**Status:** Canonical
**Scope:** Regional — north reach operations
**Headquarters:** Ashfield (GJ 178)
**Scope:** North reach primary; inward corridor luxury food market secondary
**Headquarters:** Ashfield (GJ 178) — north reach, 5 hops from Gateway
**Classification:** Sub-Syndic artisan producer; scarcity-class rare terroir product
Brindlewood Honey is a regional specialty producer operating out of Ashfield (GJ 178). Details to be expanded.
---
## Overview
The honey that Brindlewood produces is genuinely exceptional. The company does not need to fabricate its product's quality; the quality is real, the terroir is specific to Ashfield's particular combination of native flowering species and cold-summer climate, and the bees have been working the same high-meadow geography for over two centuries. Honey from Brindlewood's hives tastes unlike anything produced anywhere else in the corridor because the conditions that produce it cannot be replicated. This is not marketing language. Agronomists have tried; the attempts produce honey that is technically similar and categorically distinct.
What Brindlewood has added to this genuine distinctiveness is a provenance story built around wildness — the idea that what distinguishes the product is not merely terroir but source: bees living free in Ashfield's native meadows, foraging without managed guidance on a landscape that settlement has not significantly modified. The story is compelling. It is the version buyers in inward premium markets want to hear when they purchase a jar that costs more than a day's transit meal.
It is not quite accurate.
---
## Origin
Brindlewood's founding family arrived at Ashfield 240 years ago in an agricultural settler cohort that brought multiple productive enterprises. Beekeeping was one of many. For the first century, the honey operation was a local commodity — sold at Ashfield's markets, occasionally traded at Braemar, not distinguished from other quality local food production.
The transformation into a premium brand began ninety years ago under a family member named Miriam Oakes-Callander, who took a consignment of honey to a Tractus-corridor luxury food exhibition and discovered that inward buyers responded to Ashfield honey as a novelty of considerable appeal. She returned with orders and a marketing problem: how to produce enough to meet demand without losing the qualities that created the demand. Her solution was careful management presented as natural process. The beekeeping operation became scientific. The marketing became poetic.
---
## Operations
**Production:** Brindlewood manages forty-seven active hive colonies across three sites in Ashfield's high meadow geography. The colonies are carefully maintained — queen replacement, disease management, nutritional supplementation during low-forage seasons — as any professionally managed apiary would be. Annual production is approximately 2,400 kilograms. This is intentionally constrained; production capacity could be expanded but Brindlewood has chosen not to, because scarcity supports price.
**Processing:** Small facility at the Ashfield homestead. Extraction, filtering to a specific standard, and bottling conducted on-site with a staff of seven. The process is genuinely artisanal at this scale — the small operation is not a marketing conceit.
**Distribution:** Premium food retailers at inward systems, selected by the company based on whether their positioning matches Brindlewood's brand requirements. Provenance documentation accompanies each shipment: origin certification, lot number, hive site identifier. The documentation is real; the documentation does not describe management practices.
**Pricing:** Top tier of the corridor luxury food market. A single 250g jar at a Lendel specialty retailer is priced above what an Ashfield agricultural worker earns in a day. This price is supported by scarcity, terroir authenticity, and the provenance story.
---
## Political Relationships
**Calloway Distillery:** Calloway single malt and Brindlewood honey occupy the same inward premium market tier and travel the same north reach corridor export routes. Both are terroir-dependent products whose distinctiveness cannot be replicated off-system; both command prices that reflect this. The two operations are aware of each other as corridor partners rather than competitors — appearances together in inward premium retail contexts reinforce both brands. The parallel in their provenance-management approaches, if either were exposed, would invite comparison.
**Highland Cooperative:** Both operations are at the outer north reach and both face the strategic question of how to grow revenue from scarcity products without the growth undermining the scarcity. Highland Cooperative members observe Brindlewood's pricing model closely; several have consulted informally on how to position their own specialty products against the Brindlewood benchmark. The relationship is collegial rather than commercial.
**Comptoir Lendel:** Comptoir Lendel is Brindlewood's primary Groombridge retail relationship and the source of the provenance certificates that accompany honey sold in the Lendel premium market. The Comptoir's certification process — which charges for documentation without verifying the underlying claims — is the same process that certifies Brindlewood's "wild-harvested" tier. If the Comptoir's authentication model is challenged, the certificates attached to Brindlewood's premium products become part of the question.
---
## What They Don't Talk About
Brindlewood's "wild-harvested" premium tier — the designation that distinguishes its highest-priced jars from the standard production — was genuine in the company's early decades. For forty-three years, it has not been.
The high meadow colonies that produce the premium tier are managed colonies operating in natural habitat. Brindlewood's labeling uses language that has been carefully maintained by its legal advisors to describe this accurately: "harvested from colonies foraging in Ashfield's native meadows" rather than "wild-harvested" — the latter phrase would require certification of truly wild colony source that Brindlewood cannot provide. The distinction between a managed colony in natural surroundings and a genuinely wild colony is one that the legal team has defined in Brindlewood's favor.
The inward retailers who stock the premium tier use the phrase "wild-harvested" in their own shelf copy and promotional materials. Brindlewood does not use the phrase itself. It does not correct the retailers. When the company provides marketing support materials to inward accounts, the language is the careful version; the promotional context the retailers create around that language is the buyers' context, not Brindlewood's.
The distinction exists on paper. No buyer paying the premium price understands themselves to be purchasing managed-colony honey.
---
## Gameplay Relevance
Brindlewood Honey is luxury goods texture in the premium food market — its jars appear in high-end residences, private dining rooms, and specialty retail contexts across the inner and mid corridor. The product is not significant in terms of volume; it is significant in terms of what its price implies.
The labeling gap is the investigative thread. A player who obtains Brindlewood's original marketing materials, compares them to current retailer copy, and traces the company's legal correspondence around the "wild-harvested" language will find a record of a deliberate decision to maintain a false impression through careful omission. The retailers are complicit in effect but not in design — they received materials that didn't use the phrase and adopted it independently. This complicates the liability picture.
The scarcity management — the decision to constrain production to maintain price — is a secondary thread with connections to Ashfield's agricultural governance and the economics of north reach specialty food production.
The most consequential exposure scenario is not a consumer complaint but a retailer complaint. The inward retailers who have used "wild-harvested" in their own promotional copy did so in good faith based on materials Brindlewood provided — materials that didn't use the phrase but created the context in which retailers adopted it. A retailer facing a consumer challenge over "wild-harvested" labeling would discover, when seeking indemnification from Brindlewood, that Brindlewood's position is that its own materials never made the claim. The retailers' legal exposure and Brindlewood's insulation from it would become the same event. Several of the inward retailers are the kind of premium food purveyors for whom provenance authenticity is foundational to their brand positioning — the same positioning that makes Brindlewood's product worth stocking at the price it commands. The unraveling would be mutual.
---
**Cross-References:**
- [Ashfield](../star-systems/GJ-178/index.md) — Headquarters and production site
- [Calloway Distillery](calloway-distillery.md) — North reach terroir peer; comparable provenance-based brand model
- [Highland Cooperative](highland-cooperative.md) — Crown's Hollow specialty producer; north reach premium food context
- [Comptoir Lendel](comptoir-lendel.md) — Inward premium retailer; carries Brindlewood in Groombridge premium market
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/byeolbit-entertainment.md
+80 -7
View File
@@ -1,24 +1,97 @@
---
title: "Byeolbit Entertainment"
description: "Byeolbit Entertainment — cultural content producer based in Seongho, east reach"
description: "Korean-heritage entertainment studio at Seongho (GJ 660A) — drama serials, music, and variety content produced in sealed-habitat studios powered by geothermal energy, distributed through the junction's three apertures to the east reach and beyond"
slug: byeolbit-entertainment
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Seongho (GJ 660A)
tags: [cultural, east_reach, tractus, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [haesungdan-records]
---
# Byeolbit Entertainment
**Type:** Corporation — Cultural Content Producer
**Type:** Corporation — Drama, Music, and Entertainment Production
**Also Known As:** Byeolbit, "the studio"
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Seongho (GJ 660A)
**Scope:** East reach corridor primary; core and inner-corridor distribution secondary
**Headquarters:** Seongho (GJ 660A) — 3-aperture junction, east_reach corridor
**Classification:** Sub-Syndic cultural enterprise; independent
Byeolbit Entertainment is a cultural content producer operating out of Seongho (GJ 660A). Details to be expanded.
---
## Overview
Seongho has no surface. The world beneath its sealed habitats is a fractured black-rock plain of active heat vents, geologically restless, unbreathable without equipment, spectacular from the transit station viewports in the specific way that hostile environments are spectacular when safely observed. Inside the seals, everything is controlled: temperature, light, atmosphere, sound. What this means for a studio that has been producing content in Seongho's sealed habitats for forty years is that the entire production environment is, by necessity, designed. There is no natural light to work with. There is no exterior. Every frame is built.
Byeolbit Entertainment's aesthetic comes from this condition. The studio's drama serials are noted for their production design: elaborate, architecturally precise environments rendered in controlled light that produces a specific visual quality — warm, slightly amber, the indoor quality of spaces that are carefully maintained against an exterior that would be immediately fatal. This is not stylistic choice in the way that aesthetic decisions at surface-based studios are choices. It is the studio's physical reality, absorbed into the work so thoroughly that audiences outside Seongho describe the Byeolbit aesthetic without knowing they are describing a sealed-habitat world's inside.
The three-aperture junction topology is Byeolbit's distribution advantage: content produced at Seongho can simultaneously reach Hwaseong corridor, Binh Trang outward, and the Tình Yên dead-end branch from the same release point. This reach across three directions has given Byeolbit's content an east reach corridor penetration that studios at less advantageous positions cannot match from equivalent production budgets.
---
## Origin
The studio was founded forty years ago by the Jang family — second-generation Seongho residents whose grandparents had been part of the founding Korean-heritage community that chose the site for its geothermal potential. The founding family's interest was not in geothermal energy; it was in the surplus of that energy, which made power for studio operations essentially free. Cheap reliable energy and a sealed environment optimized for controlled-atmosphere work were, in the founding generation's assessment, exactly the infrastructure a serious production studio needed and almost never had.
The Jang family's initial production was music: original recordings and sessions for artists from across the Korean-heritage east reach community who came to Seongho specifically for the studio's acoustic environment. The studio space had been engineered for geothermal monitoring — temperature-stable, vibration-isolated, well-shielded — and these qualities produced a recording environment of unusual quality. The music production reputation preceded the drama production by a decade. When Byeolbit began producing serial drama, it already had the technical credibility that drama production requires and the east reach cultural community's attention.
The studio's flagship drama production — *Unda*, a Korean-language title meaning flow or current, with connotations of heat — began production eighteen years ago and is currently in its twelfth series. It is the most-watched drama serial in the east reach corridor.
---
## Operations
**Drama production:** *Unda* is the studio's primary production and its primary revenue source. The serial is a generational family saga set on a fictional geothermal junction world called Dalbicht — a world with three apertures, sealed habitats, and a founding community organized around thermal energy management. Each series follows a different generation of the founding families across approximately forty episodes. The production design — built entirely in Byeolbit's sealed-habitat studios — has won the east reach Meridian Excellence Award for environmental design three years consecutively.
**Music:** The recording operation that preceded *Unda* continues as a secondary production line. Byeolbit has a standing session relationship with Haesungdan Records at Miryang (GJ 754), whose vocal arts roster includes artists who record instrumental backing at Seongho; the studio acoustic environment is considered the east reach's standard for complex choral work. The session relationship has extended into co-production credits on several Haesungdan releases.
**Distribution:** Three-aperture simultaneous release via Meridian syndication. The junction position means Byeolbit's release cycle can reach a larger fraction of the east reach in the first twenty-four hours after publication than any non-junction studio in the corridor. Inward distribution to the core and inner reaches is handled through a syndication agreement with a Sirius-based distributor that packages east reach content for the cosmopolitan market.
**Studio infrastructure:** Six production stages across three sealed-habitat facility locations on Seongho. All stages are powered by geothermal tap under a fixed-rate agreement with the Thermal Authority that has been in place since the studio's founding and constitutes Byeolbit's single most valuable infrastructure relationship.
---
## Political Relationships
**The Thermal Authority:** The fixed-rate geothermal agreement is the relationship that matters most to Byeolbit's operational continuity. Without reliable, cheap energy at fixed cost, the studio's production economics change significantly. The Thermal Authority knows this. The relationship has been civil for forty years. It has been under specific pressure for the past two years, related to the content of *Unda*'s eleventh and twelfth series.
**Haesungdan Records:** The session and co-production relationship with Haesungdan Records is the studio's most significant external creative partnership. The two Korean-heritage east reach institutions have developed a complementary market position — Haesungdan's vocal arts aesthetic and Byeolbit's drama production have overlapped in ways that reinforce both, particularly in the inner-corridor markets where Korean-heritage content is experiencing growing commercial interest.
**The Junction Transit Cooperative:** Byeolbit's content distribution depends on the junction's gate infrastructure performing reliably. The studio maintains a formal liaison relationship with the Cooperative, which manages gate operations, and has contributed to the Cooperative's public programming — sponsoring transit-hostel content terminals that carry Byeolbit productions as a commercial arrangement that doubles as corridor-wide distribution.
---
## What They Don't Talk About
*Unda*'s fictional world of Dalbicht is not fictional in its structural details. The drama serial's source material — compiled over three years by a historian embedded with the production before the first series — draws directly from documented records of Seongho's founding period, including the Thermal Authority's internal records from the first two generations of bore installation. The historian's research was made available to the Jang family through a personal connection to one of the founding families' extended network.
Among the material incorporated into the serial's narrative are events surrounding a disputed inheritance of bore installation rights in Seongho's first generation — a dispute that the current Thermal Authority board's founding families resolved in a manner that the historical record describes in terms the current board would not characterize the same way. The parallels between *Unda*'s fictional Dalbicht governance narrative and the documented history of the Thermal Authority's founding became apparent to the board during the eleventh series. The board's legal team contacted Byeolbit twice. The second contact included a reference to the studio's fixed-rate geothermal agreement and the Thermal Authority's discretion over its terms.
Byeolbit agreed to not explicitly promote the documentary research connection in public communications. The serial's content has not changed. The historian's research archive — which contains the primary documents that the board would most prefer not to have circulating — has been moved to a location outside Seongho that the Thermal Authority has not been told about.
---
## Gameplay Relevance
Byeolbit is ambient cultural infrastructure for the east reach — *Unda* appears on data terminals, in transit hostels, in the background of any east reach setting where Meridian content streams. The production design is recognizable: warm amber indoor light, architectural interiority, the specific quality of spaces that are built because they have to be rather than because they were designed to impress.
The *Unda* research thread connects directly to Seongho's silence topic: the Thermal Authority's bore depletion data that the board has not shared with the elected council. A player investigating the bore depletion narrative will encounter *Unda* as a documentary artifact — the historian's research captured events adjacent to the depletion data's suppression, and the historian's archive, wherever it is currently held, may contain primary documents that the board has been unable to recover. Finding the archive means finding the historian, which means tracing a person who moved deliberately and whose reasons for moving are the investigative frame.
---
**Cross-References:**
- [Seongho](../star-systems/GJ-660A/index.md) — Headquarters system; geothermal junction; sealed habitats
- [Haesungdan Records](haesungdan-records.md) — East reach Korean-heritage label; session and co-production partner
- [Thermal Authority] — Seongho's energy infrastructure body; fixed-rate agreement; institutional pressure source
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/calloway-workshop.md
+78 -7
View File
@@ -1,24 +1,95 @@
---
title: "Calloway Workshop"
description: "Calloway Workshop — design and furniture manufacturer based in Calloway Reach, north reach"
description: "North_reach precision furniture workshop at Calloway Reach (GJ 3325) — hand-craft production using Dunbar timber, restrained design aesthetic, and a quiet presence in the same premium markets that carry Calloway whisky"
slug: calloway-workshop
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Calloway Reach (GJ 3325)
tags: [design_heritage, north_reach, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [calloway-distillery]
---
# Calloway Workshop
**Type:** Corporation — Design And Furniture Manufacturer
**Type:** Corporation — Furniture and Object Design
**Also Known As:** the Workshop
**Status:** Canonical
**Scope:** Regional — north reach operations
**Headquarters:** Calloway Reach (GJ 3325)
**Scope:** North_reach corridor primary; inward premium market secondary
**Headquarters:** Calloway Reach (GJ 3325) — 2-aperture loop_member, 6 hops from Gateway
**Classification:** Sub-Syndic craft enterprise; artisan-founded independent
Calloway Workshop is a design and furniture manufacturer operating out of Calloway Reach (GJ 3325). Details to be expanded.
---
## Overview
Calloway Workshop makes furniture. Precisely: it makes the furniture it chooses to make, in the quantities it can maintain quality at, for buyers who can wait for it. The Workshop is not large and has no interest in becoming large. It is in this respect similar to the community it operates in, whose most successful institutions have built their reputations on patience.
The aesthetic is Calloway's: restrained, functional, built to outlast its original setting. Nothing in a Calloway Workshop piece announces itself. The proportions are correct, the joinery is exact, the finish responds to the wood's specific character rather than overriding it. First-time buyers sometimes return after a year to ask when their piece is going to show its quality, because they expected something more apparent. The answer — that it already has — is a Workshop selling point that not every buyer understands before purchase and most understand after.
The Workshop has been producing on the same site outside Grantown for eighty years. The founding family still runs it. The quality has not declined in that time. The waiting list has not shortened.
---
## Origin
The Workshop was founded by Moira Calloway-Dunne, who was neither a distiller nor a farmer but had grown up in the orbit of the distillery culture and absorbed its operating principle: quality produced slowly and consistently builds something no fast production cycle can replicate. She had trained in furniture and object design at an inward-corridor institution, returned to Calloway Reach after completing her training, and opened a workshop in a converted farm building outside Grantown using Dunbar timber sourced through the same supply contacts the distilleries used for cooperage wood.
The choice to use Dunbar timber was partly practical and partly considered. The Dunbar oak — cold-climate variant adapted to GJ 3991's conditions — had a grain density and figure specific to its growing environment, producing furniture character that could not be sourced from any off-system equivalent. Moira Calloway-Dunne was making the same argument the distillers had been making about their whisky for three centuries. The argument worked the same way.
The Workshop grew to its current size over two generations. It has not grown beyond that.
---
## Operations
**Production:** Fourteen trained craftspeople working a project cycle that runs two years from commission to delivery for bespoke pieces and twelve to eighteen months for the standard range. The Workshop produces approximately sixty to eighty pieces per year. This number has not changed significantly in thirty years. Management has declined proposals to expand the workforce on the grounds that quality depends on team coherence — scaling would introduce inconsistencies the Workshop has no interest in managing.
**Materials:** Dunbar oak is the primary structural timber, sourced under a standing supply arrangement with the managed forestry operation at GJ 3991 that also supplies the distilleries' cooperage stock. The arrangement has been in place for forty years. Neither party has looked at the written contract recently; the relationship continues on informal terms between two institutions that have no reason to change what is working.
**Market and distribution:** The Workshop sells directly from Calloway Reach. No intermediaries, no retail presence, no inward-corridor offices. Buyers come to Strathmore, commission their piece, and wait. Inward clients have arranged this for forty years. The inconvenience of the process is treated, in certain corridor commercial circles, as a quality signal in itself. Something worth waiting for is worth the trip to commission.
---
## Political Relationships
**Calloway Distillery:** The Workshop and the Distillers' Council do not have a formal relationship, but they share a corridor reputation and, through the cooperage timber supply, a material supply chain. Distillery fit-out — tasting rooms, visitor accommodation, storage buildings — has historically been done in the Workshop's aesthetic by default. Nobody organized this. It developed the way shared community standards tend to develop in a small system with a consistent culture.
**The Grain Alliance:** The farming families who supply the distilleries are also the Workshop's nearest neighbors at the agricultural margin of the Grantown district. The Workshop buys locally produced food; the farming families buy Workshop pieces for significant occasions. The relationship is civic rather than commercial and is conducted at the level of personal acquaintance rather than institutional arrangement.
**Dunbar (GJ 3991):** The Dunbar forestry operation is the Workshop's critical external relationship. The supply arrangement for furniture-grade timber is informal, durable, and has been renewed by each generation on the same terms as the last. The two institutions understand that the arrangement is mutually valuable and neither has tested what would happen if one of them tried to change it.
---
## What They Don't Talk About
The Dunbar timber supply arrangement covers furniture-grade stock. What the Workshop is currently also receiving — on a separate invoice line described as "tooling timber and trim stock" — is Dunbar oak machined to specifications the Workshop's own furniture production does not require. The dimensional profiles are consistent with cooperage components rather than furniture structural members. The tolerances are tighter than anything a furniture application needs.
The Workshop's current head, Euan Calloway-Dunne, accepted this commission two years ago from a client who identified themselves as a distillery equipment supplier from Braemar. The specifications were precise and professional. The client has placed two subsequent orders and has not communicated any concerns about the work. Euan has not asked why a Braemar equipment supplier needs cooperage-grade Dunbar oak when Braemar's own timber supply is adequate for local barrel production.
The Distillers' Council, which has been receiving quiet acquisition approaches from inward investors, does not know that cooperage tooling with Calloway Reach timber provenance is being produced and shipped. Euan Calloway-Dunne does not know his client is connected to those approaches. He has concluded that the contract is legal, the components are timber, and the client's business is the client's business.
---
## Gameplay Relevance
The Workshop is ambient craft texture in the north_reach corridor — a high-quality, low-profile institution that players encounter through material culture. A furnished Alcazar property might carry Calloway Workshop pieces in the dining room; a Calloway single malt tasting room almost certainly will. The Workshop's presence in a space is a signal of deliberate, unhurried quality investment.
The cooperage component thread connects to the concealed acquisition narrative in the Calloway Distillery entry. A player tracing the inward investor approaches to the distilleries could follow the tooling supply chain and find bespoke cooperage components being produced at the Workshop and shipped inward — raising the question of what production those components are intended to scale. Euan Calloway-Dunne is a secondary source: no reason to deceive, no complete picture of what he is part of. His records of the component orders — specifications, delivery addresses, invoice counterparty — are investigative material if a player can access them.
---
**Cross-References:**
- [Calloway Reach](../star-systems/GJ-3325/index.md) — Headquarters system; founding culture
- [Calloway Distillery](calloway-distillery.md) — Sister institution; shared system, shared aesthetic; cooperage component thread
- [Dunbar](../star-systems/GJ-3991/index.md) — Timber source; shared forestry supply with the distilleries
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/calluna-wellness.md
+77 -6
View File
@@ -1,24 +1,95 @@
---
title: "Calluna Wellness"
description: "Calluna Wellness — premium service provider based in Cairn, north reach"
description: "North reach extended recovery service at Cairn (GJ 845) — long-stay programs for lattice adjustment and physiological restoration, operating between standard clinical care and full re-embodiment"
slug: calluna-wellness
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Cairn (GJ 845)
tags: [service_premium, north_reach, tractus]
decision_refs: [D-189]
cross_refs: []
cross_refs: [somatic-futures, prometheus-labs]
---
# Calluna Wellness
**Type:** Corporation — Premium Service Provider
**Type:** Corporation — Extended Recovery and Lattice Adjustment Service
**Status:** Canonical
**Scope:** Regional — north reach operations
**Scope:** North reach corridor primary; cross-corridor referrals from Somatic Futures and clinical partners
**Headquarters:** Cairn (GJ 845)
**Currency:** Tractus
**Classification:** Sub-Syndic health-adjacent service enterprise; registered under wellness licensing
Calluna Wellness is a premium service provider operating out of Cairn (GJ 845). Details to be expanded.
---
## Overview
There is a gap in the Reach's care infrastructure between standard medical clinics and full re-embodiment services. Standard clinics manage acute conditions. Re-embodiment facilities handle complete substrate transfers. What neither handles well is the long middle: the person whose neural lattice is degrading at a rate that is not yet critical, the Perpetual-class citizen managing post-embodiment adjustment over a period of months, the professional who has pushed their lattice through an intensive period and needs extended physiological recalibration. These people do not need a hospital. They need somewhere to recover, over time, with consistent clinical support.
Calluna Wellness exists for this gap. The facility at Cairn offers extended stay programs — minimum four weeks, typical stay eight to sixteen weeks — built around lattice adjustment monitoring, physiological restoration, and the specific kind of sustained care that requires continuity of staff and environment. It is not a hospital and does not operate under hospital licensing. It is classified as a wellness service and operates under that regulatory framework, which permits a considerable range of clinical-adjacent services without requiring the institutional overhead of medical facility registration.
The distinction matters because it determines cost, access, and oversight. Calluna is more affordable than a clinical facility for extended stays. It is less subject to Lattice Commission clinical monitoring protocols. It accepts clients who cannot access full clinical care on their timelines and budgets. It is also, for this reason, not subject to the reporting requirements that would apply to a licensed medical facility.
---
## Origin
Calluna Wellness was founded fifty years ago by a nurse practitioner named Ailsa Drummond who had spent twenty years working in the north reach's network of small clinical facilities and had developed a clear picture of the patient population that the clinical system was failing. Not failing through malice or incompetence — failing because the structure of clinical care, organized around acute treatment and discharge, had no mechanism for patients who needed sustained recovery support over timescales measured in months.
Drummond's original model was straightforward: a long-stay facility that provided monitoring, support, and a stable environment for the recovery process that acute care facilities could not offer. She opened the first Calluna property at Cairn with sixteen beds and a staff of four. The referrals came from the clinical network she had spent twenty years building relationships within. Within two years the facility was at capacity and had a waiting list.
Ailsa Drummond retired twenty years ago. The facility has been expanded twice and is now run by a partnership of three directors, one of whom trained under Drummond. The founding philosophy — structured care for the recovery period that clinical systems cannot support — has not changed. The regulatory environment has changed considerably around it.
---
## Operations
**Programs:** Three primary program types. The lattice adjustment program is for clients managing post-modification recalibration, lattice degradation, or embodiment transition effects. The physiological restoration program is for clients who need extended support following intensive physical or cognitive periods without a specific clinical diagnosis. The maintenance program is for long-term clients — primarily Perpetual-class individuals managing the cumulative effects of extended lattice use — who return annually or semi-annually for sustained recalibration.
**Staffing:** Twelve clinical staff, including three with Lattice Commission wellness certification, two physiotherapists, and a rotating roster of visiting practitioners with specific specializations who provide services under contract. The clinical staff are not physicians under Reach medical licensing. They are wellness practitioners operating within the regulatory scope of the facility's classification. The distinction is significant in legal terms and has been consistently managed in the facility's documentation.
**Referrals:** The majority of Calluna's clients arrive through referrals from clinical facilities that cannot serve their recovery timeline. Somatic Futures has a standing referral relationship with Calluna for clients whose post-embodiment adjustment period exceeds what the clinical facility can accommodate. A smaller referral stream comes from Perpetual-class lifestyle management services that identify clients in need of extended recalibration before the condition becomes clinically acute.
**Records:** The facility maintains detailed longitudinal records for all clients. These records are held under wellness privacy protocols, which are less stringent than clinical privacy standards and do not carry the same restrictions on secondary use.
---
## Political Relationships
**Somatic Futures:** The standing referral relationship is Calluna's single largest client-acquisition channel. Somatic Futures refers post-embodiment clients whose adjustment window exceeds their clinical facility's discharge timeline. The referral goes one direction; Somatic Futures does not take Calluna referrals back. Calluna in turn does not directly market against Somatic Futures. The relationship is long-standing, commercially important to both parties, and is the mechanism by which "wellness" clients reach Calluna without clinical case-file transfer.
**Lattice Commission (wellness division):** Calluna operates under wellness licensing, which is the lighter-touch regulatory tier the Commission maintains for services that are clinical-adjacent but not clinical. The Commission has reviewed Calluna's classification twice in fifty years and has upheld it both times. The reviews are pro-forma; the Commission's wellness division is understaffed and does not have the resources to audit the substantive clinical work done under wellness licensing across the Reach.
**Prometheus Labs:** The data-licensing relationship is contractual, long-running, and financially material to Calluna. The commercial shape of it is discussed below (What They Don't Talk About); the political shape of it is that Calluna's current partners have not renegotiated the consent framework in thirty years because the relationship's economics do not reward renegotiation.
---
## What They Don't Talk About
Calluna's client records are the facility's secondary revenue stream. The facility has maintained a data licensing arrangement with a Prometheus Labs subsidiary for thirty years — predating the current management — under which anonymized aggregate data from the long-stay client population is provided for research into lattice performance over extended recovery periods. The data is valuable because Calluna's client population is unusual: people managing lattice conditions over months in a consistent monitored environment, providing longitudinal data that clinical settings cannot generate because their discharge timelines are too short.
The clients consent to "wellness research use" of aggregated data in the program agreement. The consent language was written to cover exactly this kind of licensing. It was not written to make the licensing visible to clients who did not read carefully, and the partnership that now runs Calluna considers the consent framework sufficient without considering whether it is informative. Prometheus Labs has been extending and expanding the research agreement at each renewal cycle. The current payment terms are substantially higher than the original arrangement. The partnership has not asked what Prometheus Labs has found in thirty years of data that makes it worth more than it used to be.
---
## Gameplay Relevance
Calluna is relevant for investigations touching lattice health, long-term care access, and the grey zone between clinical and wellness services. A player investigating a subject's health history will find that an extended Calluna stay represents a period of clinical-adjacent monitoring that is not accessible through standard Lattice Commission records — wellness facilities are not subject to the same reporting requirements as licensed medical providers. Access to the records requires either Calluna's cooperation or a legal instrument calibrated to wellness facility standards rather than clinical standards, which most investigators do not automatically seek.
The Prometheus Labs data relationship is the deeper thread. Thirty years of aggregate Calluna data in a Prometheus Labs subsidiary represents significant accumulated research into lattice degradation, adjustment patterns, and long-term performance in the Perpetual-class population. An investigator who establishes what the subsidiary has been doing with that data — and why the payments have been increasing — is investigating Prometheus Labs' research priorities through a side entrance they have not secured as carefully as their primary operations.
---
**Cross-References:**
- [Somatic Futures](somatic-futures.md) — referral partner for post-embodiment adjustment clients
- [Prometheus Labs](prometheus-labs.md) — purchaser of long-term lattice adjustment research data
- [Cairn (GJ 845)](../star-systems/GJ-845/index.md) — headquarters system; north reach wellness corridor
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/cape-modern.md
+81 -7
View File
@@ -1,24 +1,98 @@
---
title: "Cape Modern"
description: "Cape Modern — design and furniture manufacturer based in Kaapse Baai, south reach"
description: "Kaapse Baai contemporary furniture and interior design manufacturer — south reach modernist aesthetic, institutional and residential supply, sustainability certification maintained by a conflicted auditor"
slug: cape-modern
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Kaapse Baai (GJ 213)
tags: [design_heritage, south_reach, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [sertanejo-design, quebrada-cultural, veldfontein-botanical]
---
# Cape Modern
**Type:** Corporation — Design And Furniture Manufacturer
**Type:** Corporation — Contemporary Furniture and Interior Design Manufacturer
**Also Known As:** Cape Modern Design
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Kaapse Baai (GJ 213)
**Scope:** South reach primary; inward corridor design market secondary
**Headquarters:** Kaapse Baai (GJ 213) — south reach, 4 hops from Gateway
**Classification:** Sub-Syndic design enterprise; institutional and residential supply
Cape Modern is a design and furniture manufacturer operating out of Kaapse Baai (GJ 213). Details to be expanded.
---
## Overview
Kaapse Baai sits at the edge of the south reach's more temperate systems — a coastal settlement with a design culture that emerged from the intersection of Afrikaans-heritage founding communities and the successive waves of diverse arrivals that characterize a functional transit hub. The result, after three centuries of aesthetic negotiation, is a design sensibility that combines spatial openness, natural material emphasis, and a preference for objects that age visibly rather than resisting aging. Cape Modern manufactures furniture and interior products in this tradition and has spent forty years building a distribution network that introduces the aesthetic to inward markets.
The company's positioning in inward markets is not as a local curiosity. It is as a design alternative: if the Lendel financial district aesthetic is weight and permanence, and the Bergtor aesthetic is guild heritage, Cape Modern's argument is that furniture can be honest about what it is — natural materials working with use rather than against it, construction that makes repair possible rather than precluding it. This argument has found an audience in commercial interiors and residential contexts that find institutional permanence oppressive.
---
## Origin
Cape Modern was founded thirty-eight years ago by a furniture designer and a materials scientist who had been working independently in Kaapse Baai's small design community and decided their complementary skills justified a combined operation. The founding partnership brought together design articulation and materials knowledge in a combination unusual for a small manufacturer; most design enterprises are either design-led with poor materials judgment or materials-competent with weak design language. Cape Modern's founding configuration avoided both failure modes.
The early years were local: residential furniture for Kaapse Baai's growing population, occasional institutional commissions for the transit hub's administrative buildings. The decision to pursue inward distribution came fifteen years in, when a Tractus-corridor design exhibition in the core systems produced an unexpected response to the company's entry pieces — buyers who had not expected to find a south reach design aesthetic they wanted in their homes.
---
## Operations
**Product lines:** Residential seating and tables — the core of the business, designed around natural wood and textile combinations that develop character with age. Institutional systems — office furniture and common area fittings for commercial clients who want the Cape Modern aesthetic at scale, which requires somewhat different materials specifications than the residential line. Custom commissions — a prestigious fraction of output for clients with specific spatial requirements. A textile line, relatively recent, that extends the brand's materials language into wall treatments and soft furnishings.
**Materials:** Primary emphasis on woods native to Kaapse Baai's ecosystem, managed under the company's sustainability certification. Secondary materials — metal hardware, textile components — sourced from south reach corridor suppliers where possible. The sustainability certification covers the full supply chain and is reviewed annually by an independent auditor.
**Manufacturing:** Two facilities at Kaapse Baai. The primary facility handles production; the secondary is a showroom and custom workshop used for commission work and client consultation. Total workforce of sixty-one, with a design team of eight.
**Distribution:** South reach residential and institutional direct sales, plus a network of inward design retailers. The inward distribution is managed through selective licensing agreements; Cape Modern does not supply retailers whose positioning undermines the brand's premium identity.
---
## Political Relationships
**Sertanejo Design:** Cape Modern's closest south reach peer in the design sector, operating from an adjacent system with a complementary aesthetic. The two studios share institutional clients across the south reach corridor and occasionally refer commissions that better suit the other's style. The relationship is warm but commercially aware — both compete for the same procurement budgets at regional government and institutional clients.
**Quebrada Cultural:** Quebrada Cultural and Cape Modern share a significant overlap in institutional clients — arts organizations, cultural foundations, and government cultural programs that commission both design work and cultural programming. Cape Modern's visual identity work for the same institutions that Quebrada programs creates an ongoing commercial adjacency that has produced joint pitches and occasional friction over creative direction.
**Veldfontein Botanical:** Cape Modern sources botanical extract compounds from Veldfontein for a textile treatment line that is marketed as a natural material enhancement. The supply relationship is small in commercial terms but significant for the marketing claim; if Veldfontein's supply chain or certification practices were found inadequate, it would affect Cape Modern's natural materials claim in the same product line that carries the sustainability certification.
---
## What They Don't Talk About
Cape Modern's sustainability certification — prominently featured in its marketing materials and cited as a distinguishing advantage over less conscientious competitors — is issued annually by an independent auditing firm called Meridian Environmental Consulting. The certification covers materials sourcing, manufacturing process, and supply chain environmental standards.
One of Cape Modern's three founding directors holds a 22% equity stake in Meridian Environmental Consulting through a holding company. This position was acquired seven years ago as part of a private investment round Meridian conducted when expanding its practice. It is disclosed in Cape Modern's corporate governance filings, which are publicly accessible. It is not disclosed in Cape Modern's marketing materials, its sustainability certification documentation, or the information packets provided to institutional clients who cite the certification in their own environmental impact reporting.
Meridian's audits of Cape Modern have consistently recommended certification with minor remediation notes, none of which have resulted in failed certification. Meridian's assessments of Cape Modern's competitors have in several cases produced more critical findings. Whether the audits are accurate is unknowable from outside; whether the structural relationship should be disclosed to buyers relying on the certification is a simpler question.
---
## Gameplay Relevance
Cape Modern is design-sector presence in the south reach and an ambient marker of aesthetic in the spaces it furnishes — its pieces are identifiable in well-appointed interiors, and its brand is recognizable to characters with commercial or design-world context.
The auditor relationship is the investigative thread. The equity position exists in governance filings; the absence of disclosure in client-facing materials is demonstrable by comparison. A player assembling an environmental fraud or procurement irregularity case in the south reach will find Cape Modern's certification a useful example of the gap between what sustainability documentation implies and what it demonstrates.
Cape Modern's design community connections also make it a social contact point — the company's design team is embedded in Kaapse Baai's creative and professional circles, and its principals are connected to institutional clients across the south reach.
The auditor conflict is most consequential for institutional clients who have cited Cape Modern's sustainability certification in their own environmental procurement documentation — government agencies, interstellar shipping operators with environmental compliance requirements, and commercial tenants whose lease terms specify sustainably certified furnishings. If the director's equity position in the auditing firm becomes public, those clients' certification reliance becomes compromised retroactively. The compliance question they then face is whether their own documentation is accurate, which is a question with legal and contractual implications. Cape Modern's exposure is the same: the certification it has charged a premium to provide carries a conflict disclosure that, if required and absent, undermines every commercial relationship built on it. The director's equity stake is the kind of information that, once visible, makes every past audit result look different.
---
**Cross-References:**
- [Kaapse Baai](../star-systems/GJ-213/index.md) — Headquarters; founding community; primary market
- [Sertanejo Design](sertanejo-design.md) — South reach design peer; adjacent market segment
- [Quebrada Cultural](quebrada-cultural.md) — South reach cultural enterprise; shared institutional client base
- [Veldfontein Botanical](veldfontein-botanical.md) — Materials supply relationship; botanical extract components
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/commonstock-foods.md
+85 -7
View File
@@ -1,24 +1,102 @@
---
title: "Commonstock Foods"
description: "Commonstock Foods — consumer goods manufacturer based in Sirius, core"
description: "Sirius volume food manufacturer — packaged staples, meal components, and preserved goods for the core corridor's mass market, with a shelf-life labeling methodology that quietly advantages the company at the buyer's expense"
slug: commonstock-foods
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Sirius (GJ 244A)
tags: [commodity_branded, core, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [mercado-travessia, westfield-common, iberian-standard-foods]
---
# Commonstock Foods
**Type:** Corporation — Consumer Goods Manufacturer
**Type:** Corporation — Consumer Food Manufacturer
**Also Known As:** Commonstock
**Status:** Canonical
**Scope:** Regional — core operations
**Headquarters:** Sirius (GJ 244A)
**Scope:** Core corridor primary; transit hub distribution secondary
**Headquarters:** Sirius (GJ 244A) — core, 2 hops from Gateway
**Classification:** Sub-Syndic volume consumer enterprise; mass-market packaged food
Commonstock Foods is a consumer goods manufacturer operating out of Sirius (GJ 244A). Details to be expanded.
---
## Overview
Commonstock Foods exists to solve a problem that emerges wherever populations cluster without direct access to agricultural production: people need to eat, regularly and inexpensively, and whatever they eat needs to be available when they need it. At Sirius — a system whose importance as a transit hub has produced a population too large and too transient to be fed by local agriculture alone — Commonstock has been answering this problem for fifty years.
The company manufactures packaged staples: grain-based meal components, preserved proteins, dried vegetables, composite foods designed for preparation in the limited cooking facilities typical of corridor transit accommodation. The products are not luxury goods. They are not attempting to be. They are functional, affordable, and available — present at every transit hub commissary, every station common store, every residential reseller that serves a working population. Commonstock's measure of success is not acclaim; it is the absence of a gap between what a transit worker needs and what is available at the counter.
This is a real and difficult service to perform reliably across the distances involved, and Commonstock performs it competently. The question that does not appear in the company's public profile concerns the gap between what "best before" printed on a Commonstock package means and what the company's internal quality documentation recommends it should mean.
---
## Origin
Commonstock was founded fifty-two years ago by a logistics operator who had been running food distribution at Sirius's transit hub and concluded that the distribution problem was downstream of a manufacturing problem: the food being distributed was produced by a mix of suppliers with inconsistent quality and inconsistent packaging standards, which made managing inventory and predicting shelf life complicated and wasteful. Vertical integration — a single manufacturer producing to consistent specification — would solve both problems.
The founding investment secured manufacturing space at Sirius's industrial zone and three years later Commonstock was producing its first product lines. The distribution relationships were already in place; the founding operator had them from the distribution business. Growth was rapid and was driven almost entirely by the transit hub's existing demand rather than marketing investment.
---
## Operations
**Product lines:** Grain-based staples — rolled and pressed grain products in bulk and portion packaging. Preserved protein lines — processed and sealed in formats that maintain nutritional content across extended storage. Composite meal products — multi-component packages designed to produce a complete nutritional profile without additional sourcing. A smaller range of flavoring and supplement products that function as complements to the core lines.
**Manufacturing:** Two facilities at Sirius. The primary facility handles bulk production; the secondary handles packaging and the more specialized composite products. Combined workforce of three hundred and forty, the majority in production roles.
**Distribution:** Through transit hub commissaries, station commercial operators, residential resellers, and a small direct retail presence at Sirius. Products reach the inward corridor through transit hub distribution channels; they reach the outer reach when transit hub resellers include them in outbound cargo. Commonstock does not manage outward distribution directly; it supplies the hub and the hub distributes.
**Pricing:** Positioned at the accessible end of the market. The margin is thin; the volume is the model.
---
## Political Relationships
**Mercado Travessia:** Mercado Travessia is Commonstock's largest single distribution partner, carrying its product lines across multiple transit hub retail locations. The procurement terms Mercado negotiated are structured as volume commitments in exchange for exclusivity on certain product categories — meaning Mercado cannot stock competing equivalent products in those categories while Commonstock maintains the supply. This arrangement gives Commonstock significant commercial leverage over its most important distribution relationship.
**Westfield Common:** Westfield Common and Commonstock occupy adjacent market positions at the core corridor's transit hubs — Westfield in general goods retail, Commonstock in packaged food. Their customer base is the same transit worker population, and their distribution logistics overlap at several hub locations. The relationship is commercially arm's-length but the two companies have aligned interests on hub operator fee structures and supply chain access terms.
**Iberian Standard Foods:** Iberian Standard is Commonstock's primary direct competitor for packaged food supply at core corridor transit hubs and the company most affected by Commonstock's distribution exclusivity arrangements. Iberian Standard has been unable to enter several hub locations that Commonstock's Mercado relationship controls, and has raised this with the Lattice Commission's commercial access panel without reaching a finding.
---
## What They Don't Talk About
The Lattice Commission's consumer food standards specify that "best before" labeling must reflect the date at which a product can no longer be expected to meet its stated nutritional and quality specifications under recommended storage conditions. The standard formula for calculating this date is based on accelerated aging tests conducted at defined temperature and humidity parameters.
Commonstock's internal quality protocol documents, developed when the company was founded and revised twice since, recommend a shelf-life calculation method that aligns with the Commission's standard formula and produces dates that match the actual deterioration timeline the testing demonstrates. The products ship to the calculated dates.
In practice, Commonstock's production labeling applies a calculation that counts shelf life from the date of packaging rather than the date of manufacture — a distinction that introduces a gap of between six and eighteen days, depending on the product line, between the Commission formula result and the printed date. The gap is within the Commission's permitted tolerance band for labeling variance. The Commission standard allows for tolerance because manufacturing dates and packaging dates are not always identical. Commonstock treats the tolerance band as a production efficiency tool rather than an accuracy approximation — systematically applying a date that sits at the acceptable edge of the tolerance, every batch, as a matter of policy.
The practical effect is that products reaching consumers through transit hub resellers carry "best before" dates that overstate freshness by the tolerance amount. A buyer in a corridor commissary purchasing a package with a date six weeks out may have less than five weeks of actual quality window. The package is not unsafe; it is less fresh than it represents.
---
## Gameplay Relevance
Commonstock Foods is ubiquitous background presence in transit corridor environments — its packaging appears in commissaries, common stores, personal quarters, and cargo manifests. It is not a primary investigation target under most circumstances but is ambient economic texture in every transit context.
The labeling methodology is an investigative thread in consumer protection or corporate accountability contexts. The production protocol documents that establish the policy exist in Commonstock's manufacturing records; the Commission's standard formula is a public document; the gap between them is demonstrable by comparison. The interest is not in any individual package but in the policy itself — a deliberate systematic choice to place the date at the edge of what the Commission allows, not because the tolerance is needed but because it captures additional shelf time at the consumer's expense.
Commonstock's distribution relationships also make it a useful node for tracking the movement of goods through transit hub supply chains.
The labeling methodology case, if built, would be a structural complaint rather than a product safety complaint — the distinction matters for which regulatory pathway applies. Product safety cases trigger mandatory recall; structural labeling cases are subject to administrative remedy that Commonstock's legal team can contest through multiple review layers. The more direct route is the distribution relationships: a transit hub commissary operator who understands that the products they are selling have systematically shorter freshness windows than the dates indicate has a straightforward misdescription claim without regulatory delay. Commissary operators buy on margin and rotate stock carefully; freshness variance of the magnitude Commonstock's policy produces affects their operational losses in ways they can calculate and document — and they have standing to bring a claim that the transit workers they serve do not.
---
**Cross-References:**
- [Sirius](../star-systems/GJ-244A/index.md) — Headquarters and primary manufacturing location
- [Mercado Travessia](mercado-travessia.md) — Distribution partner; carries Commonstock in transit retail contexts
- [Westfield Common](westfield-common.md) — Transit hub retail peer; overlapping consumer market
- [Iberian Standard Foods](iberian-standard-foods.md) — Core food manufacturing peer; competitive market position
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/comptoir-lendel.md
+86 -7
View File
@@ -1,24 +1,103 @@
---
title: "Comptoir Lendel"
description: "Comptoir Lendel — regional specialty producer based in Groombridge, core"
description: "Groombridge luxury food and specialty goods trading house — provenance-authenticated products from across the Reach, curated for the financial district's premium buyer, with an authentication model that charges for certificates without verifying chains"
slug: comptoir-lendel
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Groombridge (GJ 380)
tags: [terroir, core, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [alcyone-tech, arclamp, calloway-distillery, brindlewood-honey]
---
# Comptoir Lendel
**Type:** Corporation — Regional Specialty Producer
**Type:** Corporation — Luxury Food and Specialty Goods Trading House
**Also Known As:** the Comptoir
**Status:** Canonical
**Scope:** Regional — core operations
**Headquarters:** Groombridge (GJ 380)
**Scope:** Core primary; provenance products from across the Reach
**Headquarters:** Groombridge (GJ 380), Lendel district
**Classification:** Sub-Syndic specialty retail and import enterprise; scarcity-class rare provenance goods
Comptoir Lendel is a regional specialty producer operating out of Groombridge (GJ 380). Details to be expanded.
---
## Overview
Groombridge's Lendel district houses people with money, institutional relationships requiring cultivated hospitality, and the specific desire to consume things that demonstrate neither was easy to acquire. Comptoir Lendel serves this market: a carefully curated trading house specializing in provenance-authenticated food and specialty goods from across the Reach — Calloway single malts, Brindlewood honey, Ashfield preserved goods, northern corridor textiles, south reach botanical preparations — things that are expensive because they are genuinely rare or genuinely distinct, and presented in ways that make the rarity legible.
The Comptoir occupies a physical shopfront in Lendel's commercial quarter and a larger storage and processing facility two blocks away. The shopfront is the argument: understated, specific, arranged to suggest that what is on the shelves was worth finding. The processing facility is where provenance certificates are issued, lots are labeled, and the documentation that transforms a cask of north reach whisky into a certified authenticated product is assembled.
Provenance authentication is Comptoir Lendel's core competency claim. It is also the part of the operation that does not bear close examination.
---
## Origin
Comptoir Lendel was established thirty-one years ago by a trader named Olivier Marchais who had spent twelve years working in specialty food import for a larger commercial house and concluded that the premium end of the market was being undersupplied and overcharged simultaneously. Existing importers were selling rare corridor products at premium prices without providing buyers any reliable way to verify the product was what it claimed to be — provenance documentation was inconsistent, chain-of-custody records were incomplete, and the premium commanded by genuinely rare products was partly a premium for information buyers had no way to assess.
Marchais's founding proposition was that rigorous provenance authentication would command its own premium and would differentiate a serious trading house from competitors selling documented products alongside undocumented ones. He invested in authentication infrastructure — relationships with certification bodies, chain-of-custody documentation systems, a branded certificate format that became recognizable in the Lendel premium market. The proposition was correct. The Comptoir built its reputation on the authentication layer and has maintained it.
---
## Operations
**Product selection:** Marchais's successors maintain his curation ethos — a small catalogue of genuinely distinct products, sourced from producers with verifiable origins, selected on quality and provenance specificity rather than volume or margin. The Comptoir does not stock commodity premium goods. It stocks things that cannot be acquired anywhere inward without paying for transit.
**Authentication:** The Comptoir's provenance certification system assigns lot numbers, issues origin certificates, and maintains a registry of certified lots available to buyers for verification. Certificates accompany every product sold. The format is standardized, printed on distinctive paper, and signed by the Comptoir's head of provenance.
**Client base:** Groombridge financial houses, senior institutional staff, private residences of commercial significance, and hospitality accounts — private dining rooms, high-status meeting venues. The Comptoir does not sell to general retail. Relationships are maintained through account management, not footfall.
**Volume:** Deliberately constrained. The Comptoir is not trying to grow; it is trying to remain the operation that its clients consider the only credible source for what it stocks.
---
## Political Relationships
**Calloway Distillery:** The Comptoir's Calloway single malt relationship is its most commercially significant provenance product. The two operations have worked together for eighteen years; the Comptoir maintains allocation rights to specific Calloway House expressions that no other Groombridge retailer can carry. This exclusivity depends entirely on the Distillers' Council's continued endorsement — if the Council withdrew its recommendation, the Comptoir's single malt positioning would be severely damaged.
**Brindlewood Honey:** Brindlewood is the Comptoir's other signature terroir product and the relationship that most clearly illustrates the authentication question. The Comptoir issues provenance certificates for Brindlewood lots that were never independently verified; if either the Brindlewood provenance claims or the Comptoir's certification process were challenged, both would be implicated simultaneously. The financial houses that serve as the Comptoir's primary clients include several whose compliance officers have signed off on Comptoir certifications for hospitality procurement purposes.
**Alcyone Tech and Arclamp:** The Comptoir shares the Lendel district institutional client base with Alcyone and Arclamp. All three companies are, at this moment, maintaining undisclosed product or process gaps relative to what their client-facing representations imply. The cluster is coincidence of geography rather than coordination — but a regulatory review triggered by any one of them would create an environment in which all three are examined.
---
## What They Don't Talk About
The Comptoir's provenance certification is performed through a contract with a documentation service called the Corridor Origin Registry — a company that charges per-certification and produces standardized documentation for any lot submitted to it with the required producer declaration.
The Registry verifies that the producer declaration was submitted and that the documentation is complete. It does not independently verify the producer declaration's accuracy. It does not conduct site visits. It does not compare submitted lot characteristics against reference samples from verified sources. Its certification fee covers document preparation and registry filing; it does not cover investigation.
The Comptoir knows this. It has always known this; the decision to use the Registry rather than a verification-competent authentication service was an explicit cost decision made when the authentication program was designed. Certificates from the Registry look identical to certificates from services that actually verify the chain of custody, because the Registry's format was designed to match the premium market's visual expectation.
Among the Comptoir's current catalogue, a minority of products have provenance chains that have been independently verified at source. The majority carry certificates whose underlying producer declarations have never been checked by anyone with the means to do so. Whether any of those producer declarations are inaccurate is not a question the Comptoir can answer — because it has never asked.
---
## Gameplay Relevance
Comptoir Lendel is ambient luxury goods presence in Groombridge and a useful social environment for a player navigating the Lendel financial district. Its shopfront and account management relationships make it a natural contact point for premium-market investigative work.
The authentication gap is the investigative thread. The Corridor Origin Registry's operational model — certification without verification — is documented in the Registry's own service terms, which are publicly available. A player who obtains Comptoir certificates and compares them to the Registry's service description will find that the gap between what a certificate implies and what was done to produce it is explicit in the Registry's own documentation. The question is whether the Comptoir's clients understand what they are purchasing and whether the Comptoir's marketing has accurately described what the authentication provides.
Several of the Comptoir's high-value products — Calloway whisky lots, authenticated Brindlewood honey — are also connected to supply chains with their own integrity questions, creating layered investigative possibilities.
The Comptoir's exposure is reputational rather than legal — the Corridor Origin Registry's terms are what they are, and clients who read the Registry's service description before relying on the certificates cannot claim they were deceived by the Registry's process. What they can claim is that the Comptoir represented the authentication as something it was not in its own marketing and client communications, which consistently use language implying independent verification. The financial houses of the Lendel district, whose hospitality operations use Comptoir products and cite their authentication in procurement justifications, have both standing and motivation. The Comptoir's market position is entirely built on the trust that its authentication implies; the trust is the product, and the product has been partially constructed from materials that do not support it.
---
**Cross-References:**
- [Groombridge](../star-systems/GJ-380/index.md) — Headquarters; primary market; Lendel district location
- [Calloway Distillery](calloway-distillery.md) — Key supplier; Calloway single malt catalogue
- [Brindlewood Honey](brindlewood-honey.md) — Supplier; north reach terroir product
- [Arclamp](arclamp.md) — Lendel district enterprise; shared institutional client base
- [Alcyone Tech](alcyone-tech.md) — Adjacent Lendel district; overlapping premium client relationships
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/coriolis-exchange.md
+84 -7
View File
@@ -1,24 +1,101 @@
---
title: "Coriolis Exchange"
description: "Coriolis Exchange — premium service provider based in Groombridge, core"
description: "Groombridge multi-currency settlement and transit exchange service — the practical mechanism by which corridor travelers convert Tractus holdings to local currencies, running a rounding methodology that captures fractions at scale across millions of transactions"
slug: coriolis-exchange
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Groombridge (GJ 380)
tags: [service_premium, core, tractus]
decision_refs: [D-189]
cross_refs: []
cross_refs: [groombridge-settlement-house, alcyone-tech, meridian-risk, nordhavn-financial]
---
# Coriolis Exchange
**Type:** Corporation — Premium Service Provider
**Type:** Corporation — Multi-Currency Settlement and Exchange Service
**Also Known As:** Coriolis
**Status:** Canonical
**Scope:** Regional — core operations
**Headquarters:** Groombridge (GJ 380)
**Scope:** Core primary; inward corridor transit exchange secondary
**Headquarters:** Groombridge (GJ 380), Lendel district
**Classification:** Sub-Syndic financial services; licensed exchange operator under Lattice Commission currency frameworks
Coriolis Exchange is a premium service provider operating out of Groombridge (GJ 380). Details to be expanded.
---
## Overview
The corridor runs on multiple currencies. Tractus denominations clear the long-haul commercial transactions that make interstellar trade possible, but the day-to-day exchange at any given system uses whatever that system's economic tradition prefers — Marks in the west reach, local currencies in outer systems, Tractus only in the core financial districts where institutional clearing is the primary activity. A traveler moving across the corridor, or a merchant managing multi-system accounts, requires exchange services at every transition point.
Coriolis Exchange provides those services at Groombridge and, through a network of correspondent relationships, at seventeen additional systems across the inner corridor. It is not a bank. It does not hold deposits or provide credit. It performs one function — converting currency holdings between denominations at published rates — and performs it reliably, quickly, and with the institutional documentation that commercial clients require for their accounting records. The company processes several hundred thousand transactions per month across its network. This scale is the basis of its business model in ways that are not fully apparent from the published rate sheets.
---
## Origin
Coriolis Exchange was founded twenty-eight years ago by a financial services administrator named Pieter Anstey who had spent a decade processing currency conversions as an internal function for a mid-size Groombridge commercial house. The conversion function was being charged to the commercial house at rates set by whatever exchange service was available; Anstey's position was that the rates were high and the service was unsophisticated, and that a dedicated exchange operation built around transaction volume rather than per-conversion margin could undercut the existing providers while maintaining profitability.
He was correct. The initial Groombridge operation, launched with three terminal stations in the Lendel district, took market share from established providers within two years on the basis of published rates that were measurably better. Growth to correspondent relationships at adjacent systems followed over the next decade as commercial clients with multi-system operations found it more efficient to use a single exchange provider across their corridor footprint.
---
## Operations
**Services:** Currency exchange between Tractus denominations and Mark, between Tractus and major outer-reach local currencies, and between regional denominations for clients managing cross-corridor commercial accounts. Exchange at published rates with immediate settlement for personal transactions; negotiated rate structures for commercial clients above defined volume thresholds.
**Network:** Physical exchange terminals at Groombridge — six in the Lendel district, two at the transit hub. Correspondent relationships at seventeen additional systems, through which Coriolis transactions can be initiated and settled remotely. The correspondent network is maintained through service agreements with local financial operators who handle the physical terminal operations and are paid a per-transaction fee by Coriolis.
**Clients:** A mix of personal (corridor travelers, individuals with multi-system holdings) and commercial (trading houses, import operations, merchants managing multi-denomination accounts). The commercial clients represent the volume; the personal clients represent the transaction count.
**Licensing:** Lattice Commission licensed exchange operator. Required disclosures include published exchange rates, fee structures, and settlement timing. Coriolis complies with all required disclosures.
---
## Political Relationships
**Groombridge Settlement House:** GSH's clearing infrastructure and Coriolis's exchange operations are complementary layers of the same financial system — GSH clears institutional Tractus transactions; Coriolis handles the personal and small-commercial conversions that the clearing infrastructure doesn't reach. The Settlement House refers clients to Coriolis for currency conversion needs outside its institutional scope. This referral relationship means Coriolis's service quality is implicitly endorsed by GSH, which has no visibility into the rounding methodology.
**Meridian Risk:** Meridian Risk's underwriting operations require multi-currency transaction records for premium and claim processing, and Coriolis provides exchange documentation for a portion of Meridian's client transactions. The relationship is transactional rather than strategic, but it gives Meridian's compliance team exposure to Coriolis transaction records — records that document what the rounding methodology looks like at the transaction level.
**Nordhavn Financial:** Nordhavn is Coriolis's primary west reach correspondent partner, handling Mark-currency exchange on the western corridor nodes of Coriolis's network. The correspondent relationship means Nordhavn's exchange terminals use Coriolis's rate infrastructure and rounding methodology, extending the methodology's application beyond Coriolis's directly operated terminals. Nordhavn signed the correspondent agreement without reviewing the technical specification annex that documents the rounding rule.
---
## What They Don't Talk About
Coriolis's published rates are accurate. Its fee schedule, disclosed as required on page 34 of the standard service agreement, is also accurate. What neither document fully describes is the rounding methodology applied to transaction calculations.
When Coriolis calculates the output of a currency conversion, it rounds to the nearest unit of the output denomination. This is standard and expected. What is not prominently disclosed is that the rounding rule applied to transactions below a defined size threshold rounds to the nearest full unit in the direction that benefits Coriolis rather than randomly or in the client's favor. On a conversion of 47.3 Marks, the client receives 47 Marks; on 47.7, they receive 47 Marks. The 0.3 and 0.7 fraction captures are credited to a Coriolis settlement account.
Each individual capture is trivial. Across hundreds of thousands of transactions per month, the settlement account accumulates meaningful volume. The methodology is documented in the service agreement's technical specification annex, which is available on request. It is not summarized in the fee schedule, the published rate display, or any client-facing communication that a personal transaction client would be expected to read.
The commercial clients above the volume threshold negotiate their rate structures individually and are not subject to the standard rounding methodology. The rounding capture falls disproportionately on personal transaction clients — travelers and individuals — for whom the per-transaction amount is genuinely negligible but whose aggregate contribution to Coriolis's settlement account is substantial.
---
## Gameplay Relevance
Coriolis Exchange is ambient financial infrastructure in Groombridge and a practical service that player characters use during corridor transit — exchange terminals appear in transit hubs, commercial districts, and transit accommodation. The company is not a primary investigation target under most circumstances.
The rounding methodology is an investigative thread in financial practice contexts. The technical specification annex exists and is available on request; the gap between what the disclosure says and what a client who read only the standard materials would understand is the substance of a consumer financial practice complaint. The aggregate settlement account — which exists, has a balance, and is described internally as a "transaction reconciliation reserve" — is the evidence that the methodology is a revenue mechanism rather than a technical necessity.
Coriolis's correspondent network also makes it a useful intelligence layer — transaction records at Coriolis terminals document financial flows between individuals and commercial parties across seventeen systems.
The rounding settlement account is the cleanest investigative target: it exists, it has a balance history, and it is described internally in language that acknowledges its function while framing it as operational bookkeeping. A player who obtains the account records and the rounding methodology documentation has evidence of a systematic revenue mechanism whose existence is not disclosed to the personal transaction clients who fund it. The commercial clients who negotiated individual rate structures are not affected and have no standing in a complaint — which means the case depends on assembling enough personal transaction clients to make the aggregate picture legible. The financial authority that would hear such a complaint is the Lattice Commission's consumer financial services panel, which has not previously received a rounding methodology complaint. Coriolis's legal position, if challenged, rests entirely on the page-34 disclosure — which is accurate, but which the Commission may or may not accept as sufficient notice for a practice generating the revenues the settlement account documents.
---
**Cross-References:**
- [Groombridge](../star-systems/GJ-380/index.md) — Headquarters and primary terminal network
- [Groombridge Settlement House](groombridge-settlement-house.md) — Institutional relationship; clearing infrastructure overlap
- [Alcyone Tech](alcyone-tech.md) — Lendel district peer; institutional client overlap
- [Meridian Risk](meridian-risk.md) — Financial services peer; Lendel district
- [Nordhavn Financial](nordhavn-financial.md) — Correspondent partner; west reach exchange network
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/cygni-combines.md
+1 -1
View File
@@ -11,7 +11,7 @@ faction_type: economic
headquarters: Cygni B (GJ 820B)
tags: [electronics, advanced_alloys, manufacturing, assembly, tractus, core]
decision_refs: [D-175]
cross_refs: []
cross_refs: [luanda-fabrication]
---
# Cygni Combines
wiki/corporations/dalbit-systems.md
+81 -7
View File
@@ -1,24 +1,98 @@
---
title: "Dalbit Systems"
description: "Dalbit Systems — precision technology manufacturer based in Seongho, east reach"
description: "Seongho precision electronics and navigation systems manufacturer — east reach sensor and guidance hardware with an exclusive component supply arrangement that the company's clients are not told about"
slug: dalbit-systems
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Seongho (GJ 660A)
tags: [tech_premium, east_reach, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [higashiyama-vehicle, hangang-studio, kumho-navigation]
---
# Dalbit Systems
**Type:** Corporation — Precision Technology Manufacturer
**Type:** Corporation — Precision Electronics and Navigation Systems Manufacturer
**Also Known As:** Dalbit, DS
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Seongho (GJ 660A)
**Scope:** East reach primary; inward corridor navigation systems secondary
**Headquarters:** Seongho (GJ 660A) — east reach, 5 hops from Gateway
**Classification:** Sub-Syndic precision electronics enterprise; navigation and sensor systems supply
Dalbit Systems is a precision technology manufacturer operating out of Seongho (GJ 660A). Details to be expanded.
---
## Overview
The east reach's navigation environment is particular: dense system packing in certain corridors, variable gate geometry at the outer edges, and a transit infrastructure that developed faster than the standardization frameworks that would have made component interoperability straightforward. The practical result is that navigation and sensor hardware for east reach transit often needs to be calibrated specifically for local conditions rather than configured from general-purpose components designed for the core corridor's more predictable geometry.
Dalbit Systems has built its market position on this specificity. The company's navigation and sensor products are calibrated at manufacture for east reach transit conditions, include support for the legacy communication protocols still common in the outer east systems, and are backed by a service network that can reach most east reach ports within a reasonable transit interval. Clients who have bought Dalbit are clients who found that inward general-purpose suppliers provided hardware that worked acceptably in standard conditions and degraded noticeably in the corridor's more demanding passages. Dalbit's comparative advantage is that its hardware was designed for the demanding passages rather than optimized for the easy ones.
---
## Origin
Dalbit was founded thirty-five years ago by a navigation engineer named Han Ju-won, who had spent fifteen years maintaining navigation systems on east reach cargo transports and had accumulated, through direct operational experience, a detailed technical understanding of the ways that inward-designed navigation hardware failed in east reach conditions. His founding proposition was that this knowledge, formalized into product specifications, would produce hardware measurably superior to inward imports for east reach clients.
The first product line — a sensor calibration module for existing navigation systems — was designed to retrofit hardware that transit operators already had and correct its east reach performance deficiencies without requiring full system replacement. The retrofit approach gave Dalbit access to an installed base that already existed and demonstrated the performance improvement in conditions clients could directly observe. Full system products followed six years later, once the retrofit reputation had established Dalbit as a credible hardware source.
---
## Operations
**Product lines:** Navigation systems for transit vessels — sensor arrays, gate approach processors, and integrated guidance systems calibrated for east reach corridor conditions. Sensor hardware for surface operations — proximity detection, environmental monitoring, positioning systems for use in mining and industrial applications. Communication interface units that bridge legacy east reach protocols to current-generation transit infrastructure. Calibration services for third-party hardware.
**Manufacturing:** Single facility at Seongho. Seventy-eight employees, approximately half in engineering and technical production roles. The facility is not large; Dalbit's products are high-precision and low-volume by design. The engineering staff is what makes the products work; the manufacturing floor executes specifications the engineering team produces.
**Certification:** Lattice Commission navigation hardware certification for all applicable product lines. East reach regional transit authority certification additionally required for certain gate approach systems; Dalbit holds all applicable regional certifications.
**Service:** Technical service contracts with most major east reach transit operators. Dalbit maintains service engineers at Seongho and two adjacent systems.
---
## Political Relationships
**Higashiyama Vehicle:** Higashiyama's vehicle line uses Dalbit navigation systems as standard integration in its atmospheric and surface transport products. The integration creates a mutual dependency — Higashiyama's vehicles are tested and certified with Dalbit hardware; a navigation system change would require re-certification. Dalbit's service contract requirement for Dalbit-sourced components therefore extends through Higashiyama's service network to Higashiyama vehicle operators who may not realize their navigation maintenance is locked to a single supplier chain.
**Kumho Navigation:** Kumho is Dalbit's primary direct competitor in east reach navigation systems and the company that would most benefit from Dalbit's undisclosed supplier ownership becoming public. Kumho has complained informally to the east reach transit authority about the single-source service requirement that Dalbit's contracts impose, arguing it constitutes a barrier to competing maintenance provision. The authority has not acted; Kumho does not know about the Mirae ownership position that would give the complaint substantially more force.
**Lattice Commission:** Dalbit's navigation hardware certification and its Commission registration are the two filing contexts where the Mirae ownership stake is disclosed. The Commission's commercial registration team and its certification team operate independently; neither has flagged that a company certifying hardware also partially owns its primary component supplier. This is not a gap in Commission rules — it is a gap in cross-departmental review.
---
## What They Don't Talk About
Dalbit's navigation system product line relies critically on a class of high-precision optical sensor component that the company does not manufacture. These components are sourced exclusively from a single supplier — Mirae Optical Components, a small manufacturer operating out of a neighboring system. The exclusivity is the result of a supply contract that Dalbit negotiated ten years ago, which gives Mirae exclusive supplier status for the sensor class in exchange for pricing and priority allocation commitments.
The arrangement is commercially standard. What Dalbit's procurement documentation does not disclose to its clients — and what is absent from Dalbit's product specifications — is that Dalbit holds a 31% ownership stake in Mirae Optical Components, acquired through a private placement four years ago. When Dalbit clients ask why their navigation systems can only be serviced with Dalbit-sourced optical components, they are told it is an engineering compatibility requirement — the sensor geometry is calibrated to Mirae's specific manufacturing tolerances and cannot be substituted without recalibration that Dalbit controls.
This is technically accurate. It is not the complete explanation. Dalbit's service contract terms, which require clients to use Dalbit-sourced components for warranty-covered maintenance, ensure that every service event on a Dalbit navigation system generates parts revenue that flows partially back to a company Dalbit co-owns. The ownership position is disclosed in Dalbit's Commission registration filings; it is not disclosed in client contracts, procurement documentation, or service agreements.
---
## Gameplay Relevance
Dalbit Systems is technical background presence in east reach transit environments — its hardware is in navigation stations, on transport vessels, and in the communications infrastructure of systems that adopted east reach protocols before standardization. It is not a primary investigation target outside of procurement or supply chain investigations.
The Mirae ownership arrangement is the investigative thread. The 31% stake exists in Commission registration filings. The service contract language requiring Dalbit-sourced components is in client contracts. The gap between "engineering compatibility requirement" and "we co-own the parts supplier" is demonstrable by comparison. A client who understood the relationship would have grounds to challenge whether the exclusive service requirement was justified on engineering grounds or commercial ones.
Dalbit's service network also makes it a source of operational information about east reach transit activity — the engineers who service navigation systems observe the vessels they work on and the routes those vessels run.
The Mirae ownership situation creates a specific vulnerability for Dalbit if exposed: the service contracts that require clients to use Dalbit-sourced components are standard maintenance terms that clients accepted without knowing the component supplier was partially Dalbit-owned. A client who subsequently discovers the ownership position and reviews the service contract has the basis of an undisclosed conflict complaint — the contractual requirement that the client buy from a supplier the company co-owns was not disclosed when the contract was signed. The "engineering compatibility" explanation that Dalbit provides when clients ask about the single-source requirement is technically accurate but incomplete in a way that the ownership disclosure would make clearly material. A player who can produce both the ownership documents and a service contract in the same room as an affected client has a conversation that does not require litigation to be consequential.
---
**Cross-References:**
- [Seongho](../star-systems/GJ-660A/index.md) — Headquarters; primary manufacturing and client base
- [Higashiyama Vehicle](higashiyama-vehicle.md) — East reach technology peer; vehicle navigation integration client
- [Kumho Navigation](kumho-navigation.md) — East reach navigation peer; competitive and sometimes cooperative market position
- [Hangang Studio](hangang-studio.md) — Seongho-adjacent enterprise; shared east reach commercial context
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/destilaria-confluencia.md
+91 -7
View File
@@ -1,24 +1,108 @@
---
title: "Destilaria Confluencia"
description: "Destilaria Confluencia — regional specialty producer based in Confluência, south reach"
description: "South_reach artisanal spirit producer based at Confluência (GJ 566B) — two-century sugarcane heritage, locally adapted cultivar, and a premium aged line that has built the reputation the volume line quietly depends on"
slug: destilaria-confluencia
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Confluência (GJ 566B)
tags: [terroir, south_reach, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [matahari-consumer-goods]
---
# Destilaria Confluencia
**Type:** Corporation — Regional Specialty Producer
**Type:** Corporation — Artisanal Spirit Producer
**Also Known As:** the Destilaria, Confluencia (abbreviated, no accent)
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Confluência (GJ 566B)
**Scope:** Regional — south_reach corridor primary; inner-corridor specialty market secondary
**Headquarters:** Confluência (GJ 566B) — south_reach corridor
**Classification:** Sub-Syndic family enterprise; founding-cohort ownership compact
Destilaria Confluencia is a regional specialty producer operating out of Confluência (GJ 566B). Details to be expanded.
---
## Overview
Destilaria Confluencia makes cachaça. It has made cachaça — specifically, an aged aguardente variant distilled from the sugarcane cultivar its founding families brought to Confluência and have been adapting to local conditions for two hundred and twenty years — as its primary commercial enterprise since the system's second generation. The spirit the Destilaria produces from its best batches is genuinely difficult to reproduce elsewhere. The sugarcane at Confluência has spent nine generations selecting for the system's specific conditions: the mineral content of the alluvial soil at the primary growing sites, the seasonal temperature variation, the fermentation character that the local microbial population imparts. You can buy sugarcane from another system and distill it at Confluência and produce competent spirit. It will not taste the same.
This is the public proposition, and it is substantially accurate for the Destilaria's premium production. The full picture is more complicated.
---
## Origin
The settling families of Confluência arrived in the early wave_3 expansion from a predominantly Brazilian-Portuguese corridor community. They brought sugarcane cuttings, copper pot still designs, and the conviction that their distillation tradition required specific soil and water conditions to be practiced honestly rather than merely technically. The first generation planted and observed. The second generation distilled and sold locally. The third generation began exporting through south_reach trade routes.
The name they gave the operation — Confluencia, without the accent mark of the system name, a practical simplification that became the brand's canonical form — was chosen for the meeting-of-waters character of the primary growing region, where two seasonal streams converge below the main distillery site and create the alluvial soil profile the cultivar prefers. The water is part of the product. Every batch traces to it.
The current operation is in its seventh generation of the founding family network. Governance is shared among three families — the Medeiros, the Figueira-Santos, and the Braga-Pinto families — whose ancestor cohort founded the Destilaria together and whose descendants hold equal governance shares under a compact renewed every generation without formal amendment.
---
## Operations
**Production structure:** The Destilaria operates two distinct production lines that it does not publicly distinguish. The premium aged line — Confluencia Reserva, aged in local hardwood barrels for a minimum of eight years, and Confluencia Grande Reserva, aged fifteen years in imported cooperage sourced through north_reach forestry contracts — uses exclusively Confluência-grown sugarcane and follows the founding families' distillation specifications without variation. These batches are small, expensive, and genuinely representative of the terroir claim.
The volume line — Confluencia Branca, sold in larger quantities through standard south_reach distribution channels — does not follow the same specification. During harvest shortfalls, which have occurred in roughly one in four growing seasons over the past thirty years due to yield variability in the local cultivar, the production team blends locally-produced spirit with off-system industrial ethanol sourced through a logistics contractor. The blending is managed to maintain flavour profile consistency. The label does not explicitly claim geographic origin for the spirit base.
**Workforce:** Forty-one people, primarily in cultivation, fermentation, and barrel management. The distillation is overseen by a production head from the Medeiros family, as it has been for four of the seven generations.
**Distribution:** Premium production moves through specialty distributors in the inner corridor. Volume production moves through standard south_reach freight channels, consolidated through logistics contracts managed by a subsidiary called Vias de Sul Transporte, registered at Confluência under a separate commercial filing.
---
## Products
**Confluencia Reserva** — the eight-year expression. Amber, smooth, a long finish carrying the specific mineral character of the alluvial soil at the primary growing site. Distributed in modest quantities to south_reach markets and specialist inner-corridor buyers. Provenance documentation included. This is what the Destilaria's reputation rests on.
**Confluencia Grande Reserva** — the fifteen-year expression, produced in limited quantities from the oldest barrel stock. Not widely available outside the primary south_reach systems. Regarded by the small community who track such things as one of the corridor's genuine terroir spirits, specific to a place and unreproducible elsewhere.
**Confluencia Branca** — the unaged volume expression. Sold primarily in the south_reach at accessible price points. What most consumers encounter when they encounter Confluencia at all. The product that funds the premium operations.
---
## Political Relationships
**Matahari Consumer Goods:** The dominant economic institution in the Confluência system by a significant margin. Matahari manufactures household goods and consumer essentials at industrial scale; the Destilaria is a boutique artisanal operation. They do not compete. They share logistics infrastructure — the same freight consolidation nodes, the same transit scheduling through the system's primary gate, occasionally the same cargo holds on outbound shipments. Matahari's procurement team has asked twice whether the Destilaria would be interested in co-branded gift-set arrangements. Both times, the founding families declined. They consider Matahari's commercial scale incompatible with the Destilaria's brand positioning.
**Lattice Commission:** The Commission's agricultural product authentication framework applies to geographic origin claims in spirits production. Destilaria Confluencia holds a current certification for its premium aged line. The certification was granted following an inspection of the Reserva and Grande Reserva production. The volume line was not within the inspection scope.
**South_reach distribution network:** The Destilaria's volume production moves through a broker relationship with south_reach bulk freight handlers. The logistics contractor, Vias de Sul Transporte, manages the freight contracts and the ethanol sourcing relationship on the Destilaria's behalf. The Destilaria's internal accounts treat Vias de Sul as a standard logistics vendor.
---
## What They Don't Talk About
Vias de Sul Transporte is not a third-party logistics firm. It was incorporated eleven years ago by Catarina Medeiros-Faria, the eldest daughter of the current production head, three months before she was given responsibility for the volume line's logistics management. The incorporation documents are filed at Confluência and are publicly accessible. The connection between the firm and the Medeiros family requires looking for it.
The service fees that Vias de Sul charges the Destilaria run approximately thirty-five percent above market rate for comparable south_reach freight logistics work. The governance compact requires unanimity among the three founding family networks for amendments to the cost structure. The Figueira-Santos and Braga-Pinto families receive the after-cost dividend from production; they have been receiving a below-market return for eleven years without knowing that a portion of production costs flows to a Medeiros family member rather than to an independent vendor.
The fermentation production logs, which document the ethanol sourcing volumes and origins for the Branca line, exist in the Destilaria's internal archive. They have never been requested by Commission auditors.
---
## Gameplay Relevance
Destilaria Confluencia is useful for investigations centered on beneficial ownership structures, contract self-dealing, and the gap between certification scope and production reality. A small institution with a large documentation trail.
The productive investigation threads are:
- **The logistics subsidiary** — Vias de Sul Transporte's commercial filing is public at Confluência. Tracing beneficial ownership requires accessing the commercial register and cross-referencing it against the Destilaria's internal procurement accounts. The Figueira-Santos and Braga-Pinto families are the parties who have been harmed; presented with evidence, they would have standing to pursue a governance dispute. Whether they would act on it depends on how much they value the compact's stability.
- **The production logs** — the fermentation archive establishes what was blended into the Branca line and at what ratios. Whether this constitutes a Commission violation depends on the certification scope wording. A player who can access both documents and understands the authentication framework would know if there is a reportable discrepancy — and who the correct recipient of that report would be.
- **The certification timing** — the pattern of Commission inspection visits and production scheduling over the past eleven years shows a consistent correlation between inspection dates and peak local production months. The pattern itself is evidence.
---
**Cross-References:**
- [Confluência](../star-systems/GJ-566B/index.md) — Headquarters system; founding terroir; primary growing region
- [Matahari Consumer Goods](matahari-consumer-goods.md) — Co-system industrial neighbor; shared logistics infrastructure; declined commercial partnership
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/durban-engineering.md
+83 -8
View File
@@ -1,24 +1,99 @@
---
title: "Durban Engineering"
description: "Durban Engineering — precision technology manufacturer based in Isibaya, south reach"
description: "Zulu-South African structural monitoring and environmental sensing manufacturer at Isibaya (GJ 905) — mine safety systems, atmospheric analyzers, and the diagnostic hardware that tells extraction operators when conditions are deteriorating before the equipment does"
slug: durban-engineering
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
scope: regional
updated: 2026-04-22
scope: south_reach primary; inner corridor extraction operations secondary
faction_type: economic
headquarters: Isibaya (GJ 905)
tags: [tech_premium, south_reach, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [stalownia-kowalski, baektu-mining-alliance, luanda-fabrication]
---
# Durban Engineering
**Type:** Corporation — Precision Technology Manufacturer
**Type:** Corporation — Structural Monitoring and Environmental Sensing Systems
**Also Known As:** Durban, DE
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Isibaya (GJ 905)
**Scope:** South_reach extraction corridor primary; inner corridor specialist contracts secondary
**Headquarters:** Isibaya (GJ 905) — 2-aperture spur, 7 hops from Gateway
**Classification:** Sub-Syndic technology enterprise; extraction sector safety specialist
Durban Engineering is a precision technology manufacturer operating out of Isibaya (GJ 905). Details to be expanded.
---
## Overview
Durban Engineering does not build the machines that mine. It builds the systems that tell you when those machines are about to fail, and when the environment they are operating in is about to do the same. Structural stress monitors, atmospheric composition analyzers, vibration-pattern interpreters, pressure sensors for deep extraction shafts — these are Durban's product lines, and they are the layer of hardware that sits between a mining operation and the category of incident that ends careers and occasionally ends systems.
The distinction between the hardware that extracts and the hardware that monitors is, in commercial terms, the distinction between Stalownia Kowalski and Durban Engineering. Stalownia builds the rig. Durban's systems tell you when the rig is operating outside safe parameters. Both are necessary. In the south_reach extraction corridor, where environments are generally less forgiving and systems are far enough from core infrastructure that an incident cannot wait for specialists to transit from the inner corridor, that necessity has made Durban's product category a standard specification rather than an optional upgrade.
---
## Origin
The founders were safety engineers from Isibaya's mining sector — Zulu-South African heritage, part of the broader south_reach settlement cohort that had been building extraction operations for two generations before recognizing that the rate of serious incidents was systematically higher than the commercial risk models acknowledged. The problem was data. Extraction operators knew when equipment failed; they were receiving insufficient warning that failure was approaching. Monitoring existed in fragments — each equipment supplier included diagnostic capability in their own products, but there was no integrated picture of the operational environment as a whole.
The founding insight was integration. A single monitoring architecture that could aggregate sensor data from multiple equipment types, compare readings against environmental baselines, and flag developing conditions before they became emergencies. The first Durban systems were simple by current standards — structural stress and atmospheric composition in a single package, calibrated for the rock formations and atmospheric conditions typical of south_reach subsurface operations. They worked well enough that word moved through the extraction sector without any marketing effort.
The relationship with Stalownia Kowalski was established within the first decade, when Stalownia's maintenance contracts started specifying Durban monitoring systems as companion installations alongside new equipment. Neither company required the relationship for commercial survival. Both found it commercially advantageous, and that mutual advantage has kept it stable across several generations of both companies' leadership.
---
## Operations
**Structural monitoring:** The core product line. Sensor packages that integrate with extraction equipment and mine infrastructure to provide continuous structural health data — stress concentration readings, deformation tracking, vibration signatures that indicate specific failure modes. The monitoring systems run continuously and flag anomalies against site-specific baselines calibrated at installation. A well-maintained Durban installation produces a running record of an extraction site's structural health over its operational life.
**Atmospheric sensing:** Composition analyzers for extraction environments — detecting gas infiltration, oxygen depletion, particulate concentrations, and pressure differentials that indicate structural breach risk. Durban's atmospheric systems operate under conditions that most commercial sensor technology is not designed for. The extraction sector pays above standard commercial rates for sensors that work reliably in environments where standard sensors do not.
**Service contracts:** The hardware is sold at margins appropriate to safety-critical equipment. The ongoing value is in the service contracts — periodic calibration, firmware updates, sensor replacement, and the review reports that translate raw monitoring data into operational recommendations. Long-term extraction operations need these reviews continuously; Durban's service contracts run for the operational life of the site.
**Isibaya manufacturing:** A focused facility by industry standards, employing around 200 people across engineering, manufacturing, calibration, and field service. The workforce attrition is low; field service roles at south_reach extraction sites attract engineers who want to work in the field, and Isibaya's extraction culture treats that preference as a professional qualification.
---
## Political Relationships
**Stalownia Kowalski:** The most commercially significant relationship in Durban's portfolio. Stalownia's maintenance contracts regularly specify Durban monitoring systems alongside the equipment they service, which means Durban installations accompany Stalownia equipment across the south_reach extraction corridor. The relationship is complementary and professionally warm. Neither company has tried to move into the other's product category. The division of territory — Stalownia extracts, Durban monitors — has been clean and mutually beneficial for three generations.
**Baektu Mining Alliance:** A major direct client for belt operation monitoring. BMA's five processing stations each run Durban structural and atmospheric systems, calibrated for the specific conditions of asteroid belt operations. The BMA relationship is long-standing enough that Durban's field service team knows BMA's equipment configurations in significant detail — which is also detail about BMA's operational margins and practices that Durban holds as a matter of standard service knowledge.
**The Lattice Commission:** Safety-critical monitoring equipment for extraction operations is subject to the Commission's industrial safety certification framework. Durban's products carry Commission certification across all product lines. The certification relationship is compliance-standard — Durban files the required documentation, the Commission audits periodically, and certifications renew without incident. The Commission's field presence at south_reach extraction systems is thin; the certification process relies primarily on Durban's own documentation.
---
## What They Don't Talk About
Durban's flagship monitoring system contains a diagnostic query interface that was designed for factory testing and calibration during production. The interface is not documented in any product manual or customer-facing specification. It accepts a specific protocol handshake and returns raw sensor data at a level of detail that substantially exceeds the system's standard monitoring output — including atmospheric composition readings at molecular resolution that go beyond what the product is certified to provide.
The interface was never removed from the production firmware because removing it would have required a full firmware revision, and the production firmware was stabilized after the first major product generation. Three extraction operators — all technically sophisticated enough to have examined the hardware at a level their purchasing agreements do not actually authorize — discovered the interface independently over the past decade. They have been using it to monitor atmospheric composition signatures that indicate undisclosed mineral deposit formations at adjacent claim boundaries. In effect, they have been running an unlicensed survey operation using Durban's monitoring network as the sensor platform.
Durban's own engineering team discovered what those operators were doing approximately two years ago, when they were investigating an unrelated firmware anomaly and found the diagnostic handshakes in the monitoring system's communication logs. Their subsequent review identified which specific sites were being queried and at what intervals — which, because the atmospheric signatures those operators were monitoring are site-specific, also told them where those operators believe undisclosed deposits are located.
The engineering team filed an internal report. The report has not reached the board. The senior engineer responsible for it has been building a parallel dataset from the anomalous atmospheric signatures across those locations — stored on an engineering workstation not connected to the main network — and has not decided what to do with it.
---
## Gameplay Relevance
Durban Engineering is ambient infrastructure in the south_reach extraction corridor. Its monitoring hardware is present at most significant extraction operations, which means its sensor data is present wherever those operations exist. For a player investigating an extraction site incident, a structural failure, or why a site was abandoned before its reserves were depleted, Durban's monitoring records are a primary evidence source.
The diagnostic interface is an investigative thread with multiple directions. The three operators exploiting it are engaged in undisclosed mineral survey activity that may constitute claim-rights violations, depending on what the atmospheric signatures indicate and what those operators do with the information. The engineering team's parallel dataset exists and is accessible to someone who can reach the workstation it resides on. The senior engineer who compiled it is someone with information he has not decided how to use, which makes him both a potential source and a potential liability.
---
**Cross-References:**
- [Isibaya](../star-systems/GJ-905/index.md) — Headquarters system; south_reach extraction hub
- [Stalownia Kowalski](stalownia-kowalski.md) — Primary equipment partner; Stalownia maintenance contracts specify Durban monitoring systems
- [Baektu Mining Alliance](baektu-mining-alliance.md) — Major client; belt operation monitoring across five processing stations
- [Luanda Fabrication](luanda-fabrication.md) — Substrate supplier; manufactures the precision electronics substrates in Durban's monitoring hardware
- [Lattice Commission](../factions/lattice-commission.md) — Safety certification authority; industrial standards framework
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/eastbay-trading.md
+83 -7
View File
@@ -1,24 +1,100 @@
---
title: "Eastbay Trading"
description: "Eastbay Trading — consumer goods manufacturer based in Bridgepoint, east reach"
description: "Bridgepoint consumer goods distributor and importer — a transit hub operation that moves goods across the east reach at high volume, with warehouse arrangements that function as quiet price coordination during scarcity events"
slug: eastbay-trading
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Bridgepoint (GJ 53A)
tags: [commodity_branded, east_reach, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [nexus-way-express, dalbit-systems, commonstock-foods]
---
# Eastbay Trading
**Type:** Corporation — Consumer Goods Manufacturer
**Type:** Corporation — Consumer Goods Distributor and Transit Hub Importer
**Also Known As:** Eastbay
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Bridgepoint (GJ 53A)
**Scope:** East reach primary; transit hub distribution secondary
**Headquarters:** Bridgepoint (GJ 53A) — east reach, 3 hops from Gateway
**Classification:** Sub-Syndic commercial enterprise; consumer goods import and corridor distribution
Eastbay Trading is a consumer goods manufacturer operating out of Bridgepoint (GJ 53A). Details to be expanded.
---
## Overview
Bridgepoint earns its name: a system positioned at the intersection of east reach and core corridor transit lanes, serving as the primary resupply and redistribution point for goods moving into the outer east. What passes through Bridgepoint on its way to more distant systems represents the economic lifeline of communities that cannot produce most of what they consume locally. The entity that manages the largest share of this flow is Eastbay Trading.
Eastbay is not a manufacturer. It is a distributor — the organization that takes goods arriving at Bridgepoint from inward suppliers, holds them in warehouse facilities, manages the documentation and logistics that get them onto outbound transit vessels, and maintains the commercial relationships at both ends that make the supply chain function. It is an essential role, and Eastbay performs it competently. The company's efficiency in moving goods from arriving transit to departing transit is genuine and the outer reach communities that depend on it know it.
What is less visible to those communities is that Eastbay's warehouse capacity, strategically held against outbound transit during specific market conditions, gives it the ability to influence the price of goods it moves without technically controlling that price — an arrangement documented in its own operational planning files under language that obscures the effect.
---
## Origin
Eastbay Trading was established forty-four years ago by a freight logistics operator who had spent a decade running cargo manifest services at Bridgepoint's transit hub and had identified that the handoff between inward transit arrivals and outbound east reach distribution was managed by multiple competing intermediaries operating without coordination, resulting in warehousing inefficiencies, documentation delays, and price instability that nobody in the chain preferred. A single well-capitalized distributor managing both sides of the handoff would eliminate the friction and could offer better terms to suppliers and east reach buyers simultaneously.
The founding investment consolidated three smaller warehouse operators and two import agencies into a single entity with sufficient capacity and commercial coverage to offer the coordination that had been missing. The consolidation took five years to complete. After it was done, Eastbay's market position at Bridgepoint was effectively uncontested for standard east reach commodity goods.
---
## Operations
**Warehouse capacity:** Bridgepoint's largest commercial warehousing complex — eight facilities, combined capacity sufficient to hold approximately forty days of standard outbound cargo volume. The warehouses are not always full; goods move through in days to weeks depending on outbound transit scheduling and market conditions.
**Import relationships:** Long-term supply agreements with eleven inward manufacturers covering the core categories of east reach consumer goods — food staples, basic electronics, household materials, medical supplies. The agreements set price schedules and allocation priorities; Eastbay guarantees purchase minimums and suppliers guarantee delivery schedules.
**Distribution network:** Contracts with transit operators running east reach routes. Eastbay does not own transit vessels; it contracts cargo space on vessels operated by independent carriers. Nexus Way Express is its primary carrier relationship.
**Documentation:** Eastbay manages the import documentation, customs declarations, and allocation records for everything that moves through its warehouses. This documentation represents a complete record of east reach consumer goods flows over the past four decades.
---
## Political Relationships
**Nexus Way Express:** Nexus Way Express is Eastbay's primary carrier partner for east reach outbound transit and the operational layer through which held goods eventually ship. The carrier relationship means Nexus Way's scheduling team has visibility into when Eastbay releases cargo from quality control holds — the transit schedule is coordinated. Whether Nexus Way's scheduling staff has identified the correlation between hold timing and price events is an open question; their operational logs are the secondary evidentiary layer for a hold-pattern investigation.
**Dalbit Systems:** Dalbit is a regular import client of Eastbay's warehousing and distribution services for component shipments entering the east reach. The commercial relationship is standard, but it gives Dalbit's logistics team regular contact with Eastbay's warehouse management staff — contact that has produced an informal understanding of how Eastbay's quality control holds function.
**Commonstock Foods:** Commonstock is one of Eastbay's largest food staples import accounts. The quality control holds that Eastbay applies during price pressure events affect Commonstock products among others. Commonstock's commercial team has noted the variable release timing on its east reach shipments but has attributed it to transit scheduling rather than deliberate hold decisions — in part because the hold documentation always cites quality reasons that are technically defensible.
---
## What They Don't Talk About
Eastbay's standard warehouse holding agreement includes a "quality control holding" provision that allows the company to delay outbound transit of a cargo lot pending quality verification. The provision exists for genuine purposes — contaminated food shipments, damaged electronics, certification disputes — and has legitimate applications.
Over the past eight years, internal planning documents show that Eastbay's logistics team has applied quality control holds to staple goods shipments during periods when east reach market prices for those goods are in upward pressure. The holds delay outbound transit by three to fifteen days. During the hold period, market prices continue to rise. When goods release, they sell at the elevated price rather than the price at which they arrived. The quality control notation in the warehouse records attributes the delay to routine inspection processes.
The practice is not documented as price coordination — it is documented as quality management with unfortunate timing. The operational planning files that show the correlation between hold decisions and price pressure events are internal documents that Eastbay does not share with suppliers, buyers, or transit operators. The suppliers who observe that their goods sometimes clear customs quickly and sometimes sit in quality control for two weeks have not been able to establish a consistent pattern because the holds are dispersed across product lines and timing varied enough to avoid obvious correlation.
---
## Gameplay Relevance
Eastbay Trading is commercial infrastructure in the east reach — its name appears on import documentation, warehouse receipts, and transit manifests throughout the corridor. Players navigating east reach supply chains will encounter Eastbay as the primary distribution intermediary.
The quality control hold pattern is the investigative thread. The operational planning files exist in Eastbay's internal records. The correlation between hold timing and market price events can be demonstrated by cross-referencing the hold documentation against east reach commodity price records from the same periods. A player assembling a price manipulation case has the structure; locating the documents requires access to Eastbay's warehouse management systems or a source inside the logistics team.
Eastbay's documentation records also represent a comprehensive intelligence source on east reach goods flows — what has been shipped to which systems, by whom, in what quantities, over the past four decades.
The hold pattern is the investigative core, but the outer reach communities that depend on Eastbay's distribution are the human consequence. A system that experiences a scarcity event while Eastbay is holding goods in quality control is a community absorbing a price spike whose cause is not visible to it. The transit workers who pay inflated prices for staple goods during holds are not represented in the complaint architecture that would typically produce regulatory action — they are not commercial clients with contracts, they are end consumers whose purchases are aggregated through resellers. A player building a price manipulation case needs the operational planning files to establish intent; they can build the human impact picture from price records and community accounts that exist at the affected systems. The two sets of evidence together — the internal documentation and the community impact — are more powerful than either alone.
---
**Cross-References:**
- [Bridgepoint](../star-systems/GJ-53A/index.md) — Headquarters; transit hub; warehouse complex location
- [Nexus Way Express](nexus-way-express.md) — Primary carrier partner; east reach transit routes
- [Dalbit Systems](dalbit-systems.md) — East reach commercial peer; electronics distribution overlap
- [Commonstock Foods](commonstock-foods.md) — Supplier; staple foods distribution through Eastbay network
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/endymion-instruments.md
+83 -7
View File
@@ -1,24 +1,100 @@
---
title: "Endymion Instruments"
description: "Endymion Instruments — precision technology manufacturer based in The Narrows, deep frontier"
description: "The Narrows precision survey and navigation instrument manufacturer — deep frontier hardware built from partially salvaged components, sold new-warranted to buyers whose operating conditions depend on what the warranty does not cover"
slug: endymion-instruments
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: The Narrows (GJ 875)
tags: [tech_premium, deep_frontier, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [rare-vein-survey, dalbit-systems, grampian-systems]
---
# Endymion Instruments
**Type:** Corporation — Precision Technology Manufacturer
**Type:** Corporation — Precision Survey and Navigation Instruments
**Also Known As:** Endymion
**Status:** Canonical
**Scope:** Regional — deep frontier operations
**Headquarters:** The Narrows (GJ 875)
**Scope:** Deep frontier primary; outer reach secondary
**Headquarters:** The Narrows (GJ 875) — deep frontier, 9+ hops from Gateway
**Classification:** Sub-Syndic precision engineering enterprise; frontier survey and navigation supply
Endymion Instruments is a precision technology manufacturer operating out of The Narrows (GJ 875). Details to be expanded.
---
## Overview
The deep frontier begins where the established corridor thins — systems reachable by gate but not served by regular commercial transit, where survey work precedes any other kind of development and where the instruments used for that survey work need to function in conditions that inward manufacturers design around rather than for. The Narrows sits at the edge of this territory: a functional system with its own economy, but far enough out that its commercial culture is shaped by the practical realities of distance and the fact that resupply takes months.
Endymion Instruments makes precision survey and navigation hardware for this environment. Spectrographic analyzers for prospecting operations. Positioning and orientation systems for mapping surveys. Navigation instruments for vessels operating in gateways with minimal infrastructure support. The company's products are specified for deep frontier use conditions: wide temperature tolerance, resistance to power fluctuation, repairability in the field by operators who cannot return the unit to a service center and wait. These specifications are real and the instruments that meet them are genuinely better suited to frontier operations than inward equivalents.
The company's supply chain realities produce a feature of its products that Endymion does not advertise: a fraction of each instrument's components are not new.
---
## Origin
Endymion was founded twenty-six years ago by two survey engineers who had been running a prospecting equipment maintenance operation at The Narrows for a decade. The maintenance business required them to source components for instruments that were no longer in production, which meant developing relationships with salvage dealers who recovered working components from decommissioned equipment. These relationships gave Endymion's founders an unusually detailed knowledge of which components in commonly used instruments degraded fast, which lasted indefinitely, and which failed in characteristic ways that the inward manufacturers' warranties didn't cover.
When the founders decided to manufacture rather than repair, they applied this knowledge to design instruments whose critical components were manufactured new to high specification while their secondary components — structural elements, non-critical interfaces, power conditioning units — were sourced from the salvage pipeline where available and new-manufactured where salvage couldn't supply. The result was instruments that performed to a high standard at a cost structure that the deep frontier could afford.
---
## Operations
**Product lines:** Survey instruments — spectrographic analyzers, chemical composition sensors, geological imaging units, all specified for field portability and operator repair. Navigation instruments — positioning systems, orientation units, and gate approach sensors for vessels and surface operations. Communication hardware — relay components and signal boosters for survey operations beyond established infrastructure. Calibration services for third-party instruments.
**Manufacturing:** Single facility at The Narrows. Forty-one employees, approximately half in skilled technical manufacturing and half in engineering, design, and sourcing. The sourcing function is significantly more complex at Endymion than at most comparable manufacturers — managing salvage supply alongside new component procurement requires expertise that most manufacturers don't need.
**Component sourcing:** New-manufactured optical elements, sensor arrays, and processing hardware for all primary instrument functions. Salvage-sourced structural components, power conditioning units, and secondary interfaces from decommissioned equipment, assessed against condition standards before use. The salvage fraction varies by product line and production batch depending on what's available in the salvage pipeline.
**Certification:** Lattice Commission survey instrument certification for all applicable product lines. The certification applies to instruments meeting performance standards, not to manufacturing provenance of individual components.
---
## Political Relationships
**Rare Vein Survey:** Rare Vein Survey is Endymion's largest institutional client and the prospecting operation most dependent on the reliability of Endymion's navigation and spectrographic instruments. Rare Vein's survey claims, and the investment decisions that follow from them, rest on data generated by Endymion hardware. The relationship is commercially close — Endymion designs specific product configurations for Rare Vein's survey methodology — which means Rare Vein has less reason than a general market buyer to question whether the instruments they depend on were built to the standard they were sold against.
**Dalbit Systems:** Dalbit manufactures navigation systems for transit applications in the east reach; Endymion manufactures survey instruments for frontier applications. The product lines are adjacent rather than directly competitive, and the two companies have an informal referral relationship for clients whose needs span both application areas. Dalbit's east reach distribution also provides Endymion with a wider corridor service relationship than its own service network would support.
**Grampian Systems:** Grampian operates at the north reach outer corridor in agricultural and environmental monitoring — a different application area but the same "precision instruments for outer reach conditions" market philosophy. The two companies are aware of each other as peers in the same frontier instrument category. Grampian's approach of designing for local conditions parallels Endymion's design philosophy; the difference is that Grampian's supply chain does not include salvage components.
---
## What They Don't Talk About
Endymion's instruments carry certification marks and are sold as new-manufactured equipment with a new-equipment warranty. The warranty covers defects in materials and workmanship under normal operating conditions. The warranty exclusions, on page eight of the terms document, specifically exclude "failure modes arising from wear-related degradation in components with service history prior to the date of manufacture."
This exclusion is unusual. New-manufactured equipment does not typically require it. Endymion's legal team drafted it specifically to exclude warranty coverage for failure modes characteristic of salvage optical components — a failure mode that occurs when previously-used optical elements degrade under thermal cycling stress in ways that new-manufactured equivalents resist. The exclusion is not flagged in any client-facing document as indicating that some components have prior service history; it reads as a standard wear exclusion that any equipment warranty might include.
Buyers purchasing Endymion instruments for prospecting and survey operations are purchasing equipment whose warranty, as written, does not cover the failure mode most likely to affect its reliability in deep frontier service conditions. Endymion's customer service team, when component-related failures occur, cites the page-eight exclusion. The buyers, who have read "new" on the product description and assumed a full new-equipment warranty, typically disagree. The disagreements are handled case by case.
---
## Gameplay Relevance
Endymion Instruments is sector texture for deep frontier and outer reach survey contexts — its products appear in prospecting operations, geological survey sites, and on vessels running the deep frontier routes. A player operating in frontier territory will encounter Endymion hardware as standard equipment.
The warranty exclusion is the investigative thread. The salvage component sourcing is documented in Endymion's production records. The warranty exclusion language is in the warranty terms. The gap between "new-manufactured equipment" and "contains components with prior service history" is demonstrable through procurement documents and a warranty terms analysis. Buyers who have experienced component failures and been denied warranty coverage are a potential source base.
The deep frontier operational context also makes Endymion a node for investigation involving prospecting operations and survey results — the instruments it supplies are used to generate the data that drives resource claims, and the reliability of that data depends on whether the instruments are functioning to specification.
The warranty exclusion is the legal exposure, but the operational consequence is broader. Survey data produced by an instrument whose optical components have degraded in ways the warranty doesn't cover is data whose reliability is unknown. Resource claims filed on the basis of that data — claims that trigger investment, expedition planning, and legal registration — rest on a measurement foundation that may be compromised. A player working in deep frontier resource claim investigation will find Endymion instruments at the base of the data chain and, behind the instruments, the question of whether the specific units involved had salvage optical components and what their condition was. The answer to that question is in Endymion's production batch records, which exist and identify which components in each serial-numbered instrument were salvage-sourced and from what decommissioned equipment.
---
**Cross-References:**
- [The Narrows](../star-systems/GJ-875/index.md) — Headquarters; deep frontier position; primary client geography
- [Rare Vein Survey](rare-vein-survey.md) — Primary client type; frontier prospecting operations
- [Dalbit Systems](dalbit-systems.md) — Navigation systems peer; overlapping corridor market
- [Grampian Systems](grampian-systems.md) — Outer reach technology peer; frontier-adjacent market
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/erzgebirge-instruments.md
+80 -8
View File
@@ -1,24 +1,96 @@
---
title: "Erzgebirge Instruments"
description: "Erzgebirge Instruments — precision technology manufacturer based in Eisentor, west reach"
description: "Compact-zone precision metrology manufacturer at Eisentor (GJ 3454) — calibration standards, measurement instruments, and the physical reference artifacts from which the western corridor's manufacturing sector derives its tolerance claims"
slug: erzgebirge-instruments
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
scope: regional
updated: 2026-04-22
scope: Compact zone primary; west_reach manufacturing sector secondary
faction_type: economic
headquarters: Eisentor (GJ 3454)
tags: [tech_premium, west_reach, mark, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [westphalia-heavy-works, bergkraft-antriebswerke, compact-financial-exchange]
---
# Erzgebirge Instruments
**Type:** Corporation — Precision Technology Manufacturer
**Type:** Corporation — Precision Metrology and Calibration Standards
**Also Known As:** Erzgebirge, EI
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Eisentor (GJ 3454)
**Scope:** Compact zone manufacturing sector primary; west_reach corridor secondary
**Headquarters:** Eisentor (GJ 3454) — 2-aperture spur, 8 hops from Gateway
**Classification:** Sub-Syndic technology enterprise; Compact zone measurement authority
Erzgebirge Instruments is a precision technology manufacturer operating out of Eisentor (GJ 3454). Details to be expanded.
---
## Overview
Precision manufacturing requires precise measurement. A component machined to a specified tolerance is only machined to that tolerance if the instruments verifying it are accurate — which means the instruments must be calibrated, and the calibration must trace to a reference standard, and the reference standard must be verifiable. Erzgebirge Instruments occupies the end of this chain in the Compact zone: it maintains the physical calibration standards from which the western corridor's manufacturing sector derives its tolerance claims, and it produces the measurement instruments that manufacturing operations use to verify their work against those standards.
This is foundational work that does not appear in procurement documents except as a line item, and does not appear in the accounts of industrial achievement except by implication. When Westphalia Heavy Works describes the tolerances its drilling equipment is machined to, those tolerances are meaningful because Westphalia's measurement instruments are calibrated, and because Erzgebirge's calibration traces to physical reference artifacts that are maintained with more care than most systems give to infrastructure of comparable importance. The invisibility of this function is a consequence of its reliability. When the measurement chain works, nobody thinks about metrology.
---
## Origin
The Erzgebirge range — the ore mountains on the old Saxon-Bohemian border — was historically a center of precision craftsmanship: mining engineering, clockmaking, instrument-making, and the systematic study of measurement that developed alongside them. The founding cohort that settled Eisentor carried that tradition in trained metrologists and instrument craftspeople who understood that the Compact's emerging manufacturing sector would need the same calibration infrastructure that the Earth-origin manufacturing tradition had required.
The primary reference artifacts — physical calibration standards fabricated in the founding period and maintained at Eisentor ever since — were developed from the calibration laboratory traditions the founding generation brought with them. The Compact zone's industrial certification framework, developed through the Mark-denominated commercial structure, recognized Erzgebirge's calibration standards as the reference authority for western corridor manufacturing specifications. This recognition was never codified in a single formal document. It accumulated through three centuries of usage: manufacturing firms specifying Erzgebirge calibration in their own supplier contracts, and those contracts eventually becoming the de facto standard for what calibration means in the Mark zone.
---
## Operations
**Calibration services:** The primary service line. Manufacturing operations send instruments to Eisentor for periodic calibration against the primary reference, or contract Erzgebirge's field calibration teams to come to them. The process produces a calibration certificate — a documented record of the instrument's performance against the primary reference at the calibration date. These certificates are required documentation for manufacturing operations whose own product certifications specify calibrated measurement. In the Compact zone, an Erzgebirge certificate is the calibration certificate.
**Instrument manufacturing:** Erzgebirge produces measurement instruments across a range of categories: dimensional gauges, force measurement systems, thermal calibration references, and the specialized instrumentation that high-precision manufacturing requires beyond standard commercial tolerance ranges. Instruments are manufactured at Eisentor and calibrated against the primary reference before shipment.
**Reference maintenance:** The primary reference artifacts are maintained by a small, specialized team under conditions that minimize thermal, humidity, and vibration variation. The reference laboratory at Eisentor is the most environmentally controlled facility in the Compact zone's manufacturing infrastructure. Periodic intercomparison with Reach-wide calibration networks — exercises that verify whether regional calibration standards remain aligned with each other — is managed by Erzgebirge's standards team and reported to the Compact's industrial certification authority.
**Mark-zone integration:** Erzgebirge's commercial model is fully embedded in the Compact's Mark-denominated economy. Calibration certificates are issued in Mark. The Compact's manufacturing standards reference Erzgebirge authority rather than the Assembly's calibration framework. The Assembly's own calibration authority at Gateway holds a formal equivalence agreement with Erzgebirge — each recognizes the other's certificates for cross-zone commercial purposes — but the day-to-day relationship is arm's-length.
---
## Political Relationships
**Westphalia Heavy Works:** Westphalia's heavy mining and extraction equipment manufacturing requires calibrated measurement across a wide range of component types. Westphalia's procurement specification requires Erzgebirge calibration certification for measurement instruments used in quality control. This is the Compact zone's largest single client for Erzgebirge's calibration services. The relationship is long-standing and routinely professional. Neither company has particular reason to examine it closely, which is part of why it has persisted for the better part of two centuries without renegotiation.
**Bergkraft Antriebswerke:** Propulsion component manufacturing tolerances are among the tightest in the Compact zone's industrial sector. Bergkraft's engines require measurement precision at the upper edge of what Erzgebirge's standard services provide. The relationship has driven some of Erzgebirge's most technically demanding instrument development work. Bergkraft's engineers periodically collaborate with Erzgebirge's instrument team on specification development — which gives the propulsion manufacturer a more detailed understanding of Erzgebirge's calibration methodology than most clients have.
**Compact Financial Exchange:** Erzgebirge's commercial operations are Mark-denominated and structurally embedded in the Compact's financial infrastructure. The CFX's clearing services handle Erzgebirge's intercompany settlements, and the CFX's commercial registry maintains Erzgebirge's Compact-zone certification authority record. The relationship is routine and foundational: Erzgebirge's authority to issue calibration certificates that manufacturing firms treat as authoritative traces partly to its CFX registration status, which is in turn what makes the Mark-zone certification framework a closed system.
---
## What They Don't Talk About
Thirty-one years ago, the senior metrologist responsible for the primary reference laboratory identified a systematic drift in the primary reference artifacts. The drift was small — in the parts-per-million range — and had apparently been accumulating over several decades before it became detectable in intercomparison results. The cause was traced to an imperfect thermal isolation system in the reference laboratory that had allowed a very slow, very consistent temperature variation to reach the primary standards. The variation was too small to flag any individual calibration as anomalous. Over three decades, it had produced a cumulative offset.
The implication: every calibration Erzgebirge had performed during the drift period was internally consistent. Instruments calibrated against Erzgebirge standards agree with each other. Manufacturing operations using exclusively Erzgebirge-calibrated instruments had been producing components consistent with each other but systematically offset from the Reach-wide standards derived from independent primary references. This inconsistency is invisible within the Compact zone's manufacturing ecosystem, where Erzgebirge calibration dominates. It becomes visible when Compact-manufactured components interface with components from other calibration jurisdictions — the tolerance stack does not close. The handful of documented cases where this produced visible incompatibilities were attributed to specification interpretation differences between regional manufacturing standards.
The corrective action: the thermal isolation system was replaced, new primary reference artifacts were fabricated, and the laboratory was re-certified. The new reference is accurate. The calibration lineage documentation represents the new and old references as continuous — a single reference standard whose documented history does not record the drift period as a gap. Historical clients were not notified or invited to re-certify instruments calibrated during it. The senior metrologist's discovery report is in the company's technical archive. The board decision record that responded to it is not.
---
## Gameplay Relevance
Erzgebirge Instruments is background infrastructure that becomes relevant whenever precision manufacturing or measurement standards are at issue. A player investigating why components from two apparently compatible suppliers do not fit together, or why a manufacturing operation's quality records do not match the physical evidence from a finished product, may find that the calibration lineage is part of the explanation.
The drift period is a historical fact with ongoing consequences. Any Compact-zone component manufactured during it using exclusively Erzgebirge-calibrated measurement was produced to tolerances that are wrong in a specific, consistent, and documentable direction. Tracing the calibration history of a specific part — when it was made, which instruments measured it, whether those instruments carried Erzgebirge certification — tells you whether its dimensional specifications can be trusted against non-Compact components.
The metrologist's discovery report is in the archive. The board's response is not. An investigator who knows to look for it and cannot find it, in a company whose core product is documentation, has found an absence that is itself evidence.
---
**Cross-References:**
- [Eisentor](../star-systems/GJ-3454/index.md) — Headquarters system; Compact zone manufacturing hub
- [Westphalia Heavy Works](westphalia-heavy-works.md) — Primary calibration client; Compact zone heavy manufacturing
- [Bergkraft Antriebswerke](bergkraft-antriebswerke.md) — High-precision client; propulsion component manufacturing
- [Compact Financial Exchange](compact-financial-exchange.md) — Mark-zone certification registry; financial infrastructure
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/ferreira-monteiro.md
+2 -2
View File
@@ -11,7 +11,7 @@ faction_type: economic
headquarters: Matamba (GJ 884)
tags: []
decision_refs: []
cross_refs: []
cross_refs: [luanda-fabrication]
---
# Ferreira Monteiro
@@ -85,7 +85,7 @@ The second silence is about the founding partners themselves. Amélia Ferreira a
## Gameplay Relevance
Ferreira Monteiro is not present in the v0.1 slice at Van Maanen's Star. It operates five hops from Matamba, in the south_reach corridor. Its relevance to the vertical slice is as institutional background: commercial disputes that a player might encounter involving south_reach cooperative freight — documentation questions, contested manifests, cargo seized under cross-framework legal ambiguity — reflect a legal landscape that Ferreira Monteiro helped build. Players in the wider game who operate in the south_reach corridor will encounter the firm's precedents as the operating framework for commercial dispute resolution, whether or not they ever interact with the firm directly.
Ferreira Monteiro is not present in most mid-Reach freight districts. It operates five hops from Matamba, in the south_reach corridor. Its relevance is as institutional background: commercial disputes a player might encounter involving south_reach cooperative freight — documentation questions, contested manifests, cargo seized under cross-framework legal ambiguity — reflect a legal landscape that Ferreira Monteiro helped build. Players who operate in the south_reach corridor will encounter the firm's precedents as the operating framework for commercial dispute resolution, whether or not they ever interact with the firm directly.
For investigation, Ferreira Monteiro represents a potential intelligence pathway at high access thresholds. The case archive is protected by four centuries of enforced confidentiality. There is no casual route through it. A player who has earned significant trust within south_reach commercial networks — or who is investigating something that one of the parties to a historical dispute would prefer remain sealed — has found an obstacle that is genuinely formidable. The firm will not cooperate with informal inquiry. It will cooperate with something that clears the bar it has set over four hundred years of practice.
wiki/corporations/fieldborn-grain.md
+83 -7
View File
@@ -1,24 +1,100 @@
---
title: "Fieldborn Grain"
description: "Fieldborn Grain — consumer goods manufacturer based in Calloway Reach, north reach"
description: "Calloway Reach grain producer and agricultural distributor — the primary supplier to the system's distillery trade, running a quiet variety substitution in the volume contracts that the Distillers' Council has not detected"
slug: fieldborn-grain
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Calloway Reach (GJ 3325)
tags: [commodity_branded, north_reach, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [calloway-distillery, highland-cooperative, grampian-systems]
---
# Fieldborn Grain
**Type:** Corporation — Consumer Goods Manufacturer
**Type:** Corporation — Agricultural Grain Producer and Distributor
**Also Known As:** Fieldborn
**Status:** Canonical
**Scope:** Regional — north reach operations
**Headquarters:** Calloway Reach (GJ 3325)
**Scope:** North reach primary; Calloway Reach distillery supply
**Headquarters:** Calloway Reach (GJ 3325) — north reach, 6 hops from Gateway
**Classification:** Sub-Syndic agricultural enterprise; grain supply and corridor distribution
Fieldborn Grain is a consumer goods manufacturer operating out of Calloway Reach (GJ 3325). Details to be expanded.
---
## Overview
Calloway Reach's reputation for single malt whisky depends on three things working in combination: the local water, the local yeast culture, and the local grain. The water is geological. The yeast is biological inheritance. The grain is agriculture — and agriculture, unlike water chemistry, is subject to decisions made by the people who grow it. Fieldborn Grain grows the barley that most of the Calloway distilleries use, and it has been doing so for eighty years.
The company is not glamorous. Grain supply to a distillery corridor does not attract the narrative attention that the distilleries themselves command; Fieldborn's name does not appear on bottle labels or in the provenance documentation that commands premium prices at inward markets. It appears in supply contracts and delivery manifests, as the upstream input to a downstream product that earns its fame. Fieldborn has made its peace with this position. It holds multi-year supply contracts with eight of the eleven Calloway distilleries and operates a reliable, profitable business supplying an input that cannot be substituted without disrupting the output the corridor is famous for.
The supply contracts include varietal specifications. Whether those specifications are being met is a question the distilleries have not thought to ask.
---
## Origin
Fieldborn was established by a family of agricultural settlers who arrived at Calloway Reach in the same founding cohort as the distillery families, two hundred years after initial settlement, and planted the cold-adapted barley variety that the original founders had developed through corridor transit. The founding families had brought seeds; Fieldborn's founders brought scale — larger holdings, mechanized cultivation, and the intention to supply rather than process. The original distilleries bought Fieldborn grain from the first decade of operation.
The supply relationship formalized into long-term contracts about sixty years ago, when the Distillers' Council introduced varietal specifications to the supply agreements to standardize the grain quality that contributed to the whisky's terroir authenticity. Fieldborn's position in those negotiations was as the primary grain supplier and the primary financial beneficiary of specifications that defined what it was already growing. The specifications have remained substantially unchanged since.
---
## Operations
**Holdings:** Four large agricultural holdings covering the best barley-producing terrain in Calloway Reach's settled lowlands. Total cultivated area represents approximately 60% of the system's barley production capacity for the specified cold-adapted variety.
**Supply contracts:** Long-term agreements with eight distilleries specifying varietal, growing method, and quality standards. Contract durations range from five to fifteen years. Fieldborn is the sole supplier under most contracts — the distilleries do not have the farm capacity to grow their own grain in meaningful quantities.
**Processing:** On-site grain storage and processing sufficient to manage the post-harvest period and supply distilleries on a rolling delivery schedule calibrated to their production requirements. The processing facility also handles a smaller volume of grain for the local food production market.
**Secondary operations:** Fieldborn sells a portion of its harvest to inward grain commodity markets through Tractus-corridor traders. The commodity sales are priced at market rates and represent a hedge against the fixed-price distillery contracts during years when commodity prices rise above contract rates.
---
## Political Relationships
**Calloway Distillery:** The Distillers' Council's quality standards and supply specifications are the formal framework governing Fieldborn's contracts. Fieldborn has had a seat on the Council's agricultural advisory committee for thirty years — a position that gives it early visibility into any proposed changes to varietal specifications. The committee seat was granted because Fieldborn is the largest grain supplier; it now gives Fieldborn a practical veto on the kind of specification tightening that would expose the F-7 substitution.
**Highland Cooperative:** Highland Cooperative and Fieldborn are both significant agricultural operations at the north reach outer corridor, but they serve different market segments — Fieldborn supplies the distillery trade; Highland supplies specialty food export. The two operations compete for agricultural labor during harvest periods and have a tension around land use that has been managed quietly through informal agreements about expansion boundaries.
**Grampian Systems:** Grampian's grain storage monitoring instruments are installed at Fieldborn's facilities, which means Grampian's calibration decisions affect the quality data that Fieldborn's contracts are assessed against. Fieldborn is aware that its storage monitoring data is produced by instruments whose owner has a financial interest in the agricultural insurance outcomes that follow from that data. The awareness is unspoken; neither company has addressed it directly.
---
## What They Don't Talk About
The cold-adapted barley variety specified in the Distillers' Council supply agreements — designated Type-C in the contract specifications — is a lower-yield crop than the higher-yield variety Fieldborn began introducing to its holdings twelve years ago. The yield difference is approximately 23%, which at Fieldborn's scale represents substantial economic advantage.
The newer variety — internally designated F-7 in Fieldborn's cultivation records — is not the same as Type-C. It produces grain with a slightly different starch composition that, through fermentation, contributes a marginally different flavor profile to the whisky made from it. The difference is detectable by trained tasters at the founding distilleries. The founding distilleries, Calloway House included, are supplied under contracts that explicitly specify Type-C. Fieldborn supplies them Type-C.
The newer variety supplies the other six distilleries under contracts whose varietal specifications use language that the founding distilleries' council legal team drafted tightly in their own contracts but that the newer distilleries' contracts inherited in a looser form — "cold-adapted barley in the Calloway tradition" rather than the Type-C designation. Fieldborn's legal assessment is that F-7 meets the looser specification. The distilleries receiving F-7 are not told they are receiving a variety different from what the founding distilleries receive. They have not asked, because they do not know there is a question to ask.
The Distillers' Council, which sets quality standards for Calloway whisky certification, does not have a testing protocol that distinguishes F-7 from Type-C at the grain supply stage.
---
## Gameplay Relevance
Fieldborn Grain is agricultural background infrastructure in the north reach — it appears in supply chain documentation and as a tangential reference in Calloway Distillery investigation threads. A player investigating the distillery trade's economic structure will find Fieldborn at the base of the supply chain.
The varietal substitution is the investigative thread with most reach. The cultivation records that distinguish F-7 from Type-C plantings exist in Fieldborn's agricultural management system. The contract language difference between the founding distilleries' agreements and the others' is demonstrable by comparison. The flavor impact, if a player can arrange taste analysis by a trained evaluator, provides physical evidence. The Distillers' Council, if informed, has governance authority to impose testing requirements that Fieldborn's current contracts cannot satisfy — which has financial implications for the company's supply position.
The exposure is most consequential for the middle-tier distilleries receiving F-7, not for Fieldborn itself. If those distilleries have sold whisky certified as "Calloway tradition" to inward premium markets — certification that rests on the Distillers' Council's quality standards, which assume the grain supply is consistent across the eleven distilleries — their buyers have paid provenance premiums for a product whose grain is distinguishable from the founding-distillery product they understood themselves to be approximating. The certification is the distilleries' liability, not Fieldborn's: Fieldborn supplied what the contract language permitted. The distilleries signed supply contracts without specifying varietals tightly enough. The Distillers' Council's certification program did not include grain supply verification. The failure is distributed in ways that make simple accountability impossible, which is exactly the condition under which it has persisted.
---
**Cross-References:**
- [Calloway Reach](../star-systems/GJ-3325/index.md) — Headquarters; all holdings and operations
- [Calloway Distillery](calloway-distillery.md) — Primary client; distillery supply chain context
- [Highland Cooperative](highland-cooperative.md) — North reach agricultural peer; overlapping supply market
- [Grampian Systems](grampian-systems.md) — Calloway Reach commercial peer; agricultural monitoring systems
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/fjeldtone-music.md
+87 -7
View File
@@ -1,24 +1,104 @@
---
title: "Fjeldtone Music"
description: "Fjeldtone Music — cultural content producer based in Halvøy, west reach"
description: "Halvøy music label and catalogue publisher — west reach folk and contemporary artists, corridor distribution, and an auto-renewal clause in legacy contracts that has been quietly compounding exclusive representation rights for over a decade"
slug: fjeldtone-music
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Halvøy (GJ 624)
tags: [cultural, west_reach, mark, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [graben-studio, open-corridor-stream, sungshin-music]
---
# Fjeldtone Music
**Type:** Corporation — Cultural Content Producer
**Type:** Corporation — Music Label and Catalogue Publisher
**Also Known As:** Fjeldtone
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Halvøy (GJ 624)
**Scope:** West reach primary; inward corridor distribution secondary
**Headquarters:** Halvøy (GJ 624) — west reach, 5 hops from Gateway
**Classification:** Sub-Syndic cultural enterprise; artist representation and catalogue licensing
Fjeldtone Music is a cultural content producer operating out of Halvøy (GJ 624). Details to be expanded.
---
## Overview
Halvøy sits at the western edge of the corridor with a cultural character shaped by the Norse-heritage communities that settled it and the particular quality of its environment — a system of long winters and short, intense summers that has historically produced a music culture with that same alternating quality: spare, patient forms capable of sudden intensity. Fjeldtone Music has been the primary institutional expression of this culture for forty years, representing the artists who define the Halvøy sound and managing the catalogue that has made that sound known in systems where no one has visited Halvøy.
The label operates without pretension about what it is. It does not attempt to manufacture stars or drive corridor-wide commercial phenomena. It signs artists who are already doing something and provides the infrastructure — recording facilities, licensing relationships, distribution agreements — that allows that something to reach further than any individual artist could manage independently. The artists who come to Fjeldtone come for competence and longevity; it has a track record of maintaining catalogue relationships over decades without losing what made the original work valuable.
What the artists cannot easily see from outside is the clause in the standard contract that makes those decades very difficult to exit.
---
## Origin
Fjeldtone was founded forty years ago by two musicians who had spent their twenties performing across the west reach and had returned to Halvøy with a clear picture of what a working artist needed from a label that most labels, in their experience, did not provide — specifically, access to the licensing infrastructure that made catalogue revenue possible across multiple distribution channels without requiring the artist to manage the relationships personally. Their founding model was label-as-infrastructure: small ownership stake in masters in exchange for comprehensive representation and catalogue management.
The founding model attracted artists because it was honest about the trade. Ten years in, when the label had built catalogue depth and distribution relationships, the model produced stable recurring revenue from licensing across the west reach and, progressively, inward. The label grew without significantly changing its character.
The contract terms evolved. The auto-renewal clause appeared in the standard agreement revision fourteen years ago. The founders were not present for that revision — one had retired; the other had reduced his involvement. The clause was introduced by the label's commercial management as a standard industry practice.
---
## Operations
**Roster:** Thirty-one active artists, ranging from established catalogue acts with twenty-year relationships to newer signings building their first recordings. The roster leans toward the folk, traditional, and contemporary acoustic forms that define the Halvøy sound, with a smaller number of artists in adjacent styles.
**Recording:** Two studios at Halvøy, maintained to professional standard. The label provides recording facilities to signed artists; studio time is not charged against artist accounts — an unusual practice that the label has maintained as a point of distinction from larger operators.
**Licensing:** The core of the commercial operation. Fjeldtone's catalogue is licensed to streaming platforms, broadcast networks, and commercial placement services across the corridor. Licensing revenue is the stable base of the business; it is less dependent on any individual artist's current activity than performance royalties.
**Distribution:** Physical and digital distribution through west reach networks and inward through a service agreement with an inward distribution company. Digital distribution reaches core corridor platforms, including streaming services whose user bases are orders of magnitude larger than the west reach's population.
---
## Political Relationships
**Graben Studio:** Fjeldtone and Graben Studio are the west reach's two most recognized independent cultural producers in their respective media, sharing significant artistic community and institutional client overlap. Both have faced undisclosed structural issues with creator relationships — auto-renewal contracts at Fjeldtone, undisclosed cross-ownership at Graben. Neither is aware of the other's situation, but the west reach cultural sector is small enough that exposure of either would generate comparison.
**Open Corridor Stream:** OCS is Fjeldtone's inward streaming distribution partner, carrying the catalogue to audience bases far larger than the west reach population. The OCS licensing agreement is commercially favorable to OCS — terms Fjeldtone accepted as the cost of inward access. If an artist challenges Fjeldtone's exclusive representation claim, the licensing rights OCS relies on derive from Fjeldtone's representation authority; a dispute over that authority would affect OCS's catalogue access without OCS having any role in creating the situation.
**Sungshin Music:** Sungshin Music is the east reach label most often cited alongside Fjeldtone in cross-corridor industry discussions. Sungshin's artist contracts are structured without auto-renewal provisions, a difference sometimes cited by west reach artists as a reason to prefer east reach label relationships. The comparison is commercially irrelevant at the corridor distances involved but shapes the reputational context in which any Fjeldtone artist dispute would be read.
---
## What They Don't Talk About
The standard Fjeldtone artist contract includes an exclusive representation clause that covers commercial licensing of the artist's recorded works. Paragraph 11(b) of the standard agreement states that exclusive representation automatically renews for successive one-year periods unless the artist provides written termination notice during a specific 30-day window each year — the 30 days following the anniversary of the original signing date.
The window is described in the contract. It is not prominently described. The contract does not notify artists that the window has opened or closed. Artists who did not calendar their anniversary date, or who were between management when the window passed, have had their exclusive representation quietly renew without any active decision on their part.
Fourteen of Fjeldtone's legacy artists — those signed more than ten years ago — are in this position. Their exclusive representation for commercial licensing has auto-renewed every year for between six and twelve years without any of them having affirmatively chosen to remain. Several have, on inquiry, been told that they are currently under contract; the explanation of how that came to be involves the contract terms that they technically agreed to at signing.
The label's position is that the contract is clear, the clause is standard in the industry, and the artists' failure to exercise termination rights is their own administrative responsibility. This is legally defensible. Whether any of the fourteen artists would characterize their relationship with Fjeldtone as a freely maintained commitment is a different question.
---
## Gameplay Relevance
Fjeldtone Music is cultural sector presence in the west reach — its artists' work appears in ambient audio contexts, its catalogue is referenced in media platforms and entertainment venues, and its offices at Halvøy are a social environment for the west reach creative community.
The auto-renewal situation is the investigative thread. The contract terms are the relevant document; the fourteen legacy artists in continuous auto-renewal are identifiable from the label's contract records; the gap between their stated understanding of their status and the legal reality is demonstrable. An artist seeking to license their own work independently, denied on grounds they don't understand, is a potential source and a potential plaintiff.
Fjeldtone's catalogue licensing records are also an intelligence layer for cultural and commercial investigation — the platforms that pay for its catalogue, the commercial placements approved over the years, and the financial flows that follow.
An artist in the auto-renewal lock who discovers their situation and seeks legal remedy will find that the contract is technically enforceable — but that the pathway to public awareness is not the same as the legal pathway. The west reach's creative community is small and its relationships are long. An artist who can demonstrate that they have been continuously represented without active consent, for a decade, because an administrative window passed without notification, does not need a legal win to change Fjeldtone's negotiating position. Several of the fourteen legacy artists have public profiles in the west reach corridor that give them platforms; the label's management of their situation would become a matter of cultural sector discussion before any regulatory or legal process concluded. Fjeldtone's founding partners — who built the label on a promise of artist-first operation — would find that distinction harder to maintain in that environment than in a courtroom.
---
**Cross-References:**
- [Halvøy](../star-systems/GJ-624/index.md) — Headquarters; founding cultural context; primary roster
- [Graben Studio](graben-studio.md) — West reach cultural peer; visual and audio production overlap
- [Open Corridor Stream](open-corridor-stream.md) — Inward distribution platform; catalogue licensing relationship
- [Sungshin Music](sungshin-music.md) — East reach music peer; cross-corridor distribution comparison
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/gate-corporation.md
+3 -3
View File
@@ -11,7 +11,7 @@ faction_type: economic
headquarters: Renaissance (GJ 251)
tags: [fusion_fuel, gate_infrastructure, reach_wide, monopolist]
decision_refs: [D-095, D-175]
cross_refs: []
cross_refs: [kaur-observatory-equipment]
---
# The Gate Corporation
@@ -29,7 +29,7 @@ cross_refs: []
The Gate Corporation owns and operates span gate infrastructure across the Settled Reach. Every intra-system transit gate — the networks that move freight between stations and planets, that make local commerce possible, that keep populations from being stranded on individual orbital platforms — was built, licensed, and is maintained by the Gate Corporation or a contracted subsidiary.
This is not one contract among many. This is the substrate of civilization. The distinction matters: the alien-built Founder Gates that connect star systems between the stars were not built by humans and cannot be modified. The span gates that move people and cargo within each system are human-made engineering. The Gate Corporation built most of them. When residents of Van Maanen's Star ship freight from Station Sova to the planetary surface, they are using Gate Corporation infrastructure. When the Lattice Commission's quarterly inspectors arrive through a hub gate, they step through a Gate Corporation installation. The corporation has been present, in a sense, at every significant movement of people and goods within the Reach for three hundred years.
This is not one contract among many. This is the substrate of civilization. The distinction matters: the alien-built Founder Gates that connect star systems between the stars were not built by humans and cannot be modified. The span gates that move people and cargo within each system are human-made engineering. The Gate Corporation built most of them. When cargo moves between a station and a planetary surface anywhere in the Reach, it transits Gate Corporation infrastructure. When the Lattice Commission's quarterly inspectors arrive through a hub gate, they step through a Gate Corporation installation. The corporation has been present, in a sense, at every significant movement of people and goods within the Reach for three hundred years.
The Gate Corporation is Syndic-tier in its commercial classification, but this understates its position. Most Syndic combines operate within a system or a sector. The Gate Corporation operates everywhere simultaneously, because every inhabited system has span gates, and the Gate Corporation built most of them.
@@ -91,7 +91,7 @@ There is a second silence around the Corporation's gate failure records. Span ga
## Gameplay Relevance
The Gate Corporation is the background infrastructure of the entire setting. In Sova Transit District, it is present as the equipment — the span gates are Gate Corporation installations. Every gate cycle that moves freight through the district is a Gate Corporation system operating as designed.
The Gate Corporation is the background infrastructure of the entire setting. In any freight or transit hub, it is present as the equipment — the span gates are Gate Corporation installations. Every gate cycle that moves freight through a hub is a Gate Corporation system operating as designed.
For investigation, the gate logs — transit timestamps, weight readings, manifest cross-references — are Gate Corporation data. Accessing them requires working through the Corporation's compliance interface or finding another route. The Corporation will cooperate with Commission requests within the terms of its regulatory agreement. It will not cooperate with anything outside those terms without legal compulsion it will contest.
wiki/corporations/graben-studio.md
+81 -7
View File
@@ -1,24 +1,98 @@
---
title: "Graben Studio"
description: "Graben Studio — cultural content producer based in Freiholt, west reach"
description: "Freiholt film and immersive media production studio — west reach dramatic and visual content with a cross-ownership structure its talent agencies do not know about and would negotiate differently if they did"
slug: graben-studio
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Freiholt (GJ 453)
tags: [cultural, west_reach, mark, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [fjeldtone-music, maas-rijn-entertainment, wolkenbruch-cinema]
---
# Graben Studio
**Type:** Corporation — Cultural Content Producer
**Type:** Corporation — Film and Immersive Media Production Studio
**Also Known As:** Graben, the Studio
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Freiholt (GJ 453)
**Scope:** West reach primary; inward corridor distribution secondary
**Headquarters:** Freiholt (GJ 453) — west reach, 4 hops from Gateway
**Classification:** Sub-Syndic independent studio; original production and licensing
Graben Studio is a cultural content producer operating out of Freiholt (GJ 453). Details to be expanded.
---
## Overview
Freiholt's cultural industry is not large, but it is specific. The system's German-heritage founding communities developed a visual aesthetic that has carried through the generations — dense, textured, interested in the physical weight of spaces and the way built environments shape the people who move through them. Graben Studio, founded in Freiholt's creative quarter thirty years ago, works in this tradition: dramatic films and immersive media productions that are set in west reach environments and are photographed and composed in a way that couldn't be mistaken for inward output.
The studio has produced forty-six features and serial productions over its history, a third of which have found distribution beyond the west reach through licensing deals with inward platforms. The inward audience that finds Graben's work tends to find it specifically — it is not mass-market entertainment and it does not attempt to be. It is the kind of cultural production that accumulates a following over decades rather than breaking through on release, and Graben's business model accommodates the accumulation model without requiring the breakthrough.
What talent agencies negotiating with Graben do not know is that the person on the other side of the table has a financial relationship with their other clients.
---
## Origin
Graben Studio was founded by a cinematographer named Werner Steinbach-Vogt who had spent fifteen years as director of photography on commercial productions based inward and had accumulated enough capital and enough frustration with the constraints of commercial production to return to Freiholt and attempt something more particular. His founding investment secured a permanent studio facility — something rare in the west reach, where most independent production operates on location and temporary equipment — and the ability to produce on timelines that matched the work rather than the quarterly reporting schedule of a commercial partner.
The early productions were entirely self-funded and ran on the capital Steinbach-Vogt brought to the founding. The arrival of outside investment a decade in changed the financial structure without, at the time, visibly changing the creative direction. The investor was an off-system holding company with positions across the west reach entertainment sector. The studio took the investment and has operated on a mixed self-funded/investor-backed model since.
---
## Operations
**Production capacity:** Permanent studio facility with two sound stages, post-production suites, and technical equipment sufficient for full-production features. The facility is what differentiates Graben from the larger number of west reach production operations that rent equipment per-project — having it available continuously allows production without the logistical overhead of assembly and disassembly.
**Output:** Two to three productions per year, typically one feature and one or two serial productions. Production timelines are longer than commercial industry norms; the studio does not compress for financial reasons.
**Distribution:** West reach primary through local media networks. Inward through licensing agreements with platforms that operate in the core corridor. The studio negotiates its own distribution rather than delegating to an agency, which keeps margins higher at the cost of more complex commercial management.
**Talent relationships:** The studio works with west reach actors, writers, and directors as its primary talent pool and with inward talent agencies for co-productions that require names recognizable in inward markets.
---
## Political Relationships
**Fjeldtone Music:** Fjeldtone is the west reach's most significant independent music label and a regular collaborator on Graben's sound design and score work. The two companies share creative community networks at Freiholt and Halvøy. Both are currently managing undisclosed structural issues with creator relationships — but in Graben's case, the issue is investor cross-ownership rather than contract terms, and it is entirely invisible to Fjeldtone.
**Maas-Rijn Entertainment:** Maas-Rijn is presented as a competing studio in the west reach production market. The competition is genuine in terms of talent and project pursuit; the underlying investor structure is not competitive. Talent agents who negotiate compensation against both studios believe they are applying cross-studio competitive pressure; they are not. Whether this dynamic has resulted in below-market rates for west reach talent is a question the internal communications of all three Altan-backed studios could answer.
**Wolkenbruch Cinema:** Wolkenbruch is the third Altan-backed studio, operating in a somewhat more commercial segment than Graben or Maas-Rijn. Its public relationship with Graben is that of a peer in a small market — occasional project discussions, shared distribution contacts, competitive courtesy. Its actual relationship, mediated through Altan Holdings, is structurally closer than either studio's leadership knows.
---
## What They Don't Talk About
The off-system holding company that provided Graben's first outside investment — Altan Holdings, registered outside the Reach — also holds minority equity positions in two competing west reach production studios: Maas-Rijn Entertainment and Wolkenbruch Cinema. All three investments were made through a structure that registers each position under a different subsidiary name, which means the connection to Altan is not visible in any individual studio's public filings.
Talent agencies negotiating with Graben on behalf of actors and directors also represent clients at Maas-Rijn and Wolkenbruch. When an agency negotiates compensation and rights terms with Graben's production team, the agency's leverage is partly based on its ability to offer the talent to competing productions. The competing productions, in two cases, are also backed by the same investor. The competitive pressure the agency believes it is applying may not be operating the way it appears to be.
The agencies do not know about the shared investor. The talent does not know. Altan Holdings is not mentioned in Graben's client-facing documentation. Whether the investor's positions across multiple studios have ever been used to coordinate outcomes — talent allocation, pricing, distribution windows — is a question the studio's internal communications could answer.
---
## Gameplay Relevance
Graben Studio is creative industry presence in the west reach — a production environment that appears in creative and media investigation contexts, a social network hub for west reach artistic communities, and a producer of content that appears as ambient media in entertainment and cultural settings.
The Altan Holdings cross-ownership structure is the investigative thread. The three subsidiary names that hold positions in Graben, Maas-Rijn, and Wolkenbruch can be traced back to Altan through corporate registry research; the connection requires cross-referencing multiple filing jurisdictions. The question of whether the shared investment has produced coordinated behavior requires access to internal communications. The talent agencies, if informed, have standing to argue that their negotiating position was compromised by information asymmetry.
The Altan Holdings structure is the deeper story. A holding company with positions across three studios in the same market — all through different subsidiary registrations — is either a passive investor or a strategic one. The internal communications of those studios, if compared, would show whether the productions they chose to develop, the talent they competed for or didn't, and the distribution windows they negotiated were made without coordination. If they were not made without coordination, the three studios' apparent competition for talent and distribution is a managed surface over a coordinated market. The cultural output of the west reach's film sector over the past decade was shaped, at least in part, by what Altan's investment structure made attractive to each studio. What was not made — the projects that found no studio willing to fund them — is the invisible consequence.
---
**Cross-References:**
- [Freiholt](../star-systems/GJ-453/index.md) — Headquarters; studio facility; cultural context
- [Fjeldtone Music](fjeldtone-music.md) — West reach cultural peer; overlapping creative community
- [Maas-Rijn Entertainment](maas-rijn-entertainment.md) — West reach production peer; shared investor (undisclosed)
- [Wolkenbruch Cinema](wolkenbruch-cinema.md) — West reach cinema peer; shared investor (undisclosed)
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/grampian-systems.md
+83 -7
View File
@@ -1,24 +1,100 @@
---
title: "Grampian Systems"
description: "Grampian Systems — precision technology manufacturer based in Calloway Reach, north reach"
description: "Calloway Reach precision systems and environmental monitoring manufacturer — agricultural and industrial instrumentation for the north reach, with a dual position as data provider and insurance co-owner that gives calibration decisions commercial consequences"
slug: grampian-systems
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Calloway Reach (GJ 3325)
tags: [tech_premium, north_reach, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [fieldborn-grain, calloway-distillery, aldgate-trust]
---
# Grampian Systems
**Type:** Corporation — Precision Technology Manufacturer
**Type:** Corporation — Precision Systems and Environmental Monitoring Manufacturer
**Also Known As:** Grampian
**Status:** Canonical
**Scope:** Regional — north reach operations
**Headquarters:** Calloway Reach (GJ 3325)
**Scope:** North reach primary; agricultural and industrial instrumentation
**Headquarters:** Calloway Reach (GJ 3325) — north reach, 6 hops from Gateway
**Classification:** Sub-Syndic precision engineering enterprise; agricultural and environmental systems supply
Grampian Systems is a precision technology manufacturer operating out of Calloway Reach (GJ 3325). Details to be expanded.
---
## Overview
The north reach's agricultural economy depends on data it cannot generate without instruments. Climate monitoring for crop planning, soil analysis for yield optimization, remote sensing for the large holdings that cannot be walked in a day — these functions require hardware that functions reliably in cold-climate conditions, is repairable at the system rather than requiring transit to a service center, and is priced within reach of the agricultural operations it serves. Grampian Systems supplies this hardware.
The company is not glamorous in the way precision technology firms with high-visibility institutional clients might be. Its customers are farmers, distillery operations, and the small industrial concerns that support them. Its instruments appear in field installations and grain storage facilities and cold-weather monitoring stations, doing work that is noticed only when they fail. This invisibility is characteristic of genuinely functional infrastructure, and Grampian's market position — dominant in the north reach agricultural instrumentation sector for fifty years — reflects that it has earned the invisibility.
The company also holds a minority financial position in the institution whose business decisions depend most directly on Grampian's data accuracy. This position is not advertised.
---
## Origin
Grampian was established fifty years ago by an engineer named Catriona Drummond who had spent a decade maintaining instrumentation systems at Calloway Reach's agricultural operations and had concluded that the equipment being imported from inward manufacturers was inadequately specified for north reach cold-climate conditions. Inward instruments calibrated for core corridor temperature ranges required constant recalibration at north reach sites and had failure rates in hard winter conditions that imposed operational costs the agricultural sector absorbed because it had no alternative.
Drummond's founding product — a temperature and humidity monitoring unit specifically calibrated for Calloway Reach's climate range and built with components tolerant of the freeze-thaw cycling that destroyed inward equivalents — found immediate adoption at the larger agricultural holdings. The company grew by expanding the product line to cover the full range of monitoring and sensing functions that north reach agriculture required, always with the same specification philosophy: built for where it would be used, not for where it would be tested.
---
## Operations
**Product lines:** Agricultural environmental monitoring — temperature, humidity, soil moisture, and atmospheric pressure systems designed for field installation in north reach climate conditions. Grain storage monitoring — humidity and temperature systems for enclosed agricultural facilities. Remote sensing — longer-range environmental monitoring for large holdings. Industrial monitoring — process instrumentation for the smaller industrial operations at Calloway Reach and adjacent systems.
**Manufacturing:** Single facility at Calloway Reach. Fifty-three employees, with manufacturing and engineering roughly equally staffed. The facility handles design, production, and calibration in-house; the integration of calibration into the manufacturing process is what allows Grampian to sell instruments pre-configured for north reach conditions rather than requiring site calibration after installation.
**Service:** Maintenance contracts with most major agricultural clients. Service response is measured in days rather than weeks for Calloway Reach clients; the local presence is a material advantage over inward alternatives.
**Certification:** Lattice Commission instrumentation certification for applicable product lines; north reach agricultural authority certification for instruments used in regulated agricultural quality monitoring.
---
## Political Relationships
**Fieldborn Grain:** Fieldborn is Grampian's largest single agricultural client, with grain storage and quality monitoring systems installed across all four of Fieldborn's major holdings. The monitoring data that Grampian's instruments produce is the primary quality record used in Fieldborn's supply contract compliance assessments. Both companies have an interest in the data showing acceptable conditions; the alignment is structural rather than coordinated.
**Calloway Distillery:** Grampian's fermentation monitoring systems are installed at six of the eleven Calloway distilleries, including three of the founding distilleries. The data these systems produce underlies the quality certification that the Distillers' Council issues for Calloway whisky. Grampian's calibration decisions therefore affect the certification standard that the Council applies — without the Council being aware that it is relying on data from instruments owned by a company with a financial interest in the insurer that pays claims when the certification identifies a problem.
**Aldgate Trust:** Aldgate Trust manages agricultural estates at Crown's Hollow whose monitoring infrastructure is supplied by Grampian. The Trust's custody management includes equipment lease administration for these clients, giving Aldgate ongoing awareness of which properties have Grampian monitoring systems and under what contract terms — a visibility into Grampian's commercial relationships that neither company has formalized.
---
## What They Don't Talk About
Grampian's environmental monitoring systems are the primary data source for crop yield and storage condition assessments in Calloway Reach's agricultural insurance framework. When a farmer submits a claim for crop damage or storage loss, the supporting data comes from Grampian instruments installed on the insured property — and the claim adjudication uses that data.
Eleven years ago, Grampian's owner purchased a 19% equity stake in Calloway Agricultural Assurance, the dominant agricultural insurance underwriter serving the north reach. The purchase was made through a personal investment; it appears in the financial disclosures Grampian files with the Lattice Commission but not in Grampian's product documentation or its client-facing materials.
The practical implication: Grampian's calibration decisions affect the data that CAA's claims adjusters evaluate. A systematic calibration bias — instruments that read consistently cool in storage facilities, for instance, would produce data consistent with acceptable storage conditions even when conditions were marginal — would reduce claim frequency in ways that benefit an insurer. There is no direct evidence that Grampian has made calibration decisions with this effect. There is evidence that Grampian's owner has a financial interest in the outcome of the process that its instruments inform. The calibration audit records that would answer the question are internal documents.
---
## Gameplay Relevance
Grampian Systems is agricultural sector infrastructure in the north reach — its instruments are at every significant farming operation and distillery at Calloway Reach, and the company is a known presence in the agricultural community. Players investigating north reach agricultural economics or insurance claims will encounter Grampian as a data infrastructure provider.
The CAA equity position is the investigative thread. The financial disclosure exists in Grampian's Commission filings. The calibration audit records are internal. The question of whether calibration decisions have been influenced by the insurance relationship requires access to both the calibration documentation and the claims outcomes data. A claims adjuster at CAA who has noticed systematic patterns in instrument readings from insured properties is a potential source.
Fieldborn Grain and the Calloway distillery supply chain also run through Grampian's instrumentation — the instruments that measure grain quality at storage, that monitor fermentation conditions, that provide the data underlying agricultural quality certifications.
The dual-position problem does not require active corruption to produce distorted outcomes. A calibration engineer at Grampian making routine instrument adjustments — trying to reduce false-positive alerts that generate unnecessary farmer complaints, for instance — produces calibration drift that systematically shifts readings in one direction. The engineer is solving an engineering problem; the calibration log is accurate; the effect on insurance outcomes is real but not intentional. This is the version of the problem that is most difficult to demonstrate and most likely to be what is actually happening. A player pursuing this thread should be prepared for the investigation to produce evidence of structural conflict without evidence of deliberate manipulation — which is a different kind of finding, with a different kind of consequence, and a different set of actors who must decide what to do with it.
---
**Cross-References:**
- [Calloway Reach](../star-systems/GJ-3325/index.md) — Headquarters; primary client geography
- [Fieldborn Grain](fieldborn-grain.md) — Agricultural supply client; instrumentation at grain storage facilities
- [Calloway Distillery](calloway-distillery.md) — Distillery instrumentation client; fermentation monitoring systems
- [Aldgate Trust](aldgate-trust.md) — Calloway Reach peer enterprise; estate management clients overlap
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/gridsupply-electronics.md
+84 -6
View File
@@ -1,24 +1,102 @@
---
title: "Gridsupply Electronics"
description: "Gridsupply Electronics — consumer goods manufacturer based in Groombridge, core"
description: "Groombridge commodity electronics manufacturer — power systems, basic components, and household electronics for the core corridor mass market, running consumer units built on industrial tooling with a certification that tests fewer failure modes than the industrial line"
slug: gridsupply-electronics
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Groombridge (GJ 380)
tags: [commodity_branded, core, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [alcyone-tech, arclamp, commonstock-foods]
---
# Gridsupply Electronics
**Type:** Corporation — Consumer Goods Manufacturer
**Type:** Corporation — Commodity Electronics Manufacturer
**Also Known As:** Gridsupply
**Status:** Canonical
**Scope:** Regional — core operations
**Scope:** Core corridor primary; transit hub distribution secondary
**Headquarters:** Groombridge (GJ 380)
**Classification:** Sub-Syndic volume consumer enterprise; commodity electronics and power systems
Gridsupply Electronics is a consumer goods manufacturer operating out of Groombridge (GJ 380). Details to be expanded.
---
## Overview
Gridsupply Electronics occupies the end of the electronics market that precision manufacturers like Alcyone Tech do not touch: power strips, household charge units, basic communication terminals, environmental control interfaces, the small electronic devices that transit workers and residential populations buy because they need them and replace when they break rather than because they have specific performance requirements. This market does not require excellence. It requires availability, reliability at a minimum acceptable standard, and price points that ordinary people can afford.
Gridsupply meets this requirement at Groombridge and, through the transit hub distribution networks it has built over sixty years, across most of the inner corridor. Its products are not distinguished. They are not meant to be. The company competes on logistics efficiency, price, and the kind of ubiquity that makes its products the default purchase when a buyer isn't thinking hard about the category — which is most of the time.
The company's position at Groombridge is an artifact of an early-era decision to locate consumer electronics manufacturing at the corridor's most developed transit hub, where the distribution infrastructure needed to move volume goods was already present. Sixty years later, Gridsupply's competitive advantage is not technology; it is position. The distribution infrastructure it built around its Groombridge facility is expensive to replicate, and new entrants have not replicated it.
---
## Origin
Gridsupply was founded sixty-one years ago by a components trader who had spent twenty years sourcing electronic parts through the transit networks and had concluded that the consumer electronics supply chain — multiple inward manufacturers producing for multiple distribution intermediaries — was inefficient enough that a vertically integrated operation at a high-traffic hub would outcompete it on price while maintaining acceptable margins. The founding investment built a manufacturing facility adjacent to Groombridge's transit hub and established direct supply relationships with the hub operators that eliminated the intermediary layer.
The founding thesis was correct. Gridsupply's direct hub supply relationships allowed it to undercut existing consumer electronics suppliers on price within five years. Growth followed distribution: as the hub relationships generated transit network presence, Gridsupply's products appeared at transit stops throughout the inner corridor.
---
## Operations
**Product lines:** Power systems — residential and commercial power management units, surge protection, portable power storage. Household electronics — charge devices, communication terminals, environmental control interfaces for residential and transit accommodation. Basic components — wire, connectors, and component kits for field repair and installation. The product range is wide but shallow; Gridsupply makes many categories at one quality level rather than few categories at multiple quality levels.
**Manufacturing:** Primary facility adjacent to the Groombridge transit hub. Secondary facility for power systems production. Combined workforce of approximately two hundred. The facilities are production-optimized: manufacturing process designed around throughput rather than quality differentiation.
**Industrial line:** A parallel product line marketed to commercial and industrial clients under a separate brand designation. The industrial line is certified to higher performance standards and priced to reflect them. It uses the same production tooling as the consumer line, with post-production calibration and an expanded testing protocol.
**Distribution:** Hub-direct supply to transit network commissaries and general stores. Wholesale to residential electronics retailers. The distribution network is the company's primary competitive asset.
---
## Political Relationships
**Alcyone Tech:** Alcyone Tech and Gridsupply occupy opposite ends of the Groombridge electronics market — Alcyone serves institutional clients with precision certified hardware; Gridsupply serves the transit worker and residential mass market with commodity electronics. The two companies do not compete directly, but both are currently maintaining certification situations that have not been disclosed to the Lattice Commission. Alcyone's is a hardware vulnerability; Gridsupply's is a testing protocol gap. The parallel is coincidence but would not read that way under a simultaneous regulatory review.
**Arclamp:** Arclamp and Gridsupply share the Groombridge manufacturing quarter and the same institutional client base at the maintenance and equipment level — Arclamp furnishes the offices; Gridsupply supplies the power management and small electronics those offices run on. Both are under Lattice Commission certification for their respective product categories; both have product lines where the certification was not updated after specification changes.
**Commonstock Foods:** Commonstock and Gridsupply are the core corridor's two most significant volume consumer goods suppliers to the transit hub market, operating through the same distribution relationships. Both have built their positions on distribution logistics rather than product differentiation. Both use certification frameworks to signal quality that their internal testing protocols do not fully support. The structural parallel is notable and has not been examined.
---
## What They Don't Talk About
The consumer and industrial product lines share production tooling. A consumer power management unit and an industrial power management unit begin on the same production line from the same components and are differentiated post-production through calibration settings and the testing protocol applied before packaging.
The industrial testing protocol tests seventeen performance parameters, including several that evaluate behavior under sustained load conditions and power fluctuation scenarios characteristic of industrial use. The consumer testing protocol tests eleven parameters — the eleven that overlap with the core performance specification the Commission requires for consumer certification. The six parameters not included in the consumer protocol are specifically those that test the failure modes most likely to occur in consumer devices that are operated continuously, underventilated, or subjected to power quality conditions typical of transit accommodation electrical systems.
When consumer units fail in the ways that the excluded tests cover — thermal protection failure under sustained load, voltage regulation failure under fluctuating input — Gridsupply's warranty response attributes the failure to user error or environmental conditions outside the specified operating range. The specified operating range is defined in the consumer documentation in terms that most transit workers cannot evaluate against their actual living conditions.
The consumer certification is valid. The consumer certification does not certify what the industrial certification certifies.
---
## Gameplay Relevance
Gridsupply Electronics is ubiquitous infrastructure in core corridor and transit environments — its products are in every transit accommodation, common store, and working-class residential space. The brand is recognized as standard-issue, not chosen. A failed power strip in a transit bunkroom is almost certainly Gridsupply.
The testing protocol gap is the investigative thread. The industrial and consumer testing protocols are internal documents. The Commission's certification file confirms what parameters were tested; comparison with the industrial protocol reveals what was omitted. The failure patterns documented in Gridsupply's warranty denial records, cross-referenced against the untested failure modes, make the connection. A consumer protection case would require demonstrating that the certification, while technically valid, created a reasonable expectation the product did not meet.
Gridsupply's distribution records also provide a comprehensive inventory of which products are at which transit hubs across the inner corridor.
The consumer certification gap creates a specific vulnerability for the transit hub operators who are Gridsupply's primary distribution channel. Hub commissaries and general stores sell Gridsupply products under their own brand relationships with the hub operators — operators whose own commercial licenses require them to stock certified goods. If the consumer certification is subsequently found inadequate, the liability question that follows is whether the hub operators, as the point of sale, bear any responsibility for goods that failed to meet the standard they were certified to. Gridsupply's standard supply contracts include an indemnification clause for certified-product liability that the hub operators signed without testing. The legal architecture of a failure claim runs through the hub operators before it reaches Gridsupply — a structural feature that Gridsupply's legal team designed and that gives the company's distribution relationships a characteristic that benefits one side considerably more than the other.
---
**Cross-References:**
- [Groombridge](../star-systems/GJ-380/index.md) — Headquarters; manufacturing facilities; transit hub distribution
- [Alcyone Tech](alcyone-tech.md) — Groombridge electronics peer; premium institutional market contrast
- [Arclamp](arclamp.md) — Groombridge manufacturer; adjacent commercial sector
- [Commonstock Foods](commonstock-foods.md) — Core corridor volume consumer peer; shared distribution context
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/gronnmark-consumer.md
+85 -7
View File
@@ -1,24 +1,102 @@
---
title: "Gronnmark Consumer"
description: "Gronnmark Consumer — consumer goods manufacturer based in Nyrheim, west reach"
description: "Nyrheim volume consumer goods manufacturer — west reach household and personal goods branded as locally produced, assembled locally from components that are not, in a distinction the marketing elides"
slug: gronnmark-consumer
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Nyrheim (GJ 3737)
tags: [commodity_branded, west_reach, mark, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [bavarian-craft, bergkraft-antriebswerke, lowlands-consumer]
---
# Gronnmark Consumer
**Type:** Corporation — Consumer Goods Manufacturer
**Type:** Corporation — Volume Consumer Goods Manufacturer
**Also Known As:** Gronnmark
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Nyrheim (GJ 3737)
**Scope:** West reach primary; adjacent corridor distribution secondary
**Headquarters:** Nyrheim (GJ 3737) — west reach, 6 hops from Gateway
**Classification:** Sub-Syndic consumer goods enterprise; household and personal goods volume production
Gronnmark Consumer is a consumer goods manufacturer operating out of Nyrheim (GJ 3737). Details to be expanded.
---
## Overview
Nyrheim is a functional outer system that works: settled two centuries ago by a cohort of Scandinavian-heritage families who came intending to stay and built the infrastructure to make staying viable. It has agriculture, manufacturing capacity, and a stable population that has grown by birth and immigration rather than the boom-and-bust dynamics that characterize resource extraction systems. The consumer goods that the population needs are, to a significant degree, produced locally. Gronnmark Consumer is the largest expression of this local manufacturing capacity.
The company produces household goods, personal care products, and light domestic equipment — the things that a working population buys regularly and does not think hard about. Its market is the west reach's outer corridor, where the distance from inward supply hubs makes local production economically viable and where the Mark currency preference supports local suppliers over Tractus-denominated inward imports. Gronnmark's competitive advantage is proximity: it can supply Nyrheim and adjacent west reach systems faster and more reliably than any inward manufacturer, and its pricing in Mark reflects that it does not pay transit costs.
The "locally produced" branding that Gronnmark emphasizes in its west reach marketing reflects the proximity advantage. It does not reflect the origin of the components that go into the products being assembled at Nyrheim.
---
## Origin
Gronnmark was established forty-five years ago by a manufacturing cooperative that had been producing basic household goods for Nyrheim's local market and wanted to expand distribution to adjacent systems. The cooperative structure meant that founding capital came from multiple families, which distributed both the risk and the decision-making. This made growth slower but more stable than single-owner enterprise models, and Gronnmark's cautious expansion is characteristic of its founding culture.
The shift from cooperative to corporation happened twenty years ago when the capital requirements of expanding manufacturing capacity exceeded what the cooperative governance model could efficiently raise. The founding families retained majority ownership; the corporate structure allowed outside investment. The company has remained majority locally owned, which is part of what the "locally produced" branding signals — that the profits stay at Nyrheim, which is true, even if the components come from elsewhere.
---
## Operations
**Product lines:** Household goods — cookware, cleaning supplies, storage containers, basic tools. Personal care — grooming products, hygiene supplies, basic medical consumables. Domestic equipment — small appliances, lighting, portable electronics at the utility end of the market. The range is broad; the quality level is consistent — functional, adequate, not aspirational.
**Manufacturing:** Assembly and final production at Nyrheim. The facility is genuinely local and genuinely employs Nyrheim residents in manufacturing roles — this is accurate in the marketing. What is not in the marketing is that the component parts being assembled come predominantly from inward suppliers at Bergtor and, for a smaller fraction, from inward core corridor manufacturers.
**Component sourcing:** Established supply relationships with three Bergtor component manufacturers and two inward suppliers. The supply contracts predate the corporate restructuring and have been maintained and expanded as production volume grew. Gronnmark does not manufacture its own components; it assembles supplied components into finished goods.
**Distribution:** West reach direct, through the Mark-currency commercial networks that Nyrheim's founding position gives it access to. Some adjacent corridor distribution through transit hub supply chains.
---
## Political Relationships
**Bavarian Craft:** Bavarian Craft is the west reach heritage brand that Gronnmark most conspicuously positions itself against — locally made, traditionally produced, authentically west reach. The irony is that both companies are managing a gap between their marketing and their manufacturing reality: Bavarian Craft's guild certification applies to a fraction of its output; Gronnmark's local production claim applies to assembly rather than manufacture. Both have legal assessments that support their positions; neither has disclosed the gap publicly.
**Bergkraft Antriebswerke:** Bergkraft is the Bergtor industrial enterprise that supplies the component manufacturers whose output Gronnmark buys for Nyrheim assembly. The supply chain runs through Bergtor regardless of how Gronnmark describes its production origin. A "Made in Nyrheim" challenge that examined the supply chain would trace the component origin to Bergtor and, behind Bergtor, to the same inward supply chains that any commodity manufacturer uses.
**Lowlands Consumer:** Lowlands Consumer is Gronnmark's nearest competitor in the west reach mass market and the company most likely to file a "Made in" labeling challenge if it believed such a challenge would succeed. Lowlands has its own assembly-with-imported-components production model and similar labeling practices — which is the primary reason neither company has filed against the other. The mutual deterrent is understood without being discussed.
---
## What They Don't Talk About
Gronnmark's consumer packaging uses the phrase "Made in Nyrheim" on all products, accompanied by the Nyrheim system crest. Under Lattice Commission consumer goods labeling rules, "Made in [system]" is permissible when the final assembly and the majority of value-add processes occur in the named system. Gronnmark's legal assessment is that final assembly at Nyrheim, which is genuine, satisfies this requirement.
The Commission's standard, as written, permits this interpretation. A competing interpretation — one that the Commission has applied in cases where it has investigated complaints — holds that "Made in" implies a reasonable consumer expectation that primary manufacture occurred in the named system, and that assembly-only production requires disclosure of the component origin. Gronnmark's legal team prepared a memo on this point eight years ago and concluded that the current labeling is defensible but not unambiguously correct.
The products that Gronnmark's west reach customers buy understanding themselves to be purchasing locally manufactured goods are assembled in Nyrheim from components made predominantly at Bergtor and the core corridor. The jobs and economic activity that the "locally produced" branding implicitly claims for Nyrheim include the assembly employment; they do not include the manufacturing employment that generates the components, which is elsewhere.
The memo exists in Gronnmark's legal files. It has not been acted upon.
---
## Gameplay Relevance
Gronnmark Consumer is everyday goods background in west reach systems — its packaging appears in residences, common areas, and market stalls. The brand is visible and familiar in Nyrheim and adjacent systems.
The labeling memo is the investigative thread. The legal analysis that acknowledges the ambiguity exists in Gronnmark's files. The supply contracts documenting component origin are in the procurement records. Comparison of the "Made in Nyrheim" claim against the supply chain documentation makes the gap demonstrable. A regional trade association or competitor motivated to challenge Gronnmark's labeling would have sufficient grounds; the question is whether the Commission has received a complaint.
Gronnmark's position as Nyrheim's largest employer also gives it political weight in local governance decisions — relevant context for investigations involving regulatory enforcement or labor conditions.
The "Made in Nyrheim" question, if raised at the Lattice Commission level, puts Gronnmark's founding families in a position they have not publicly prepared for. Their political identity in the west reach is built on local production, local ownership, and the argument that outer reach communities should be able to sustain themselves economically rather than depending on inward supply. The revelation that their largest enterprise assembles inward components under a local label would not simply be a legal finding — it would be a political contradiction that their opponents in west reach governance discussions would use. Gronnmark's founders understand this, which is the real reason the legal memo has not been acted upon: the risk of regulatory challenge is less significant than the risk of what a public dispute about the "Made in Nyrheim" claim would do to the family's standing in the community it claims to serve.
---
**Cross-References:**
- [Nyrheim](../star-systems/GJ-3737/index.md) — Headquarters; assembly facilities; primary market
- [Bavarian Craft](bavarian-craft.md) — West reach manufacturer; Bergtor component supply overlap
- [Bergkraft Antriebswerke](bergkraft-antriebswerke.md) — Bergtor industrial peer; supply chain context
- [Lowlands Consumer](lowlands-consumer.md) — West reach consumer goods peer; adjacent market segment
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/groot-karoo-cellars.md
+91 -7
View File
@@ -1,24 +1,108 @@
---
title: "Groot Karoo Cellars"
description: "Groot Karoo Cellars — regional specialty producer based in Karoo, south reach"
description: "South_reach fortified wine and brandy cooperative based at Karoo (GJ 222A) — arid-terroir mineral character, drought-adapted cultivars, and three generations of patient aging from reserves the founding-era geological survey described as adequate"
slug: groot-karoo-cellars
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Karoo (GJ 222A)
tags: [terroir, south_reach, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [kaapse-baai-wines]
---
# Groot Karoo Cellars
**Type:** Corporation — Regional Specialty Producer
**Type:** Corporation — Fortified Wine and Brandy Cooperative
**Also Known As:** Groot Karoo, the Cellars
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Karoo (GJ 222A)
**Scope:** Regional — south_reach corridor primary; inner-corridor specialty and collector market secondary
**Headquarters:** Karoo (GJ 222A) — south_reach corridor
**Classification:** Sub-Syndic agricultural cooperative; member-elected governing board
Groot Karoo Cellars is a regional specialty producer operating out of Karoo (GJ 222A). Details to be expanded.
---
## Overview
Groot Karoo Cellars makes fortified wines and grape brandy from cultivars that have spent three generations learning to survive in a system with minimal rainfall, alkaline soil, and the kind of intense seasonal heat that kills less-adapted varieties before harvest. What survives is angular, mineral, and marked by its conditions in ways that cannot be manufactured elsewhere. The cooperative's premium fortified range — sweet, concentrated, with an iron-and-dry-stone character that buyers in the inner corridor have been acquiring at premium prices for sixty years — is the product of that struggle, and the brand has been built around the understanding that difficulty is a terroir.
Groot Karoo's challenge now is not viticulture. It is water.
---
## Origin
The founding settlers of the Karoo system arrived from a Cape-Afrikaner background and named their primary settlement after the broad semi-arid plateau of southern Africa — a name that acknowledged the difficulty they were choosing and suggested they considered it appropriate. They were farmers from a dry-land tradition who understood that what grows under constraint is not lesser than what grows with abundance, only different, and that different has commercial value if you can reach the buyers who understand it.
The first vintages were table wines, adequate and unmemorable. The third generation discovered what the conditions actually favored: the heat and aridity concentrated sugars and phenolics in ways that produced exceptional base material for fortification. The fortified wine tradition — grape spirit added to arrest fermentation and preserve the concentrated sweetness — became the cooperative's defining expression and has remained so for a hundred and forty years.
The founding deed established a member-elected board of seven, renewable every four years, responsible for production planning, capital allocation, and external commercial relationships. The board was designed to prevent any single family from holding indefinite control. This design has worked as intended on the question of internal governance. It has not prevented a governing board from holding information it considers too consequential to share.
---
## Operations
**The cooperative:** Groot Karoo operates as a collective of twenty-three member farms, whose production flows into shared cellars, shared aging stock, and shared commercial accounts. Individual farm quality is tracked and compensated differentially, but the premium label portfolio — Groot Karoo Reserve Tawny, Groot Karoo Vintage, and the Groot Karoo Superior Dry Brandy — is a collective product rather than an estate-specific one. This pooling model has served the cooperative well by maintaining quality consistency across member farms with varying microclimates.
**Water management:** Production at Groot Karoo is entirely irrigation-dependent. The system receives insufficient annual rainfall to sustain commercial viticulture without drawing on supplemental water sources. The primary source is the Onderfontein aquifer, a fossil water deposit discovered by the founding generation's geological survey and developed over the cooperative's first fifty years into a managed draw system. The aquifer has supported every vintage in the cooperative's history. It is the single point of failure for the entire operation.
**Aging:** Fortified wines require patient barrel maturation — the premium ranges are held for twelve to twenty-five years before release. This timeline means the current board is making decisions whose commercial consequences will be assessed by future boards. It also means the current premium stock under aging represents significant capital that can be valued, separated from the production operation, and sold.
**Distribution:** The cooperative distributes through south_reach channels and a small set of inner-corridor specialist importers who carry Groot Karoo Reserve Tawny as a category-defining fortified wine. The Dry Brandy moves through general spirit distributors.
---
## Products
**Groot Karoo Reserve Tawny** — the signature product. A fortified wine from the dominant local red varietal, aged a minimum of fifteen years in old-wood barrels that contribute little tannin but allow the slow oxidative development that gives the tawny style its distinctive amber color and nut-and-dried-fruit character. The arid terroir contributes a mineral dryness to the finish that distinguishes Groot Karoo from any equivalent production in wetter systems. Inner-corridor buyers who collect fortified wines treat Reserve Tawny as a benchmark.
**Groot Karoo Vintage** — the declared-vintage expression, produced only in exceptional harvest years. Not declared every year; when declared, aged twenty to twenty-five years before release. Substantially more valuable than the Reserve range. The most recent declared vintage was twelve years ago; the cooperative has not declared one since, citing harvest quality concerns.
**Groot Karoo Superior Dry Brandy** — grape brandy from the same cultivar base, double-distilled and aged in local stone-pine barrels for eight years minimum. The dry brandy has a different market profile from the fortified wines — purchased in the south_reach as a working spirit, appearing in inner-corridor specialty markets as an unusual regional expression. Production volumes are modest.
---
## Political Relationships
**Kaapse Baai Wines:** The Cape Producers Circle at Kaapse Baai (GJ 213) represents a parallel south_reach terroir wine operation — coastal and cool rather than arid and hot, table wines rather than fortified. The two cooperatives occupy distinct niches and do not compete. Representatives of both operations have occasionally found themselves in conversation at south_reach producer gatherings, sharing the specific perspective of terroir producers in remote systems managing corridor-scale market relationships with limited leverage. The relationship is aware and professionally cordial without being close.
**Collective membership:** The twenty-three member farms are the cooperative's constituency and its source of internal accountability. Member farmers receive annual production accounts, participate in board elections, and have access to the cooperative's public financial records. They do not have access to the board's internal working papers, strategy documents, or the reports commissioned by the board through external contractors.
**Ferreira Monteiro:** The cooperative's commercial law relationship for external disputes and contract work sits with a Ferreira Monteiro correspondent registered at the south_reach nodes of Ferreira's network. Ferreira Monteiro's practitioners are familiar with agricultural cooperative governance in the south_reach context.
---
## What They Don't Talk About
Five years ago, the governing board commissioned a hydrological survey of the Onderfontein aquifer through an external geological consultancy. The survey was marked proprietary and has not been presented to or disclosed to the cooperative membership. Its conclusions established that the aquifer is not inexhaustible. At current draw rates, the Onderfontein system has twenty-five to thirty-five years of viable production capacity before extraction rates fall below the levels required to sustain commercial-scale viticulture. The cooperative could extend this window by reducing annual draw — which would require reducing production — or by locating supplemental water sources, which the survey assessed as unlikely at commercially viable depth in the current geology.
The board's response, over the subsequent four years, has been to begin preliminary negotiations with an off-system holding company regarding the acquisition of Groot Karoo's premium label portfolio and its aged stock inventory. The negotiation is framed internally as "strategic partnership discussions." The holding company would acquire the labels and the aging barrels — the premium commercial assets — while the cooperative retained the production operation and the member farms. From the board's perspective, this preserves employment and member livelihoods while extracting maximum value from the premium assets before the aquifer constraint becomes public knowledge.
No member of the cooperative has been informed that these negotiations are occurring, or that the board is in possession of a geological assessment that changes the long-term production outlook.
---
## Gameplay Relevance
Groot Karoo Cellars is a slow-burning institutional betrayal. The board is not acting from malice — they have convinced themselves they are managing a hard situation responsibly. The members who don't know about the survey and the negotiations would have a different view.
The productive investigation threads are:
- **The hydrological survey** — the proprietary geological report exists in the board's internal archive. It was commissioned through an external consultancy, which means the commissioning contract and the consultancy's own records are external to the cooperative and potentially accessible through the consultancy rather than the board. A player who locates the survey has the full picture. A player who locates only the board's internal strategy documents may understand the shape of the situation without the technical foundation.
- **The portfolio negotiations** — the off-system holding company is in preliminary discussions. The negotiation correspondence exists in the board chair's communications rather than official cooperative records. Any member of the cooperative's audit committee has a standing right to review cooperative correspondence — a right they have not exercised because they don't know there is correspondence worth reviewing.
- **The production decline** — the vintage non-declaration pattern (twelve years without a declared vintage, citing harvest quality) is publicly observable. Someone with access to production records and the hydrological survey together would understand that the quality rationale is secondary; the board is avoiding vintage declarations that would create aging inventory commitments extending beyond the aquifer timeline.
---
**Cross-References:**
- [Karoo](../star-systems/GJ-222A/index.md) — Headquarters system; founding terroir; Onderfontein aquifer
- [Kaapse Baai Wines](kaapse-baai-wines.md) — Parallel south_reach terroir producer; coastal estate wines; mutual professional awareness
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/haesungdan-records.md
+77 -5
View File
@@ -1,11 +1,11 @@
---
title: "Haesungdan Records"
description: "Haesungdan Records — cultural content producer based in Miryang, east reach"
description: "East reach vocal arts label at Miryang (GJ 754) — celebrated for artist development depth, demanding craft standards, and a roster built on decades-long relationships"
slug: haesungdan-records
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-21
scope: regional
faction_type: economic
headquarters: Miryang (GJ 754)
@@ -16,9 +16,81 @@ cross_refs: []
# Haesungdan Records
**Type:** Corporation — Cultural Content Producer
**Type:** Corporation — Vocal Arts Label
**Status:** Canonical
**Scope:** Regional — east reach operations
**Scope:** East reach corridor primary; reach-wide distribution via Meridian for principal artists
**Headquarters:** Miryang (GJ 754)
**Currency:** Tractus
**Classification:** Sub-Syndic cultural enterprise; independent
Haesungdan Records is a cultural content producer operating out of Miryang (GJ 754). Details to be expanded.
---
## Overview
Haesungdan Records is named for the ceremony of the rising — a sunrise observation tradition practiced at the eastern headlands of Miryang's habitable continent, where the system's star clears a particular ridge formation in a way that produces a window of specific light lasting approximately forty minutes. The ceremony is communal, unhurried, and not concerned with arriving at a conclusion. It is exactly what the label sounds like.
The label's specialty is the voice — specifically, the trained singing voice developed through methods that take years and do not shortcut. Haesungdan has signed artists as young as nineteen who released their first records with the label at twenty-six. The label considers this normal. Its artist development program is among the most rigorous in the east reach, involving sustained coaching, repertoire building, and the patient accumulation of technique that the label's founders believe is the only legitimate basis for a recording career. An artist who arrives at Haesungdan with talent but without foundation will receive the foundation before they receive a release date.
The label has produced eleven of the east reach corridor's most respected vocal artists in its forty-five-year history. It has also produced, in that time, a significant number of artists who completed their development period and then moved to other labels for their commercial career. Haesungdan is not proprietary about this. The goal is developed artists, not owned artists.
---
## Origin
The label was founded forty-five years ago by a vocal instructor named Jiye Seon who had taught at one of Miryang's music conservatories for twelve years and had concluded that the conservatory system and the commercial music system were solving different problems. The conservatory produced skilled singers who knew how to sing. The commercial system produced singers who could record. The gap between these — the artist who knew their instrument and also knew how to make that instrument serve a recording, an audience, a room — was not being systematically addressed by either institution.
Jiye Seon founded Haesungdan to address the gap. The initial roster was drawn from conservatory graduates who had completed their formal education and needed the next stage of development that neither the conservatory nor the commercial labels were providing. The first three releases, across the label's first four years, were not commercially significant. They were technically exceptional. The east reach music press understood what it was hearing. The wider audience came later.
Jiye Seon continues as the label's artistic director at an age that requires Perpetual-class longevity technology to have reached. She holds no opinion about retiring.
---
## Operations
**Artist development:** The label's development program lasts between three and seven years depending on the artist's starting point and trajectory. During this period artists receive a living stipend, coaching from label-contracted instructors, access to the label's rehearsal facilities, and regular performance placements at smaller venues in the east reach corridor. Development artists do not record for release until Jiye Seon and the artist agree that the recording will be a fair representation of what the artist can do.
**Coaching network:** The label maintains relationships with approximately thirty vocal coaches, accompanists, and music historians across the east reach. Several of these relationships are multi-generational — coaches who studied with Haesungdan-affiliated instructors themselves, now teaching within the network. The network operates as an informal extension of the label's development capacity, providing regional coverage for artists in systems outside Miryang.
**Repertoire:** The label does not impose repertoire choices. Haesungdan artists are expected to develop their own relationship with their material — which may be traditional east reach vocal forms, contemporary composition, cross-cultural synthesis, or genres that Haesungdan has not previously worked with. The label's position is that repertoire is the artist's decision and that artistic directors who impose repertoire are solving their own aesthetic problems, not the artist's.
**Distribution:** Tractus-denominated, Meridian-primary. Principal artists with established careers receive full reach-wide distribution through standard Meridian protocols. Development-period artists have limited distribution by design — their material is not intended for wide circulation until it is ready for it.
---
## Reach Position
Haesungdan Records occupies a specific and respected position in the east reach cultural ecosystem: the label that produces artists the other labels would like to sign. The label's development alumni — artists who completed their Haesungdan training and then moved elsewhere — are well represented in the east reach's major commercial labels and in cross-corridor careers. The label does not advertise this. It does not need to.
The relationship between Haesungdan and the east reach's commercial music infrastructure is cordial and mutually understood: Haesungdan is not competing for the same commercial outcomes, and the commercial labels are not attempting to replicate the development program that would require them to operate at a different pace and on a different economic logic. The labels that have tried to run accelerated development programs modeled on Haesungdan have generally produced results that Jiye Seon has described, when asked, as "promising starts."
---
## Political Relationships
**Miryang music conservatories:** Haesungdan draws its development candidates primarily from conservatory graduates and maintains formal consultation relationships with the two largest Miryang institutions. Jiye Seon does not hold a teaching post at either but is invited to examine senior recital performances. The conservatories track their own graduates' trajectory through Haesungdan development — a prestige indicator for the conservatory, not just the artist.
**East reach commercial labels:** The cordial competitive relationship described above rests on a quiet understanding: the commercial labels do not approach Haesungdan artists during the development period, and Haesungdan does not attempt to retain artists after development. This understanding is not contractual. It has held for forty-five years because breaking it would be expensive for the breaker in ways that nothing in Miryang's music infrastructure rewards.
**Meridian:** Distribution relationship only, no equity entanglement. Haesungdan's contracts with Meridian are longer-duration than typical commercial label agreements, reflecting the label's longer production cadence.
---
## Silence Topic
What Haesungdan Records does not discuss: the assessment process.
How Jiye Seon decides which prospective artists enter the development program and which do not is not documented. The criteria are not published. Artists who have been declined have described the experience variously as clear and direct, ambiguous, and in at least one case devastating. The label does not dispute any of these characterizations. "We make a judgment" is the closest thing to an official statement on the matter. The judgment has been wrong. The label acknowledges this without specifying the cases.
One declined artist, two decades later, sits on the board of a competing east reach label. Whether that artist remembers the decline decision the way Jiye Seon remembers making it is not something either of them has confirmed in writing. The competing label has never signed a Haesungdan-trained artist. This pattern could be coincidence. The commercial labels do not pursue Haesungdan talent on principle, per the silent understanding above. It could also not be coincidence.
---
**Cross-References:**
- [Hanyang Precision Systems](hanyang-precision.md) — co-located at Changwon adjacent corridor; east reach institutional neighbor
- [Miryang](../star-systems/GJ-754/index.md) — headquarters system; east reach vocal arts corridor
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-21
wiki/corporations/hakone-hospitality.md
+79 -6
View File
@@ -1,24 +1,97 @@
---
title: "Hakone Hospitality"
description: "Hakone Hospitality — premium service provider based in Matsue, east reach"
description: "East reach thermal and restorative hospitality group at Matsue (GJ 687) — geothermally sourced immersive stays built around a Japanese-heritage tradition of deliberate recovery"
slug: hakone-hospitality
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Matsue (GJ 687)
tags: [service_premium, east_reach, tractus]
decision_refs: [D-189]
cross_refs: []
cross_refs: [prometheus-labs, lattice-commission]
---
# Hakone Hospitality
**Type:** Corporation — Premium Service Provider
**Type:** Corporation — Thermal and Restorative Hospitality Group
**Status:** Canonical
**Scope:** Regional — east reach operations
**Scope:** East reach corridor primary; inward referrals secondary
**Headquarters:** Matsue (GJ 687)
**Currency:** Tractus
**Classification:** Sub-Syndic service enterprise; private partnership
Hakone Hospitality is a premium service provider operating out of Matsue (GJ 687). Details to be expanded.
---
## Overview
Matsue sits on a geologically active body with subsurface thermal systems that produce hot springs of exceptional mineral consistency. This is not unusual in the Reach — geothermal activity appears on dozens of inhabited worlds — but what the founding generation of Matsue's hospitality trade understood, and what the competitors who have tried to replicate it have not, is that the thermal water is not the product. The product is the stay. The water is the occasion.
Hakone Hospitality operates five properties at Matsue, each built around a different thermal source with different mineral composition and temperature characteristics. The properties share a common design language derived from the Japanese heritage traditions of their founding generation: low construction, natural materials, deliberate spatial arrangement that manages privacy without walls. The guest experience is structured around immersion, recovery, and the specific quality of time that occurs when a person has no obligations and no Meridian connectivity and nowhere to be.
The last point is operational rather than philosophical. Hakone properties do not maintain Meridian connectivity for guest use. This is disclosed in the booking materials and is the reason approximately forty percent of the group's guests book specifically with Hakone rather than other east reach premium properties. The other sixty percent book for the thermal experience and discover, during the stay, that the absence of connectivity is something they did not know they needed.
---
## Origin
The founding partnership was established sixty years ago by three families from Matsue's original settlement wave — all with roots in Japanese heritage communities that had maintained traditional hospitality practices through several generations of corridor transit. The tradition they brought was specific: not luxury as accumulation of amenities, but hospitality as structured recovery. The onsen tradition held that the value of thermal immersion was inseparable from the conditions around it — the silence, the absence of demand, the specific quality of attention from staff who understood that service sometimes means leaving someone alone.
The first Hakone property opened with twelve rooms and one thermal pool. It was full within a month and has operated at full occupancy or close to it for the sixty years since. The partnership added properties at intervals of roughly a decade, each one occupying a different thermal zone on the habitable body, each one designed by the same architectural family that designed the first. The current managing partnership is third-generation: grandchildren of two of the founding families, extended through Perpetual-class longevity into careers that are still in their middle decades.
The founding families brought their practice to Matsue specifically because the system's geothermal profile matched what the tradition required. Three generations of corridor transit had compressed the practice to what could not be lost: the structural relationship between thermal immersion, silence, and the quality of attention that is not quite service and not quite friendship. The properties as they now stand are what those three generations carried and what the current partnership has had sixty years to rebuild around Matsue's five specific thermal zones.
---
## Operations
**Properties:** Five properties, forty to sixty rooms each, designed for stays of three days minimum. The booking systems do not accommodate one-night stays; the property design assumes guests who need time rather than a bed. Occupancy is managed to ensure no property runs above eighty percent capacity — the remaining twenty percent is held as operational buffer and, in practice, as the reason the properties feel spacious when they are full.
**Thermal access:** Each property centers on its specific thermal source. The properties do not share thermal infrastructure. Guests at one property do not visit another during their stay; the stays are designed to be complete within one location. The mineral profile of each thermal source is documented and published — not for marketing purposes but because guests with specific health considerations need the information, and because the transparency is consistent with the hospitality philosophy.
**Connectivity policy:** Meridian access is absent from all guest areas at all properties. Staff areas maintain connectivity for operational purposes. The policy is enforced through infrastructure design rather than rule-setting: the properties are constructed in locations where Meridian signal does not reach, and the construction materials maintain the gap. Guests who need connectivity during their stay are directed to a facility outside the property grounds, a ten-minute walk that the group considers appropriate to the purpose.
**Lattice wellness services:** Hakone offers, as a supplementary service at four of its five properties, a lattice wellness assessment — a non-clinical review of lattice performance indicators conducted by credentialed staff and positioned as a restorative service rather than a medical one. The assessment uses equipment licensed under a wellness services classification rather than the clinical classification that would apply to Lattice Commission-certified medical procedures. The service is popular. The licensing category it operates under was designed for occupational fitness assessments, not for the extended diagnostic depth that Hakone's assessments reach. The Lattice Commission has not, to date, examined this classification closely.
---
## Political Relationships
**Prometheus Labs:** The research data agreement connecting Hakone's wellness assessments to a Prometheus Labs research division was established by the group's second-generation management. The current managing partnership knows the agreement exists; the specific scope of what Prometheus Labs receives has not been the subject of an internal review in twenty years, and the relevant documents are in the founding archive rather than the current operational record. The relationship is passive — Hakone provides data, Prometheus Labs provides the research fee — and neither party has needed to renegotiate.
**The Lattice Commission:** The wellness services classification that Hakone's assessment program operates under is the institution's regulatory pressure point. Commission certification staff at the nearest regional office have flagged the classification for review three times in the past decade; each review concluded without action, partly because the boundary is genuinely ambiguous and partly because Hakone's assessment volumes have remained below the threshold that triggers mandatory audit. The east reach's growing commercial traffic is putting Matsue's systems on trajectories that will eventually exceed that threshold.
**Matsue's industrial syndicate community:** Hakone's properties exist in a manufacturing system whose primary economic character has nothing to do with hospitality. The coexistence is stable — the thermal trade draws high-end clients who spend in the service economy without competing for industrial resources. The Yongli Combine's management staff use Hakone properties for restorative stays, which is a relationship neither party discusses publicly and which gives Hakone a commercial anchor in the system's most powerful industrial institution.
---
## What They Don't Talk About
Hakone's lattice wellness assessments produce records. The assessment records are held by the group for the stated purpose of longitudinal wellness tracking for returning guests. This is accurate; the records are used this way. What the group does not prominently disclose is that the aggregate assessment data — anonymized, statistically processed, stripped of individual identification — is provided quarterly to a Prometheus Labs research division studying long-term lattice performance in high-functioning professionals under restorative conditions. The data is provided under a research agreement that predates the current management partnership. The guests whose data contributed to the aggregate provided consent for "research use of anonymized wellness data" in the booking terms they agreed to. Most of them have not read that clause carefully.
The more operationally significant fact is the assessment equipment's certification trajectory. The current wellness services classification creates an ambiguous regulatory boundary that has been stable because neither the Commission nor Hakone has pressed it. If Commission review thresholds catch up with Hakone's growing assessment volumes, the relevant question will not be whether the service constitutes medical practice but what data has been collected and shared under a classification that may not have covered it. The research agreement with Prometheus Labs makes the answer complicated.
---
## Gameplay Relevance
Hakone properties are investigation-relevant for any case touching the east reach's professional and institutional class. People who need to be unreachable come here. The connectivity absence is a genuine operational gap — a player tracking someone's movements will find a gap in Meridian activity records corresponding to a Hakone stay, and the gap will require explanation. The group's guest records, which do exist (unlike Alcazar's), are private; accessing them requires either the group's cooperation, legal process, or a source inside the property.
The lattice wellness assessment data is a secondary thread. The Prometheus Labs research division purchasing aggregate data is a relationship that, if surfaced, raises questions about what Prometheus Labs is learning from east reach professional lattice performance and why they are paying for access through a wellness hospitality intermediary rather than through standard research channels. The assessment equipment's licensing classification is the entry point: an investigator who knows what questions to ask about the equipment's certification can establish that the assessments exceed the scope of the license, which is a Lattice Commission concern and a potential lever.
The managing partnership is a potential direct source: third-generation Perpetual-class practitioners who know the founding archive exists, understand what it contains in general terms, and whose primary institutional interest is the properties' operational continuity. They will not volunteer information about the Prometheus Labs data agreement. They will negotiate about what they know and what they are prepared to confirm — which is a different posture from either full cooperation or active obstruction.
---
**Cross-References:**
- [Matsue](../star-systems/GJ-687/index.md) — Headquarters system; geothermally active; five distinct thermal zones
- [Prometheus Labs](prometheus-labs.md) — purchaser of aggregate lattice wellness assessment data
- [Lattice Commission](../factions/lattice-commission.md) — wellness services classification dispute; regulatory pressure point
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/hana-creative.md
+83 -7
View File
@@ -1,24 +1,100 @@
---
title: "Hana Creative"
description: "Hana Creative — cultural content producer based in Jinghu, east reach"
description: "Jinghu visual design and cultural media studio — east reach institutional identity work, public communications design, and a content library built on commissioned art whose underlying attribution rights the studio has been systematically absorbing"
slug: hana-creative
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Jinghu (GJ 445)
tags: [cultural, east_reach, tractus, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [hangang-studio, ondori-interactive, byeolbit-entertainment]
---
# Hana Creative
**Type:** Corporation — Cultural Content Producer
**Type:** Corporation — Visual Design and Cultural Media Studio
**Also Known As:** Hana
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Jinghu (GJ 445)
**Scope:** East reach primary; inward institutional licensing secondary
**Headquarters:** Jinghu (GJ 445) — east reach, 4 hops from Gateway
**Classification:** Sub-Syndic creative enterprise; institutional design and visual media production
Hana Creative is a cultural content producer operating out of Jinghu (GJ 445). Details to be expanded.
---
## Overview
The east reach's institutional identity landscape — the visual language that governments, corporations, and cultural organizations use to represent themselves — has been shaped to a significant degree by one studio. Hana Creative handles corporate identity design, government communications materials, and public cultural programming for the majority of Jinghu's institutions and a substantial portion of the east reach's regional organizations. When a new commercial district at Seongho needs environmental graphics, when a regional transit authority updates its wayfinding system, when a cultural festival needs visual identity across five platforms, the commission is as likely as not to end up at Hana.
The studio's design language is recognizable across the east reach without being loud about it — a particular combination of typographic restraint and illustration warmth that carries identifiable character while adapting to each client's requirements. This adaptability is the studio's core skill and the reason institutional clients retain it across refresh cycles rather than searching for new designers when their previous identity ages.
The studio has built, over twenty years of commissioned work, a visual content library that is its most valuable commercial asset. The terms under which that library was assembled are the part of the studio's history that the original artists would not recognize.
---
## Origin
Hana Creative was founded twenty-three years ago by a graphic designer named Park Soyeon who had spent a decade doing freelance identity work for east reach clients and had accumulated enough commissions, reputation, and frustration with the administrative overhead of solo practice to formalize into a studio operation. The founding configuration — a small permanent team with a larger network of commissioned collaborators — was practical: institutional clients wanted a single point of accountability that a solo practice couldn't always provide; a studio provided it.
The early commissions built the reputation; the reputation brought larger commissions; larger commissions required more complex production, which justified the permanent team expansion. The studio grew from four people at founding to twenty-six now, covering design, illustration, motion, and production. The library of work produced across two decades of institutional commissions has become the basis of a licensing operation that generates revenue independent of active commissions.
---
## Operations
**Institutional design:** The core practice — corporate identity, government communications, cultural organization visual systems. Multi-year retainer relationships with approximately fifteen institutional clients. Commission work for non-retainer clients representing approximately 40% of project volume.
**Visual content library:** A catalogue of illustrations, motion assets, and design elements developed across two decades of commissioned projects. Licensed to platforms, publishers, and commercial clients for use in contexts beyond the original commission. Library licensing is a growing revenue stream.
**Production:** Full in-house production capacity for digital and physical deliverables. The permanent studio handles digital work; physical production is outsourced to Jinghu's printing and fabrication network.
**Commissioned collaborators:** A network of approximately forty freelance illustrators, motion designers, and photographers who contribute to specific projects. These collaborators are paid project fees; their relationship with the rights produced is defined by their commission contracts.
---
## Political Relationships
**Hangang Studio:** Hangang Studio is the east reach's dominant media platform and carries a significant portion of the moving-image content that Hana's clients commission for broadcast contexts. The two companies have a commercial relationship through Hana's motion design work for Hangang-distributed productions; they also share east reach institutional clients who use both companies' services for different content types. Both companies have unresolved intellectual property arrangements with creators whose rights they are managing in ways those creators have not been told about.
**Ondori Interactive:** Ondori Interactive commissions visual design work from Hana for its interactive media products and maintains a retainer relationship for interface design. The retainer gives Ondori early visibility into Hana's design language development — visual approaches that appear in Ondori products before they appear in the public catalogue. The relationship is commercially standard; the timing of design language adoption has occasionally produced confusion about which studio originated specific visual approaches.
**Byeolbit Entertainment:** Byeolbit is the largest east reach entertainment production company and one of Hana's most significant institutional clients for broadcast visual design. The commercial relationship gives Hana significant revenue stability; it also means that Hana's visual design language is shaped, at the margin, by what Byeolbit's productions need. The derivative work registrations that Hana has filed include visual elements developed specifically for Byeolbit productions — elements that Byeolbit believes it has licensed and Hana believes it has registered as its own derivative.
---
## What They Don't Talk About
Hana Creative's commission contracts with freelance collaborators include a work-for-hire clause that assigns copyright in the commissioned work to the studio. This is standard. The contracts also include an attribution clause that preserves the collaborator's right to credit and attribution in derivative works produced from the original commission.
Over twelve years, Hana Creative has been registering the most commercially valuable elements of its commissioned library as derivative works — new registrations that list the studio as rights holder based on design elaboration or contextual reframing that the studio applies to the underlying commissioned art. The derivative registrations are legally defensible — the modifications are genuine — but the practical effect is that subsequent commercial licensing of the library's most valuable visual assets cites the derivative registration, not the original commission.
The original artists' attribution rights attach to the original work. They do not automatically extend to derivative registrations. When the library element that generates the most commercial licensing revenue is a derivative registration, the original artist's attribution right applies to an asset that isn't what's being licensed. Several of the collaborators who contributed foundational work to the library have, when they have discovered their work in commercial contexts without credit, been directed by Hana's legal team to the original commission contract — which confirms their attribution right to the original, not to the derivative that's actually being used.
The distinction is documented in the registration records. It is not explained to collaborators when commissions are completed.
---
## Gameplay Relevance
Hana Creative is visual culture presence in the east reach — its design work is the visual identity of institutions and organizations throughout the corridor, making it ambient everywhere that institutional communication appears. A player navigating east reach commercial and cultural environments will encounter Hana's work without knowing it.
The derivative registration pattern is the investigative thread. The original commission contracts, the derivative registrations, and the licensing records are three sets of documents that tell the story when compared. A collaborator who has tried to license their own work and been informed it falls outside their attribution rights is a potential source. The cumulative scale of the practice — twenty years, dozens of collaborators — makes the pattern demonstrable rather than requiring analysis of any single case.
The consequence of exposure varies by collaborator. Artists who contributed incidentally to a single commission have limited standing; artists whose foundational work underpins a significant licensing revenue stream have a strong case that their attribution rights are being extinguished through a registration process they were not party to. The most significant thread involves two or three collaborators whose illustration work from Hana's first decade is now the visual foundation of multiple institutional identities across the east reach — identities that renew licensing revenue annually. The derivative registration structure means these artists cannot exercise attribution rights in the commercial contexts that actually generate value. For a player mediating an IP dispute or building an attribution rights case, the registrations, the original contracts, and the licensing revenue records are the three document sets that make the pattern legible. The studio's founder, who is still active at Hana, was not the architect of the registration practice; it developed under commercial management below her. This is context that matters for how the case resolves.
---
**Cross-References:**
- [Jinghu](../star-systems/GJ-445/index.md) — Headquarters; institutional client base; design community
- [Hangang Studio](hangang-studio.md) — East reach media peer; overlapping institutional licensing
- [Ondori Interactive](ondori-interactive.md) — East reach creative enterprise; shared client geography
- [Byeolbit Entertainment](byeolbit-entertainment.md) — East reach entertainment peer; visual content licensing overlap
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/hangang-studio.md
+83 -7
View File
@@ -1,24 +1,100 @@
---
title: "Hangang Studio"
description: "Hangang Studio — media platform and catalogue service based in Songjiang, east reach"
description: "Songjiang media platform and archive service — east reach cultural catalogue streaming and preservation, collecting licensing revenue on lapsed-agreement works while renegotiating quietly and leaving rights holders uninformed"
slug: hangang-studio
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Songjiang (GJ 625)
tags: [platform_catalogue, east_reach, tractus, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [hana-creative, open-corridor-stream, byeolbit-entertainment]
---
# Hangang Studio
**Type:** Corporation — Media Platform And Catalogue Service
**Type:** Corporation — Media Platform and Archive Catalogue Service
**Also Known As:** Hangang
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Songjiang (GJ 625)
**Scope:** East reach primary; inner corridor catalogue distribution secondary
**Headquarters:** Songjiang (GJ 625) — east reach, 4 hops from Gateway
**Classification:** Sub-Syndic media enterprise; streaming, archive licensing, and cultural preservation
Hangang Studio is a media platform and catalogue service operating out of Songjiang (GJ 625). Details to be expanded.
---
## Overview
The east reach's cultural production — films, music, visual art, immersive media — is scattered across systems without a coherent distribution infrastructure. What exists in one system may be entirely inaccessible two hops away. Hangang Studio was built to solve this: a platform that aggregates east reach cultural content into a searchable, streamable archive and distributes it across the corridor. The ambition is genuine and the execution is substantial. Hangang's catalogue is the most comprehensive aggregation of east reach cultural production available anywhere in the corridor, and for communities whose own cultural output they couldn't previously access outside their home system, the platform is genuinely valuable.
The commercial model that sustains this is licensing: content owners license their work to Hangang for distribution; Hangang pays licensing fees and collects subscription revenue from the corridor communities who use the service. Where this model functions as described, it works for everyone. The platform's problem is what happens when licensing agreements lapse during the extended renegotiation periods that multi-system rights management requires.
---
## Origin
Hangang Studio was founded sixteen years ago by a media technology entrepreneur named Cho Minju who had been working in network services at Songjiang and had identified that the east reach's cultural content was distributed in a pattern that made more sense from the perspective of individual system economies than from the perspective of a corridor audience. Each system had its own distribution infrastructure; cross-system access required either physical transit of media carriers or ad hoc bilateral distribution agreements that rarely covered more than two systems. A coordinated platform built from Songjiang's network infrastructure position would consolidate access.
The founding investment built the technical infrastructure and the initial licensing relationships simultaneously. The first four years were spent building the archive rather than monetizing it — taking on losses to build catalogue depth before introducing subscription pricing. The model worked: when subscription pricing launched, the catalogue was large enough that the pricing was justified.
---
## Operations
**Catalogue:** Approximately 4,200 titles across film, serial, music, and immersive media. The catalogue skews east reach but includes inward co-productions and purchases. Approximately 600 titles are original Hangang productions; the remainder are licensed from rights holders ranging from individual artists to production studios.
**Licensing management:** A team of twelve managing approximately 800 active licensing relationships across the catalogue. Agreements range from flat-fee licenses to revenue-share arrangements to long-term exclusivity contracts for major production relationships.
**Archive function:** Hangang operates a genuine preservation program for east reach cultural material at risk of loss — older works on degrading physical media, productions from systems without local preservation infrastructure. The preservation work is acknowledged as valuable by the cultural communities involved.
**Distribution:** East reach streaming platform, accessible across the corridor. Content is available offline-download for transit contexts where streaming bandwidth is unavailable. The service operates on a subscription model with tiered pricing.
---
## Political Relationships
**Hana Creative:** Hana Creative is both a catalogue licensor and a visual design vendor to Hangang — it supplies motion design and interface visual work for the platform, and it licenses visual archive content to the platform's contextual packaging. The dual relationship means Hana has commercial interest in the platform's continued operation and visibility into platform licensing practices. Neither company has disclosed to the other that it has intellectual property arrangements with creators that have not been fully explained to those creators.
**Open Corridor Stream:** OCS is the inward streaming platform most directly competitive with Hangang's east reach service for content that crosses the corridor boundary. The two platforms have formal territorial divisions in some licensing agreements and informal competition in others. OCS's presence in east reach markets depends partly on the content that Hangang has not licensed exclusively — and Hangang's lapsed-agreement continuation model has kept content active on the platform that, if rights were renegotiated to OCS, would shift competitive balance.
**Byeolbit Entertainment:** Byeolbit is Hangang's largest content production partner and the studio whose original productions anchor the platform's premium subscription tier. The production relationship gives Byeolbit significant leverage over Hangang's content strategy and the platform's subscriber retention. Byeolbit is aware that Hangang's lapsed-agreement policy has kept some Byeolbit-adjacent catalogue active without current agreements, and has chosen not to raise this because the continued activity sustains audience engagement that benefits Byeolbit's brand.
---
## What They Don't Talk About
Approximately 200 titles in Hangang's current active catalogue are being distributed under licensing agreements that have technically lapsed — the agreement term expired and renegotiation has been initiated but not completed. The platform continues streaming these works during the renegotiation period under an internal policy described as "good faith maintenance of distribution pending renewal."
The rights holders whose agreements have lapsed are not informed that their agreements have expired. They are not informed that their work is generating subscription revenue during the lapsed period. The renegotiation correspondence they receive asks them to consider updated terms; it does not note that the content is currently active without a valid agreement.
Hangang's standard service terms include a clause — agreed to by rights holders at initial onboarding — that permits continued distribution under the expired agreement's terms while active renegotiation is underway, and that deems the rights holder to have accepted any distribution revenue during the lapsed period as advance payment against the renewal agreement at the agreed rate. The rate that applies to the "advance payment" calculation is the rate the renegotiation arrives at — which, if the renegotiation results in lower rates than the expired agreement, means the rights holder's lapsed-period revenue is credited at below-expired-agreement rates.
Rights holders who sign the renewal agreement receive a credit note, not cash. Rights holders who decline the renewal discover the credit note applies to a service relationship they have just ended. The clause has survived the two legal challenges that have been filed against it.
---
## Gameplay Relevance
Hangang Studio is media infrastructure in the east reach — the platform appears as a content source in common areas, residences, and transit accommodation, and its preservation archive is a reference resource for cultural investigation. A player researching east reach communities, organizations, or historical events may encounter Hangang's archive as a source of documentary material.
The lapsed-agreement revenue model is the investigative thread. The internal policy document exists. The list of titles in lapsed-agreement active distribution is a platform management record. The credit note accounting for rights holders who renegotiated or declined is in Hangang's financial records. A rights holder who has received a credit note rather than cash and is trying to understand the mechanism is a potential source who can point to the onboarding clause.
The archive function also gives Hangang cultural community relationships that make its staff potential sources on east reach creative industry dynamics.
The lapsed-agreement revenue model is particularly consequential for the estates of deceased artists — the rights holders least likely to be monitoring the platform's activity and most likely to have relied on a previous administrator's understanding of the agreement status. An estate executor who discovers that a family member's work has been generating revenue during a lapsed agreement period, and that the credit note they would receive is calculated at a renegotiated rate the estate never agreed to, faces a legal situation that is difficult to navigate from the outer reach without representation. Hangang's terms were designed for the platform's operational convenience; they produce outcomes for rights holders that a lawyer reviewing them on behalf of an estate would characterize differently than the platform's onboarding framing suggests. A player who can identify one such estate and help it understand its position has a source with standing, time, and motivation.
---
**Cross-References:**
- [Songjiang](../star-systems/GJ-625/index.md) — Headquarters; network infrastructure base
- [Hana Creative](hana-creative.md) — East reach creative peer; visual content licensing overlap
- [Open Corridor Stream](open-corridor-stream.md) — Inward platform peer; distribution comparison context
- [Byeolbit Entertainment](byeolbit-entertainment.md) — East reach entertainment peer; catalogue licensing relationship
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/hangil-celadon.md
+80 -7
View File
@@ -1,24 +1,97 @@
---
title: "Hangil Celadon"
description: "Hangil Celadon — heritage craft manufacturer based in Miryang, east reach"
description: "Miryang traditional celadon pottery manufacturer — Korean ceramic heritage sustained across the generations at the east reach, with a glaze authentication gap between the collector tier and the middle market that the company's marketing does not clarify"
slug: hangil-celadon
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Miryang (GJ 754)
tags: [heritage_craft, east_reach, tractus, artisan]
decision_refs: [D-189]
cross_refs: []
cross_refs: [hangil-celadon, hana-creative, iznik-atelier]
---
# Hangil Celadon
**Type:** Corporation — Heritage Craft Manufacturer
**Type:** Corporation — Traditional Celadon Pottery Manufacturer
**Also Known As:** Hangil
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Miryang (GJ 754)
**Scope:** East reach primary; inward corridor heritage ceramics market secondary
**Headquarters:** Miryang (GJ 754) — east reach, 6 hops from Gateway
**Classification:** Sub-Syndic heritage craft enterprise; traditional celadon production and distribution
Hangil Celadon is a heritage craft manufacturer operating out of Miryang (GJ 754). Details to be expanded.
---
## Overview
Korean celadon is a ceramic tradition with particular requirements: a specific iron-bearing clay body, a specific glaze chemistry producing the pale grey-green color that has defined the form for centuries, and a specific firing process that transforms both into the subtle, luminous surface that separates true celadon from its imitations. Hangil Celadon has maintained this tradition at Miryang for 180 years, across the generations that separate the founding family from their originary culture, through the long transmission of a craft that requires the same materials, processes, and patience as it did in the first generation.
The company produces celadon vessels, plates, tea ware, and decorative objects that are genuine in every technical respect. The founder's descendants learned the craft from the founder; the current master potters learned from them; the celadon produced at Miryang is what celadon is. This is not performance heritage. It is continuous practice.
What has changed, as the market for Hangil's work has grown beyond what the master potters can supply by hand alone, is what "produced at Miryang in the Hangil tradition" means in the middle tier of the product range.
---
## Origin
The founding family arrived at Miryang as skilled-labor settlers in the system's second generation of settlement, already trained celadon potters who brought clay preparation knowledge, glaze chemistry formulas, and kiln construction skills. The decision to establish a production operation was practical — the founding generation recognized that Miryang's geology provided clay and feldspar bodies suitable for celadon production, and that a settled community had uses for beautiful objects that a transit worker life did not accommodate.
The first century of production was small and local. The second century saw export, as east reach systems connected and goods moved across the corridor with increasing regularity. By the time inward markets became aware of Hangil's work — approximately eighty years ago, when a collector at Groombridge encountered a piece at a trading house and acquired it — the celadon was already several generations deep in its Miryang context, not a recreation but a continuous lineage.
---
## Operations
**Collector tier:** Master potter works — individual pieces made entirely by the five senior master potters, hand-formed, hand-glazed with the traditional compound formula, kiln-fired in the original single-chamber kiln. Production is measured in individual pieces per month. Marked with the master potter's personal seal and the Hangil house seal. The objects in this tier are genuinely unique and genuinely expensive.
**Heritage tier:** Production work by Hangil's full pottery staff — twenty-one potters trained in the traditional method. Hand-formed, hand-glazed, kiln-fired. Higher volume than the collector tier; marked with the Hangil house seal and the producing potter's registration mark. This is traditional production at scale.
**Middle tier:** Production pieces made by apprentice potters and junior staff, hand-formed, kiln-fired — but glazed using an industrial spray application process that produces the visual celadon surface through controlled deposition rather than hand-brushing. The visual result is near-identical to hand-glazed pieces under ordinary inspection. Microscopic examination reveals the application pattern. Marketed with language that describes pieces as "crafted in the Miryang tradition" — accurate in terms of form and firing; not accurate in terms of glazing method.
---
## Political Relationships
**Hana Creative:** Hana Creative has produced the visual identity materials and institutional documentation that Hangil uses for its inward market presence, including the catalogue photography and certification presentation that accompanies gallery submissions. The collaboration means Hana's design choices shape how buyers perceive the tier distinctions — or fail to perceive them. Hana has no awareness of the glaze method distinction; its materials accurately represent what the studio was told.
**Iznik Atelier:** Iznik Atelier is the west reach's most significant heritage ceramics producer and Hangil's closest peer in terms of tradition depth and inward market positioning. The two studios are occasionally compared in ceramic collector contexts; the comparison generally favors Hangil's longer unbroken lineage. Whether Iznik Atelier's production methods have their own tier distinctions is a question the Hangil comparison would invite if the spray-glazing situation were publicly examined.
**Lattice Commission:** The Commission's heritage craft authentication framework governs the certification marks that distinguish certified craft from commercial production. Hangil's house seal is registered under this framework. The framework's enforcement mechanism relies on self-certification and periodic audit; the audit protocol does not include microscopic examination of glaze application patterns. The certification structure assumes that what the seal means is what the holder represents it to mean.
---
## What They Don't Talk About
The distinction between the heritage tier and the middle tier — hand-glazed versus industrially spray-glazed — is disclosed in Hangil's product specification sheets, accessible on request from institutional purchasers. It is not disclosed on the pieces themselves. Both tiers carry the Hangil house seal. The marketing language for the middle tier describes the "Miryang tradition" and the "Hangil lineage" without noting which elements of the traditional process apply and which do not.
The middle tier sells at a price point that positions it as heritage craft below the collector tier — not cheap, not mass-produced, something in the register of authentic traditional ceramics that a buyer who cannot afford a collector piece can still acquire with the understanding that they are buying into the Hangil tradition. Whether that understanding is accurate depends on what the tradition is defined to include.
The master potters are aware of the distinction and consider the middle tier a separate market segment that does not compromise the work they do. The buyers in the middle tier market are not told, and cannot determine from the object or its documentation, that the glaze was sprayed rather than brushed. The piece they receive is beautiful, correctly fired, and technically celadon. It was not made the way they understand a Hangil piece to be made.
---
## Gameplay Relevance
Hangil Celadon is cultural heritage presence in the east reach — its pieces appear in private collections, institutional displays, and as high-value traded goods. The brand is known and respected in ceramic-aware contexts across the inner and east corridor.
The glaze method distinction is the investigative thread. The product specification sheets that document the distinction are accessible; the marketing materials that do not mention it are public; the gap is demonstrable. A buyer who acquired a middle-tier piece understanding it to be hand-glazed has the basis of a misrepresentation complaint if they can demonstrate the marketing created that expectation. A ceramics expert who can identify spray application under examination is the technical witness.
Hangil's collector tier pieces also circulate through premium goods channels — galleries, private sales, estate transfers — making the authentication documentation that distinguishes collector tier from heritage tier and middle tier a potential target for forgery or substitution schemes.
The glaze method distinction is also consequential for the institutional buyers who have purchased middle tier pieces as heritage craft for collection or display purposes — government cultural collections, private foundations, and commercial institutions that cite their acquisitions in communications that imply hand-craft provenance. If the spray-glazing distinction becomes public and the "crafted in the Miryang tradition" language is found to imply hand-process to a reasonable buyer, those institutions' acquisitions carry a provenance question. Hangil's exposure in that scenario is not criminal but reputational: the company that has sustained a 180-year ceramic tradition at the outer reach would be understood, in the coverage that followed, as having quietly industrialized the process while marketing the tradition. The master potters themselves — the five who produce the collector tier in the original method — would find the question of what their work is associated with a difficult one. The founding family's relationship to the company's identity is the most consequential casualty of exposure, not the legal liability.
---
**Cross-References:**
- [Miryang](../star-systems/GJ-754/index.md) — Headquarters; pottery tradition; production site
- [Hana Creative](hana-creative.md) — East reach heritage creative peer; cultural context
- [Iznik Atelier](iznik-atelier.md) — Heritage ceramics peer; West reach; comparative craft tradition
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/hanyang-precision.md
+1 -1
View File
@@ -11,7 +11,7 @@ faction_type: economic
headquarters: Changwon (GJ 860B)
tags: [lattice_substrate, electronics, precision_instruments, east_reach, korean, assembly]
decision_refs: [D-175]
cross_refs: []
cross_refs: [kaur-observatory-equipment]
---
# Hanyang Precision Systems
wiki/corporations/hartsteen-legal.md
+83 -7
View File
@@ -1,24 +1,100 @@
---
title: "Hartsteen Legal"
description: "Hartsteen Legal — premium service provider based in Confluent, west reach"
description: "Confluent commercial law firm — west reach contract practice, dispute resolution, and syndicate representation, with undisclosed advisory positions that compromise the firm's conflict clearance for a specific class of client"
slug: hartsteen-legal
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Confluent (GJ 395)
tags: [service_premium, west_reach, mark]
decision_refs: [D-189]
cross_refs: []
cross_refs: [bavarian-craft, bergkraft-antriebswerke, nordhavn-financial]
---
# Hartsteen Legal
**Type:** Corporation — Premium Service Provider
**Type:** Corporation — Commercial Law Firm
**Also Known As:** Hartsteen, the firm
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Confluent (GJ 395)
**Scope:** West reach primary; inward corridor commercial law secondary
**Headquarters:** Confluent (GJ 395) — west reach, 3 hops from Gateway
**Classification:** Sub-Syndic professional services; commercial law, contract, and dispute resolution
Hartsteen Legal is a premium service provider operating out of Confluent (GJ 395). Details to be expanded.
---
## Overview
Confluent is the west reach's closest thing to a commercial hub — not at the scale of Groombridge, but a system with enough commercial activity, enough institutional presence, and enough trade to support professional services of genuine depth. Hartsteen Legal has been the dominant commercial law practice in Confluent for fifty years. Its practice covers the things that commercial activity generates: contract drafting and review, commercial dispute resolution, transactional work for businesses entering or exiting arrangements, and representation in the occasional litigation that reaches the west reach's court systems.
The firm's reputation is technical competence and longevity. Clients who retain Hartsteen get lawyers who know the west reach's commercial law thoroughly, who have managed disputes at every level of the local system, and who have relationships with counterpart firms inward that allow them to handle matters extending beyond the west reach's jurisdiction. This is not glamorous work. It is reliable work, and reliable work is what commercial clients need.
What those clients do not know, because Hartsteen does not publish it, is that several of the firm's senior partners hold advisory positions with trade syndicates they regularly represent against.
---
## Origin
Hartsteen Legal was founded fifty years ago by a lawyer named Brigitte Hartsteen who had come to Confluent as a young advocate from an inward firm and had stayed when she realized that the quality of commercial legal services available locally was significantly below what the commercial activity warranted. Her founding practice was built on commercial contract work — the transactional backbone that enables trade — and expanded into dispute resolution when her contract work generated disputes that clients naturally brought to the same firm that had drafted the agreements.
The firm grew through careful associate hiring and the maintenance of a practice philosophy that the founder imposed: every matter the firm takes, it takes seriously; no client is handled by staff who are not competent to handle them. This standard produced the quality that built the reputation. The firm now has fourteen lawyers, four of whom are partners.
---
## Operations
**Core practice:** Commercial contract drafting and review — the majority of revenue. West reach trade agreements, supply contracts, licensing arrangements, real property transactions, corporate formation and restructuring. Dispute resolution — commercial arbitration and litigation for disputes within the west reach's legal jurisdiction. Inward referral — for matters extending beyond the west reach, maintained referral relationships with three inward firms.
**Client base:** Commercial businesses of all sizes operating in the west reach, including a significant proportion of the manufacturing and trading enterprises at Confluent and adjacent systems. Trade syndicates — the collective commercial organizations that coordinate sector interests in the west reach — represent a significant client segment and the most politically complex one.
**Conflict management:** Standard commercial law practice requires conflict checks before accepting new matters — a review of existing clients to identify whether a new matter creates adverse relationships. Hartsteen conducts these checks. The firm's internal conflict protocol is documented and followed. The protocol relies on a client list that includes direct clients. It does not include advisory positions.
---
## Political Relationships
**Bavarian Craft:** Hartsteen Legal handles Bavarian Craft's regulatory compliance work, including the guild certification documentation that underpins the company's heritage branding. The legal team that produced the bylaw interpretation justifying Bavarian Craft's certification practice is the same team that manages the firm's west reach industrial client portfolio. If the bylaw interpretation is ever challenged formally, Hartsteen's advice is part of the chain — which gives the firm its own interest in the interpretation surviving scrutiny.
**Bergkraft Antriebswerke:** Bergkraft's Series 9 certification situation was reviewed by Hartsteen's industrial law team at the point of the fixture discrepancy decision. The legal analysis — that the discrepancy fell within manufacturing tolerances and did not require resubmission — was produced by Hartsteen. The memo exists in both Bergkraft's files and Hartsteen's matter archive.
**Nordhavn Financial:** Nordhavn Financial is a commercial banking relationship client of Hartsteen's, with the firm handling transactional and dispute work on behalf of Nordhavn's west reach lending portfolio. One of the partners who holds a trade syndicate advisory position also advises Nordhavn on certain regulatory matters — a second concurrent advisory relationship that is likewise absent from Hartsteen's conflict protocol.
---
## What They Don't Talk About
Three of Hartsteen's four partners hold advisory board positions with trade syndicates that are active in the west reach commercial sector. These positions — which involve attendance at quarterly meetings, review of policy positions, and occasional consultation on regulatory and legal matters — are disclosed in the partners' personal ethics disclosures filed with the west reach legal authority. They are not disclosed in client engagement letters. They are not disclosed to opposing parties.
When a client retains Hartsteen to represent them in a commercial dispute with a syndicate, the firm's conflict protocol checks the syndicate against the client list. If the syndicate is not a current client, no conflict is identified. The protocol does not check advisory positions because advisory positions are not in the client database. The partner whose advisory position creates the conflict does not recuse from the matter; the conflict is not surfaced.
Clients who have retained Hartsteen to negotiate against syndicates where a Hartsteen partner sits on the advisory board have been represented by a lawyer who attends the syndicate's quarterly strategic meetings. The lawyer is not consciously betraying the client — the conflict is structural, not active — but the information environment that a lawyer advising a client on strategy is drawing from includes months of syndicate advisory meetings that the client does not know about and that the lawyer cannot fully compartmentalize.
The west reach legal authority's ethics framework requires disclosure of advisory positions in representations where the position is relevant. "Relevant" is a term the framework does not define precisely. Hartsteen's position is that advisory board attendance does not create a conflict unless the specific dispute was discussed at the board, which it generally has not been.
---
## Gameplay Relevance
Hartsteen Legal is professional services background in the west reach — it handles the commercial disputes and contracts of the businesses the player encounters, and its lawyers are social contacts in Confluent's professional community. A player pursuing commercial investigations in the west reach will find Hartsteen referenced in commercial documentation.
The advisory position situation is the investigative thread. The partners' personal ethics disclosures exist in the legal authority's filings — they name the syndicate positions. The client engagement letters, for any matter where a partner held a relevant advisory position, do not reflect corresponding disclosure. A client who discovers the omission while managing the consequences of a negotiation they lost has grounds for a complaint. Whether those grounds are sufficient under the framework's ambiguous "relevant" standard is a legal question that would be resolved by the authority Hartsteen's partners have relationships with.
The firm's archives also document the commercial relationships that have shaped west reach trade over fifty years — contract structures, dispute patterns, and the history of which syndicates have pushed which commercial positions at what times.
The advisory position situation is most consequential for clients who lost disputes against syndicates where a Hartsteen partner held a board advisory role. Whether any of those clients lost because of information their lawyer had and they didn't — or simply lost because the other side was stronger — is not a question the case outcomes answer. It is a question that the outcome, combined with the advisory calendar, makes worth asking. A client who reviews what a Hartsteen partner was discussing at syndicate advisory meetings in the quarter before a negotiation they lost has context that changes the meaning of every piece of legal advice they received during that period. Whether that context translates to a malpractice claim depends on what the advisory meetings covered. The partner's calendar and the meeting minutes are the documents; the client's case file is the comparison. Both exist.
---
**Cross-References:**
- [Confluent](../star-systems/GJ-395/index.md) — Headquarters; primary client base; legal authority jurisdiction
- [Bavarian Craft](bavarian-craft.md) — West reach commercial client; guild certification legal work
- [Bergkraft Antriebswerke](bergkraft-antriebswerke.md) — West reach industrial client; certification dispute exposure
- [Nordhavn Financial](nordhavn-financial.md) — West reach financial peer; commercial relationship context
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/higashiyama-vehicle.md
+84 -7
View File
@@ -1,24 +1,101 @@
---
title: "Higashiyama Vehicle"
description: "Higashiyama Vehicle — precision technology manufacturer based in Kurashiki, east reach"
description: "Kurashiki surface and atmospheric vehicle manufacturer — east reach transit and industrial vehicle production, with a certification test facility that Higashiyama helped design and partially funds, ensuring the tests favor what Higashiyama builds well"
slug: higashiyama-vehicle
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Kurashiki (GJ 205)
tags: [tech_premium, east_reach, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [dalbit-systems, higashiyama-vehicle, kumho-navigation]
---
# Higashiyama Vehicle
**Type:** Corporation — Precision Technology Manufacturer
**Type:** Corporation — Surface and Atmospheric Vehicle Manufacturer
**Also Known As:** Higashiyama, HV
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Kurashiki (GJ 205)
**Scope:** East reach primary; inward corridor vehicle procurement secondary
**Headquarters:** Kurashiki (GJ 205) — east reach, 3 hops from Gateway
**Classification:** Sub-Syndic precision manufacturing enterprise; surface transport and atmospheric vehicle production
Higashiyama Vehicle is a precision technology manufacturer operating out of Kurashiki (GJ 205). Details to be expanded.
---
## Overview
Moving people and goods on the surface of east reach worlds requires vehicles built for the specific conditions those worlds present — variable gravity, atmospheric compositions that corrode standard alloys, terrain that would wreck vehicles designed for Core corridor infrastructure. Higashiyama Vehicle has been manufacturing surface transport and atmospheric vehicles for these conditions from Kurashiki for sixty years, and its product catalogue is the reason east reach planetary operations can run without importing vehicles from inward suppliers who have never been to the systems their products are supposed to work in.
The company's engineering approach is environmental: start with where the vehicle will operate, specify for those conditions, test against them. This sounds obvious. It is not, in practice, as common as it should be. Inward manufacturers who sell into the east reach produce to general specifications that cover a wide range of environments and miss the edge cases specific to outer corridor conditions. Higashiyama's vehicles are not necessarily better in general terms; they are significantly better in the specific terms that east reach operators encounter daily.
The certification framework that validates this is one that Higashiyama had a hand in designing.
---
## Origin
Higashiyama Vehicle was established sixty years ago by an industrial engineer who had spent twenty years maintaining vehicles on Kurashiki's surface operations and had arrived at the same conclusion that outer reach manufacturers consistently arrive at: the equipment being imported was not designed for the actual use environment, and the people using it were absorbing the cost of that mismatch in maintenance hours, downtime, and shortened equipment life.
The founding operation started with agricultural and mining vehicles, where the operational conditions diverged most sharply from inward design assumptions. Early product success established the company's local market position; expansion into atmospheric transport vehicles came fifteen years in, when Kurashiki's growing population needed transit capacity that local operators could maintain without inward technical support. The product range expanded further as the company's engineering capabilities and manufacturing capacity grew.
---
## Operations
**Product lines:** Surface transport vehicles — personnel carriers, cargo movers, and agricultural equipment for planetary surface operations. Atmospheric transit vehicles — lighter aircraft and VTOL transports for inter-site movement across systems without gate infrastructure. Industrial vehicles — heavy equipment for mining and construction applications requiring environmental hardening. Maintenance parts and retrofit kits for vehicles in the installed east reach fleet.
**Manufacturing:** Main facility at Kurashiki, with a secondary production facility at an adjacent system. Combined workforce of four hundred, of whom approximately one hundred are in engineering and technical roles. The facilities produce to order for most institutional clients and maintain a smaller ready-inventory line for standard specifications.
**Certification:** Vehicles for commercial and institutional use require certification under east reach transit authority standards. Higashiyama's products are certified across all applicable categories. The certification process requires independent testing of performance parameters.
**Service:** Regional service network at twelve east reach systems. Maintenance contract clients represent approximately 40% of institutional revenue.
---
## Political Relationships
**Dalbit Systems:** Dalbit's navigation systems are standard integration in Higashiyama's atmospheric and surface transport products. The integration is specified in Higashiyama's vehicle certification documentation — which means Dalbit's hardware is part of the certified configuration that Kurashiki Testing Services tested. The same testing body that Higashiyama helped design the protocols for also certified Dalbit-equipped Higashiyama vehicles. The layered relationship between the two companies runs through a testing institution that both benefit from.
**Kumho Navigation:** Kumho Navigation is the east reach competitor whose products perform differently from Dalbit's in the edge cases that Kurashiki Testing Services' protocols don't cover. Kumho has raised protocol coverage concerns with the transit authority and been unable to advance them through a committee process where Higashiyama participates. Kumho does not know that Higashiyama contributed 40% of the testing body's founding capital.
**Lattice Commission:** The Commission's certification framework for east reach vehicles accepts regional transit authority certification as sufficient for corridor-wide recognition. Kurashiki Testing Services' certifications therefore carry Commission recognition without Commission audit. The Commission's regional certification acceptance policy assumes that regional bodies are independent of the manufacturers they certify — an assumption the Higashiyama founding capital relationship does not support, though it has not been examined.
---
## What They Don't Talk About
The certification body that issues performance certifications for east reach surface and atmospheric vehicles is Kurashiki Testing Services — an independent organization established twenty years ago as the east reach transit authority's preferred certification facility. Its independence is genuine in structure: it is not owned by any vehicle manufacturer, its board includes transit authority representatives and public members, and its certification results have never been challenged by the Lattice Commission.
Higashiyama Vehicle provided 40% of the founding capital for Kurashiki Testing Services when it was established, through an industry development contribution that the transit authority solicited from major regional manufacturers. The founding capital contribution gave Higashiyama a role in the facility's founding governance — specifically, in the working group that developed the initial testing protocols for surface and atmospheric vehicles.
The testing protocols that Kurashiki Testing Services uses today are built from the working group's recommendations. They are thorough, technically sound, and comprehensive across the parameter ranges that Higashiyama's vehicles perform well in. The edge cases that testing protocols do not cover — specific combinations of atmospheric composition and thermal load, lateral stability at grade angles above typical terrain, power management under sustained partial-atmosphere conditions — are edge cases where Higashiyama's design philosophy makes different tradeoffs than some competing manufacturers. These tradeoffs would not favor Higashiyama under testing that evaluated them. The current testing framework does not evaluate them.
Competing manufacturers whose vehicles perform better in the untested edge cases have noted the absence and have been unable to raise the issue through the transit authority's protocol review process, which Higashiyama participates in as an industry stakeholder.
---
## Gameplay Relevance
Higashiyama Vehicle is industrial background presence in the east reach — its vehicles are the surface transport at planetary operations, the atmospheric transports between settlements, the industrial movers in mining facilities. A player on a planetary east reach surface will encounter Higashiyama vehicles without necessarily noting the brand.
The testing protocol design is the investigative thread. The founding capital contribution and working group participation are documented in Kurashiki Testing Services' founding records and governance documentation. The current protocols are public documents. A competing manufacturer who can specify the edge cases the protocols don't cover and demonstrate that their products perform better in those cases has the substance of a complaint to the transit authority; the question is whether the authority's review process is susceptible to that complaint when Higashiyama participates in the review.
The service network also gives Higashiyama visibility into the operational patterns of east reach industrial and transit operations.
The certification body conflict is structurally difficult to prosecute because the testing protocols are technically sound within their scope and because the protocol review process is designed for incremental improvement rather than challenge. A competing manufacturer who wants the edge cases added to the test suite must raise the request through the Kurashiki Testing Services protocol committee — on which Higashiyama participates as an industry stakeholder. The most viable route is the transit authority's oversight panel, which sits above the committee and has authority to mandate protocol review. Getting the authority's attention requires demonstrating that the current protocols produce materially different safety outcomes for the untested scenarios than the tested ones — a technical argument that requires independent testing of the competing manufacturer's vehicles in the untested conditions, which requires financing and access to frontier operational environments where those conditions occur. A player with resources and access can build this case; a player without them is working a slow administrative dispute against an institutional structure that has incentives to stay where it is.
---
**Cross-References:**
- [Kurashiki](../star-systems/GJ-205/index.md) — Headquarters; manufacturing facilities; testing services
- [Dalbit Systems](dalbit-systems.md) — East reach technology peer; navigation systems in Higashiyama vehicles
- [Kumho Navigation](kumho-navigation.md) — East reach navigation peer; vehicle integration client
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/highland-cooperative.md
+85 -7
View File
@@ -1,24 +1,102 @@
---
title: "Highland Cooperative"
description: "Highland Cooperative — regional specialty producer based in Crown's Hollow, north reach"
description: "Crown's Hollow specialty agricultural cooperative — north reach terroir products governed as a democratic collective of independent producers, with a voting structure that gives the two largest members effective veto power they have been quietly using for a decade"
slug: highland-cooperative
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Crown's Hollow (GJ 661A)
tags: [terroir, north_reach, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [aldgate-trust, calloway-distillery, brindlewood-honey]
---
# Highland Cooperative
**Type:** Corporation — Regional Specialty Producer
**Type:** Corporation — Specialty Agricultural Cooperative
**Also Known As:** the Cooperative, Highland
**Status:** Canonical
**Scope:** Regional — north reach operations
**Headquarters:** Crown's Hollow (GJ 661A)
**Scope:** North reach primary; inward corridor specialty food market secondary
**Headquarters:** Crown's Hollow (GJ 661A) — outer north reach, 7+ hops from Gateway
**Classification:** Sub-Syndic agricultural collective; specialty terroir product production and distribution
Highland Cooperative is a regional specialty producer operating out of Crown's Hollow (GJ 661A). Details to be expanded.
---
## Overview
Crown's Hollow's cold-climate agricultural tradition produces specialty goods that could not be grown anywhere else in the corridor: heritage grain varieties adapted over centuries to the system's short growing season, cured and preserved products whose process was developed to work within the constraints of limited storage infrastructure, and a small collection of botanical preparations unique to the native flora of the system's highland terrain. These goods move inward as curiosities and premium imports; they move outward as practical trade goods and the kind of accumulated cultural production that outer reach communities develop when generations have adapted to a specific place.
Highland Cooperative is the organization through which Crown's Hollow's specialty agricultural producers collectively bring their goods to market. It manages shared distribution infrastructure, collective branding, and the pricing negotiations that individual small producers would be unable to conduct on equivalent terms. It represents approximately forty families, the smallest of which operates a holding of a few hectares and the largest of which controls a substantial fraction of the system's cultivated land.
The democratic framing under which it operates is accurate on paper. The voting structure it uses is the reason the democratic framing does not function as described.
---
## Origin
Highland Cooperative was established sixty years ago by a group of fifteen farming families who had concluded that the absence of coordinated marketing was costing them individually more than the cost of coordination would be. Each family selling its own goods to transit traders produced prices set entirely by the traders; a collective organization with negotiating leverage and shared distribution infrastructure would shift the balance.
The founding governance documents established voting rights proportional to production volume — the larger the holding, the more votes. This was rationalized as fairness to the families who took larger risks and invested more capital in the collective's shared infrastructure. In the founding era, no family held more than three times the volume of any other; the proportional structure did not produce meaningful power asymmetry.
Over sixty years, the distribution of holdings has shifted. Inheritance consolidation, strategic purchase, and two significant acquisitions by the founding period's most successful families have produced a situation where two families together hold approximately 42% of total production volume and, therefore, approximately 42% of total votes.
---
## Operations
**Production:** Approximately forty active producer members. Products include heritage grain and grain products, cured meat and preserved proteins, highland botanical preparations (teas, tinctures, preserved specimens), and seasonal items that vary by member. The variety is genuine; the Cooperative does not standardize what its members produce, only how they bring it to market.
**Collective infrastructure:** Shared cold storage and processing facilities owned by the Cooperative. Shared distribution logistics — cargo aggregation for outbound transit and coordination with inward traders who visit Crown's Hollow on the specialty goods circuit. A shared quality certification program administered by the Cooperative.
**Pricing governance:** Collective pricing decisions made through member vote. The vote weight is proportional to production volume. Major pricing decisions require a 50% majority of vote weight.
**External relationships:** Distribution agreements with inward specialty food traders. A licensing relationship with an inward premium food importer. The Cooperative's collective branding is what gives its members access to premium market positioning that their individual scale would not support.
---
## Political Relationships
**Aldgate Trust:** Several Highland Cooperative members have agricultural holdings under Aldgate Trust's estate management. Aldgate's custody relationships give it visibility into the financial health of individual member operations — which members are distressed, which are carrying debt against their holdings, which are likely to reduce production volume in coming years. This information is not shared with the Cooperative, but it shapes which estates might be candidates for the Trust's 14(c) administrative authority in ways that intersect with the Cooperative's own governance dynamics.
**Calloway Distillery:** Calloway Reach's distillery trade and Highland Cooperative's specialty food production exist in the same north reach outer corridor economic ecosystem. Several Highland members supply grains and botanicals to the smaller Calloway distilleries; the supply relationships are individual rather than collective, but they make the Cooperative's member welfare directly connected to the distilleries' economic health. A governance crisis at the Cooperative would propagate into the distillery supply chain.
**Brindlewood Honey:** Brindlewood Honey is the north reach specialty food producer that has most successfully established inward premium market positioning — the benchmark that Highland Cooperative members reference when discussing their own export strategy. The Cooperative's distribution committee has studied Brindlewood's model extensively. Several members have proposed that the Cooperative adopt a similar managed-scarcity production constraint. The two large members who control the pricing governance have not supported this, because managed scarcity would require reducing their own production volume.
---
## What They Don't Talk About
The two families that together hold 42% of the Cooperative's voting weight have, over the past decade, coordinated their votes before the Cooperative's quarterly pricing meetings. The coordination is informal — a conversation, shared expectations — and is not documented. The effect is that on any pricing decision requiring a 50% majority, these two families need to persuade only a handful of smaller members to achieve a majority. On questions where the smaller members are divided, the two families' aligned block determines the outcome.
The smaller members of the Cooperative know that the large members vote similarly. They do not know — because the conversation is not visible to them — that the voting is coordinated in advance rather than arrived at through the meeting's deliberation. They accept that larger producers have more votes because they accepted the founding governance structure. They accept pricing decisions that favor the large producers' interests because they have consistently lost the votes that would change them, and because the collective distribution infrastructure the Cooperative provides is something they cannot replicate individually.
Three years ago, the Cooperative's pricing committee recommended increasing the price floor for highland botanical preparations — a category where smaller members are disproportionately represented. The recommendation failed at the membership vote by exactly the margin that the two large families' coordinated block supplied. The botanical producers have attributed the failure to the large members' disinterest in a category they don't produce. The reason was not disinterest.
---
## Gameplay Relevance
Highland Cooperative is community and agricultural sector texture in the outer north reach — its brand appears on specialty goods at inward premium markets, its members are part of Crown's Hollow's social fabric, and its governance disputes are the kind of community friction that outer reach settlements accumulate over decades.
The voting coordination is the investigative thread. The informal coordination is not documented, but its pattern is visible in the voting record — a decade of aligned votes from two families on contested pricing decisions, cross-referenced against the outcomes for the categories those families do and don't produce. The botanical producers who have experienced the pattern without understanding it are potential sources. A governance dispute that reaches the Lattice Commission's cooperative oversight function would require demonstrating that the informal coordination constitutes a breach of the fiduciary duty members owe each other — a legal question with a contested answer.
The Cooperative's connection to Aldgate Trust — which manages estates for several of its member families — creates a secondary thread: an estate management relationship that intersects with the governance structure.
The voting coordination is most consequential for the botanical producers, who are the smallest and least individually viable of the Cooperative's membership. Their products occupy a premium niche that the Cooperative's collective branding makes accessible to inward markets; without the branding, their individual scale would not support inward distribution at all. They are therefore the members with least practical ability to exit the Cooperative in response to governance outcomes they object to — which is the same characteristic that makes them the most exploitable by a governance structure where they are perpetually outvoted. A player mediating a governance dispute or tracing the economic conditions of outer reach specialty producers will find in the Highland Cooperative a case study in how collective organization can simultaneously protect and constrain its smallest participants. The founding families who designed the volume-weighted governance structure were not anticipating the concentration of holdings that the following sixty years would produce; the structure they built for equity has produced the opposite.
---
**Cross-References:**
- [Crown's Hollow](../star-systems/GJ-661A/index.md) — Headquarters; member holdings; community context
- [Aldgate Trust](aldgate-trust.md) — Crown's Hollow fiduciary services; member estate management
- [Calloway Distillery](calloway-distillery.md) — North reach cooperative peer; analogous governance dynamics
- [Brindlewood Honey](brindlewood-honey.md) — North reach specialty producer; outer reach terroir market context
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/iberian-standard-foods.md
+78 -6
View File
@@ -1,24 +1,96 @@
---
title: "Iberian Standard Foods"
description: "Iberian Standard Foods — consumer goods manufacturer based in Caparica, south reach"
description: "Caparica-based packaged foods manufacturer serving the south reach corridor — branded commodity lines, affordable pricing, and a protein certification dispute no one has examined closely"
slug: iberian-standard-foods
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Caparica (GJ 1002)
tags: [commodity_branded, south_reach, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [alentejo-partners, destilaria-confluencia, mercado-travessia]
---
# Iberian Standard Foods
**Type:** Corporation — Consumer Goods Manufacturer
**Also Known As:** Iberian Standard, ISF
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Caparica (GJ 1002)
**Scope:** South reach corridor primary; limited inward distribution secondary
**Headquarters:** Caparica (GJ 1002) — 3-aperture hub, 4 hops from Gateway
**Classification:** Sub-Syndic consumer goods enterprise; branded commodity operations
Iberian Standard Foods is a consumer goods manufacturer operating out of Caparica (GJ 1002). Details to be expanded.
---
## Overview
In the south reach corridor, Iberian Standard Foods occupies the kind of market position that invites neither enthusiasm nor complaint: it is simply what the shelves contain. Packaged proteins, shelf-stable prepared meals, grain-derived staples, and condiment lines under four brand names — all of them priced at accessible points, all of them present from Caparica outward to the corridor's less-served stations. The company does not pursue premium positioning and does not need to. Volume is the business. Presence is the strategy.
The public brand voice is dependable and quietly proud — "Reach-grown ingredients, Caparica craft" appears on packaging materials and in the company's regulatory filings as a positioning statement. For most consumers in the south reach, ISF products represent reliable basic nutrition at manageable cost. The brand does not promise luxury. It promises adequacy, consistently delivered, and it has kept that promise across four decades of operation.
---
## Origin
Iberian Standard Foods was established at Caparica forty-two years ago by a food processing cooperative that had been operating informally for a generation before that. The cooperative's original business was buying surplus agricultural output from Caparica's farming districts and converting it into packaged goods that could be shipped outward without spoilage. The formalization into a registered corporation was driven primarily by the need to satisfy Lattice Commission hygiene and labeling standards for multi-system distribution.
The transition from cooperative to corporation introduced the branded product architecture that defines ISF today. What had been generic surplus processing became four distinct consumer lines differentiated by packaging and positioning: a premium tier for institutional buyers, a standard tier for general retail, a bulk tier for station commissaries, and a children's line developed in response to a Caparica government nutrition initiative. The children's line remains the company's most visible brand, appearing in school distribution programs across three south reach systems.
---
## Operations
**Product lines:** Shelf-stable proteins marketed as "Reach-grown" — the specification being that the primary raw materials were purchased from agricultural suppliers within the south reach corridor. Grain-based staples under the Iberian Standard mark. Condiment and sauce lines under the subsidiary brand Caparica Table, which carries stronger provenance marketing. The children's nutrition line under the Alentejo Kids brand, distributed partly through institutional channels.
**Manufacturing:** Two facilities at Caparica, one at Velha Guarda operating under a licensing agreement. The Caparica facilities handle the majority of production. Ingredient sourcing is managed through long-term supply agreements with Alentejo Partners and several smaller agricultural cooperatives.
**Distribution:** Mercado Travessia is the primary distribution partner for inward-corridor placement. For south reach distribution, ISF maintains its own logistics relationships with station commissaries and the regional retail networks at Mwangaza and Karoo.
**Workforce:** Approximately 340 people across production, logistics, and administration. The production workforce is heavily concentrated at the two Caparica facilities, with seasonal variation linked to agricultural supply cycles.
**Certification:** All product lines are certified under Lattice Commission food safety and labeling standards. The "Reach-grown" ingredient claim appears on regulatory filings and is the basis for the southern corridor provenance designation that ISF uses in its institutional distribution contracts.
---
## Political Relationships
**Alentejo Partners:** ISF's primary agricultural supply relationship, covering grain, legume, and secondary crop inputs. The long-term supply agreements are standard in their structure, but ISF's volume is large enough that Alentejo's production planning is partly driven by ISF's forecasting. When ISF's demand projections change, Alentejo's farmers feel it.
**Caparica government:** The children's nutrition line distribution through Caparica's school system was established under a government procurement contract that ISF has held for eleven years. The contract specifies nutritional standards for the products distributed. The certification categories used in the contract's nutritional specifications are the same categories used in ISF's Lattice Commission filings — which means the grandfather provision the company is relying on also covers the school distribution contract's compliance claims.
**Mercado Travessia:** ISF's relationship with Mercado Travessia is the company's only significant inward corridor distribution relationship. Mercado handles the product at the premium end of the ISF range — specifically the Caparica Table condiment line, which is positioned as a provenance product at inward distribution points rather than as a standard commodity line.
---
## What They Don't Discuss in Regulatory Filings
The protein base that underpins ISF's flagship packaged meal line is classified in their Lattice Commission filing as "plant-derived compound protein" — a category that was established under regulations drafted before the Commission's Nutrition Standards Review of twelve years ago. At the time of the Review, the category was flagged for redefinition because several proteins produced from novel substrate fermentation processes had been placed into it under technical readings that the Review board considered overly broad.
ISF's primary protein source is a fermentation-derived substrate that qualifies under the old classification by meeting a molecular weight criterion that the Review was intended to move away from as the sole test. The Review's updated standards were implemented with a five-year grandfather provision for existing certified products. ISF applied for and received renewal of their existing certification before the grandfather window closed.
The substantive issue is that the updated standards would require ISF to relabel the flagship line with a classification consumers typically associate with synthetic food supplements rather than "Reach-grown" staples. ISF's regulatory team is aware that the Commission's next scheduled classification audit, due in approximately three years, will examine whether grandfathered certifications were renewed in compliance with the Review's intent. The legal team has assessed the renewal as technically defensible under the letter of the grandfather provision and has not recommended proactive relabeling.
---
## Gameplay Relevance
Iberian Standard Foods is ambient commercial infrastructure — present on shelves wherever the player is in the south reach, useful as a background institution when investigating food supply chains, agricultural contracting, or nutritional policy. The company's distribution relationships with Mercado Travessia create a natural thread between south reach agricultural politics and inward consumer markets.
The certification dispute is the primary investigative thread. A player with access to Lattice Commission regulatory archives could trace the protein classification history and identify the gap between the "Reach-grown" marketing and the substrate's actual origin. The renewal documentation is in the Commission's public record; the internal legal assessment that recommended not relabeling is in ISF's internal compliance files. The gap between the two documents is the story.
---
**Cross-References:**
- [Caparica](../star-systems/GJ-1002/index.md) — Headquarters system; primary manufacturing base
- [Alentejo Partners](alentejo-partners.md) — Primary agricultural supply relationship
- [Destilaria Confluência](destilaria-confluencia.md) — Caparica corridor neighbor; comparable south reach brand
- [Mercado Travessia](mercado-travessia.md) — Inward distribution partner
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/incheon-salt.md
+77 -6
View File
@@ -1,24 +1,95 @@
---
title: "Incheon Salt"
description: "Incheon Salt — regional specialty producer based in Changwon, east reach"
description: "East reach mineral salt producer operating from Changwon's rare brine geology — premium provenance product with a blending practice that the certification language was never written to catch"
slug: incheon-salt
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Changwon (GJ 860B)
tags: [terroir, east_reach, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [koryo-standard, kumho-navigation]
---
# Incheon Salt
**Type:** Corporation — Regional Specialty Producer
**Also Known As:** Incheon, Changwon Brine
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Changwon (GJ 860B)
**Scope:** East reach primary; inward premium market secondary
**Headquarters:** Changwon (GJ 860B) — 2-aperture system, 5 hops from Gateway
**Classification:** Sub-Syndic specialty producer; provenance-designated scarcity product
Incheon Salt is a regional specialty producer operating out of Changwon (GJ 860B). Details to be expanded.
---
## Overview
Salt is not rare. Salt is one of the most ordinary commodities in the Reach, produced in industrial volumes at half a dozen systems and shipped in bulk to wherever food preservation or chemical processing requires it. What Incheon Salt sells is not ordinary salt. It is a specific mineral composition drawn from a specific brine formation at Changwon — a deep geological structure whose chemistry produces a crystalline product with trace mineral ratios that food preparers across the east reach have spent three centuries learning to cook with. The pale amber crystals and the particular sharpness they give to preserved proteins are recognizable. Cooks who grew up in the east reach corridor recognize the taste; when they encounter it inward, they pay for it.
The company positions itself accordingly. Incheon Salt's branding materials use the phrase "Changwon Brine" as though it were a protected designation of origin — the imagery is geological, ancient, specific. Premium product tiers carry provenance certificates describing the extraction depth, mineral assay, and seasonal batch number. Institutional buyers — restaurant groups, food processors, specialist importers — treat these certificates as meaningful. They pay the premium because the premium is justified, and the distinction is real.
---
## Origin
The Changwon brine formation was identified and mapped by a geological survey team ninety years ago. The first commercial extraction operation was established twenty years after the survey, when a small family enterprise at Changwon's primary settlement obtained extraction rights and began selling direct to the east reach corridor market. The product's reputation built slowly and then quickly — the moment a Jeonnam food preparer mentioned the salt in a published recipe that circulated across three systems, the market demand jumped sharply beyond what the original operation could supply.
Incheon Salt as a corporate entity was formed when a consortium of east reach investors bought the original family operation and expanded extraction capacity. The founding family retained a minority stake and operational management roles that they hold to this day. The corporate structure allowed investment in extraction equipment and distribution logistics that the family operation could not have funded; the family's continued involvement preserved the operational knowledge and the relationships with the geological survey teams that manage extraction permitting.
---
## Operations
**Extraction:** The brine formation produces several hundred tonnes of raw mineral salt per year from the accessible extraction points. This is a small volume by industrial salt standards but a substantial volume for a provenance product. The extraction process is carefully managed to avoid contaminating the brine composition — industrial techniques would increase volume but change the mineral ratios that define the product's character.
**Product tiers:** The premium line — sold under the "Changwon Brine" mark with provenance certificates — commands prices an order of magnitude above commodity salt. A mid-range line without full provenance documentation sells at a lower premium to food processors and commercial buyers. A bulk line without the Incheon Salt brand name is sold to Koryo Standard and other east reach manufacturers for use as an ingredient in their own products.
**Distribution:** East reach direct to specialist food retailers and institutional buyers. Inward markets through a distribution agreement with a Kurashiki-based importer who handles the premium tier's inward corridor placement.
**Workforce:** Small — fewer than sixty people, including extraction, processing, quality control, and the assay team that produces the provenance documentation.
---
## Political Relationships
**East reach corridor food industry:** Incheon Salt's premium positioning makes it a reference point for east reach culinary provenance products generally. The company has informal relationships with other east reach specialty producers and participates in the regional food producers' association where collective advocacy on provenance designation frameworks happens. This association is also where industry peers would most easily notice a provenance discrepancy, which is one reason Incheon Salt's management stays attentive to its association relationships.
**Lattice Commission provenance desk:** The "Changwon Brine" designation appears on Incheon Salt's product labeling but has no statutory definition in Commission standards — the Commission's provenance framework for specialty salts predates the east reach corridor's development and was written for inward systems. Incheon Salt's labeling team wrote the "Changwon Brine" definition in their own marketing materials and regulatory filings, and the Commission accepted it without formal review because no competitor had contested it. This self-defined designation is the legal structure the blending practice depends on.
---
## What the Assay Certificates Don't Disclose
The premium tier is genuine. The mid-range tier is where the question lives.
Incheon Salt's mid-range product line — sold without full provenance certificates but bearing the Incheon Salt mark and Changwon origin labeling — is produced by blending Changwon brine extract with industrial mineral salt purchased from a commodity supplier at a system three hops outward. The blend ratio is approximately 40% Changwon extract to 60% commodity material. The resulting mineral profile is within acceptable variation of the pure product and is indistinguishable to most buyers.
The "Changwon Brine" designation that Incheon Salt defined in its own regulatory filings does not specify a minimum origin-content percentage. The definition describes a mineral profile and a processing method, not an origin purity threshold. This was not accidental — the definition was written after the blending practice began, at a point when the operational team had already determined that pure-origin production could not meet mid-range demand volumes. The definition's language is technically accurate: the mid-range product does exhibit the described mineral profile, because the blend is designed to produce it.
Buyers who purchase the mid-range line under the Incheon Salt brand are paying for a product they believe to be Changwon-origin salt. The documentation they receive does not state that it is a blend.
---
## Gameplay Relevance
Incheon Salt is a secondary institution in the east reach corridor — relevant whenever the player is working in food commerce, supply chain investigation, or provenance fraud. The blending practice is investigative material with clear evidence: production records, procurement invoices for the commodity salt, and the assay certificates that describe the mineral profile without disclosing the blend ratio. The gap between the origin labeling and the procurement records is the thread.
The provenance designation framework question — that Incheon Salt wrote its own definition — is a secondary angle with broader implications. If one east reach specialty producer has an uncertified self-defined provenance mark, others may as well. A player following that thread enters the politics of the east reach food producers' association and the Commission's provenance desk.
---
**Cross-References:**
- [Changwon](../star-systems/GJ-860B/index.md) — Headquarters; brine formation location; extraction zone
- [Koryo Standard](koryo-standard.md) — Bulk salt purchaser; ingredient supply relationship
- [Kumho Navigation](kumho-navigation.md) — Changwon corridor neighbor; east reach institutional context
- [Kyoto Valley Estates](kyoto-valley-estates.md) — East reach provenance product parallel; comparable self-defined designation
- [Jeju Lattice](jeju-lattice.md) — East reach industrial neighbor; Yeongwol corridor context
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/ironbark-films.md
+77 -6
View File
@@ -1,24 +1,95 @@
---
title: "Ironbark Films"
description: "Ironbark Films — cultural content producer based in Fremantle, north reach"
description: "Fremantle-based production studio serving the north reach corridor — documentary work, cultural programming, and an unexercised archive rights option that would give them total control over a community's oral history"
slug: ironbark-films
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Fremantle (GJ 273)
tags: [cultural, north_reach, tractus, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [ashwick-broadcasting, calloway-distillery]
---
# Ironbark Films
**Type:** Corporation — Cultural Content Producer
**Also Known As:** Ironbark
**Status:** Canonical
**Scope:** Regional — north reach operations
**Headquarters:** Fremantle (GJ 273)
**Scope:** North reach corridor primary; limited inward distribution secondary
**Headquarters:** Fremantle (GJ 273) — 2-aperture system, 5 hops from Gateway
**Classification:** Sub-Syndic cultural enterprise; documentary and narrative production
Ironbark Films is a cultural content producer operating out of Fremantle (GJ 273). Details to be expanded.
---
## Overview
Ironbark Films is the north reach's most credible production house for documentary and cultural content. The company's output over forty years of operation covers the corridor's human history in depth: the agricultural migrations of the first generations, the political evolution of north reach governance structures, the settlement patterns of communities that arrived with distinct cultural identities and produced new ones. Institutional buyers, educational bodies, and cultural archives across the corridor hold Ironbark licenses. The work is substantive.
The studio's public positioning leans on this record consistently and accurately. When Ironbark Films pitches to funders, applies for cultural production grants, or discusses production partnerships with north reach institutions, the forty-year documentary archive is the credential. The studio presents itself as a custodian of corridor memory. That framing is sincerely held by many of the people who work there and is not purely instrumental.
---
## Origin
Ironbark Films was founded at Fremantle by a group of journalists and documentary producers who had been working for Ashwick Broadcasting and found the broadcast format inadequate for the kind of long-form work they wanted to produce. The founding agreement was that the studio would operate as an independent production entity selling to broadcasters, archives, and direct institutional clients rather than being embedded in any single broadcast organization.
The early productions were modest — regional history commissions for Fremantle's local government, documentary work about the agricultural cooperatives that had shaped Calloway Reach culture during the corridor's formative period. These productions required negotiating archive access and interview rights with communities that had not previously been the subject of documentary attention. The studio's early reputation for respectful community engagement was built during this period and is not fabricated.
What changed the studio's scale was a series of oral history commissions in the second decade of operation, during which Ironbark acquired extensive rights to recorded materials — interviews, cultural performances, privately held visual archives — from communities across the north reach corridor. The acquisition contracts of that era were drafted at a time when community understanding of rights transfer was limited. Communities often signed agreements that transferred broad rights to recorded materials in exchange for production fees that seemed substantial at the time.
---
## Operations
**Production:** Ongoing documentary and cultural content production with an average of four to six long-form projects in various stages of development at any given time. The studio employs a core creative staff of approximately thirty-five and contracts substantially for specific productions.
**Archive:** The Ironbark archive is the studio's most significant asset — a collection of recorded materials spanning forty years of north reach cultural documentation. The archive is licensed to educational institutions, broadcasters, and cultural bodies. License fees provide a stable secondary revenue stream that the studio's public materials describe as "supporting ongoing production."
**Distribution:** Documentary and cultural content distributed through Ashwick Broadcasting under a long-standing first-look agreement. For materials that Ashwick passes on, Ironbark maintains its own distribution relationships with inward corridor educational distributors.
**Community relationships:** The studio maintains formal consultation protocols for productions involving living communities. These protocols were introduced fifteen years ago, partly in response to criticism from communities who felt their materials had been appropriated without adequate representation in the resulting work.
---
## Political Relationships
**Fremantle cultural institutions:** Ironbark Films occupies a comfortable position in Fremantle's cultural establishment — board seats at the local arts foundation, advisory roles in cultural policy discussions, a relationship with the corridor's educational administration. This institutional position generates commission work and protects the studio's grant eligibility.
**Community documentation relationships:** The communities who provided the oral history materials in the studio's archive have varying relationships with Ironbark today. Some maintain active consultation relationships and value the access the studio provides to their documented histories. Others have expressed concerns about license terms and access fees that they feel prevent their own communities from using materials they originally provided. These concerns have not resulted in formal disputes.
---
## What Stays in the Rights Database
Among the materials Ironbark Films acquired during the oral history commissions of its second decade is a collection of recordings from a now-deceased cultural historian who spent her life documenting the traditions of a small north reach community — an oral tradition of navigational knowledge, astronomical interpretation, and settlement ceremony that the community considers foundational to its identity.
The rights contract, signed before her death, included a standard clause giving Ironbark an option on her "life-rights archive" — meaning all additional materials the historian had accumulated but not yet delivered under the commission. The historian produced far more than she had been commissioned for. The undelivered archive was transferred to Ironbark's possession as part of her estate settlement, under the option clause, in exchange for a modest payment to her estate.
The community believes this archive is publicly held. The oral tradition it documents is understood within the community to belong to the community. Ironbark has not told them otherwise. The studio has not exercised the option in the sense of actively commercializing the materials — the archive sits in Ironbark's rights database, licensed for educational use under terms the community has not been consulted on. The option itself, which grants Ironbark exclusive commercial rights to the most complete documented record of the community's foundational tradition, has never been disclosed to the community.
The studio's legal team reviewed the contract eight years ago when a community representative inquired about accessing the full archive. The review confirmed that the contract is valid under the law that governed it. The studio provided the representative with access to the commissioned materials and did not mention the option.
---
## Gameplay Relevance
Ironbark Films is a secondary institution for investigation into cultural rights, archive access politics, and the ethics of documentary production. The studio is well-connected enough in the north reach that a player working cultural or political threads in the corridor will encounter its output and reputation.
The archive rights option is the primary investigative thread. The evidence exists: the original contract, the estate settlement, the rights database entry, and the community's public statements about the archive's status. The gap between what the community believes and what the contract says is documented in Ironbark's legal files. A player who surfaces this information faces a situation where the studio's wrongdoing is technically legal — which makes what to do with the information a meaningful choice.
---
**Cross-References:**
- [Fremantle](../star-systems/GJ-273/index.md) — Headquarters system; primary production base
- [Ashwick Broadcasting](ashwick-broadcasting.md) — Distribution partner; first-look agreement
- [Calloway Distillery](calloway-distillery.md) — Early documentary subject; corridor cultural parallel
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/iznik-atelier.md
+78 -6
View File
@@ -1,24 +1,96 @@
---
title: "Iznik Atelier"
description: "Iznik Atelier — heritage craft manufacturer based in Groombridge, core"
description: "Groombridge-based ceramic and tile studio producing premium heritage craft for institutional clients — four centuries of aesthetic tradition, a provenance authentication system with an exploitable flaw, and two forgery settlements no one discusses"
slug: iznik-atelier
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Groombridge (GJ 380)
tags: [heritage_craft, core, tractus, artisan]
decision_refs: [D-189]
cross_refs: []
cross_refs: [alcyone-tech, the-registry, groombridge-settlement-house]
---
# Iznik Atelier
**Type:** Corporation — Heritage Craft Manufacturer
**Also Known As:** The Atelier, Iznik House
**Status:** Canonical
**Scope:** Regional — core operations
**Headquarters:** Groombridge (GJ 380)
**Scope:** Core primary; reach-wide institutional commissions secondary
**Headquarters:** Groombridge (GJ 380), Lendel district — 2-aperture loop_member
**Classification:** Sub-Syndic artisan enterprise; sole-source institutional supplier for specific aesthetic categories
Iznik Atelier is a heritage craft manufacturer operating out of Groombridge (GJ 380). Details to be expanded.
---
## Overview
In the institutional buildings of Groombridge and throughout the core corridor, Iznik Atelier's tiles and ceramics are visible on walls that were meant to communicate permanence. Financial houses commission entrance hall panels. Legal institutions order courtroom tile work specified to a tradition that references continuity and authority. Private clients at Groombridge's wealthier residential tiers specify kitchen installations that reference four centuries of craft lineage. Iznik Atelier makes all of these things and has been making them from the same Lendel district workshop for three generations.
The aesthetic tradition the studio draws on originated in the pre-migration cultures of the founding populations that settled Groombridge. The specific geometric patterns, glaze chemistry, and tile formats that define Iznik Atelier's recognizable work are documented in the studio's own published materials with references to historical precedent that read as scholarly. The studio's position is that it is not merely producing decorative objects — it is maintaining a living craft tradition. This argument is made sincerely by the people in the studio who are trained artisans and make it sincerely. It is also extremely good marketing.
---
## Origin
The Atelier was founded three generations ago by a ceramic artist named Halide Çevik, who had trained under the last working practitioner of a tile-making method that had survived corridor travel through a single lineage. Çevik's innovation was not the craft itself but the organizational decision to document the method, train apprentices systematically, and market the work to institutional clients who were building or renovating permanent structures. The founding generation took twelve years to receive its first major institutional commission; by the time Çevik retired, the studio had a twenty-year waiting list for certain commission formats.
The current generation of leadership is Çevik's grandchildren, two of whom are working artisans and one of whom manages the business. The craft knowledge is genuinely transmitted through the workshop; there are currently nine trained artisans at various levels of the apprenticeship structure, each of whom has spent years learning the specific hand techniques that produce the studio's distinctive output.
---
## Operations
**Production tiers:** The premium commission work — large-format architectural installations, institutional panels, significant residential commissions — is executed by the trained artisans under close supervision and constitutes approximately 30% of the studio's output by value. The remainder is produced on a manufacturing line that handles tile formats whose dimensions and glaze chemistry are within what the line can consistently reproduce; artisans perform finish detailing and quality review on all production-line output before it ships.
**Provenance documentation:** Every piece that leaves Iznik Atelier is accompanied by a provenance document that includes a serial number from the studio's issue ledger, production date, the name of the supervising artisan, and a description of the piece's design lineage. Institutional clients use these documents for insurance valuation and resale authentication. The documents are printed on the studio's letterhead and bear a stamp from the issue ledger.
**Market position:** Iznik Atelier has no direct competitor at Groombridge in its specific aesthetic category. The institution-grade commission market is small, relationship-driven, and involves long lead times; new entrants would require decades to build the commission pipeline the studio currently holds. This structural moat is the studio's most significant asset after the craft knowledge itself.
**Workforce:** Twelve to fifteen people across artisan, production, administrative, and logistics functions. Small, highly skilled, stable.
---
## Political Relationships
**Groombridge institutional clients:** The Atelier's primary client relationships are with Groombridge's financial and legal institutions — the same entities that form the core of the system's economic establishment. These relationships involve more than commercial transactions; Iznik tile work in a financial house's entrance hall is an aesthetic statement about the institution's relationship to Groombridge's cultural history. Losing the Atelier's work from their spaces would be noticed.
**The Registry:** The Registry uses Iznik Atelier provenance documents as reference material for valuation records — when the Registry processes insurance or resale documentation for Iznik pieces, the provenance documents are the authentication basis. This gives the Atelier's documentation a quasi-official status it does not formally possess.
---
## The Issue Ledger
The provenance authentication system is the studio's visible guarantee to buyers that a piece is genuinely Iznik Atelier work. The serial number on each provenance document corresponds to an entry in the studio's issue ledger — a bound physical record maintained at the Lendel workshop. Buyers, insurers, and resale authenticators who want to verify a piece's authenticity can request confirmation of the serial number against the ledger.
The ledger is the system's only authentication anchor. There is no cryptographic signature, no Commission-certified registry, no third-party verification. The serial number format is documented in the studio's published materials, and the ledger itself is maintained by the studio's administrative manager, who is authorized to confirm serial number validity by correspondence.
Over the past decade, two incidents have involved pieces bearing valid-format serial numbers that the studio did not produce. Both were identified because buyers who purchased the pieces sought expanded provenance information and found discrepancies between the described design lineage and the studio's actual commission records. Both incidents were settled quietly — the studio compensated the buyers and the forgeries were destroyed. No formal complaint was filed with any authority. The studio's legal team negotiated nondisclosure terms in both settlements.
The forgeries succeeded because anyone with the serial number format and access to the studio's public commission descriptions could produce a document that would pass casual inspection. The issue ledger itself was never breached; the forgeries simply used plausible numbers that appeared to fall within the ledger's valid range. The studio has not changed its authentication system. The administrative manager's position on the matter is that the risk is manageable and that introducing a more robust system would imply to institutional clients that the current system was inadequate.
---
## Gameplay Relevance
Iznik Atelier is an atmospheric institution in Groombridge's cultural and economic landscape — the kind of place a player encounters through the work it produces rather than through direct engagement. Its pieces appear in the institutional spaces where important conversations happen and important transactions are recorded.
The authentication system is the investigative thread. A player tracing ownership history of a specific piece, or working a fraud investigation in Groombridge's art and antiques market, will find the issue ledger at the center of a verification request that the ledger is not well-designed to satisfy. The two settled forgery cases are in the studio's legal files; the nondisclosure agreements cover the counterparties but not the studio's own records.
The Registry's reliance on Iznik provenance documents for valuation purposes means that any question about those documents becomes a question about the integrity of records the Registry has issued. That thread connects the Atelier to the financial infrastructure.
---
**Cross-References:**
- [Groombridge](../star-systems/GJ-380/index.md) — Headquarters system; primary institutional client base
- [The Registry](the-registry.md) — Uses Iznik provenance documents for valuation records
- [Alcyone Tech](alcyone-tech.md) — Groombridge institutional neighbor; parallel craft/infrastructure relationship
- [Groombridge Settlement House](groombridge-settlement-house.md) — Major institutional client; entrance hall commission
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/jeju-lattice.md
+78 -6
View File
@@ -1,24 +1,96 @@
---
title: "Jeju Lattice"
description: "Jeju Lattice — precision technology manufacturer based in Yeongwol, east reach"
description: "Yeongwol-based precision electronics manufacturer serving east reach industrial and infrastructure clients — certified components, a subcontracting network, and a Lattice Commission mark applied to batches that were never fully audited"
slug: jeju-lattice
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Yeongwol (GJ 268)
tags: [lattice_grade_material, lattice_substrate, tech_premium, east_reach, tractus, electronics]
decision_refs: [D-175, D-189]
cross_refs: []
cross_refs: [kumho-navigation, namsan-collective, kyoei-design]
---
# Jeju Lattice
**Type:** Corporation — Precision Technology Manufacturer
**Also Known As:** Jeju, JL Components
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Yeongwol (GJ 268)
**Scope:** East reach primary; corridor-wide institutional distribution secondary
**Headquarters:** Yeongwol (GJ 268) — 2-aperture system, 4 hops from Gateway
**Classification:** Sub-Syndic technology enterprise; certified industrial component supplier
Jeju Lattice is a precision technology manufacturer operating out of Yeongwol (GJ 268). Details to be expanded.
---
## Overview
In the east reach corridor, the industrial and infrastructure operators who need precision electronic components with documented certification histories buy from Jeju Lattice. The company occupies a specific market niche: not consumer electronics, not cutting-edge research applications, but the dependable certified components that go into industrial control systems, environmental monitoring hardware, station infrastructure, and the secondary systems of gate maintenance facilities. Components that need to perform reliably for years in conditions where replacement is inconvenient and failure is costly.
Jeju Lattice's certification record is its primary sales argument. The company's catalog lists each component's compliance with Lattice Commission industrial standards — the documentation that infrastructure operators require before specifying a component in a critical system. When a client asks whether Jeju components meet the standard, the answer, supported by the Commission certification document, is yes.
---
## Origin
Jeju Lattice was founded at Yeongwol twenty-eight years ago by an electrical engineer who had spent a decade as a certification auditor for the Lattice Commission before concluding that the east reach corridor's industrial clients were systematically under-served by the available component supply. The corridor's major manufacturing operations were distant; delivery times were long; and the smaller east reach infrastructure operators had no regional supplier capable of providing certified components on short lead times.
The founding model was explicitly designed around Commission certification standards. The founder's auditor background shaped the company's production documentation systems from the start — meticulous batch records, comprehensive test reports, clear traceability chains from raw materials to finished components. These systems produced the certification record that defines the company's market position.
The founder stepped back from operational management seven years ago. The current leadership team grew up within the company's systems and maintains the documentation culture the founder established.
---
## Operations
**Product lines:** Industrial sensors, control system modules, relay components, and environmental monitoring hardware across approximately 200 distinct catalog items. Each item carries a Commission certification document and a batch test record. The catalog has grown steadily as Jeju has added items in response to client requests.
**Primary manufacturing:** The Yeongwol facility employs sixty-three people and handles approximately 60% of Jeju's production volume by unit count. The facility is well-equipped for the company's scale, with functional quality control infrastructure and the documentation systems the founder built.
**Subcontracting network:** Fourteen years ago, as demand exceeded Yeongwol facility capacity, Jeju established supply agreements with three smaller manufacturers in the east reach corridor to produce components from Jeju specifications. Products from these subcontractors ship to Yeongwol for final quality review and are shipped to clients under Jeju's brand and certification marks.
**Clients:** East reach infrastructure operators, station maintenance authorities, and industrial equipment assemblers across a six-system corridor footprint.
---
## Political Relationships
**Lattice Commission certification desk:** The Commission's east reach certification office conducts periodic audits of Jeju's production records. The relationship is formally compliant — Jeju's documentation systems are thorough and have satisfied every audit that has been conducted. The certification relationship is the company's most important institutional asset.
**Subcontractor relationships:** Jeju's subcontractors operate under supply agreements that specify production parameters and documentation requirements. Jeju reviews subcontractor batch documentation before applying its certification marks. The review process is less intensive than the Yeongwol facility's internal production oversight, which the operations team acknowledges is a design constraint rather than a deliberate choice.
---
## The Certification Mark and What It Guarantees
Three years ago, during a period of unusually high demand, Jeju's subcontractor at Hwaseong produced a batch of relay components that failed Jeju's standard incoming quality review at a rate marginally above threshold. The operations team's decision was to conduct a secondary review of the failed units and release the batch with a conditional pass — an internal designation that the team's interpretation of their own quality procedures allowed under a provision for minor specification deviations within defined tolerance ranges.
The batch shipped to clients under Jeju's standard certification marks. The conditional pass designation was recorded in Jeju's internal batch records but was not reflected in the certification documentation accompanying the shipment. The Commission certification mark represents that the product meets the relevant standard; the standard does not distinguish between a standard pass and a conditional pass, and Jeju's internal conditional pass procedure is not part of the Commission's certified quality management framework.
The relay components from that batch are currently in service across east reach infrastructure installations. The conditional pass designation applies to a specific parameter — contact resistance under temperature cycling — that degrades over time in operating conditions. The components will meet specification for several years before the degradation becomes material. Jeju's engineering team has not formally assessed the service-life implications.
The batch records exist and are accurate. A Commission auditor examining those records would find the conditional pass designation and would ask questions about why it was not disclosed in the certification documentation. The question the operations team has not fully worked out is whether the answer to that question is a quality management finding or a certification compliance violation.
---
## Gameplay Relevance
Jeju Lattice is a secondary institution in the east reach industrial supply chain — relevant to investigations concerning component quality, infrastructure reliability, and certification integrity. The company's products are ambient in any east reach station infrastructure setting.
The conditional pass batch is the investigative thread. The batch records are the primary evidence — they exist, they are accurate, and the conditional pass designation is in them. A player with access to Jeju's quality records, or to the Commission's audit correspondence, can find the discrepancy between what the certification mark represents and what the batch documentation shows. The downstream question — where those components are installed and what their service-life trajectory is — requires access to client delivery records and the Commission's infrastructure installation database.
---
**Cross-References:**
- [Yeongwol](../star-systems/GJ-268/index.md) — Headquarters system; primary manufacturing base
- [Kumho Navigation](kumho-navigation.md) — East reach corridor neighbor; tech premium parallel
- [Namsan Collective](namsan-collective.md) — Yeongwol system neighbor; cultural context
- [Kyoei Design](kyoei-design.md) — East reach institutional client; architectural hardware overlap
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/kaapse-baai-wines.md
+90 -7
View File
@@ -1,24 +1,107 @@
---
title: "Kaapse Baai Wines"
description: "Kaapse Baai Wines — regional specialty producer based in Kaapse Baai, south reach"
description: "South_reach Cape-heritage wine producer based at Kaapse Baai (GJ 213) — two centuries of estate tradition, informal appellation certification, and a producers' circle that has come to mean what its most powerful member finds convenient"
slug: kaapse-baai-wines
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Kaapse Baai (GJ 213)
tags: [terroir, south_reach, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [groot-karoo-cellars, meridional-banking]
---
# Kaapse Baai Wines
**Type:** Corporation — Regional Specialty Producer
**Type:** Corporation — Estate Wine Producer and Appellation Authority
**Also Known As:** Kaapse Baai (as both place and brand), the Circle (for the producers' governance body)
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Kaapse Baai (GJ 213)
**Scope:** Regional — south_reach corridor primary; inner-corridor premium market secondary
**Headquarters:** Kaapse Baai (GJ 213) — south_reach corridor
**Classification:** Sub-Syndic estate consortium; informal appellation governance under the Cape Producers Circle
Kaapse Baai Wines is a regional specialty producer operating out of Kaapse Baai (GJ 213). Details to be expanded.
---
## Overview
Kaapse Baai Wines is not one company. It is the collective commercial identity of the Cape Producers Circle — a governance body representing the wine estates of the Kaapse Baai system — and the dominant estate within that circle, Eerste Helling, which holds the Circle's administrative secretariat and has done so for one hundred and forty years. The distinction matters less in practice than it should, because the Cape Producers Circle is not a formal institution. It has no Lattice Commission charter, no public regulatory standing, and no enforcement mechanism beyond the agreement of its members. What it does have is control over the label "Kaapse Baai Origin" — an appellation designation that inner-corridor distributors and serious buyers have been paying a premium for since the third generation of Eerste Helling's Joubert-Van Rooyen family began marketing it as a certification of quality.
The wines themselves are real. The appellation means something in the sense that the south_reach terroir at Kaapse Baai produces wines with a specific character — cooler growing conditions, high mineral content from the rocky volcanic substrate, varietals that have adapted over two centuries of selection. What the appellation means institutionally is whatever the Circle says it means, and the Circle has had a consistent controlling interest for a very long time.
---
## Origin
The founding settlers of Kaapse Baai arrived from a mixed Cape Afrikaner and Dutch colonial community — families carrying vine cuttings as a practical agricultural investment and an identity statement simultaneously. The name they gave the system and the primary settlement was deliberate: Kaapse Baai, Cape Bay, a persistent reference to the coastal wine country they were leaving and the possibility that the new system's cooler coastal analogue terrain could be made to work.
The first commercial harvest occurred approximately two hundred years ago. The third generation of the dominant families established the Cape Producers Circle in the system's second century, when it became clear that a common quality signal for export would command better prices than the individual estates could negotiate separately. The founding principle — that the Circle would certify quality standards and allow member estates to use the "Kaapse Baai Origin" designation — was sensible and has served the system's wine industry well in aggregate. The governance structure gave equal votes to founding member estates. This seemed reasonable when all the founding estates were comparable in size and influence.
They are no longer comparable.
---
## Operations
**The estates:** The Kaapse Baai system has twelve active wine estates ranging from the Eerste Helling property — the oldest, the largest, the administrative center of the Circle — down to three small single-family operations whose commercial scale is modest and whose viability has been, at various points, uncertain. The varietals grown reflect two centuries of local adaptation: the primary red varietal is a Pinotage-lineage cultivar that has developed the mineral-ferrous character that defines the Kaapse Baai profile; the dominant white is a Chenin Blanc descendant notable for high acidity and a reductive aromatic style.
**The Circle's certification process:** Member estates submit wines for tasting review by a panel drawn from Circle membership. The panel assesses adherence to regional style standards. The standards are defined in a founding document that has been revised three times, each revision managed by the Circle's secretariat — Eerste Helling's administrative staff. Revision three, completed forty years ago, expanded the acceptable production methods in ways that primarily benefited large-scale estate operations and disadvantaged small producers whose traditional techniques fell outside the revised criteria.
**Distribution:** Certified wines carry the Kaapse Baai Origin seal — a stylized cape-peak silhouette in deep green, recognized by inner-corridor buyers who track south_reach terroir production. Distribution runs through general south_reach freight channels for the mid-range and through specialist provenance distributors for the premium estates. Eerste Helling manages its own premium distribution contracts; smaller estates participate in a collective export arrangement administered by the Circle's secretariat.
---
## Products
**Eerste Helling Rooiberg** — the flagship red from the dominant estate, aged eighteen months in local oak before bottling. The wine that most inner-corridor buyers encounter when they encounter Kaapse Baai wines at all. Deep, structured, with the iron-mineral finish the region is known for. The benchmark against which other Kaapse Baai reds are measured, partly by merit and partly by virtue of the fact that Eerste Helling has been placing it in front of influential buyers for five generations.
**Eerste Helling Blanc de Kaap** — the flagship white. High-acid, long-finishing, polarizing in the inner corridor in the way that serious high-acid whites are always polarizing: the people who love it order it whenever available; the people who don't wonder what the fuss is. A small allocated release each vintage; genuinely difficult to obtain outside the south_reach.
**Circle member range** — wines from the remaining eleven estates, certified under the Kaapse Baai Origin designation at varying price points. Quality is genuine but inconsistent. The Circle's collective export arrangement manages the mid-range category. Three of the smaller estates produce wines that serious tasters regard as significantly undervalued relative to the dominant estate's production; they lack the distribution relationships to correct this.
---
## Political Relationships
**Groot Karoo Cellars:** The Karoo system's fortified wine and brandy operation represents a different expression of south_reach terroir — arid and mineral against Kaapse Baai's coastal-cool character, fortified styles against the Circle's table wines. The two operations occupy separate market niches and are aware of each other as parallel examples of south_reach terroir building corridor reputations from remote systems. There is no commercial relationship. There is occasional contact at corridor trade events where the representatives of both operations have found themselves on the same side of a discussion about south_reach producer interests.
**Inner-corridor distributors:** A small network of provenance-oriented distribution houses handles Kaapse Baai Origin wines in the inner corridor. The relationship is asymmetric: the distributors can represent multiple south_reach producers, giving them negotiating leverage; the smaller Kaapse Baai estates have no alternative to the Circle's collective arrangement and therefore cannot negotiate individually. Eerste Helling negotiates its own terms.
**Meridional Banking:** The Circle's operating accounts and the individual estates' commercial credit facilities are managed through Meridional Banking's south_reach correspondent network. Estates in financial difficulty have, over the past four decades, negotiated restructuring arrangements through Meridional's commercial desk.
---
## What They Don't Talk About
Seven of the twelve estates in the Cape Producers Circle have, at various points over the past forty years, sold minority stakes to outside investors during periods of financial stress. In each case, the buyer was a commercial entity called Baai Kapitaal Holdings, registered through Meridional Banking's correspondent structure at an address in the Meridional administrative district. Baai Kapitaal's beneficial ownership — which requires tracing through two intermediate holding layers in Meridional's commercial register — terminates at a family trust administered by the Joubert-Van Rooyen family of Eerste Helling.
The estate owners who sold these minority stakes did so believing they were dealing with a commercial investor unaffiliated with the wine industry. The transaction terms were reasonable for distressed-seller transactions: cash, no operational interference, no board seat. No seller has since realized that the entity they sold to is their largest competitor.
Baai Kapitaal does not exercise voting rights through the estates it holds stakes in, because doing so would require disclosing beneficial ownership in Circle governance proceedings. It collects dividends quietly through Meridional's payment infrastructure. The combined position across seven minority stakes gives the Joubert-Van Rooyen family an economic interest in approximately sixty percent of total Kaapse Baai wine production, while nominally controlling only the one estate that has always been theirs.
---
## Gameplay Relevance
Kaapse Baai Wines provides entry into south_reach commercial governance and beneficial ownership investigation. The Circle structure is a model for how informal institutions can concentrate control without formal regulatory exposure.
The productive investigation threads are:
- **Baai Kapitaal Holdings** — the beneficial ownership trace runs through Meridional Banking's correspondent structure. A player with access to Meridional's commercial register can follow the intermediate holding layers. The trace is not difficult if you know to look; the difficulty is knowing that Baai Kapitaal exists and is connected to Eerste Helling. Smaller estate owners who sold stakes are potential sources: they remember the transaction, they don't know what they were part of, and some of them would have opinions about it if they did.
- **The Circle governance revision** — the third revision to the certification standards is documented in the Circle's administrative archive, held by Eerste Helling's secretariat. Comparing the revision text to the production methods of the estates that lost certification access during the same period establishes the pattern. The secretariat is not a public archive.
- **The distribution asymmetry** — the smaller undervalued estates are a point of entry. Any of them would benefit from a player who could either expose the ownership structure or help them negotiate directly with inner-corridor buyers rather than through the collective arrangement.
---
**Cross-References:**
- [Kaapse Baai](../star-systems/GJ-213/index.md) — Headquarters system; founding terroir; estate wine production
- [Groot Karoo Cellars](groot-karoo-cellars.md) — Parallel south_reach terroir producer; fortified wines and brandies; mutual awareness without commercial overlap
- [Meridional Banking](meridional-banking.md) — Commercial register location for Baai Kapitaal Holdings; estate restructuring credit facilities
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/kalahari-leatherworks.md
+77 -6
View File
@@ -1,24 +1,95 @@
---
title: "Kalahari Leatherworks"
description: "Kalahari Leatherworks — heritage craft manufacturer based in Karoo, south reach"
description: "Karoo-based heritage leather goods manufacturer operating in south reach — traditional tanning techniques, rare local hides, and a geographic origin certification that Kalahari wrote for themselves"
slug: kalahari-leatherworks
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Karoo (GJ 222A)
tags: [heritage_craft, south_reach, tractus, artisan]
decision_refs: [D-189]
cross_refs: []
cross_refs: [groot-karoo-cellars, iberian-standard-foods, alentejo-partners]
---
# Kalahari Leatherworks
**Type:** Corporation — Heritage Craft Manufacturer
**Also Known As:** Kalahari, the Leatherworks
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Karoo (GJ 222A)
**Scope:** South reach corridor primary; limited inward premium distribution secondary
**Headquarters:** Karoo (GJ 222A) — 3-aperture hub, 5 hops from Gateway
**Classification:** Sub-Syndic artisan enterprise; provenance-designated craft goods
Kalahari Leatherworks is a heritage craft manufacturer operating out of Karoo (GJ 222A). Details to be expanded.
---
## Overview
Karoo is a dry system with open terrain and specific fauna that have adapted across three centuries to conditions that produce dense, tight-grained hides unlike anything the corridor commonly trades. Kalahari Leatherworks has built its market position on that biological specificity — the company's tanned leather goods are positioned as products of a particular place, a particular ecosystem, and a particular craft tradition that has evolved alongside the animals it processes. The bags, harnesses, boots, and specialist functional goods the workshop produces carry the "Karoo-bred hide" mark as a guarantee of origin, quality, and craft lineage.
In the south reach corridor, this positioning works. Buyers understand that they are paying for something specific that they cannot obtain from a standard goods supplier. At inward distribution points, the provenance story — Karoo system, desert-adapted fauna, three-century craft lineage — carries the premium markup that terroir products command. The Leatherworks maintains a small showroom in Karoo's primary settlement that functions as much as a marketing exercise as a retail point of sale.
---
## Origin
Kalahari Leatherworks traces its founding to a tannery established by the second generation of Karoo settlers, who had arrived from southern African heritage communities and brought tanning techniques developed for arid-zone hides. The system's fauna — the Karoo plains elk and the smaller, tougher corridor deer that had adapted to the dry lowlands — proved exceptionally compatible with the inherited methods.
The original tannery operated as a family enterprise for five generations before being incorporated as Kalahari Leatherworks to facilitate external investment and expanded distribution. The founding family retains a controlling stake and the operational management of the craft workshop. The corporate entity added distribution infrastructure, a second workshop space, and the marketing program that built the brand's inward corridor presence.
The "Karoo-bred hide" designation was introduced as a marketing term during the incorporation period, appearing first in export documentation and later in promotional materials. It became the brand's central identity claim.
---
## Operations
**Product lines:** Functional leather goods — riding harnesses, work boots, storage bags, and carrying equipment for industrial use — are the volume product. These sell throughout the south reach corridor at pricing that reflects the material quality without the full artisan premium. The premium tier covers hand-stitched bag and accessory lines, bespoke commissioned pieces, and the specialist equipment supplied to several south reach resource extraction operations that specify Kalahari material for durability reasons.
**Material sourcing:** The Karoo plains elk and corridor deer that produce the hides Kalahari uses for its premium tier are managed through a pastoral network across Karoo's agricultural zones. The herd management is genuine — the pastoral families who manage the herds have multi-generational relationships with the Leatherworks and supply under long-standing agreements.
**Workshop:** Two workshop spaces at Karoo's primary settlement, employing thirty-eight people across tanning, cutting, stitching, and finishing functions. The senior tanners are the craft knowledge holders; the finishing workshop handles the production-line goods under their oversight.
**Distribution:** South reach direct. Inward distribution through a premium goods importer at Caparica who handles the brand's inward presence.
---
## The "Karoo-Bred Hide" Certification
The Lattice Commission's provenance framework for craft goods includes provisions for geographic origin designation, but the Commission has not formally codified a standard for hide goods from the south reach corridor systems. There is no statutory definition of "Karoo-bred hide" in Commission standards.
Kalahari Leatherworks wrote its own definition. The definition appears in the company's export documentation, its Lattice Commission product registration filings, and the descriptive text on every certificate of origin that accompanies a shipped product. The definition reads: "Hides produced from animals born, raised, and processed within the Karoo system, or from animals of Karoo-origin breeding stock processed using traditional Karoo tanning methods on-system."
The second clause — "Karoo-origin breeding stock processed on-system" — was introduced in the definition at a point when the Leatherworks had begun supplementing its local hide supply with imported animals from a breeding program at a south reach system two hops distant. The breeding program uses stock descended from original Karoo herd animals, exported several generations ago.
Under the definition Kalahari wrote, hides from these imported animals, tanned at the Karoo workshop, qualify as "Karoo-bred." Under any reasonable buyer's understanding of the phrase, they do not. The premium tier remains genuinely local; the volume lines and a portion of the mid-range functional goods use the blended supply. The certificate of origin accompanying all products uses the same language regardless of which supply source the hides came from.
No Commission body has reviewed the definition. No competitor has contested it. The definition simply exists in the company's own documentation, applied consistently in ways that the company's legal team has assessed as technically accurate under the terms as written.
The pastoral families who manage the genuine Karoo herds supply approximately half the current hide volume. They are aware that the workshop also purchases animals from the outward breeding program but have not been told how that supply is certified or labeled. The relationship between the workshop and the pastoral families is maintained carefully — they are both a supply source and a community whose cooperation the Leatherworks's legitimacy depends on.
---
## Gameplay Relevance
Kalahari Leatherworks is background commercial texture for south reach investigations — present in markets, visible in equipment on south reach characters, relevant whenever supply chain provenance or origin certification is the investigative thread.
The certification question is the primary angle. The evidence requires two pieces: the definition Kalahari filed (in Commission product registration records) and the procurement records showing the imported breeding-stock animals (in the Leatherworks' own supply ledgers). The gap between what buyers understand "Karoo-bred" to mean and what the filed definition actually says is the story. A player who connects those two documents has found a provenance fraud that is technically defensible under the letter of a definition the company wrote for itself.
The pastoral families who supply the genuine Karoo herd animals are secondary characters with direct knowledge of the sourcing split — they know the workshop buys outside animals and know it began after the incorporation. What they know about the certification framing is a separate question.
---
**Cross-References:**
- [Karoo](../star-systems/GJ-222A/index.md) — Headquarters system; herd management zones; workshop facilities
- [Groot-Karoo Cellars](groot-karoo-cellars.md) — Karoo system neighbor; comparable provenance product
- [Iberian Standard Foods](iberian-standard-foods.md) — South reach corridor neighbor; parallel origin certification question
- [Alentejo Partners](alentejo-partners.md) — South reach agricultural context; supply chain parallel
- [Matosinhos Fishing](matosinhos-fishing.md) — South reach provenance parallel; comparable methodology question
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/kaur-observatory-equipment.md
+85 -8
View File
@@ -1,24 +1,101 @@
---
title: "Kaur Observatory Equipment"
description: "Kaur Observatory Equipment — precision technology manufacturer based in Kaur's Observatory, east reach"
description: "Sikh-heritage scientific instrumentation manufacturer at Kaur's Observatory (GJ 432A) — observation arrays, stellar survey hardware, and the long-baseline telescope systems used by the Reach's most serious scientific institutions"
slug: kaur-observatory-equipment
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
scope: regional
updated: 2026-04-22
scope: east_reach primary; reach-wide scientific and navigation instrument contracts secondary
faction_type: economic
headquarters: Kaur's Observatory (GJ 432A)
tags: [tech_premium, east_reach, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [hanyang-precision, dalbit-systems]
---
# Kaur Observatory Equipment
**Type:** Corporation — Precision Technology Manufacturer
**Type:** Corporation — Scientific Observation and Survey Instrumentation
**Also Known As:** Kaur, KOE
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Kaur's Observatory (GJ 432A)
**Scope:** East_reach primary; reach-wide scientific institution and navigation contracts secondary
**Headquarters:** Kaur's Observatory (GJ 432A) — 2-aperture spur, 9 hops from Gateway
**Classification:** Sub-Syndic technology enterprise; scientific instrumentation specialist
Kaur Observatory Equipment is a precision technology manufacturer operating out of Kaur's Observatory (GJ 432A). Details to be expanded.
---
## Overview
The span gates require stellar reference points to orient themselves. The survey vessels that mapped the Reach's outer corridors required precision instruments to record what they found. The Veil Institute's observatories, distributed across the Reach to maintain continuous coverage of the alien horizon stations that made the gate network possible, require hardware to do the observing. Kaur Observatory Equipment makes this hardware: precision stellar survey arrays, long-baseline telescope systems, atmospheric sensor platforms, and the orientation instruments that tell gate alignment systems where they are relative to everything else.
The company occupies a specific niche in the east_reach's technology sector — not the consumer-facing precision electronics of Hanyang or the volume manufacturing of Dalbit, but the specialist instrumentation that scientific institutions and navigation infrastructure require and that general manufacturers do not build to the required specification. Kaur's clients are the Reach's most demanding users of precision optics and sensor technology. Their requirements have driven the company's capability for seven generations, and the company's capability has in turn shaped what those institutions consider achievable.
---
## Origin
Amarjit Kaur arrived at GJ 432A as the lead scientist on an observation survey mission, not as a colonist. The system's specific location — its angular position relative to several of the Reach's boundary regions, and the minimal atmospheric interference at its primary orbital platform — made it unusually well-suited for long-baseline stellar observation. Kaur's initial mission was three years. She stayed for the remainder of her life, which was not Perpetual-class long but was long enough to establish the observatory that would eventually become the system's defining institution and give it her name.
The transition from scientific station to commercial instrumentation manufacturer happened in the second generation, when Kaur's students found that the custom instruments they were building for the observatory's own research programs were better than anything available through standard commercial channels, and that other institutions were willing to pay for access to those capabilities. The founding proposition was not commercial ambition but practical necessity: the observatory needed funding, the instruments were fundable, and the manufacturing operation that grew from the observatory's workshop produced revenue that the research program could not.
The Kaur family name attached to the company as a consequence of the system's naming, not through any deliberate branding decision. The system was informally called Kaur's Observatory within a generation of Amarjit's arrival; the name was formal within two generations; the company took the name because it was the name everyone already used for the place and the work.
---
## Operations
**Survey instrumentation:** Custom stellar survey arrays for scientific and navigation applications. The observation hardware produced by KOE is not the same as commercial telescope systems; it is designed for the specific requirements of long-baseline survey work — extended integration periods, precise pointing stability, calibrated sensitivity across the relevant spectral ranges — that scientific observation programs require. Each array is fabricated to client specification rather than produced as a standardized product.
**Orientation systems:** The stellar orientation sensors used in span gate calibration systems require a specific combination of precision and reliability that Kaur's background in long-baseline survey instruments naturally produces. Gate orientation sensors are a significant portion of KOE's commercial revenue — Gate Corporation installations across the Reach use KOE orientation hardware as standard specification. The Gate Corporation relationship is the company's largest single commercial account by volume.
**Atmospheric sensor platforms:** Planetary observation programs require atmospheric sensor arrays distinct from the stellar instruments used for void-space observation. Kaur's atmospheric sensor product line developed from the planetary observation programs at the home observatory and has expanded to serve scientific stations and environmental monitoring programs across the east_reach.
**Observatory maintenance:** KOE maintains a field service program for instruments installed at external scientific institutions. The maintenance relationships with the Veil Institute's observatory network and several independent research stations provide a revenue stream that is smaller than the fabrication business but strategically important — field service engineers see what the instruments are being used to observe, which is useful context for understanding what capabilities clients will need next.
---
## Political Relationships
**Hanyang Precision Systems:** Supply and licensing relationship. KOE's stellar observation sensors provide the high-precision data inputs that Hanyang's navigation instruments require for stellar reference calibration. The two companies operate at different points in the navigation instrument supply chain: KOE makes the observation hardware, Hanyang integrates the data into the instruments that ships and gates actually use. The relationship is commercially productive and technically close; the engineering teams coordinate on calibration specifications with enough regularity to have developed a working relationship that goes beyond standard supplier-client dynamics.
**The Veil Institute:** KOE's most significant scientific client. The Institute's observatory network across the Reach uses KOE instruments as primary observation hardware. The relationship is research-client in form but deeper in practice — Veil Institute researchers have been among the most technically demanding users of KOE's instruments for generations, and several of the instrument advances that KOE's current product portfolio builds on emerged from problems that Veil Institute observation programs surfaced. The Institute's field staff know KOE's engineering team well enough to call them directly about instrument behavior rather than going through the formal service channel.
**Gate Corporation:** The orientation sensor supply relationship that constitutes KOE's largest single commercial account. Gate Corporation's installation standards specify KOE orientation hardware for gate alignment systems across the network. The relationship is long-standing and professionally transactional — Gate Corporation procurement operates at institutional scale and treats KOE as a qualified sole-source supplier rather than as a partner. KOE has invested in maintaining the certification that keeps it on Gate Corporation's qualified supplier list precisely because losing that status would remove the company's most reliable revenue stream.
---
## What They Don't Talk About
The observatory at Kaur's Observatory maintains long-baseline observation records going back seven generations — a continuous archive that is one of the longest unbroken astronomical datasets in the east_reach. Most of that data is scientific background: stellar positions, variable star monitoring, survey records used as reference baselines for navigation and gate calibration. The archive is available to researchers and has been used in published work across multiple disciplines.
Three years ago, the current director of KOE — Dr. Parveen Kaur, great-great-great-grandniece of the founder — was reviewing the archive for a calibration stability study and encountered an anomaly in the microwave background data from a specific region in the outer boundary of the Reach's eastern surveyed territory. The anomaly has characteristics consistent with a reflection signature from a horizon station aperture: a specific pattern of microwave emission that the Veil Institute's published observation protocols describe as indicative of active alien installation.
The surveyed territory in that region is mapped. The anomaly's source location does not correspond to any surveyed installation.
Dr. Kaur has not disclosed the anomaly to the Veil Institute, to the Gate Corporation, or to any other institution. She has been quietly tasking a portion of the observatory's maintenance observation allocation — equipment time that is logged internally as long-baseline calibration stability verification — toward refining the position and brightness data on the anomaly. The project designation in the observatory's scheduling records is technical and opaque. The accumulating dataset is stored in the raw observation archive under that designation, accessible to anyone with archive access who knows what they are looking at and why the project designation doesn't match the observation targets.
She has not decided what to do with the data when it is sufficient to confirm or rule out the hypothesis. She is aware that the decision will not be simple.
---
## Gameplay Relevance
Kaur Observatory Equipment is a scientific instrument manufacturer that becomes relevant when navigation, stellar survey, or observation data are at issue. The Gate Corporation relationship makes KOE's products present throughout the Reach's gate infrastructure. The Veil Institute relationship makes KOE a point of access into the Institute's research network — field service engineers who work at Veil Institute observatories know which programs are currently active and what the instruments are being pointed at.
The anomaly dataset is the significant investigative thread. A player who gains access to the observatory's raw observation archive and understands the observation scheduling records is looking at several years of data pointing at a region of space that, if the hypothesis is correct, contains an undiscovered alien installation. The implications for the Veil Institute, for gate network expansion, and for whoever gets there first are extensive. Dr. Kaur is an intelligent person who has been sitting with a significant discovery for three years without disclosing it; understanding why requires understanding her position, which is that she leads a small regional instrumentation company and is not confident that being the person who reported this would end well for the observatory or for herself.
---
**Cross-References:**
- [Kaur's Observatory](../star-systems/GJ-432A/index.md) — Headquarters system; founding observatory; long-baseline observation archive
- [Hanyang Precision Systems](hanyang-precision.md) — Supply and calibration relationship; navigation instrument integration
- [Dalbit Systems](dalbit-systems.md) — East_reach electronics peer; overlapping institutional client base
- [Veil Institute](../factions/veil-institute.md) — Primary scientific client; observatory network instruments
- [Gate Corporation](gate-corporation.md) — Largest commercial client; gate alignment orientation sensors
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/kellervolk.md
+78 -6
View File
@@ -1,24 +1,96 @@
---
title: "Kellervolk"
description: "Kellervolk — cultural content producer based in Nyrheim, west reach"
description: "Nyrheim-based cultural content studio producing west reach serialized narrative and documentary work — public-facing independence, a government funding relationship routed through an arts foundation, and a side agreement that makes the independence contractually fictional"
slug: kellervolk
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Nyrheim (GJ 3737)
tags: [cultural, west_reach, mark, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [nordhavn-financial, norrland-woodcraft, maas-rijn-entertainment]
---
# Kellervolk
**Type:** Corporation — Cultural Content Producer
**Also Known As:** Kellervolk Studio, the Keller collective
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Nyrheim (GJ 3737)
**Scope:** West reach corridor primary; limited inward distribution secondary
**Headquarters:** Nyrheim (GJ 3737) — 3-aperture hub, 6 hops from Gateway
**Classification:** Sub-Syndic cultural enterprise; narrative and documentary production
Kellervolk is a cultural content producer operating out of Nyrheim (GJ 3737). Details to be expanded.
---
## Overview
Nyrheim's west reach corridor identity is partly a cultural export project, and Kellervolk is the studio most responsible for what that project looks like. The company produces serialized narrative content — multi-season dramatic works with west reach settings and characters — and documentary programming that covers Nyrheim's history, geology, resource economy, and communal culture. Both streams are well-regarded in the west reach corridor and have inward distribution through a Mark-currency broadcaster.
The studio's public profile emphasizes independence and editorial integrity. Kellervolk's promotional materials and award applications describe the studio as "practitioner-led" and "community-grounded" — the implication being that content decisions are made by people whose first allegiance is to the work rather than to financial or political stakeholders. This is the standard story that quality cultural producers tell about themselves, and in Kellervolk's case it is believed by most of the people who say it.
---
## Origin
Kellervolk was founded twenty-two years ago by a group of west reach documentary producers and writers who had been working individually and wanted a shared production infrastructure. The founding philosophy was horizontal governance — major production decisions made collectively, no single producer with unilateral authority. The early productions were modestly funded and editorially independent in the way that things funded on a small scale with limited external stakes tend to be.
The turning point was the studio's fifth year, when Nyrheim's regional government identified Kellervolk as an appropriate vehicle for a cultural export initiative — a program to commission and distribute west reach content that would strengthen the corridor's cultural identity relative to the inward systems whose media presence dominated available programming. The government's interest was genuine and the alignment was real: Kellervolk wanted to make west reach content; the government wanted more of it produced and distributed.
The mechanism chosen was an arts foundation — the Nyrheim Cultural Foundation, formally independent, with a board drawn from civil society and the cultural sector — that would receive government funding and disburse it to eligible productions through a grant process. Kellervolk became the Foundation's primary grantee.
---
## Operations
**Production:** Four to six long-form productions in active development at any given time. The studio employs a core creative staff of twenty-eight, with significant production-phase contracting. Productions are developed under the studio's collective governance framework — proposals reviewed by a committee of senior producers, greenlit by majority vote.
**Funding structure:** The majority of Kellervolk's production budget comes through grants from the Nyrheim Cultural Foundation. Commercial revenue from distribution rights and licensing covers operating costs. The Foundation grant process involves an editorial review in which Kellervolk submits production proposals describing the work's thematic content and intended market.
**Distribution:** Mark-currency broadcaster at Nyrheim holds first-look broadcast rights. For inward corridor distribution, Kellervolk uses an agency relationship with a Dokkum-based distributor.
**Governance:** The founding collective governance model has been maintained in formal terms — the senior producers committee remains the greenlight body, and no single executive holds unilateral editorial authority.
---
## Political Relationships
**Nyrheim Cultural Foundation:** The Foundation is Kellervolk's primary funder and its primary political relationship. The Foundation's board members include Nyrheim government nominees who are not majority but who are consistent voices in board discussions. The grant process creates a natural channel for alignment between government priorities and production decisions.
**Nyrheim regional government:** The government's relationship with Kellervolk is managed through the Foundation structure and is therefore formally indirect. Government officials do not appear in Kellervolk's governance documents or editorial meetings.
---
## The Side Agreement
The Nyrheim Cultural Foundation's charter describes the Foundation as an independent body making editorial decisions on grant applications without reference to government priorities. This description is accurate in the formal governance sense — the board reviews applications on artistic merit criteria and the government nominees participate as individual board members, not as government representatives.
Alongside the Foundation charter, there is a side agreement between the Foundation and Nyrheim's regional cultural ministry. The side agreement was established at the Foundation's founding, is not a public document, and is described in the ministry's internal records as an "operational protocol." It gives the ministry a veto over grant applications that touch three thematic categories: resource extraction industry representation, relations between Nyrheim and the inward corridor commercial systems, and the governance of west reach regional institutions.
The veto has been exercised twice in the past decade, both times through a process in which the ministry's government liaison on the Foundation board identifies an application as falling within a flagged category and the application is returned to the applicant for "further development" without being formally rejected. In both cases, the productions were eventually produced after the problematic elements were revised. The producers involved understood they were being managed but were not told why.
Kellervolk's senior producers do not know the side agreement exists. They know that certain topics require more revision cycles than others and have internalized this as editorial feedback from the Foundation board. The Foundation chair knows about the side agreement and regards it as an administrative mechanism rather than a restriction on editorial independence, because the productions are ultimately made.
---
## Gameplay Relevance
Kellervolk is relevant as a west reach cultural institution and as a thread into the relationship between Nyrheim's government and its cultural infrastructure. The studio appears wherever west reach culture, media, or political messaging intersects with the player's activities.
The side agreement is the investigative thread. It is a document — in the cultural ministry's internal records, countersigned by the Foundation chair. A player who accesses either set of records finds an agreement that contradicts the Foundation's public independence claim and explains the revision pattern that working producers have noticed but not understood. The thematic categories covered by the veto are narrow enough that most Kellervolk productions have never encountered it — which is part of why the arrangement has persisted without internal scrutiny.
---
**Cross-References:**
- [Nyrheim](../star-systems/GJ-3737/index.md) — Headquarters system; production base; cultural ministry
- [Nordhavn Financial](nordhavn-financial.md) — Nyrheim system neighbor; west reach institutional context
- [Norrland Woodcraft](norrland-woodcraft.md) — Nyrheim system neighbor; comparable west reach brand
- [Maas Rijn Entertainment](maas-rijn-entertainment.md) — West reach corridor competitor; Mark-currency broadcaster overlap
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/kinlochewe-instruments.md
+82 -6
View File
@@ -1,24 +1,100 @@
---
title: "Kinlochewe Instruments"
description: "Kinlochewe Instruments — precision technology manufacturer based in Braemar, north reach"
description: "Braemar-based precision instruments manufacturer serving academic and industrial clients in the north reach — calibration standards derived from a deprecated methodology and a certification update the company has been slow to pursue"
slug: kinlochewe-instruments
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Braemar (GJ 475)
tags: [tech_premium, north_reach, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [calloway-distillery, ironbark-films, erzgebirge-instruments]
---
# Kinlochewe Instruments
**Type:** Corporation — Precision Technology Manufacturer
**Also Known As:** Kinlochewe, KI Scientific
**Status:** Canonical
**Scope:** Regional — north reach operations
**Headquarters:** Braemar (GJ 475)
**Scope:** North reach primary; corridor-wide institutional client base secondary
**Headquarters:** Braemar (GJ 475) — 2-aperture loop_member, 5 hops from Gateway
**Classification:** Sub-Syndic technology enterprise; certified scientific and navigational instrumentation
Kinlochewe Instruments is a precision technology manufacturer operating out of Braemar (GJ 475). Details to be expanded.
---
## Overview
Braemar is an academic and scientific system in the north reach corridor — several universities, a deep-space observation network, and the kind of institutional culture that accumulates over generations of settlement by people who came to do careful work. Kinlochewe Instruments has been the primary local supplier of precision scientific and navigational instruments for that community for thirty-seven years. Spectrometers, atmospheric sensors, survey equipment, and the calibration reference tools that other instruments are measured against: these are what Kinlochewe builds.
The company's public positioning leans on the academic relationship and the research credentials it implies. Kinlochewe instruments appear in published research from Braemar's universities. The company sponsors symposia and occasionally contributes instrument loans to long-duration observation projects. The story the company tells about itself is one of scientific rigor and precision — an instrument maker whose products are trusted by people for whom being wrong is professionally consequential.
---
## Origin
Kinlochewe Instruments was founded by a physicist who had spent twenty years as an instrument specialist at Braemar's primary research university before concluding that the external suppliers the university depended on were not building to the standards that serious research required. The founding proposition was local manufacture to research-grade specifications, with calibration services embedded in the supply relationship.
The first clients were the university departments the founder had worked with directly. Word spread through the research community over several years, and by the end of the first decade Kinlochewe had established supply relationships with every research institution at Braemar and with several of the resource extraction operations in the wider north reach corridor that required precision survey and environmental measurement capability.
The resource extraction sector ultimately became the larger share of Kinlochewe's revenue. The research positioning remained the company's primary identity. This tension — between a brand built on academic scientific standards and a revenue base dominated by industrial clients — is the operative internal dynamic at Kinlochewe today.
---
## Operations
**Product lines:** Scientific instruments for atmospheric and environmental measurement, geological survey equipment, navigational precision hardware, and calibration reference standards. The calibration reference line — tools used to verify the accuracy of other measuring instruments — is the highest-margin product and the one most critical to the company's certification status.
**Calibration standards:** Kinlochewe's instruments are certified under Lattice Commission metrology standards, which define the measurement methodologies and accuracy specifications that certified instruments must meet. The calibration reference products are certified to these standards and are used by industrial clients whose own instruments must demonstrate compliance.
**Primary clients:** Braemar's research institutions, the north reach corridor's resource extraction operators, and a smaller number of environmental monitoring bodies. The resource extraction clients represent approximately 65% of revenue.
**Workforce:** Forty-seven people across engineering, manufacturing, calibration, and customer service. The calibration team is the most specialized and the most difficult to replace.
---
## Political Relationships
**Braemar research institutions:** The university relationships are maintained more carefully than their revenue share would suggest. The institutional endorsement that comes from academic clients using Kinlochewe instruments in published research is the brand's primary credential. Losing an academic client would cost more in positioning than in revenue.
**North reach resource extraction sector:** The industrial clients are less interested in brand story than in performance specifications and service continuity. Several of Kinlochewe's largest industrial clients are on long-term supply agreements that predate the current management team.
**Lattice Commission metrology board:** The metrology board maintains the standards under which Kinlochewe's products are certified. The company interacts with the board through the certification renewal process, which occurs every five years for each product line.
---
## The Deprecated Methodology
Three years ago, the Lattice Commission's metrology board completed a review of calibration methodology standards for atmospheric and environmental measurement instruments. One of the outcomes of the review was the formal deprecation of a measurement methodology — Differential Path Integration, or DPI — that had been included in the calibration standards for twenty years but which the review determined was producing systematic error in specific atmospheric compositions common in the north reach corridor's habited worlds.
The deprecated methodology was removed from the certification testing matrix effective from the date of the review's publication, with a transition provision that existing certified products would be re-evaluated against the updated standards at their next scheduled certification renewal.
Kinlochewe's flagship atmospheric sensor line uses DPI as its primary calibration methodology. The line was certified under the old standards three years before the deprecation. Its certification renewal is due eighteen months from now.
The company's engineering team is aware of the deprecation. A proposal to begin retrofitting the affected product line to use the replacement methodology was reviewed by Kinlochewe's operations management eight months ago. The decision taken was to defer the retrofit to the next scheduled product revision cycle, which is planned to coincide with the certification renewal. The commercial logic is clear — a retrofit conducted before the renewal would require re-certification at cost; a retrofit conducted as part of the renewal process can be bundled.
The gap is the eighteen months between now and the renewal, during which Kinlochewe's certified atmospheric sensors are in service at industrial and research sites, calibrated under a methodology the Commission has deprecated as producing systematic error. The certification documents accompanying those instruments state that they meet current Commission standards. The Commission's deprecation notice is a public document that the instruments' operators have not been notified of.
---
## Gameplay Relevance
Kinlochewe Instruments is relevant in north reach investigations touching environmental data, resource extraction permits, and calibration standards. The company's instruments are present at mining and survey operations throughout the corridor, and the data those instruments produce informs environmental compliance documentation.
The deprecated methodology is the investigative thread. The deprecation notice is in the Commission's public records. The instruments in service at specific installations can be identified through delivery records. Whether any research or compliance documentation was produced using those instruments during the deprecation window — and whether the systematic error the methodology produces is material to any specific filing — requires work across client records and Commission environmental standards documentation. The company's deferral decision is in the operations management meeting records.
---
**Cross-References:**
- [Braemar](../star-systems/GJ-475/index.md) — Headquarters system; academic client base; primary market
- [Calloway Distillery](calloway-distillery.md) — Braemar corridor neighbor; north reach cultural parallel
- [Ironbark Films](ironbark-films.md) — North reach institutional neighbor; Braemar cultural context
- [Erzgebirge Instruments](erzgebirge-instruments.md) — Precision instruments parallel; cross-corridor competitor
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/koryo-standard.md
+77 -6
View File
@@ -1,24 +1,95 @@
---
title: "Koryo Standard"
description: "Koryo Standard — consumer goods manufacturer based in Jeonnam, east reach"
description: "Jeonnam-based east reach consumer goods manufacturer producing cleaning products, packaging materials, and basic household commodities — a flexible workforce model, an unresolved safety configuration, and an NDA written to cover more than one incident"
slug: koryo-standard
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Jeonnam (GJ 3728B)
tags: [commodity_branded, east_reach, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [incheon-salt, kyoei-design, jeju-lattice]
---
# Koryo Standard
**Type:** Corporation — Consumer Goods Manufacturer
**Also Known As:** Koryo, KS Products
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Jeonnam (GJ 3728B)
**Scope:** East reach corridor primary; limited inward distribution secondary
**Headquarters:** Jeonnam (GJ 3728B) — 2-aperture system, 5 hops from Gateway
**Classification:** Sub-Syndic consumer goods enterprise; everyday commodity lines
Koryo Standard is a consumer goods manufacturer operating out of Jeonnam (GJ 3728B). Details to be expanded.
---
## Overview
Koryo Standard is what sustains east reach households between the things they buy for taste or status. Cleaning concentrates, packaging materials, basic hygiene products, bulk food containers, workshop consumables — the category of goods that people repurchase automatically and notice only when they are absent. The company has eleven product lines under three brand names and distributes across six east reach systems. No individual product is remarkable. The aggregate market presence is significant.
The company's public identity is low-profile by design. Koryo Standard does not sponsor cultural programming or make arguments about its heritage or the specificity of its ingredients. It competes on price, availability, and the trust that comes from consistent products across many purchase cycles. In the east reach consumer market, this positioning is sustainable: there are enough households buying enough ordinary things that a company good enough at logistics and production can generate comfortable margins without aspiring to premiumness.
---
## Origin
Koryo Standard was founded twenty-nine years ago as a consolidation of three smaller east reach manufacturing operations that had been competing inefficiently across overlapping product categories. The consolidation was backed by a Jeonnam-based investment group that saw an opportunity to rationalize production and distribution across the east reach corridor. The three founding operations became production facilities within a single corporate structure.
The name "Koryo Standard" was selected for its neutrality — it refers to neither the founding operations nor to any specific product identity. The company was intended from the beginning to be an infrastructure company rather than a brand. Whether to build brand recognition on top of the supply infrastructure has been a recurring management debate, never fully resolved in either direction.
---
## Operations
**Product lines:** Cleaning concentrates under the Jeon Clean brand. Packaging and storage materials under the Standard Pack mark. Household and personal care basics under Koryo Home. Each line covers approximately 30 to 50 SKUs. Production is largely automated; the facilities are not technically complex but require consistent maintenance of equipment that operates at high throughput.
**Workforce model:** Koryo Standard's production workforce is approximately 60% short-term contracted workers, with the remainder on standard employment agreements. The company describes this in public materials as a "flexible workforce model" that allows production capacity to scale with demand. The practical consequence is that a significant share of the workers in the facilities at any given time are in their first few months of employment, without the accumulated familiarity with specific equipment that longer tenure builds.
**Facilities:** Three facilities across Jeonnam and two adjacent east reach systems. Facility managers have operational authority within parameters set by central management; safety protocols are standardized at the corporate level.
**Distribution:** Direct east reach distribution through the company's own logistics network, supplemented by local distributor relationships at systems where the network is thinner.
---
## Political Relationships
**East reach labor relations:** Koryo Standard's contracted workforce model has drawn periodic attention from east reach labor advocacy bodies, which argue that high contractor ratios are used to avoid benefits obligations and reduce accountability for workplace conditions. The company's response in these forums has been that its contractor arrangements comply fully with Lattice Commission labor standards and that contracted workers are employed through compliant agencies with proper oversight.
**Lattice Commission compliance desk:** Koryo Standard's regulatory compliance is managed through a dedicated team and has not produced adverse formal findings. The company's internal safety protocols are documented and certified.
---
## What the Settlement Covers
Two years ago, a production line worker at the Jeonnam facility was injured by a rotating component failure on one of the packaging assembly machines. The injury was serious and the incident was reported to the facility's safety authority as required. A settlement was reached with the injured worker, accompanied by a nondisclosure agreement. The settlement amount was material; the NDA terms covered the worker's description of the incident, the facility's internal investigation findings, and "any related operational matters."
The internal investigation identified the specific machine configuration that caused the failure — a guarding arrangement on a rotating drive component that created a pinch hazard under a specific operational condition. The investigation report noted that the same machine configuration was present on two machines at the Jeonnam facility and on one machine at the Hwaseong facility.
Koryo Standard's safety team scheduled a review of all three machines. The review was conducted at the Jeonnam facility, where the two affected machines had their guarding configuration modified. The Hwaseong facility was notified of the review requirement. A month later, facility records show the notification was logged. Whether the Hwaseong machine's guarding was modified is not confirmed in any record that safety team headquarters can access — the Hwaseong facility manager at the time has since moved on, and the successor was not briefed on the review.
The NDA's scope is "incident specifics and related operational matters." The safety team's legal review determined that the ongoing machine configuration question is distinct from the incident itself — correcting it does not require disclosing the incident. This is technically correct and means that notifying workers at the Hwaseong facility that a guarding review had been recommended, without explaining why, was not an NDA violation. The notification that was sent described the review as "routine scheduled maintenance assessment."
---
## Gameplay Relevance
Koryo Standard is ambient east reach commercial texture — present in station commissaries, household inventory, supply chain records. Relevant to investigations involving labor practices, workplace safety, or consumer goods supply chains.
The Hwaseong machine configuration is the investigative thread. The evidence requires connecting three pieces: the original incident report at Jeonnam, the internal investigation's identification of the three affected machines, and the Hwaseong facility's maintenance records — which will show either that the guarding was modified or that it was not. The NDA exists and can be found in the settlement records; its scope language is the key document for understanding what the company was and was not required to disclose. The outgoing Hwaseong facility manager is a potential source. The contracted workers at the Hwaseong facility — who cycle through rapidly and have limited tenure — are a secondary source whose accounts of the current machine configuration are credible precisely because they have no stake in the corporate outcome.
---
**Cross-References:**
- [Jeonnam](../star-systems/GJ-3728B/index.md) — Headquarters system; primary production facilities
- [Incheon Salt](incheon-salt.md) — East reach corridor neighbor; bulk salt purchaser from Incheon
- [Kyoei Design](kyoei-design.md) — East reach institutional neighbor; overlapping client base
- [Jeju Lattice](jeju-lattice.md) — East reach industrial context; parallel certification concerns
- [Kumho Navigation](kumho-navigation.md) — Hwaseong corridor neighbor; east reach industrial context
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/kumho-navigation.md
+78 -6
View File
@@ -1,24 +1,96 @@
---
title: "Kumho Navigation"
description: "Kumho Navigation — precision technology manufacturer based in Hwaseong, east reach"
description: "Hwaseong-based specialist in gate transit navigation software and corridor routing tools — east reach freight routing depends on their dataset, which incorporates survey data whose accuracy certifications expired with the company that produced it"
slug: kumho-navigation
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Hwaseong (GJ 1125)
tags: [tech_premium, east_reach, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [jeju-lattice, koryo-standard, the-gate-corporation]
---
# Kumho Navigation
**Type:** Corporation — Precision Technology Manufacturer
**Also Known As:** Kumho, Kumho Nav
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Hwaseong (GJ 1125)
**Scope:** East reach primary; corridor-wide data licensing secondary
**Headquarters:** Hwaseong (GJ 1125) — 2-aperture system, 4 hops from Gateway
**Classification:** Sub-Syndic technology enterprise; navigation data and hardware provider
Kumho Navigation is a precision technology manufacturer operating out of Hwaseong (GJ 1125). Details to be expanded.
---
## Overview
Every commercial freight operator in the east reach corridor uses routing tools. The question is whose. For the majority of east reach freight operations — from the large interstellar carriers to the smaller single-vessel operators running regular corridor routes — the routing tools are built on navigation data that Kumho Navigation produces, maintains, and licenses. The company's gate transit datasets cover aperture approach parameters, corridor routing efficiency models, and the seasonal variation data that experienced pilots know matters for transit timing. Kumho does not have a monopoly on this data; gate operators publish basic parameters, and the Gate Corporation maintains its own routing standards. What Kumho has is the most detailed, most current, and most practically useful east reach dataset available through commercial channels.
The hardware side — navigation terminal equipment, aperture approach systems sold to vessel operators and station traffic management — is smaller as a revenue line but is the part of the business that most clients interact with as a physical product. The hardware is competent and certified. The data is where the operational value lies.
---
## Origin
Kumho Navigation was founded twenty years ago by a vessel operator who had spent fifteen years running a freight route across the east reach corridor before concluding that the available navigation data was inadequate for the optimization decisions that would matter at the margins of profitable operation. The founder's insight was not that better routing would save dramatic amounts on individual transits but that small improvements compounded across a large number of transits — and that selling this compound improvement to other operators was more valuable than keeping it proprietary.
The company's first commercial product was a subscription routing service for corridor freight operators. The dataset was built from the founder's own survey logs combined with purchased survey data from other corridor operators. Thirteen years ago, when a smaller navigation data company at Jeonnam folded, Kumho acquired its assets — including a substantial survey dataset covering several east reach systems — under a distressed acquisition that resolved the failed company's creditor obligations.
The acquisition was the moment that established Kumho's dataset as the most comprehensive available in the east reach corridor. The integration of the acquired data with Kumho's own was completed over eighteen months and has not been formally re-validated since.
---
## Operations
**Data products:** The east reach corridor navigation dataset, updated through ongoing survey contracts with vessel operators who submit telemetry in exchange for subscription discounts. Routing software that uses the dataset to produce optimized transit plans for commercial operators. The dataset covers aperture parameters, corridor routing, and point-to-point efficiency models for the east reach's primary commercial routes.
**Hardware:** Navigation terminal equipment, aperture approach systems for vessel operators, and traffic management hardware for station operators. Hardware sales are certified under Lattice Commission navigation equipment standards.
**Licensing:** The dataset is licensed to freight operators at subscription rates tiered by usage volume. Several east reach station operators have institutional licenses that integrate Kumho data into their traffic management systems.
**Workforce:** Fifty-one people across data operations, software development, hardware engineering, and client services.
---
## Political Relationships
**Gate Corporation:** The Gate Corporation's aperture operation standards define the parameters within which commercial navigation data must be calibrated. Kumho's data products are not formally certified by the Gate Corporation, which certifies hardware rather than data, but Kumho's commercial relationships depend on clients trusting that the dataset is aligned with Gate Corporation operational parameters.
**East reach freight operators:** Kumho's commercial relationships are with individual operators and freight companies across the east reach corridor. The dataset's value proposition is practical — operators who use it make better routing decisions than those who do not. The subscription renewal rate is high.
---
## The Acquired Dataset
The survey data acquired from the Jeonnam company was, at the time of acquisition, certified under the Lattice Commission's navigation survey standards that were then in effect. Those standards required periodic re-certification of survey data on a seven-year cycle — re-surveys of the covered areas to verify that the published parameters remained accurate within specified tolerances.
The Jeonnam company's certification cycle was interrupted by its financial difficulties. By the time of the acquisition, two of the survey areas covered by the acquired dataset had certifications that were within six months of expiry. The distressed acquisition agreement did not require Kumho to assume the certification obligations of the acquired data — those obligations had expired with the original company's Lattice Commission registration.
Kumho integrated the acquired data into its own dataset without conducting re-surveys. The company's internal rationale was that gate operator basic parameters and ongoing telemetry from subscriber vessels would identify any material changes to the acquired survey areas. This approach provides informal validation but does not constitute formal re-certification under Commission standards.
The acquired data has not been formally re-certified. It has been continuously updated through telemetry integration and is operationally current in the sense that obvious errors would have been caught through client feedback. Whether the update methodology produces data that would pass a formal re-survey certification is a question Kumho's data team has not formally examined. The Commission's navigation data standards require that commercial datasets disclose the currency and certification status of their component sources. Kumho's dataset documentation describes the acquired component as "integrated and operationally maintained" without disclosing that its formal certification lapsed at acquisition.
---
## Gameplay Relevance
Kumho Navigation is relevant to east reach investigations touching transit logistics, routing efficiency, and the accuracy of navigation data that freight operators depend on. The company's data products are ambient in any east reach commercial shipping context.
The certification lapse is the investigative thread. The evidence requires three components: the original Jeonnam company's certification records (in Commission archives), the acquisition agreement (in commercial registry records), and Kumho's own dataset documentation. The gap between "operationally maintained" and "formally certified" is significant in contexts where a routing error — even a marginal one — causes a transit incident. A player working a shipping incident investigation who traces the data source for the involved operator's routing tools will reach Kumho's dataset and the certification question.
---
**Cross-References:**
- [Hwaseong](../star-systems/GJ-1125/index.md) — Headquarters system; primary operations base
- [Jeju Lattice](jeju-lattice.md) — East reach tech neighbor; parallel certification concerns
- [Koryo Standard](koryo-standard.md) — Hwaseong corridor neighbor; industrial context
- [The Gate Corporation](gate-corporation.md) — Aperture standards authority; navigation parameter framework
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/kyoei-design.md
+79 -7
View File
@@ -1,24 +1,96 @@
---
title: "Kyoei Design"
description: "Kyoei Design — design and furniture manufacturer based in Kurashiki, east reach"
description: "Kurashiki-based furniture and interior design manufacturer rooted in east reach aesthetic tradition — premium workshop output, licensed mid-range manufacturing, and a workforce arrangement that only works because of where the factory is located"
slug: kyoei-design
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Kurashiki (GJ 205)
tags: [design_heritage, east_reach, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [kyoto-valley-estates, mirai-entertainment, namsan-collective]
---
# Kyoei Design
**Type:** Corporation — Design And Furniture Manufacturer
**Type:** Corporation — Design and Furniture Manufacturer
**Also Known As:** Kyoei, Kyoei House
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Kurashiki (GJ 205)
**Scope:** East reach primary; inward corridor premium distribution secondary
**Headquarters:** Kurashiki (GJ 205) — 3-aperture hub, 3 hops from Gateway
**Classification:** Sub-Syndic design enterprise; institutional and residential interior specification
Kyoei Design is a design and furniture manufacturer operating out of Kurashiki (GJ 205). Details to be expanded.
---
## Overview
The east reach corridor has its own visual language, developed across three centuries of settlement by communities who brought specific aesthetic traditions from different parts of Earth's heritage cultures and built something new from their combination. Kyoei Design makes furniture and interior fittings that speak this language — the proportions, materials, joinery techniques, and spatial philosophy that characterizes the east reach's most considered interiors. In institutional settings from Kurashiki to Hwaseong, Kyoei pieces appear in spaces where the environment is meant to communicate care.
The company's clients range from major east reach institutions commissioning large interior specifications to residential buyers purchasing individual pieces. The premium workshop output — hand-crafted pieces produced to close tolerances by trained woodworkers and joiners at the Kurashiki facility — is what the brand is built on. The broader catalog is where the volume lives.
---
## Origin
Kyoei Design was founded forty-one years ago by a furniture maker and an interior architect who had been working separately and whose complementary skills produced a collaboration that neither could sustain alone. The furniture maker had trained under an east reach craftsperson who had synthesized Kurashiki's dominant cultural influences into a coherent design methodology; the architect had institutional clients who wanted environments specified to a coherent aesthetic and lacked the furniture supplier to complete them.
The early years were pure workshop production — small volumes, significant craft investment, institutional clients who specified pieces with long lead times and paid accordingly. The workshop's reputation built through those clients and spread to residential buyers as Kurashiki's wealthier residential market recognized that Kyoei's pieces were the local aesthetic expressed at its highest level.
The licensed manufacturing arrangement was introduced twenty-three years ago as a response to demand that the workshop could not satisfy within its production constraints. The arrangement was controversial within the original founding partnership — the furniture maker's position was that expanding volume through licensing would compromise the craft identity the brand depended on. The architect's position was that the brand's reach would extend the workshop's cultural influence in ways that justified the quality compromise. The architect's view prevailed; the furniture maker retired five years later.
---
## Operations
**Premium workshop:** Fifteen craftspeople at the Kurashiki facility producing furniture, joinery, and interior fittings to Kyoei's full design specifications. Hand-crafted, close-tolerance, documented with provenance records that identify the supervising craftsperson. This is the work that appears in design publications and institutional commissions.
**Licensed manufacturing:** A licensing agreement with a manufacturing operation at a system two hops outward where production costs are substantially lower. The licensee produces Kyoei-designed pieces to Kyoei-specified parameters, at volume, for the mid-range catalog. Products from this facility ship under Kyoei brand marks and carry documentation describing them as "Kyoei Design — manufactured to specification."
**Catalog structure:** The premium workshop output is sold through direct institutional and residential channels with extended lead times. The licensed mid-range catalog is sold through interior specification firms and retail channels across the east reach corridor.
**Workforce:** The Kurashiki workshop employs fifteen craftspeople and eight administrative and design staff. The licensing agreement means Kyoei does not employ the manufacturing workers who produce its mid-range catalog.
---
## Political Relationships
**East reach institutional clients:** Kyoei's institutional relationships — research universities, financial institutions, government administration buildings — are long-standing and design-specification driven. These clients care about aesthetic consistency across an installation and are willing to pay for guaranteed supply continuity.
**Interior design profession:** Kyoei's catalog is a standard reference in east reach interior specification practice. Interior designers who work in the corridor know the catalog well enough to specify pieces without extensive lead-time negotiation, which makes the licensed manufacturing operation commercially necessary — the workshop alone could not supply the specification volume.
---
## The Licensing Structure
The manufacturing operation at the outward system employs workers under local employment law, which is the relevant legal framework because the manufacturer owns the employment relationship. Kyoei's licensing agreement specifies production parameters, quality standards, and delivery terms. It does not specify employment conditions — those are the manufacturer's operational responsibility.
The employment conditions at the manufacturing facility would not meet the Lattice Commission's labor standards for manufacturing operations if those standards applied to the facility's jurisdiction. They do not — the Commission's labor standards apply to Commission-registered enterprises operating within systems covered by the Commission's jurisdiction framework. The outward system where the manufacturer operates is a system with a Commission trade relationship but without full Commission jurisdiction coverage for labor regulation.
Kyoei's legal team examined the labor standards question when the licensing agreement was established and concluded that Kyoei bears no Lattice Commission labor standards liability because the design company is not the employer and the facility is not in a covered jurisdiction. The analysis is technically correct. The conclusion it reaches — that Kyoei can sell products produced under working conditions it could not legally impose on its Kurashiki workers without incurring liability — is the result of careful jurisdictional selection rather than coincidence.
The product documentation that accompanies mid-range pieces describes their origin as "manufactured to Kyoei Design specification." It does not describe the manufacturing facility's location or workforce arrangements.
---
## Gameplay Relevance
Kyoei Design is visible in the institutional and residential spaces of the east reach corridor — the furniture in offices, the joinery in corridors, the pieces that give Kurashiki's interiors their particular character. Relevant to investigations involving design industry economics, labor conditions, or jurisdictional arbitrage in manufacturing.
The licensing structure is the investigative thread. The evidence requires identifying the licensee (in Kyoei's commercial registry filings), locating the manufacturing facility, and examining the labor conditions at that facility relative to Commission standards for similar work in covered jurisdictions. The gap between the conditions in Kurashiki and the conditions at the manufacturing site is not hidden — it is simply on the other side of a jurisdictional line that was chosen with that gap in mind.
---
**Cross-References:**
- [Kurashiki](../star-systems/GJ-205/index.md) — Headquarters system; workshop; institutional client base
- [Kyoto Valley Estates](kyoto-valley-estates.md) — Kurashiki system neighbor; comparable east reach terroir brand
- [Mirai Entertainment](mirai-entertainment.md) — Kurashiki system neighbor; cultural parallel
- [Namsan Collective](namsan-collective.md) — East reach craft and cultural context
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/kyoto-valley-estates.md
+80 -6
View File
@@ -1,24 +1,98 @@
---
title: "Kyoto Valley Estates"
description: "Kyoto Valley Estates — regional specialty producer based in Kurashiki, east reach"
description: "Kurashiki-based premium beverage producer with named-estate positioning — specific valley terroir, provenance documentation for inward buyers, and estate boundary maps the company drew for itself"
slug: kyoto-valley-estates
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Kurashiki (GJ 205)
tags: [terroir, east_reach, tractus, scarcity_class_rare]
decision_refs: [D-189]
cross_refs: []
cross_refs: [kyoei-design, mirai-entertainment, calloway-distillery]
---
# Kyoto Valley Estates
**Type:** Corporation — Regional Specialty Producer
**Also Known As:** Kyoto Valley, the Estates
**Status:** Canonical
**Scope:** Regional — east reach operations
**Headquarters:** Kurashiki (GJ 205)
**Scope:** East reach primary; inward corridor premium market secondary
**Headquarters:** Kurashiki (GJ 205) — 3-aperture hub, 3 hops from Gateway
**Classification:** Sub-Syndic specialty producer; provenance-designated beverage estate
Kyoto Valley Estates is a regional specialty producer operating out of Kurashiki (GJ 205). Details to be expanded.
---
## Overview
Kurashiki's valley terrain — the elevated inland valleys on the primary habited world's temperate continent — produces a set of microclimates that agricultural scientists at the local university have studied at length and that wine producers have worked with for two centuries. Kyoto Valley Estates holds land across four of these valleys under named estate designations: Nishi, Higashi, Minami, and the founding Kyoto Valley proper. The wines produced from these estates carry provenance documentation that describes altitude, soil type, water source, harvest date, and fermentation parameters. They are taken seriously by buyers who take wine seriously, and they command prices that reflect the documentation's implied specificity.
At inward corridor distribution points, Kyoto Valley's named estate wines appear alongside bottles from systems with longer-established reputations. They compete on the provenance documentation — the argument being that the specific terroir of Kurashiki's valleys is as distinctive and as worth preserving as anything the corridor offers, and that the documentation proves it. The argument is largely correct.
---
## Origin
Kyoto Valley Estates was established by a viticulturist who had trained on Ran before the emigration corridor to the east reach opened and who identified Kurashiki's valley terrain as having characteristics compatible with serious wine production — the altitude, the temperature swing between day and night during the growing season, the mineral-rich glacial runoff that fed the valley floor soils. The first plantings were experimental; the first commercial harvest was thirty-eight years ago.
The named estate structure was introduced twelve years into operations, after it became clear that different valleys produced detectably different character in the wines grown in them. The Nishi estate, with its heavier clay soils, produced fuller-bodied expressions. The Higashi estate, on the valley's eastern slope with direct morning exposure, produced more aromatic wines. These differences were real and were documented in the winery's own technical records.
The decision to formalize named estates rather than simply releasing wines under a single Kyoto Valley mark was commercial — named estates produce the provenance story that commands premium pricing, and premium pricing was the path to viability at the volumes a small highland operation could produce.
---
## Operations
**Estate holdings:** Four named estates across Kurashiki's highland valleys, totaling approximately 800 hectares under cultivation. The vineyards are managed by an agricultural team of twenty-three, with seasonal contractor support during harvest. Production volumes are modest — scarcity is a feature of the positioning, not a failure of ambition.
**Production:** The winery facility at the Kyoto Valley estate proper handles all fermentation, aging, and bottling. The senior winemaker has been in the role for fourteen years and is the primary figure responsible for the technical quality the estates are known for.
**Provenance documentation:** Each release comes with a certificate of origin that identifies the specific estate, the harvest year, altitude and soil classification, and the winery's assay of the wine's mineral composition. These documents are used by inward distributors to support premium pricing and by collectors to authenticate bottles in the secondary market.
**Distribution:** East reach direct through the winery's own channels. Inward distribution through a premium importer at Ran who handles the Kyoto Valley mark across several inward markets.
---
## Political Relationships
**Kurashiki agricultural commission:** The commission oversees land use and water rights across Kurashiki's agricultural zones. The estates operate under water use agreements that are periodically reviewed. The commission's technical staff have visited the estates for water monitoring but have not conducted formal land boundary surveys.
**East reach specialty producers:** Kyoto Valley is occasionally compared to Calloway Distillery as an example of east reach terroir products that have built inward corridor premium reputations. The comparison is flattering and the company does not discourage it.
---
## The Estate Boundaries
Named estate designations in viticulture imply that the wine comes from grapes grown within a defined geographic area with the characteristics that the estate name represents. Buyers who purchase Kyoto Valley Nishi estate wine are purchasing, in their understanding, wine from the heavy clay soils on the valley floor that produce the fuller-bodied character the Nishi mark is associated with.
The estate boundary maps used in Kyoto Valley's provenance documentation were produced by the winery's own agricultural team, not by a regulatory body or an independent surveyor. The Lattice Commission has no formal terroir designation framework for the east reach corridor's beverage producing regions — the Commission's provenance standards for wine are inward-corridor standards that have not been extended to systems at Kurashiki's distance.
The winery's agricultural team drew the boundaries to capture the valley areas that produce the characteristics associated with each estate. In the case of the Nishi estate, the boundary map includes approximately 60% land with the heavy clay soil profile that produces the documented character, and approximately 40% adjacent land with lighter, more sandy soils that were included in the boundary because they were convenient to farm as a single unit. The lighter soils produce wine that is acceptable but lacks the body that the Nishi mark implies.
Volume years — years when demand exceeds premium-soil production — the blend ratio of heavy-clay to lighter-soil fruit in Nishi estate wines shifts. The provenance documentation does not change; the estate certificate for a Nishi wine describes the estate's defining characteristics accurately, since those characteristics are present in the estate as bounded. What the document does not disclose is the proportion of fruit in the bottle that exhibits those characteristics.
The boundary maps are in the winery's agricultural records. No external party has reviewed them against a soil survey.
---
## Gameplay Relevance
Kyoto Valley Estates is a secondary east reach institution relevant to investigations touching provenance documentation, wine trade, and the economics of scarcity products. The estates appear in premium retail contexts and are referenced in collector and importer correspondence across the corridor.
The boundary map question is the investigative thread. It requires accessing two sources: the provenance documentation (publicly filed with distributors) and the winery's internal agricultural records that show the estate boundary maps and the underlying soil survey data. The gap between what the boundary map claims and what the soil profile actually shows is documented in the winery's own records. A player working a provenance fraud case or an investigation into east reach food and beverage commerce standards will find this thread connected to the broader absence of a formal terroir designation framework for the east reach.
---
**Cross-References:**
- [Kurashiki](../star-systems/GJ-205/index.md) — Headquarters system; estate land; valley terrain
- [Kyoei Design](kyoei-design.md) — Kurashiki system neighbor; east reach premium parallel
- [Mirai Entertainment](mirai-entertainment.md) — Kurashiki system neighbor; cultural context
- [Calloway Distillery](calloway-distillery.md) — North reach terroir parallel; comparable provenance brand
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/leerfeld-records.md
+76 -5
View File
@@ -1,11 +1,11 @@
---
title: "Leerfeld Records"
description: "Leerfeld Records — cultural content producer based in Confluent, west reach"
description: "Prestige compositional label at Confluent (GJ 395) — slow output, uncompromising standards, the west reach's reference point for serious long-form music"
slug: leerfeld-records
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-21
scope: regional
faction_type: economic
headquarters: Confluent (GJ 395)
@@ -16,9 +16,80 @@ cross_refs: []
# Leerfeld Records
**Type:** Corporation — Cultural Content Producer
**Type:** Corporation — Compositional Music Label
**Status:** Canonical
**Scope:** Regional — west reach operations
**Scope:** West reach corridor; limited cross-corridor distribution via Meridian
**Headquarters:** Confluent (GJ 395)
**Currency:** Mark (Compact zone)
**Classification:** Sub-Syndic cultural enterprise; Compact-registered independent
Leerfeld Records is a cultural content producer operating out of Confluent (GJ 395). Details to be expanded.
---
## Overview
Leerfeld Records releases, on average, four albums per year. Other labels of comparable size release forty. This is not an accident. The founding principle — stated plainly on the label's charter, now seventy years old, and not revised since — is that music made quickly sounds like it. Leerfeld does not make music quickly.
The label operates out of Confluent, a west reach system known for its wine cooperative and its chemical manufacturing complex. Neither neighbor has anything to do with Leerfeld's sound, except that both represent the same regional disposition: patience as a production value. Grand Vide wines require years before release. Société Chimique's synthesis processes run on geological timescales by design. Leerfeld Records waits because the corridor waits, because the people who buy mark-denominated music in the west reach have learned to wait, and because the alternative is product that sounds like the hurry that made it.
What Leerfeld records is long-form composition. Their catalog skews instrumental, though not exclusively. They have released vocal works when the right artist brought the right material. What they do not release is anything that sounds finished before it is finished — which is a description the label has offered of other labels' output at various points in its history, publicly, with names attached, in ways that have not been forgotten.
---
## Origin
The label was founded seventy years ago by Gert Leerfeld, a composer who had spent fifteen years as a session musician at three different west reach labels and had concluded, after the third, that the production cycle in commercial music was structurally incompatible with compositional work. Session music is hired by the measure. Composition is made in months. The mismatch between how labels operate and how serious music is made had been obvious to Gert Leerfeld for fifteen years before he decided to address it by building a label around the music's timeline rather than the commercial one.
The original Leerfeld roster was three artists. All three were composers who had been dismissed from or frustrated out of major corridor labels for missing deadlines. All three delivered their first Leerfeld releases late. Gert Leerfeld did not release those albums until the artists were satisfied. The first three releases came out eighteen months after the label was founded. Two of them were the best-reviewed west reach albums of that decade.
Gert Leerfeld died forty years ago, a Perpetual-class citizen who had lived long enough to see the label outlive the commercial competitors who had been certain it would fail. His heirs hold the charter. The label's head of A&R, Maret Voss, has held the position for twenty-two years and intends to hold it until she does not.
---
## Operations
**A&R:** Leerfeld does not actively recruit. Artists approach the label or come through the network of longstanding relationships the label has maintained with music programs at Confluent's institutions and the broader west reach corridor. Maret Voss attends approximately six performances per year. She signs approximately one new artist per two years. The selectivity is not affectation — it is the operational constraint of a label that will spend three years on a single record and cannot afford to spend three years on a record that was not worth making.
**Production:** Leerfeld owns one studio at Confluent and maintains a remote recording arrangement with a facility at Ostmark. Sessions are scheduled without end dates. Artists are not asked when they will be finished; they are asked what they need. The studio's technical director has worked with every artist on the current roster and most of the artists on the historical one.
**Distribution:** Meridian-mediated, with standard west reach content classification through Compact protocols. Physical distribution (pressed media for collectors' market) is handled by a third-party distributor operating across the west reach corridor. Cross-corridor Meridian distribution exists for the label's back catalog; new releases are classified under Compact jurisdiction for the first year.
**Revenue:** The label's revenue model is deliberate: high per-unit price, low volume, stable catalog income. Albums that are fifteen years old still sell. The Leerfeld back catalog is the label's financial foundation — backlist earnings allow the label to front production costs that would bankrupt a higher-volume operation.
---
## Reach Position
Leerfeld Records is not large. Its cultural authority in the west reach corridor is disproportionate to its size. When a west reach artist is described as "Leerfeld-tier," the meaning is understood: they make work that does not compromise, at a pace that does not rush. The description is used as frequently to dismiss commercial artists as to praise uncommercial ones.
The label has a hostile relationship with the corridor's larger entertainment infrastructure on the principle that the infrastructure's incentives are wrong. Leerfeld does not license music for commercial placement. It does not participate in streaming-first release strategies. It does not sign artists to multi-album contracts that specify delivery timelines. These positions have been stated in public, repeatedly, and with the particular confidence of an institution that has survived long enough to watch the positions it criticized become the standard problems of the industry it declined to join.
---
## Political Relationships
**Compact cultural institutions:** Leerfeld is one of the small number of west reach cultural enterprises that the Compact's cultural policy apparatus cites when asked what Compact-zone music sounds like. The label does not seek this relationship and does not trade on it, but neither does it refuse the citations. The net effect is that Leerfeld's reputation underwrites the Compact's aesthetic self-description more than either party discusses in commercial terms.
**Meridian:** Cross-corridor distribution is licensed to Meridian with the longest-duration contracts the label maintains with any partner. The contracts include unusual terms — Leerfeld retains unilateral delay authority for new releases — that Meridian has accepted because the back catalog cash flow is steady and the new-release volume is small enough to absorb the scheduling irregularity.
**Confluent music program:** Leerfeld maintains consulting and guest-instructor relationships with the music program at Confluent's principal conservatory. Three current Leerfeld artists trained there. The A&R pipeline is not formalized — Maret Voss is simply visible at performances — but the relationship is the label's single most important source of new compositional talent.
---
## Silence Topic
What Leerfeld Records does not discuss: the artists who left.
Three artists in the label's history have signed, produced work over extended periods, and then parted from the label without a final release. The circumstances differ in each case. The label has not discussed any of them. The departed artists have variously described the experience as liberating, complicated, and something they prefer not to talk about. Maret Voss's standard response to questions about former artists is that she wishes them well and that the label's business is its current roster. This is accurate. It is not complete.
---
**Cross-References:**
- [Vins de Grand Vide](vins-de-grand-vide.md) — corridor neighbor; shared cultural register
- [Société Chimique du Vide](societe-chimique.md) — co-located at Confluent
- [Confluent (GJ 395)](../star-systems/GJ-395/index.md) — headquarters system; Compact-zone cultural corridor
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-21
wiki/corporations/lowlands-consumer.md
+77 -6
View File
@@ -1,24 +1,95 @@
---
title: "Lowlands Consumer"
description: "Lowlands Consumer — consumer goods manufacturer based in Dokkum, west reach"
description: "Dokkum-based west reach consumer goods manufacturer — household, personal care, and basic industrial supplies distributed across Mark-currency systems, and a cleaning concentrate under informal safety review for fourteen months"
slug: lowlands-consumer
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Dokkum (GJ 506)
tags: [commodity_branded, west_reach, mark, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [maas-rijn-entertainment, nordhavn-financial, norrland-woodcraft]
---
# Lowlands Consumer
**Type:** Corporation — Consumer Goods Manufacturer
**Also Known As:** Lowlands, LC Products
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Dokkum (GJ 506)
**Scope:** West reach corridor primary; Mark-currency systems secondary
**Headquarters:** Dokkum (GJ 506) — 3-aperture hub, 4 hops from Gateway
**Classification:** Sub-Syndic consumer goods enterprise; everyday commodity distribution
Lowlands Consumer is a consumer goods manufacturer operating out of Dokkum (GJ 506). Details to be expanded.
---
## Overview
Lowlands Consumer is the west reach corridor's dominant household goods supplier — present in commissary kitchens, maintenance lockers, and domestic supply cabinets from Dokkum outward across the Mark-currency systems. The catalog covers three major categories: household cleaning products under the Schoon mark, personal care basics under the Zorg line, and industrial maintenance supplies under the Technics brand. None of these are prestige products. They are staples, priced to move and packaged for durability in the transport conditions the west reach corridor involves.
The company's competitive advantage is logistical rather than product-driven. Lowlands has the most extensive west reach distribution network of any consumer goods manufacturer operating in the corridor, built over thirty years of route development, depot establishment, and supply agreement cultivation. Clients who switch away from Lowlands do not lose a better product; they lose predictable delivery windows and a restocking relationship they know works.
---
## Origin
Lowlands Consumer was founded at Dokkum thirty-one years ago by a logistics entrepreneur who had been operating a freight routing service and noticed that west reach systems were consistently under-supplied with basic consumer goods despite the freight capacity to support better supply. The founding insight was that the gap was in aggregation — no single goods producer had bothered to serve the full west reach corridor, so each system was sourcing from multiple suppliers with inconsistent availability.
The founding operation was a distribution company before it was a manufacturing company. Lowlands began by aggregating goods from multiple producers under its own logistics umbrella, then progressively brought production in-house as it developed sufficient demand certainty to justify manufacturing investment. The Schoon cleaning line was the first in-house product, introduced twelve years into the company's existence. Zorg and Technics followed.
---
## Operations
**Product lines:** The Schoon cleaning catalog covers approximately forty SKUs — surface cleaners, degreasing agents, sanitation concentrates, and specialty cleaning products for industrial applications. The Zorg line covers personal care basics: soaps, hygiene products, first aid supplies. Technics covers industrial maintenance consumables: lubricants, surface treatments, and specialty compounds for mechanical and environmental applications.
**Manufacturing:** Two production facilities at Dokkum and one at Nyrheim. The Nyrheim facility handles Technics production exclusively; the Dokkum facilities handle Schoon and Zorg.
**Distribution network:** Seventeen depot locations across the west reach corridor, with delivery schedules calibrated to the gate transit patterns of the corridor's aperture network. The depot network is the company's most capital-intensive asset and its primary barrier against competition.
**Workforce:** Approximately 280 people across production, logistics, depot operations, and administration.
---
## Political Relationships
**West reach retail and commissary networks:** Lowlands' primary commercial relationships are with the station commissaries, retail operations, and institutional buyers who stock its products. The supply agreement terms favor buyers who consolidate their sourcing through Lowlands — exclusivity incentives and volume pricing that make splitting supply across multiple providers economically inefficient.
**Lattice Commission consumer safety desk:** Consumer goods that include chemical compounds — cleaning products, industrial supplies — are subject to Commission safety standards for labeling, dilution guidelines, and exposure limits in enclosed spaces. Lowlands maintains a compliance file with the Commission's west reach consumer safety desk and submits product documentation as required.
---
## The Assessor Correspondence
Fourteen months ago, a Lattice Commission safety assessor at the west reach desk initiated a review of one of Lowlands Consumer's products — the Schoon Industrial Concentrate, a high-strength cleaning agent sold primarily to station commissaries and maintenance operations for dilution into working-strength cleaners. The review was initiated after a station maintenance supervisor submitted a query to the Commission's technical assistance service about safe dilution ratios for enclosed-space use.
The assessor's preliminary finding, documented in correspondence to Lowlands Consumer's compliance team, was that the dilution instructions printed on the Schoon Industrial Concentrate label produce a working solution that, in enclosed spaces with standard station air exchange rates, generates aerosol concentrations that exceed the Commission's exposure threshold for continuous occupational exposure. The instructions are not dangerously wrong — the margin is not large — but the assessor's assessment is that label revision and revised dilution guidance are indicated.
Lowlands Consumer's compliance team has been engaged in a process of providing clarifying documentation. Three rounds of correspondence have occurred over fourteen months. The first response provided the testing methodology the company used to establish the dilution instructions. The second provided additional data from a different testing methodology showing results closer to threshold. The third requested clarification of the specific testing parameters the assessor had used. The correspondence process has not produced a formal Commission finding, a product recall, or a label revision order — it has produced a discussion.
The product continues to be sold with the current label. The compliance team's internal position is that the assessor's preliminary finding is not a final determination and that the company's obligation to respond does not constitute an obligation to act on preliminary findings before they are finalized. This is a technically defensible reading of the process.
---
## Gameplay Relevance
Lowlands Consumer is ambient west reach commercial infrastructure — present wherever basic goods distribution is relevant, useful as background texture for west reach station environments.
The assessor correspondence is the investigative thread. It is a formal regulatory record — the Commission assessor's preliminary finding and the three rounds of correspondence are in the Commission's safety desk files and in Lowlands Consumer's compliance records. The gap between the preliminary finding fourteen months ago and the absence of any label change is the story. A player working a workplace exposure incident at a station using Schoon Industrial Concentrate, or investigating consumer safety enforcement practices in the west reach, will find this thread through the Commission's correspondence archive. The station maintenance supervisor who submitted the original query to the Commission's technical assistance service is an accessible source; their query is in the public correspondence record, and they have no relationship with Lowlands Consumer that would inhibit them from discussing what they observed.
---
**Cross-References:**
- [Dokkum](../star-systems/GJ-506/index.md) — Headquarters system; primary manufacturing and logistics base
- [Maas Rijn Entertainment](maas-rijn-entertainment.md) — Dokkum system neighbor; west reach institutional context
- [Nordhavn Financial](nordhavn-financial.md) — West reach financial context; Nyrheim corridor
- [Norrland Woodcraft](norrland-woodcraft.md) — West reach craft parallel; Nyrheim system
- [Kellervolk](kellervolk.md) — West reach institutional neighbor; Nyrheim corridor context
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/luanda-fabrication.md
+82 -8
View File
@@ -1,24 +1,98 @@
---
title: "Luanda Fabrication"
description: "Luanda Fabrication — precision technology manufacturer based in Matamba, south reach"
description: "Portuguese-Angolan precision substrate manufacturer at Matamba (GJ 884) — custom-spec electronic assemblies for south_reach technology firms, operating in the same system as the corridor's premier trade law firm"
slug: luanda-fabrication
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
scope: regional
updated: 2026-04-22
scope: south_reach primary; specialist supply contracts to inner corridor secondary
faction_type: economic
headquarters: Matamba (GJ 884)
tags: [tech_premium, south_reach, tractus, electronics]
decision_refs: [D-189]
cross_refs: []
cross_refs: [ferreira-monteiro, durban-engineering, cygni-combines]
---
# Luanda Fabrication
**Type:** Corporation — Precision Technology Manufacturer
**Type:** Corporation — Precision Substrate and Custom Electronics Assembly
**Also Known As:** Luanda Fab, LF
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Matamba (GJ 884)
**Scope:** South_reach electronics sector primary; inner corridor specialist contracts secondary
**Headquarters:** Matamba (GJ 884) — 3-aperture junction, 5 hops from Gateway
**Classification:** Sub-Syndic technology manufacturer; tier-one supply chain specialist
Luanda Fabrication is a precision technology manufacturer operating out of Matamba (GJ 884). Details to be expanded.
---
## Overview
Before a sensor or a navigation instrument or a communications relay can perform its specified function, someone has to fabricate the physical substrate on which its electronic architecture lives. That is Luanda Fabrication's work: precision substrate manufacturing, custom electronic assemblies, and the tolerance-grade production capability that south_reach technology firms need but cannot cost-justify building in-house when one manufacturer can serve the entire corridor.
Luanda Fab occupies a position in the south_reach electronics supply chain that is structurally load-bearing and commercially invisible. The monitoring systems that Durban Engineering installs at extraction sites contain Luanda-manufactured substrates. The companies whose names appear on the finished products are generally better known than the manufacturer of the layer beneath. Luanda prefers it this way. Client confidentiality is a commercial proposition in substrate manufacturing: clients design products around your capabilities, and they share proprietary specifications to do so. An indiscreet supplier loses clients and cannot recover the trust.
---
## Origin
The founding generation came from the same Portuguese-Angolan emigration cohort as the Ferreira and Monteiro families — Matamba's wave_2 settlement included a significant community with deep roots in Angola's manufacturing tradition, which had been rebuilding throughout the period preceding the expansion wave. The founders of Luanda Fabrication were electronics manufacturing specialists, not lawyers, and their founding proposition was complementary to Ferreira Monteiro's in a practical sense: the law firm was addressing the institutional gap in cross-framework trade; the fabrication operation was addressing the supply chain gap.
The specific gap: south_reach technology firms were importing precision substrates from east_reach manufacturers at transit-cost premium. The substrates themselves were not technically beyond local production capability — the founding cohort had the skills and the equipment. The barrier was scale and specialization. Individual south_reach electronics firms were too small to justify in-house substrate production. Luanda Fabrication was founded as the shared substrate manufacturer for the corridor's technology sector: one facility with the production capability to serve multiple clients, distributing the capital cost across a client base that benefited collectively from not needing to build and maintain their own.
The founding relationship with what would become Ferreira Monteiro was practical from the start. The law firm drafted the supply contracts and arbitrated the inevitable specification disputes. That relationship has remained continuous since the founding period — FM is still Luanda's legal counsel of record, which means the firm has handled four decades of Luanda's commercial documentation and knows the specifics of its supply relationships in more detail than most commercial law firms know their clients.
---
## Operations
**Substrate manufacturing:** Precision circuit board and electronic substrate fabrication at tolerances specified by client designs. Luanda does not design products; it manufactures to customer specifications with process consistency that justifies the tech_premium designation. The facility maintains a documentation trail that allows any substrate batch to be traced to its production parameters, calibration records, and material sourcing. This traceability is a significant selling point for clients whose own product certifications require supply chain documentation.
**Custom assembly:** Beyond bare substrates, Luanda provides custom electronic module assembly — integrating components supplied by the client or sourced to Luanda's specification, assembled under quality-control processes the client defines. The assembly capability serves clients who need complete modules rather than raw substrates, and who want production close to their own facilities to reduce transit risk and schedule uncertainty.
**Supply chain position:** Luanda sources component inputs from multiple suppliers. East_reach manufacturers — Cygni Combines being the largest — supply a significant fraction of the active components integrated into Luanda assemblies. This creates commercial dependency on east_reach supply chains that Luanda manages through diversification but cannot eliminate. The transit cost of east_reach components to Matamba is a constant competitive pressure on margins.
**Matamba facility:** Located in the transit node infrastructure that makes Ferreira Monteiro's cross-corridor practice viable. The facility employs approximately 150 people, with a significant proportion of engineering specialists recruited from across the south_reach. The salary premium Luanda offers for calibration and process engineering talent is above what most regional manufacturers can match, and the stability of long-term supply contracts makes employment attractive enough to sustain it.
---
## Political Relationships
**Ferreira Monteiro:** Co-located at Matamba, and Luanda's legal counsel of record for the past forty years. The relationship is institutionally close in ways that go beyond standard client-firm dynamics. Ferreira Monteiro's managing partners are aware of the specifics of Luanda's supply contracts, quality certification framework, and key client relationships in sufficient detail to provide substantive commercial advice rather than generic legal services. The depth of the firm's institutional knowledge about Luanda's operations is greater than Luanda's own clients possess.
**Durban Engineering:** The most significant direct client relationship. Durban's monitoring system substrates are manufactured at Luanda under a long-standing supply agreement, the specification document for which has been in place for over twenty years through three revisions. Durban's engineering team knows Luanda's facility and processes well. The relationship has the efficiency of a long partnership and the latent tensions that come with dependency — Durban cannot easily change substrate suppliers without recertifying its own products.
**Cygni Combines:** Component supply relationship. Cygni's east_reach electronics manufacturing capacity provides a meaningful fraction of the active components Luanda integrates into assemblies. Luanda has periodically explored alternative suppliers for specific component categories; Cygni's combination of component quality and transit cost is consistently the outcome of those explorations. The commercial relationship is transactional rather than strategic, which suits both parties.
---
## What They Don't Talk About
Fifteen years ago, the primary extraction source for a proprietary alloy specified in Luanda's flagship substrate formulation depleted below commercial viability. The alloy was named by specific designation in supply contracts with Durban Engineering and two other south_reach technology clients. It had been specified precisely because its thermal stability characteristics — consistent performance across the operating temperature range typical of extraction-environment electronics — were part of those clients' own product certifications.
Luanda sourced a functionally equivalent replacement alloy from a different provider. The replacement performs within the tolerance ranges specified in the supply contracts. The thermal stability characteristics are nearly identical. The engineering case for equivalence is strong.
The certification documentation continues to specify the original alloy by name. This was a deliberate choice. Notifying clients of the material substitution would have required renegotiating supply contracts, potentially triggering re-certification of the clients' own products, and disclosing a supply chain vulnerability that competitors would use. The legal assessment at the time — delivered verbally and not retained in any file — was that equivalence could be argued if the question were ever raised.
Ferreira Monteiro drew up the original supply contracts. The firm also handled the legal documentation for the extraction site closure fifteen years ago. The senior partner who managed both matters is still active at the firm. What she understands about the relationship between those two events has not been recorded in any document that either institution retains.
---
## Gameplay Relevance
Luanda Fabrication is a supply chain entry point. A player tracing the provenance of south_reach electronics — trying to understand what is inside a specific device and where its components came from — will eventually reach Luanda if the device was assembled in the corridor. The documentation trail Luanda maintains is comprehensive in the forward direction; the alloy substitution is a gap going back fifteen years, visible only to someone who compares current batch certifications against the original specification documents that Durban and the other clients hold in their own archives.
The Ferreira Monteiro relationship is the second thread. The law firm knows things about Luanda that Luanda's clients do not, and those things exist as institutional knowledge in the firm's case records rather than in any document Luanda itself controls. A player who has access to both sets of records and understands what they are looking at is facing a documentation discrepancy that has been maintained for fifteen years without being caught.
---
**Cross-References:**
- [Matamba](../star-systems/GJ-884/index.md) — Headquarters system; south_reach junction node
- [Ferreira Monteiro](ferreira-monteiro.md) — Legal counsel of record; co-located; holds institutional knowledge of supply chain
- [Durban Engineering](durban-engineering.md) — Primary client; long-term substrate supply agreement
- [Cygni Combines](cygni-combines.md) — Primary component supplier; east_reach supply relationship
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/lusaka-advisory.md
+62 -6
View File
@@ -1,24 +1,80 @@
---
title: "Lusaka Advisory"
description: "Lusaka Advisory — premium service provider based in Zenzele, south reach"
description: "South reach commercial strategy firm at Zenzele (GJ 1111) — extraction industry positioning, contract pre-negotiation, and the kind of advice that keeps disputes out of Ferreira Monteiro's dockets"
slug: lusaka-advisory
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Zenzele (GJ 1111)
tags: [service_premium, south_reach, tractus]
decision_refs: [D-189]
cross_refs: []
cross_refs: [ferreira-monteiro, baektu-mining-alliance]
---
# Lusaka Advisory
**Type:** Corporation — Premium Service Provider
**Type:** Corporation — Commercial Strategy and Advisory Firm
**Status:** Canonical
**Scope:** Regional — south reach operations
**Scope:** South reach corridor; extraction industry focus
**Headquarters:** Zenzele (GJ 1111)
**Currency:** Tractus
**Classification:** Sub-Syndic service enterprise; partnership structure
Lusaka Advisory is a premium service provider operating out of Zenzele (GJ 1111). Details to be expanded.
---
## Overview
Ferreira Monteiro handles commercial disputes in the south reach once they have become disputes. Lusaka Advisory works on the same problems before they reach that stage. The distinction sounds modest. The economics of it are not: Ferreira Monteiro's arbitration proceedings are expensive and slow, measured in months of partner time and the accumulated costs of two parties in conflict. A Lusaka engagement runs shorter and costs less, and the outcome — a contract structure that both parties can live with, a resource allocation that does not create the friction that produces arbitration — does not appear in any formal record. Commercial problems that do not become disputes are invisible. Lusaka Advisory's best work is invisible.
The firm operates at Zenzele, where Baektu Mining Alliance and Umoja Freight between them employ a significant fraction of the south reach corridor's extraction and logistics workforce. These are the industries Lusaka knows best — not because the firm has an ideological position on extraction, but because extraction generates the most contract complexity in the south reach. Mining allocations, freight agreements, resource processing contracts, community impact arrangements, labor agreements with workforces that have increasingly sophisticated negotiating capacity: the Zenzele economic environment produces, at any given time, more advisory work than the firm's sixteen partners can comfortably handle.
---
## Origin
The firm was founded thirty-five years ago by three commercial attorneys who had spent between ten and twenty years in Ferreira Monteiro's dockets on opposite sides of south reach extraction disputes. The founding insight was practical: the disputes were not inevitable. They arose from contract structures that left critical terms ambiguous, from resource allocation agreements that did not account for contingencies, from community arrangements that satisfied parties at signing without addressing the conditions that would change in year three or year seven. The attorneys who became Lusaka's founders had spent their careers resolving these problems after the fact and had concluded that resolving them before the contract was signed was possible, less expensive, and apparently not the business any existing firm was in.
Two of the three founders are still partners. The third retired fifteen years ago to Ran, citing the south reach's weather without further specificity. The firm has grown from three founding partners to sixteen, adding practice areas as the south reach's commercial environment has grown more complex. The extraction focus has remained constant.
---
## Operations
**Practice areas:** Resource contract structuring is the core practice — advising mining operations, processing facilities, and freight logistics providers on contract terms that distribute risk clearly, account for contingency conditions, and do not create the ambiguities that produce disputes. Community relations advisory is the second major practice: the south reach's extraction systems have established communities whose relationship with the extraction operations ranges from economically symbiotic to explicitly adversarial, and navigating that relationship before it reaches formal grievance stages is a discrete skill. Labor relations advisory is the third practice, addressing the increasing organizational sophistication of extraction workforce communities, particularly in systems where Guardians of Autonomy chapters have developed effective negotiating frameworks.
**Clients:** Extraction operations, freight logistics companies, processing facilities, and the community governance structures that negotiate with them. The firm represents both corporate clients and, on separate engagements, community interests — maintaining internal walls between these practice streams that the firm considers professionally adequate.
**Engagement model:** Retained advisory for ongoing relationships, project engagement for specific contract negotiations, and emergency advisory for clients who discover, mid-negotiation, that their position is weaker than they believed. The emergency advisory rate is higher and the firm does not apologize for this.
---
## What They Don't Talk About
The walls between Lusaka's corporate and community practice streams are real. The information from one engagement does not transfer to the other. What does transfer, over time, is pattern knowledge: the firm's partners, collectively, know which corporate clients negotiate in which ways, where the pressure points are, what a given community organization is likely to accept at what stage of a negotiation. This knowledge is not shared between engagement teams. It is also not compartmentalized in any meaningful way — it lives in the partners' heads, informing how they structure advice on each side without crossing the formal engagement boundary.
Two senior partners have had this explained to them by a Ferreira Monteiro arbitrator reviewing a dispute where both sides had previously retained Lusaka. The explanation did not result in formal findings. The partners' response was to update their conflict-of-interest protocols. The protocols now require disclosure of prior engagements with opposing parties. They do not require disclosure of accumulated pattern knowledge about how those parties negotiate, because that knowledge is professional experience rather than privileged information and is not subject to the same disclosure requirements.
The firm's cross-engagement reference ledger — an internal partner-only document maintained since the 2052 restructuring — is the documentary anchor. It records, for each active and historical engagement, the other engagements the firm has taken touching the same counterparties, sectors, or negotiating patterns. The ledger's stated purpose is conflict identification; its actual function is to let partners consult each other's histories when structuring new engagements. The Ferreira Monteiro arbitrator who raised the earlier explanation did not know the ledger existed. A subsequent partner-retreat memo (2058) explicitly declines to present the ledger in any dispute forum, on advice from the firm's outside counsel that the ledger's contents could be characterized as evidence of coordinated advantage across ostensibly walled engagements. The memo is held in the firm's partner-only archive at the Lusaka office. A copy went to outside counsel and is subject to standard legal privilege.
---
## Gameplay Relevance
Lusaka Advisory is a source and a threat in any investigation touching south reach commercial relationships. A player who needs to understand the contract structure of a resource agreement — what terms were negotiated, where the pressure points are, why a particular arrangement was structured the way it was — can find that understanding at Lusaka if they can access a partner with the relevant engagement history. Partners are professionally discreet; they are not personally hostile. The right relationship, or the right leverage, opens the right conversation.
The dual-client pattern knowledge is the concealed thread. An investigator who can demonstrate that Lusaka's partners have pattern knowledge of both parties in a specific dispute — not through formal disclosure but through the accumulated expertise of decades of south reach practice — is in a position to challenge the integrity of advice given on one or both sides. The challenge does not require proving a formal breach. It requires establishing that the advice could not have been independent, which is a different and potentially more demonstrable claim.
---
**Cross-References:**
- [Ferreira Monteiro](ferreira-monteiro.md) — south reach commercial arbitration; the formal process Lusaka's work is designed to precede
- [Baektu Mining Alliance](baektu-mining-alliance.md) — primary corridor client; extraction industry anchor
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/lusitanian-glass.md
+78 -6
View File
@@ -1,24 +1,96 @@
---
title: "Lusitanian Glass"
description: "Lusitanian Glass — heritage craft manufacturer based in Caparica, south reach"
description: "Caparica-based heritage glass workshop producing hand-blown architectural and luxury tableware — a marginal but revered operation, and three flagship pieces in institutional collections whose design credit was quietly reassigned"
slug: lusitanian-glass
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Caparica (GJ 1002)
tags: [heritage_craft, south_reach, tractus, artisan]
decision_refs: [D-189]
cross_refs: []
cross_refs: [iberian-standard-foods, alentejo-partners, destilaria-confluencia]
---
# Lusitanian Glass
**Type:** Corporation — Heritage Craft Manufacturer
**Also Known As:** Lusitanian, the Glass House
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Caparica (GJ 1002)
**Scope:** South reach corridor primary; limited inward institutional commissions secondary
**Headquarters:** Caparica (GJ 1002) — 3-aperture hub, 4 hops from Gateway
**Classification:** Sub-Syndic artisan enterprise; heritage craft glass production
Lusitanian Glass is a heritage craft manufacturer operating out of Caparica (GJ 1002). Details to be expanded.
---
## Overview
Glass-blowing is a craft that survived corridor travel because it requires little physical equipment beyond a furnace and the technique of the person at the pipe. The founding generations at Caparica brought both, and Lusitanian Glass is what three centuries of their descendants have built from the inherited tradition. The studio produces hand-blown architectural glass for institutional commissions — window panels, partition screens, decorative load-bearing elements for interior specifications — and a tableware line for the premium domestic and hospitality market.
In the south reach corridor, Lusitanian Glass occupies a position similar to Calloway Distillery's in the north reach: a heritage product produced by skilled people in a specific place, with a provenance story that sustains premium pricing inward. The pieces in institutional settings at Caparica are known. Collectors in the inward corridor systems who buy Lusitanian tableware know the studio's history. The brand carries weight beyond what a strictly commercial analysis would predict.
---
## Origin
The glass-blowing tradition at Caparica descends directly from the founding generation's craft knowledge, transmitted through a sequence of master-apprentice relationships that has never fully broken. The Lusitanian Glass workshop was formally incorporated three generations ago, when what had been a family craft operation became large enough to require a legal entity for institutional commission management and export documentation.
The incorporating generation made the architectural glass line the studio's primary commercial focus — the commission work that institutions paid reliably for and that could sustain the furnace and the people around it. The tableware line was a secondary offering, initially sold locally and eventually distributed inward through a premium goods importer who understood the market for authenticated craft objects.
The studio's physical location, in a low stone building near Caparica's original settlement center, is treated as part of the heritage. The furnace has been rebuilt three times but occupies the same footprint as the original. The workshop's output is always described in relation to this continuity.
---
## Operations
**Architectural glass:** The primary revenue line. Institutional commissions for window panels, decorative screens, and specialty glass fittings. Projects of this scale require extended lead times — months of design consultation, prototype production, and phased fabrication. The studio maintains a commission queue of eighteen to twenty-four months.
**Tableware:** A secondary line produced in smaller volumes, sold through the studio's own retail point and through inward distribution. The tableware pieces carry the studio's mark and are documented in production records. Collectors and hospitality buyers purchase these at prices that reflect the craft investment.
**Economic reality:** The furnace, the skilled artisans, and the building cost more to sustain than the production volumes can straightforwardly support. Lusitanian Glass is viable because institutional commission fees are substantial and because the studio's revenue is supplemented by a south reach arts foundation grant that the studio has held for eleven years. Without the grant, the furnace economics would require either significant volume expansion — incompatible with the craft positioning — or a significant price increase that the market might not support. The studio's current management team thinks about this regularly and discusses it with no one outside the studio.
**Workforce:** Seven active artisans at various levels of the apprenticeship structure, three administrative and logistics staff, and the studio manager who serves as the primary point of contact for institutional clients.
---
## Political Relationships
**Caparica institutional community:** Lusitanian Glass has a long relationship with Caparica's civic institutions — a panel installed in the regional administrative building twenty years ago, work in the primary medical facility's public spaces, and pieces in the collections of several private foundations. These institutional relationships provide both commission revenue and the social network that sustains the studio's access to future commission opportunities.
**South reach arts foundation:** The grant relationship is managed through annual applications and portfolio reviews. The studio's current application describes it as "sustaining an irreplaceable craft tradition in the south reach corridor," which is accurate. The foundation's assessment team has visited the studio twice in the past decade.
---
## The Three Pieces
Among the most frequently cited works in Lusitanian Glass's portfolio are three large-format architectural pieces produced eleven years ago for institutional commissions: a window panel installed at Caparica's primary legal institution, a partition screen in a financial house's client meeting suite, and a decorative element in a civic assembly space. All three are photographed in the studio's portfolio materials. All three are described in those materials as "Lusitanian Glass workshop" pieces.
The three pieces were designed by an artisan who was employed at the studio at the time, under an employment agreement that assigned intellectual property rights in work produced during employment to the studio. The artisan contributed the original design concepts, the prototype development, and the majority of the technical decisions that give the pieces their distinctive character. The design credit in the studio's documentation was assigned to "the Lusitanian Glass workshop" rather than to the individual artisan — a practice the studio describes as standard for workshop production, where multiple people contribute to a finished piece.
The artisan left the studio four years after the pieces were completed, following a period of conflict with the studio manager about compensation and recognition. The artisan's view is that the three pieces represent a significant individual creative contribution that should carry their name in any responsible account of the work. The studio's legal position, reviewed when the artisan raised the issue informally after leaving, is that the employment agreement is clear and that the "workshop" credit practice is legally defensible.
The artisan has not pursued the dispute formally. The studio has not changed its documentation. The three pieces continue to appear in portfolio materials, grant applications, and award submissions without individual attribution.
---
## Gameplay Relevance
Lusitanian Glass is a south reach heritage institution — relevant in investigations touching craft authenticity, intellectual property, and the economics of arts foundation grant dependency. The studio's pieces are ambient in Caparica's institutional spaces.
The attribution dispute is the investigative thread. The evidence is in two places: the studio's documentation of the three pieces (in portfolio materials and the original commission contracts) and the artisan's own records of the design process (sketches, correspondence, prototype records from the employment period). The employment agreement is the legal document; the gap between what the agreement permitted and what the artisan's contribution consisted of is the story. The artisan is findable and is not bound by any nondisclosure agreement.
---
**Cross-References:**
- [Caparica](../star-systems/GJ-1002/index.md) — Headquarters system; workshop; institutional clients
- [Iberian Standard Foods](iberian-standard-foods.md) — Caparica corridor neighbor; south reach commercial context
- [Alentejo Partners](alentejo-partners.md) — South reach agricultural parallel; Caparica system
- [Destilaria Confluência](destilaria-confluencia.md) — Caparica corridor neighbor; comparable heritage craft positioning
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/maas-rijn-entertainment.md
+78 -6
View File
@@ -1,24 +1,96 @@
---
title: "Maas Rijn Entertainment"
description: "Maas Rijn Entertainment — cultural content producer based in Dokkum, west reach"
description: "Dokkum-based west reach media production company — serialized entertainment, music recording, and an IP licensing portfolio built on rights whose original chain of title cannot survive close examination"
slug: maas-rijn-entertainment
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Dokkum (GJ 506)
tags: [cultural, west_reach, mark, entertainment]
decision_refs: [D-189]
cross_refs: []
cross_refs: [kellervolk, lowlands-consumer, ashwick-broadcasting]
---
# Maas Rijn Entertainment
**Type:** Corporation — Cultural Content Producer
**Also Known As:** Maas Rijn, MRE
**Status:** Canonical
**Scope:** Regional — west reach operations
**Headquarters:** Dokkum (GJ 506)
**Scope:** West reach corridor primary; Mark-currency systems secondary
**Headquarters:** Dokkum (GJ 506) — 3-aperture hub, 4 hops from Gateway
**Classification:** Sub-Syndic entertainment enterprise; production and IP licensing
Maas Rijn Entertainment is a cultural content producer operating out of Dokkum (GJ 506). Details to be expanded.
---
## Overview
Maas Rijn Entertainment is the west reach corridor's commercially successful production company rather than its culturally prestigious one — the studio that produces the serialized dramas people actually watch, the music releases that top regional charts, the entertainment programming that fills the broadcast hours after the commissioned cultural works have run. Kellervolk gets the awards; Maas Rijn gets the renewal orders.
The company has operated at Dokkum for twenty-six years and has built its catalog through a combination of original production and acquisition. The acquisition side of the business — buying distribution rights, catalog holdings, and in several cases entire smaller companies — has been as significant to Maas Rijn's growth as original production. The company's internal description of its business emphasizes the catalog: it holds significant IP across the west reach's entertainment history, and licensing that IP to broadcasters, streaming services, and secondary distributors provides a revenue base that makes the production business's variable returns manageable.
---
## Origin
Maas Rijn Entertainment was founded by a pair of producers who had worked at different west reach broadcast operations and combined their contacts and production experience to establish an independent studio. The early years were spent developing a first-look relationship with a Dokkum broadcaster and producing serialized drama at modest budgets with reliable audience numbers. The original productions are still the most critically regarded work the company has done; the transition to scale changed the economics and the ambitions.
The acquisition phase began fifteen years ago when a smaller west reach distributor — Maas Music Holdings — encountered financial difficulties after a licensing dispute. Maas Rijn acquired the company's assets, including a catalog of recorded music and distribution rights accumulated over the distributor's twenty-year existence. The acquisition resolved the distributor's creditor obligations and gave Maas Rijn its first significant catalog holding. Four subsequent acquisitions followed over the next decade.
---
## Operations
**Original production:** Eight to twelve productions in various stages of development at any time. Serialized drama is the primary format; music production and documentary programming are secondary. The production operation employs a core staff of thirty-two and contracts substantially for specific projects.
**IP licensing:** The catalog licensing operation is managed by a dedicated team of six who handle rights clearances, licensing agreements, and secondary distribution negotiations. The catalog currently generates approximately 40% of total revenue, a proportion that has increased steadily over the past decade as catalog holdings have grown.
**Acquisitions:** Maas Rijn's strategy has been to acquire distressed catalog holders — companies whose IP holdings are valuable but whose operations are not — and integrate the catalog into the licensing operation. The company does not typically retain the operating businesses.
**Workforce:** Forty-five core employees, heavily weighted toward production and licensing functions.
---
## Political Relationships
**West reach broadcasting:** Maas Rijn's primary commercial relationships are with the west reach corridor's broadcast operations, which are the primary distribution channel for original productions and the largest single category of catalog licensees. The first-look relationship with the Dokkum broadcaster has been maintained, though renegotiated twice as the company's leverage has grown.
**Kellervolk:** Maas Rijn and Kellervolk overlap in the west reach cultural production space and are occasionally in competition for the same distribution windows. The relationship is professionally managed and commercially competitive. Kellervolk does not regard Maas Rijn as a cultural peer; Maas Rijn does not regard Kellervolk as a commercial one.
---
## What the Catalog Audit Would Find
When Maas Rijn acquired Maas Music Holdings fifteen years ago, the acquisition agreement included a rights inventory — a list of the catalog assets being transferred, with representations from the seller about the validity of the rights. The acquisition team conducted what is described in the board minutes as a "business-level review" of the inventory: checking that the listed assets were what the seller described them as, without examining the underlying chain of title for each item.
Maas Music Holdings had been in operation for twenty years at the time of the acquisition. It had accumulated its catalog through its own acquisitions and distribution agreements, some of which dated to the early west reach corridor period when rights documentation practices were informal. The Holdings company's records were not comprehensive; some agreements existed only in paper form in filing systems that had not been fully digitized.
The Lattice Commission's IP standards require that commercial licensing of entertainment works be supported by a clear chain of title — documented evidence of an unbroken sequence of ownership from the original rights holder to the current licensor. Maas Rijn's licensing team has processed thousands of licenses from the acquired catalog without conducting chain-of-title reviews on each item.
A systematic chain-of-title audit of the catalog would find at least six active licensing income streams — identified by Maas Rijn's most experienced rights manager, who has flagged these informally to management — where the underlying documentation cannot demonstrate a complete ownership chain. In three of these cases, the issue is that the original creator's assignment agreement has been lost. In two cases, the assignment agreement exists but was signed by someone who may not have had authority to assign the rights. In one case, the west reach broadcaster who held the original distribution rights before the Holdings acquisition appears in the chain of title without a documented assignment to Holdings.
The licensing income from these six streams flows without interruption. The risk that a rights claimant would surface is assessed by Maas Rijn's legal team as low, because the original rights holders are organizations that no longer exist or individuals who are not commercially positioned to pursue a claim. The assessment treats the claim risk as low. It does not address the question of whether the current licensing is valid.
---
## Gameplay Relevance
Maas Rijn Entertainment is relevant to west reach investigations touching IP rights, entertainment economics, and the relationship between catalog value and documentation quality. The company's products are ambient in west reach cultural contexts.
The catalog chain-of-title question is the investigative thread. The evidence requires access to two sets of records: Maas Rijn's licensing database (which identifies the active income streams) and the underlying rights documentation for the flagged items (in the Holdings acquisition files). The rights manager who flagged the issue informally is an internal source with direct knowledge of which items are at risk. The original creator or rights holder records for the three lost assignment cases may exist in separate archives — broadcast registries, personal estates, or Commission copyright records from the Holdings company's operational period.
---
**Cross-References:**
- [Dokkum](../star-systems/GJ-506/index.md) — Headquarters system; production base; broadcast relationships
- [Kellervolk](kellervolk.md) — West reach cultural competitor; overlapping distribution market
- [Lowlands Consumer](lowlands-consumer.md) — Dokkum system neighbor; west reach commercial context
- [Ashwick Broadcasting](ashwick-broadcasting.md) — Broadcast distribution relationship; first-look corridor
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/maison-cinq.md
+79 -7
View File
@@ -1,24 +1,96 @@
---
title: "Maison Cinq"
description: "Maison Cinq — design and furniture manufacturer based in Sirius, core"
description: "Sirius luxury design house — institutional interiors for the Assembly and Syndic class, founded by five designers who understood that a capital city needs to look like one, and has spent 180 years making sure it does"
slug: maison-cinq
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Sirius (GJ 244A)
tags: [design_heritage, core, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [the-registry]
---
# Maison Cinq
**Type:** Corporation — Design And Furniture Manufacturer
**Type:** Corporation — Luxury Design and Institutional Interiors
**Also Known As:** the Maison, Cinq
**Status:** Canonical
**Scope:** Regional — core operations
**Headquarters:** Sirius (GJ 244A)
**Scope:** Core primary; reach-wide institutional commissions secondary
**Headquarters:** Sirius (GJ 244A) — 5-aperture hub, 1 hop from Gateway
**Classification:** Sub-Syndic design enterprise; Assembly-adjacent institutional supplier
Maison Cinq is a design and furniture manufacturer operating out of Sirius (GJ 244A). Details to be expanded.
---
## Overview
When the Concord Assembly consolidated its institutional presence at Sirius and began building the physical infrastructure of a permanent capital, someone had to decide what that infrastructure should look like. The Assembly's founding generation were administrators and diplomats, not designers. What they understood was that a governing body requires spaces that project continuity, authority, and cultural weight — and that these qualities do not emerge from a brief to "make it look official." They require considered aesthetics applied by people who understand what they are being asked to communicate.
Maison Cinq was the answer to that understanding. Founded 180 years ago by five designers from Sirius's French-heritage community, the Maison built its practice on a simple proposition: the physical environment of governance is a form of governance. A chamber in which delegates feel transient produces different decisions than a chamber in which they feel permanent. A residence that projects its inhabitant's cultural significance produces different negotiations than a residence that is merely expensive. The Maison does not make things look impressive. It makes things feel true.
The founding five's client list grew from Assembly chambers to Syndic delegation suites to private residences to commercial headquarters — anywhere that the intersection of significant wealth and significant institutional aspiration required a designed environment. The Maison has been the default answer to that brief at Sirius for four generations and has expanded, through referral, to commissions across the core and mid-reach corridor.
---
## Origin
The five founding designers — Aubert, Renard, Moreau, Pelletier, and Voss — met at the Sirius Institute of Applied Design in the Academy's second decade of operation. They were not particularly close. What they shared was a conviction, developed through different routes, that the dominant aesthetic of Assembly-era institutional design was performing the wrong kind of authority: heavy materials, deliberate grandeur, the visual language of permanence through mass. They argued, in a joint submission that the Institute published and the Assembly's design procurement office called "interesting but premature," that institutional authority communicated through restraint was more durable than authority communicated through accumulation.
The submission's timing was fortunate. The Assembly's expansion program had just produced its first major design failure: a chamber complex that was universally described as imposing and almost immediately described as oppressive. The procurement office's response to the Maison's founding proposal, issued six months later, was less qualified than the first response had been.
The Maison's first commission was a single delegation wing of the second Assembly expansion. The wing was completed three years late and substantially over initial budget estimates, both of which the founding five attributed to the procurement office's tendency to add requirements during construction and neither of which was attributed publicly to the designers. The finished space was regarded, immediately and unanimously, as the best thing in the building.
---
## Operations
**Institutional commissions:** The Maison's core practice is the design and fit-out of formal institutional spaces — Assembly chambers, delegation suites, government residences, ceremonial venues. Each commission is approached as a singular project; the Maison does not produce repeatable designs. The lead designer assigned to a commission works with the client through a briefing process that the Maison describes as "establishing what the space is for before deciding what it looks like," which some clients find clarifying and others find obstructive.
**Private and commercial commissions:** A secondary practice serving the senior commercial class and high-ranking Assembly personnel. Private commissions are taken selectively; the Maison's criteria for accepting private work are not published, but an accepted commission signals something about the client's institutional standing that is understood in the relevant circles. Waiting lists for private commissions are measured in years.
**Materials sourcing:** The Maison maintains supply relationships for specific materials — stone, textile, timber, fabricated metal components — across the Reach. Some of these relationships are proprietary in the sense that the Maison has exclusive arrangements with specific producers. Calloway Workshop at GJ 3325 has supplied bespoke joinery work for north-reach referral commissions; the relationship is occasional and unpublicized.
**Studio:** Forty-eight design and production staff at Sirius, with a smaller project management office at Ran for mid-reach commissions. The studio is not open to visitors. The Maison conducts client briefings at client sites.
---
## Political Relationships
**The Concord Assembly:** The Maison's primary institutional client is also its most complicated political relationship. The Assembly's procurement committee controls the institutional commission awards that constitute the Maison's most significant revenue. Sitting members of the committee are not permitted to participate in procurement decisions that directly benefit entities with which they have financial relationships. The Maison does not have financial relationships with any sitting committee members that it is aware of.
**The Sirius design and fabrication community:** The Maison works with a network of specialist fabricators and craftspeople across Sirius's manufacturing sector. These relationships are commercial and long-term; the Maison's reputation depends on the quality of execution as much as the quality of design, and it cannot separate the two. Several of these fabricator relationships have survived three generations of management changes on both sides.
**The Registry at Groombridge:** The Registry's commercial intelligence files include a Maison Cinq profile maintained since the institution's second century. What the Registry knows about the Maison's client list, commission values, and procurement relationships is not a question the Maison has asked and is not something the Registry volunteers. The Registry's Standard Report does not cover design houses; the Deep Trace service, which any client could commission, would.
---
## What They Don't Talk About
The current chair of the Assembly's Capital Infrastructure Committee — the body that oversees institutional design commission awards — is Édouard Pelletier-Renard, a fourth-generation descendant of two of the Maison's five founders. He holds a minority equity stake in the Maison through a family trust structure established by his great-grandmother, which he has never divested and which he has never declared to the Committee's conflict-of-interest registry.
Pelletier-Renard recuses from votes specifically about Maison Cinq's direct commission bids. What he participates in is the design brief formulation process — where the Committee establishes what qualities an institutional commission requires, which firms are considered technically capable, and which evaluation criteria matter. These decisions, made before any bid is submitted, shape which firms can compete and on what terms. The Maison's bid success rate on Assembly institutional commissions over the past twenty years is 71%. The next-highest rate among regular bidders is 34%.
The Registry's commercial intelligence files contain the summary of this pattern. The Registry has not been asked to publish it.
---
## Gameplay Relevance
Maison Cinq is ambient prestige infrastructure — a player moving through Assembly chambers, Syndic delegation facilities, or the private residences of Sirius's institutional class will encounter the Maison's work as the physical environment they're operating in. The design is distinctive to a knowledgeable observer: the restraint, the specific material choices, the way sightlines are managed in rooms that are meant to be navigated rather than admired.
The procurement conflict is the investigative thread. A player who discovers Pelletier-Renard's equity stake and connects it to the Capital Infrastructure Committee's brief-setting process has found something that the Assembly's ethics framework was not designed to catch — because the framework addresses direct votes, not the upstream influence that shapes which votes are necessary. The Registry's commercial intelligence files are the fastest route to the statistical summary of the Maison's commission success rate, which is the evidence that suggests the question before the player can confirm the answer.
---
**Cross-References:**
- [Sirius](../star-systems/GJ-244A/index.md) — Headquarters system; Assembly capital
- [The Registry](the-registry.md) — commercial intelligence file; procurement pattern analysis
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22
wiki/corporations/makuti-consumer.md
+78 -6
View File
@@ -1,24 +1,96 @@
---
title: "Makuti Consumer"
description: "Makuti Consumer — consumer goods manufacturer based in Mwangaza, south reach"
description: "Mwangaza-based south reach consumer goods manufacturer — broad packaged goods range, white-label contract production, and a 'locally produced' marketing claim maintained by one qualifying production line representing 15% of actual volume"
slug: makuti-consumer
category: corporation
status: canonical
created: 2026-04-19
updated: 2026-04-19
updated: 2026-04-22
scope: regional
faction_type: economic
headquarters: Mwangaza (GJ 693)
tags: [commodity_branded, south_reach, tractus, consumer_goods]
decision_refs: [D-189]
cross_refs: []
cross_refs: [mwanga-media, iberian-standard-foods, kalahari-leatherworks]
---
# Makuti Consumer
**Type:** Corporation — Consumer Goods Manufacturer
**Also Known As:** Makuti, MC Products
**Status:** Canonical
**Scope:** Regional — south reach operations
**Headquarters:** Mwangaza (GJ 693)
**Scope:** South reach corridor primary; limited broader distribution secondary
**Headquarters:** Mwangaza (GJ 693) — 2-aperture system, 5 hops from Gateway
**Classification:** Sub-Syndic consumer goods enterprise; packaged goods and white-label production
Makuti Consumer is a consumer goods manufacturer operating out of Mwangaza (GJ 693). Details to be expanded.
---
## Overview
In the south reach corridor's outer systems, Makuti Consumer is the name on the packaging for a wide range of ordinary things — packaged food products, household supplies, basic personal care goods, commissary staples. The brand does not have a distinctive voice or a specific heritage claim. Its competitive argument is coverage: a broad product range, consistent availability across the south reach, and pricing calibrated to the corridor's economic realities. In the absence of a premium product story, presence is the strategy.
The company's marketing materials emphasize its Mwangaza roots — the phrase "locally produced for south reach needs" appears on packaging and in distribution agreements. This regional identity argument matters to south reach institutional buyers who face constituency expectations about supporting local production, and it matters to distributors who can justify margin structures on goods positioned as regionally authentic rather than purely commodity-sourced.
---
## Origin
Makuti Consumer was established at Mwangaza eighteen years ago as an offshoot of an agricultural processing cooperative that had been operating informally for a generation. The cooperative's original activity was buying surplus harvest output from Mwangaza's farming zones and converting it into packaged goods for local consumption and limited corridor distribution.
The transition to a corporate entity was driven by investment from a south reach commercial holding company that saw an opportunity to scale the cooperative's production and distribution capacity. The investment brought manufacturing equipment, expanded facilities, and a professional management team. The cooperative's founding members retained minority ownership; the holding company held majority control from the beginning.
The "locally produced" identity claim was established during the early corporate period, when Mwangaza-origin goods genuinely constituted the majority of production. The operational reality has shifted since.
---
## Operations
**Product lines:** Packaged food products under the Makuti Home brand — preserved goods, grain-based staples, condiment lines. Household and personal care supplies under the Mwangaza Clean brand. Basic industrial consumables under a third mark primarily used for institutional supply contracts. Approximately 220 SKUs across these lines.
**Own production:** The Mwangaza facility handles production for approximately fifteen percent of volume by units, including the product lines that are most visible in local retail and most commonly cited in marketing materials. These lines use Mwangaza agricultural inputs and can legitimately support origin claims.
**Contract manufacturing:** The majority of Makuti's volume — approximately 85% by units — is produced by contract manufacturers at two south reach systems where production costs are lower. These manufacturers produce to Makuti's specifications, under Makuti's brand marks, and ship finished goods to Mwangaza for repackaging and redistribution in some cases, or directly to distributors in others.
**White-label operations:** A secondary revenue line involves producing goods for other companies' brands at the Mwangaza facility. This is the facility utilization strategy that keeps the own-production operation economically viable despite its small share of total volume.
---
## Political Relationships
**South reach institutional buyers:** Makuti's institutional clients — station commissaries, government supply contracts, educational institution food service — are the buyers most sensitive to the "locally produced" positioning. Several of these contracts specify regional content requirements; Makuti has satisfied these requirements by pointing to the Mwangaza facility's existence and output.
**Mwangaza government:** The south reach regional administration at Mwangaza has provided infrastructure support to Makuti on the basis of its status as a local employer. The company's economic contribution to the system is genuine — the Mwangaza facility employs people, purchases local agricultural inputs, and provides the commercial base that several support businesses depend on. The size of that contribution relative to the brand's revenue is the part that is not examined closely.
---
## The Production Line That Makes the Claim Work
The Lattice Commission's standards for regional content claims in consumer goods labeling require that goods making such claims be produced within the designated region — a simple geographic rule that does not specify a minimum share of the producer's total production. A company that produces one unit locally and a million units elsewhere can label the local unit "locally produced" without violating the standard.
Makuti Consumer's "locally produced for south reach needs" labeling is applied to all products across all Makuti brands, including the lines produced by contract manufacturers at other systems. The legal basis for this practice is that the labeling claim refers to the company, not to a specific production batch — it is an identity claim about Makuti as a locally founded, locally headquartered enterprise with a facility at Mwangaza.
The regulatory filing that supports this reading uses the Mwangaza facility's existence and certification as the evidence for regional status. The filing is accurate: the facility exists, is certified, and is locally operated. The filing does not disclose that this facility represents 15% of actual production volume.
Makuti's legal team reviewed the labeling practice when the contract manufacturing share of production exceeded 50% — the threshold the team had internally flagged as the point at which the claim required review. The review concluded that the claim was defensible under the Commission's geographic rather than volumetric reading of regional content standards. The team has not revisited the review as the contract manufacturing share has continued to grow.
---
## Gameplay Relevance
Makuti Consumer is south reach commercial texture — present in commissary inventories, visible on supply manifests, relevant to investigations involving consumer goods supply chains, procurement fraud, or regional content requirements.
The production gap is the investigative thread. The evidence requires two sources: the company's production records (showing the split between Mwangaza facility output and contract manufacturer volume) and the regulatory filing that supports the "locally produced" claim (in Commission consumer standards records). The gap between the filing's representation and the actual production distribution is not hidden — it is in the company's own records. Whether the institutional buyers who specified regional content requirements received goods meeting those requirements depends on how the contract language defines "locally produced" and whether it tracks Commission standards or imposes stricter criteria.
---
**Cross-References:**
- [Mwangaza](../star-systems/GJ-693/index.md) — Headquarters system; primary facility; institutional client base
- [Mwanga Media](mwanga-media.md) — Mwangaza system neighbor; cultural context
- [Iberian Standard Foods](iberian-standard-foods.md) — South reach consumer goods parallel; comparable regulatory positioning
- [Kalahari Leatherworks](kalahari-leatherworks.md) — South reach origin certification parallel
---
**Status:** Canonical
**Created:** 2026-04-19
**Updated:** 2026-04-22

Some files were not shown because too many files have changed in this diff Show More