Expand description
Transport / DTO types used at port boundaries.
These types live in the application layer (not domain) because they model the wire shape — OpenAI-compatible chat envelopes, vector-search hits, rerank responses — rather than the invariants the domain layer enforces.
Re-exports§
pub use chat_request::ChatRequest;pub use chat_response::ChatResponse;pub use enrichment_messages::ChatMessageDto;pub use enrichment_messages::ContentPart;pub use enrichment_messages::EnrichmentMessages;pub use enrichment_messages::MessageContent;pub use enrichment_messages::ToolCallDto;pub use enrichment_messages::ToolCallFunction;pub use enrichment_messages::enrichment_messages_from_json;pub use enrichment_messages::enrichment_messages_to_json;pub use merge_result::MergeResult;pub use rerank_result::RerankResult;pub use search_hit::SearchHit;pub use search_hit::SearchHitMetadata;
Modules§
- chat_
request - OpenAI-compatible chat-completion request envelope.
- chat_
response - OpenAI-compatible chat-completion response envelope.
- enrichment_
messages - Typed OpenAI-compatible chat-message DTOs used by the enrichment pipeline (§3 + §4 + H-5 refactor).
- merge_
result - Merge-result DTO (POC
smos/models.py:140-159). - rerank_
result - Rerank-result DTO (POC
smos/models.py:133-139). - search_
hit - Vector-search hit DTO.
Structs§
- Merge
Candidate - One pool member that survived the cosine merge threshold.
- NliResult
- Full NLI verdict for a fact pair.
- NliScores
- Per-label softmax scores produced by an NLI classifier.