The ampack specification, requirement by requirement
Every numbered requirement of the ampack specification, with its level (MUST, SHOULD, MAY), its document and section, and what verifies it; the documents; the profiles and whether each is implemented. Generated from the specification's own files. A draft, like the specification.
The format's own specification: 454 numbered requirements, generated from its files.
Published by joslat. This is one of Memcert's own packs: its publisher and its curator are the same party.
io.github.joslat.packs.ampackspec 1.0.0
pack digest sha256:bc291a357f8e9166d45c3bf6e53e89dd7ce2f3dd24257bb87f8ebc00569d7d76
file SHA-256 3deab2455e58422afcd4c7a9a62bfc70a66b95778891f567025422078d88edd6
Evidence
Each check and what it found. No stars and no grade.
From its card
What is inside
The first records, as an agent would be shown them. They are data, shown as text.
Check it yourself
ampack verify io.github.joslat.packs.ampackspec-1.0.0.ampack --policy trust.json --explain ampack scan io.github.joslat.packs.ampackspec-1.0.0.ampack --policy trust.json ampack test io.github.joslat.packs.ampackspec-1.0.0.ampack --policy trust.json
Or drop the two files into the browser verifier.
Every step of the verification, as the tool printed it
What the tool advises the publisher to add
- trial.missing io.github.joslat.packs.ampackspec: It declares no trial: a host that requires trials for its namespace refuses it, and nothing measures it on that host's history.
- derivation.missing io.github.joslat.packs.ampackspec: It says nothing of what it was made from (META/derivation.json): a host cannot cap its records' confidence by their sources, nor see the pack it was derived from.