Vowgap

Find the promise a design change broke.

Inspiration

An approved property revision can reach the technical team while old promises survive in brochures, scripts and signed reservations. The difficult question is which promise applies to which unit and date.

What it does

Vowgap creates a source-linked promise-impact register from authorized NAS records. It separates future marketing corrections from existing commitments requiring responsible human review. In the synthetic Cedar Quay case, one Type B parking change identifies stale brochure and script claims, routes two signed reservations for separate review, and excludes Type A.

How we built it

A seven-file Markdown Skill uses the official UGREEN creation kit 0.7.3 and catalog 2.0.0. The parent delegates to file-agent, document-agent and knowledge-agent for supported discovery, extraction, reconciliation and separately confirmed report saving. Approval evidence, exact identity and effective dates control conclusions. A later unsigned draft never replaces an approved record.

Development and validation

The native orchestration instructions are implemented and the official static checker returned zero errors and warnings. Development fixtures and local packaging checks are kept outside the Skill ZIP. No NAS installation, runtime execution, measured accuracy or performance improvement is claimed. Model-only exercises, where recorded, are simulations rather than NAS tests.

Boundaries and challenges

Missing or conflicting evidence remains unresolved. Vowgap does not amend agreements, send customer notices or provide legal or engineering sign-off. It preserves source records. Saving requires separate confirmation and safe creation of a new file; otherwise the report stays in conversation. Confidential records must not be transmitted to external services. Native permissions, file formats and save semantics still require target-device validation.

What we learned and what comes next

Capability catalogs establish available operations, not successful device behavior. If selected, validate discovery/read/save on synthetic inputs in the assigned NAS, then run the core cases and failure suite and record an actual demonstration.

Built With

• markdown