Transition of teams and functions
During Candeia’s formation, automation, bots and operators may maintain administrative or technical tasks where legally permitted. The purpose of transition is to hand public functions to legitimately selected people and collegiate bodies without losing data, continuity, evidence or accountability.

Candeia still depends on direct development work for several functions. The transition to institutional responsibilities will happen only when real people, rules and processes exist to assume them.
In brief
Know what is currently automated or provisional
Map tasks, data, credentials, decisions and dependencies.
Separate assistance from competence
A bot may execute a rule or routine; it does not acquire sovereignty or public office by doing so.
A qualified person receives context and access
Documentation, audit records, state and responsibilities must be transferred in an auditable manner.
Remove the provisional arrangement without breaking the service
The handover must preserve records, appeal rights and recovery capability.
How it works
Identify automated, operational and sovereign tasks.
Complete the appropriate public selection, election or appointment.
Hand over documentation, access, history and responsibilities.
Confirm continuity and remove unnecessary provisional privileges.
Limits and safeguards
- Automation cannot be “promoted” into a public office-holder.
- A person who operated a provisional system acquires no vested right to a permanent office.
- The handover must revoke obsolete privileges and preserve audit records, evidence and the possibility of rollback or recovery where appropriate.
For citizens, the change should look like institutional continuity, not an opaque change of owner. Those who begin making decisions must be legitimate; those leaving the function must lose incompatible access; and the history cannot disappear during the handover.