Operational Core — The Records Behind the Work
Manage the people, work, events, communication, knowledge, and relationships that support HEPO's three offerings alongside existing business systems.
Maintain policies, knowledge articles, briefs, and structured content with their categories, media, and relevant records.
Content is HEPO's module for maintaining and presenting the organisation's knowledge. Authors create entries such as policies, knowledge articles, programme briefs, and news. Classification, structured information, media, and relationships help readers find the entry in the context where it matters.
Content supplies the knowledge record used by the offerings. A programme can refer to its brief; a project can refer to an instruction; retrieval can use relevant material when answering a question.
A new participant needs the instructions relevant to their role and first project. The organisation can connect the appropriate content to that context and present the entry with its supporting information. The reader can then follow related material instead of relying on a filename to establish applicability.
The author still needs to maintain the content. A connected policy can be out of date, and a category alone cannot establish its authority. Publication rules and responsibility for review make the knowledge useful over time.
| Element | Practical purpose |
|---|---|
| Type and classification | Identify the kind of content and how it is organised |
| Body | Present the explanation, instruction, or account |
| Structured information and features | Hold additional details in supported forms rather than burying everything in prose |
| Media assignments | Connect documents, images, or video to the entry |
| Related records and hierarchy | Show what the entry concerns and how it relates to other knowledge |
| Publishing configuration | Establish the supported presentation and publication behaviour |
The authoring and reader experiences have different jobs. Authors manage and compose the material. Readers encounter its body, features, related records, and other configured blocks through the content experience.
The original idea of a living index is concrete here: a brief connects to a programme, a policy to the work it concerns, and a reference to related content. These connections help users and configured retrieval find relevant information.
The assistant can use supported retrieval and record operations. It cannot treat every stored document as current, authoritative, or automatically applicable. The selected sources and their context still matter to the answer.
Content owners decide which material governs the work and who keeps it current. Consultants help structure the knowledge around actual questions. Implementers configure classifications, supported blocks, relationships, and publication surfaces.
Walk one programme brief from authoring to its reader view, with a linked document and a related project. Check that the intended reader can find the relevant material and that restricted content remains restricted.
Media & Storage holds the assets; Relationships explains the connections.