Explanation
The agents' creed, and what Coding v2 changes
Coding v2 is Coding with a single rule set placed ahead of everything else in the system prompt.
Coding v2 offers a session the same tools and the same panes Coding offers. A session reaches the same things under either mode.
What changes is a single block of text, placed ahead of everything else Claude Code's own system prompt already says. Turret calls that block the agents' creed. Coding v2 puts it first; Coding never adds it at all.
The creed states a handful of hardline rules a session holds to for its whole life under Coding v2. The session fixes a defect it notices, rather than filing it away for later. The creed requires a clean lint and a clean build before the session calls its work done.
A session that spawned another session waits for it, reads what it did, and folds the work in or explains why not. The session reports what actually happened, plainly, including a step it skipped or a result it could not verify. The creed holds more rules than these.
The creed's own copy of the rules speaks generically. It names a project's lint command, its typecheck and its tests, worded to fit any project. A Coding v2 session can open on any working directory, so the creed names no specific project's own commands.
Coding v2 is its own mode. Opening a session as Coding v2 or as Coding decides whether the creed applies for that session's whole life. A session's own row shows which mode it ran under once the session is done, telling the two apart afterward.
See Modes for what Coding v2 offers alongside Coding, and Turn on Coding v2 for making it available as a choice.