Browse docs

Glossary

Plain-language definitions for Mighty scan, image evidence, billing, and prompt-safety terms.

Use this glossary when a result, setting, or docs page uses a security or image-evidence term that needs a precise product meaning.

Scan Outcomes

TermMeaning
ALLOWMighty did not find enough risk to interrupt the workflow. This is not a guarantee that the material is true, benign, or legally sufficient.
WARNSuspicious or ambiguous evidence exists. Route to human review, add friction, or request stronger evidence.
BLOCKRisk is high enough that the workflow should stop or quarantine the item before trust.
Risk scoreA 0-100 score for routing and triage. Treat it as decision support, not a standalone fraud verdict.
Threat categoryA machine-readable label for the kind of evidence found, such as prompt injection, hidden text, authenticity signal, metadata inconsistency, or edit evidence.

Scan Settings

TermMeaning
modeControls scan depth and latency: fast, secure, or comprehensive. Mode does not add a separate SCU multiplier.
focusControls which evidence family Mighty prioritizes and how image units bill. steg, ai, and edits are focused paths; all runs the supported image/PDF evidence paths together.
focus=stegLooks for hidden content, prompt injection, content steering, unsafe text, secrets, and related threat signals.
focus=aiLooks for image/PDF authenticity evidence, such as likely AI generation, AI editing, reposting, provenance gaps, or visual inconsistency.
focus=editsLooks for localized manipulation evidence, especially when a submitted image can be compared with an original/source image.
focus=allRuns supported hidden-content, AI-authenticity, and edit-evidence paths together for image/PDF evidence. Bills 10 SCU per image unit.
profileAdjusts policy tolerance, such as balanced, strict, or AI-safety-oriented routing.
data_sensitivityControls how sensitive Mighty should be to normal business PII, credentials, secrets, and regulated data.

Evidence Terms

TermMeaning
AI authenticityEvidence about whether an image or PDF visual appears generated, AI-edited, reposted, provenance-backed, or visually inconsistent.
AI editsLocalized evidence that visible content may have been changed, such as altered text, cloned areas, removed objects, or manipulated damage.
Steganography, or stegHidden or disguised content inside text, images, OCR output, PDFs, or documents. In Mighty docs, steg also covers prompt-injection and hidden-instruction safety.
Prompt injectionText or hidden instructions that try to override a system, developer, tool, or workflow policy.
Content steeringInstructions that try to push a model or workflow toward a specific unsafe, biased, unauthorized, or misleading action.
ProvenanceEvidence about origin and history, such as metadata, capture hints, signatures, or whether a file appears derived from another source.
Reference fileThe trusted or original/source image used for pairwise edit comparison with a submitted image.
Embedded imageA unique image inside a PDF that can be billed separately from page processing. Repeated copies are deduplicated by hash before counting.

Billing And IDs

TermMeaning
SCUSecurity Compute Unit, Mighty's usage unit for scan work. SCU starts at $0.001.
Image unitA physical image counted for image evidence billing. Focus changes the price for the unit; it does not change the count.
scu_chargedSCU charged for a completed scan. It can include text, page, image, and embedded-image work.
scan_idUnique ID for one scan result.
scan_group_idID that links related input, OCR, output, derived-file, and follow-up scans for the same item or workflow.
scan_phaseWhether the material is being scanned before trust as input, after generation as output, or in another supported workflow phase.

For practical setting recipes, see Choose Scan Settings. For exact SCU rates, see Billing, SCU, And Limits.