Skip to content

Latest commit

 

History

History
31 lines (20 loc) · 1.82 KB

File metadata and controls

31 lines (20 loc) · 1.82 KB

Summary and bounded outcome

ContextSafe safety boundary

Evidence, compatibility, and rollback

Verification

  • make verify passes from the repository root.
  • New behavior has happy-path, malformed-input, boundary, and relevant safety-negative tests.
  • Deterministic receipt or canonical-output vectors were refreshed when applicable.
  • Patient data, credentials, rejected input values, and unrestricted evidence do not enter logs or public receipts.
  • Schema and public-contract compatibility are preserved or the version and migration path are documented.

Review gates

  • Acceptance criteria are linked above and the affected ISO/IEC 25010 characteristic(s) are named.
  • Documentation, ADRs, operating instructions, and rollback guidance are updated where behavior changed.
  • Workflow and dependency changes use least privilege, immutable action SHAs, and receive code-owner review.
  • Clinical, trans-community, privacy, security, accessibility, legal, and interoperability review is requested where the change depends on that judgment.
  • The root definition of done is satisfied, or every unchecked item is explained below.

Exceptions, N/A reasons, or bounded follow-up