docs: define BYOC at the customer-controlled boundary - #105
Merged
Conversation
abrichr
force-pushed
the
docs/byoc-glossary
branch
from
July 30, 2026 16:42
9c3b2a7 to
68542b5
Compare
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.
Summary
Contract
BYOC is the existing connector and configuration name for a customer-owned cloud runner and storage boundary. OpenAdapt Cloud carries bounded authorization and control metadata and receives only declared results and evidence allowed by the data boundary. The broader public term is customer-controlled execution. It also covers workstations, servers, and on-premises virtual machines that do not use BYOC.
Verification
uv run mkdocs build --strictgit diff --checkNo copy-pinning tests were added.