Skip to content

Add guarded MLAMBDA FIX declarations - #151

Merged
rsasaki0109 merged 1 commit into
mainfrom
agent/wp173-lambda-fix
Jul 29, 2026
Merged

Add guarded MLAMBDA FIX declarations#151
rsasaki0109 merged 1 commit into
mainfrom
agent/wp173-lambda-fix

Conversation

@rsasaki0109

Copy link
Copy Markdown
Owner

Summary

  • add WP173 guarded MLAMBDA FIX declaration layer on the locked WP172 trajectory
  • require WP172 independent consensus, MLAMBDA ratio >= 3, at least 6 satellites, and 5 contiguous epochs
  • retain FLOAT on every failed or missing condition

Locked results

  • Tokyo: 1,296/11,924 FIX (10.8688%), false-FIX 0, sub-50 cm 46.5112%
  • Nagoya: 1,370/7,583 FIX (18.0667%), false-FIX 0
  • mandatory negative holdouts: 0 declared FIX
  • regenerated independent RTK replay: canonical WP173 trajectory identical
  • production audit: 12/12; reproducibility bundle: 38/38

Validation

  • Python smoke: 329 passed, 1 skipped
  • focused WP173/public/audit/bundle suites pass
  • ruff and diff checks pass

Limitation

Tokyo run1 is an operational audit, not a virgin scientific holdout. Most epochs intentionally remain FLOAT.

@rsasaki0109
rsasaki0109 marked this pull request as ready for review July 29, 2026 07:47
@rsasaki0109
rsasaki0109 merged commit e98c5c2 into main Jul 29, 2026
8 checks passed
@rsasaki0109
rsasaki0109 deleted the agent/wp173-lambda-fix branch July 29, 2026 07:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant