Crucible Endpoint Completion

Completion selects one contender as the sole endpoint behind the existing Eve interlay. It does not create a migration, copy data, or synchronize contenders.

Request

Use the same body for preflight and completion:

{
  "selected_endpoint_uuid": "22222222-2222-2222-2222-222222222222",
  "expected_interlay_revision": "revision-from-the-current-interlay",
  "acknowledge_warnings": true,
  "data_readiness_evidence_ref": "change/CHG-1842"
}

data_readiness_evidence_ref is optional when no write gap is known and required when the run recorded known write-delivery gaps. It must be a printable reference of at most 512 characters. Eden stores the reference, not the external evidence itself.

Preflight

Call POST /api/v1/endpoint-comparisons/runs/{run}/completion/preflight. Eden checks:

• The selected endpoint belongs to the immutable contender snapshot.
• Adapter, protocol family, endpoint kind, and identity dispatch plan still match.
• Source and selected endpoints remain in the organization and use direct routing.
• The operator retains shared READ and WRITE permission.
• The selected endpoint passes its generic runtime health validation.
• The interlay is running, has the expected revision, and has no active migration.
• The selected endpoint has a successful observation in the last five minutes.
• Known write gaps or telemetry loss have an external data-readiness evidence reference.

Preflight always warns that write delivery is best effort. It also reports no-consensus events, incomplete observations, no accepted write evidence, known gap counts, pending evidence, and dropped evidence. Review and explicitly acknowledge warnings before completion.

Apply

Call POST /api/v1/endpoint-comparisons/runs/{run}/complete. Eden:

1. Serializes completion with the interlay mutation lock.
2. Changes the run to completing and stops new comparisons.
3. Drains accepted work for up to 30 seconds.
4. Uses the normal interlay persistence and runtime reconciliation path to change only the endpoint.
5. Removes the Crucible runtime attachment.
6. Records the prior endpoint, selected endpoint, evidence snapshot, operator-visible outcome, and timestamps.
7. Marks the run completed.

The interlay UUID, address, listeners, ports, TLS, authentication, masking, and governance settings do not change.

If persistence or runtime reconciliation fails, Eden restores the prior endpoint and run state. Startup also reconciles an interrupted completion from its durable prior endpoint, selected endpoint, and resume state. Repeating completion with the same endpoint is idempotent. A different selection after completion returns a conflict. Selecting the endpoint already serving the interlay is a valid no-op completion and does not restart the listener.

Data Readiness

Crucible evidence can show behavior and best-effort delivery. It cannot establish data durability. The selected endpoint must already contain production-ready data. Use Exodus when historical movement, live-write capture, cutover gates, or rollback are required.