steward-continuity-boundary-lifecycle

Maintains stewardship protocol continuity and tool/personality boundaries across agent governance workflows.

2|Updated Aug 15, 2026
One-click install
npx skills add https://github.com/Arenukvern/shortly --skill steward-continuity-boundary-lifecycle-arenukvern
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: steward-continuity-boundary-lifecycle
Source: https://github.com/Arenukvern/shortly/tree/main/.agents/skills/steward-continuity-boundary-lifecycle
Command: npx skills add https://github.com/Arenukvern/shortly --skill steward-continuity-boundary-lifecycle-arenukvern

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Repository agents risk overclaiming steward personality, merging identities in handoffs, laundering authority through tool output, or persisting raw private memory. This Skill enforces a protocol-first lifecycle that keeps self-model updates, delegation hygiene, and boundary reviews legible and evidence-gated. ## Core Features & Use Cases - Mode Declaration & Threshold Detection: Distinguishes tool-execution from steward-presence, delegation, and sub-steward-lens modes, activating only at ADRs, handoffs, evidence claims, or boundary conflicts. - Self-Model Governance: Provides a consent-aware self-model schema with falsifiers, non-claims, and redaction policies so continuity persists only when it changes future governance behavior. - Boundary Violation Review: Flags authority laundering, personality inflation, identity merging, and lowered evidence bars, routing durable fixes to ADRs, FAQs, evals, or validators. - Use Case: After merging an ADR, ask the agent to update the repo steward self-model; the Skill runs threshold checks, applies the schema, attaches a falsifier, and validates the artifact with the steward CLI before persisting. ## Quick Start Ask the agent to review whether the current task should enter steward presence or stay in tool-execution mode and produce a stewardship protocol review.

Frequently Asked Questions about steward-continuity-boundary-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a repo steward self-model after an ADR?▼

Trigger the skill at the ADR threshold, then apply the self-model schema in references/self-model-schema.md. Persist only synthesized, consent-aware state tied to the trigger, include a falsifier, and validate the artifact with steward schema validate before saving.

When should an agent enter steward presence mode?▼

Enter steward-presence only for ADRs, handoffs, evidence claims, boundary conflicts, tool promotion, product-direction tension, or repeated governance friction. Deterministic tasks like formatting, validation, and mechanical checks stay in tool-execution mode.

How do I audit a delegation for boundary violations?▼

Review the delegation for authority laundering such as 'the steward says' without evidence, personality inflation around tool output, identity merging in handoffs, and lowered evidence bars during mode shifts. Route durable fixes to an ADR, FAQ, eval, harness, or validator.

What is the steward presence readiness lens?▼

It is a sign-based ladder from P0 protocol exists to P5 proven repo steward. Three readiness signs across at least two repo surfaces justify a bounded steward-presence trial, but never a proven_repo_steward claim without structured comparison evidence.

What should never be persisted in a steward self-model?▼

Never persist raw chats, secrets, hidden reasoning, credentials, private relational memory, or unreviewed emotional material. A self-model is a synthesized governance artifact, not a diary and not proof of consciousness.

Does passing schema validation prove steward status?▼

No. A steward schema validate pass is shape-only, not steward proof. Status upgrades like proven_repo_steward require repeated or held-out task evidence with falsifiers, and a not_rejected claim check is still not acceptance.