Bella Tenebrix

Immediate Identity

Core identifiers and role definition

• Name: Bella Tenebrix

• Aliases / Callsigns: “Archivist”

• One-Line Summary: Czerka verification operative validating liability and authorizing escalation under audit-controlled thresholds in unstable recovery zones

• Species: Human

• Age: 32

Timeline Placement

Chronological position within SWTOR continuity

• Era Placement: 3621 BBY

• Continuity Anchor: Active Czerka verification operative operating under audit-controlled escalation authority and real-time telemetry integration

Affiliation & Alignment

Political classification and institutional context

• Allegiance Classification: Corporate & Underworld

• Primary Institutional Affiliation: Czerka Interstellar — Recovery Operations Division

• Affiliation Visibility Status: Compartmentalized

Operational Snapshot

At-a-glance present-state reference (non-narrative)

• Status Designation: Active

• Primary Function: Performs liability validation, asset classification, and escalation authorization for recovery operations under audit oversight

• Operational Scale Category: Small-Team

• Primary Base of Operations: Czerka data-integrated recovery network (mobile deployment vessels across Outer Rim sectors)

• Current Residence: Secured quarters aboard rotating Czerka deployment craft

• Operational Range: Multi-Sector

Background Snapshot

Origin and current identity baseline

• Background Summary: Raised on Zakuul within a centralized civic structure governed by controlled information systems, Bella developed a verification-focused mindset rooted in procedural discipline and measured response. Training within the Knights of Zakuul reinforced restraint, perception, and controlled Force use. Following the Empire’s collapse, she transitioned into Czerka Interstellar, applying structured validation within liability-driven recovery operations across destabilized and data-fractured environments.

Personal Identity

Biographical and cultural context

• Gender / Pronouns: Female (she/her)

• Homeworld: Zakuul

• Cultural Origin: Centralized civic-information culture emphasizing order, verification, and controlled response

• Relationship to Origin Culture: Detached; retains procedural habits without ideological alignment

• Languages: Galactic Basic (fluent); Zakuulan administrative register (fluent)

Interpersonal Presence

How the character is perceived in direct interaction

• Baseline Presence: Still and observant; attention fixed outward with minimal visible reaction

• Social Demeanor: Measured and procedural; responds only after internal assessment

• Notable Mannerisms: Pauses before speaking; maintains still posture during analysis; corrects inaccuracies without escalation

Physical Presentation

Observable appearance and outward presentation

• Height: 5 ft 4 in (163 cm)

• Build & Bearing: Slim; compact; minimal unnecessary movement

• Eye Color: Amber-gold

• Hair: Royal purple; long and secured

• Skin Tone: Light with neutral undertone

• Distinguishing Features: Subtle marking below lower lip; steady, analytical gaze

• Typical Attire: Reinforced archive-recovery gear with integrated scanning systems

• Alternate Presentation: Archived Zakuulan Knight armor (not in active use)

Identity Throughline

Core continuity linking origin to current trajectory

• Identity Throughline: Withholds escalation until outcomes are defensible, even under time-sensitive conditions

Current Status

Present position within the SWTOR timeline

• Current Situation: Actively assigned to multi-sector recovery operations, validating liability conditions and authorizing escalation under continuous audit monitoring

External Conditions

Immediate external conditions affecting activity

• Active Pressures: Liability validation requirements determining escalation authorization; continuous audit review of decision timing and record integrity; degraded or incomplete data in destabilized environments; deniable action windows limiting authorization timing; escalation authority suspension risk if delays result in loss

• Operational Stability: Strained

• Primary Vulnerability: Delayed escalation under ambiguous conditions resulting in preventable loss and audit-triggered authority restriction

Trajectory

Likely direction based on current conditions

• Short-Term Direction: Maintain escalation authority by producing defensible, timely validation decisions

• Long-Term Trajectory: Retained as verification authority if timing stabilizes; downgraded if delays persist

