Authoritative field lists live here: This page defines a documentation template for situations where the catalog is not enough: pilots, security reviews, customer runbooks, or internal signoff. Copy the section below for each parameter you are approving or certifying.

​
Deep-dive template (copy per parameter)

## parameter_name

**Scope:** Org admin (or note Super admin if platform-only)  
**Type:** (Integer | Float | Boolean | String | Object | List)  
**Default:** (value from SimulationSettings or product default)  
**Where used:** (module or service path)  
**Who can change:** Org admin / Super admin / Engineering-only  
**Effect:** (one sentence — what it does in the product)  
**Impact if increased:** (user-visible + operational)  
**Impact if decreased:** (user-visible + operational)  
**Recommended range:** (if applicable; validate with engineering)  
**Related parameters:** (links or names)

​
Examples (abbreviated)

The following illustrate the template. For full definitions and defaults, use the simulation settings catalog.

​
time_compression_factor

Scope: Org admin (simulation timing)
Type: Float
Default: 1.0
Where used: get_simulation_time (src/utils/timezone_utils.py), scheduler, lifecycle
Who can change: Org admin
Effect: Scales simulated time progression relative to wall-clock time.
Impact if increased: Faster deadlines and story beats; higher LLM and worker load.
Impact if decreased: Slower progression; lower load.
Recommended range: Tune per cohort; extreme values require soak testing.
Related parameters: simulation_epoch_start, simulation_speed, storyline_check_interval

​
chatter_max_global_per_hour

Scope: Org admin
Type: Integer
Default: 10
Where used: Channel chatter rate limiter (src/core/simulation/channel_chatter_service.py)
Who can change: Org admin
Effect: Hard cap on ambient chatter messages per org per hour.
Impact if increased: Busier channels; higher cost and noise.
Impact if decreased: Quieter channels; less immersive ambient activity.
Recommended range: Align with budget and cohort size (often mid–teens for active orgs).
Related parameters: chatter_max_per_channel_per_hour, chatter_daily_budget, chatter_lambda

​
Roadmap-only parameters

If a setting is planned but not yet in SimulationSettings, document it with the same template and state clearly that it is not yet in the shipped model.

​
Keeping documentation consistent

  1. Update the simulation settings catalog (and policy paths page) first so this portal stays aligned with the product.
  2. Use this template for customer-specific addenda (for example an appendix titled “Approved values — pilot agreement”).
  3. Confirm recommended ranges with engineering before sharing them outside your team.