The project shell keeps the real state in one place

Once you open a project, Guildhall shifts from “service over projects” into “show me the state.” The shell is built around one promise: setup, active work, reviewer feedback, and the next human decision should not require a scavenger hunt.

The views that matter most

• Thread: the command surface. Setup prompts, spec approvals, live worker trouble, and “you need to answer this now” all gather here.
• Work: the queue and movement surface. This is where you judge whether the guild is making progress or just manufacturing elegant confusion.
• Release: the verdict lane. If something is about to ship, this surface should tell you why it deserves the privilege.
• Settings: the policy and setup layer. Providers, facts, advanced settings, and the knobs that determine how much rope the guild gets.

What the shell is optimizing for

• Make the next real action obvious
• Keep human questions and machine progress in the same narrative lane
• Surface release and reviewer state before it becomes an unpleasant surprise
• Let you drill into transcripts and provenance without leaving the shell

Current strengths

• Left-rail shell structure
• Task drawer inspection model
• Release and reviewer visibility

Still tightening: some denser views need stronger grouping, better type rhythm, and calmer summary bands. The shell already tells the truth; now it needs to tell it with more grace.