|
| 1 | +# Experience Notation |
| 2 | + |
| 3 | + |
| 4 | + |
| 5 | + |
| 6 | + |
| 7 | + |
| 8 | +--- |
| 9 | + |
| 10 | +**Experience Notation** is a domain-specific language (DSL) for modelling human experience in a structured, machine-readable format. |
| 11 | + |
| 12 | +Originally developed as part of **[Demoscope.ai](https://demoscope.ai)**, a commercial platform for LLM-powered synthetic user feedback and behavioural insights, Experience Notation has grown into a general-purpose modelling language for complex, human-centred experiences. |
| 13 | + |
| 14 | +It is designed to support design research, behavioural prototyping, AI simulation, and service modelling workflows. It enables researchers, designers, policymakers and technologists to represent user journeys, decisions and contextual factors from a human-centred perspective. The language supports personas, actions, branching logic, environmental influences, disruptions, behavioural metrics and more. |
| 15 | + |
| 16 | +Experience Notation is open and extensible. |
| 17 | +[View on GitHub](https://github.com/context-notation/experience-notation) |
| 18 | + |
| 19 | +--- |
| 20 | + |
| 21 | +## Key Features |
| 22 | + |
| 23 | +* **Human- and machine-readable**: Write in plain text that both people and systems can understand |
| 24 | +* **Structured grammar**: Validated by an EBNF specification for syntax correctness and tooling |
| 25 | +* **Modular elements**: Use `Event`, `Step`, `Persona`, `Conditional`, `Metric`, `Tag`, `Ref`, `Meta`, and `Disruption` blocks to model complexity |
| 26 | +* **Support for branching logic**: Model decisions and outcomes using `IF`, `THEN`, and `ELSE` constructs |
| 27 | +* **Persona modelling**: Define users inline or externally using `External-Source` and enrich them with experience, interaction, and adaptation attributes |
| 28 | +* **Environmental context**: Capture contextual factors and real-world conditions using `Environmental-Factors` and `Disruption` |
| 29 | +* **Metadata and tagging**: Attach key-value pairs and identifiers for filtering, categorisation, and semantic structure |
| 30 | +* **Parallel events and referencing**: Model concurrent paths using `Parallel-Events` and interlink steps and events via `Ref` |
| 31 | + |
| 32 | +--- |
| 33 | + |
| 34 | +## Where Experience Notation Could Be Applied |
| 35 | + |
| 36 | +Designed to address real-world complexity, Experience Notation helps researchers and technologists model and analyse human journeys with clarity and structure. Below are domains where it shows early promise. |
| 37 | + |
| 38 | + |
| 39 | +| Domain | Application | |
| 40 | +|--------|-------------| |
| 41 | +| **AI Safety** | Model coordination failures, edge-case decisions and value conflicts to support safe deployment of LLMs | |
| 42 | +| **Government** | Simulate public service interactions, emergency response flows and population-wide accessibility impacts | |
| 43 | +| **Product Design** | Map user journeys to identify service friction, accessibility gaps and opportunities for inclusive improvement | |
| 44 | +| **Healthcare** | Model goal-driven journeys involving behavioural triggers, disruptions and personal adaptation over time | |
| 45 | + |
| 46 | +--- |
| 47 | + |
| 48 | +## Who Is It For? |
| 49 | + |
| 50 | +- AI safety researchers simulating agent behaviour |
| 51 | +- Designers mapping inclusive service experiences |
| 52 | +- Policy teams evaluating accessibility and impact |
| 53 | +- Developers building human-aware systems |
| 54 | + |
| 55 | +Whether you are modelling risk, prototyping services or benchmarking language models, Experience Notation offers a structured and interpretable approach to reasoning about experience. |
| 56 | + |
| 57 | +--- |
| 58 | + |
| 59 | +> **Join our community** to shape the future of human-centred design and AI |
| 60 | +> [GitHub Discussions](https://github.com/context-notation/experience-notation/discussions) |
| 61 | +
|
| 62 | +___ |
| 63 | + |
| 64 | +## Support & Collaboration |
| 65 | + |
| 66 | +Experience Notation was authored by **Nikolaos Maniatis** and is maintained by **The Cato Bot Company Limited** as part of the [Context Notation](https://context-notation.com) initiative. |
| 67 | + |
| 68 | + |
| 69 | +For questions about: |
| 70 | +- Using Experience Notation in your projects |
| 71 | +- Contributing to development |
| 72 | +- Research collaborations |
| 73 | +- Commercial support options |
| 74 | + |
| 75 | +Feel free to reach out: |
| 76 | + |
| 77 | +📧 [hello@context-notation.com](mailto:hello@context-notation.com) |
| 78 | +💬 [GitHub Discussions](https://github.com/context-notation/experience-notation/discussions) |
| 79 | +🌐 [context-notation.com](https://context-notation.com) |
0 commit comments