Background
The release must package the validated profile and communicate its advantages without overstating external certifications or evidence status.
Scope
In scope:
- Freeze supported suites, providers, transports, BCOS versions, platforms, migration boundaries, limitations, and security advisories.
- Publish release artifacts, SBOM/provenance, checksums, test evidence, deployment docs, compatibility matrix, and upgrade/rollback guidance.
- Review README, website, SDK docs, examples, and sales claims for technical accuracy and approved wording.
Out of scope:
- Advertising formal MLPS, commercial cryptography assessment, product certification, legal timestamp, or judicial recognition before the scoped result exists.
Proof, storage, and compatibility impact
- Phase: Assessment
- Workstream: Compliance
- Risk: High
- Changes must preserve TrustDB evidence semantics, durable publication boundaries, bounded large-data behavior, and explicit trust roots.
Acceptance criteria
Validation plan
- Release candidate rehearsal, clean-room deployment, and signed checklist.
- Security/compliance/legal claims review.
Dependencies
Schedule
- Start: 2027-01-04
- Target: 2027-01-08
Background
The release must package the validated profile and communicate its advantages without overstating external certifications or evidence status.
Scope
In scope:
Out of scope:
Proof, storage, and compatibility impact
Acceptance criteria
Validation plan
Dependencies
Schedule