GeezerVison is showing github.com — docs: record the K10 and K11 gate verdicts by axisrow · Pull Request #858 · Apibim-com/BeamCraft
Conversation
axisrow
commented
Nov 9, 2026
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
What this changes
Records the owner's 2026-11-09 acceptance of gates K10 and K11 in the three places the
roadmap flow requires:
ROADMAP.md: the two verdict rows become passed 2026-11-09 and the header date moves.docs/plan/decisions.md: the 2026-11-09 entry records the decision.docs/plan/k10-k11-acceptance-evidence.md (new): the evidence the verdict was taken on —
the delivered cards (T01–T04 and V11–V17 for K10, I04 and I05 for K11, with the stored
schedule-template slice noted for honesty) and the follow-ups that stay documented and
unscheduled.
No code changes. The M3 milestone closes on the same decision, outside this pull request.
How you verified it
-
cargo fmt --all -- --check (recorded gate stage, exit 0)
-
cargo clippy --workspace --all-targets -- -D warnings (recorded gate stage, exit 0)
-
cargo test --workspace (recorded gate: 2707/2707 runnable tests executed with nextest
0.9.149 on macOS aarch64, plus mandatory doctests and cargo doc -D warnings, all exit 0;
the receipt binds this head and base)
Provenance
- Nothing taken from Tekla Structures or any Trimble product (assets, code, documentation, tables)
- No GPL/AGPL code copied in
- No new assets
🤖 Generated with Claude Code
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
The owner accepted both gates on 2026-11-09: the tools-and-views scope
(T01-T04, V11-V17) and the attributes-and-schedules work (I04, I05). The
verdict needs its evidence record, so this adds the acceptance-evidence
document, the decisions.md entry and the two passed verdicts in ROADMAP.md.
The M3 milestone closes on the same decision.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review of PR 858 (docs: record the K10 and K11 gate verdicts)
Verdict: approved. No inline findings.
The change is the legitimate docs-only vehicle for a gate verdict, used exactly as the roadmap flow prescribes: the two ROADMAP rows become passed 2026-11-09 with the header date moved, the decisions entry records the decision, and the new evidence document states what was accepted. The records are mutually consistent and the evidence document is factually accurate against the repository:
- The upstream milestone M2: tools and views stands at 18 closed cards, none open, exactly as the evidence claims; spot-checked cards across the K10 and K11 tables (#533, #463, #461, #439, #450, #531, #532) are all closed, and the K11 delivered-by references #748 and #750 are merged upstream pull requests.
- The accepted scope is really on master: the placement-aware GR-N22 guard, the placement_to_world/placement_to_local maps behind the magnetic follow-up, the skipped_plates view export, the bolt follow_moved_part and the corrected arc sweep angles are all present on the base tree, so the verdict accepts delivered behaviour and the evidence line that the GR-N22 acceptance wording now matches the delivered guard is true.
- The honesty markers hold: the stored schedule-template slice is recorded separately with its fork delivery reference rather than folded into the #532 acceptance, the I01-I03 deferral stays in the ROADMAP row, and the follow-ups are listed as documented and unscheduled rather than closed.
The receipt is exact: commit 99fb464 (the head), tree 4a1d2a85 (verified against the commit object), base 7c21d02 (the current upstream master tip and the parent of this single commit), full scope per the docs-PR precedent, 2707/2707, source_unchanged, all six stages green.
No code changes; provenance statements hold.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
axisrow
added a commit
to axisrow/BeamCraft
that referenced
this pull request
Nov 10, 2026
…pibim-com#862 waves and the Apibim-com#859 delivery squash
BeamCraft-Test-Gate: {"version":1,"commit":"d17c66c78a29a7a6eb79597d24c4f21fed0aeba9","tree":"48979ce99d835a7595502b1405fcba222b928e04","base":"d17c66c78a29a7a6eb79597d24c4f21fed0aeba9","merge_parent":"a95d6b7dc77025e90319938b8dad174422ac91f1","os":"macos","arch":"aarch64","scope":"full","ui_independent_reason":null,"ui_tested":true,"rustc":"rustc 1.99.1 (58cf8f9c3 2026-10-13)","cargo":"cargo 1.99.1 (5f94df478 2026-08-27)","nextest":"cargo-nextest 0.9.149 (3fe4ef319 2026-10-20)\nrelease: 0.9.149\ncommit-hash: 3fe4ef31972f24e0c94cfe291718eab0fe678260\ncommit-date: 2026-10-20\nhost: aarch64-apple-darwin","expected_tests":2739,"executed_tests":2739,"ignored_tests":["beamcraft-test-gate::process::process_fixture"],"source_unchanged":true,"stages":[{"name":"format","exit_code":0,"elapsed_ms":1751,"timed_out":false},{"name":"clippy","exit_code":0,"elapsed_ms":8593,"timed_out":false},{"name":"prepare","exit_code":0,"elapsed_ms":25637,"timed_out":false},{"name":"tests","exit_code":0,"elapsed_ms":195244,"timed_out":false},{"name":"doctests","exit_code":0,"elapsed_ms":1487,"timed_out":false},{"name":"docs","exit_code":0,"elapsed_ms":3614,"timed_out":false}]}
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.
|