What it does
Claim Evidence Binder turns a home NAS into a claim desk. For one incident window it inventories the cameras, pages the event timeline, and copies each clip while its evidence handle is still valid. It resolves a plate to an identity read, copies the claim documents and extracts and reconciles their amounts, OCRs a photographed page, writes a digest, then seals the folder with a SHA-256 manifest.
Why it belongs on a NAS
Cloud claim portals require the footage to leave the device, so on-device integrity cannot be attested by design. Consumer assistants cannot reach a local surveillance library. Neither copies evidence under its own expiry, nor names the events whose evidence never arrived.
How it is built
A Markdown orchestration Skill against the Uliya Skill Kit catalog 2.0.0, with one delegation per expert step and an explicit consumes/produces contract between steps. Every write is approval-gated, so all five delegation states are handled, including waiting for approval on the first folder creation.
What it refuses to claim
The manifest detects later change or removal of any listed file; additions are caught only by comparing the listed count with the folder count. Recording integrity before collection is out of scope, and events without evidence are named instead of filled in.
Status
Round 1 package complete: SKILL.md plus five references, and the official checker returns static-pass with zero errors and zero warnings.
Built With
- file-workflow
- ug-document
- ug-filesystem
- ug-knowledge
- ug-photo
- ug-surveillance
- uliya-skill-kit-2.0.0
