Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/XxYouDeaDPunKxX/PA-PVP-mini/llms.txt

Use this file to discover all available pages before exploring further.

Round detection is automatic — the protocol infers the current round from whichever input blocks are present. You can override this entirely by supplying CURRENT_ROUND explicitly, in which case no inference happens at all. When CURRENT_ROUND is absent, the protocol applies the rules below in strict priority order.

​
Detection Rules

PriorityConditionOutcome
1CURRENT_ROUND is explicitly providedUse that value exactly — no inference
2Neither PREVIOUS_ROUND_OUTPUT nor MEMORY_NOTE is presentRound 1
3Prior material is present and contains explicit round numberscurrent = max(prior round numbers) + 1
4Prior material is present but no round numbers are visibleRound 2
Rules are evaluated top to bottom. The first matching condition determines the round; the remaining rules are not checked.

​
What Changes Between Rounds

The round number controls two things: how findings are labeled, and whether a MERGE STATUS block appears in the output. Round 1
  • Every finding is labeled INDEPENDENT.
  • No MERGE STATUS block is produced.
  • The reviewer performs one full review of ORIGINAL_ARTIFACT with no reference to prior output.
Round 2+
  • The reviewer first writes an independent review of ORIGINAL_ARTIFACT without consulting prior output. Only after that step is complete does it check prior findings.
  • Findings are labeled INDEPENDENT, CONFIRMED, CHALLENGED, or NEW depending on whether they match, contradict, or extend prior work.
  • A MERGE STATUS block appears at the end of the output with four fields: confirmed_fixes_ready, challenged_items, new_fixes, and conflicts.
See Output Format for the full field definitions of both blocks.

​
Round Label Reference

LabelAppears inMeaning
INDEPENDENTRound 1 and Round 2+Finding produced without reference to prior output
CONFIRMEDRound 2+ onlyPrior finding re-observed and validated in this round
CHALLENGEDRound 2+ onlyPrior finding rejected, overstated, duplicated, or weak
NEWRound 2+ onlyFinding not present in prior output
Supply CURRENT_ROUND explicitly whenever you want to reset the counter, force a repeat of Round 1 on revised content, or prevent ambiguity when prior material contains inconsistent or missing round numbers. It is the most reliable way to control round behavior.

Build docs developers (and LLMs) love

Get started for freeTalk to us