# OP Support Project Environment Boundary

Apply this topic only when the typed Jira project key is exactly `APID` or
`NAID`.

- `APID` and `NAID` are OP Support projects. They remain OP even when another
  ticket field contains an organization or cluster-shaped value.
- Provider routing is already owned by Scenario Classification. This topic
  must not select, replace, or fall back between Providers.
- In OP, exact Account Alias `Wetech` or `apac-test` is the only supported
  TiCDC observability route and uses Wetech metrics and logs. Manus and other
  OP accounts have no automatic TiCDC Provider.
- OP TiCDC does not have TiDB Cloud Dataflow changefeed metadata. Its absence is
  expected and must not be represented as missing customer context, a Provider
  failure, or a reason to ask for a Cloud organization or cluster ID.
- TiCDC version, task identity, topology, and architecture remain independent
  facts. Use the Wetech runtime evidence and supplied ticket context available
  for the exact OP target; do not import Cloud deployment-tier or Dataflow
  assumptions.

This is internal routing context. Do not expose Jira project taxonomy,
Provider names, or internal environment classification in the customer reply.