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.

pa_pvp mini determines which round it is executing based on the input blocks it receives. This matters because Round 1 and Round 2+ behave differently: Round 1 produces an independent review only, while Round 2+ runs both an independent review and a merge-and-challenge step against prior material. Understanding the detection logic helps you submit correctly, especially when seeding the protocol with non-pa_pvp material or stitching together multiple prior rounds.

​
Detection rules

Round detection follows a strict priority order. The first rule that applies wins; the rest are not evaluated.
  1. If CURRENT_ROUND is explicitly provided, use that value. Do not infer the round from context. The explicit value is always authoritative.
  2. If neither PREVIOUS_ROUND_OUTPUT nor MEMORY_NOTE is present → Round 1.
  3. If either PREVIOUS_ROUND_OUTPUT or MEMORY_NOTE is present → Round 2+.
  4. If prior material includes explicit round numbers → current_round = max(previous_round_numbers) + 1.
  5. If prior material exists but contains no explicit round numbers → current_round = 2.
This means that the presence of any prior material is sufficient to trigger Round 2+ behavior, even if that material came from an external source rather than a previous pa_pvp run. If you do not want that behavior, use CURRENT_ROUND to override it.

​
The CURRENT_ROUND override

CURRENT_ROUND is an optional input block that sets the round number explicitly. Use it in any of the following situations:
  • You are submitting external material as PREVIOUS_ROUND_OUTPUT. Without the override, round detection will infer Round 2+, but the round number may be wrong or meaningless for your context. Set CURRENT_ROUND: 1 to run a clean Round 1 review against external material as context, or set a specific number to establish continuity.
  • You want Round 1 behavior even though prior material is present. Pasting a prior review for reference does not have to trigger Round 2+. Use CURRENT_ROUND: 1 to force independent-only behavior.
  • You are stitching together multiple prior rounds into a single submission. If you are collapsing several rounds of output into one PREVIOUS_ROUND_OUTPUT block, the auto-detected round number will likely be wrong. Set CURRENT_ROUND to the correct value explicitly.
Example submission with an explicit round override: 
CURRENT_ROUND: 3

ORIGINAL_ARTIFACT:
[your artifact text]

PREVIOUS_ROUND_OUTPUT:
[combined output from rounds 1 and 2]
When CURRENT_ROUND: 3 is present, the reviewer will not attempt to infer the round from the content of PREVIOUS_ROUND_OUTPUT. It will execute Round 2+ logic at round 3.

​
Why round detection matters

The round number controls which execution path the reviewer follows. Getting it wrong produces incorrect output.
RoundBehavior
Round 1Independent review of ORIGINAL_ARTIFACT only. All findings labeled INDEPENDENT. No MERGE STATUS block.
Round 2+Independent review first, then audit of prior material. Findings labeled INDEPENDENT, CONFIRMED, CHALLENGED, or NEW. MERGE STATUS block included.
If the round is detected as Round 1 when it should be Round 2+, the challenge step is skipped entirely — prior findings are never audited, conflicts are never surfaced, and the MERGE STATUS block is absent. If it is detected as Round 2+ when it should be Round 1, the reviewer will attempt to audit prior material that was not meant to be challenged, potentially producing spurious CHALLENGED or CONFIRMED labels.
If you paste a previous pa_pvp output into your submission as context — perhaps to give the reviewer background — but you want a completely fresh Round 1 review, add CURRENT_ROUND: 1 to your submission. Without it, the presence of prior output will trigger Round 2+ detection and the reviewer will run the merge step against material you intended only as context.

Build docs developers (and LLMs) love

Get started for freeTalk to us