Available today
The published 3.0 license, an experimental signing and verification core, a draft toolkit specification, and the 3.1 review proposal.
The next steps are review, clearer examples, and a reproducible implementation. Each milestone should come with evidence of what has actually been completed.
These are proposed milestones, not release dates or commitments by partner institutions. QGPL 3.1 remains a review draft.
The published 3.0 license, an experimental signing and verification core, a draft toolkit specification, and the 3.1 review proposal.
Assess the proposed rights map, AI output boundaries, minimal disclosure, assurance claims, and transport obligations. Record unresolved issues openly.
Use a synthetic dataset to demonstrate signing, independent verification, a failed check, and an evidence renewal link without private information.
Align the format, fixtures, documentation, and packaged commands. Publish versioned downloads and verification instructions once they are ready.
Seek independent legal and technical review, then assess repository pilots and whether SPDX submission or an OSI review is appropriate. Approval is not assumed.
A clause with a counterexample, a reproducible verification failure, or a clearer explanation can move the project forward. Use the exact version when discussing a result.