Community access / Message evidence
Cancellations, expiry and unresolved Discord instructions
Link withdrawals to originals and preserve ambiguous statuses without inventing exits or profitable outcomes.
Withdrawal is an instruction event
A cancellation identifies a change in what the author intends under the source's stated workflow. It is not automatically an actual account close or realised profit. Link it to the original and retain the member's observed access and receiving clock. An expiry boundary can also make an item unavailable for a task without any cancellation event. Keep those concepts separate. A review should not guess which original a short withdrawal refers to merely because another post recently mentioned a similar symbol or a favourable price move.
Predeclare overlapping classifications
An original can have more than one raw observation, such as a late receipt and a later cancellation. The counting policy needs a priority that creates disjoint subtraction buckets; keep both notes in the event journal. Otherwise the same item can be removed twice from the received subset. The calculator rejects late plus cancelled counts greater than unique received, but it cannot verify that the user's classifications are true. Record the policy and relationship identities before reviewing outcomes, and do not reinterpret them to improve a desired coverage or performance number.
Unresolved is a legitimate status
If the parent is absent, access is lost or the chronology is unsupported, keep the stronger finding unresolved. A summary saying trade closed does not establish a subscriber's quantity, order status or fill. A screenshot of a target or invalidation level cannot supply the missing price path. An evidence journal can still be useful by naming the exact object needed to continue. The absence of a record is not permission to invent a win, loss, refund entitlement or proof of misconduct just to make the comparison appear decisive.
A bounded task conclusion
For a message study, report the original population and statuses under the declared interval. For actual account outcomes, obtain the independent execution record. The fictional packet leaves account results entirely absent and retains the cancelled original among all eight. Its result is a coverage demonstration, not an instruction to trade or a portfolio calculation. A useful consumer assessment can identify an unlinked withdrawal or a clear expiry while leaving the source's complete strategy and account performance unvalidated. Keep the same limitation in the machine export.
Completed fictional member-view case
Fictional case: O6 has an explicit linked cancellation and remains in the eight-original packet. A different short withdrawal has no parent, so the journal records it as an unresolved event without creating another original or guessed account exit. The declared priority makes late and cancelled subtraction buckets disjoint. No market outcome or actual seller is involved. The final packet counts one cancelled received original and preserves the unrelated ambiguity, avoiding both double subtraction and a fabricated successful execution.
| Object | Record | Bounded finding |
|---|---|---|
| O6 | Linked cancellation | Original remains in population |
| Unlinked withdrawal | Parent unknown | Event unresolved |
| Account result | Absent | No close or profit inferred |

Primary references and scope
Public documentation read 13 October 2026. It supports the stated mechanism, not a bought room, tested member device or the invented case.