Bella Tenebrix

Immediate Identity

Core identifiers and role definition

• Name: Bella Tenebrix

• Aliases / Callsigns: “The Archivist”

• One-Line Summary: Compliance-monitored recovery specialist stabilizing and verifying compromised archival systems under restricted escalation authority

• Species: Human

• Age: 32

Timeline Placement

Chronological position within SWTOR continuity

• Era Placement: 3621 BBY

• Continuity Anchor: Post–Eternal Empire collapse; active in Czerka Interstellar recovery operations under compliance supervision with enforced audits and restricted independent action

Affiliation & Alignment

Political classification and institutional context

• Allegiance Classification: Corporate

• Primary Institutional Affiliation: Czerka Interstellar (Recovery Operations)

• Affiliation Visibility Status: Public (current affiliation); compartmentalized (prior affiliations)

Operational Snapshot

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

• Status Designation: Active

• Primary Function: Stabilizes, contains, and verifies compromised archives and hazardous data environments under compliance-approved thresholds

• Operational Scale Category: Small-Team

• Primary Base of Operations: Mobile, assignment-based deployment

• Current Residence: Mobile; Czerka transport and temporary secured facilities

• Operational Range: Multi-sector

Background Snapshot

Origin and current identity baseline

• Background Summary: Raised on Zakuul within a tightly regulated civic-military structure emphasizing obedience and systemic order; conditioning reinforced procedural discipline and a verification-centered identity baseline

Personal Identity

Biographical and cultural context

• Gender / Pronouns: Female (she/her)

• Homeworld: Zakuul

• Cultural Origin: Zakuulan civic-military governance under Valkorion’s reign

• Relationship to Origin Culture: Detached

• Languages: Galactic Basic (fluent); Zakuulan administrative register (fluent); Sith lexicon recognition (limited)

Interpersonal Presence

How the character is perceived in direct interaction

• Baseline Presence: Reserved; controlled; observant; minimally expressive

• Social Demeanor: Procedural; composed; concise; defaults to structured response patterns when engaged

• Notable Mannerisms: Silence under stress; narrowed attention; procedural fixation; delayed verbal response during active verification cycles

Physical Presentation

Observable appearance and outward presentation

• Height: 5 ft 4 in (163 cm)

• Build & Bearing: Slim; compact; minimal movement

• Eye Color: Amber-gold

• Hair: Royal purple; long; secured

• Skin Tone: Light, neutral undertone

• Distinguishing Features: Subtle marking below lower lip

• Typical Attire: Lightweight reinforced field attire for hazardous recovery environments

• Alternate Presentation: Zakuulan Knight armor (prior service)

Identity Throughline

Core continuity linking origin to current trajectory

• Identity Throughline: Maintains stability through verification-driven function within structured systems

Current Status

Present position within the SWTOR timeline

• Current Situation: Conducting archive stabilization, containment, and data verification for Czerka under compliance supervision by Lorim Vance, with mandatory audits, escalation authorization checks, and recorded equipment usage

External Conditions

Immediate external conditions affecting activity

• Active Pressures: Corporate liability constraints; compliance oversight enforced by Lorim Vance; accelerated timelines with penalties for delay or deviation, including reassignment to lower-priority recovery zones

• Operational Stability: Strained

• Primary Vulnerability: Delayed escalation in time-sensitive conditions triggering compliance scrutiny, formal incident reports, and potential reassignment or suspension

Trajectory

Likely direction based on current conditions

• Short-Term Direction: Continue assignment-based stabilization, containment, and verification under compliance monitoring with enforced escalation thresholds

• Long-Term Trajectory: Continued monitored deployment with pressure to adjust escalation thresholds or risk restriction to non-critical assignments

• Open Threads: Conflict over record suppression directives; consequences of delayed intervention resulting in reprimands and formal compliance citations

• Change Pressure: Orders requiring destruction, suppression, or falsification of records; non-compliance risks removal from field duty, detention under corporate security, or asset seizure

Timeline Highlights

Major turning points affecting role, status, or trajectory

• 3653 BBY (Age 0) — Zakuulan civic conditioning
  Impact: Established obedience and procedural discipline

• 3645 BBY (Age 8) — Entry into Knight training pipeline
  Impact: Reinforced verification-focused behavior and obedience

• 3638 BBY (Age 15) — Transition to active Knight service
  Impact: Early deployment under accelerated training; normalized containment priorities and civilian expendability

• 3630 BBY (Age 23) — Horizon Guard selection
  Impact: Selected into Vaylin’s guard under high-attrition command; exposure created internal conflict between obedience and evacuation prioritization

• 3626 BBY (Age 27) — Post-Empire displacement
  Impact: Loss of institutional protection; transition to survival-based work with limited resources

• 3621 BBY (Age 32) — Czerka recovery integration
  Impact: Established role in archive stabilization and verification under compliance oversight

Common Locations

Recurring locations beyond primary base of operations

• Common Locations: Unstable recovery sites; contested facilities; damaged vaults; containment perimeters

Key Relationships

Individuals or groups with direct influence on the character

• Allies & Contacts: Brina Tenebrix (cousin; recovery operative and frequent mission partner; former Knight and Horizon Guard)

• Rivals & Adversaries: Czerka compliance officers and supervisory chain, particularly Lorim Vance’s audit staff responsible for escalation review and incident attribution

• Personal Connections: Sira Tenebrix (mother; civilian systems analyst); Kael Tenebrix (father; alleged Sith-aligned auxiliary, unverified); Trace (female loth-cat companion, registered non-essential asset); Brina Tenebrix (cousin; maintains separate loth-cat companion)

• Affiliated Groups: Czerka recovery teams

Relational Dynamics

Obligations and tensions arising from relationships

• Relational Obligations: Familial ties; coordination with recovery personnel under assignment directives

• Relational Tensions: Conflict with compliance expectations; divergence from intervention-focused counterparts; friction with personnel prioritizing rapid escalation over verification

Reputation

How the character is perceived externally

• Professional Reputation: Reliable and precise; slow to escalate; trusted for accuracy but formally flagged in compliance records for delayed escalation

• Public / External Perception: Low-profile Czerka recovery specialist

• Notoriety Level: Obscure

• Reputation Stability: Stable but conditionally maintained pending compliance review outcomes

Engagement Hooks

Entry points for roleplay engagement

• Engagement Hooks: Archive recovery assignments; containment operations; unstable facility investigations; data disputes

• Engagement Style: Investigative; reactive; assignment-driven

Institutional Role

Formal role and standing within an organization

• Functional Role: Archive stabilization, containment, and data verification

• Rank / Title: Recovery Operative

• Authority Level: Limited

• Jurisdiction: Assignment-scoped

• Institutional Standing: Trusted for documentation accuracy; monitored for delayed escalation; retained for audit reliability despite escalation deficiencies

Command Structure

Reporting relationships and authority flow

• Reports To: Lorim Vance (Czerka compliance officer)

• Direct Subordinates / Team: None

• Operational Autonomy: Limited to assignment parameters with enforced compliance checkpoints and escalation authorization requirements

• Expression of Authority: Advisory; exercised through verified data rather than directive control

Resources & Access

Material, logistical, and structural support

• Available Resources: Archive recovery kit; scanners; containment tools; restricted double-bladed lightsaber (usage logged and reviewed); assignment shuttle; assignment-scoped archive access

• Standard Loadout: Archive recovery kit; scanners; containment tools; restricted double-bladed lightsaber

• Access Level: Restricted

• Logistical Support: Consistent

• Resource Dependency: Czerka authorization systems and deployment logistics

• Resource Constraints: Assignment-based authorization; limited access per deployment; dependent on Czerka approval with revocation risk including immediate suspension upon compliance violation

Oversight & Control

Monitoring, restriction, and intervention mechanisms

• Oversight Level: Monitored

• Oversight Triggers: Authorization delays; procedural deviation; asset loss resulting in audit, reassignment, or assignment suspension by compliance authority

Strategic Position

Value and risk within the organization

• Strategic Value: High documentation fidelity and containment accuracy

