A tiny convention that tags a directory with machine-readable context — what it is, how critical it is, what it needs. So your configuration travels with the service, not the admin.
pip install folder-nature
Every folder in your infrastructure means something — but that meaning lives in the
admin's head, in scattered config, or nowhere at all. folder-nature writes it down,
right next to the thing it describes, in a small .folder-nature file.
Now tools can read what a directory is for before they touch its contents. Move it to another host and the context moves with it — no rebuilding configuration from scratch.
.folder-nature under a root and returns a single verdict.
Shipped since v0.2.0. Nine of the sixteen CLI commands
cover it, and about two-thirds of the code lives here. Signing and
watermarking answer who published this and has it been
altered — stated plainly inside the tool itself, they do
not prevent copying. cp beats any in-file
mechanism, and we have zero visibility into a customer's machine. What
the mark layer makes is a copy that is checkable.
compile() before write.verify --root — one verdictStructure, folder marks, file signatures, manifest↔disk parity, and optional per-file selftests. Everything green, or a named failure RED. No partial pass.folder-nature keygen --out ~/.config/folder-nature/signing.key
folder-nature stamp . --number 0
folder-nature sign . --key ~/.config/folder-nature/signing.key
folder-nature verify . --root --pubkey ~/.config/folder-nature/signing.key.pub pip install folder-nature
folder-nature init . --template workspace --name "my-workspace"
folder-nature show .
folder-nature search . --tag client
folder-nature verify . --root Install it, star it, ship it. Building a commercial product on top and want it without the open-source obligations? There's a license for that.