Application Service Standard

Executive Summary

Application services are the primary use-case boundary inside each module. They coordinate commands, queries, policies, repositories, domain services, events, integrations, and AIOS tool interactions.

Responsibilities

Responsibility	Requirement
Use-case orchestration	Coordinates one business use case without owning domain rules.
Tenant context	Requires tenant and organization context where customer data is involved.
Security	Enforces authorization, entitlement, approval, and audit requirements.
Transaction boundary	Coordinates module-owned state changes.
Repository access	Uses only the module's own repositories.
Event publication	Publishes module-owned events after accepted state changes.
AIOS boundary	Receives AIOS requests and accepts AI outputs through governed paths.
Integration boundary	Calls the Integration Gateway or module-owned integration adapter.

Example Application Service Areas

Module	Example
organization	Onboard organization, update organization profile, manage tenant context.
compliance	Upload evidence, review expiry, raise compliance risk.
opportunity	Match tender, save opportunity, update opportunity recommendation.
bid	Create bid workspace, request approval, mark submission readiness.
intelligence	Request AI task, package reasoning, propose memory update.

Rules

• Application services do not expose aggregates as API responses.
• Application services do not call another module's repository.
• Application services validate tenant and organization context before material work.
• Application services are the only state-changing entry point for AIOS-generated outputs.