Description
WonderPhi Vault — Batch Security Recipe Library for WonderPhi Compute
Inventor: Christopher Gabriel Brown
Patent status: Patent pending — see PATENT_PORTFOLIO.md for the full portfolio of Christopher Gabriel Brown’s filings
IP protection: U.S. copyright (17 U.S.C. § 102(a)(1)) and applicable international treaties
Version: 1.0.0
SKU: 2102
Status: Ready for distribution — working software
Overview
WonderPhi Vault is a companion library to WonderPhi Compute that provides 30 batch recipes covering encryption, signing, hashing, certificate lifecycle management, secrets scanning, and PII redaction. It does not encrypt or sign anything itself — it reads a folder of input files (or a list of targets) and writes a plain-text .plan.wpc.txt file: one command per input, ready to feed to wpc.exe for parallel execution across every CPU core.
The entire tool is a single Python script — wpv-recipe.py — built on the Python standard library alone. There are zero external dependencies, zero pip install steps, no network access, and no telemetry. It requires Python 3.8 or higher. The recipes drive well-known, industry-standard command-line tools that must already be installed on the operator’s machine: certutil , openssl , gpg (Gpg4Win), 7z , signtool.exe , ssh-keygen , exiftool , curl , and findstr .
The library never modifies wpc.exe . The 10 Commandments (the constitutional framework of WonderPhi Compute) remain intact at all times.
Source metrics
Metric Value
Total recipes 30
Recipe categories 9
Source files (excluding release archive) 6
Main script ( wpv-recipe.py ) 317 lines · 14,968 bytes
README ( README.md ) 125 lines · 4,150 bytes
Recipe index ( INDEX.md ) 44 lines · 3,322 bytes
Retail license ( LICENSE ) 127 lines · 4,919 bytes
Industrial license ( LICENSE-INDUSTRIAL.txt ) 147 lines · 6,163 bytes
Release archive ( wonderphi-vault-v1.0.0.zip ) 8,944 bytes
Python version required 3.8+
External Python dependencies 0 — standard library only
Plan-file header # WPC v1
Recipe categories and complete recipe list
All 30 recipes are organised into 9 categories. Each recipe operates in one of two input models: files (scan a folder for matching file extensions) or lines (one target per line in a text file).
Hash & Integrity (5 recipes)
Recipe Model Needs Description
sha256-each files certutil (built-in) SHA-256 each file to a sidecar — tamper-evident archive
sha256-manifest files certutil (built-in) SHA-256 each file + combined MANIFEST-sha256.txt (evidence bag); includes a barrier/post step that concatenates all individual hashes
sha512-each files certutil (built-in) SHA-512 each file — higher-assurance archival
md5-each files certutil (built-in) MD5 each file — legacy compatibility only
verify-manifest files certutil (built-in) Re-hash each file and write current SHA-256 for post-transit verification
GPG / PGP (5 recipes)
Recipe Model Needs Description
gpg-encrypt-each files gpg (Gpg4Win) GPG-encrypt each file to a recipient key (set --tag to recipient key ID)
gpg-decrypt-each files gpg (Gpg4Win) GPG-decrypt each ciphertext ( .gpg , .pgp , .asc ) to a sidecar
gpg-sign-each files gpg (Gpg4Win) Detached-sign each file (set --tag to signing key ID)
gpg-verify-each files gpg (Gpg4Win) Verify each detached .sig signature file
gpg-symmetric-each files gpg (Gpg4Win) Symmetric-encrypt each file (password via --tag )
AES / OpenSSL (2 recipes)
Recipe Model Needs Description
aes-encrypt-each files openssl AES-256-CBC + PBKDF2 encrypt each file (100,000 iterations, salted; password via --tag )
aes-decrypt-each files openssl AES-256-CBC + PBKDF2 decrypt each .enc file (password via --tag )
Archive with Password — 7-Zip (2 recipes)
Recipe Model Needs Description
7z-encrypt-each files 7z (7-Zip) 7z-archive each file with AES-256 encryption, hidden filenames ( -mhe=on ), compression level 7 (password via --tag )
7z-decrypt-each files 7z (7-Zip) Extract each password-protected .7z into its own subfolder
Code Signing — Authenticode (2 recipes)
Recipe Model Needs Description
signtool-sign-each files signtool.exe (Windows SDK) Authenticode-sign each PE/MSI ( .exe , .dll , .msi , .sys , .ocx ); set --tag to /f cert.pfx /p pass /tr timestamp /td sha256 /fd sha256
signtool-verify-each files signtool.exe Verify Authenticode signature on each PE/MSI
Certificates & TLS (6 recipes)
Recipe Model Needs Description
cert-fingerprint-each files openssl SHA-256 fingerprint of each PEM certificate file ( .pem , .crt , .cer , .key )
cert-expiry-each files openssl notAfter (expiry) date of each PEM certificate file
cert-extract-chain lines openssl Dump the full certificate chain from each host:443
tls-cipher-audit lines openssl Attempt TLS 1.3 connection with a modern cipher suite on each host (cipher audit)
hsts-check lines curl (built-in) Fetch each URL and report the Strict-Transport-Security header
csp-check lines curl (built-in) Fetch each URL and report the Content-Security-Policy header
Secrets Scanning (3 recipes)
Recipe Model Needs Description
secret-scan-aws files findstr (built-in) Grep each source/document file for AWS access-key ID patterns ( AKIA / ASIA )
secret-scan-github files findstr (built-in) Grep each file for GitHub token patterns ( ghp_ , gho_ , ghs_ )
secret-scan-private-key files findstr (built-in) Grep each file for embedded PEM private-key headers ( BEGIN RSA PRIVATE KEY , BEGIN OPENSSH PRIVATE KEY , BEGIN EC PRIVATE KEY )
PII / Redaction (3 recipes)
Recipe Model Needs Description
pii-scan-ssn files findstr (built-in) Grep each document for US Social Security Number patterns ( NNN-NN-NNNN )
pii-scan-cc files findstr (built-in) Grep each document for 16-digit credit-card number patterns
exif-strip-each files exiftool Strip ALL metadata from each image ( .jpg , .jpeg , .png , .tif , .tiff , .heic , .webp ) in-place after backup
SSH Keys (2 recipes)
Recipe Model Needs Description
sshkey-generate-batch lines ssh-keygen (built-in) Generate an ed25519 SSH keypair per name in the input list
authorized-keys-audit lines OpenSSH client Fetch and SHA-256 each remote host’s authorized_keys file
Input models
Model Recipes using it How it works
files 24 of 30 Recursively scans a folder for files matching the recipe’s extension globs. Supported glob sets: ANY (all files), CERTS_PEM ( .pem , .crt , .cer , .key ), DOCS ( .pdf , .docx , .doc , .txt , .md , .log , .csv , .json , .xml ), IMAGES ( .jpg , .jpeg , .png , .tif , .tiff , .heic , .webp ), BINS ( .exe , .dll , .msi , .sys , .ocx ), SOURCE ( .py , .js , .ts , .go , .rs , .java , .rb , .php , .c , .cpp , .h , .sh , .ps1 ).
lines 6 of 30 Reads a text file with one target (hostname, URL, or name) per line. Blank lines and lines beginning with # are ignored.
Command-line interface
Flag Meaning
--list List all 30 recipes with descriptions, categories, and tool requirements, then exit
--out FILE Path where the plan file is written (default: .plan.wpc.txt )
--outdir DIR Directory where recipe output files are placed (default: wpv-out )
--tag VALUE Value substituted for {tag} in generated commands — recipient key, password, certificate flags, etc. (default: current timestamp YYYYMMDD-HHMMSS )
--stdout Print the plan to the console instead of writing a file
--check Dry run — report how many inputs matched the recipe’s globs; write nothing
External tools required
Each recipe specifies the tool it drives. The tool must be installed and on the operator’s PATH on the machine where wpc.exe runs the plan. Five of the nine tool families are built into Windows and require no installation.
Tool Source Used by
certutil Built into Windows 5 hash/integrity recipes
findstr Built into Windows 5 secrets-scanning and PII recipes
curl Built into Windows 10+ 2 certificate/TLS recipes (HSTS, CSP)
ssh-keygen Built into Windows 10+ (OpenSSH) 1 SSH-key recipe
OpenSSH client Built into Windows 10+ (OpenSSH) 1 SSH-key audit recipe
gpg Gpg4Win (paid download) 5 GPG/PGP recipes
openssl OpenSSL for Windows 6 AES + certificate/TLS recipes
7z 7-Zip (paid download) 2 encrypted-archive recipes
signtool.exe Windows SDK 2 code-signing recipes
exiftool ExifTool by Phil Harvey 1 EXIF-stripping recipe
Plan-file format
Every generated plan begins with the # WPC v1 header line, followed by metadata comments recording the recipe name, description, input model, tag value, and task count. The body contains one shell command per line — each command operates on a single input file or target. Recipes that include a post-processing step (e.g. sha256-manifest ) insert a barrier comment ( # --- barrier --- combine hashes into a manifest --- ) followed by the manifest-concatenation command. The plan is saved as UTF-8 text with the extension .plan.wpc.txt .
Architecture and design principles
Principle Detail
Separation of concerns The library writes the plan. WonderPhi Compute runs the plan. Nothing in this library executes any security operation directly.
Zero dependencies Uses only Python standard-library modules: argparse , fnmatch , sys , pathlib , datetime .
No network access The generator never opens a socket, never phones home, never sends telemetry.
Constitutional integrity Never modifies wpc.exe . The 10 Commandments remain intact.
Template-driven recipes Each recipe is a Python dictionary with name , cat , model , needs , inputs , out_ext , desc , tmpl , and optional post fields. Adding a new recipe requires only appending one dictionary to the RECIPES list.
Deterministic output Given the same input folder and tag, the plan is identical. No randomness.
Encryption specifications
Method Cipher Key derivation Parameters
OpenSSL AES recipes AES-256-CBC PBKDF2 100,000 iterations, random salt ( -salt )
7-Zip archive recipes AES-256 7-Zip internal KDF Compression level 7 ( -mx=7 ), hidden filenames ( -mhe=on )
GPG symmetric recipe Default GPG cipher (AES-256) GPG internal (S2K) Batch mode, passphrase via --tag
GPG asymmetric recipes Recipient’s public-key cipher N/A (public-key) --trust-model always , batch mode
Usage examples
Scenario Command
Tamper-evident archive of an evidence folder python wpv-recipe.py sha256-manifest .\evidence
GPG-encrypt every export to a recipient key python wpv-recipe.py gpg-encrypt-each .\exports --tag ops@company.com
7z with AES-256 and hidden filenames for compliance archival python wpv-recipe.py 7z-encrypt-each .\records --tag "AlphaBravo7Charlie!"
Code-sign every DLL/EXE in a build output python wpv-recipe.py signtool-sign-each .\dist --tag "/f cert.pfx /p pass /tr http://timestamp.digicert.com /td sha256 /fd sha256"
Scan a codebase for AWS keys python wpv-recipe.py secret-scan-aws .\src
Scan for GitHub tokens python wpv-recipe.py secret-scan-github .\src
Scan for embedded private keys python wpv-recipe.py secret-scan-private-key .\src
Flag SSN patterns in a document dump python wpv-recipe.py pii-scan-ssn .\docs
Flag credit-card patterns in a document dump python wpv-recipe.py pii-scan-cc .\docs
Strip EXIF from every image before publishing python wpv-recipe.py exif-strip-each .\photos
Check TLS certificate HSTS headers for every domain python wpv-recipe.py hsts-check .\domains.txt
Dry-run — see how many files match python wpv-recipe.py sha256-each .\evidence --check
Licensing
Licence tier File Key terms
Retail Single-User LICENSE Perpetual, non-exclusive, non-transferable. Tied to the buyer, not to any machine. No seat count, no activation, no telemetry. Personal and commercial use for output delivered to yourself or your own employer. No redistribution.
Industrial (Commercial) LICENSE-INDUSTRIAL.txt Perpetual, non-exclusive, non-transferable. Covers all machines, VMs, containers, and cloud instances operated by a single legal entity. No seat count, no machine limit, no annual renewal. Production and customer-facing workloads permitted. No resale, SaaS, or white-label use without a separate OEM licence.
Both licences are governed by the laws of the State of Georgia, United States of America, with exclusive jurisdiction in the state or federal courts sitting in Gwinnett County, Georgia.
What Is in the Package
File Lines Size Purpose
wpv-recipe.py 317 14,968 bytes The recipe generator — Python, standard library only. Contains all 30 recipe definitions, the file/line scanner, and the plan emitter.
README.md 125 4,150 bytes Product documentation: overview, recipe list, usage examples, CLI options, and file manifest.
INDEX.md 44 3,322 bytes Full recipe table — 30 rows with recipe name, category, input model, external tool requirement, and description.
LICENSE 127 4,919 bytes WonderPhi Software License v1.0.0 — Retail Single-User.
LICENSE-INDUSTRIAL.txt 147 6,163 bytes WonderPhi Software License v1.0.0 — Industrial (Commercial License).
release/wonderphi-vault-v1.0.0.zip — 8,944 bytes Release archive of version 1.0.0.
How this is delivered
This package ships on a single Blu-ray disc, posted to the delivery address on your order. The archive on the disc is AES-256 encrypted; the passphrase is sent separately, by email, once the disc is despatched — so the disc alone is of no use to anyone who intercepts it.
Discs are despatched by tracked, signed-for post. Allow 5 business days for mastering and verification before despatch.
© 2026 Christopher Gabriel Brown. All rights reserved.
Footnotes
- Product number 8521.
- Family: wonderphi.
- Purchase: When you buy, you buy the use of that blueprint only.