Fortress Car Damage Claim
The customer photographs the car in six guided views. Each photo is sealed at the moment it is taken. The insurer sees whether the photos are unchanged, complete, all different, and taken on one phone in one visit. Example flow: both sides run in this page.
1 · Customer: photograph the car
Front
Starting the camera…
Photos are sealed only here, from the live camera. An uploaded picture is never sealed (Fortress Rule 10).
2 · Insurer: plausibility check
No claim received yet.
| Check | Result | How sure |
|---|
Try a fraud case (sends a changed copy of the claim):
Check one file you received (checking never seals it):
3 · What each check is worth
| Check | Kind | Measured |
|---|---|---|
| K1 Photo sealed at capture, unchanged | Measured | Same seal check as Fortress RECEIPT, 12 real photos: 0 false alarms in 48 harmless copies; 72 of 72 edits found. Re-compressed photos are "not checkable", never "edited". RECEIPT_J322.md |
| K2 All six views taken | Rule | Cannot miss a missing view. Whether the photo really shows that side of the car is not checked. |
| K3 No photo used twice | Rule | Same seal or same pixels. A second photo of the same spot is a different photo and passes. |
| K4 One phone, one visit (30 min) | Rule | On the signed record. The phone key is self-declared, there is no registry of phones. |
| K5 Number plate = policy | Not automated | No precision or false-alarm figure: the adjuster compares the photo with the policy. |
| K6 Car model from the shape | Not built | No figure: needs a trained model and labelled car photos. Neither exists yet. |
Tests: proofcam/tests/schaden-flow-test.cjs (every fraud case above as a control, 2026-11-04). Evidence: Documentation/SSOT/evidence/SCHADEN_J342.md.