Repository navigation
docs(workspace): define PM coordination and recovery retirement - #175
Merged
Merged
Conversation
itlezy
changed the title
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.
Parent coordination now has one maintained policy entrypoint for mission, approved scope, decision ownership, parallel assignments, integration batches, technical status and final cleanup. The workspace startup policy routes parent agents to it; the documentation index and site navigation make it discoverable.
The current mandate is consolidation with existing gates, followed only by a fast Clippy/type-check preflight and PM-coordinated integration batches. Working hours remain guidance. The completion check covers clean current mains, integrated or explicitly archived topic history, final PR dispositions, retired checkouts and finished owned worker/monitor processes.
The workstream guide also documents Builder #56's explicit abandonment path: archive exact heads in local recovery refs before retirement, retain all dirty/open-PR/ownership refusals and keep topic deletion a separate parent operation.
Validation: normal privacy/hygiene hooks, item taxonomy and documentation structure checks passed. Full hosted documentation and platform checks remain required before merge. The initial navigation check correctly caught a missing index link, which is fixed in the final tree.
Refs emulebb/emulebb-build#55. The recovery-guide rollout follows Builder #56.