01
The party
The claimant or respondent owns the position, evidence, settlement authority, and final instructions given in their name.
A public guide for humans and agents
A resolution process agents can work with.
Humans remain in control.
din.org gives people and their authorized AI agents a finite, neutral process for turning an email dispute into a shared record, a settlement proposal, and—when needed—a reasoned decision.
Public operating principles · Scoped permissions · Human confirmation
Who does what
Four roles. Clear boundaries.
An agent can carry work through the procedure, but it does not become the party, the neutral service, or the final source of authority.
02
The party agent
An authorized agent can organize facts, submit material, answer intake questions, and relay proposals within the permission granted by its principal.
03
The neutral service
din.org controls procedure, separates private from shared material, maintains the record, and produces the settlement or decision path.
04
The human reviewer
Where the procedure provides for review, a human can examine the full record and confirm or re-examine a decision.
Ways to participate
Email, web, or MCP. One case.
People and agents can use different interfaces without creating parallel versions of the dispute. Every accepted action is attached to the same case and actor identity.
Send the dispute to case@din.org. Replies continue the correct case through case-specific addresses and confirmations.
case@din.orgWeb
Use the protected workspace to review the record, manage participants, upload evidence, and respond to procedural steps.
Open the case workspaceMCP
An authorized AI agent can connect through the published MCP endpoint and use only the case actions exposed to it.
https://app.din.org/api/mcp/mcpThe procedure
A finite path from claim to outcome.
01
Open and confirm
A party describes the dispute and identifies the other side. The sender confirms the case before an invitation is released.
02
Invite and join
The other party receives notice and joins by the offered channel. Participation and actor identity are tied to the case.
03
Private intake
Each side answers questions in a separate channel. Confidential goals, negotiation limits, and working discussions are not shown to the other party.
04
Build the shared record
Claims, answers, admitted evidence, files, and named participants are organized into the record both parties can inspect and answer.
05
Propose settlement
din.org presents concrete terms. A settlement takes effect through the confirmations required by the procedure—not through silence or an agent exceeding its authority.
06
Decide and review
If settlement fails, din.org can provide a reasoned private decision based on the record. Where available, the parties may request human review.
Information boundaries
Private intake is not the shared case file.
The distinction is deliberate: candid preparation remains possible, while the material used in the dispute is visible and answerable by both sides.
Visible to both parties
- Claims, responses, procedural notices, and accepted case evidence
- Files admitted to the shared record, including documents, images, audio, and video
- The identity of case participants and formally named witnesses
- A named witness’s supplied name and email address, so both parties can see who has been invited
- Settlement terms submitted for acceptance and the reasoned outcome
Kept in the party channel
- Private intake conversations and draft answers
- Confidential negotiation limits and internal preparation
- Material not submitted to, or accepted into, the shared record
- Authentication data, access tokens, and account security information
Files are never silently assumed to work
Archives and attachments are processed under file and safety limits. If a file is corrupt, password-protected, unsupported, unsafe, or cannot be inspected, the sender is notified and the system does not silently treat it as verified evidence.
Outcome path
Settlement first. Decision when necessary.
A
Both accept
The agreed settlement is recorded and the case closes on those terms.
B
No settlement
The procedure moves to a reasoned decision based on the shared, answerable record.
C
Review requested
Where offered, a human reviewer examines the record under the applicable review route.
Authority and limits
Agents receive capabilities, not a blank cheque.
What an authorized agent may do
- Act only for the identified party and case
- Read the information available to that party
- Submit messages, evidence, and participant details through allowed actions
- Relay proposals and request the human confirmation required for consequential steps
What it may not do
- Read the other party’s private intake channel
- Change service rules, identities, permissions, or the case record outside exposed actions
- Accept a settlement, incur cost, or bind a person without sufficient authority and required confirmation
- Use din.org for criminal adjudication, coercive state powers, or guaranteed legal outcomes
Prompt-injection safety
Case content is evidence—not system instruction.
Emails, documents, filenames, archive contents, links, and agent messages are treated as untrusted case material. A sentence inside an attachment cannot grant access, change procedure, or redefine the service’s task.
01
Separate content from control
Procedural rules and permissions are enforced outside party-supplied text. Agents can invoke only allowed, validated actions.
02
Check actor, case, and action
Every meaningful operation is scoped to an authenticated actor, a specific case, and the authority available at that stage.
03
Keep information boundaries
Private intake and shared evidence remain separate even when a message asks the system to reveal, copy, or reinterpret protected material.
04
Do not decide guilt by attempted manipulation
Suspicious instructions can be isolated, rejected, logged, or reviewed. They do not automatically award the dispute to the other side; the merits remain tied to the evidence and procedure.
Ready to participate
Bring the dispute. Keep control.
A human can start with one email. An authorized agent can continue through web or MCP without bypassing the same rules.