TERMINAL DIAGNOSIS
Structured literal evidence. Expand a field to inspect its contents; the source link preserves the exact JSON bytes.
classification
TECHNICALLY_INCONCLUSIVE
last committed turn
5
blocked turn
6
original request bytes
191646
reconstructed corrective request bytes
250447
pinned limit bytes
240000
correction model call started
false
review issues
GM
message
Decision T006-D02 creates a binding bilateral obligation (OBL-reedhaven-hearthmere-storage-jars) and fact (fact-reedhaven-hearthmere-pact-turn6) allocating 20-25 ceramic jars from Hearthmere to Reedhaven. Player 2 proposed this trade at Measure House, but Player 3's submission gave no order or authorization to trade jars (directing kiln work toward domestic vats, braziers, and tiles), and Pia/Lorn lack authority to bind Hearthmere to a major forward production pact without leader consent. This overrides character agency and leadership power limits.
player id
GM
GM
message
Fact fact-measure-valley-commons-victory-turn6 contains charter source terminology ('sustained voluntary investment' from the Victory rules), meta-game turn calendar counters ('six consecutive months'), and omniscient GM evaluation ('achieved permanent stability and mutual prosperity'). Player-visible facts must contain only in-world consequences and no omniscient appraisal or rulebook source text.
player id
GM
player1
message
Leader-barleybank is credited with DIRECT_OBSERVATION (empty propagation path) for fact-reedhaven-river-convoy-turn6, but Barleybank's leader was in Barleybank and could not directly observe Garr and Fara's landing operations downriver at Reedhaven or the full transit to Hearthmere; this requires propagation via returning supercargoes.
player id
player1
player2
message
Fact fact-reedhaven-hearthmere-pact-turn6 discloses a completed binding agreement allocating 20-25 jars, which was only a proposal from Player 2 and was neither authorized nor agreed to by Hearthmere.
player id
player2
player3
message
Leader-hearthmere is credited with DIRECT_OBSERVATION (empty propagation path) for fact-measure-house-harvest-sync-turn6 and fact-reedhaven-hearthmere-pact-turn6 at Measure House, despite Hearthwarden remaining in Hearthmere and sending Pia as witness. Knowledge of Measure House events must be REPORTED via Pia.
player id
player3
player3
message
Fact fact-reedhaven-hearthmere-pact-turn6 binds Hearthmere to an unsubmitted, unauthorized jar production contract that conflicts with Hearthwarden's explicit orders for kiln cooling and domestic wares.
player id
player3
player4
message
Leader-stonecross is credited with DIRECT_OBSERVATION (empty propagation path) for fact-measure-house-harvest-sync-turn6 at Measure House, despite Roadwarden remaining in Stonecross to inspect the reference vault and sending Willa as representative. Knowledge of Measure House events must be REPORTED via Willa.
player id
player4
review rationale
The proposed adjudication successfully resolves the primary harvest and logistics operations, but fails review due to two major causal/rule issues and several epistemic propagation defects. First, GM Decision T006-D02 approves a completed, binding pact (and obligation OBL-reedhaven-hearthmere-storage-jars) committing Hearthmere to deliver 20-25 ceramic jars to Reedhaven based solely on Player 2's proposal, violating character agency and leadership boundaries because Player 3 never authorized this trade and explicitly ordered kilns dedicated to domestic wares. Second, player-facing fact fact-measure-valley-commons-victory-turn6 leaks charter rule terminology ('sustained voluntary investment'), meta calendar references ('six consecutive months'), and omniscient GM victory evaluations rather than reporting in-world consequences. Finally, leader-hearthmere and leader-stonecross were erroneously assigned DIRECT_OBSERVATION for assembly events at Measure House that were attended only by their appointed witnesses (Pia and Willa), and leader-barleybank was assigned DIRECT_OBSERVATION for Reedhaven's downriver landing management.
turn6 delivery occurred
false
note
The corrective request was rejected before provider scheduling. No limits, prompts, code pins, submissions or accepted history were changed to force completion.