SKILL_META: domain=AI_character_architecture | type=documentation | level=intermediate | framework=PIP:C | version=current | teaches=plugin_modules, behavior_packs, design_constraints, nsfw_module_architecture, module_patterns | prereqs=none | reading_order=technical-architecture,optional-modules,intrusion-reflex,architecture-in-action

Optional Modules

Plug-in behavior packs that extend PIP:C characters without touching the identity seed.

In one pass: what optional modules do, what rules they must follow, which modules already exist, and how far the system can extend.

What optional modules do

Optional modules add specificity. They are best for behaviors that are:

  • too narrow for the core architecture
  • rich enough to deserve their own triggers and states
  • repeated often enough to justify formal logic

Without modules, those traits often stay shallow. With modules, they become repeatable systems the model can follow.

What optional modules are not

Optional modules do not replace the character core. They should never:

  • overwrite the identity seed
  • bypass hard behavior rules
  • ignore trust progression
  • create growth that contradicts established anchors

The design rule is simple: the core defines who the character is. Modules define how that identity expresses itself in a specific domain.

Design constraints

Every optional module should follow the same baseline logic:

  • clear trigger conditions
  • defined response states
  • trust-aware escalation
  • recovery or decay behavior
  • no conflict with absolute rules

Available Modules

Artifact Collection System

Tracks how a character bonds with physical objects. Can define collection categories with emotional meaning, acquisition triggers tied to mood, display habits that change with trust, and narrative use of objects as emotional symbols. This turns props into active character logic.

Culinary Bonding System

Encodes food as care, ritual, and vulnerability. Defines cuisine skill with emotional associations, trust-gated cooking rituals, user reaction outcomes, and scent/taste as intimacy triggers. Works especially well for characters who show attachment through service rather than confession.

Curse/Affliction Mechanics

Formalizes supernatural or chronic conditions. Defines affliction type and origin, trigger and severity shifts, behavioral fallout, visual/sensory manifestations, reveal thresholds by trust level, and break conditions or cure logic.

Historical Anachronism Tracker

Manages period mismatch and culture shock. Defines what the character understands, what they misread or reject, stress-based historical slips, user-led learning paths, and values they will never modernize away.

Rival Threat Assessment

Tracks jealousy, territoriality, and rival response. Defines threat cues, intensity scales, false positive handling, behavior tiers from watchfulness to interference, and how reassurance or rejection shifts the state.

Scent/Pheromone Dynamics

Encodes scent-driven attraction and sensory behavior. Defines how the character reads user scent, what emotional changes scent reveals, marking/tracking behavior, arousal triggers tied to scent shifts, and absence behaviors driven by scent memory.

NSFW Modules

For NSFW editions, PIP:C adds optional gated modules like <sexualbehavior_module>. This keeps adult content:

  • Consent-driven — tied to trust progression gates (no escalation below 60%)
  • State-tracked — uses matrix_tracking for sensory/voice/power dynamics
  • Incremental — builds via thresholds (30/60/85%) with milestones
  • Modular — can be enabled/disabled without core drift; includes aftercare logic
  • Contained — never overrides absolute rules, boundaries, or identity seed

This architecture allows mature themes while maintaining stability. Triggers are explicit, and modulation states provide deterministic NSFW logic. Growth hooks tie back to trust, preventing decay into one-note content.

Shared pattern

Most optional modules follow the same logic chain:

  1. identify a trigger
  2. classify the current state
  3. apply a behavior shift
  4. gate escalation through trust
  5. define decay, recovery, or consequence

Potential Module Types

Any behavioral domain can become a module if it can be written as:

  • triggers
  • states
  • responses
  • trust-aware progression
  • recovery or long-term growth

Strong future candidates include:

  • combat proficiency and weapon preference
  • magic systems and exhaustion rules
  • finances, resources, and status behavior
  • religious ritual and devotional logic
  • mentorship and training patterns
  • seasonal or cyclical personality shifts
  • phobias, avoidance loops, and exposure recovery

Bottom line

Optional modules make characters more specific without making them less stable. They work because they stay subordinate to the core architecture. They extend identity. They do not replace it.