Inspiration
A document archive is useful only when people can tell which sources were inspected, which changes they approved and whether the copies actually match. SE6 Evidence Archive brings those questions to the UGREEN Automate Your Workflow track.
It is a focused application of SE6Triad, an experimental persistent state-transition architecture linking observation, awareness, relational mapping, authorized interaction, verification and renewal. Its Four Pillars—Authenticity, Integrity, Responsibility and Enrichment—motivate source-linked explanations, checked copies, explicit permission and useful organization. The broader architecture is a research vision; this Skill implements a narrow proposed workflow, not the complete SE6 system.
What it does
The Markdown orchestration Skill is designed to inspect authorized documents, present a source-linked archive plan, obtain approval for exact source/destination mappings, recheck sources before writing and create copies without overwriting existing destinations. Originals remain intact. Fresh source and destination SHA-256 reads check the resulting copies.
Filesystem work is delegated to the officially supported file-agent; read-only document questions go to document-agent. A missing permission, changed source or destination collision must stop the affected operation rather than produce a false success claim.
How we built it
The initial package was newly authored during this hackathon using the official Uliya Skill Kit 0.7.3 English capability catalog and controlled checker. It contains SKILL.md and three directly linked Markdown references. ChatGPT/Codex assisted capability review, design, authoring, static validation, proposal preparation and application drafting. Original package content is offered under MIT. No private SE6 source, credentials, model weights or external API dependency are included.
Challenges we ran into
The central design challenge is separating an agent's intended action from an observed result while staying inside the official expert-agent workflow. Approval must cover the actual copy mappings, and checks must use current source and destination state.
NAS access and runtime validation remain pending. Installation, expert behavior, permissions and model processing arrangements have not been validated on a NAS. Separate readback uses the same platform expert; it is not an independent security authority and cannot establish document truth, authenticity or immutable provenance.
Accomplishments that we're proud of
The official controlled checker reports static-pass with zero errors and zero warnings. The initial Skill package and proposal PDF were submitted for Round 1. The workflow specifies bounded authorization, preservation of originals, no overwrites and explicit failure reporting.
These are design and static-validation accomplishments. No successful NAS execution, SkillHub publication, general AI superiority or guaranteed safety is claimed.
What we learned
Verifiable organization requires more than a plausible summary. Source identity, approval boundaries, changed inputs and fresh readback need explicit treatment. Static checks help establish package conformance, but only runtime tests can reveal whether the platform executes the workflow as intended.
What's next for SE6 Evidence Archive
If selected, use the assigned NAS to test an approved two-document archive, approval refusal with no writes, and changed-source/destination-collision cases. Preserve actual outputs, record failures and verify originals remain intact. Runtime findings will determine revisions; a working demonstration is still required before claiming operational NAS support.
Log in or sign up for Devpost to join the conversation.