Use Probity from an automated job

Use the worked report example to interpret test results separately from evidence conclusions. Its retained accounting procedure checks original files through the maintained Lab consumer.

Find a project

Read llms.txt for the navigation index or catalog.json for structured records. Components name the tools; repository records hold their pinned README sources. Integration profiles belong to a component.

Use the stable id for lookups. Follow docs_url for the quickstart and source.commit to reproduce the captured source.

Check discovery

Use the fixed discovery prompts and receipt checker to retain a reader or agent session and review its answers against pinned public sources. Keep actual discovery attempts separate from author-operated packet checks.

Run a local replay

To produce a new local APS/PriorSeal capture, use the replay tools guide. Declare the caller and keep the source hashes, actual process logs and result together. The guide links one complete pinned procedure, including the copied-file route.

Read a retained run

From a pinned Atlas checkout:

python3 tools/check_lab.py --list
python3 tools/check_lab.py --record E6-observer-admission --json

The checker validates artifact hashes and measured fields before returning a record. The JSON includes results, operator roles and review state.

Share a result

Keep the source pins, command, raw output and retained artifact together. Submit them through the run form, or use the correction form when a recorded claim needs fixing.