/onboard procedure: read roster + team-memory + posture + claims + codify lease + rules-changed for a new operator joining a multi-operator COC repo.

What problem does it solve?

Multi-operator Claude Code repos struggle with reliable onboarding because new operators need a consistent snapshot of identity, roster, posture, claims, and the codify lease without accidentally proceeding on stale or unverified state.

Core Features & Use Cases

• Read-only, deterministic briefing: Produces a structured onboarding runbook that reads operator identity, roster, team-memory, active workspace, posture, adjacency claims, codify lease status, and rules changes without writing any state.
• Integrity-guarded team-memory handling: Validates each team-memory entry’s integrity, surfaces failures explicitly (including an empty failed_integrity section), and skips superseded facts.
• Operational safety gates: Blocks onboarding continuation when identity is blocked, surfaces pending_verification acknowledgements, and prevents concurrent /codify by checking the active codify lease.
• Rules-changed verification support: Detects and enumerates modified MUST clauses candidates for pending verification.

Quick Start

Use the /onboard skill in your first multi-operator session to generate a full read-only snapshot of operator identity, team state, posture, active claims, codify lease status, and required acknowledgements.