> For the complete documentation index, see [llms.txt](https://docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services/2025-delivery-assurance-contract-updates/product-committee/byron-network-constitutional-committee-voting-tool.md).

# Byron Network - Constitutional Committee Voting Tool

{% hint style="danger" %}
**ARCHIVED**

This page has been archived. It's content might be outdated.
{% endhint %}

* Supplier: Byron Network OU
* Contract Name: Constitutional Committee Voting Tool
* Contract Date: 1st April 2025 - 31st July 2025

### Contract Details

<table data-full-width="true"><thead><tr><th width="153.11114501953125">Milestone Name</th><th width="161">Milestone Completion Date</th><th width="394.4444580078125">Milestone Description</th><th>Milestone Amount</th><th width="162.5555419921875">Milestone Status<select><option value="tuQZQU0qZdoU" label="Not Started" color="blue"></option><option value="egD9AGmh1U3S" label="On Track" color="blue"></option><option value="Re3cd2eP2WaH" label="Complete" color="blue"></option><option value="bEAnsa2nIuMk" label="Delayed" color="blue"></option></select></th><th>Milestone Acceptance Form</th></tr></thead><tbody><tr><td>Milestone 1 - Design Approach</td><td>To be completed by 11th April 2025</td><td><p>Map out all key user flows for both phases (CC election and making the tool reusable) and define the approach to develop them.<br></p><p><strong>Acceptance Criteria:</strong></p><ul><li><p>Meet WCAG 3.0 AA standards for accessibility</p><ul><li>User flows and mockups meeting requirements described in Deliverablesing<br>testing into the CI/CD pipeline</li></ul></li></ul></td><td>€11,800</td><td><span data-option="Re3cd2eP2WaH">Complete</span></td><td></td></tr><tr><td><p>Milestone 2 -</p><p>Phase 1 /<br>Development of CC<br>candidates registration</p></td><td>The initial structure and registration<br>of candidates must be developed,<br>tested, and approved in April 2025.<br><br>After the first release, follow the CC election dates - registration for<br>candidates starts on the 1st of May<br>2025.</td><td><p>An action plan for the first milestone related to delivering registration functionalities for CC candidates needed to support CC election, test it,<br>and make it production ready.<br><br><strong>Acceptance Criteria:</strong><br>User should be able to browse through<br>open ballots</p><ul><li>User should be able to see details of a<br>ballot</li><li><p>Description</p><ul><li>Application Start, Application End,<br>Voting Start, Voting End, and<br>Results dates, parameters on<br>voters and vote tallying</li><li>User should be able to browse a list of<br>candidates<br>○ Avatar/Profile picture<br>○ Full name<br>○ Short summary</li><li>User should be able to check details about<br>a candidate<br>○ Avatar/Profile picture<br>○ Full name<br>○ E-mail<br>○ Short summary<br>○ If a group candidate, then be able<br>to supply individuals' names<br>○ Links to social media profiles<br></li></ul></li><li><p>User should be able to submit their<br>candidacy via a form</p><ul><li><p>The form should require providing<br>details visible in the candidate’s<br>details view</p><ul><li>Avatar/Profile picture</li><li><p>Short text fields (one line)</p><ul><li>Full name</li><li>E-mail</li><li>Social media<br>profiles</li><li>Long text fields (multiple<br>lines)</li></ul></li><li>Questions to answer with<br>bullet points, allowing for<br>one selection</li><li>Checkboxes to accept<br>Terms &#x26; Conditions and<br>Privacy Policy</li></ul></li></ul></li><li>User should be able to edit their candidacy</li><li>User should be able to remove their<br>candidacy</li></ul></td><td>€19,400</td><td><span data-option="Re3cd2eP2WaH">Complete</span></td><td><a href="https://drive.google.com/file/d/1XTHwcwjkpmdtyeHR4LXBvHnsxeofPp48/view?usp=drive_link">https://drive.google.com/file/d/1XTHwcwjkpmdtyeHR4LXBvHnsxeofPp48/view?usp=drive_link</a></td></tr><tr><td>Milestone 3 - Phase 1 /<br>Development of CC voting</td><td><p>The initial voting must be<br>developed, tested, and approved in<br>May 2025.</p><p><br>After the first release, follow the CC election dates - voting starts on the 10th of June 2025.</p></td><td><p>An action plan for the first milestone related to delivering voting functionalities to support CC<br>election needs, test it, and make it production<br>ready.</p><p><strong>Acceptance Criteria</strong></p><ul><li><p>User should be able to vote on candidates<br>using their wallet connection</p><ul><li>It should be a multiselection<br>supermajority vote</li><li>Allow each user selection of / cast<br>votes for up to 5 people</li><li>Use CIP-30 for wallet connectivity</li><li>Comply with CIP-10 by registering<br>a metadata key for voting</li><li>Utilise CF-Cardano-Ballot<br>functionalities</li><li>User should be able to vote on candidates<br>using CLI</li><li>Use CIP-93 and CIP-94 for<br>reference</li></ul></li><li>User should be able to see the results of the voting once it’s completed</li><li><p>Users should be able to verify that their vote<br>was included in the vote</p><ul><li>Utilise CF-Cardano-Ballot<br>functionalities</li></ul></li></ul></td><td>€19,000</td><td><span data-option="Re3cd2eP2WaH">Complete</span></td><td><a href="https://drive.google.com/file/d/1MakHbVdX_fbUVlcScerwXjaFbz1OhLlC/view?usp=drive_link">https://drive.google.com/file/d/1MakHbVdX_fbUVlcScerwXjaFbz1OhLlC/view?usp=drive_link</a></td></tr><tr><td>Milestone 4 -Phase 2 /<br>Refinement phase to plan<br>making the tool re-usable</td><td>To be completed by July 2025.</td><td><p>Refine the flows, allowing community members to<br>create polls with this tool via GovTool.</p><p><strong>Acceptance Criteria</strong></p><ul><li>Meet WCAG 3.0 AA standards for<br>accessibility</li><li>User flows and mockups meeting<br>requirements described in Deliverables</li></ul></td><td>€11,300</td><td><span data-option="tuQZQU0qZdoU">Not Started</span></td><td></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.intersectmbo.org/intersect-knowledge-base/archive/cardano-budget-archive/intersect-operational-services/2025-delivery-assurance-contract-updates/product-committee/byron-network-constitutional-committee-voting-tool.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.