# Round 15 disposition

Input: revision 21, SHA-256 `05176ed1fa72da09cae9c4683bd8fedf1cf15c85b175686260282b4d9e5fb63e`.

Opus completed with two substantive findings. GLM completed the gateway/recovery scope with no substantive findings and a normal stop. K3's full-plan process is still running when the next snapshot is frozen; its final report will be reconciled separately. No clean verdict is claimed for a pending process.

## Opus 1: authority-key custody and cloning

Accepted. Revision 22 requires device-bound, non-exportable custody for Mac authority and recipient-certification keys, with an explicit backup-clone impersonation test. It does not assume a this-device-only label proves non-exportability. Incompatible pre-login availability is a feasibility blocker, never an ordinary-file fallback.

Migration needs a new key with authenticated continuity or independent recovery. The exact interaction is an explicit user-choice gate. A question was sent about one-time migration recovery; no answer has been received and no extra biometric or ceremony has been adopted. The gate must be resolved with the user before implementation. Routine app updates preserve identity and pairing.

## Opus 2: restored audit cursors

Accepted. Revision 22 binds records, cursors and signed sync batches to journal epochs. Restoration recovery creates a fresh epoch tied to the combined trust generation. Old cached history is preserved, the discontinuity is labelled, and new-epoch sync cannot overwrite old sequence numbers or stall on an obsolete cursor. Key changes must pass authenticated recovery before new batches are trusted.

A gateway registration diagram illustrates the already-specified candidate/proof/activation sequence. All changes remain plan-only; platform gates are not claimed as verified.

## Pending process resolved

K3 subsequently completed with exit 0 and a nonempty full-plan report. It reported no substantive findings. No additional correction was required.