critique

The user wants this built behind a critic gate: $ARGUMENTS

This is a normal dispatch with one thing added: the work does not count as done because pi said it was done. A second pi session — a different session, with no memory of the first — reads the diff against a contract and returns ACCEPT or REJECT, and a REJECT goes back to the generator to fix.

The reason to separate the sessions is the whole point. A model asked to review its own output has already committed to it: it has the reasoning that produced the code sitting in context, and it will defend that reasoning rather than read what actually got written. A session that has never seen the generator's thinking has only the diff to go on, which is the same thing a human reviewer has.

You are neither of them. You write the contract, and at the end you judge — because two models agreeing with each other is not verification.

1. Write the contract first — before anything is dispatched

The contract is the critic's rubric, and it is written before the generator runs. This ordering is not a formality:

• A critic with no rubric free-associates. It will report style preferences and taste, because those are what is available to say about code when nobody has said what the code is for.
• A rubric written after seeing pi's output gets bent toward that output. You read what was built, and the criteria quietly become a description of it. Then ACCEPT means nothing, because it was never possible to fail.

Write it to a temp file, in numbered items, each one decidable by reading the diff:

DIR=$(mktemp -d)
cat > "$DIR/CONTRACT.md" <<'EOF'
# 驗收契約

1. <a condition someone can check by reading the code, and answer yes or no to>
2. ...
EOF
echo "$DIR"

"Handles errors appropriately" is not an item — nobody can fail it. "A malformed payload returns 400 and does not reach the parser" is: you can point at the line that decides it.

If you cannot write four or five items this way, stop and say so. That is not a contract problem; it means the task is not specified well enough to be gated, and gating it will burn three rounds discovering that.