Inspiration

A contractor says the job is done and asks to be paid. Before anyone signs, the request for acceptance (RFA) travels to onsite, network, procurement and finance teams, and each one asks for the same report and photos. Signing can take more than a month. Nobody's job is to compare the contractor's photos with the delivery notes and earlier jobs, so a reused photo or a quantity gap is caught late, or never. The idea comes from first-hand experience of contractor acceptance.

What it does

On the Record is a UGOS Skill that checks every line of an RFA against the records already on the NAS: the purchase order, delivery notes, site visit reports, test reports and site photos. Each line gets one of four verdicts (verified, mismatch, no evidence, needs onsite check), each citing a file path, a date and its type (captured, stated or modified), and a quote or photo field. The pack shows the amount ready to sign, the amount on hold, and one request per unresolved line. It also flags submitted photos that are byte-identical to photos from another job. Nothing is written until the user approves.

How we built it

The Skill is a Markdown-only orchestration package that follows the Uliya Skill Development Standard (kit 0.7.3). It delegates to four registered experts:

  • document-agent (extract, reconcile): reads the RFA and reconciles it with the PO, delivery notes and site reports;
  • file-agent (find, scan-dedupe): finds the job's records and detects reused photos across the archive;
  • photo-agent (meta, vision-ocr): reads capture time, GPS and label text;
  • knowledge-agent (save-text): saves the report, after approval.

Each step passes only real upstream results, and all five delegation states are handled. The package passes the kit's static checker with 0 errors and 0 warnings. A fictional test archive (6 documents, 34 photos with EXIF and GPS, a planted photo reuse and planted gaps) comes with an answer key for the finalist test day.

Challenges

Keeping claims honest. A photo can't prove a cable length or a port test. A file's modified time changes when it's copied. An unreadable label is neither a match nor a mismatch. The verdict rules encode each of these limits.

What's next

Running it on a real UGREEN AI NAS: the document-to-photo hand-off, duplicate scanning across shares, and OCR on small asset labels. Then reusing the same evidence pack at every signature, from RFA to final acceptance.

All companies, people, serials and prices in the test data are fictional.

Built With

Share this project:

Updates

Submission history