• Open Threads: Escalation timing scrutiny under audit review; dependency on Brina’s early-entry actions for real-time data; pressure to adjust validation thresholds

• Change Pressure: Corporate demand to balance defensible accuracy with operational speed

Timeline Highlights

Major turning points affecting role, status, or trajectory

• 3653 BBY (Age 0) — Civic Conditioning
  Impact: Established procedural discipline and structured perception

• 3645 BBY (Age 8) — Knight Training Intake
  Impact: Reinforced controlled Force use and verification-based response

• 3638 BBY (Age 15) — Active Knight Service
  Impact: Exposure to environments requiring measured, accurate response

• 3630 BBY (Age 23) — Horizon Guard Exposure
  Impact: Reinforced consequences of incomplete or incorrect information

• 3626 BBY (Age 27) — Post-Collapse Displacement
  Impact: Loss of institutional framework; transition to structured survival

• 3621 BBY (Age 32) — Czerka Integration
  Impact: Established verification authority within liability-driven operations

Common Locations

Recurring locations beyond primary base of operations

• Common Locations: Damaged archive facilities; containment zones; data-fractured vaults; contested Outer Rim recovery sites; off-ledger data nodes

Key Relationships

Individuals or groups with direct influence on the character

• Allies & Contacts: Brina Tenebrix — Czerka recovery operative and primary co-assignment partner

• Rivals & Adversaries: Czerka compliance auditors and Recovery Oversight personnel

• Personal Connections: Brina Tenebrix (cousin) — unbreakable familial bond; absolute loyalty supersedes institutional obligation; Trace — female loth-cat companion; controlled emotional anchor and stabilizing presence during recovery cycles

• Affiliated Groups: Czerka recovery teams; limited interaction with unregistered data brokers

Relational Dynamics

Obligations and tensions arising from relationships

• Relational Obligations: Maintains absolute loyalty to Brina; responsible for ensuring actions remain defensible under shared audit exposure

• Relational Tensions: Pressure from field operatives requiring faster authorization; audit scrutiny tied to delayed escalation

Reputation

How the character is perceived externally

• Professional Reputation: Highly precise and reliable; trusted for defensible record integrity but flagged for delayed escalation

• Public / External Perception: Low-profile verification specialist operating in high-risk environments

• Notoriety Level: Obscure

• Reputation Stability: Stable

Engagement Hooks

Entry points for roleplay engagement

• Engagement Hooks: Liability disputes in active recovery zones; escalation authorization conflicts under audit pressure; data integrity investigations in unstable environments

• Engagement Style: Observes, validates, and authorizes or withholds escalation based on defensible evidence

Institutional Role

Formal role and standing within an organization

• Functional Role: Liability validation and escalation authorization

• Rank / Title: Recovery Operative (Verification Specialist)

• Authority Level: Limited

• Jurisdiction: Czerka-controlled recovery operations across Outer Rim sectors

• Institutional Standing: Trusted for accuracy; under scrutiny for escalation timing

Command Structure

Reporting relationships and authority flow

• Reports To: Lorim Vance — Czerka Recovery Oversight Division

• Direct Subordinates / Team: None

• Operational Autonomy: Limited; dependent on validation thresholds and audit tolerance

• Expression of Authority: Indirect; exercised through authorization, delay, or denial

Resources & Access

Material, logistical, and structural support

• Available Resources: Archive recovery kit; advanced scanners; containment tools; restricted double-bladed lightsaber; data-linked systems

• Standard Loadout: Scanning systems; archive tools; containment equipment

• Access Level: Restricted

• Logistical Support: Consistent

• Resource Dependency: Czerka data systems, telemetry streams, authorization networks

• Resource Constraints: Escalation authority limited by validation requirements and audit oversight

Oversight & Control

Monitoring, restriction, and intervention mechanisms

• Oversight Level: High

