The Operating Model
The model separates knowledge formation from work initiation, then reconnects them through governed resolution. Inputs update Shared Memory. Requests create Work Objects. Authorised participants assemble context, produce outcomes and return results to the institutional record.
Why one loop
Named workflows are shaped by departments, forms, legacy systems, reporting lines and historical practices. They are essential for discovery because they reveal what enters the organisation, who has authority, which information is required and what outcomes must be produced.
They should not be reproduced as isolated digital pipelines. At the mandate level, most workflows participate in one or more stages of the same operating loop. Designing the shared loop first prevents each new automation from creating another information silo.
The nine stages describe how the institution operates continuously. They are not a delivery schedule. Delivery is sequenced separately, in five scoped waves supported by five capability tracks, described on the transition and implementation page.
Inputs and Requests
Inputs are facts, observations, evidence and changes. They may arrive as reports, records, documents, Executive Director directives, RA 11930 or Strategic Plan requirements, events, media, authorised online messages such as Viber, institutional updates, case evidence or outcome confirmations. Their purpose is to update the institution's understanding.
Requests ask the institution to analyse, monitor compliance, implement a directive, advise, decide, coordinate, deliver training or awareness work, refer, act or resolve. Their purpose is to create a governed obligation and a definition of completion.
An Input and a Request may arrive together. The system records both without confusing them: one changes memory; the other initiates work.
The nine stages
A mandate-relevant source or event enters the organisational boundary.
The system extracts structure, meaning, entities, time, provenance and applicable authority.
Atomic facts, events, relationships and evidence items become governed Data Blocks.
The Data Blocks update entity histories and the institution's current understanding without erasing prior states.
A request creates or updates a governed Work Object with an owner, state, authority, required evidence and completion criteria.
Authorised participants retrieve relevant memory and contribute evidence, analysis, judgement or action.
The Work Object reaches a final governed outcome according to policy and authority.
The system creates a structured Rich Data Block and the required human-readable report, decision, referral or instruction.
Result evidence returns through ingestion, updates memory and supports evaluation of policy and operating practice.
The improvement path
The system can compare intended outcomes with actual results, identify recurring failure patterns and surface opportunities for better coordination or policy. It does not change policy autonomously. Recommendations remain traceable to evidence and enter the appropriate human approval process.