julee.api.requests¶
Pydantic models for API requests. These define the contract between the API and external clients.
Following clean architecture principles, request models delegate validation to domain model class methods and reuse field descriptions to avoid duplication while maintaining single source of truth in the domain layer.
Classes¶
Request model for creating an assembly specification. |
|
Request model for creating a knowledge service query. |
Module Contents¶
- class julee.api.requests.CreateAssemblySpecificationRequest(/, **data)[source]¶
Bases:
pydantic.BaseModelRequest model for creating an assembly specification.
This model defines what clients need to provide when creating a new assembly specification. Validation logic is delegated to the domain model to ensure consistency and avoid duplication.
Fields excluded from client control: - assembly_specification_id: Always generated by the server - status: Always set to DRAFT initially by the server - created_at/updated_at: System-managed timestamps
- class julee.api.requests.CreateKnowledgeServiceQueryRequest(/, **data)[source]¶
Bases:
pydantic.BaseModelRequest model for creating a knowledge service query.
This model defines what clients need to provide when creating a new knowledge service query. Validation logic is delegated to the domain model and descriptions are reused to avoid duplication while maintaining single source of truth in the domain layer.
Fields excluded from client control: - query_id: Always generated by the server - created_at/updated_at: System-managed timestamps