Timing — Pole & Ring
Evidence scope: The behavior below is from the pinned Solidity source. A source-file hash does not establish deployed bytecode equivalence. Check the selected deployment and caller before sending a transaction.
RING.Eta resolves the active pair through SEI, calls YUE.React for Phobos, then PANG.Push, and overwrites Moments[currentSoul] with the returned Iota. This records one latest value per session Soul, not an append-only history. LAU.Void can change the session’s Soul.
The play
Section titled “The play”Read Moments for an explicitly known Soul. To preview Eta, simulate its entire nested call with the intended origin. YUE.React is owner-gated, so a source-visible public Eta method is not proof that every deployed caller path succeeds. Verify owner relationships and exact simulation results.
YANG.Pole values and reaction outputs are contract state. A calendar alone does not establish when they change or which modular result will be larger. Do not infer a timed reset or guaranteed reward from a snapshot overwrite.
Use these calls here. Simulations preview the current state; each confirmed call is a separate transaction.
YANG.Pole(uint256)Read
Open this function to load its call form.
RING.Moments(uint64 Soul)Read
Open this function to load its call form.
RING.Eta()Simulate / call
Open this function to load its call form.