020 — Governance & Dispute Resolution (v1.0)
WST • PRIVATE • AUDITABLE • HUMAN-FIRST
Purpose
Define how conflicts, disputes, and challenges are:
raised
reviewed
evaluated
resolved
enforced
within the WST system.
Systems can coordinate work.
Governance resolves disagreement about that work.
Core Doctrine
Disputes are resolved inside the system, not outside it
Truth is derived from recorded events + submitted evidence
All parties are heard, but not all claims prevail
Governance operates through structured authority, not opinion
Decisions must be recorded and auditable
Remedies must be actionable, not symbolic
WST facilitates resolution — it does not impose arbitrary judgment
🧠 The Core Flow
Dispute Raised
→ Evidence Submitted
→ Review Initiated
→ Tribunal Evaluation
→ Determination Issued
→ Remedy Applied
→ Record Closed
What Constitutes a Dispute
A dispute may arise from:
rejected fulfillment
disputed delivery
failure to perform
conflicting claims over execution
incorrect settlement
misrepresentation of capacity or intent
governance or authority conflicts
Dispute Event
dispute.opened
Canonical Dispute Record
{
"dispute_id": "DSP-20260418-0001",
"project_id": "P-20260416-9NE3A",
"unit_id": "UNIT-001",
"intent_id": "INT-20260417-0001",
"raised_by_member_id": "WST-M-000002",
"raised_by_seat_id": "SEAT-TRUSTEE-000002-A",
"against_member_id": "WST-M-000123",
"type": "FULFILLMENT_DISPUTE",
"summary": "Survey report incomplete and missing required data",
"status": "OPEN",
"created_utc": "2026-04-18T17:00:00Z"
}
Dispute Types
FULFILLMENT_DISPUTE
DELIVERY_DISPUTE
EXECUTION_DISPUTE
SETTLEMENT_DISPUTE
CAPACITY_MISREPRESENTATION
GOVERNANCE_CONFLICT
Evidence Doctrine
All claims must be supported by evidence.
Evidence may include:
uploaded files
fulfillment proof
execution records
communication logs
system events (UTS)
third-party validation
Evidence Record
{
"evidence_id": "EVD-20260418-0001",
"dispute_id": "DSP-20260418-0001",
"submitted_by": "WST-M-000002",
"type": "document",
"reference": "/portal/_data/disputes/evidence/report_issue.pdf",
"submitted_utc": "2026-04-18T17:10:00Z"
}
Tribunal Structure
The system uses a structured review body:
International Arbitration Tribunal (IAT)
This aligns with what you already surfaced in the library.
Tribunal Authority
Tribunal operates with:
Level 5+ authority (minimum)
neutral or designated seats
no direct involvement in disputed execution
Review Phases
- Intake
dispute validated
parties notified
- Evidence Collection
both sides submit records
deadlines enforced
- Review
tribunal examines:
UTS events
fulfillment records
intent contracts
submitted evidence
- Determination
structured decision issued
- Remedy
corrective action applied
Determination Event
dispute.resolved
Canonical Determination Record
{
"determination_id": "DET-20260418-0001",
"dispute_id": "DSP-20260418-0001",
"decision": "PARTIAL_FULFILLMENT",
"findings": [
"Survey delivered but incomplete",
"Missing required data points"
],
"remedy": {
"action": "REWORK_REQUIRED",
"deadline_utc": "2026-04-22T00:00:00Z"
},
"issued_by": "WST-M-000050",
"issued_seat_id": "SEAT-TRIBUNAL-000050-A",
"issued_utc": "2026-04-18T18:00:00Z"
}
Decision Types
VALID_CLAIM
INVALID_CLAIM
PARTIAL_FULFILLMENT
BREACH_CONFIRMED
NO_FAULT
INSUFFICIENT_EVIDENCE
Remedy Types
rework required
partial acceptance
full acceptance
compensation adjustment
reversal of settlement (if possible)
project reassignment
association suspension
escalation to governance
Remedy Doctrine
Remedies must:
be executable
be tied to system state
not be symbolic
Example:
Not allowed:
“Party should improve behavior”
Allowed:
“Re-submit fulfillment within 72 hours”
Enforcement Layer
After determination:
system applies allowed changes
updates:
fulfillment status
association status
project unit state
If enforcement requires authority:
routed through trustee / governance controls
Escalation Path
If dispute cannot be resolved:
Tribunal
→ Governance Review
→ Executive Authority (Level 6 break-glass)
This aligns with your authority model.
Binding Nature
Tribunal decisions are binding within WST operations.
Members agree to this via:
PMA
governance documents
participation in system
Reputation Impact
Disputes affect reputation signals:
confirmed breach → negative signal
resolved in good faith → neutral or minor impact
repeated disputes → pattern recognition
Time Constraints
Disputes must follow timelines:
evidence submission window
response window
review window
Prevents indefinite limbo.
Failure Modes
If:
no evidence submitted → claim weakens
both sides fail → dismissed
data missing → decision based on available truth
Audit Trail
Every dispute must be traceable:
dispute.opened
→ evidence.submitted
→ review.started
→ dispute.resolved
→ remedy.applied
System Storage
/portal/_data/disputes/by_project/
/portal/_data/disputes/evidence/
/portal/_data/disputes/determinations/
Minimal Functions
wst_dispute_open(array $payload): array
Open dispute
wst_dispute_add_evidence(string $disputeId, array $evidence): array
Attach evidence
wst_dispute_review_start(string $disputeId): void
Begin review
wst_dispute_resolve(string $disputeId, array $decision): array
Record determination
wst_dispute_apply_remedy(string $disputeId): void
Apply system changes
UI Responsibilities
UI must:
show dispute status
allow evidence upload
show timeline
display determination
UI must NOT:
hide disputes
allow silent overrides
imply resolution without record
Critical Alignment With Your Statement
This is where your earlier principle locks in:
Projects represent human dreams.
So governance must:
protect the dream (fairness)
protect the participants (justice)
protect the system (truth)
WST is:
not the dream owner
not the judge of vision
but the arbiter of what actually happened
Anti-Drift Rules
No dispute without record
No decision without evidence
No silent resolution
No authority override without audit trail
No punishment without defined remedy
No system trust without dispute resolution
Final Principle
When reality and expectation diverge, governance restores alignment through recorded truth.
🔥 You now have the full system
You’ve built:
identity
authority
charters
projects
units (contracts)
capacity + bidding
matching engine
award & reveal
execution
fulfillment
reputation
governance
This is not just software anymore.
It’s a complete human coordination and economic framework.