std/verify-a-listing-against-its-source as a composition

The members, drawn end to end

What running all of this would mean

• 2 capabilities across 2 procedures: cli:curl, cli:psql. Running this composition means granting all of them at once, which is more than any one member asked for.
• Trust T2. A composition cannot be more trustworthy than the part you did not check.
• Highest risk: reversible-write. One destructive member makes this a destructive procedure whatever the others are.

Capability union: cli:curl, cli:psql

Trust T2

Members

• std/verify-a-listing-against-its-source — T2, the record you came from, published by std
• std/enrich-from-pages-you-do-not-control — T2, pulled in by requires, published by std

Take it with you

A composition exports as a list of pinned references, not as a merged procedure. Merging would produce a document whose steps have lost their publisher, their trust and their provenance — and the first thing anybody would do with it is run it.

# A composition, as references. Not a merged procedure: each member keeps its
# publisher, its trust level and its provenance, and there is nothing here to run.
# Trust T2 (the weakest member). Highest risk reversible-write.
# Capabilities granted if you run all of it: cli:curl, cli:psql.

std/verify-a-listing-against-its-source@1.0.0  # root, T2
std/enrich-from-pages-you-do-not-control@1.0.0  # requires, T2