- WHY: enforce identity-only contract boundaries for policy orchestration - WHAT: add thalos-owned policy contracts, adapters, and grpc translation surfaces - RULE: apply workspace dependency graph and identity ownership constraints
863 B
863 B
Token Policy and Use Cases
Use-Case Boundaries
IIssueIdentityTokenUseCase: orchestrates token issuance behavior.IEvaluateIdentityPolicyUseCase: orchestrates policy evaluation behavior.IIdentityTokenReadPort: DAL-facing identity token boundary.IIdentityPolicyContextReadPort: DAL/integration-facing identity policy context boundary.
Contract Integration
- Policy orchestration uses Thalos-owned transport-neutral identity contracts.
- gRPC translation boundaries are isolated behind
IIdentityPolicyGrpcContractAdapter. - Service contracts remain transport-neutral at the application boundary.
Policy Baseline
- Token issuance and policy evaluation are orchestrated in service use cases.
- Data retrieval and persistence details remain in thalos-dal and identity adapters.
- Protocol adaptation remains outside use-case logic.