Files

T

jpmschweitzerandClaude Opus 4.6 b672b9c269 feat(docs): restructure wiki taxonomy with templates and Krenn System entry (#301 , #319 )

Move wiki from docs/wiki/ to root wiki/. Add 14 category templates with
YAML frontmatter, governance model, hierarchical spatial structure
(system > station > district > location). Populate Krenn System entry
as first concrete star system. Update cross-references in workshop and
sprint docs.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-13 00:58:45 +01:00

7.9 KiB

Raw Blame History

title, slug, canonical_id, category, status, created, updated, tier, pattern, motivation, social_sites, entanglement, triangles, home_district, tags, decision_refs, cross_refs

title

slug

canonical_id

Resha Neven

Tier 2 NPC | Logistics Hub (The Terminal) | Mundane

Core Identity

Name: Resha Neven Age: 23 Role: Dock worker (new hire, 3 months), Sova Transit District Logistics Hub System Origin: Krenn System, Residential Radial B (Station Sova — short-term housing district) Lattice Tier: Baseline Employer: Sova Logistics Consortium

10-Axis Profile

1. Want

Primary: Do the job well and prove herself.

Resha is 3 months into her first permanent position at the hub. She came from short-term contract work in other districts — unstable, underpaid, no community. This job matters. She wants to be competent, reliable, valued. She studies the shift protocols, asks questions about procedures, and takes notes.

Secondary: Understand why things don't make sense.

Resha asks questions because she's learning. Some of those questions — about locked bays, irregular schedule changes, containers that appear on manifests but aren't in the bay — are innocently dangerous. She doesn't know she's asking about the ring's operations. She's asking because the procedures she was taught don't match what she observes.

2. Secret / Vulnerability

Surface secret: None. Resha is transparent — she's new, eager, and has nothing to hide.

Deep secret: None. Resha's significance isn't what she's hiding — it's what she's noticing.

Vulnerability: Naivety. Resha doesn't understand the social dynamics well enough to know which questions are dangerous. Her curiosity makes her a risk to the ring and a potential asset to the detective — neither of which she's aware of.

3. Relationships

Voss: Shift supervisor. Resha respects authority and tries to please Voss. Voss is professionally competent with Resha but wants her to stop asking about irregularities.

Kael Davan: Senior colleague. Kael is patient with Resha — shows her the ropes, answers procedural questions, covers for her mistakes. Resha looks up to Kael. This makes Kael protective, which complicates Kael's position.

Maret Korr: Freight scheduler. Maret gives Resha scheduling data and is protective in a quiet, professional way. Resha's questions about manifest discrepancies echo Maret's own concerns.

4. Tolerance Threshold

Low. Resha hasn't been tested yet. She's never been in a situation where loyalty conflicts with safety. If directly threatened or warned to stop asking questions, Resha would be scared and confused. She doesn't have the experience to navigate institutional pressure.

5. Daily Routine

06:00 - 14:00: Day shift — cargo handling, bay allocation assistance, learning procedures 10:30 - 11:00: Break room, often with Kael or other dock workers 14:00 - 15:00: Post-shift, sometimes stays late studying shift protocols 15:00+: Home (Residential Radial B) or occasionally bar (not a regular — Resha is still establishing social connections)

6. Information Inventory

Knows: Basic hub operations (3 months of learning), shift procedures, which bays handle what cargo, Voss's authority, Kael's reliability. Observations: locked bays that don't appear on her manifest, schedule changes posted after the fact, containers with routing codes she wasn't trained on.

Doesn't know: Ring, smuggling, the significance of her observations, Kael's secret life, Voss's compromise, anything about the bar social dynamics.

7. Contentment

Moderate-high. Resha is happy to have a stable job. The community is welcoming enough. The work is hard but meaningful. Her contentment is that of someone at the beginning of something — optimistic, not yet disillusioned.

8. Personality Traits

Primary: Curious — asks questions, observes, wants to understand systems. Secondary: Earnest — genuine effort, no cynicism, takes the work seriously. Tertiary: Observant — notices details because she's learning, not because she's suspicious.

9. Tell System

Tell	Trigger	Observable To
Asks questions about locked bays	Encounters a procedure she wasn't trained for	Voss (nervous), Kael (protective), Smuggler (if at hub)
Takes notes on her lattice	Recording procedures, schedules, observations — standard for a new hire, but the data she's capturing includes anomalies	Maret (recognizes the pattern), Detective (if accessing Resha's notes)
Looks to Kael for guidance	Uncertain about a procedure or social situation	Everyone at the hub

10. Skill Set

Occupational: Cargo handling (learning), bay allocation (basic), manifest reading (training level). Combat tag: No. Lattice capability: Baseline.

Voice Sample

Mood: Eager (baseline)

"The Bay 7 manifest doesn't list that container. Should I flag it, or is that a late addition? I just want to make sure I'm processing it right."

Mood: Confused (observing irregularity)

"Voss changed the afternoon rotation again. Is that normal? I thought the schedule was set at shift start."

Dual-Lens Notes

Smuggler: Resha is a variable. Her questions are innocent but dangerous. The smuggler reads Resha as someone who needs to be managed — either brought into confidence (risky) or steered away from sensitive areas (ongoing effort). "Resha's asking about Bay 7 again. Someone needs to teach her that not every question needs an answer."

Detective: Resha is a fresh pair of eyes. Uncompromised, observant, and unaware of the social pressures that keep everyone else silent. If the detective talks to Resha early, her observations become data. If the detective talks to Resha late, Resha may have been warned to stop asking questions — and THAT is also data. "New hire. Three months. Still asking questions the veterans stopped asking years ago. Either naive or useful. Possibly both."

Triangle Roles

Not a formal triangle member. Resha's function is atmospheric and catalytic — her questions create pressure on Voss and Kael, her observations could feed into the detective's investigation, and her presence reminds the hub workers that the operation is only invisible to people who've learned not to look.

Pattern / Motivation

Pattern (System A): CATALYST — Resha's innocent questions about locked bays, irregular schedules, and unmanifested containers force the ring's infrastructure into defensive reactions. Every question she asks creates pressure on Voss and Kael. She is a disruption vector — not by intent, but by the simple act of trying to learn her job. Motivation (System B): CIVILIAN — Resha is not investigating, not scheming, not cooperating with anyone. She is a new hire trying to understand procedures. Her questions are genuine, not strategic. The CIVILIAN motivation means the disruption is accidental — born of earnestness, not suspicion.

Composition read: CATALYST + CIVILIAN creates innocent disruption: "She just asked. Everyone flinched." Resha disrupts (CATALYST) through pure curiosity (CIVILIAN), which makes her impossible to manage through normal channels. You cannot tell a new hire to stop asking procedural questions without explaining why — and the explanation is the thing that must stay hidden. The system is so compromised that learning it honestly is itself a threat. For the smuggler, Resha is a variable that requires constant steering. For the detective, Resha is a fresh pair of eyes whose observations carry no political filtering — whatever Resha noticed, she noticed because it was genuinely anomalous.

Cross-References: Voss, Kael Davan, Maret Korr

7.9 KiB Raw Blame History