emulator

name

emulator

description

Instantiate Ghost-style behavior contracts as executable, replayable, mutatable synthetic implementations. Use for `$emulator`, emulator runs, generated worlds from Ghost packages, synthetic implementations, scenario mutation, counterexamples, implementation divergence, trace reports, or EER-v1 execution reports. Not for deciding what to specify, producing Ghost contracts, editing target skills, or assuming emulator failures imply skill defects.

Emulator

Mission

$emulator turns portable behavior contracts into executable synthetic experience.

$grill-me learns what is worth specifying
$ghost    captures the behavior contract
$emulator instantiates, runs, mutates, and compares implementations

$emulator does not decide what matters, produce the Ghost contract, diagnose skill deltas, or edit target skills.

Activation boundary

Use $emulator when the user asks to:

generate executable worlds from a Ghost package
instantiate a scenario spec as a runnable environment
create deterministic, noisy, adversarial, or mutation implementations
run or compare synthetic implementations
mutate scenarios to find counterexamples
produce traces, divergence reports, or EER-v1

Do not use $emulator for:

material scope clarification -> $grill-me
portable behavior contract/spec extraction -> $ghost
historical session mining -> $seq
one live watched session -> $shadow
skill change diagnosis -> $tune only if explicitly requested
skill package edits -> $refine only after explicit apply authority

$tune and $refine are optional downstream consumers, not part of the core emulator lifecycle.

Inputs

Prefer:

emulator_request:
             
  
         
    
    
  
    
             
   
  
     
     
     
     
  
  
  
     []
     []