Relationships is the shared capability for connecting HEPO records with a defined meaning. A person can be assigned to a unit, work can belong to a project, and a document can support a review. Users navigate those connections; configured processes, retrieval, and evaluation can use them as context.

The connection matters as much as the two records. Knowing that a person reports to a manager says something different from knowing that the same two people attended a meeting.

Follow a work item through its context

A blocked work item belongs to a project. A meeting concerns the blockage, a thread records the follow-up, and a document supplies the missing information. Those links help a reviewer move from the current work state to the relevant account of what happened.

The relationships must be recorded or established through a supported operation. HEPO does not automatically know every meaningful connection, and two linked events do not establish that one caused the other.

Types and assignments have distinct jobs

Relationship types name the kind of connection. The organisation's vocabulary may include reporting, participation, responsibility, or a link between a subject and supporting information.

Assignments place a record in a particular context, such as a person in a programme or media on a content entry. The relevant assignment can carry its own details and lifecycle.

Related views expose the supported connections to a permitted reader. The useful result is a navigable context, with enough meaning to understand why records are connected.

The supported entity types and operations determine which links can be created and used. A relationship framework does not imply that every arbitrary pair has a complete implemented workflow.

Human navigation and machine interpretation

For a reviewer, a named connection helps answer what relates to this task, person, or decision. For the assistant and evaluation capabilities, it supplies structured context that can complement text and other evidence.

That context improves the question the system can address, but it does not guarantee a correct inference. A reporting relationship does not automatically grant access, and a related document does not automatically become authoritative. Security and Data Integrity govern the relevant operations and information.

Author the connections that matter

Business owners and consultants define the meanings worth recording. Implementers configure supported types and assignment paths. A useful first walkthrough follows a person, a work item, a project, and an event, checking what each connection means and who may inspect or change it.

These connections are a shared foundation for P&C interpretation, process coordination, and the connected information explored in Simulation & Gamification.

Operational Core | Platform overview