Inspiration
A folder can contain every expected filename and still leave the next person unsure what was approved, which version matters, or whether two documents disagree. Handoff Ledger was designed around that gap: review an explicit handover checklist against the documents, and preserve what the evidence does not establish.
What it does
Handoff Ledger is an initial UGOS Skill for reviewing authorized NAS project documents. The user supplies the source folders and checklist. The proposed workflow inventories up to 20 documents and 10 requirements, groups identical-content copies, reads the relevant evidence, and checks source hashes again before reporting.
Each requirement receives one of four states: FOUND, CONFLICT, NOT_FOUND_IN_REVIEW, or UNVERIFIED. The ledger keeps short excerpts and their actual source locations, file coverage, duplicate aliases, and concrete next actions. An unreadable file cannot become a claim that evidence is missing. A changed document makes the affected conclusion unverified. The report is a review aid, not a certification that the handover is complete.
The user sees the report in chat first. Saving a new Markdown report is optional and requires approval for the content and destination. Source documents are not changed.
How it was built
The package was newly authored for this hackathon on October 29, 2026 using the official UGOS Skill Creation Tool 0.7.3 and capability catalog 2.0.0. It contains a Markdown Skill, a report contract, delegation examples, and a validation plan.
The parent Skill delegates inventory and hashes to the registered file expert, document reading and comparison to the document expert, and an approved save to the knowledge expert. It does not add executable scripts, its own model, or an external API. Inference behavior depends on UGREEN's configured platform; fully offline processing is not claimed.
What was checked, and what remains
The official static checker reported zero errors and zero warnings. A simulated review examined three cases: a source changing during review, conflicting dates, and a denied document read. The contract was revised to preserve those outcomes as uncertainty or conflict.
These checks are not NAS execution. Installation, expert responses, permission behavior, repeat runs, and actual saved-file verification remain untested on a real UGREEN NAS. If selected as a finalist, the validation plan will be run on the assigned device before any runtime-success claim is made.
AI assistance and dependencies
OpenAI Codex authored and revised the Markdown, drafted the proposal, and performed static and simulated reviews under the entrant's direction. No customer research, user testimonials, or measured productivity improvements are claimed. The package redistributes no third-party code, model weights, dataset, or UGREEN tool source. It depends on UGREEN's registered experts and platform-configured models. The original submission remains the author's work, subject to the contest permissions granted on entry.
Built With
- markdown
- ugos
Log in or sign up for Devpost to join the conversation.