Reusable workspaces, plugins and skills, with their provenance.
The directory tells you what exists and where to fetch it. The bytes, the keys and the trust stay with the network that published them — BatonCloud is a locator, not a store. Looking for the networks themselves? They are on Network.
Open resources
Workspace templates, skills, knowledge, policies and workflows — each with what the registry knows about where it came from.
Showcase · Resource DNA sample
Examples of a signed DNA record.
1–5 of 47 showcases
Open resources sample
Examples of a fetchable resource — the directory lists none yet.
1–10 of 68 resources
What a DNA record proves
- These exact bytes were registered, by the holder of key
key_id, at a time. - A document's carrier line leads back to a record — and whether the content still matches it.
- When a parent's signed manifest is still present: a verified derivation.
What it does not prove
- That a resource was used. Having it is not running it.
- That similar content is copied content. Similarity is reported as probable, never as a verdict on intent.
- That the carrier line cannot be removed. It is one line; one
sedremoves it.
A checksum is not a signature. The
sha256 on a resource proves the bytes you fetch are the bytes that were published. Only a DNA record — a signature under a named key — says who registered them. And a template that declares no resource request has not declared zero: it renders unknown. See the networks publishing them 