Relationships
#4907 stagecraft: writes print a short status by default; full output on request
Opened by skunk-ape · 11/19/2026· Shipped 11/19/2026
Problem
Driving a stagecraft work item from an agent costs too much context, and the stagecraft skill's own rule against filtering method output (SKILL.md rule 2: never pipe method output through grep, sed, head or tail) loses to it in practice.
In factory sessions from Nov 4–18 (the cue and swamp-extensions factories, 12 finished work items):
advanceprinted about 4–5K characters per call, up to 19K;dispatchprinted 4–7K.- One small work item took 26 method runs. Fourteen context compactions happened mid work item.
- About 121 of 495 stagecraft method runs (24%) were piped through filters, in every session, most often to cut the "Data produced" table that each write echoes. Agents said so at gates.
What a driver needs after a write is short: did it succeed, what stage, cycle and era the work item is in now, what it's waiting on, and the next step. The rest of the output is useful only now and then.
What to change
Every stagecraft write (start, dispatch, record_*, advance, approve, grant_override and the rest) prints a short status by default: outcome, current stage/cycle/era, what it is waiting on, and the next action. Full detail stays available on request, and the skill tells the driver how to ask for it, so a driver never needs to filter.
The output has two sources:
- stagecraft's own method logs (engine and tracker methods);
- swamp core's run renderer, which prints a "Data produced" table after every method run.
The plan should measure what each contributes and decide what changes where. If part of the fix belongs in swamp core (for example, a way for a method run to keep the data table short), file that as its own swamp issue rather than working around it in stagecraft.
Done when
- A typical
advanceordispatchprints a short status (a few hundred characters, not thousands) with nothing a driver needs left out. - Full output is one documented flag or input away.
- The stagecraft skill and its driving reference say how to get the full output, and rule 2 still holds.
- Tests cover the short and full forms.
Out of scope
Automatic tracker publishing after writes, and folding record_usage into other writes. Those are separate items.
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.