For AI agents: the complete documentation index is available at https://docs.flezise.com/llms.txt, the full documentation bundle is available at https://docs.flezise.com/llms-full.txt, and this page is available as Markdown at https://docs.flezise.com/artifacts/submit-for-review.md.
Docs

Submit for review

Submitting moves an artifact from Draft to In Review and notifies the configured approvers. Nothing advances to approval without this step.

The Submit for Review button at the right end of the artifact header bar

Submit for Review

Open the artifact and press Submit for Review in the header bar. The button appears only while the artifact is a draft.

An artifact returned for revision shows Resubmit for Review in the same place. Both buttons do the same thing; the label changes based on whether the artifact is in Revise status (changes_requested).

Submit for Review is also available in bulk: select multiple artifacts from the list and press Submit for Review in the bulk action bar.

What blocks submission

Generation is still running. The button is disabled while the builder agent is generating content. Wait for generation to finish.

A dependency is not approved. If the artifact lists other artifacts in its depends_on field, every one of them must be in approved or locked status before submission is allowed. The error names the dependency that is still open.

After submission

Three things happen in sequence:

  1. The artifact status moves to In Review.
  2. The approval policy initializes for this submission, creating a pending action for every user who can approve at the current level.
  3. The verifier agent (Argus) runs exactly one review and posts its findings to the artifact.

The verifier agent's findings appear in the Review cockpit and in the Review readiness card in the right-hand sidebar.

Next steps