com.tituslegaldesign.immigration.dispute
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.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | immigration.tituslegaldesign.com |
| Indexed |
Record
record · key tidProperties
assertedValue
stringWhat the disputing party says the value should be.
maxLength: 3000
Why the record is contested. factual-error = the value is wrong; outdated = it was right and no longer is; disputed-interpretation = the underlying facts are agreed but their characterization is not; missing-context = not false but materially incomplete; superseded = a later agreement replaced this one.
knownValues: factual-error | outdated | disputed-interpretation | missing-context | superseded
When this dispute was filed.
disputantRole
stringSelf-declared relationship of the disputing party to the record. Self-declared: consumers should not treat it as verified.
knownValues: subject-agency | government | legal-representative | journalist | researcher | other
evidence
arraySupporting documents, archived as content-addressed blobs in the disputing party's own repository.
maxLength: 10
field
stringWhich agreement-record field is contested, when the dispute is field-specific. Absent for disputes about the record as a whole.
maxLength: 100
resolvedBy
string · at-uriOptionally set by the DISPUTING party once satisfied, pointing at the agreementEvent that addressed the dispute. Only the disputant can write this, since the record is in their repository.
statement
stringThe disputing party's explanation, in their own words.
maxLength: 5000
AT URI of the disputed agreement record.
CID of the exact record version being disputed. A later correction by the publisher does not silently resolve this dispute; it leaves it attached to the version that was actually wrong.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
app.matakite.dispute
recordA 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.
-
An append-only changelog entry for a 287(g) agreement record. One event is written every time the sync detects a change: a new agreement, a cancellation, a field-level modification, or a data correction. Together these events form the public changelog that ICE's snapshot-only publishing omits. Record key is a TID (timestamp identifier); events are never updated or deleted. Events carry the CID of the agreement record version they describe, so a third party holding an older CAR export can verify
-
dev.cocore.compute.dispute
recordAn 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