plan: v1.115 rotor-out robustness + verification-fidelity follow-ups - #258
Closed
avrabe wants to merge 2 commits into
Closed
plan: v1.115 rotor-out robustness + verification-fidelity follow-ups#258avrabe wants to merge 2 commits into
avrabe wants to merge 2 commits into
Conversation
…low-ups Lands the release plan for the follow-ups surfaced by the v1.114 rotor-out work (the parasitic-moment flip the idealised Monte-Carlo campaign could not falsify — dispersion is breadth, not fidelity): - SWREQ-FALCON-FAULT-P03 (proposed) — single-rotor-out FDI robustness under heavy GNSS/gyro noise; detection latency blew up in the v1.114 dispersed full-loop campaign at the heavier envelope. Issue #255. - SWREQ-FALCON-FAULT-P04 (proposed) — supervisor-driven controlled landing after a rotor loss (close the altitude scope the campaign reports-not-gates) + a clean gz confirmation run and the recordable recovery video. Issue #256. - FEAT-FALCON-v1.115 (proposed) — the release grouping; also tracks the verification-fidelity audit of other safety campaigns (issue #257). Both reqs derive-from SYSREQ-FALCON-005 (control allocation). rivet PASS (proposed reqs carry the expected "needs verification" backlog warning until implemented). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
avrabe
enabled auto-merge (squash)
July 10, 2026 20:47
…query
Add `release: falcon-v1.115.0` to FAULT-P03/P04 + FEAT-v1.115 so the release
scope is a QUERY, not an opinion:
$ rivet release status falcon-v1.115.0
Release falcon-v1.115.0 — 2 artifact(s)
proposed 2
✗ NOT cuttable — 2 artifact(s) not yet verified.
`rivet release status` exits non-zero when not cuttable (CI-gateable); it
burns down to cuttable as P03/P04 reach `verified`. Pairs with
`rivet list --release falcon-v1.115.0`.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
Author
|
Superseded by #259, which folds these v1.115 plan artifacts into the FAULT-P03 implementation (P03 → verified, P04 deferred to v1.116) and narrows the Verification-gate filter to avoid the concurrency-cancel that showed here as a false 'fail'. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release plan for the follow-ups surfaced by the v1.114 rotor-out work. Lands rivet artifacts (proposed) assigned to falcon-v1.115.0 and mirrors them to tracking issues.
Why
v1.114 fixed a rotor-out recovery that flipped the vehicle on the real plant despite being "verified" and dispersed over thousands of Monte-Carlo trials. The miss: the campaign + point-test ran an idealized attitude-only sim (constant thrust, true-state feedback, no estimator, no rotational drag). Dispersion is breadth, not fidelity — thousands of trials of a gap-blind model can't falsify a bug the model can't express. This PR turns the residual findings into a plan.
Artifacts (proposed → falcon-v1.115.0)
Both reqs derive-from SYSREQ-FALCON-005. rivet validate PASS (proposed reqs carry the expected "needs verification" backlog warning until implemented). No code change — this is the plan; the feature loops execute it.
Closes none yet (tracks #255 #256 #257).
🤖 Generated with Claude Code