Administration Relationships

Why This Exists

This document explains how Administration relates to other Algosure domains.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Relationship clarity keeps Administration useful for platform operations without turning it into an owner of every platform fact.

Relationship Diagram

flowchart TD
    Identity[Identity]
    Organization[Organization]
    Billing[Billing]
    Notification[Notification]
    Analytics[Analytics]
    Intelligence[Intelligence]
    Integrations[Integrations]
    SourceDomains[Source Domains]
    Administration[Administration]

    Identity -->|admin authorization enforcement| Administration
    Organization -->|tenant facts referenced| Administration
    Billing -->|subscription references| Administration
    Administration -->|notification requests| Notification
    Analytics -->|admin reporting models| Administration
    Intelligence -->|support summaries where approved| Administration
    Administration -->|integration configuration records| Integrations
    SourceDomains -->|audit and support references| Administration

Relationship Catalogue

Domain	Relationship	Data ownership rule
Identity	Authorizes admin actions and enforces access.	Identity owns enforcement. Administration records admin workflows.
Organization	Provides tenant and organization facts.	Organization owns profile facts. Administration owns admin view metadata.
Billing	Provides subscription and entitlement facts for support views.	Billing owns billing facts. Administration owns support/admin context.
Notification	Delivers administrative and support notifications.	Notification owns delivery state. Administration owns request reason.
Analytics	Provides reporting models for admin dashboards.	Analytics owns reporting models. Administration owns admin workflow state.
Intelligence	May summarize support cases or audit review context.	Intelligence owns reasoning output. Administration owns review records.
Integrations	Uses integration configuration records.	Administration owns configuration records; integration services own runtime execution details where defined.
Source Domains	Provide source references for support and audit review.	Source domains own source facts. Administration owns review workflow.

Boundary Rule

Administration can display, coordinate, configure, and review across domains. It cannot silently become the write path for source facts owned elsewhere.