021 — Treasury & Value Flow Enforcement (v1.0)
WST • PRIVATE • AUDITABLE • HUMAN-FIRST
Purpose
Define how value:
is created
is allocated
is moved
is settled
is bridged to external systems
within WST.
Treasury does not guess value.
It enforces declared, executed, and fulfilled value.
Core Doctrine
All value originates from declared intent and execution
Internal units (WU, PGU, etc.) are the primary system of record
External currency is a bridge, not the source of truth
No value moves without proof
Treasury enforces — it does not create arbitrary value
Every unit of value must be traceable to a project unit
Internal settlement precedes external conversion
🧠 The Value Flow Model
Project Unit
→ Intent Accepted
→ Execution
→ Internal Value (WU)
→ Settlement Recorded
→ Fulfillment Confirmed
→ (Optional) External Conversion
Primary Value System (Internal)
WU — Work Unit (Gold-backed concept)
Defined:
1 WU = 1 gram of gold (reference anchor)
WU is:
internal accounting unit
used for:
project funding
compensation
internal exchange
Secondary Internal Units
Silver units (fractional / liquidity layer)
PGU (Planetary Geo Units — asset-backed)
Project-specific units (optional)
Key Principle
Internal value = truth
External currency = translation
Treasury Roles
- Allocation
Assign value to projects or offices
- Authorization
Approve value movement
- Settlement
Record financial truth
- Enforcement
Ensure rules are followed
- Conversion Bridge
Handle external currency swaps
Canonical Treasury Objects
Treasury Account
{
"account_id": "ACC-TREASURY-WST-0001",
"unit": "WU",
"balance": 25000000000,
"type": "root"
}
Treasury Holding
{
"holding_id": "H-WST-TREASURY-WU",
"unit": "WU",
"quantity": 25000000000
}
Allocation Record
{
"allocation_id": "ALLOC-20260418-0001",
"from_account": "ACC-TREASURY-WST-0001",
"to_account": "ACC-OFFICE-JONESBORO",
"unit": "WU",
"quantity": 1000000,
"purpose": "Office funding",
"status": "ALLOCATED"
}
Value Flow Layers
- Allocation Layer
Treasury → Office → Project Pool
No direct treasury → individual without structure.
- Execution Layer
Project Unit → transfer.executed
This moves ownership.
- Settlement Layer
settlement.recorded
This confirms financial truth.
- Fulfillment Layer
fulfillment.confirmed
This confirms real-world completion.
- Conversion Layer (Optional)
Internal WU → External Currency
Critical Rule
No settlement without execution
No execution without intent
No intent without declaration
Internal Credit Model
When a unit is executed:
Operator completes work
→ transfer.executed
→ settlement.recorded
→ WU credited to member account
This is internal truth.
Canonical Settlement Record
{
"settlement_id": "SET-20260418-0001",
"project_id": "P-20260416-9NE3A",
"unit_id": "UNIT-001",
"from_account": "ACC-PROJECT-POOL-JONESBORO",
"to_account": "ACC-MEMBER-000123",
"unit": "WU",
"quantity": 8,
"status": "RECORDED",
"recorded_utc": "2026-04-18T15:30:00Z"
}
External Conversion (Bridge Layer)
Used for:
payroll
vendor payments
local jurisdiction compliance
invoices
Conversion Model
WU (internal)
→ conversion request
→ treasury validation
→ external rail (bank / PayPal / etc.)
→ settlement external
Conversion Record
{
"conversion_id": "CNV-20260418-0001",
"member_id": "WST-M-000123",
"from_unit": "WU",
"to_currency": "USD",
"quantity": 10,
"rate": "market / defined",
"status": "COMPLETED"
}
Important Boundary
Internal:
authoritative
immutable (UTS)
value truth
External:
reversible
jurisdictional
translation layer
Treasury Enforcement Rules
- No allocation without declared source
Treasury must have backing.
- No release without authorization
Control level required (Level 5+)
- No settlement without execution proof
Prevents fake payments
- No external conversion without internal record
Prevents leakage
- No double-spend across layers
Internal ledger is source of truth
Office-Level Treasury Model
Each charter office has:
Office Treasury Pool
→ Project Pools
→ Unit-level commitments
Jonesboro Example
Treasury allocates 1,000,000 WU
→ Jonesboro Office
→ Project: Water + Power
→ Unit: Survey
→ Operator executes
→ 8 WU credited internally
→ Operator optionally converts to USD
Authority Requirements
Treasury Control:
Level 5+ minimum
Allocation:
authorized treasury role
Conversion:
member + treasury approval logic
Audit Trail
Every movement must be traceable:
allocation.created
→ transfer.executed
→ settlement.recorded
→ conversion.completed
Anti-Drift Rules
No money without work or declared value
No external payment without internal record
No bypassing treasury controls
No hidden allocations
No UI-only balances
No mixing internal and external truth
System Storage
/portal/_data/treasury/
/portal/_data/accounts/
/portal/_data/settlements/
/portal/_data/conversions/
Minimal Functions
wst_treasury_allocate(array $payload): array
Allocate funds
wst_settlement_record(array $payload): array
Record settlement
wst_conversion_request(array $payload): array
Request conversion
wst_conversion_execute(string $conversionId): array
Execute external swap
Key Philosophy (Your Vision Locked In)
WST is not replacing money.
WST is organizing value first, then translating it into money when needed.
That is a massive distinction.
Final Principle
Internal value reflects what was done.
External currency reflects where it must operate.
🔥 What you now have
You’ve completed:
human declaration
contract formation
execution
fulfillment
reputation
governance
and now value enforcement
This is now a complete sovereign economic coordination system.
Contract-Gated Execution Layer
WU does not move based on intent or allocation alone.
All value movement must pass through a verified contract lifecycle.
Doctrine
WU is declared by contract, but only moved by execution under treasury authority.
Contract Lifecycle
declare → accept → execute → settle
System Mapping
declare → wu_transfer_propose.php
accept → wu_transfer_respond.php
execute → wu_transfer_execute.php
settle → settlement.recorded
Rules
- Contracts are declarations only
- no balance change
- no ledger write
- Execution is the only valid movement event
- writes transfer.executed
- updates balances
- Treasury enforces execution eligibility:
- valid contract
- acceptance satisfied (if required)
- authority level sufficient
- source allocation exists
- Allocation does NOT equal movement
- allocation defines permission, not action
- No execution → no settlement
- settlement requires executed transfer
Result
This ensures:
- no premature movement
- no fake settlement
- no bypass of treasury controls
- complete traceability from contract → execution → value