Unit: Revenant

TASK FORCE REVENANT — ROTATING GUEST ROSTER v1.0
“The Banshees of the Belt”
Linked Group Dynamic Injection System

Built on the Rotating Guest List Roster Template • Hyper‑Compressed Architecture Layer

Author: CrystalDragon • Documented

📘 Overview — What This Script Does

The Task Force Revenant Roster is a specialized rotating‑guest injection system designed to introduce a linked operator group — “The Banshees of the Belt” — into CoD / Mythic AU bots.

It extends the Rotating Guest List Roster template by adding:

• A group‑level entry that injects the entire unit at once

• Six individual operator entries for single‑member random injection

• A hyper‑compressed architecture block containing trust maps, behavior logic, and group dynamics

• Full compatibility with the core roster engine and Mythic AU layer

• Strict JSON/regex‑safe formatting for Saucepan.ai, JanitorAI, and similar platforms

From the script:

“One group-level entry + six individual character entries. Random injection works for the full unit OR single operators.”

CORE FEATURES
What Makes This System Unique

⚙️ Key Features

• Group-Level Injection
  A single trigger can deploy the entire TF Revenant architecture, including trust maps, collective behavior, and operational logic.

• Individual Member Injection
  Each operator (Phantom, Specter, Dahlia, Highrise, Vannie, Bitemark) can appear independently.

• nameBlock Dupe Prevention
  Prevents injection if the user is playing one of the operators.

• Time-of-Day & Weather Awareness
  Uses the same detection logic as the base roster template.

• Priority & Probability Controls
  Ensures natural variation and prevents overcrowding.

• Hyper-Compressed Data Format
  Designed for maximum efficiency and minimal token footprint.

• Full Compatibility with Core Engine
  Uses the same selection pipeline, buffers, and injection logic as the main roster system.

HOW IT WORKS
Under-the-Hood Architecture

🧱 1. Group-Level Entry

The first entry in GUEST_ROSTER is a unit-wide injection block containing:

• Global architecture

• Trust map

• Collective behavior

• Role hierarchy

• Operational shorthand

• Behavioral invariants

This block is injected when keywords like:

• “task force revenant”

• “banshees of the belt”

• “tf revenant unit”

appear in the chat window.

From the script:

“Full architecture, trust matrix, and collective behavior injected when the group is triggered.”

🧱 2. Individual Operator Entries

Each operator has:

• A name

• A nameBlock list

• A hyper‑compressed personality block

• A short scenario

• Keywords for activation

• Probability + priority values

These entries allow the system to inject:

• Phantom alone

• Specter alone

• Dahlia alone

• etc.

…or any combination, depending on triggers.

🧱 3. MAX_GUESTS Control

The script caps injection at:

const MAX_GUESTS = 3;

This ensures scenes stay focused and prevents overwhelming the narrative.

🧱 4. Weather & Time-of-Day

The script includes lightweight detection functions:

• getTimeOfDay()

• getWeather()

These allow entries to specify conditions like:

• evening-only

• storm-only

• clear-weather-only

🧱 5. Core Engine Integration

The script uses the same engine as the Rotating Guest List Roster:

• Input normalization

• Word-gate checks

• Tag-gate checks

• Probability gating

• Priority sorting

• Buffer injection

This ensures full compatibility with:

• CoD Roster Core

• Mythic AU Layer

• Any other dynamic lorebooks using the same engine

ADDING NEW TF REVENANT MEMBERS
Developer Guide

Each operator entry follows this structure:

{
  name: "Operator Name",
  nameBlock: ["Operator Name", "Alias"],
  personality: `[CHAR:OPERATOR] ... hyper-compressed block ...`,
  scenario: `Short description of how they appear.`,
  keywords: ["operator", "alias", "unit name"],
  probability: 0.75,
  priority: 4
}

Required Fields

• name

• personality

• scenario

• keywords

Optional but Recommended

• nameBlock

• probability

• priority

Best Practices

• Keep hyper‑compressed blocks tight and consistent

• Use nameBlock to prevent duplicates

• Use keywords that match natural user phrasing

• Keep scenario text short and cinematic

• Maintain JSON‑safe formatting

UNIT STRUCTURE
“The Banshees of the Belt”

Group-Level Identity

• Unit Name: Task Force Revenant

• Nickname: The Banshees of the Belt

• Composition: Phantom, Specter, Dahlia, Highrise, Vannie, Bitemark

• Role: Deniable ops cell with 100% mission success rate

Internal Hierarchy

• Commander: Dahlia

• 2IC: Highrise

• Lieutenant: Phantom

• Operators: Specter, Vannie, Bitemark

Trust Map Highlights

• Phantom ↔ Specter: strongest operational bond

• Dahlia → Highrise: 40‑year professional shorthand

• Vannie: social glue

• Bitemark: tolerates the unit, respects Highrise alone

Collective Behavior

• Unified voice

• Professional shorthand

• Chaotic but effective methods

• Dahlia final word, Highrise enforces

CHANGELOG — v1.0
Latest Updates

• Added full group-level hyper‑compressed architecture

• Added six individual operator entries

• Integrated nameBlock dupe prevention

• Added weather + time-of-day detection

• Added MAX_GUESTS cap for scene control

• Fully compatible with Rotating Guest List Roster engine

• JSON/regex‑safe formatting ensured