Relationships
#4938 stagecraft studio: Inspect shows each stage as a field explorer, not YAML
Opened by skunk-ape · 11/20/2026· Shipped 11/20/2026
Problem
To understand a stage in the studio, a person ends up reading the factory definition's YAML. Inspect shows a few structured fields (let, passed inputs, result evidence) and the prompts as expandable blocks. Everything else means reading the source. Nothing on the page says what a field does, whether it's optional, or what it defaults to when left out.
What to change
Inspect shows each stage as a field explorer:
- every field the definition schema allows for that stage's work mode, grouped sensibly (work, products, gates and exits, limits, prompts);
- for each, its value, or its default when unset, marked as the default;
- whether it is optional;
- a tooltip, or a line on focus, saying what the field does;
- prompts and other long prose collapsed, with the file name when the text comes from an included file (if the include feature has landed).
The field descriptions are written once, on the definition schema, and REFERENCE.md's field tables are generated from or checked against them, so the studio and the docs can't drift. Today the schema carries no descriptions, so writing them is part of this work.
The studio stays read-only (DESIGN.md, "Read-only"). The Source tab stays for anyone who wants the YAML.
Done when
- Every stage field in the schema shows in Inspect with its value or default, optional or required, and a description.
- Descriptions come from the schema, and a test fails when a field has none or REFERENCE.md disagrees.
- Works in light and dark themes, at narrow widths, and by keyboard (tooltips reachable on focus).
- The PR includes screenshots, and a live preview was reviewed before verification.
Out of scope
Editing definitions in the studio, and any change to the engine's behaviour.
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.