Authorized managers of involved teams; commissioner review is an orthogonal capability.
Configured trade deadline, review, veto, and processing policy.
HELP TOPIC // trades
/trades-review-and-processing · corpus 0.1 · verified 43c1c50
Trades, review, and processing
Compose, respond to, and track a trade without guessing its boundary.
Sources
Who can use this answer.
Read the current gate
Claimed teams, eligible assets, and open trade capability.
The label carries the consequence.
Composing, proposed, countered, pending-response, accepted-pending-review, review-open, approved, rejected, canceled, vetoed, processed, expired, failed, unavailable.
Use the runtime clock
Proposal expiry/review/processing/deadline values are runtime-derived in league-local time.
Keep the right audience
Terms are visible to involved teams and configured reviewers only.
Take the next safe step.
- →
Select counterparty/assets.
- →
Review named teams and consequence.
- →
Respond/counter/withdraw while permitted.
- →
Read review/veto/processing result in activity.
Know what changes.
What happens
Accepted terms may enter review and then move named assets.
What can be undone
Proposal/response/review reversibility ends at runtime boundary; processed movement is not undone by refresh.
What you should see
Result names trade state, teams/assets, and activity receipt.
Keep context. Do not replay blindly.
Stale offer, lock, deadline, authorization, and processing failures leave rosters unchanged.
Return to Trades with form context; reread offer and never replay stale submission.
One concrete read.
Example: Accepted may remain review-open until the configured boundary; acceptance is not processing.
Runtime source: Trade config/state, rosters, locks, memberships, processor, activity.
Corpus receipt: introduced 0.1; last verified 43c1c50dfbd493b01368d2c74959eb23de098749.