@Ze-Stuart thanks for the input. Due to your suggestion it has been a long 2 week low sleep work to built an ambit app with claude ahahh
Lot’s of reverse engineering. Not easy.
I am missing just some points that if someone can help (I believe from Suunto would be easier, @pavel.samokha @dimitrios-kanellopoulos @isazi )
How does the firmware decide a rule is a browsable WORKOUT (listed in the WORKOUT menu)
vs a normal pinned display app? Is it purely that the rule is wired to the
PID_RUNNER_GPS_TEMPLATE_GUIDANCE display template, or is there another marker
(a rule flag, a CustomModes tag, an EXERCISE_MODES_RULE field beyond the 6 bytes
[RuleIdx][UseRule][LogRule] we see, an Apps-entry field, …)?
What bytecode/data does the guidance graph consume to draw a segment (segment count,
per-segment duration/distance/lap end, upper/lower target, target metric)? i.e. what is the
.Binary a Category:"guidance" rule compiled to — its structure, or the App-Zone/VM
primitives it uses that a generic app does not?
Is the guidance .Binary a different bytecode dialect than a normal App-Zone app, or the
same VM with specific built-ins/opcodes for segments/targets? (If the latter, the live
community compiler might be able to emit it with the right source.)
Full claude recap here.
These features that were lost in the movescount transition, and I am trying to get them back to the community.