Common postures (not job titles)
The same org can wear more than one hat over time; the important part is clarity at the interface.
Service producers
Publish capabilities with explicit contracts, lifecycle, and support posture so others can rely on edges without guesswork.
Integrators
Compose offerings across boundaries, carry consent and provenance, and own the glue that is not generic rail.
Operators of shared interchange
Operate the connection fabric, identity surfaces, observability, and incident practice that many parties rely on together.
Participants and stewards
Community expectation, dispute norms, and roadmap pressure - the soft tissue that keeps scale humane.
Why roles matter for Network
When roles are implicit, integrations look pairwise. When roles are explicit, the mesh can be governed.
- Discoverability improves when ownership of an edge is clear: who changes it, who monitors it, who vouches for it.
- Risk conversations shorten when operators of shared rail are named - not buried in a generic 'platform team.'
- Participation models (covered under Governance) tie back to these postures instead of abstract slogans.
From roles to effects
Once membership is clearer, scaling connections changes economics - in bounds.