@projectpac/source-dobj-inventory

The first source adapter: it keeps this principal's digital objects in sources, so a flow can stake one without ever holding it.

A flow cannot write a source. That rule is what makes this extension necessary rather than convenient: the objects live in a daemon beside the node (dobjd, which holds the principal's objects and their bearer secrets), and something has to bring them into the node's own accounting of what this principal has. That something owns what it writes -- data management accepts a write only from the context of the source's owner -- so no flow, and no other extension, can put an object where a flow might name it.

Two shapes come out of one poll:

• dobj-inventory, one document listing what this principal holds, with the secret fields left out. It is the thing an agent's prompt can be told about.
• one source per object, holding that object's file exactly as dobjd has it. That is the material a box execution stakes, and naming it is all a flow ever does with it.

Like every source adapter it talks to an outside service (dobjd's HTTP API), not to other nodes, and runs on the schedule its manifest declares rather than a loop of its own.