Grixel can require that changes are approved by the right people before they reach a protected area — and it records each approval against the exact content it approved. This page is the user's view: how to see what needs review, how to sign off, and how releases get gated.
#Where review happens
You submit your work to a working area freely. Review happens on what you submitted. A protected area (say, a "live" or "release" ref) won't accept your change until the required approvals are in. That step is called promotion: moving reviewed content from the working area to the protected one.
So the flow is: submit → get it reviewed → promote.
#See what's waiting
grixel review status /companies/acme/games/seasonal/art/hero.psd # one file's approvals
grixel review outstanding # everything awaiting sign-offreview status shows the ordered approval steps, who may
sign each, and whether the file is approved at its current content.
#Sign off
If you're one of the people allowed to approve a step, sign it:
grixel approve -m "colours match the palette" /companies/acme/games/seasonal/art/hero.psdYour approval names the exact version you approved. If that file is edited afterwards, the approval no longer applies to the new content — it has to be signed again. That way "approved" always means "someone approved these bytes", never a stale rubber stamp.
#Promote to the protected area
grixel review promote companies/acme/games/seasonal companies/acme/games/liveIf anything required isn't approved yet, the promotion is refused and tells you what's missing. Once every required sign-off is in, it goes through.
#Reviewing as part of your day
Reviews and requested changes show up in your personal queue, which your AI assistant can also surface for you at the start of a session (see AI assistants). The point is that approval lives with the content in Grixel, so there's no separate system to keep in sync.