You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<divclass="subtitle">Interactive horizontal flowchart of the Filecoin Improvement Proposal (FIP) Lifecycle</div>
159
-
<divclass="flowchart-area" id="flowchart-area">
160
-
<svgclass="flowchart-svg" id="fip-svg"></svg>
47
+
48
+
<divclass="test-content">
49
+
<h2>Test Page Working!</h2>
50
+
<p>If you can see this, the basic HTML structure is working correctly.</p>
51
+
<p>The issue might be with the SVG rendering or JavaScript.</p>
161
52
</div>
53
+
162
54
<divclass="feedback-section">
163
55
<b>Community Invitation for Feedback</b>
164
56
This framework is designed to empower robust governance, prioritizing clarity, transparency, and community agency. We warmly invite feedback, suggestions, or concerns regarding any aspect of this lifecycle. Community collaboration is essential in evolving this governance process, ensuring it remains responsive, fair, and effective for the Filecoin ecosystem.
{id: 'discussion',label: 'Discussion',x: 80,y: 180,width: 140,height: 48,details: `<b>Discussion Stage</b><br>This initial phase is meant to facilitate open dialogue, ensuring that any potential proposals are thoroughly debated within the community before formalizing a FIP.<br><i>Rationale:</i> Encourages early collaboration, reducing redundancy and increasing alignment with community priorities.`,roleLabel: 'Governance Facilitator'},
172
-
{id: 'no-fip',label: 'NO FIP',x: 80,y: 320,width: 120,height: 48,details: `<b>No FIP</b><br>The discussion does not result in a formal FIP proposal.`},
173
-
{id: 'fip-draft',label: 'FIP DRAFT',x: 320,y: 180,width: 140,height: 48,details: `<b>FIP Draft</b><br>Formalizes ideas from discussions into structured proposals clearly outlining intent, implementation details, and anticipated impacts.<br><i>Rationale:</i> Enhances proposal quality and readability, setting clear expectations and standards.`},
174
-
{id: 'fip-editors',label: 'FIP Editors',x: 500,y: 180,width: 140,height: 48,details: `<b>FIP Editors</b><br>Subject matter experts or dedicated editors analyze drafts to provide critical and constructive feedback.<br><i>Rationale:</i> Maintains high-quality proposals, reducing future complications or ambiguities.`,roleLabel: 'FIP Editors'},
175
-
{id: 'fip-assigned',label: 'FIP ASSIGNED',x: 700,y: 180,width: 140,height: 48,details: `<b>FIP Assigned</b><br>Formally assigns the FIP a unique identifier and places it in an official governance pipeline.<br><i>Rationale:</i> Provides traceability, clarity, and structure to the lifecycle management.`},
176
-
{id: 'timelock',label: 'TIMELOCK',x: 900,y: 180,width: 140,height: 48,details: `<b>Timelock</b><br>Introduces a deliberate delay before implementation, allowing community and stakeholders sufficient time for comprehensive review.<br><i>Rationale:</i> Prevents rash or inadequately vetted changes, improving decision-making quality.`},
177
-
{id: 'community-veto',label: 'Community Veto',x: 1150,y: 100,width: 140,height: 48,details: `<b>Community Veto</b><br>Enables community-driven rejection through an adaptive quorum model rather than traditional thresholds.<br><i>Rationale:</i> Reduces voter fatigue and apathy, ensuring that significant opposition (rather than inactivity) stops proposals.`},
178
-
{id: 'security-veto',label: 'Security Veto',x: 1150,y: 260,width: 140,height: 48,details: `<b>Security Veto</b><br>The Security Council holds veto power over proposals posing substantial network security risks, requiring supermajority consensus.<br><i>Rationale:</i> Prioritizes network security and stability, ensuring technical integrity takes precedence.`},
179
-
{id: 'veto-outcome',label: 'Veto Outcome',x: 1400,y: 180,width: 160,height: 48,details: `Veto is a governance block that halts a proposal. After the timelock, votes are tallied, quorum checked, then veto counts are compared against community or security council thresholds. It represents a formal blockade—either by the broader community or by a specialized Security Council—signaling that critical concerns remain unresolved.`},
180
-
{id: 'veto-successful',label: 'Veto Successful',x: 1650,y: 100,width: 140,height: 48,details: `<b>Veto Successful</b><br>Proposal is transparently communicated as rejected, ending the process clearly.<br><i>Rationale:</i> Offers transparency and definitive resolution, reducing confusion or repeated proposal iterations.`},
181
-
{id: 'no-veto',label: 'No Veto',x: 1650,y: 260,width: 140,height: 48,details: `<b>No Veto</b><br>If no significant concerns are raised during the veto period, the proposal proceeds to acceptance.<br><i>Rationale:</i> Streamlines the process for uncontroversial proposals while maintaining the safety net of the veto period.`},
182
-
{id: 'fip-rejected',label: 'FIP Rejected',x: 1850,y: 100,width: 140,height: 48,details: `<b>FIP Rejected</b><br>The proposal is rejected and the process ends here.`},
183
-
{id: 'fip-accepted',label: 'FIP Accepted',x: 1850,y: 260,width: 140,height: 48,details: `<b>FIP Accepted</b><br>The proposal is accepted and moves to the implementation stage.`},
184
-
{id: 'implementers-call',label: "Implementers' Call",x: 2050,y: 260,width: 160,height: 48,details: `<b>Implementers' Call</b><br>Ensures alignment and understanding among those tasked with implementing the accepted FIP.<br><i>Rationale:</i> Secures efficient, coherent execution of proposals, avoiding misinterpretation or misalignment.`},
185
-
{id: 'fip-final',label: 'FIP Final',x: 2250,y: 260,width: 140,height: 48,details: `<b>FIP Final</b><br>Finalized proposals are clearly documented and archived for community reference, ensuring historical clarity and accountability.<br><i>Rationale:</i> Preserves institutional knowledge, facilitating ongoing transparency and accountability.`}
0 commit comments