HEPO's three offerings share an application framework, working records and server services. People & Culture Orchestration interprets agreed evidence and supports development. Process Orchestration executes defined, authorised work. Simulation & Gamification supports exploration, declared scenarios and learning activities.

This reference explains the shared responsibilities beneath those uses. A module reuses platform patterns, while its particular operations, permissions and integration still require implementation and verification.

Four groups of shared capability

Group	Responsibilities
Identity and accounts	Identity/session services and the internal/external account context; an account record is distinct from permission to act
Operational Core	People, organisation, work, events, presence, communication, knowledge, files, places and their relationships
Reports and analytics	Report definitions, measures, dimensions, source bindings, execution and permitted export
Shared services and interfaces	Classification, features, additional information, configurable lists/forms/details, dashboard composition and supported query patterns

The cultural catalogue, evaluation, indices, recommendations, programmes, wellbeing review and simulation capabilities use this foundation. Shared structure makes reuse possible; it does not make every desired surface or domain extension available automatically.

Sixteen architectural responsibilities

Responsibility	Purpose
Coordination	Initialise services and coordinate multi-step work, including defined failure handling
Communication gate	Route exchanges among registered components
Action execution	Supply common patterns for invoking and handling actions
Validation	Apply format and business checks at the relevant boundaries
Persistence	Store and retrieve data, including supported cache behaviour
Transformation	Convert between defined representations
State distribution	Distribute changes to participating application components
Device signals	Translate supported device input into application signals
Visual presentation	Render the operator's working surfaces
File processing	Handle supported uploads, downloads, and document flows
Identity lifecycle	Manage identities, credentials, sessions, and their states
Entity relationships	Maintain named connections among records
Security framework	Express and enforce configured access rules
UI framework	Provide reusable interface patterns for modules
External interface	Connect the platform to agreed external capabilities
Application identity	Hold the deployment's administrative identity and configuration

The map describes responsibility rather than a list of products. A configured operation may use several services. Failure handling must distinguish a local transaction from an external action that cannot be undone by database rollback.

Follow a typed request

The application sends a typed request for a registered operation. The server resolves the supported process or endpoint, applies the relevant authority and validation, performs the work and returns a result. Registered definitions and generated contracts reduce repeated interface work.

Review the actual path for the operation being delivered. Client presentation is not a substitute for server enforcement, and an assistant invocation requires the same attention to authority as any other entry point. Generated contracts still require compatible deployed versions and validation of custom changes.

Keep execution and evaluation distinct

Process execution coordinates operations, dependencies and human gates. Evaluation interprets permitted evidence against definitions. A recommendation proposes a response; the responsible person chooses what to undertake. A programme carries the resulting development work, and later review considers records and participant experience.

That connection is central to HEPO. It does not mean every part of the P&C sequence is mechanically calculated from the previous one, nor that a reading authorises an action by itself.

Extend at the level the requirement needs

Common Canvas arranges supported views. Shared Module configures supported record-management screens. Code Factory generates artifacts for module or capability extensions. An industry-specific record or workflow may require additional server operations, rules, integration and testing.

A production-quality extension needs access, validation, relationships, audit and lifecycle behaviour established on its own paths. Reusing the framework helps the implementation; it is not a universal security or compatibility guarantee.

Data model | Security model | Deployment topology | Documentation