Inspiration
Construction teams often reconcile change requests, approval notes, and invoices by hand. A charge may look reasonable while its approval, scope, or billing basis is unclear. We wanted a focused way to examine those relationships without treating a plausible AI answer as proof.
What it does
ChangeTrace proposes a Change Evidence Chain for three documents explicitly selected by the user: a change request, an approval note, and an invoice.
It is designed to show source-supported observations, flag missing or conflicting evidence, and compare amounts only when the project, change, currency, tax treatment, and billing basis are sufficiently supported. Unverified observations are excluded from matching and calculations.
A documented difference is a prompt for human review—not a legal conclusion, signature verification, or determination that payment is due.
How we built it
We authored a Markdown Uliya Skill that delegates path inspection and document analysis to registered experts. The intended workflow uses file-agent with ug-filesystem stat, followed by document-agent with ug-document qa or extract, one selected file at a time.
The Skill requests read-only actions, does not search for substitute files, and does not save or transmit a report. Actual runtime behavior and data handling depend on the UGREEN environment and remain unverified.
Challenges we ran into
A completed expert delegation does not necessarily prove that a file was accessible or that an extracted fact has inspectable source evidence. The available documentation also does not guarantee per-observation attribution or single-file enforcement.
The Skill therefore requires evidence and stops dependent comparisons when support or scope cannot be established.
Accomplishments that we're proud of
We created a narrowly scoped Skill with explicit evidence gates, financial-comparability checks, failure handling, and a controlled test for conflicting approval records.
The Skill passed a static checker obtained from a third-party mirror; the mirror's official provenance has not been independently verified. Six fictional PDF fixtures were checked locally.
What we learned
A useful evidence review must distinguish an unsupported observation from a verified absence. It must also explain when a calculation is withheld rather than filling gaps with assumptions.
What's next for ChangeTrace
If selected as a finalist, we plan to test the Skill on the assigned UGREEN NAS. The priority is to verify actual expert delegation, single-file scope, PDF handling, and inspectable source attribution before relying on any comparison.
No Uliya expert or NAS workflow has been tested yet.
Built With
- ai
- markdown
- ugreen
- uliya
