FohBoh | Sentry™ — Zero AI. Certified Recovery.

3–7%

typical certified overcharge
as % of gross delivery sales

198

deterministic rules
M01 + M02 combined

100%

Zero AI — every result
is mathematically provable

SHA-256

tamper-proof hash on
every certified record

The Core Problem

DSPs and processors overcharge restaurants every month — and no one certifies it.

Delivery and card fees are governed by signed contracts most operators have never re-read. The overcharges are systematic, compounding, and perfectly legal to dispute — if you can prove them.

📄

The Contract

Signed agreements specify commission bases, rates, and fees. DoorDash charges on order_subtotal. Uber Eats on platform_gross_sales. One wrong field = systematic error on every order.

📊

The Settlement

DSPs produce weekly CSVs with 14+ columns per row. Identifying rate violations, tax inclusion errors, or tier downgrades manually is impossible at scale.

⚖️

The Legal Gap

Operators know they're being overcharged but lack court-admissible evidence. Allegations without certified proof go nowhere. Legal counsel won't file without it.

✅

Sentry Solves It

MGE computes a deterministic Shadow Record per transaction, certifies every variance against the signed contract, and produces a SHA-256 sealed CAAR — court-ready in 24 hours.

System Architecture

Three Layers. One Provable Chain of Custody.

No machine learning. No estimation. Pure contract-versus-actual comparison, auditable from source data to sealed output.

L0Raw Data

DSP Settlement CSVProcessor Statement CSVPOS Channel ExportSigned DSP Agreements (PDF)Merchant Agreement (PDF)Bank Statement (PDF)

↓ SHA-256 hash on intake · Schema validation · 4-indicator intake confirmation

L1MGE Core™

Shadow Record EngineSemantic Truth LayerDeterministic Law EngineLoop A · Contract ComparisonMQ6 Trust Scoring

↓ 198 rules evaluated · per-row variance computation · trust scoring across 6 dimensions

L2Sentry™

M01 Merchant Fee RecoveryM02 Delivery Fee Recovery107 MFR Rules83 DFR RulesLocation WaterfallWGS Portal

↓ Certify & Lock · SHA-256 seal · CAAR generated · ExportPack bundled

L3Certified Output

CAAR — Court-Admissible Analysis Report9-Artifact ExportPackSHA-256 Integrity ManifestDemand Letter Ready

Certification Pipeline

Four Steps. One Locked Record.

Every certification runs the same deterministic 4-step MGE pipeline. Each step is logged, timestamped, and SHA-256 anchored before the next begins.

STEP 01

🔍

Semantic Truths

The MGE ingests raw DSP and processor data, resolves native column names against the sealed Schema Registry, and builds the Semantic Truth layer — the authoritative interpretation of what each value means.

STEP 02

⚖️

Deterministic Law

198 rules evaluate every row against the signed contract config. Commission base, applied rate, included/excluded fields, tier classification — each is compared to the Shadow Record independently.

STEP 03

🔄

Loop A Execution

The primary certification loop. Contract-versus-actual comparison runs across every transaction. Variances are isolated, quantified, attributed to specific rule violations, and assigned to the certified overcharge ledger.

STEP 04

🔐

Certify & Lock

The result is written to the KPI Vault, SHA-256 sealed, and assigned a CAAR state. The ExportPack is assembled. The record is immutable — no one can alter it without breaking the hash.

Recovery Modules

M01 · M02 · M03 — Three Certified Revenue Streams

Each module operates as an independent certification engine with its own rule set, schema registry, and CAAR output. They share one MGE Core.

M01 — Merchant Fee Recovery

Card Processor Certification

107 MFR rules evaluate every processor transaction against the signed merchant services agreement. Markup basis points, per-transaction fees, tier classification, PCI charges, reserve holds, and chargeback fees are all certified independently.

Rules: 107 MFR rules

Data: Processor CSV · Signed agreement · POS export · Bank statement

Key violations: Rate overcharge · Tier downgrade · Unauthorized fees · Reserve excess

Gate: D3 reconciliation requires bank statement · Trust Score ≥ 85 for CAAR

M02 — Delivery Fee Recovery

DSP Commission Certification

83 DFR rules evaluate every DSP settlement row against the signed merchant agreement. Commission base field selection is the most critical input — each DSP uses a different native column name. Wrong base = systematic error on every order.