• Institutional Risk: Escalation delay in rapidly deteriorating scenarios

Information Visibility

Distribution of knowledge within institutional systems

• Public Record: Czerka Interstellar recovery operative assigned to post-incident archive and containment sites

• Restricted Information: Prior Horizon Guard service; prior Knights of Zakuul affiliation; family background includes father rumored to be Sith-aligned and connected to Valkorion

• Classified / Hidden Information: Internal compliance reports and escalation timing assessments

Motivation & Conflict

Core drivers and internal tension

• Core Motivation & Internal Conflict: Preservation of verifiable truth versus risk that delayed escalation enables preventable harm

• Dominant Conflict Type: Internal

Decision Profile

How the character evaluates and commits to action

• Decision Style: Sequential verification-driven processing through ordered observation, corroboration, and threshold validation before commitment

• Risk Tolerance: Moderate

• Default Decision Bias: Maintain verification sequence unless clear indicators of irreversible loss or containment breach override process

Execution Pattern

How actions are carried out in practice

• Execution Style: Methodical and staged; prioritizes containment stabilization followed by layered verification before action

• Escalation Threshold: Confirmed irreversible loss, verified containment compromise, or immediate breach indicators that invalidate continued verification

• Escalation Sequence: Observe → verify → cross-reference → assess → intervene → reassess compliance exposure

• Operational Strengths: Pattern recognition; procedural consistency; composure; documentation accuracy

• Non-Competencies: Limited rapid-response adaptability in high-chaos environments; minimal proficiency in aggressive or offensive engagement

Constraints & Failure Conditions

Limits, blind spots, and risk triggers

• Cognitive Blind Spots: Overextension of verification loops under ambiguous conditions, delaying response in rapidly shifting scenarios

• Behavioral Constraints: Procedural fixation; hesitation under unclear escalation criteria; reduced adaptability when conditions change faster than verification can confirm

• Authority / Ethical Limits: Avoids coercion, domination, and sustained manipulation

• Critical Failure Condition: Preventable irreversible loss or enforced suppression of verifiable truth resulting in removal from field operations, detention under Czerka security authority, or permanent reassignment to non-field archival processing

• Behavioral Risk Indicators: Prolonged verification cycles; delayed escalation authorization requests; narrowed situational awareness under stress

Stress Response

Behavior under pressure and recovery patterns

• Stress Response: Progressive narrowing of focus with increased reliance on procedural sequencing; communication decreases as internal processing intensifies

• Conflict Posture: Controlled and non-reactive; resists impulsive escalation while maintaining internal decision structure

• Recovery Pattern: Withdrawal into structured tasks; re-establishes procedural clarity before re-engagement

Force Status

Baseline sensitivity and training background

• Force Sensitivity Level: Low-to-moderate

• Force Training Background: Formal Knights of Zakuul doctrinal training

Alignment & Philosophy

Belief system and orientation within the Force

• Alignment Orientation: Non-aligned

• Force Philosophy: Pragmatic restraint prioritizing perception, stability, and minimal disruption

Discipline & Application

How the Force is used in practice

• Primary Disciplines: Perception; defense; containment

• Application Style: Subtle; controlled; proximity-bound

• Signature Expression: Short-range Force perception used to detect instability and maintain defensive awareness

Force Presence

Perception by other Force-sensitive individuals

• Force Presence: Muted; restrained

• Visibility Level: Subtle

• Presence Control: Trained suppression maintaining low detectability

Limitations & Stability

Constraints and consistency of Force use

• Force Limitations: Limited offensive capacity; proximity-bound effectiveness; fatigue under sustained exertion

• Stability Level: Stable

• Known Restrictions: Emotional fatigue under sustained moral compromise

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 third-person; short-form for transitions

• Preferred Themes & Interests: Institutional pressure; moral ambiguity; character-driven conflict

• Engagement Preference: Collaborative; light pre-planning optional

Boundaries

Content limits and communication expectations

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

• Consent & Communication: Prior discussion for lethal outcomes, coercive Force use, memory alteration, or permanent changes; fade-to-black; open check-ins