47 lines
1.1 KiB
Markdown
47 lines
1.1 KiB
Markdown
# Contracts Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Contract register for renewals, obligations, responsible units, documents, sign-off chains, and vendor or partner references.
|
|
|
|
## Owns
|
|
|
|
- contract register
|
|
- renewal reminders
|
|
- obligation tracking
|
|
- responsible-unit assignment
|
|
- sign-off chain references
|
|
- vendor and partner links
|
|
|
|
## Does Not Own
|
|
|
|
- procurement request execution
|
|
- document storage
|
|
- payment scheduling
|
|
|
|
## Integration Candidates
|
|
|
|
- procurement
|
|
- approvals
|
|
- files
|
|
- records
|
|
- notifications
|
|
- ledger
|
|
|
|
## 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 contract record, party, renewal, obligation, responsible unit, and document reference concepts.
|