Skip to main content
Use Production → Requests (/production/requests) to follow change requests through the Forge Dogfood Factory’s delivery lifecycle. The request is the change being delivered; the associated implementation plans and workflow runs provide the execution context.
Change requests (dark)Change requests (light)

Change requests — Forge Console at /production/requests

What you can do

Find the request

The page opens on Active. Choose a filter before interpreting an empty queue: A request awaiting approval is intentionally absent from Active. A request marked verified can appear under Completed even before its stored status becomes completed. Each row shows its title and status, with risk, priority, source deployment, external references, and updated time when those values exist. Open the row to inspect the full request.

Inspect a request before acting

  1. Read Description and Acceptance criteria to establish the requested result.
  2. Check Properties for risk, priority, and severity.
  3. If Source deployment is present, confirm the environment and PR context. A preview reference and a production reference describe different evidence.
  4. Review Triage notes for the reasoning, recorded approver, or rejection reason.
  5. Open the associated implementation plan to follow the delivery work. Use external references when you need the linked issue or PR.
The detail is an inspection surface: the presence of an approver’s name is a recorded fact, not an instruction to approve the request again. Use the relevant Approvals or My Work task when a human decision is waiting on you.

Verify progress

Return to the list and compare the current status and updated time. To investigate execution, follow the associated plan and inspect Runs; a request’s delivery status is not a substitute for the status of an individual workflow run.

Key state to watch

  • awaiting_approval — shown under Needs Approval, not Active.
  • verification_rejected — verification of the change was rejected; the request stays under Active.
  • Source deployment — a preview reference and a production reference are different evidence.
See Factories for the production team and Events for execution evidence.
  • Approvals: requests waiting on a decision.
  • Runs: the run a request started.
  • Factories: the production team that delivers requests.