Styxis
Company
Knowledge

Keep a DSA dispute traceable so the user need not explain it again

Separate eligibility, decision and implementation records across platform-to-ODS handoffs.

The burden of a broken case link

A case can move between organisations while losing the relationship to its original decision. The user may then be asked to explain the same circumstances again. A platform decision, an ODS outcome and implementation are different events. Truthound can check their prepared dates and references, not decide the dispute.

The October dialogue

The Commission's October 20, 2026 dialogue with platforms and Digital Services Coordinators addressed DSA out-of-court dispute settlement. Its October 21 account separates information exchange, eligibility, fees and implementation. The dialogue is not evidence that every platform's process has already improved.

Can the record return to the original decision?

Preserve identifiers for the original moderation decision, application, ODS case and implementation record. Different organisations may use different numbers, requiring an evidenced mapping. Similar names or dates should not merge different people's cases. Keep an unresolved mapping explicitly unresolved.

Complete has several meanings

Complete can mean receipt, review, delivery of a decision or implementation. One state cannot substitute for all four. An ODS decision's existence should not fill the platform's implementation field automatically. Each stage needs its own evidence and owner.

The handoff Truthound can check

Truthound Core Python SDK 3.3.4, operating on a prepared Polars table, provides DateOrderValidator for defined date pairs and ForeignKeyValidator for supplied child/parent case keys. Owners must specify legitimate exceptions such as reopening and correction. These checks cannot infer legal eligibility.

Compare the existing predicate

An existing Pandera 0.35.0 pandas predicate can keep the handoff rules. Compare an application without its original decision, a decision without implementation evidence and a reopened case. The useful test is where missing evidence returns for action, rather than whether a file merely has valid fields.

A reopened case is not automatically duplicate

A reopened case may legitimately point to the same original decision. Deleting it as a duplicate can erase the user's follow-up; counting every processing attempt as a new case can inflate activity. Separate case identity from processing-attempt identity before choosing a metric.

Assign the missing-link question

Assign someone to investigate the missing link before asking the user to start again. Information not yet produced and information not shared require different actions. The mapping and processing history should make that distinction visible.

Explain the next step to the user

The useful user explanation states the current stage and outstanding confirmation, rather than exposing an internal complete flag. Technical completeness supports that explanation. Keep validation focused on preserving the handoff without automating the user's rights or the dispute's outcome.

Conditions

Establish the lawfully handled case population, stage definitions and responsible parties first.

Alternatives

Compare an existing Pandera 0.35.0 pandas case predicate against the same handoff exceptions.

Limitations

  • Date and reference checks do not decide a dispute's merits or eligibility for ODS review.

Evidence

Event checked
Subject checked
Modified