QAVE Studio Docs
QAVE Studio Docs
Sign inGet started — the Studio loop
Getting StartedFirst assurance runQuick assure
ConceptsLifecycleGlossaryHow QAVE Studio worksComing soon
Account & workspaceSignup and loginPeopleDemo creditsRolesSettings
Generate simulation suitesContext templatePII and field enhanceDimensionsAgents and plannerDraft review and Save
ExportExport formatsExport formats (detail)
Assurance SDKSDK overviewQAVE Studio suite fetch APIAgent and JSONL queueLangfuse bridge
Execute and tracesRecipe chatbot (reference SUT)TracingFetch tracing
AssureEvaluate APIRubrics and evidenceReading scores
History
WorkbenchGolden data
CoverageCoverage dashboardCoverage strategiesCoverage advisorTest case quality
RAG AssuranceRAG runsRAG datasetsRAG analytics
Project evalsError analysisUnderstanding scores
Studio guidesDimensionsTuplesConversation modesMulti-lingual testingWorkflowsHuman reviewBest practices
ReferenceAPI and packagesTroubleshooting
Generate

Context template

Capture the system-under-test context that drives dimensions and planning.

The context template is the single source of truth describing the target AI system for generation.

Form and versions

  • Section A structured fields describe the product, users, risks, and behaviour.
  • Submit always creates a new version and requires a template name (1–50 characters).
  • Next resumes the selected version (does not create a new version).
  • Use the version picker (v{N} - {name}) to load a prior version.
  • Next stays disabled when no version is selected, the version is REJECTED / still DRAFT, or otherwise ineligible.

Additional context files

  • Optional multi-file attachments: docx, pdf, txt, md (5 MB per file).
  • Attachments are LLM context only — they never mutate form fields.
  • Auto-populate form from upload is removed.

APIs (names as in code)

POST /projects/{id}/context-template
GET  /projects/{id}/context-template/versions
GET  /projects/{id}/context-template/versions/{n}
POST /projects/{id}/context-template/submit
POST /projects/{id}/context-template/{template_id}/approve

Responses include name, has_enhanced_fields, and pii_skipped.

Generate simulation suites

Context template through draft review to an approved suite — the Generation pipeline.

PII and field enhance

Optional PII scrub before cloud LLM calls, then synchronous field enhancement.

On this page

Form and versionsAdditional context filesAPIs (names as in code)