Ownership, Assignment & Service-Level Policies Enforce relationship-aware policies where trusted resource context exists
Phase 19 - Authorization, Ownership, RBAC & Permissions Volume 05 - Authentication & Security
v
v
v
Phase 19 transforms verified identity into contextual, server-side authorization decisions.
Ownership is a relationship, not a boolean TaskFlow does not currently have a Task.ownerId. It has workspace membership and task assignment. We therefore teach the real domain relationship instead of inventing an owner field just to demonstrate authorization.
Caller Task relationship Update?
MEMBER Task.assigneeId == current TaskFlow user Yes
if (ROLE_PERMISSIONS[role].has(Permission.TASK_UPDATE_ANY)) { return true } return ROLE_PERMISSIONS[role].has(Permission.TASK_UPDATE_ASSIGNED) && task.assigneeId === user.id
assigneeId comes from database state after access-scoped loading. The browser cannot make itself the assignee by sending a userId field and thereby bypass authorization.
Authorization and business rules compose First decide whether the caller may attempt the operation. Then Phase 14 invariants still decide whether the operation itself is valid. Permission does not bypass business rules.
Authentication answers who the request represents. Treating decoded or client-supplied identity as trusted is a security boundary failure.
Restate the goal of “Ownership Assignment and Service Level Policies” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: credentials/session → token → verification → trusted identity → protected operation. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Permission model + guards/policies protecting TaskFlow workspace/task actions with deliberate 401/403/404 semantics.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
const token = readBearerToken(request);
const claims = await verifier.verify(token);
request.user = {
id: claims.sub,
email: claims.email,
};Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Inspect whether a token exists, whether it is expired, which issuer/audience signed it, and what the API verifier expects.
Trust only verified server claims; never repair identity by accepting a client-sent user id.
Without copying the final source, create a second small scenario that applies “Ownership Assignment and Service Level Policies” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Write a matrix test covering at least owner, member, outsider, unauthenticated caller, and missing resource.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Role strings checked inconsistently in every route
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.