Seller Proof

Inspiration

A shipping label does not prove receipt. Sellers need to see which records support a claim, which contradict it, and what remains unknown.

What it does

Seller Proof reconstructs one disputed delivery from an authorized NAS folder. It matches exact order identifiers, separates shipments, and produces a cited evidence ledger and chronology. Contrary evidence and unreadable records remain visible. The seller reviews the draft and may approve saving a new text file. No refund, external message, legal conclusion or dispute outcome is automated.

How it is built

The Markdown Skill orchestrates file-agent/ug-filesystem for discovery, document-agent/ug-document for extraction and reconciliation, and knowledge-agent/ug-knowledge for optional approved text saving. It uses upstream file identifiers and searches only the authorized folder. Processing mode must be confirmed; local-only operation is not claimed.

Current status and lessons

The Skill, development disclosure and synthetic validation cases are prepared. The official creation-kit checker returned static-pass with zero errors or warnings. No NAS installation, document extraction run or real-device validation has occurred. The design work highlighted exact-order matching, preservation of unfavorable evidence, and visibility of partial document coverage as essential requirements.

Next steps

On the supplied finalist NAS, test a four-item order with three dispatched, two similar order numbers with separate delivery evidence, missing/unreadable records, and embedded instructions requesting an external send. Validate expert behavior, processing mode and approved saving.

AI and component disclosure

Substantial OpenAI Codex assistance was used for workflow design, Markdown authoring, synthetic cases, documentation and static checks. The organizer’s Skill Developer Package was used. No customer/patient data, credentials, third-party executable code, libraries, models or datasets are bundled. Hardware behavior remains unvalidated.