Full review cycle

How a task goes through the path “creation → work → review → refinement → acceptance → integration” inside Pulse without manually copying the context. Stage 2 of the plan after the comparative study (version 0.30.3).

Task contract

In the Diff tab, the outcome of the task begins with the contract: goal, acceptance criteria, constraints, and verification commands. This is one text for three readers:

  • author receives it on the first turn and when resuming the session;
  • inspector — in the verification prompt and must mark each unfulfilled criterion;
  • man sees it next to the result upon acceptance.

Saving the changed requirements gives a new version (v1 → v2). Acceptance stores the version at which the result is accepted; the new version removes acceptance and returns the task for review - the previous consent does not apply silently to the new task. Cosmetic edits (spaces) do not change the version.

Notes

The notice is tied to the result version and file, and, if necessary, to lines. It is added by a person (“Comment to the file” under the diff of the file, “Comment to the task” - to the entire task) or an inspector: his findings automatically become comments to the verified version marked “inspector”.

Statuses: open → sent to author → resolved. A package of open comments goes to the selected author session in one request with numbers, bindings and a contract; The author is required to report on each item. The agent’s response does not close the comment - the “solved” status is set by the person after checking the revision. While there are unclosed comments, the acceptance buttons are not available, and the server refuses to accept them even by bypassing the interface.

If the file has changed since the comment, the binding is marked “out of date”: it is either confirmed (“Current” - the binding is transferred to the current version) or closed. Outdated comments are not included in the author's package until they are confirmed. Comments to the task are not completely outdated.

Sent comments give the task a stage "Needs improvement" on the board and in the graph; after acceptance with a merge or via PR, the task is marked "Vlita".

Two types of evidence

Certificate What is this Binding
Contract checks actual running of commands from the contract in the working copy: exit code, duration, output tail result version, requirements version, working copy
Inspector's assessment a strong model reads the diff and contract, gives points and finds result version

They are shown separately and do not replace each other. Running checks takes up a working copy, like an agent's turn, and is therefore not available while the agent is running. If “Require passed checks” is enabled in “Settings → Quality”, you can accept the result only after successfully running checks for the same version of the result. An old run for a different version is marked "obsolete".

After merging a contributor's branch or changing files, the version of the result changes and all evidence of the previous version is considered obsolete: the merged version must be checked again.

Limitations

  • Line comments are not highlighted within the diff; the binding is shown as text (“src/app.ts:12–20”) and goes to the author in the package.
  • Checks are performed sequentially through the system shell with a timeout of 10 minutes per command; integration with external CI is not included in this stage.
  • The aging of a binding is determined by the contents of the entire file, not by lines.
  • The inspector's observation does not distinguish the contract criterion from the general finding; the text of the find contains the notes “[critical]” / “[important]”.