# Use Opt-In Eager BYOC Activation

A configured BYOC session may set `byoc.enabled: true`. `cp9 up` first brings
the remote Dev full baseline to its existing readiness boundary, then invokes
the same BYOC activation engine and durable journal as `cp9 byoc activate`.
`up` propagates activation failure and succeeds only after activation returns
ready. An interrupted or failed `up` resumes the unchanged journal when the
same command and immutable config are rerun.

When `byoc.enabled` is false or omitted, `cp9 up` preserves the earlier
baseline-only behavior and leaves customer-account mutation to the explicit
day-2 `cp9 byoc activate` command. A `byoc` block still requires the complete
customer and account-setup handoff in either mode; enabling eager activation
does not weaken validation or infer customer ownership. `cp9 byoc status`
remains read-only and `cp9 byoc activate/status` remain supported for day-2
operation, recovery, and observation.

This supersedes only ADR 0039's explicit-only activation choice. It does not
change the BYOC Region boundary, the optional BYOC-A product-acceptance train,
the shared Dev full baseline, or `cp9 destroy` ownership. Eager activation does
not create a user TiDB or customer dataplane substrate; it stops at the same
ready BYOC Region as the day-2 command.