Inspiration

A receiving dispute can require evidence from purchase records, parcel labels, and entrance footage. These sources need a shipment-specific link before they can support a conclusion.

What it does

Receiving Evidence Reconciler starts from an order and a delivery day. It proposes sensible defaults (timezone, photo album, camera tolerance) in one question, then extracts order and tracking fields, reconciles the purchase order and invoice, and compares identifiers with waybill OCR.

When camera evidence is available, it proposes entrance events near the photograph's capture time and sets an arrival flag: corroborated, time-matched, or no camera evidence. Every link in the chain is rated strong, time-only, or none, so the user can see exactly how solid the proof is.

The user reviews the result before any tags, album, or saved file are created. Matching records plus a matching label give Receipt-Verified; a conflict gives Discrepancy-Hold. Without cameras the Skill still reaches a verdict, flagged "no camera evidence". It never treats a sealed box photograph as proof of its contents.

How it is built

The Markdown package follows the official Uliya Skill Developer Package v0.7.3. Five registered experts own six CLI families and 19 distinct catalog actions, including optional actions. The parent delegates real business inputs and handles all five public completion states.

New tags are resolved by name after creation before their numeric IDs are used. Camera queries carry timezone and offset-bearing timestamps. Optional identity review prefers a specific vehicle identifier; face matching is disabled unless separately authorized. Saved reports exclude identities and surveillance images.

What exists and what remains

The package, matching rules, verdict table, worked example, and synthetic test fixtures are written. The bundled checker validates static structure and ownership. It does not establish installation or operational behavior on a NAS.

Round 2 must validate actual model routing, OCR accuracy, permission handling, clock alignment, tag lookup, and album membership. Camera events on the assigned NAS remain unconfirmed.

Original contribution

The starter kit already includes document-audit and camera-query examples. This project adds an explicit shipment evidence chain, confidence rules, verdict precedence, and a review flow that remains useful when one source is unavailable.

Built With

  • computer-vision
  • document-ai
  • markdown
  • multi-agent-orchestration
  • ocr
  • ugos
  • ugreen-ai-nas
  • uliya-skill-kit
Share this project:

Updates

Submission history