dset-specs-loops-framework

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.

Diagnose software or production failures through reproducible evidence, minimization, hypotheses, instrumentation, first-bad-commit analysis, and DSET Back-to-Left provenance. Use when the user asks to investigate, explain, triage, or find the cause of a defect, regression, failed gate, incident, or inconsistent behavior; diagnosis and reporting are read-only unless the user separately authorizes artifact edits or a fix.

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.