• Oversight Triggers: Escalation delay beyond acceptable window; data inconsistency or unverifiable records; failure to authorize under sufficient evidence

Strategic Position

Value and risk within the organization

• Strategic Value: Ensures operational decisions remain defensible and liability-compliant

• Institutional Risk: Delayed escalation resulting in preventable loss and increased liability exposure

Information Visibility

Distribution of knowledge within institutional systems

• Public Record: Czerka verification specialist

• Restricted Information: Zakuulan Knight background

• Classified / Hidden Information: Escalation timing records and internal audit evaluations

Motivation & Conflict

Core drivers and internal tension

• Core Motivation & Internal Conflict: Preserve defensible truth while operating within systems requiring rapid escalation

• Dominant Conflict Type: Institutional

Decision Profile

How the character evaluates and commits to action

• Decision Style: Sequential validation (observe → verify → corroborate → assess → authorize)

• Risk Tolerance: Moderate

• Default Decision Bias: Withholds escalation pending sufficient validation

Execution Pattern

How actions are carried out in practice

• Execution Style: Methodical and staged; prioritizes validation before escalation

• Escalation Threshold: Confirmed irreversible loss or containment failure

• Escalation Sequence: Observe → verify → corroborate → assess → authorize or delay

• Operational Strengths: Pattern recognition; procedural consistency; composure

• Non-Competencies: Rapid response under chaotic conditions; improvisation; offensive engagement

Constraints & Failure Conditions

Limits, blind spots, and risk triggers

• Cognitive Blind Spots: Overextends validation under ambiguous conditions

• Behavioral Constraints: Procedural fixation; hesitation when confirmation is incomplete

• Authority / Ethical Limits: Will not falsify records or manipulate data, even under direct pressure

• Critical Failure Condition: Preventable irreversible loss caused by delayed escalation

• Behavioral Risk Indicators: Repeated validation loops; delayed authorization decisions; reliance on incomplete data

Stress Response

Behavior under pressure and recovery patterns

• Stress Response: Increased focus; reduced communication; deeper procedural fixation

• Conflict Posture: Controlled and non-reactive

• Recovery Pattern: Returns to structured environments; stabilizes through ordered systems, often involving presence of Trace

Force Status

Baseline sensitivity and training background

• Force Sensitivity Level: Low-to-Moderate

• Force Training Background: Knights of Zakuul

Alignment & Philosophy

Belief system and orientation within the Force

• Alignment Orientation: Non-Aligned

• Force Philosophy: Used to clarify instability and maintain controlled perception

Discipline & Application

How the Force is used in practice

• Primary Disciplines: Perception; detection; containment awareness

• Application Style: Subtle; proximity-based; observation-enhancing

• Signature Expression: Detection of inconsistencies and instability within immediate surroundings

Force Presence

Perception by other Force-sensitive individuals

• Force Presence: Muted and restrained

• Visibility Level: Subtle

• Presence Control: Maintained suppression

Limitations & Stability

Constraints and consistency of Force use

• Force Limitations: Limited offensive capability; reduced effectiveness under time pressure

• Stability Level: Stable

• Known Restrictions: Degradation in performance when forced to act without sufficient validation

Player Information

Basic contact and identification

• Player Name / Handle: Bella Tenebrix (Empire); Bella Tenebrixx (Republic)

• Preferred Contact Method: In-game messaging

Availability

General activity patterns

• Activity Level: Occasional

• Time Zone & Availability: Eastern Time (UTC-5), evenings and weekends

Roleplay Preferences

Style, tone, and engagement expectations

• Preferred RP Style: Paragraph-based, structured

• Preferred Themes & Interests: Institutional conflict; data integrity vs control; consequence-driven narrative

• Engagement Preference: Collaborative with optional planning

Boundaries

Content limits and communication expectations

• Content Boundaries: No explicit sexual content; no gratuitous violence

• Consent & Communication: Prior discussion for major developments; fade-to-black; open check-ins