49 lines
1.2 KiB
Markdown
49 lines
1.2 KiB
Markdown
# Permits Domain Boundary
|
|
|
|
## Purpose
|
|
|
|
Permit and license workflows for applications, renewals, conditions, inspections, objections, revocations, and compliance evidence.
|
|
|
|
## Owns
|
|
|
|
- permit application lifecycle
|
|
- license and permit records
|
|
- conditions
|
|
- renewals
|
|
- objections
|
|
- revocation state
|
|
- inspection handoffs
|
|
|
|
## Does Not Own
|
|
|
|
- generic case engine
|
|
- inspection checklist execution
|
|
- certificate verification registry
|
|
|
|
## Integration Candidates
|
|
|
|
- cases
|
|
- inspections
|
|
- forms-runtime
|
|
- files
|
|
- portal
|
|
- certificates
|
|
- records
|
|
|
|
## 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 permit type, application, decision, condition, renewal, objection, revocation, and inspection link records.
|