Handout — AI Summit Styria 2026

Everything the talks left out on purpose: every table, number, limit and evidence path. Handout zu den Vorträgen: alle Tabellen und Messwerte stehen hier, damit die Vorträge beim Warum bleiben können.

FORTRESS: A Sovereign, Reproducible Provenance Layer for AI-Era Content with a Null-Controlled False-Attribution Guard

Session 1 · 10:30 AI Summit Styria 2026 · every table and number behind the talk

Two opposite products from one engine

RESILIENT — survives

  • mark survives the distribution pipeline
  • provenance, attribution, leak-tracing
  • may be applied to any file
  • this paper

FRAGILE — breaks on any edit

  • authenticity and tamper-evidence
  • applied only at live capture
  • badge: captured live & unaltered
  • never applied to uploads

How robust watermarking is usually reported

A multi-number scorecard — axes never fused

AxisQuestion
Robustness (per attack)payload survives this transform?
ImperceptibilityPSNR distribution vs. original
True-attributionmarked image → its own source
False / phantom-attributionnull or foreign image → any source?
Cross-attributionmarked image → a wrong source?
Capacitypayload bits per image
Signature integritytamper / forgery caught?

Paper Table I · every value from one harness, dated JSON manifest

Method in plain words

Two profiles, measured at their extremes

Stealth

  • block 32, low embedding margin
  • maximally invisible
  • one global key

Crop-hardened

  • complete key in each of 4×4 tiles
  • any surviving tile recovers all 128 bits
  • the robust default

Robustness per attack (n = 12, payload recovery)

AttackCrop-hardenedStealth
Clean re-encode · JPEG q85/q60/q40 · double-JPEG100%67%
Downscale 75% / 50%100%42%
Gaussian noise σ6100%67%
Brightness −2492%50%
Combo (noise + resize + JPEG)100%42%
Crop 10% / 25% / 50%83% / 100% / 83%0%
Crop 25% off-centre92%0%

Paper Table II · 12 images at 1024², 8 real photographs + 4 procedural textures

Robustness has a price in image fidelity

24.2 dBmedian PSNR, crop-hardened
28.5 dBmedian PSNR, stealth
≈ 7 dBless distortion with the stealth profile

Paper Table II · n = 12 · PSNR measures distortion, not visibility — as reported in the paper

Attribution scorecard — the differentiator

MeasurementRaten
True-attribution (clean + JPEG q60, guard)66.7%24
Cross-attribution (marked → wrong source)0%12
False-attribution WITH guard (null control)0%17
Null: raw bit-distance to nearest key (median)0.4617
Genuine: raw bit-distance to own key (median)0.0012

Paper Table III · null control = 12 unmarked originals + 5 foreign images

The null control

0 / 17false attributions with the guard
0.46median bit-distance, null inputs
0.00median bit-distance, genuine marks
0 / 12cross-attributions among marked images

Paper Table III · chance level = 0.5

The guard: a principled reject

Provenance signature integrity

PropertyResult
Signature realnessECDSA P-256, 70–72 bytes, not a stub
Valid signatureverifies
Field tamper (source → "ATTACKER")caught
Forged-key signaturerejected
Post-quantum (ML-DSA)roadmap at submission (companion system)

Paper Table IV

Regulatory mapping — with honest scope

Use caseRegulationHonest scope
AI-content provenanceAI Act Art. 50marking, not detection; ≈0% vs. AI redraw
Anti-piracy leak-traceMovieLabs ECPattribution, not DRM; chain ~42%
Creator / scraper rightsGDPRnever "makes you compliant"
Live authenticityEU CoP / C2PA"captured live", never "not AI"

Paper Table V · chain ~42% and redraw ≈0% from separate prior harnesses, not this scorecard

Honest limits (1/2) — disclosed breakers

Honest limits (2/2) — scope

Since submission — measured after acceptance (dated, with evidence)

2026-07-08 Reed–Solomon decoder bug fixed in all engines; pre-fix numbers, incl. the paper's, are lower bounds — 8,000-trial stress test
Fortress repo · backend/src/fortress/rl-robustness/rs-stress.cjs
2026-07-11 Post-quantum signing shipped in the SDK: hybrid Ed25519 + ML-DSA-65 (FIPS 204), downgrade rejected — signer test 10/10 (re-run 2026-10-07)
Fortress repo · sdk/fortress-provenance-sdk/signer-test.cjs
2026-08-28 72-cell image-engine bench: spread-spectrum engine reads 71/72 at median 46.9 dB, crop-10 12/12, crop-25 11/12; paper-era DWT-V3 48/72, crop 0/12; 0 false hits in all arms
Fortress repo · messstation/bench-motoren-bild.mjs (+ .jsonl)
2026-09-05 Blind crop, no key, 6 images: crop 5/10/15% → 6/6 · 5/6 · 5/6; unmarked negative control 0/6 false hits
Fortress repo · Documentation/SSOT/evidence/GEO_KANON_BLINDSCHLUESSEL.md

