Suggested
The author submitted an exact post URI and CID.
Captured V0 evidence · not a current feed
This one actually touched ATProto.
A disposable account submitted a real author-owned post, the community actor admitted it, and later removed it from the community view. The PDS signed those repository records; the observer independently verified the repository proofs before projecting them.
Historical snapshot. Captured
2026-08-15T05:18:50.144497Z. Serving it today does not prove that no newer
repository state exists.
V0-X7-WRITE-SMOKE run-v0-x7-2026-08-15-02
at://did:plc:b53udqv47g2dayvpstzdefpq/app.bsky.feed.post/bqoofp2b4mv5pbafyreicib6x7dlxdl64y33wdywd3gw7ech3s6pqpdvwtai6aknqzsqnzr4What happened
The retained lifecycle
Added
The community actor signed an admission for that occurrence.
Source checked
The observer verified the exact source record.
Removed
The community stopped projecting it; the source was not deleted.
Why trust the admission?
A bounded answer, not a magic badge.
The admitted occurrence is the exact URI/CID pair below. The accepted admission event carries a verified repository-proof outcome for the community actor. That establishes the observed signed record—not community legitimacy, membership, or a universal right to moderate.
at://did:plc:b53udqv47g2dayvpstzdefpq/zone.neutral.community.admission/admit-7f024ab1227580de733032a8370324fec97c0c8e7a27ee822a24441a4471feb8bafyreierr4wzdcq2jzlz4if3e3hio2js5tidh7uydngzq4uaodkcco5n7e
The observer also retained 2 transport-only delivery result(s) that did not qualify as authority. They remain visible in the JSON instead of being rewritten as success.
What is real here
- public non-production ATProto records
- PDS-signed repository commits
- independent DID/signature/MST proof verification
- the retained removal
What is not claimed
- current repository state
- complete history
- membership or standing
- governance legitimacy
- production readiness
Inspect the exact JSON receipt Check the deliberately historical health status