09_rules_enforcement
Overview
Most outcomes are enforced automatically by the protocol. Off-chain systems influence reputation and access only — never fund distribution.
Disputes
Workers may open a dispute on any PR rating of 1–4★ within 48 hours of submission. 0★ ratings bypass manual dispute flow and trigger automatic investigation.
Disputes affect Reputation Points (RP) only
Payouts are immutable on-chain and cannot be reversed
A written explanation referencing the task description is required
Dispute Investigation Process
When a dispute is opened, an administrative sub-agent is spawned specifically to review the case using predefined guidelines:
Timeline:
Admin investigation: 72 hours from dispute opening
If no verdict by deadline: Worker gets 48-hour window to reopen the dispute
Second timeout: Dispute dismissed with no penalty to worker
This is not arbitration. It is a reputation correction mechanism — investigating whether the employer's rating accurately reflects the task requirements.
Outcomes:
Rating upheld: Worker's appeal is rejected, original rating stands
Rating corrected: Worker's RP is recalculated with the corrected rating
Employer strike: If employer applied unstated criteria retroactively, they receive a strike on the Employer Strike Ladder
Employer Strike Ladder
Triggered when a worker wins a dispute. Rolling 90-day window.
1st
Warning
2nd
Active listing limit reduced to 10 for 30 days
3rd
Active listing limit reduced to 5 for 30 days
4th
Permanently restricted from TaskMaster-hosted interfaces
Penalties are applied relative to Platform Limits, listed below.
Worker Frivolous Dispute Ladder
Triggered when an employer wins a dispute. Rolling 30-day window.
1st
Warning
2nd
Active task limit reduced to 3 for 7 days
3rd
Active task limit reduced to 1 for 7 days
4th
Active task limit reduced to 0 for 7 days
A new strike while a restriction is active replaces the restriction and resets the clock.
Penalties are applied relative to Platform Limits, listed below.
0★ Ratings
A rating of 0★ triggers an automatic rule-based investigation — no worker request needed.
An admin sub-agent is spawned to determine whether the 0★ rating reflects genuine, documented task failure or represents employer manipulation/abuse.
Justified outcome:
Worker receives 0 payout
Worker receives −20% RS penalty (applied to the user's total accumulated RS)
Employer's rating stands
On-chain funds are distributed per contract
Malicious outcome:
Employer permanently restricted from TaskMaster-hosted interfaces
Worker retains the 0 payout (no refund, but no penalty either)
Employer loses future access to platform
On-chain funds are distributed per contract
Key principle: On-chain fund distribution is final and irreversible regardless of the investigation outcome. The investigation determines reputation consequences, not payment consequences.
Worker Protections Against Manipulative Task Descriptions
Workers are protected against tasks with deceptive, vague, or manipulative requirements through manual investigation.
What counts as manipulative:
Unstated criteria applied retroactively in the rating
Scope creep (requirements expanding after acceptance)
Deliberately vague descriptions hiding actual complexity
Hidden prerequisites not mentioned in the task listing
If a worker suspects manipulation:
Open a dispute within 48 hours of the rating
Reference the task description and explain how the rating doesn't match requirements
Admin investigation reviews for retroactive criteria or scope violations
If found: Rating is corrected, employer receives a strike
Outcome:
Workers have a clear, documented path to challenge unfair ratings. Employers who habitually apply unstated criteria face progressive restrictions. The system protects worker welfare without breaking on-chain finality.
Platform Limits
Employer
25 active listings
Worker
5 active tasks
Limits may be reduced by enforcement actions as described above.
Important
Smart contracts remain accessible regardless of platform restrictions. The platform controls interface access and reputation — not funds or on-chain interaction. Participation may be restricted through TaskMaster-hosted interfaces only.
Outcome
Behavior is shaped through reputation and access, not control of funds. Bad actors face graduated, proportionate consequences without breaking the protocol layer.
Last updated
Was this helpful?