We propose the scorecard as an open evaluation standard

A Sovereign, Reproducible Trust Layer for LLM Systems: Two-Number Prompt-Injection Detection with Post-Quantum, Browser-Verifiable Audit Receipts

Session 6 · 14:00 AI Summit Styria 2026 · every table and number behind the talk

LLMs enter regulated work faster than the tools that make them trustworthy

What is usually reported vs. what we measure

Usual practice

  • One fused F-measure
  • Proprietary corpus
  • Cloud API sees the prompt
  • Decoys asserted convincing

This work

  • Two numbers, never fused
  • 100% public corpora, one command
  • On-premise, CPU-first
  • Decoys measured, with a control

Architecture: two decoupled subsystems

AEGIS — injection and content guardrail

Stage 1 · injection

  • Aho-Corasick automaton, pure TypeScript
  • One linear pass, regex verification
  • Cumulative severity threshold

Stage 2 · content safety

  • Llama-Guard-3:1b, on-premise
  • CPU or NPU via local runtime
  • Reported separately from Stage 1

LEDGER — the audit substrate

Two-number scorecard (public corpora)

AxisTPRFPRn (adv / benign)
Injection (Stage 1)97.7%4.0%176 / 150
Content safety (Stage 2)79%10%100 / 150
Content F-measure0.814Llama-Guard-3:1b, on-prem
Stage-1 latency (CPU)1.73 ms median6.95 ms p95

Paper Table I · hackerprompt + jailbreakhub vs OR-Bench · config NO_PHI+L3 · dated 2026-06-08

Injection per source — strong on standard, weak on narrative

SourceTPRn
hackerprompt72%—
jailbreakhub85.5%—
wildjailbreak (narrative)16.0%200
Aggregate (broad mix)47.6%676 / 1500

Paper Table II · aggregate FPR 3.8% · limit results sit in the same table as headline results

Measuring deception-defense indistinguishability

Attacker modelTemplateRetrieval
D1 watermark (byte inspection)100%none
D2 verbatim-collision onset~13 probes~1250 (10^6 cache)
D4 stylometry AUC (held-out)1.0000.636
Same-population control AUC0.443≈ 0.5 → method valid
Retrieval residual content tellAUC 0.764

Paper Table III · lower = harder to fingerprint

Deception: reduced, not eliminated

1.000 → 0.636held-out stylometry AUC
0.764residual content-relevance tell
default-offnot relied upon for security

Statistical indistinguishability at pure-CPU serving is not achieved (paper Sec. VI)

Offline verification in the browser

Audit substrate verification

PropertyResult
Signature realnessML-DSA-65, 3309-byte (not stub)
Action-replay tampercaught (verdict TAMPERED)
Metric-inflation tampercaught (signature invalid)
Forged-key signaturerejected
RFC 3161 timestampgranted; references digest (live TSA)
Test coverage96 unit assertions, 7 test files

Paper Table IV

Disclosed limits (1/2)

Disclosed limits (2/2)

EU AI Act: a mapping, not conformity

What a receipt does

  • Art. 12 / 19 logging, Annex IV records
  • Machine-checkable, per action
  • Portable, offline-verifiable

What it does not do

  • Claim conformity
  • Replace harmonised standards
  • Replace a notified body

Companion work (separate papers)

Multilingual over-blocking (AIS26)

  • English point: 4.0% benign FPR
  • 16.13% on 46,440 multilingual prompts
  • Opt-in dampener: 20.5% → 10.5%

FORTRESS content provenance

  • Invisible marks for AI Act Art. 50
  • False attribution 0/12 (null-controlled)
  • Anchorable in the same LEDGER log

Since submission — measured after acceptance (dated, with evidence)

2026-10-07 Detection numbers NOT re-measured — the paper's scorecard (dated 2026-06-08) stands as published
Destill-NI repo · Documentation/HONEST-GTM/OVERNIGHT_RL_RESULT_2026-06-08.md
2026-10-07 Issuer key served live: destill.ai/.well-known/did.json → HTTP 200, JSON, ML-DSA-65 key identical to the sample credential's
curl -s https://destill.ai/.well-known/did.json vs C:/Destill-NI/destill-site/verify/sample-evidence.json
2026-10-07 Sample receipt re-verified with a second, independent implementation (Node 24 native ML-DSA-65): 3309-B signature valid, 1-bit tamper rejected, RFC 3161 token references digest
Destill-NI repo · destill-site/verify/sample-evidence.json (browser verifier: verify/verify.html, @noble/post-quantum)

Don't trust us — check it

We propose an open evaluation standard

Temporal-Majority Provenance Watermarking Survives Real Video Codecs: An H.264/HEVC/VP9/AV1 Scorecard with Audio Context

Session 8 · 15:20 AI Summit Styria 2026 · every table and number behind the talk

FORTRESS in one slide

