Skip to main content

Interface: ActorConfig

Defined in: apps/paracosm/src/engine/types.ts:350

Configuration for a simulation actor — the swappable decision-making entity that runs each parallel counterfactual. Was ActorConfig in 0.7.x; renamed in 0.8.0 to match the user-facing terminology (scenario.labels.actorNoun selects the per-domain label like "commander" / "mayor" / "release director").

The legacy ActorConfig name is exported below as a @deprecated type alias so 0.7.x callers compile unchanged. Drop in 1.0.

Extended by

Properties

archetype

archetype: string

Defined in: apps/paracosm/src/engine/types.ts:352


hexaco

hexaco: HexacoProfile

Defined in: apps/paracosm/src/engine/types.ts:373

Six-axis HEXACO personality profile. Required for back-compat with v0.7 callers; for non-HEXACO trait models (e.g. ai-agent), supply a representative HEXACO snapshot AND set traitProfile to the canonical model + traits the runtime should use. The normalizeActorConfig helper at runtime synthesizes a traitProfile from this field when traitProfile is omitted, so existing leader configs continue to work unchanged.

Deprecated

since 0.8.0: prefer traitProfile for new code. Removal scheduled for 0.9.0.


instructions

instructions: string

Defined in: apps/paracosm/src/engine/types.ts:383


name

name: string

Defined in: apps/paracosm/src/engine/types.ts:351


traitProfile?

optional traitProfile: TraitProfile

Defined in: apps/paracosm/src/engine/types.ts:382

Pluggable trait profile naming a registered TraitModel and its per-axis values. When set, this overrides the legacy hexaco field for cue translation, drift, and prompt generation. When omitted, the runtime synthesizes a profile from hexaco with modelId: 'hexaco'. See docs/superpowers/specs/2026-04-26-trait-model-generalization-design.md.


unit

unit: string

Defined in: apps/paracosm/src/engine/types.ts:360

The organizational unit / faction / org / team this leader commands (e.g. "Station Alpha", "Engineering Org", "Player Faction"). Was colony pre-0.5.0; renamed for domain-agnostic semantics so non-space scenarios (markets, game worlds, incident response) read naturally instead of being named after a Mars heritage concept.