🍋 Trace-or-Fake Market Game 3×2 rule simulator

COMSCI/ECON 206 · Week 2 · Intellectual Statement II — when generation is free and verification is expensive, good code and junk code look the same (a lemons market). You are a developer publishing your own open-source tool. Two questions decide your strategy; every run is recorded; after three runs the page reports what you observed.

Q1 · When you release your tool, do you attach an auto-generated trace file (every claim carries clickable source links plus an input–output declaration)? A · Provide the trace file honest cost +5% · total market benefit +20% B · Publish with no trace file cost unchanged · benefit unchanged C · Fake a trace file defect cost −20% · market benefit −20%

Q2 · Do you enroll in the platform verifier, so buyers can one-click spot-check your links and results? Use the verifier cost +5% · stability +20% Do not use the verifier cost unchanged · stability unchanged

Payoff matrix (all 6 cells)

C = cost index · B = market-benefit index · S = stability index · L = long-run score (= benefit − cost + stability gain). The highlighted cell is your current selection. The numbers are computed from the single #payoff-spec block below the page — the same block verify_game.mjs executes off-line.

All values on a base of 100 for cost, market benefit, and stability.
Strategy ↓ / Verifier →	Use verifier	No verifier

Run log — three runs are required for the report

Run	Q1 choice	Q2 · verifier	Cost	Benefit	Stability	Margin	Long-run score	Scenario note

🍋 Trace-or-Fake Market Game 3×2 rule simulator

Outcome of the chosen strategy

Payoff matrix (all 6 cells)

Run log — three runs are required for the report