| name | dset-prototype |
| description | Run a bounded disposable experiment to answer a specific design, framework, library, protocol, performance, recovery, or integration question with comparable evidence. Use when uncertainty blocks a DSET Solution Landscape or Decision and production-quality implementation would be premature; never use the prototype as an unreviewed path into production. |
DSET Prototype
This is the thin wrapper for the registered prototyping workflow. Repository-local governing documents own every substantive experiment, evidence, licensing, disposal, and promotion 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 prototyping --format json or python -m dset_toolchain rules resolve prototyping --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 evidence and decisions to the resolved owning artifacts. Never treat disposable runtime work as accepted design or production implementation.
