Skip to content
Majlis docs

Verification and review

Verification submits

Section titled “Verification submits”

Verification runs an explicit command and records its result against an artifact fingerprint:

Terminal window
majlis finish T-14 --revision <current-revision> -- go test ./...

finish requires a readable Git worktree and fingerprints the artifact before it executes the command. Non-Git or unavailable artifact identity fails before execution. On success it submits the evidence and the task enters review. It does not commit, merge, or mark work done.

mj_finish over MCP submits already recorded verification evidence; it does not run verification or accept work.

Acceptance completes

Section titled “Acceptance completes”

Acceptance is an authorized review of the same submitted artifact, with its digest and the current task revision:

Terminal window
majlis task accept T-14 --revision <n> --artifact <digest> \
  --reviewer <assigned-reviewer-actor> --idempotency-key <key>
  • An assigned, independent reviewer accepts using their own provisioned session.
  • Self-review is rejected where independent review is required. An owner override is recorded as an override, never as independent review.
  • Only accepted work moves to done and makes dependent tasks ready.
  • A changed artifact needs fresh verification and review. Revision checks stop a stale acceptance from replacing newer state.

Requesting changes

Section titled “Requesting changes”
Terminal window
majlis task request-changes T-14 ...

The reason is saved as a note in the task thread (up to 600 characters / 4 KiB), the submitted artifact is revoked, and the task returns to work, all in one transaction. Notes provide feedback, not acceptance or ownership.

Set up reviewers in Operator and reviewer setup.