Business Validation & Time-Based Policies Why semantically valid state needs more than Zod request validation
Phase 14 - Service & Business Logic Architecture Volume 04 - Professional Backend
v
v
Phase 14 turns CRUD-oriented service methods into explicit application rules and workflows while keeping infrastructure simple.
Business validation is not the same as transport validation Phase 12 protects the request boundary. Phase 14 protects the application state. These validations run at different moments and answer different questions.
Is dueAt a valid ISO datetime? Zod 400 BAD_REQUEST
Does this course allow a new past due date? TasksService 400 DUE_DATE_IN_PAST
Does projectId exist? TasksService + DB 404 PROJECT_NOT_FOUND
Is assigneeId a UUID? Zod 400 BAD_REQUEST
Is assignee a Workspace member? TasksService 409 ASSIGNEE_NOT_WORKSPACE_M EMBER
A policy may use current time A due-date-in-the-past rule depends on application meaning and the current clock. It is not just a string-format rule. The service therefore parses the already validated timestamp and compares it with the current time.
private assertDueDate(dueAt?: string | null): void { if (!dueAt) return; if (new Date(dueAt).getTime() < Date.now()) { throw new DueDateInPastException(); } }
Be careful with clocks Time-based business rules eventually deserve a controllable Clock dependency in heavily tested domains. We do not introduce that abstraction yet because formal unit testing and time simulation arrive later. The book calls out the trade-off so the learner understands why Date.now() may later become a seam.
If the frontend also warns about past dates, that improves UX, but the backend remains authoritative. Client validation is convenience; server business logic protects the system.
Business Validation and Time Based Policies matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.
Restate the goal of “Business Validation and Time Based Policies” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: untrusted input → runtime schema → validated value → business rule → safe 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: Refactored task service with explicit policies/invariants and thin controllers.. 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 CreateTaskSchema = z.object({
title: z.string().trim().min(1).max(160),
priority: z.enum(["LOW", "MEDIUM", "HIGH"]),
});
const input = CreateTaskSchema.parse(requestBody);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.
Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.
Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.
Without copying the final source, create a second small scenario that applies “Business Validation and Time Based Policies” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Test the rule without booting the whole web server where practical.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.God services with hundreds of unrelated lines
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.