Module lookups 

Reading the records a write’s policies declared they read, before the write is judged.

The gate is judged inside a synchronous section, so nothing under it can await and nothing under it may reach the network. The read is therefore split in two, in the order a write meets them:

1. Reader::prefetch, from the route that accepted the write, while there is still a runtime. It works out which records the applicable policies want for this write and fills didbot-lookup’s cache with what it does not already hold, inside that crate’s own deadlines.
2. Reader::answers, from didbot-pds’s write path, which is didbot_pds::policy::WriteLookups. It reads the same cache, does no I/O, and hands the answers to the gate as ordinary subject fields.

Both halves work out what a write wants from the same code, so a record the first half reads is the record the second half looks for.

Structs

DeclaredLookups

The lookups this deployment’s policies declare, swapped each time the policy set is rebuilt.

Reader

This deployment’s two-phase read of the records its policies declare.

Type Aliases

Wanted 🔒

What one write wants read: the lookup, the account it is about, and the record to read.