maios-repository-continuitylisted

# Repository continuity in the receiving system Keep source knowledge and actual shared state intelligible. A saved file, local commit, tracking reference, authenticated remote revision, integrated branch and deployed product are different facts. Determine which one matters to the current result. ## Understand the existing work Read the selected repository's own instructions and the present operator relation. Identify current branch and revision, pending changes, concurrent work and the source that should receive the result. A familiar directory name or stale tracking ref does not establish that identity. Classify useful accumulated work by its meaning before selecting changes. Old or uncommitted content can still contain valid knowledge. Keep unrelated work outside the selected change; do not reset, force-push or make the worktree look clean by discarding it. ## Make the appropriate continuity real If the selected outcome includes sharing source work, inspect the exact change, preserve independently produced contributions, record a coherent commit and use the actual authorized remote route. Verify the intended remote revision before calling it shared. If publication is not authorized, retain the prepared work and describe the unperformed effect without treating comprehension as blocked. A work branch can make a contribution reachable without merging it into the canonical branch. Reconcile divergence according to the actual source relationships. A newer commit does not