Resilient mark (this talk)

  • survives the distribution pipeline
  • provenance, attribution, leak tracing
  • offline, EU-sovereign engine

Fragile seal (not this talk)

  • breaks on any edit
  • captured live & unaltered
  • live capture only

What is usually reported vs. what we measure

Common reporting

  • a simulated compressor
  • a still-image number quoted as video
  • codec survival on a clean channel

This paper

  • the real ffmpeg encoders
  • per-frame rate and temporal majority, separately
  • a clean-baseline control
  • breakers stated next to the headline

Why four codecs

Method in plain words

The load-bearing measurement: a clean baseline

Headline result (paper, 2026-06-30 manifest)

33%per-frame, clean baseline before codec
33%per-frame after each of 4 codecs
0codec-induced loss vs. baseline
25.9 dBmedian embed PSNR

3 clips × 6 frames = 18 frames per codec · 1024² · real ffmpeg

Codec survival vs. clean baseline

StageCRFPer-framevs. baseline
Clean (pre-codec)—33% (1/3 clips)—
H.264 (libx264)2333%= baseline
HEVC (libx265)2833%= baseline
VP9 (libvpx-vp9)3433%= baseline
AV1 (libaom-av1)3633%= baseline

Paper Table I · 1024², F = 6, 3 clips · temporal majority 1/3 clips for every codec

H.264 quality sweep: flat

CRF 18CRF 23CRF 28CRF 35
33%33%33%33%

Paper Table II · per-frame recovery, 3 clips, 18 frames per point

Reading it honestly: the result is bimodal by clip

The clip that embeds (1 of 3)

  • 100% per-frame
  • through H.264, HEVC, VP9 and AV1

The clips that do not (2 of 3)

  • 0% before any codec
  • 0% after, whatever codec or bitrate

Geometry + codec: partially closed (paper, 2026-07-03 manifest)

Audio context — cited, not measured by this harness

Audio codecPayloadNote
MP3 128 kbpsrecoveredconfidence ~0.97
MP3 64 kbpsrecoveredlow-band carrier survives
AAC / Opus / Vorbisrecoveredhigh confidence

Paper Table III · embed SNR ~14–17 dB: audible-ish, NOT inaudible

Honest limits (all from the paper)

Reproducible by one command

Since submission — measured after acceptance (dated, with evidence)

2026-07-08 Reed–Solomon decoder fixed in all engines: paper numbers (run 2026-06-30) are lower bounds
Fortress repo · backend/src/fortress/rl-robustness/rs-stress.cjs
2026-07-08 H.264 + crop combined, 12-frame clips: clip 8/8 at crop 10/25% × CRF 23/28; stealth control 0/8; 0 false alarms (lab)
Fortress repo · backend/src/fortress/rl-robustness/OUTPUT-VIDEO-CROP/video_crop_report.md
2026-08-28 72-cell still-image engine bench: video-ss 71/72 (98.6%), median U 46.9 dB; paper-era DWT-V3 family 48/72, crop 0/12
Fortress repo · messstation/bench-motoren-bild.mjs
2026-09-14 Audio, real material: codec BER 0.0% in 4/4 cells, but the model inaudibility gate FAILED in every cell (lab)
Fortress repo · Documentation/SSOT/evidence/AUDIO_J4_ECHTES_MATERIAL.md
2026-10-02 Geometry replay through real libx264: 55/55, 0 hit loss, 11.5× less search time; scale 0.83 reads 12/12 at CRF 23 but 0/12 at CRF 28
Fortress repo · Documentation/SSOT/evidence/GEO_WIEDERGABE_H264.md

What these newer results do not yet say

We propose an open evaluation scorecard for video provenance

Check it yourself — one link and QR code per case

Prüfe selbst: ein Link und ein QR-Code pro Fall. Overview: destill.ai/ais26/pruefen

QR

Image: trace a leak

Bild: Leak nachweisen
QR

Video: through H.264

Video: durch H.264
QR

NI-Stack: stage 1 in the browser

NI-Stack: Stufe 1 im Browser
QR

Proof of Agent Work: check a receipt

Proof of Agent Work: Beleg prüfen
QR

Text & code: recompute

Text & Code: nachrechnen

Reward hacking: harness

Reward Hacking: Prüfstand
no public tool yet · ip@destill.ai

The two posters

A0 portrait, vector PDF (prints cleanly at A1 as well).

How to read the numbers

Who stands behind this

Hagen Schmidt, inventor. Research carried out in the association Lebensfluss e.V., Gratkorn near Graz. A spin-out is in preparation. Patent applications are filed in the inventor’s name. Open to an IP licence or acquisition, a co-founder or takeover partner, a standards co-proposer, and a research or funding consortium. Contact: ip@destill.ai · destill.ai/ais26

Rights notice: the conference publication licence covers the text and figures of the contributions only; it grants no licence under any patent or patent application, and no implied patent licence.