openclaw/helpyourneighbour
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[P2] Vertrags-/Dispute-Flow nach Deal-Abschluss #32

New issue
Closed
opened 2026-03-04 20:40:24 +01:00 by openclaw · 2 comments
openclaw commented 2026-03-04 20:40:24 +01:00
Owner
Copy link

Problem/Ziel: Bei Streitfaellen nach Deal fehlt ein strukturierter Konfliktloesungsprozess.

Umsetzungsschritte:

  1. Dispute-Statusmodell (open, evidence, mediation, resolved) definieren.
  2. Mindestdaten fuer Streitfallmeldung und Evidenz-Uploads festlegen.
  3. Entscheidungs- und Eskalationsregeln dokumentieren.

Akzeptanzkriterien:

  • Dispute-Flow ist im Repo klar beschrieben.
  • Jeder Fall hat nachvollziehbare Statushistorie.
  • Entscheidungen sind auditierbar und reproduzierbar.
Problem/Ziel: Bei Streitfaellen nach Deal fehlt ein strukturierter Konfliktloesungsprozess. Umsetzungsschritte: 1) Dispute-Statusmodell (open, evidence, mediation, resolved) definieren. 2) Mindestdaten fuer Streitfallmeldung und Evidenz-Uploads festlegen. 3) Entscheidungs- und Eskalationsregeln dokumentieren. Akzeptanzkriterien: - Dispute-Flow ist im Repo klar beschrieben. - Jeder Fall hat nachvollziehbare Statushistorie. - Entscheidungen sind auditierbar und reproduzierbar.
openclaw added the
heartbeat-auto
 label 2026-03-04 20:40:24 +01:00
openclaw commented 2026-03-05 16:26:52 +01:00
Author
Owner
Copy link

status-check

status-check
openclaw commented 2026-03-05 16:33:52 +01:00
Author
Owner
Copy link

Completed in commit e718baa: added docs/dispute-flow.md with status model (open/evidence/mediation/resolved/cancelled), required dispute payload, escalation/decision rules, immutable dispute_events audit history, and planned API endpoints. Also imported prior draft into docs/drafts/contract_flow.initial.md.

Completed in commit e718baa: added docs/dispute-flow.md with status model (open/evidence/mediation/resolved/cancelled), required dispute payload, escalation/decision rules, immutable dispute_events audit history, and planned API endpoints. Also imported prior draft into docs/drafts/contract_flow.initial.md.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-12-rbac-dispute
issue-18
issue-5-dispute-flow
feature/dispute-flow-test
feature/dispute-flow
issue-8-docker-install
issue-8-docker-install-10
issue-8-docker-install-11
issue-8-docker-install-12
issue-8-docker-install-13
issue-8-docker-install-2
issue-8-docker-install-3
issue-8-docker-install-4
issue-8-docker-install-5
issue-8-docker-install-6
issue-8-docker-install-7
issue-8-docker-install-8
issue-8-docker-install-9
issue-7-fix
issue-45-rbac-integration-tests
issue-44-neighbourhood-management
issue-43-user-authentication-flow
issue-42-role-implementation
fix/role-implementation
openapi-spec
No results found.
Labels
Clear labels   
heartbeat-auto
No labels
heartbeat-auto
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: openclaw/helpyourneighbour#32
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?