Alexandria
Getting Started

Getting Started

Overview of the Alexandria components and how they fit together under the Vocabulary Hub specification v0.3.0.

Getting Started

Alexandria lets a dataspace authority publish the vocabularies and policy profiles every participant must speak, and lets each participant check its own DSP traffic against them locally.


Binaries

BinarySourceRole
alexandria-servercmd/alexandria-serverVocabulary Hub (C-HUB). Serves the /v1 management API and the public /pub tree. Validates OAuth 2.0 bearer tokens, keeps namespaces isolated and signs credentials with the hub key.
alexandria-clientcmd/alexandria-clientEdge proxy (C-CLI). Sits in front of a DSP connector, synchronizes verified packages and applies the rule set to every message. Exposes an admin API on its own listener.
alexandriaccmd/alexandriacProfile compiler. Validates and compiles alexandria.profiles/v1 YAML documents offline.
fake-idpdeploy/fake-idpLaboratory OAuth 2.0 / OIDC provider: discovery, JWKS, an interactive sign-in page and a token CLI.
fake-connectordeploy/fake-connectorLaboratory DSP connector that acknowledges and records the traffic it receives.

How the Pieces Fit Together

1. Namespaces and stewards

The hub is divided into namespaces, each with its own vocabularies, release line and listing sequence. The hub admin creates namespaces and assigns stewards; stewards perform every operation inside their namespace. No namespace operation reads or modifies another namespace (REQ-SYS-010).

2. From draft to release

A steward creates a draft, validates it and proposes it, which freezes an immutable candidate with its diff, release class and planned dates. Approving the candidate publishes the package, signs a VersionRecord and issues a new VersionListing.

3. Synchronization

Each alexandria-client polls the listing of its namespace, verifies the proof against the hub DID, checks continuity (no rollback, no changed dates, no dropped revocation) and downloads the packages it needs, verifying every digest. A listing is accepted whole or not at all.

4. Decisions at the edge

For every DSP message the client selects one rule, evaluates its gates against the packages in force at the local instant and applies the action for the rule mode. The decision uses only local state: there is no network request on the request path (REQ-SYS-002), and forwarded bodies are byte-identical (REQ-SYS-003).

Prefer a browser to curl? The console covers both binaries and can be embedded in them with make build-gui.


Next Steps

On this page