47 lines
1.1 KiB
Markdown
47 lines
1.1 KiB
Markdown
# Committee Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Committee, board, council, and senate workflows for meetings, agendas, minutes, decisions, voting, and follow-up tasks.
|
|
|
|
## Owns
|
|
|
|
- committee bodies
|
|
- meeting agendas
|
|
- minutes
|
|
- decision records
|
|
- votes
|
|
- follow-up assignments
|
|
|
|
## Does Not Own
|
|
|
|
- generic task execution
|
|
- document storage
|
|
- calendar event storage
|
|
|
|
## Integration Candidates
|
|
|
|
- calendar
|
|
- docs
|
|
- files
|
|
- tasks
|
|
- workflow
|
|
- approvals
|
|
|
|
## Seed State
|
|
|
|
The current repository state is intentionally small:
|
|
|
|
- module manifest and entry point
|
|
- tenant-level permission definitions
|
|
- manager and viewer role templates
|
|
- documentation topic describing the module boundary
|
|
- Gitea issue workflow templates
|
|
- manifest contract test
|
|
|
|
No runtime API, database model, migration, WebUI route, or navigation item is registered yet. The first implementation slice should preserve the boundary above and only add user-visible surfaces once the workflow model is clear.
|
|
|
|
## First Implementation Slice
|
|
|
|
Define committee body, meeting, agenda item, decision, vote, minute, and follow-up task references.
|