Loading…
How records move: the rules they meet, the queue, how long it takes, and the scrapers that feed it. Open any record to see its own way through.
Every rule api.coop knows, in the order a record meets them. A rule's records are trusted only while the commons root endorses it.
Run on each source record: where it is, which place it is at, what it is the same as.
They run in this order: geocode, venue, dedupe, migration, adjudicator, then takedowns.
Joins what the rules say is the same into one curated record.
Run once on each curated record, and leave a receipt when done.
15 endorsed mirrors write records too, but they are sources, not steps: see them on Sources.
place, event → sameAs, containedIn, heldAt, derivation
runs newer code: endorsed 5070ced, runs 9ef6a1c
The queue is for the operator.
runs newer code: endorsed 5070ced, runs 9ef6a1c
The queue is for the operator.
The queue is for the operator.
api.coop trusts a rule's records while the commons root did:plc:r2wtt2lqn37k4tv4n2fl7d6l endorses it for that record type. Revoking an endorsement untrusts everything the rule published, past records included. A rule that runs newer code than its endorsement names keeps its trust until it is endorsed again or revoked.