jpmschweitzerandClaude Sonnet 4.6
6b1c5e4d29
Character schema and builds: - #179: Character definition schema (6-section formal spec) - #180: Smuggler character build (full schema instantiation) - #181: Detective character build (full schema instantiation) - #182: Divergent starting knowledge (master comparison table) - #183: Divergent relationships (NPC web per character) Institutional design: - #322: Detective chain of command (Veth, Pres, Tsev backstory) NPC pattern documents: - #332: Contradiction arc — reusable FRIEND pattern (5 phases, checklist) - #329: Mirror moment design — 10 paired dual-lens observations Experience design: - #259: First 5 minutes (narrative texture additions to Gestalt's systems doc) - #307: Flat NPC trait pass (Pael, Ren, Tev — traits, routines, dual-lens) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
13 KiB
Detective: Institutional Chain of Command
Ticket: #322 | Priority: High | Sprint: 12 Status: v0.1 Draft Owners: Paula (narrative arc), Miri (setting/institutional context) Decisions referenced: D-005, D-027, D-037, D-041
1. Purpose
The detective is not a freelance investigator. They are a Commission officer, which means someone assigned them here, someone defined their mandate, someone is waiting for reports, and someone may have an interest in how this investigation concludes — not all of them aligned.
The institutional chain of command is not just background. It determines:
- What the detective is officially permitted to do (arrest authority, warrant scope, search powers)
- What they're NOT supposed to do (exceed mandate, go outside channels, use extra-institutional leverage)
- Who benefits if the investigation succeeds — and who doesn't
- The political weight of the previous liaison's rotation — which may not have been routine
This document establishes the detective's institutional world. It does not need to be fully visible to the player in v0.1 — it lives in the detective's case file, in their monologue, in what institutional NPCs say when authority-tier access opens. But it must be consistent.
2. The Commission — Brief Institutional Context
The Commission (Intersolar Commission) is the primary regulatory body governing freight transit, customs enforcement, and neural lattice certification across the Settled Reach. It is not a police force. It operates through:
- Compliance review — routine audits of freight hubs, manifest reconciliation
- Liaison officers — semi-permanent postings to transit hubs; advisory and investigative authority
- Field technicians — technical support, equipment maintenance, passive monitoring (Sera Venn's role)
- Enforcement officers — arrest authority; called in from sector headquarters for formal investigations
The detective's posting as "Commission Liaison Officer" sits between compliance and enforcement. They have investigative authority — enough to request manifests, interview persons of interest, and flag suspects — but formal arrest and search warrant authority requires escalation to sector headquarters.
This matters for the detective's v0.1 situation: They can investigate. They cannot arrest without authorization from above. If they find evidence of a smuggling ring, they need to report it up the chain before taking action — and that creates a window of political exposure.
3. The Formal Chain
Level 1: The Detective (On-Station)
Title: Commission Liaison Officer, Sova Transit District Mandate (official): Routine compliance review — manifest reconciliation, scheduling compliance, standard freight hub audit. Mandate (actual): Investigate manifest irregularities suggesting organized smuggling. Identify structure, membership, and supply chain. Report to Sector Oversight with arrest recommendations. Reporting to: Sector Liaison Coordinator, Commission Sector 7 Headquarters (off-station, a span-gate transit away)
Level 2: Sector Liaison Coordinator — Renna Veth
Title: Liaison Coordinator, Commission Sector 7 Who she is: Career Commission officer. Mid-level administrator with 20 years of routine compliance work and two serious investigations to her name. Professional, risk-averse. Not corrupt — but also not courageous. Wants the investigation to produce results without embarrassing the Commission or producing a political fight she didn't expect. Her interest in this investigation: Wants it resolved cleanly. A successful arrest closes a compliance gap in her sector metrics. A failed investigation — especially one that implicates a Commission insider — would be a problem. Relationship with detective: Assigned the detective to Sova because the detective has a clean record and a reputation for methodical work. Does not know the detective personally.
Level 3: Sector Deputy Commissioner — Halden Pres
Title: Deputy Commissioner, Sector 7 Who he is: Political appointee. Has been in position for 6 years. Sector 7 covers the Krenn System transit hubs, which are economically significant — freight logistics for Velen's surface operations. Not personally corrupt. But his political relationships include figures who have interests in how freight regulation is managed in the sector. His knowledge of this investigation: Was briefed at level of "routine compliance review at Sova." Does not know the actual investigative mandate. If the investigation escalates — if arrests are made, if Commission involvement in a smuggling ring is implied — he will be briefed, and his political relationships will activate. The political risk: Deputy Commissioner Pres is not an enemy. But if the investigation implies that a previous Commission liaison was arranged to protect a smuggling ring, Pres may have indirect connections to whoever arranged it. He is not the villain. But he is a constraint.
4. The Previous Liaison: Korrean Tsev
Title (former): Commission Liaison Officer, Sova Transit District Rotation: Posted to Sova for 18 months; rotated out 3 months before the detective arrived. Official reason for rotation: Standard posting cycle. Liaison officers rotate every 18-24 months to prevent over-familiarity with local operations.
The detective's case file note: The previous liaison, Korrean Tsev, was in position during the period when manifest discrepancies were already detectable in the freight data. No irregularity reports were filed. Three compliance audits during Tsev's tenure all came back clean. The anomalies that the detective's pattern analysis flagged from the data should have been visible to Tsev.
Was the rotation arranged?
The detective's case file flags this as unconfirmed but suspicious. The canonical answer (not available to the player in v0.1): yes, it was arranged. Tsev was not corrupt in the sense of taking ring money — but Tsev was compromised by personal loyalty. A relationship with someone at sector administration meant Tsev was quietly moved when the manifest anomalies became too persistent to ignore, rather than being required to file a report that would implicate people above Tsev's pay grade.
What the detective can learn in v0.1:
- That Tsev filed no reports (case file, accessible from session start)
- That the anomalies were detectable during Tsev's tenure (manifest data analysis, takes investigation time)
- That Tsev was rotated on a compressed timeline (standard was 24 months; actual was 18 months) — this is discoverable through institutional records if the detective requests them
What the detective cannot learn in v0.1:
- WHY the rotation was arranged
- Who in sector administration was involved
- Whether Deputy Commissioner Pres had knowledge
This is a thread that extends beyond the v0.1 vertical slice. The detective can pull the thread enough to see it exists, but not enough to unravel what's at the other end.
5. Torek Lintar: Commission Compliance Officer
Torek Lintar is Commission compliance on Sova — not an investigator, not a liaison officer, but a permanent-fixture compliance monitoring role. Commission compliance officers are lower in the formal hierarchy than liaison officers, but they have one thing liaison officers don't: local knowledge accumulated over years.
Torek has been on Sova for 4 years. He knows everyone. He knows the bar. He knows the shifts. He knows the social fabric in a way a three-day-old liaison officer cannot.
The detective's starting relationship with Torek: Professional known name from institutional channels. Not a friend. Encountered at the bar (Torek is a bar regular).
What Torek knows that the detective doesn't:
- The ring's social footprint, at least at the edges — conspicuous spending, familiar faces
- Sera Venn's unofficial compliance check (Torek suspects; he doesn't know for certain)
- The shape of the social web connecting Kael's group
Why Torek hasn't reported what he knows: Torek's tolerance threshold for confrontation is low. He is ring-adjacent (D-024 triangle 3: Bar Tensions), which means he is socially embedded with people who are embedded with the ring. His conspicuous spending suggests he may have accepted something from ring-peripheral sources — not enough to be a member, but enough to compromise his ability to report cleanly. He is not a villain. He is a compromised observer who has talked himself into believing the right moment to report will come later.
Torek as asset for the detective: If the detective builds enough trust (social + authority), Torek can become an information source — but carefully. The ring is aware of Torek's connection to Commission compliance. Torek going to the detective too visibly risks blowback on both of them.
Torek as the signal in Sera's FRIEND arc: Sera avoids Torek. Three times. Three different excuses. The detective's monologue reads this as a behavioral pattern. The reason: Sera ran an unofficial check on Kael's work patterns (using Commission technical access she wasn't supposed to use) and found the same manifest discrepancies the detective found. Torek, as Commission compliance, would be the person Sera should have reported this to. Sera's avoidance of Torek is the tell that she found something and didn't report it. The detective doesn't know this yet — but the behavioral signal points there.
6. Political Pressures on the Investigation
The detective's investigation operates under several simultaneous pressures:
| Pressure | Source | Direction | Effect |
|---|---|---|---|
| Succeed cleanly | Veth (Sector Coordinator) | Upward | Produce results without creating institutional embarrassment |
| Don't exceed mandate | Institutional | Inward | Formal arrests require escalation; the detective can't act unilaterally |
| Previous liaison question | Case file | Lateral | Pulling this thread risks finding Commission involvement; politically dangerous |
| Sera's position | Personal | Personal | Using what Sera knows against her would destroy the detective's only personal relationship in the district |
| Community non-cooperation | Social | Environmental | The district's default resistance to institutional authority; this is not malice, it's culture |
The detective is not just investigating a smuggling ring. They are investigating within an institutional structure that has already failed to catch this ring once. The question of whether that failure was incompetence or arrangement is the shadow behind every manifest discrepancy.
7. How This Appears in Monologue
The detective's institutional context should surface in monologue lines as internal processing — the analytical framing through which they filter every observation. Not institutional jargon, but institutional habit.
Examples:
At session start, observing the hub: "Third day. Tsev was here for eighteen months and filed nothing. Either I'm better at this than Tsev, or there's something in the water. Let's find out."
When Voss deflects a question: "That answer was technically responsive. It gave me nothing. Voss knows exactly what I'm asking. Note it."
When considering what Torek knows: "Lintar's been on Sova for four years. He's seen whatever there is to see. Commission compliance doesn't file reports in a vacuum — something told him to stay quiet."
When the Sera contradiction emerges: "I could escalate this. Report what I suspect to Veth. But if I'm wrong about Sera, I've just burned my only ally on a hunch. And if I'm right — I need to know how far this goes before I put it in writing."
8. v0.1 Content Scope
What needs to be authored for this to work:
| Element | Content Requirement |
|---|---|
| Detective opening monologue (lines about Tsev's missing reports) | 1-2 lines from session start knowledge |
| Case file items (accessible via evidence display) | 3-5 readable entries: Tsev rotation note, manifest cluster data, POI summaries |
| Torek dialogue (authority tier) | 3-5 lines for institutional context questions |
| Veth (off-station, not interactive) | Referenced in case file and detective monologue only |
| Detective monologue about political constraints | 2-3 lines scattered across session |
The chain of command does not require NPCs to appear — Veth and Pres are off-station and non-interactive in v0.1. Their presence is felt through the detective's case file entries and internal monologue about institutional constraints. Torek is the only chain-of-command-adjacent NPC who is interactive.
Ticket #322 — Detective institutional chain of command. v0.1 scope.