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

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

Term	Meaning
`mode`	Controls scan depth and latency: `fast`, `secure`, or `comprehensive`. Mode does not add a separate SCU multiplier.
`focus`	Controls 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=steg`	Looks for hidden content, prompt injection, content steering, unsafe text, secrets, and related threat signals.
`focus=ai`	Looks for image/PDF authenticity evidence, such as likely AI generation, AI editing, reposting, provenance gaps, or visual inconsistency.
`focus=edits`	Looks for localized manipulation evidence, especially when a submitted image can be compared with an original/source image.
`focus=all`	Runs supported hidden-content, AI-authenticity, and edit-evidence paths together for image/PDF evidence. Bills 10 SCU per image unit.
`profile`	Adjusts policy tolerance, such as balanced, strict, or AI-safety-oriented routing.
`data_sensitivity`	Controls how sensitive Mighty should be to normal business PII, credentials, secrets, and regulated data.

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

Term	Meaning
SCU	Security Compute Unit, Mighty's usage unit for scan work. SCU starts at `$0.001`.
Image unit	A physical image counted for image evidence billing. Focus changes the price for the unit; it does not change the count.
`scu_charged`	SCU charged for a completed scan. It can include text, page, image, and embedded-image work.
`scan_id`	Unique ID for one scan result.
`scan_group_id`	ID that links related input, OCR, output, derived-file, and follow-up scans for the same item or workflow.
`scan_phase`	Whether 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.

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.

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

Term	Meaning
`mode`	Controls scan depth and latency: `fast`, `secure`, or `comprehensive`. Mode does not add a separate SCU multiplier.
`focus`	Controls 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=steg`	Looks for hidden content, prompt injection, content steering, unsafe text, secrets, and related threat signals.
`focus=ai`	Looks for image/PDF authenticity evidence, such as likely AI generation, AI editing, reposting, provenance gaps, or visual inconsistency.
`focus=edits`	Looks for localized manipulation evidence, especially when a submitted image can be compared with an original/source image.
`focus=all`	Runs supported hidden-content, AI-authenticity, and edit-evidence paths together for image/PDF evidence. Bills 10 SCU per image unit.
`profile`	Adjusts policy tolerance, such as balanced, strict, or AI-safety-oriented routing.
`data_sensitivity`	Controls how sensitive Mighty should be to normal business PII, credentials, secrets, and regulated data.

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

Term	Meaning
SCU	Security Compute Unit, Mighty's usage unit for scan work. SCU starts at `$0.001`.
Image unit	A physical image counted for image evidence billing. Focus changes the price for the unit; it does not change the count.
`scu_charged`	SCU charged for a completed scan. It can include text, page, image, and embedded-image work.
`scan_id`	Unique ID for one scan result.
`scan_group_id`	ID that links related input, OCR, output, derived-file, and follow-up scans for the same item or workflow.
`scan_phase`	Whether 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.