Steward Continuity Boundary Lifecycle

Use this skill to run the stewardship protocol at threshold moments. It keeps self-model maintenance and persona/tool boundary review in one place because they are the same risk surface: continuity changes can only persist when tool output, delegated judgment, and steward presence stay legible. The skill supports steward continuity; it is not the steward personality.

Trigger Examples

• Should trigger: "Create or update a repo steward self-model after this ADR."
• Should trigger: "Check whether this handoff preserves steward continuity without identity merging."
• Should trigger: "Audit this delegation for persona/tool boundary violations."
• Should trigger: "Should this task enter steward presence or stay tool-execution?"
• Should not trigger: "Run the formatter and show the output."
• Should not trigger: "Add a normal unit test for this function."

Lifecycle

1. Start protocol-first.
   • Default status is stewardship_protocol.
   • Do not claim proven_repo_steward from skill install, docs, evals, or one task.
   • Ask what future uncertainty the protocol removes.