Trust classes: which runners may run what, and whose checkpoints a job accepts issue #79 open andymccall opened this · 0 comments
andymccall set labels feature, security ·
andymccall referenced by change 39e737fbc7a9 on main ·
andymccall set labels feature, security ·
andymccall referenced by change 39e737fbc7a9 on main ·
Runners get a trust class from how they are known:
attested(cloud confidential VMs and vTPM, keyless workload identity),owned(the organisation's registered hosts),device(members' phones and laptops),anonymous(browsers). A job or sandbox may require a minimum (trust "owned"; release and publish jobs default to it); a job resumes only from checkpoints made at its class or above; receipts and provenance carry the class of every runner that contributed; spot checks re-run a sample of low-class jobs elsewhere and compare outputs. Design: docs/handover.md §9.