What the compiler computes
The compiler performs a deterministic transformation of form inputs. It copies the selected modality, language and dialect, annotation, model task, permitted uses, license preference, delivery format, evaluation criteria, timeline, and additional context into a structured sourcing request. It converts the volume input into a whole number and pairs it with the selected unit. The readable preview formats that number with thousands separators.
There is no model call, price calculation, inventory lookup, quality score, or sourcing forecast. A request for 1,000 hours remains 1,000 requested hours; the tool does not convert it into items, tokens, cost, or an availability promise.
Illustrative defaults
The initial example requests Hebrew (Israeli) speech, 1,000 hours, speaker labels and aligned transcripts, and WAV at 48 kHz with a JSONL manifest. These are illustrative inputs, not measured data or universal recommendations. Edit each field to fit your intended use. A user-edited request can still contain unchanged example defaults; review all fields before sending.
Validation and review
Volume must be a whole number from 1 through 1,000,000,000,000. This is an input boundary, not a sourcing capacity claim. Language and delivery format are required. Contact name, work email, organization, and agreement to the privacy notice are required to submit. Text lengths and fixed-choice fields are validated again by the server.
The three stages preserve answers while moving Back and forward. The live specification shows every requirement. Contact details and consent are summarized at the review stage. A request must still be assessed by a person for feasibility, rights, ambiguity, and fit.
Download and submission
The readable specification and JSON file are generated in the browser without a network request. JSON uses schema version 1.0 and identifies itself as a sourcing request. It contains no name, email, organization, website, or attribution data. Downloading does not send a request to Trainset Partners.
Selecting Send sourcing request transmits the form and first-landing attribution to the same-origin submission endpoint. The server saves it and requests an internal email notification. An on-page success message confirms storage; it does not mean inventory has been reserved, a license has been cleared, or an email has arrived. See the privacy notice for storage and retention details.
Evaluation after a brief
Source selection compares the request with documentation and samples. Rights, sample quality, language coverage, and delivery constraints must be checked before a proposal or handoff. Agree thresholds with your technical and legal teams; an automatically generated brief is the starting point for that review.