# #014

#### December *5, 202&#x35;**:-*** Admin Tooling Expansion & Dispute Lifecycle Foundations

### Purpose

To improve platform integrity and transparency through enhanced admin interfaces, dispute lifecycle tracking, and match rule configurability for advanced tournament customization.

***

### Key Highlights

**🛠️ Admin Dashboard Upgrade**

* Replay viewer now supports multi-speed review, move-by-move navigation, and flag annotation.
* Admin audit logs added: records every manual match override, dispute verdict, and flag dismissal.
* Mod actions are now tied to specific user sessions, allowing traceability and rollback if needed.

**⚖️ Dispute Lifecycle Infrastructure (Alpha)**

* Initial schema drafted for user-submitted match disputes: includes timestamps, evidence links, and resolution status.
* Backend supports time-limited appeal windows and admin assignment queues.
* Notifications now sent to users when disputes are received, updated, or closed.

**⚙️ Custom Match Rules Support (Prototype)**

* Tournament config expanded to allow stake minimums, turn timers, win conditions, and rule modifiers.
* Ruleset validation hooks stubbed in both frontend and smart contract layer.
* Admin UI for rule preset creation undergoing UI/UX testing.

**📊 Trust Score Logging & Analytics**

* Trust score model now logs decay over time, admin interventions, and referral quality weighting.
* Decay logic encourages continued fair play post-flag resolution.
* Admin dashboard supports historical trust timeline review per user.

***

### Why It Matters

* Robust dispute handling fosters trust in Tapzi’s fairness model, especially with higher stakes.
* Custom rules open the door for event diversity and community-hosted formats.
* Auditability protects both players and moderators in edge cases.
* Real-time analytics empower proactive moderation and reward honest participation.

***

### Open Issues

* Dispute escalation and reassignment logic not yet automated.
* Custom match rules are not enforced on frontend (validation is backend-only for now).
* Some audit logs not showing correct timezones across admin panel views.

***

### Fixed

* Match replay viewer now properly resumes after pause/seek on mobile.
* Stake validation bug fixed for custom tournaments—now enforced consistently server-side.
* Admin actions now emit system logs for downstream alerting and compliance review.

***

### Next Steps

* Complete frontend enforcement of custom match rules.
* Integrate dispute tracking into user dashboard for transparency.
* Add basic resolution metrics to trust score audit feed.
* Begin work on moderator performance dashboard with verdict review outcomes.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tapzi.io/tapzi-dev-release/014.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
