At this level
computer.localnetwork.epk ยท 5- computer.localnetwork.epk.content record not from the namespace authority The private part of a press kit, written by the Local Network root account into the press kit's space whenever a manager publishes it.
- computer.localnetwork.epk.defs defs not from the namespace authority Who can ask to see the private part of a press kit, and whether they get it straight away. Each audience is auto (approved at once), review (a manager decides) or none (can't ask). Someone in several audiences gets the most open of their answers. Managers can always add people directly.
- computer.localnetwork.epk.draft record not from the namespace authority One manager's unpublished changes to one press kit, in their repo in the project's backstage (computer.localnetwork.space.backstage). The record key is the press kit's: an existing one's, or for a new press kit, the key it will be published under, so a manager has at most one draft per press kit. A draft the Local Network root account writes on someone's behalf has a key of its own, since the root can hold several managers' drafts of one press kit; its base names the press kit, or for a new one,
- computer.localnetwork.epk.grant record not from the namespace authority Access to the private part of a press kit. Written by the Local Network root account into the project's computer.localnetwork.space.epkRequests space, which only the project's managers read, keyed by the press kit record's key and the subject's DID (with every % as ~), joined by a colon; the press kit's space lists the subject as a reader. Grants made before that sit in the press kit's space, keyed by the subject's DID, until the root moves them. Deleting it, and removing the member, takes acces
- computer.localnetwork.epk.request record not from the namespace authority A request to see the private part of a press kit, written by the person asking into the project's computer.localnetwork.space.epkRequests space, which only the project's managers read.