💡 Revise Guardrail Script Inclusion UI for New Constitution Proposal Type
Los mantenedores suelen responder en 1 día
@mesudip ya está trabajando en esto.
Desde el 3/11/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Area
Proposal Pillar
Is there new design needed?
Yes
What?
The current UI for creating a proposal of the "New Constitution" type in the GovTool proposal discussion forum includes a checkbox:
"Do you want to include new guardrail scripts?"
This checkbox is misleading, as not including new guardrail scripts results in deleting all existing guardrails, which is a drastic and potentially unintended action.
This task proposes to revise the UI and interaction flow to:
- Make guardrail inclusion default and explicit
- Prevent unintentional deletion of existing guardrails
- Communicate the consequences of excluding them clearly
Why?
- The current checkbox creates confusion and might mislead proposers into unintentionally removing important security mechanisms.
- Deleting all guardrails without a strong confirmation step is too radical to be a single toggle.
- Clearer communication helps align user expectations with governance protocol rules under CIP-1694.
How?
- Replace the checkbox with a descriptive UI element, such as:
- A toggle with explicit labels like “Include guardrail scripts (recommended)” vs. “Remove all existing guardrails (advanced)”
- Or, a mandatory section where all included guardrails must be listed and reviewed
- Add a warning tooltip or modal when a user attempts to exclude guardrails, explaining:
- That doing so deletes all existing guardrails
- This action may have serious protocol implications
- Ensure the default behavior includes guardrails, and require a conscious override to remove them
(Optional) User Story with acceptance criteria
As a community member proposing a new constitution,
I want the interface to clearly show whether I'm including or removing guardrail scripts,
So that I don’t accidentally delete critical security scripts and undermine protocol safety.
Acceptance Criteria
- The guardrail checkbox is replaced with a more descriptive UI control
- The default behavior includes existing guardrails
- A user choosing to exclude guardrails must confirm this choice explicitly
- A warning tooltip or modal explains the consequence of removing guardrails
- The final proposal draft reflects the correct choice before submission
- Lenguaje dominante
- HTML
- Estrellas
- 22
- Forks
- 28
- Merge medio
- 17 h 44 min
- PR fusionados (30 d)
- 27
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de IntersectMBO/govtool
-
🏗 Infrastructure
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
IntersectMBO/govtool#4297 ·
Los mantenedores suelen responder en 1 día
-
⚙ Backend 📜 Proposal Pillar 2026-Revamp
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
IntersectMBO/govtool#4279 ·
Los mantenedores suelen responder en 1 día
-
frontend: API provider switchAbierto🖥 Frontend 2026-Revamp
Dificultad 4/5 3-5 días Aptitud para principiantes 65/100
IntersectMBO/govtool#4275 ·
Los mantenedores suelen responder en 1 día
-
🐛 Bug
Dificultad 4/5 3-5 días Aptitud para principiantes 58/100
IntersectMBO/govtool#4274 ·
Los mantenedores suelen responder en 1 día
-
💡 Feature idea
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
IntersectMBO/govtool#4268 ·
Los mantenedores suelen responder en 1 día