Architectural decision
Role is not Permission
Job titles describe production work.
Before · Conflated concepts
RolePermission / CapabilityAssignment
After · Explicit boundaries
Relationships
- Production Assignment describes work as Role
Problem and decision
A familiar title is not sufficient evidence of software authority.
Evaluate explicit scoped capabilities independently of role labels.
Alternatives considered
- Authorize by job title
- Authorize by department alone
Tradeoffs and consequences
Authority must be configured and evaluated separately.
A role change cannot silently elevate access.
Related architecture
Related workflows
Current architectural direction; this record does not establish production release.