WSF Reference Examples

Canonical reference applications demonstrating WSF semantics in action.

This repository (wsf-examples/) contains worked examples that show how WSF semantics are applied. All examples use the canonical enterprise OTCHERE Inc and the canonical individual Kwesi. The example enterprise name is for reference.

---

Repository Structure

wsf-examples/
├── README.md (this file)
├── enterprise/        ← OTCHERE Inc canonical enterprise model
├── digital-twin/      ← OTCHERE DC-01 data center digital twin
├── simulation/        ← Order fulfillment state/event simulation
├── state-event/       ← State transition patterns
├── capability/        ← OTCHERE capability catalogue
├── query/             ← Example semantic queries
└── validation/        ← Example semantic validations

---

Canonical Enterprise Model

enterprise/otchere-inc.md ; the authoritative reference for how a WSF-compliant enterprise is modeled.

Includes:

• OTCHERE Inc (Organization entity)
• Kwesi (Person entity, multiple Roles)
• Capabilities (Order Fulfillment, Customer Service, Financial Planning)
• Systems (OTCHERE DC-01)
• Relationships (has-part, operates, possesses)

---

Digital Twin Example

digital-twin/otchere-dc-01.md ; demonstrates the Digital Twin pattern from CR-WSF-17 Rev.1 §16.

Entity Type: Data Center
   ↓
Entity Instance: OTCHERE DC-01
   ├── Identity
   ├── State (operational condition)
   ├── Events (historical occurrences)
   ├── Relationships (parent org, components, customers)
   ├── Capabilities (compute, storage, network)
   ├── Context (organizational, geographic)
   ├── Time (creation date, maintenance windows)
   └── Space (physical location, network location)

---

Simulation Example

simulation/order-fulfillment.md ; demonstrates the Simulation pattern from CR-WSF-17 Rev.1 §17.

Initial State: Order = Pending
   ↓
Event: Payment Received
   ↓
Transition: Pending → Paid
   ↓
Resulting State: Order = Paid
   ↓
Event: Order Fulfilled
   ↓
Transition: Paid → Fulfilled
   ↓
Resulting State: Order = Fulfilled

Capability vs Actual Event distinction preserved:

• Capability: OTCHERE has Order Fulfillment Capability (always true when capability exists)
• Event: Order #12345 was fulfilled on 2026-08-29 (specific occurrence)

---

Example Convention

All examples in this repository (and across all WSF repos) MUST use:

• Enterprise: OTCHERE Inc (or OTCHERE)
• Individual: Kwesi
• System: OTCHERE DC-01 (data center)
• System: OTCHERE-CRM-01 (CRM system)

ACME is prohibited per Principle: Example Consistency (LOCKED-PICKS v9 §13).

---

How to Use These Examples

1. Read enterprise/otchere-inc.md for the canonical entity model
2. Read digital-twin/otchere-dc-01.md for the digital twin pattern
3. Read simulation/order-fulfillment.md for the simulation pattern
4. Use as templates for your own domain applications
5. Reference back to WSF concepts in wsf/concepts/

---

See Also

• wsf/ : Canonical semantic assets (Entity, Capability, etc.)
• wsf-spec/ : Normative specifications
• wsf-software/ : Semantic Engine implementation
• wsf-visuals/ : Visual diagrams for examples