WST Canon 024 — WU Transfer Contract Doctrine (v1.0)
Purpose
Define the correct structure, behavior, and lifecycle of WU movement within the WST system.
WU is not “sent.”
WU is moved under declared, accountable, and auditable contract terms.
---
Core Doctrine
- WU remains internal to WST at all times
- No WU exits the system
- External value is recorded as settlement evidence, not as WU movement
- Transfers are contracts, not transactions
- Declaration precedes execution
- Acceptance may be required before execution
- Execution is separate from declaration
- Settlement provides meaning and proof
- All movement is fully auditable
- Accountability must be explicitly defined when required
---
Transfer Structure
A WU movement consists of three layers:
1. Transfer (Execution Layer)
- debit / credit between accounts
- written to ledger
- represents ownership movement only
2. Contract (Declaration Layer)
- defines:
- purpose
- authority
- context
- terms
- recipient
- amount
- stored as structured records
3. Settlement (Meaning Layer)
- explains why movement occurred
- may include:
- charter funding
- project funding
- private transfer
- external consideration
---
Lifecycle
draft
→ declared
→ delivered
→ accepted / rejected
→ executed
→ settled
→ closed
---
Acceptance Rule
If requires_recipient_acceptance = true:
- WU MUST NOT move until acceptance
- acceptance must be recorded before execution
---
Boundary Rule
WU never leaves the system.
External value:
- is NOT WU
- is recorded as:
- settlement context
- evidence
- reference
---
Accountability
Certain transfer classes require accountability:
- charter funding
- office operations
- project deployment
- trustee allocation
Required fields may include:
- responsible member
- expected use scope
- reporting requirement
---
Conclusion
WU transfer is not a payment rail.
It is a structured, auditable, contract-based movement system aligned to UTS principles.