Civic · Workflow
Institutional participation
What would you like to do?
An authority account (collectivité, élu·e, agent) opens its workspace; residents sign, signal, suggest or respond.
End to end
Trigger
An authority account (collectivité, élu·e, agent) opens its workspace; residents sign, signal, suggest or respond.
Inputs
Consultation question; official response text (20+ characters); need status; programme description.
Processing
Only authority roles answer on the record; every state is forward-only and dated; restitutions are mandatory to close a consultation. The platform does not claim any partnership with any institution — participation is by the institution's own account.
User actions
Open consultations, publish local programmes, answer campaigns, needs and suggestions in their own name.
System actions
LP_Consultations::open/advance, LP_Governance::respond_campaign, LP_Governance::answer_need, LP_Suggestions::respond, LP_Governance::publish_program.
Relationships created
Institution answers campaign / need / suggestion; programme published for commune.
Notifications
Every signer, supporter and respondent receives the answer.
Next possible actions
Residents form projects around programmes · Institutions hold permanences as events.
Completion state
Answered on the record (milestone "Official voice").
Engines involved
Each named method exists in the core plugin — the verification harness fails the build if one goes missing.