# EMPOWER-X machine-readable Rulebook, version 1.0 (draft)

These files express the EMPOWER-X Rulebook in a form software can read and check. The Rulebook pages on the website are the binding text and prevail if anything here differs; the Technical Committee then corrects these files within 30 days.

| Folder | File | What it is for | Rule | Access |
|---|---|---|---|---|
| rulebook | rulebook-index.json (+ schema) | Every chapter and topic: title, in-short line and binding text, with links to the files below | All | Public |
| vocabulary | empx.ttl | EMPOWER-X terms: access levels, roles, offer properties, ODRL extensions | R4.3 | Public |
| credentials | gaia-x-credential-profile.json | Which Gaia-X Loire credentials a participant presents | R1.4, R5.1 | Public |
| credentials | membership-credential.schema.json (+ example) | The EMPOWER-X membership credential (W3C VC 2.0) | R1.4, R5.1 | Public |
| credentials | status-list.example.json | Revocation list format (W3C Bitstring Status List) | R5.1 | Public |
| policies | open / participants / restricted / compute-to-data .odrl.json | One ODRL 2.2 policy template per access level | R5.2, R5.3 | Public |
| policies | policy-mapping.json | How each template is enforced on the node | R5.2 | Public |
| offers | offer-profile.shacl.ttl (+ good and bad examples) | Checks the publication checklist on an offer's DCAT-AP metadata | R6.1, R6.2 | Public |
| data-models | data-models.json | Approved data models and reference datasets | R4.2 | Public |
| tests | conformance-tests.yaml | The five end-to-end tests and where to record results | R5.6 | Members |
| status | implementation-status.json | Which rules the platform already enforces | R5.6 | Members |

## What is a draft value

- `{{...}}` marks a value the technical team fills in: provider and offer DIDs in policy templates, adopted data-model versions, the policy-engine rule set, test results and dates.
- Gaia-X class names and envelope format must be checked against the Gaia-X Compliance Service release in use.
- Statuses in implementation-status.json come from the Rulebook's status notes; items marked "to confirm" need the technical team.
- The vocabulary namespace is https://empower-x.io/ns/rulebook#; the URLs need to resolve once the files are published.

## How the files were checked

- All JSON files parse; the membership credential example validates against its schema; the rulebook index validates against its schema.
- The vocabulary and the offer profile parse as RDF (Turtle).
- The offer profile was run with SHACL: offer.example.ttl conforms; offer.bad-example.ttl fails with the checklist messages.