Registry
A persona’s portable registry lives in references/registry.json. It lists linked workflows, pipelines, and lists with their resource keys and file paths, definition fingerprints, and published revisions. Older entries can use the root Git link when an explicit revision is absent.
The portable registry
Section titled “The portable registry”Fields and example
Section titled “Fields and example”references/registry.json lists linked workflow, pipeline, and list definitions. An entry identifies the definition, its repository and paths, and the content the publisher reviewed. The excerpt uses placeholders for publisher-generated values.
{ "schemaVersion": 2, "repos": [ { "kind": "list", "resourceKey": "list.example.meetings", "displayName": "Meetings", "repositoryUrl": "https://github.com/example/meetings", "branch": "main", "path": "references/lists/meetings", "assetPath": "assets/list.json", "definitionFingerprint": "<publisher-generated sha256>", "revision": "<published git commit>" } ]}Resolve and verify
Section titled “Resolve and verify”Resolve a resource key to the linked revision and asset path. For an older entry with no explicit revision, use the root commit’s Git link. Gabriel normalizes the definition to compact JSON with object keys sorted recursively and array order preserved. The fingerprint must match before use. Publish linked repositories first so the root can carry their reviewed revisions.
Other indexes in Gabriel
Section titled “Other indexes in Gabriel”Authoring graph and package registries
Section titled “Authoring graph and package registries”references/workspace.json tracks the broader authoring graph, including links beyond portable imports. An npm-compatible registry serves separately packaged playbooks, teams, and personas by exact package name, version, and archive digest. A marketplace listing helps people discover those releases.
See the full registry contract and package pinning.