Skip to content

Probe extreme Set Slow Motion factors (P8 follow-up) #143

Closed

Description

@e54-bot

Follows #139 and P8 (probes/p8-slow-motion-wait). Owner decision (2026-11-03): measure a few extreme factors to decide whether Set Slow Motion affects the simulated script timeline at all.

Problem

P8 measured factors 50 and 90 with the 100 control: Total Time Elapsed advanced 16 ms per tick and Wait rounded up to whole 16 ms ticks, as at 100. After #139, every other factor ends a run not_modeled. Bastion or another real mode that uses another factor stops there.

Desired behavior

A probe measures Total Time Elapsed and Wait under extreme factors: the smallest value the client accepts, values below that (to observe clamping, such as 0 and a negative), and a value above 100. The probe follows docs/capture-convention.md, and its expected log states the hypothesis "no effect on the script timeline".

Acceptance criteria

  • The probe is added under probes/, with expect.json, and runs in cargo test with runs: 0 until captured.
  • The owner runs it in the client three times, and the capture is ingested with athena ingest.
  • If every factor matches: the simulator treats Set Slow Motion as having no effect on the script timeline for the measured range (including clamped inputs), and the docs state the measured range.
  • If any factor mismatches: the simulator keeps that factor not_modeled and docs/findings.md records the observation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    p1Critical path of the current roadmap line, or a bug that hits real workflowsready-for-implementationContract settled; an Engineer can implement without inventing a decision

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions