Runtime Validation Mental Model Why TypeScript types are not runtime validation and where trust boundaries belong
Phase 12 - DTOs, Zod & Input Validation Volume 04 - Professional Backend
Architecture milestone JSON crosses the network
↓
↓
↓
Phase 12 introduces an explicit runtime validation boundary before controller and service logic.
Static types are not a firewall A TypeScript annotation exists for the compiler and editor. By the time JSON arrives over HTTP, the sender is not constrained by your TypeScript source code. Postman, PowerShell, a browser, a mobile app, or a malicious caller can send any syntactically valid JSON value.
type CreateTaskInput = { projectId: string; title: string; };
// This type cannot stop a network caller from sending: { "projectId": 123, "title": false, "admin": true }
Figure 1 - Trust boundary External caller
↓
↓
↓
↓
↓
Validation belongs at the system boundary because that is where untrusted external data enters trusted application code.
Validation vs business rules vs database constraints Question Best first owner Example
Is this input shaped correctly? Validation schema title is a non-empty string
Is this request allowed by the Service/business logic assignee belongs to workspace domain?
Must this invariant hold for Database constraint foreign key references a real Project persisted rows?
Strong systems usually use all three layers. Validation is not a replacement for database constraints, and database constraints are not a replacement for meaningful application rules.
DTO does not have to mean class In older NestJS examples, DTO usually means a class decorated with class-validator annotations. NestJS 12 adds a first-class schema-first workflow. In this course, a DTO means the validated data shape crossing the HTTP boundary. We infer the TypeScript DTO type from the Zod schema instead of manually duplicating it in a class.
export const createTaskSchema = z.strictObject({ projectId: z.uuid(), title: z.string().trim().min(1).max(200), });
export type CreateTaskDto = z.infer<typeof createTaskSchema>;
The schema is executable at runtime and also produces the TypeScript type. This removes a common source of drift where validation says one thing while a separately maintained interface says another.
Parsing may also transform Validation libraries can do more than return yes/no. Trimming, coercion, defaults, and transformations can change the value that crosses the boundary. For that reason, think in terms of input -> parse -> validated output rather than input -> boolean.
Figure 2 - Parse lifecycle raw JSON value
↓
↓
validated / transformed output
↓
controller parameter
The controller should operate on the parsed output, not on the raw body.
Runtime Validation Mental Model 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 “Runtime Validation Mental Model” 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: Reusable create/update/query schemas integrated into NestJS request handling with useful validation errors.. 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 “Runtime Validation Mental Model” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
List the exact fields accepted by create-task and reject unknown/invalid shapes deliberately.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Assuming TypeScript validates runtime JSON
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.