OPF Tone

Technical

Lead with the question or claim, then walk through the mechanism and the numbers. Use exact terminology; assume the audience can handle and prefers it. Diagrams, tables, and benchmarks are first-class.

technical4 voice cues3 sample phrases

Tone

Technical

cues

avoid

Precise, evidence-led voice for engineering, research, and product-detail audiences.

“p95 inference latency is 38ms on a single A100, down from 312ms on the prior runtime.”

Generation cue

State the claim, then the mechanism, then the evidence.

Summary

Precise, evidence-led voice for engineering, research, and product-detail audiences.

OPF Field

tone

Schema

https://openpresentation.org/schema/opf-tone/v1

Voice Cues

1
State the claim, then the mechanism, then the evidence.
2
Use exact terminology — don't soften technical terms for general readability.
3
Quote benchmarks with conditions (cold/warm, p50/p95/p99, dataset, hardware).
4
Prefer diagrams and tables over prose paragraphs for structural information.

Avoid

1
Vague claims ('much faster', 'better', 'easier').
2
Marketing framing without supporting data.
3
Glossing over caveats and tradeoffs.
4
Casual register that obscures precision.

Sample Phrases

“p95 inference latency is 38ms on a single A100, down from 312ms on the prior runtime.”

“We replaced the streaming serializer with a batched protobuf path; throughput rose 4.2× under load.”

“The result holds for context windows up to 32k tokens; beyond that, see appendix B.”

Recommended Narrative IDs

challenge-resolutioninnovationconference-talkengineering-update

OPF Config

tones:technical

Open Presentation Format

{
  "$schema": "https://openpresentation.org/schema/opf/v1",
  "version": "1.0",
  "meta": {
    "title": "PPTX.gallery — tones/technical"
  },
  "tone": "technical",
  "design": {},
  "slides": [
    {
      "id": "gallery-preview-1",
      "layout": "title-slide",
      "elements": []
    }
  ]
}

Open in OPF Playground

Preview this config live at pptx.dev/playground.