How Hakiki executes.
Hakiki is not a form app. It is a strictly structured workflow engine designed to execute operational procedures securely and immutably.
The Path to Immutability.
Every checklist executed in Hakiki follows a rigid, mathematically verifiable lifecycle. Operations are governed centrally, verified at the perimeter, and locked in the ledger.
Global Admin defines the rigid structure using the Node Builder.
requiresSignoff: true
}
An operator starts the checklist, instantiating an active Execution bound to the Template version.
The system intercepts inputs. Does the user have permission to submit this data?
Completion logic hashes the state. The execution is forever locked against future edits.
Authoring
Global and Tenant administrators drag-and-drop structural nodes to construct templates. Nodes define mandatory files, signatures, and input shapes. Templates are versioned like Git branches.
Orchestration
When an operator starts a procedure, Hakiki clones the Template Version and creates a totally isolated Execution Instance. The rules are locked at instantiation.
Enforcement
Every node evaluates incoming data against RBAC (Role-Based Access Control). If a user attempts to bypass a structural step, the validation gate rejects the payload.
Ledger Lock
Upon completion, the execution is cryptographically hashed. All PostgreSQL DB rows move to an immutable state. Future edits are structurally impossible.