What verification means
A harness must finish its processing chain and carry a readable verification record before it can be asked over or released. Verification checks the evidence already on disk; it does not claim the captured boundary is complete beyond the sources you locked.
Most failures show Not verified. A failed recheck shows Not confirmed, because MSOCK cannot know whether an earlier answer is still current.
Choose the remedy shown
| What MSOCK reports | What it means | Supported action |
|---|---|---|
| The last step never recorded that it finished | No verification record exists, or a later change invalidated it | Verify & complete. MSOCK derives the record from files already on disk; it does not re-extract |
| The chain did not finish | The final Synthesize work is incomplete | Run the final Synthesize harvest; Ask and Release remain unavailable until it finishes |
| The verification record is damaged | The record cannot be read | Verify & complete to derive a replacement from the existing harness |
| The record belongs to another harness | A copied, replaced, or tampered record certifies the wrong folder | Review the warning, then explicitly choose whether to replace the record and verify |
| The record was written by a newer MSOCK | This build cannot safely read or overwrite it | Update MSOCK, then check again |
| MSOCK cannot read where the harness came from | The origin marker is unreadable, so provenance cannot be trusted | Restore from backup or download/re-create the harness; there is no automatic repair |
| This engine cannot report chain verification | The installed engine is too old or incompatible | Update MSOCK, then check again |
| Checks are still loading | No conclusion has been reached | Check again; nothing is changed on disk while status is unknown |
| MSOCK could not re-read the checks | The last known answer might be stale | Check again; the badge is Not confirmed |
| An unrecognised verification state was returned | This build does not understand the engine response | Update MSOCK if a newer version is available, then check again |
States that are not verification failures
| State | Meaning | Next action |
|---|---|---|
| Scan resumable | An interrupted run has durable checkpoints | Resume from the harness; completed checkpoints are reused |
| Needs your answer | Processing paused for a question | Answer it, then resume |
| Sign-in expired | The Claude session can no longer continue | Sign in to Claude Code, then resume |
| TLS/network issue | Processing is waiting on connectivity | Fix the network or certificate problem, then resume |
The pause reason takes precedence over generic progress. Resolve the named cause rather than restarting the harness.
Release-room wording
The processing pipeline labels the recovery action Verify & complete. In the Release room it reads Verify & complete to release. Both run the same safe derivation over what is already on disk.
When verification succeeds, reopen Release and continue with the local version. Team publishing remains a separate, deployment-authorised action.