| name | dset-clarify |
| description | Turn ambiguous product or domain intent into explicit DSET vocabulary, boundaries, invariants, requirements, scenarios, proof obligations, and decision records. Use before specification acceptance when a feature request has unresolved branches, overloaded terms, hidden actors or states, unclear ownership, conflicting edge cases, or premature solution choices. |
DSET Clarify
This is the thin wrapper for the registered domain-clarification workflow. Repository-local governing documents own every substantive rule.
Bootstrap and invocation
- Locate the repository root by walking upward to
dset/scopes/meta/dset.yaml for schema 1.2 or legacy dset/dset.yaml for schema 1.0/1.1; stop if both authorities exist.
- Run
dset rules resolve domain-clarification --format json or python -m dset_toolchain rules resolve domain-clarification --format json.
- Stop on any nonzero result. Never fall back to this wrapper, agent memory, an installed template, or remote framework prose.
- Before governed work, report the resolved workflow ID, profile/version, customization identity, ordered rule IDs and paths, wrapper identity, and conflicts.
- Read and apply the resolved governing documents in their returned order.
Handoff
Apply only the authorization and output boundaries resolved from the repository. Return durable conclusions to their owning project artifacts. Without write authorization, return a proposed update and leave the repository unchanged.
