Sync Repo-README from project files
+81
@@ -0,0 +1,81 @@
|
|||||||
|
<!-- codex-wiki-sync:7c634261fb77c981bef55e71 -->
|
||||||
|
|
||||||
|
> Mirrored from `/mnt/DATA/git/govoplan-committee/README.md`.
|
||||||
|
> Origin: `repository`.
|
||||||
|
> Active tasks and changing state belong in Gitea issues; this wiki page is durable project context.
|
||||||
|
|
||||||
|
---
|
||||||
|
# GovOPlaN Committee
|
||||||
|
|
||||||
|
<!-- govoplan-repository-type:start -->
|
||||||
|
**Repository type:** module (domain).
|
||||||
|
<!-- govoplan-repository-type:end -->
|
||||||
|
|
||||||
|
`govoplan-committee` is the GovOPlaN module for committee, board, council, and senate workflows for meetings, agendas, minutes, deliberation, voting, formal decision references, and follow-up tasks.
|
||||||
|
|
||||||
|
The first headless slice exposes a versioned `committee.decision_path`
|
||||||
|
capability. It combines committee meeting context with an effective Mandate,
|
||||||
|
including organization, function, and jurisdiction coverage, with approval,
|
||||||
|
legal bases, evidence, reasoning, and effects to create the shared
|
||||||
|
formal Decision contract. Mandate resolution and Decision persistence remain
|
||||||
|
optional providers. The module intentionally does not yet add HTTP routes,
|
||||||
|
database models, migrations, or WebUI navigation.
|
||||||
|
|
||||||
|
## Initial Ownership
|
||||||
|
|
||||||
|
- committee bodies
|
||||||
|
- meeting agendas
|
||||||
|
- minutes
|
||||||
|
- deliberation/vote context and formal decision references
|
||||||
|
- votes
|
||||||
|
- follow-up assignments
|
||||||
|
|
||||||
|
## Boundaries
|
||||||
|
|
||||||
|
This module does not own:
|
||||||
|
|
||||||
|
- generic task execution
|
||||||
|
- document storage
|
||||||
|
- calendar event storage
|
||||||
|
- the generic formal decision lifecycle; a future Decisions provider owns
|
||||||
|
authority, facts/rules, reasoning, effects, review, correction, and revocation
|
||||||
|
|
||||||
|
Detailed boundary notes are in [docs/COMMITTEE_DOMAIN_BOUNDARY.md](docs/COMMITTEE_DOMAIN_BOUNDARY.md).
|
||||||
|
|
||||||
|
## Integrations
|
||||||
|
|
||||||
|
Expected optional integrations:
|
||||||
|
|
||||||
|
- calendar
|
||||||
|
- docs
|
||||||
|
- files
|
||||||
|
- tasks
|
||||||
|
- workflow
|
||||||
|
- approvals
|
||||||
|
|
||||||
|
## Development Install
|
||||||
|
|
||||||
|
From the core checkout:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
cd /mnt/DATA/git/govoplan-core
|
||||||
|
./.venv/bin/python -m pip install -e ../govoplan-committee
|
||||||
|
```
|
||||||
|
|
||||||
|
Focused manifest verification:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
cd /mnt/DATA/git/govoplan-committee
|
||||||
|
PYTHONPATH=src:/mnt/DATA/git/govoplan-core/src /mnt/DATA/git/govoplan-core/.venv/bin/python -m unittest discover -s tests
|
||||||
|
```
|
||||||
|
|
||||||
|
## Gitea Workflow
|
||||||
|
|
||||||
|
Issue templates are installed under `.gitea/`, and the shared label taxonomy is copied to `docs/gitea-labels.json` with the module label `module/committee`.
|
||||||
|
|
||||||
|
From the core checkout, labels can be synced once a local `GITEA_TOKEN` is available:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
cd /mnt/DATA/git/govoplan-core
|
||||||
|
/mnt/DATA/git/govoplan/tools/gitea/gitea-sync-labels.py --root /mnt/DATA/git/govoplan-committee --apply
|
||||||
|
```
|
||||||
Reference in New Issue
Block a user