Section 2 · OES Spec
Experiment identity and documentation
The human-facing context that makes a result meaningful later.
An experiment result without context is almost useless for a learning repository. The identity block captures what the team set out to learn, who owned it, and where to find the surrounding research, design, and code artifacts.
Fields
| Field | Type | Purpose |
|---|---|---|
| experiment.idrequired | string | Stable unique ID. |
| experiment.slug | string | Human-readable identifier. |
| experiment.titlerequired | string | Display name. |
| experiment.summary | string | Short plain-English summary. |
| experiment.description | string | Longer context. |
| experiment.hypothesis | string | What the team believed would happen. |
| experiment.learningGoal | string | What the team wanted to learn. |
| experiment.businessGoal | string | Business objective — activation, revenue, retention, etc. |
| experiment.productArea | string | Product surface or area. |
| experiment.tags | string[] | Search/indexing tags. |
| experiment.status | enum | One of: draft, planned, running, stopped, analyzed, decided, archived. |
| experiment.owner | object | Responsible person or team. |
| experiment.stakeholders | object[] | PM, engineer, data scientist, designer, executive sponsor. |
| experiment.links | object[] | PRD, Figma, Jira, GitHub PR, dashboard, customer research. |