Repository navigation
Clarify host setup and maintenance ownership - #85
Draft
gustavonline wants to merge 1 commit into
Draft
gustavonline wants to merge 1 commit into
gustavonline wants to merge 1 commit into
Conversation
Describe the existing coordinator, Foundation and project AgentOps responsibilities, startup stages, scoped maintenance holds and consistent same-host recovery. Preserve separate source, synthetic and live-host evidence. Refs #83. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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.
Host setup could look ready before startup and recovery had actually been demonstrated. The Foundation setup and adoption guides now explain who owns each step and which observations are still required.
Before, a deferred update could become a general stop. The guidance now keeps admitted work moving when no hold exists, while respecting a real maintenance hold and preserving healthy jobs. It also covers separate owner/execution accounts, one native maintenance opportunity and consistent private recovery before disruptive changes.
Validation: independent exact-source ACCEPT; 8 skills checked with zero errors; 11 unit tests passed; 9 portable Foundation files staged; four synthetic decisions matched the rubric. Boot, reconnect, update and recovery remain separate live gates. Nothing was installed or restarted.
Addresses #83 (reusable source guidance); live-host acceptance remains open.