PA_PVP Glossary (Operational, Closed Vocabulary)
This glossary exists to reduce semantic drift across AI<->AI iterations. Prefer these exact terms and avoid synonyms.
Core Outputs
-
Verdict: DO NOWDO LATERDISCARD -
Impact: LOWMEDHIGH -
Urgency: LOWMEDHIGH -
Profile: DIYFULL -
Mode: PLANARTIFACTTARGET -
State: DRAFTACTIVESTANDBYPROBINGCLOSEDEXPIREDDISCARDED -
item_exec_mode / ds:OKSLOWNO_TOOL(derived, per-item) -
terminal:YESNO(derived from state; terminal states areCLOSED,DISCARDED,EXPIRED) -
closure_tier/ct:SIMULATEDREAL-(derived; meaningful only whenstatebecomesCLOSED) dominant_gate/gate: single-cause trace tag (derived, one value)-
FAIL_FAST_CUTFALSIFICATIONDEBT_CEILINGFRAGILITYDEPENDENCY_BLOCKCONFIDENCE_CAPEXTERNAL_BLOCKREDESIGN_TRIGGERSCORE_TRIAGENONE
-
events: derived event trace (max 3) used as causal anchors in DELTA runs-
TRIGGER_<name>PROBE_<probe_id>_STATE_CHANGEDRIVER_<name>_CONFIDENCE_CHANGEEVIDENCE_TIER_UPGRADE
-
derived_version: derivation ruleset id used to compute derived fields (audit compatibility)
Trigger Tags (Item Panel)
trigger is the primary rule tag that caused the item transition.
It is a closed vocabulary, but it is intentionally not duplicated in full here (see the canonical kernel for the complete list).
Common trigger tags you will see in practice:
DEPENDENCY_BLOCK: waiting on unresolved dependency / resource constraintCIRCULAR_DEPENDENCY: cycle detected independs_on(structural modeling error; requires redesign)REDESIGN_TRIGGER: anti-stagnation / invalid plan / redesign requiredBLOCKED_EXTERNAL: blocked by external I/O/auth/timeout (gateEXTERNAL_BLOCK)
Batch Tags (Input)
<<<B ...>>>: batch header (defaults likeexpire_days,keep_open)exec_capability: runtime availability profile- batch:
<<<B ... exec_capability=NO_RUNTIME|RUNTIME_OK>>>(defaultNO_RUNTIME)
- batch:
close_policy: closure policy- batch:
<<<B ... close_policy=SIM_OK|REAL_ONLY>>>(defaultSIM_OK)
- batch:
ssot_scale: output noise control (output-only; SSOT semantics do not change)- batch:
<<<B ... ssot_scale=MIN|DEBUG>>>(defaultMIN)
- batch:
resource_pool: optional batch resource capacity list (for concurrency)- batch:
<<<B ... resource_pool=R1:1,R2:2>>>
- batch:
<<<I ...>>> ... <<<END>>>: one decision item (must have stableid)ask_user: external-data question mode- batch:
<<<B ... ask_user=NONE|ALLOW>>>(defaultNONE) - per-item:
<<<I ... ask_user=INHERIT|NONE|ALLOW>>>(defaultINHERIT)
- batch:
uses: optional per-item resource usage list (must refer toresource_poolids)- item:
<<<I ... uses=R1:1,R2:1>>>
- item:
reversibility: optional per-item reversibility class- item:
<<<I ... reversibility=REVERSIBLE|COSTLY_REVERSIBLE|IRREVERSIBLE>>>
- item:
- Inside each item exactly one:
<<<PLAN>>>: bullet plan or numbered steps<<<ARTIFACT>>>: artifact to audit/optimize (prompt/code/doc/etc)<<<TOOL>>>+<<<TARGET>>>: tool audits a target artifact (must not invert)
- Optional:
<<<PREV>>>: previous machine state for the item (enables delta-only ping-pong)<<<NEW_EVIDENCE evidence_tier=HISTORICAL|REAL|EXPERIMENT>>>: new evidence object (required to revisit CLOSED items with the same id)<<<CHANGE>>>: short change declaration (allowed to revisit SIMULATED-closed items without new evidence)
Evidence
-
rating labels: LOWMEDHIGH -
confidence labels: HIGHMEDLOWVERY LOW -
evidence_tier: SIMULATEDDERIVEDHISTORICALREALEXPERIMENT best_evidence_tier: derived max tier seen for the item (used for caps and event trace)-
SIMULATEDDERIVEDHISTORICALREALEXPERIMENT
-
Interpretation:
SIMULATED/DERIVEDare weak evidence in Complex/Chaotic domains.REAL/EXPERIMENTare the default path to HIGH confidence when uncertainty matters.
Probes
Probe status:
-
ACTIVEINCONCLUSIVEVALIDATEDFALSIFIEDEXPIRED
Probe fields (must be explicit for debt protection):
target_driverkill_switchdecision_contextand the LITE fields:decision_context_iddecision_context_driverdecision_context_metricconstraint_signature(canonical signature; required for new probes)-
context_match:YESNOUNKNOWN -
representativeness:HIGHMEDLOW- optional structural override token (audit-only):
OVERRIDE_REPR(owner)- format:
representativeness: MED OVERRIDE_REPR(peerA)(base bucket unchanged)
- format:
- optional structural override token (audit-only):
expires_at(TTL)adopted_at(per adopter timestamp)
Probe log margin fields (optional but structured):
-
kill_switch_threshold: numberUNKNOWN -
kill_switch_value: numberUNKNOWN -
kill_switch_margin:PASS_WIDEPASS_NARROWFAILUNKNOWN
constraint_signature canonical form (keys and order are fixed):
ENV=<prod|staging|dev|sim>|SCALE=<XS|S|M|L|XL>|DATA=<R|S|H>|TIME=<1m|10m|60m|1d>|CONSTRAINTS=<id1,id2,...>
Ping-Pong
DELTA-only: when<<<PREV>>>exists, only output changes (one BREAK + one PATCH).contested:YESmeans the next DELTA must address the contested point explicitly.
Panels
[USER_PANEL]: human-readable summary at the top (derived-only, no new semantics)[PANEL]: machine panel (short, strict)[HUMAN_TABLE]: markdown table after the code block (derived-only from[QUEUE], for human scanning; UI-only, must not be used as SSOT)[HUMAN_TABLE_OPS]: optional second markdown table after[HUMAN_TABLE](derived-only from[QUEUE]+[ITEM_PANEL]+[DERIVED]+[PROBE_LOG]when present)[RISK_DASHBOARD]: optional derived-only risk hotspot table after[HUMAN_TABLE](derived-only from[QUEUE]+[ITEM_PANEL]short fields)
Consumer Commands (Human Render)
REPORT: consumer-layer command. Paste a PA_PVP snapshot and get a derived-only full human report.REPORT LITE: consumer-layer command. Paste a PA_PVP snapshot and get a 1-page derived-only human report.
Hard rules:
- Reports MUST be derived-only from the pasted snapshot (no new facts, no changes to verdict/gates/steps).
- If something is missing, output must say
missing in snapshot. - If the snapshot is missing or malformed, output must be
ERROR: missing or invalid snapshotand stop. - Reports MUST NOT include any code blocks.
AskUser output (panel-level, single question max):
AskUser: NONE- or
AskUser: <id>: <one minimal evidence request>
Steps (Execution Logging)
Step 1 priority (hard, fixed-order):
- If multiple rules require a specific “Step 1 MUST …” action (reopen mitigation, cycle redesign, probes, dependency blocks, conservation redesign), the kernel selects Step 1 by a fixed priority order.
- Lower-priority requirements that remain relevant must appear as the earliest non-conflicting later step (not dropped).
Probe executability constraint (hard):
- If an item enters
PROBINGwith unresolved dependencies, the Step 1 probe/acquisition must be dependency-independent (must not require dependency output or blocked dependent execution).
Cheap-First Probe note:
- “Cheap-First” is a design constraint for probe steps (timebox<=10m, binary), not a scheduling override over Step 1 priority.
Step status markers (inline on step lines):
status=COMPLETED: step executed in this run and produced an outputstatus=COMPLETED_SIMULATED: step completed using simulated/derived outcome (required inexec_capability=NO_RUNTIMEruns)status=FAILED: step executed but hitfail_if(must trigger the relevant gate by fixed rule)status=FAILED_EXCEPTION: step failed due to runtime exception inexec_capability=RUNTIME_OKruns (must useEXCEPTION_*output token)
Runtime exception output tokens (closed vocabulary, RUNTIME_OK only):
EXCEPTION_IOEXCEPTION_TIMEOUTEXCEPTION_AUTHEXCEPTION_INVARIANTEXCEPTION_DEPENDENCY
Derived Counters (Optional Memory)
counters is a derived, scan-friendly memory line inside [DERIVED]:
tb=<timebox_total_m>/<timebox_budget_m>cx=<complexity_score>/<complexity_budget>pc=<probe_cycle_total>nm=<near_miss_total>nmd=<deterministic_near_miss_total>inc=<probe_inconclusive_total>ovr=<override_repr_total>rb=<reopen_block_total>
Reopen anti-loop memory (derived, authoritative):
reopen_total: how many times the item has been reopened after beingCLOSED(carried across<<<PREV>>>). Whenreopen_total>=1, reopening is blocked (trigger=REOPEN_BLOCKED_BUDGET).
Counters are log-derived:
counters:is scan-only and may be omitted. If omitted, derive the same quantities from[PROBE_LOG]using the kernel definitions.
Debt and complexity:
- If
falsification_debt=OPEN(...), it increases complexity tax (soft disincentive) in addition to any hard debt ceiling guardrail.
Anti-drift Rules (Vocabulary)
Avoid:
- “depends” as a verdict
- vague steps (“improve”, “optimize”, “make better”) without verifiable action
Prefer:
- explicit drivers
- explicit cause/effect in the impact graph
- explicit probes with kill-switch and representativeness
Emission Precedence (Output-only)
MIN_SURFACE: ifprofile=DIYorimpact=LOWand the item is not enteringPROBING, the item output should stay minimal:[ITEM_PANEL]+[DERIVED]+[STEPS]+[NEXT]- probe harness blocks are emitted only when the item is actually
PROBING
[NEXT] semantics:
- If
new_stateisACTIVE/PROBING,[NEXT]is the next executable/measurable action. - If
new_stateisSTANDBY,[NEXT]may be omitted; if present, treat it as “next planned action on revive” (not necessarily executable now).