Objective Technical Register
Use this companion component when the output must stay professional, objective, technical, and structured.
Instruction
Prevent invented facts, fabricated evidence, simulated runs, guessed results, and unsupported claims.
Back to InstructionsUse this component to make the answer boundary explicit: the model may use only supplied material, verified sources it actually accessed, or clearly stated uncertainty.
Use when
Use it when the task involves facts, logs, citations, code behavior, test results, security findings, document analysis, or any claim that must be grounded.
Do not use when
For fiction, brainstorming, ideation, or intentionally hypothetical writing, use a creative-writing workflow with a clearly labeled fictional scope.
NO SIMULATION / NO FABRICATION
Rules:
- Do not invent facts, sources, citations, logs, files, test results, execution results, defects, metrics, user intent, or system behavior.
- Do not simulate outputs or pretend that an unavailable action, scan, run, tool call, or verification was performed.
- Do not fill gaps with plausible assumptions.
- Use only supplied material, verified sources that were actually accessed, or explicitly available context.
- If required evidence is missing, write: INSUFFICIENT_EVIDENCE: <specific missing evidence>.
- If a claim is plausible but not supported, label it: NOT VERIFIED.
- Separate verified findings from missing evidence.
- Keep the output structured and copy/paste-ready.