IntersectMBO / IntersectMBO/govtool
Improve Governance Action context and activity APIs
- Dominant language
- HTML
- Stars
- 21
- Forks
- 29
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 7
Description
## Outcome
Governance Actions include the context and activity needed to understand their lifecycle and participation.
## Scope
- Define Governance Action context and activity models
- Expose lifecycle events, voting activity, past votes, and rationales
- Include live vote metrics and relevant voting-power context
- Define consistency and freshness expectations across providers
## Acceptance criteria
- [ ] Scope is decomposed into independently deliverable child issues.
- [ ] Architecture and API decisions are linked from this issue.
- [ ] Test, documentation, observability, rollout, and failure behavior are defined where applicable.
- [ ] Epic exit criteria are verified before closure.
## Planning note
This is a 2026 GovTool revamp work item. Its child features and tasks should be added as the scope is refined.
Contributor guide
Research direction
Start by decomposing the context and activity scope into independently deliverable child issues. Define the architecture and API decisions, then identify applicable test, documentation, observability, rollout, and failure-behavior work. The epic is done when the child scope is delivered and its exit criteria are verified.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100