Skip to content
Technology How it works Breeder — Hyperion Burner — Aegis Burner — MetroVolt AI-Native Architecture Magnets Fuel cycle Safety Roadmap
Solutions AI & Data Centers Defense & Government Grid & Baseload Neutron Detection Quantum
Learn Technical Library
Proof Publications Whitepapers Technical Library Open Science & Reproducibility The Honest Gates
Company About / Mission Leadership Environment Health & Safety Investors Careers Press Contact
3D Model
AI Architecture › L5 · Applications & Copilots
L5 · Applications & Copilots

Prompt Construction and Templates

Structured, versioned prompt templates that fix each copilot's role, constraints, tool contract, and output schema — so behavior is reproducible and testable.

THE STACK · click to jumpL7Ecosystem & StrategyL6Experience & VisualizationL5Applications & CopilotsL4OrchestrationL3Twin Modeling & AIL2Data FabricL1Control PlaneL0Foundation▲tlmctl▼L5 · APPLICATIONS & COPILOTSAgentic copilots that reason over the machine.1Plasma Copilotscenario design2Engineering Copilotsubsystem analysis3Operations Copilotrunbooks & procedures4Agentic Toolsbounded action-taking5Knowledge BaseRAG over the fabric6Guardrailssafety-boundedMACHINE TIEReads the twin and fabric; proposes actions that route through L4.KRONOS FUSION ENERGYAI-NATIVE S.M.A.R.T. GENERATORAPPLICATIONS & COPILOTSSHEET 07REV. 2026-08L5 · AI-NATIVE STACK
L5 · Applications & Copilots — its place in the stack (left, click any layer) and its internal components (right). Telemetry rises; control descends.

Prompts are versioned artifacts

A copilot's prompt is not free-form text written per request; it is a versioned template with slots. The template fixes the copilot's role and machine, states the hard constraints (envelope, refusal rules, economics prohibition, honest-framing rules), declares the tool contract, and specifies the output schema. Request-specific content — twin-state summary, retrieved evidence, the question — fills the slots.

Template sections

text
TEMPLATE plasma_copilot v7:
  [ROLE]    You advise on {machine}. You propose; you never actuate.
  [CANON]   {frozen_numbers}   # cited, never invented
  [RULES]   stay in envelope; cite every fact; label inference;
            no economics; no net-gain claim pre-FOAK; refuse if unsafe
  [TOOLS]   {bounded_tool_schemas}
  [STATE]   {twin_state_summary}
  [EVIDENCE]{retrieved_chunks}
  [TASK]    {question}
  [OUTPUT]  {answer, citations[], uncertainty, proposal?}

Why versioning matters

Because the prompt shapes behavior, it is treated like code: versioned, reviewed, and tested. A change to the template is evaluated against the full regression suite before it ships, so a wording change that quietly weakens a safety constraint is caught. The template version is recorded with every answer for audit, so any output can be reproduced with its exact prompt.

Templates encode the honest-framing rules directly: the copilot is instructed never to claim hardware net gain before FOAK, always to distinguish the frozen design point from measured results, and to cite canonical numbers rather than recall them. These rules live in the prompt and are re-checked in evaluation, so honesty is a tested property, not a hope. Filled templates are assembled under the context budget from live twin state.

Content reviewed August 2026 · design-and-simulation stage