Websites Responsibilities

How the Product Area Is Divided

One module covers site administration, editorial content, application changes and portal runtime adapters. Platform stores authoritative sites, hostnames and delivery records. Websites stores templates, changes and content. Customer application packages handle request routing and member-facing adapters, while the console hosts administration.

Websites, Content and the Portal Runtime

The module owns the five Domain Objects listed in its responsibility declaration. The Service Contracts assign each object to its actual owner and identify the business operations, integration adapters and runtime entry points exposed by that owner. The invariant references provide the guarantees and their enforcement evidence; this overview adds no stronger promise about provider execution or concurrency.

Refresh work connects editorial publication to customer cache invalidation. Repository callbacks and app deliveries supply application-change outcomes, with separate schedules for delivery reconciliation and content refresh. Some local operation names describe package handlers rather than declared service routes.

What Is Delegated to Platform and Other Areas

Platform supplies security, application licensing, eligibility policy, workspace lifecycle and console framing. CRM retains member and organization records and decides their permitted changes. External delivery tooling executes builds and deployments and writes serving pointers. Custom-field designation and submission publication remain explicit product decisions; the examined module has neither custom-field registration nor a published submission intake operation. It retains change history and content versions without generalized field-history integration.