No. A framework sets what must be true. A process model sets the work that makes it true. Treating the two as the same thing is how organisations end up with a long policy and no operating system, or with a workflow and no test of success.
What each one is allowed to do
A governance framework states outcomes and how they are tested. It belongs to the governing body. Under King V that body oversees data, information and technology, including AI. The framework does not assign the Tuesday task. A management-system standard, such as ISO/IEC 42001, says establish, implement, operate, monitor and improve an AI management system, and it can be certified. It deliberately does not prescribe the full catalogue of management processes. A risk framework such as the NIST AI RMF is a thinking structure: Govern, Map, Measure, Manage. It is not an operating model and not a certificate. Principles set norms. They do not assign work.
A process model does assign work. It names the process, the owner, the trigger, the inputs and the work product. It says what happens next. It is the layer a standard points at and does not replace. EN 18286 is closer to a process description than 42001 is, because it is product- and lifecycle-centric and it requires defined processes at every stage. It is still a standard. It is not the organisation's process model. The organisation still has to decide who owns each stage, what the gate checks, and what record the stage leaves.
Why the collapse happens
The words overlap. "Framework" is used for a standard, a set of principles, a spreadsheet of controls and a piece of software. "Model" is used for a machine-learning model and for an operating model. A vendor that sells a template pack will call it a framework. A vendor that sells a workflow will call it a management system. Neither claim survives contact with the definitions above.
The collapse is also convenient. If a framework is treated as a process model, completing the framework looks like operating the system. If a process model is treated as a framework, the organisation never has to say what outcome the work is supposed to achieve. Both mistakes produce activity. Neither produces a testable system.
How they fit
The order is outcomes, then the process model, then software. The governing body sets the outcomes. The process model turns those outcomes into work. The software runs the work and keeps the evidence. A platform without agreed outcomes implements activity with no test of success. A framework without a process model is a test with nothing to test. A process model without a framework is work with no reason.
Control Objectives for AI Systems (AICOB) is the process model. It sits under the governance framework and above the platforms. Law, standards and internal policy are mapped onto it. A mapping is a claim only when it is explicit: one process-control activity named against a named article, clause or control. King V is mapped onto AICOB. It is not AICOB. POPIA is mapped onto AICOB. It is not AICOB. ISO/IEC 42001 is mapped onto AICOB. It is not AICOB. The EU AI Act, where it reaches a South African organisation, is mapped onto AICOB. It is not a process model either. It is a regulation that requires one.
What this means for the systems that follow
Later articles on King V, POPIA, ISO/IEC 42001 and the EU AI Act (where it applies) each describe a duty written as a system. None of them is, by itself, the organisation's process model. Each is an instrument the process model is asked to meet. The platforms are the environment in which that meeting happens. None of this certifies the organisation or declares it compliant. Those decisions sit with the assessor, the Information Regulator, a notified body where the EU AI Act applies, or the governing body itself. The system makes the work visible so the decision can be made on evidence.