UNC is an umbrella for several related tools.

unc

The core peer-to-peer file-sharing client.

UNC indexes a local shared folders, registers files with one or more catalog hubs, searches those hubs, browses peers, and fetches files directly from sharing peers.

unc_hub

The catalog hub. The hub is not in the transfer path - it simply helps users find users that have files, then steps aside.

A hub accepts file registrations, tracks peer presence, answers search queries, and returns the Reticulum fetch destination for peers hosting a file.

unc_chat

A room-based chat and blob-sharing prototype.

It supports public and private room concepts, room manifests, retention policy, membership, private-room key epochs, invite packages, and client-side private-room key handling.

unc_agent

A room-driven remote-operations agent.

Because of its design, a room can become more than chat: it can carry signed task requests, results, status, and artifacts across intermittent Reticulum links.

The current implementation is intentionally narrow: trusted controller identities, allowlisted local commands, JSON results, and durable room history.

unc_meta

This site.

The meta repo gathers project documentation, roadmap material, architecture notes, status pages, and public-facing explanations.