ssot-boundary

name	ssot-boundary
description	Manage boundary entities with full CLI coverage, including scoped feature/profile membership and freeze operations.

SSOT Boundary

Use this skill for boundary-only operations.

Command discipline

• Do not spend turns rediscovering syntax with --help during normal SSOT work. Use the command surface and examples in this skill directly.
• Pick one verified CLI rail for the repo (ssot, ssot-registry, ssot-cli, or uv run ssot) and reuse it consistently by substituting that rail into the examples below.
• Only inspect parser or help text when the user explicitly asks about the CLI surface or when observed runtime behavior contradicts the command patterns documented here.

Command surface

• boundary create|get|list|update|delete|add-feature|remove-feature|add-profile|remove-profile|freeze

Workflow

1. Inspect current scoped features/profiles.
2. Add or remove scope members explicitly.
3. Freeze boundary when scope is final for release evaluation.

Operating rules

• Freeze is a hard scope gate; avoid post-freeze scope churn.
• Freeze does not prove runtime implementation, required tests, evidence, or verification are complete.
• Confirm in-scope features are targeted appropriately before freezing.
• If the request includes implementation, tests, verification, release certify/promote/publish, or closure, escalate to $ssot-e2e-change-orchestrator.

Example

ssot boundary get . --id bnd:demo.v1
ssot boundary add-feature . --id bnd:demo.v1 --feature-ids feat:demo.login feat:demo.audit
ssot boundary freeze . --boundary-id bnd:demo.v1