wealth/docs/decisions/0060-compose-lock-on-own-ch...

17 lines
1.0 KiB
Markdown

# 0060 An analyst who can't publish sees the reason on their own channel
Status: Accepted · Area: architecture · Date: 2026-10-10 · Decided by: user · Supersedes: 0048
## Context
J09-1e draws «پیش‌بینی جدید» for a pending, rejected or suspended analyst as the locked dialog over their own channel. 0048 rendered a locked page on `/compose/*`.
## Decision
- `/compose/post` and `/compose/prediction` read the creator's standing in the browser; when publishing is blocked they replace the route with the creator's own channel and open the locked dialog there (`?locked=post|prediction`, removed once shown). A 403 on publish re-reads the standing and does the same.
- Every publish sends an `Idempotency-Key` that stays the same while the body is unchanged and is renewed after any change or `IDEMPOTENCY_KEY_REUSED`.
## Alternatives
- A locked page on the composer route (0048): a second place for the same message.
## Consequences
Published predictions can't be edited or deleted (API `PREDICTION_LOCKED`).