46 lines
1.1 KiB
Markdown
46 lines
1.1 KiB
Markdown
# Transparency Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Transparency and FOI workflows for public-records requests, publication duties, disclosure workflows, redaction, and transparency portals.
|
|
|
|
## Owns
|
|
|
|
- FOI and public-records requests
|
|
- publication duties
|
|
- disclosure workflow state
|
|
- redaction review records
|
|
- transparency portal handoff
|
|
|
|
## Does Not Own
|
|
|
|
- records classification master data
|
|
- document binary storage
|
|
- audit log storage
|
|
|
|
## Integration Candidates
|
|
|
|
- records
|
|
- files
|
|
- dms
|
|
- portal
|
|
- audit
|
|
- policy
|
|
|
|
## 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 transparency request, disclosure review, redaction task, publication duty, and portal publication records.
|