Guildwork

Paid for by an incidentRouting and capabilities

The silent default agent

What broke

Given a profile path that did not exist, the harness exited 0 with an empty stderr and ran the default agent — byte for byte the control's system prompt. And the bare-name form of the flag loaded the profile headless and loaded nothing in the interactive terminal, with no failure line even in the CLI's own debug log.

The rule it paid for

The launcher resolves the profile itself, from the governance commit, before anything starts; the regime is part of the claim and every refusal names it.