Tools
Reference Node
One node that speaks the protocol: the matcher and its scoring, the consensus arithmetic, signing and verification, and the ActivityPub surface a participant exposes to the network.
A node is the unit of participation. Running one is how an organization joins, answers broadcasts from its own data and mints identifiers under its own key.
Status: in progress. The protocol layer is built and the adapters over it are thin by design. The source is not yet in the public repository. What it implements is published in full as the specification, and the pilot it was built for is described in running the pilot.
Client
The operator’s interface that runs against the reference node. A dashboard of what needs resolving, search across the roster, a comparison view for a candidate pair and the resolution screen.
Status: in progress, and not yet in the public repository. The screens it implements are drawn in the interface mockups.
Playground
A browser playground runs the matcher, the scoring, the consensus arithmetic and Ed25519 signatures as specified, over the specification’s worked examples or over an imported roster. Its source is a single page with no build step, which makes it readable as an implementation of the protocol rather than only a demonstration of it.
The network of other resolvers is modeled inside the page. There is no server: the page’s security policy forbids outbound connections, so nothing loaded into the page leaves the browser.
Artifacts
- Data Pilot Template is the workbook a participant fills in to load a roster.
- Pilot ingest mapping reads that roster into the pilot service, column by column.
- Ranking formula is the scored query the pilot ran, with the weight carried by each identifier.
- Query examples by first name, last name and full name.
The weight set and frequency table that make a score mean the same thing everywhere are published in the specification, under Matching Engine and Scoring, and the conformance rules under Certification.
Related
Offer Management shares the same underlying pattern. Two specifications, one federated shape.