Exchange Moderation & Admin Architecture

DigiEmu Exchange moderation is enforced by the server-side API. The admin page is a user interface, not the security boundary.

Roles

Exchange accounts use two v1 roles:

member
admin

New accounts remain member by default. An administrator must be promoted explicitly in D1.

Reports

Authenticated members can report a published question or answer with a short reason.

A report records:

reporter;
target type;
target identifier;
reason;
status;
creation time;
resolving administrator and time when resolved.

A member can have only one open report for the same target.

Moderation

Administrators can change a question or answer between:

published
hidden

Public question and answer APIs already return only published content, so hidden content disappears from the public Exchange without being deleted from D1.

Moderation evidence

Admin actions append an entry to exchange_moderation_events.

The event records:

administrator;
target type;
target identifier;
action;
optional reason;
timestamp.

The v1 application exposes no API to rewrite or delete moderation events.

Security boundaries

Implemented in v1:

authenticated reporting;
server-side admin-role enforcement;
same-origin checks for report and moderation writes;
prepared D1 statements;
per-user report-rate limit;
hidden rather than destructive moderation;
append-only moderation-event writes through the application API.

Not implemented yet:

multi-level moderator roles;
moderator assignment UI;
automated spam classification;
Turnstile or CAPTCHA;
appeal workflow;
user suspension or banning;
legal takedown workflow;
24/7 moderation or response-time commitments.

The presence of an admin dashboard does not imply continuous human monitoring.