Llama 3 70B
Earlier model guide Explore current task guides ↗
Writing. Create writing from a reviewed request. Availability depends on your plan and configured models.
Start creating in Chat ↗Make a draft from a reviewed brief
Llama 3 70B is the configured writing route for a text result you can inspect and continue.
Give the document a job
Name the audience, approved coffee facts and desired message. Review the Writing request, selected context and cost before asking for the draft.
Read the saved version
Open the document, check names and claims, then revise or branch from the exact version that deserves another direction.
A generated claim still needs checking
Selected context guides the writing; it does not verify every sentence. Follow the writing guide or see how saved writing can continue.
See an example workflow
An illustrative example. Review current inputs, settings and the quote in your workspace.
- StartSelect approved coffee facts.
- Request or actionChoose Writing and review the Llama 3 70B route.
- ReviewFact-check the draft against the selected source.
- Saved resultA saved document version.
- ContinueRevise or branch from the chosen version.
Example AskGL request
Write a short coffee-blend introduction using only the approved name and origin in the selected brief. Avoid invented claims.
Replace sample facts with approved details. Source selection and later review, comparison or packaging happen in the workspace, outside the prompt text.
Continue from the output
Good to know.
Creation notes
Prepare your starting point
A writing request needs a purpose, audience, length and approved facts. Keep background information separate from the deliverable. Select current Knowledge or a content record when the draft depends on saved details, and require missing information to be omitted rather than invented.
Writing workflowReview what you keep
Read names, dates and claims before judging style. Ask for one focused revision of the selected draft and compare what improved and what was lost. Native document editing is a separate supported action; a generated paragraph does not automatically update its factual source.
Compare related modelsCommon questions
Does an earlier guide mean this model is deprecated?
Guide age and model lifecycle are different. Check current catalog status and workspace availability; do not infer retirement from the route name.
Can another model replace it silently?
Choose a compatible replacement explicitly and review a fresh quote. Keep the recorded original model and its saved results identifiable.