Repository navigation
Conversation
Three workloads run side by side, each allowed one destination. The maintenance workload asks for one it was not given; the host refuses and records it, mvmctl explain shows it, and the two inspection workloads carry on. This is beats 1 to 4 and 6 of the proposed factory-edge presentation, with no assertions, staging or teardown machinery: about 25 lines of logic that print the demo. The workloads are started one after another, because starting them together can fail with 'another local volume lifecycle operation is already in progress'. The guide is half a page and maps each step to the mvm-client call the Studio UI would use. That table is from reading the library, not from running it, and it records one gap found on the way: the library cannot report what a machine is allowed to reach (#5521).
auser
enabled auto-merge
November 15, 2026 01:16
This branch has not been deployed
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
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.
The factory-edge demo as the proposal describes it, and nothing more: three workloads run side by side, each allowed one destination; the maintenance workload asks for one it was not given; the host refuses and records it;
mvmctl explainshows it; the two inspection workloads carry on. Beats 1 to 4 and 6 of 'Proposed factory-edge presentation' inspecs/contracts/host-interface-distributed-execution.md. Stop and replace (beat 5) is not included.scripts/factory-edge-demo.shis about 25 lines of logic that print the demo, with a--downto remove the workloads. No assertions, staging, teardown machinery or tests of its own; it was verified by running it on the demo Mac against the v0.28.0-rc.2 release (16 seconds, output pasted in the guide's description of what it prints).scripts/factory-edge-demo.mdis half a page: how to run it, how each step maps to themvm-clientcall the Studio UI would use, a one-time setup, and known limits.The library table is from reading the code, not from running it, and says so. It records one gap found on the way: the library cannot report what a machine is allowed to reach (#5521), which beat 2 needs.
Known limit: the workloads are started one after another, because starting them together failed once with
another local volume lifecycle operation is already in progress(a launch lock). That is a product behaviour worth its own issue.This supersedes the staging, demo-live and one-command scripts (#5495, #5504, #5519), which are a verification harness rather than a demo. Removing the merged ones is a separate decision and not part of this PR.