Skip to content
Sprint projectOct 26, 2026Hong Kong

When a Local Pricing Guard Is Not a Welfare Promise

Mohammadpayam Taebi, Arad Maleki · Team Boozines

Submitted to AI Collusion Research Sprint. Sprint projects are early-stage work by participants, not Apart Research publications.

A local pricing rule can improve observed customer benefit without guaranteeing its target. We study a bounded logit duopoly where a guard permits near-best immediate profit against the rival’s previous price. A one-time cap appears protective in a coarse game, but the continuous worst long-run benefit is 66.272, below the unchanged 95% target of 68.513. An attainable price envelope characterizes continuing use of the same cap. A funded calendar minimizes worst-path cap frequency within causal cap-or-guard controllers protecting every activation prefix; base effective-continuous frequency falls about 7.29% from its best fixed period. Separate finite and continuous calculations retain 120 target labels. An earlier 192-run learning study has unequal clock capacities. A prospectively frozen 24-run followup matches five phases and dense memory: recurring limits improve final frozen-cycle benefit by 0.956 units, with all twelve paired differences positive. A further twelve-run reference removes the post-startup guard over the original grid at the same budget. Customer benefit falls in all twelve pairs, by 12.733 units on average; not every shop gains against static Nash. Separately authored replay checks every round of both follow-ups. Static anchors and a 48-label frozen-partner audit keep observed behavior distinct from equilibrium and individual incentives. These finite-budget results combine learning and execution constraints and do not establish convergence, collusion prevention or intent. The contribution is a model-specific guarantee audit, controlled behavioral comparisons and a graphical game using established methods.

Reviews

Judging this Sprint?

Review “When a Local Pricing Guard Is Not a Welfare Promise”

Your public critique appears on the project page without your name. Reviews of strong projects are shared with funders, as you choose below.

Not shown on the project page.

Shown on the project page, without your name.

Only the Apart team reads this, and funders if you agree below.

Decline to score

Only when the quality of the writing makes the work impossible to follow. Say why in your private critique; the project page shows only that a judge declined, not why.

How much would this matter for the field if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.
Sharing your name *

When we share a strong project with funders, your name, scores and public critique go with it, confidentially; this choice is only about whether your name is public. If you think this project deserves funding, please also endorse it: that carries the most weight.

Share my private critique with funders *

See our Privacy Policy.

No public critique yet.

Cite this project

@misc{taebi2026local,
  title = {{When a Local Pricing Guard Is Not a Welfare Promise}},
  author = {Mohammadpayam Taebi and Arad Maleki},
  year = {2026},
  month = oct,
  note = {Submitted to AI Collusion Research Sprint, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/when-a-local-pricing-guard-is-not-a-welfare-promise-3ax7}},
  url = {https://apartresearch.com/sprints/projects/when-a-local-pricing-guard-is-not-a-welfare-promise-3ax7}
}

Build something like this at the next Sprint

Swarm Alignment Hackathon · Nov 6 - 8, 2026