FA-98994 / Optimizer update state / Member archive
Optimizer state follows list position instead of parameter identity · case 04
Optimizer state follows list position instead of parameter identity.
Case contract
For records [id,p,g,m], update each record independently using m_next=.5*m+.5*g and p_next=p-m_next; preserve record order.
Why this case matters
Optimizer implementations must associate each parameter with its own mathematically specified update state.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| reordered records | [["b", 19.0, 1.0], ["a", 9.0, 1.0]] | [["b", 21, -1], ["a", 7, 3]] | Failed |
MEMBER ARCHIVE
The complete case is available to members.
This record includes three runnable implementations, regression fixtures, execution results, and source hashes.
Member access is invitation-based. Sign in with your invited account to inspect the sources.
Sign in to the archive ↗