A tenancy is the wider OCI account boundary. Compartments organize resources and help define where policy applies. They are different from a region or an Availability Domain. Read those boundaries before changing a similarly named resource in an operations handoff.
The local tasks create child-compartment records under a fictional tenancy. OCI resource identifiers are OCIDs; use the supplied identifier for a real maintenance target rather than relying on a display name. A local compartment record doesn't evaluate policies or grant a caller access. The training model saves the requested organization and metadata. Production setup still needs its actual parent, identity relationships, permissions and resource context checked independently.
Keep tenancy, compartment and location boundaries distinct.