Operator-Skill State Shape

Page Promise

Operators can choose the correct hi operator command, interpret installed state and per-scope outcomes, recover safely, and distinguish operator-skill lifecycle work from other HI update surfaces.

Chosen Shape

Use two linked pages:

• A compact command flow at /docs/cli/commands/operator for syntax, status vocabulary, mutation behavior, recovery, and the deprecated delegate.
• A product-foundation concept at /docs/cli/product-foundation/operator-skill-state for immutable authority, copy precedence, verification, partial success, typed failure, and domain boundaries.

This split keeps direct command use short while giving the trust model enough room to be understood without exposing internal implementation mechanics.

Command Structure

1. Purpose and immutable target summary.
2. Command table for status, install, update, and migrate.
3. Status interpretation.
4. Mutation and verification behavior.
5. Failure, retry, and reload behavior.
6. Deprecated delegate and concept-page link.

Concept Structure

1. Independent operator-skill state.
2. Immutable target identity and compatibility.
3. Effective global/project-local state with visible shadowing.
4. Post-write verification.
5. Per-scope partial outcomes and guarded recovery.
6. Typed inspection/integration failures.
7. Explicit neighboring-domain boundaries.

Format Decisions

• Use one table on the command page because each subcommand repeats purpose and outcome fields.
• Use short prose and bullets for status vocabulary and failure behavior.
• Use one compact precedence flow on the concept page.
• Name the exact immutable target without publishing a raw installation URL.
• Link the command and concept pages to each other.
• Avoid implementation types, internal agent instructions, and unverified future behavior.

Merge Notes

• Add operator to content/docs/cli/commands/meta.json.
• Add operator-skill-state to content/docs/cli/product-foundation/meta.json.
• Add this artifact bundle to the private public-docs index and metadata.
• Keep public content under surface: wiki, permission: internal, and status: implemented to match the existing CLI routes.