Internal vs Cross-Organizational Use

Compex supports both internal enterprise workflows and cross-organizational collaboration. In both cases, the same primitives apply: policy-controlled execution, approvals, audit events, evidence records, and role-separated access.

Internal enterprise workflows

Internal workflows happen inside one organization. A data owner, AI team, analytics team, or platform team may all belong to the same enterprise, but sensitive data still needs controlled access and evidence.

Examples:

• Internal governed model training on regulated datasets.
• Analytics teams running bounded queries without raw exports.
• Department-level approvals before sensitive workloads run.
• Audit records for internal review cycles.

Cross-organizational workflows

Cross-organizational workflows involve separate parties, such as an AI company and a regulated client. The data owner keeps control over protected data while the processor runs approved work under policy.

Examples:

• AI vendor serving a bank, hospital, or insurer.
• External processor running scoped analytics.
• Joint evaluation of a model against client data.
• Controlled service delivery to approved users.

What this means

For business readers, the main distinction is who participates in the approval chain. Internal workflows may be faster to scope. Cross-organizational workflows usually require more explicit contracts, evidence expectations, and role separation.

Current status

Compex is pilot-ready for both patterns when the pilot has a clear data owner, processor, reviewer, workload, and output boundary.

Limitations

Cross-organizational pilots need legal and operational alignment outside the platform. Compex can provide governance primitives and evidence records, but it does not remove the need for agreements between parties.