CA-GTMACC · Go-To-Market Access
The rules that decide whether a Node or Offering can access external clients.
Configuration artifact
CA-GTMACC governs which unit types may offer to external clients, and at which lifecycle stage. It is conditional and deliberately narrow: in the current release only its external-client eligibility meaning is settled.
How It Works
CA-GTMACC governs which unit types may offer to external clients and at which lifecycle stage. It reads against customers, units, and lifecycle, so it requires CA-CUSNED, CA-UNITYP, and an effective CA-UNILIF lifecycle basis. It sits on a branch independent of CA-OFFNAT — there is no dependency edge between them. Its broader long-term classification remains an open question; only the external-client eligibility rule is settled today.
Dependency role. CA-GTMACC is conditional — relevant only where external-client access must be governed. Its prerequisites are CA-CUSNED, CA-UNITYP, and the effective CA-UNILIF lifecycle basis. It is a separate branch from CA-OFFNAT and unlocks no further configuration artifact.
Statements
- CA-GTMACC means Go-To-Market Access.
- CA-GTMACC governs which unit types may offer to external clients, and at which lifecycle stage.
- CA-GTMACC requires CA-CUSNED, CA-UNITYP, and an effective CA-UNILIF basis.
- CA-GTMACC currently settles only external-client eligibility; broader classification remains unresolved.
- CA-GTMACC and CA-OFFNAT are independent configuration branches.
Why It Matters
External-client access is a governance question that needs to know who is served, which units may participate, and which lifecycle stage applies. Where that governance is in use it is part of operational readiness; where it is not, the artifact stays out of the minimum set.
Related
- CA-CUSNED — a prerequisite of CA-GTMACC.
- CA-UNITYP — a prerequisite of CA-GTMACC.
- CA-UNILIF — the lifecycle basis CA-GTMACC requires.
- Dependencies — the full unlock graph.