Rules: 83 DFR rules per DSP (DoorDash · Uber Eats · Grubhub · Slice)

Data: DSP settlement CSV · Signed DSP agreement · POS export

Key violations: Rate overcharge · Tax inclusion · Tip inclusion · Member rate error

Critical field: Commission Base — order_subtotal (DD) vs platform_gross_sales (UE)

🔒

M03 — Royalty Recovery · Locked

Franchise & Brand Royalty Certification

T32–T40 triggers covering royalty basis errors, promotional exclusions, and multi-unit fee caps. Unlocks after M01 + M02 active ≥ 90 days with Trust Score ≥ 85 on both. Designed for franchise operators billing on revenue that includes DSP overcharges.

MQ6 Trust Scoring

Six Dimensions. One Score That Gates CAAR.

The MGE MQ6 model produces a composite Trust Score across six data quality dimensions. A score of 85 or above is required to generate a CAAR.

D1 · 25% weight

Data Completeness

Weight: 25%

Are all required files present? Statement CSV, POS export, signed agreement, bank statement. Missing any one drops this dimension significantly.

D2 · 20% weight

Rule Validation

Weight: 20%

Schema column match percentage across all uploaded CSVs. Measures whether native file columns map cleanly to MGE canonical field definitions.

D3 · 25% weight

Reconciliation

Weight: 25%

Three-way cross-system reconciliation: settlement CSV + POS export + bank deposit. Without the bank statement, D3 scores 0 and the composite cannot reach 85.

D4 · 15% weight

Source Integrity

Weight: 15%

SHA-256 hash verification on every uploaded file. Proves the document was not modified between the source system and the vault — chain of custody anchor for FRE 902(11).

D5 · 10% weight

Drift Detection

Weight: 10%

Trailing variance baseline comparison. Identifies whether this period's overcharges are consistent with prior periods or represent an anomalous spike.

D6 · 5% weight

Data Freshness

Weight: 5%

Were uploads performed in the current certification session? Stale vault entries that haven't been refreshed this period reduce this dimension.

Certification States

Seven States. S3 Unlocks CAAR.

Every certification run produces a deterministic state. S3 requires Trust Score ≥ 85 and certified variance above the legal action threshold — the state that generates a CAAR.

91

MQ6 Trust Score

CAAR gate: 85
This score = S3 state
ExportPack: all 9 READY

CAAR Eligible

S1CertifiedCompliant — Trust Score ≥ 70, no variance detected

S2CertifiedDiscrepancy Identified — variance detected, below legal threshold

S3CAAREscalated — Legal Threshold Reached · CAAR generated · ExportPack ready

S4PartialPartial certification — Trust Score 60–69

S5PendingAwaiting data upload or schema sealing

S6RejectedData Quality Failure — Trust Score below 60

S7ArchivedSuperseded by a later certification run

CAAR — Court-Admissible Analysis Report

Self-Authenticating Evidence. No Witness Required.

A Sentry CAAR self-authenticates under three Federal Rules of Evidence simultaneously. No FohBoh representative is required to appear in any proceeding.

📋FRE 803(6)

Business Records Exception

The CAAR qualifies as a regularly-kept business record produced in the ordinary course of the certification workflow. No foundation witness required to admit it as evidence.

🔐FRE 902(11)

Self-Authentication

The SHA-256 integrity manifest and chain-of-custody log satisfy the self-authentication standard for certified domestic records. The hash is the witness.

🔗FRE 1002

Best Evidence Rule

The sealed schema, hashed source files, and complete audit trail satisfy the original document requirement. The ExportPack is the original — not a copy.

ExportPack · 9 Artifacts Bundled

01CAAR PDF — narrative + findings

02Truth Source CSV — Shadow Record

03Claim Source CSV — certified variances

04Signed Contract — source agreement

05Bank Statement — reconciliation anchor

06Evidence Manifest — metadata log

07Audit Trail — immutable activity log

08Rule Citations — rule-to-violation map

09SHA-256 Integrity Manifest

Core Architectural Principle

Zero AI. Zero Guessing.
Every Variance Is Mathematically Proved.

Sentry uses no machine learning, no probabilistic inference, and no language models. Every certified figure is computed by a deterministic rule engine against a sealed contract record. The math is the proof.

Deterministic Engine No ML / No LLM Reproducible Results Rule-Based Certification 100% Auditable Court-Admissible Output

Zero AI. Zero Guessing.Certified Recovery.