External Actors

Executive Summary

External Actors defines the people and organization-facing roles that interact with Algosure at the C4 Level 1 system context boundary. It also clarifies the role of Digital Professionals, which are context actors but remain inside Algosure rather than external human users.

Why This Exists

Algosure must serve customer organizations while preserving clear accountability between human decision-makers, organization users, AIOS, and Digital Professionals. This actor view prevents architecture from treating AI workers, customer users, and external systems as the same kind of participant.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

Business Value

Clear actor boundaries help define approval responsibility, security posture, tenant access, audit evidence, and human-in-the-loop governance before implementation begins.

Actor Context

flowchart LR
    subgraph External["External to Algosure"]
        CEO[Customer Organization / CEO]
        OrgUsers[Organization Users]
    end

    subgraph AlgosureBoundary["Inside Algosure"]
        Algosure[Algosure System]
        AIOS[AIOS]
        Professionals[Digital Professionals]
    end

    CEO --> Algosure
    OrgUsers --> Algosure
    Algosure --> AIOS
    AIOS --> Professionals
    Professionals --> AIOS
    AIOS --> Algosure

External Human Actors

Actor	External Status	Relationship to Algosure
Customer organization	External tenant-owning organization	Owns business goals, users, approvals, data rights, procurement accountability, and subscription relationship.
CEO	External executive decision-maker	Sets strategic priorities, receives executive insight, approves material decisions, and remains accountable for organization outcomes.
Executive sponsor	External leadership role	Aligns Algosure adoption with organization strategy, budget, risk tolerance, and operating model.
Organization administrator	External customer role	Manages organization-level access, configuration requests, users, and tenant governance.
Procurement users	External customer users	Work with opportunities, bids, suppliers, marketplace sourcing, contract preparation, and procurement tasks.
Compliance users	External customer users	Manage compliance evidence, expiry readiness, verification tasks, and exception handling.
Finance users	External customer users	Work with funding, payment, financial qualification, and commercial readiness context.
Bid contributors	External customer users	Provide documents, inputs, evidence, pricing, narratives, and reviews for bid processes.
Approvers	External customer users	Approve high-impact actions, submissions, commitments, funding decisions, and exception resolutions.
Viewers and auditors	External customer users	Review status, evidence, history, reports, and audit trails according to authorization.

Internal Context Actors

Digital Professionals are included in the system context because they participate in work, but they are not external systems or independent legal actors.

Actor	Boundary Status	Relationship to Algosure
AIOS	Inside Algosure	Orchestrates delegated work, context assembly, reasoning, approvals, exceptions, events, memory workflows, and audit evidence.
Digital Professionals	Inside Algosure	Perform scoped AI work under AIOS control and approved guardrails.
Ari	Inside Algosure	Supports executive orchestration, prioritization, and leadership-facing work where approved.
Ava	Inside Algosure	Supports customer, communication, or operations-oriented work where approved.
Orion	Inside Algosure	Supports opportunity and market intelligence work where approved.
Lex	Inside Algosure	Supports compliance, legal, and document reasoning where approved.
Nova	Inside Algosure	Supports bid and proposal work where approved.
Atlas	Inside Algosure	Supports data, analytics, and insight work where approved.
Forge	Inside Algosure	Supports process, automation, and execution design where approved.
Nexus	Inside Algosure	Supports marketplace and supplier coordination where approved.
Beacon	Inside Algosure	Supports notification, monitoring, and signal routing where approved.
Sage	Inside Algosure	Supports learning, guidance, and capability development where approved.
Pulse	Inside Algosure	Supports reporting, operational health, and rhythm monitoring where approved.

Actor Boundary Rules

Rule	Meaning
Humans approve high-impact actions	AI recommendations, generated documents, submissions, payment actions, and external commitments require human approval where risk or policy requires it.
Customer users remain tenant-scoped	Every customer actor operates inside an authorized tenant context.
Digital Professionals do not own authority	Digital Professionals may recommend, draft, analyze, summarize, and execute approved tasks, but authority remains with Domains, AIOS policy, and human approval rules.
Actor activity is auditable	Material human and AI actions must produce traceable evidence.
Roles are not implementation permissions	This document identifies context actors, not detailed role-based access control permissions.

Non-Implementation Boundary

This document does not define:

• User account models.
• Permission matrices.
• Identity provider configuration.
• Screen navigation.
• AI prompts.
• Agent runtime implementation.
• Notification routing rules.