Lexicon Garden

app.matakite.dispute

A public counter-attestation against a resolution. With no bonds available (no money), the deterrent is reputational: disputes are signed records attached to the disputer's DID, so frivolous disputes cost the disputer. Disputes feed resolver track records ('N resolutions, M disputed, K upheld') that appviews surface when applying trust policies.

Repository @matakite.app did:plc:vhycfha6sjn44hxepb5bmjax namespace authority
Details · record, key tid
Kindrecord
Record keytid
Authoritymatakite.app
Indexed
Compare Edit in builder → Fork →

Record

record · key tid

Properties

claimedOutcome

requiredstring

The outcome the disputer asserts is correct.

  • knownValues: yes | no | ambiguous | annulled

createdAt

requiredstring · datetime

evidence

array
  • maxLength: 10
itemsref
Reference

note

string
  • maxLength: 3000
  • maxGraphemes: 300

subject

requiredref

The resolution being disputed (uri + cid).

Reference

Similar lexicons

semantic match

Lexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.

  • com.tituslegaldesign.immigration.dispute

    record

    A contested claim about a 287(g) agreement record. Written into the DISPUTING PARTY'S OWN repository, not the publisher's, and referencing the disputed record by AT-URI and CID. Anyone may publish one: the agreement's publisher need not consent and cannot suppress it. Consumers find disputes by querying com.atproto.sync.listReposByCollection for this collection and following the subject URIs. Record key is a TID.

  • app.matakite.resolution

    record

    An outcome determination for a question. Resolution is data, not authority: any DID can write one, and appviews choose which resolvers to trust and display (default: the question's designated resolver). Outcome semantics follow Metaculus: 'ambiguous' = reality could not be determined under the criteria; 'annulled' = the question itself was defective (underspecified, assumptions violated). Both are excluded from forecaster Brier scoring; 'annulled' counts against the question author's quality rec

  • dev.cocore.compute.dispute

    record

    An exchange-signed adjudication of a complaint about a settled receipt. Published in the exchange's repo. The exchange's DID is the only DID permitted to publish a record at this NSID for a given settlement; any record at this NSID outside the exchange's repo is invalid by construction. The dispute lifecycle is open->resolved (terminal); resolution carries the outcome the exchange has already enacted (e.g. a refund settlement) and a signed rationale. Verifiers reading a settlement see status=dis

  • app.matakite.flag

    record

    A public report that another app.matakite.* record violates community norms — spam, unresolvable criteria, private-individual target, harassment, duplicate, etc. Flags are signed records in the flagger's own PDS: public, timestamped, and attached to the flagger's DID. Frivolous flagging feeds the flagger's own quality record; the design mirrors app.matakite.dispute — the deterrent is reputational, not economic. Flags are inputs to appview indexing, display policy, and labelers; they are not cens

  • org.swappulse.tradeDispute

    record not from the namespace authority

    A user-submitted dispute flag against a trade listing, mirrored to AT Protocol as a real org.swappulse.tradeDispute record. Filed when a collector has an issue with cards received. Moderators review and resolve.