Shared, declarative manifests for cryptographic contexts/slots across the BlackCat ecosystem.
Manifests describe:
- AEAD/HMAC slot names (
core.crypto.default,core.hmac.csrf, ...), - key requirements (
type,length), - optional rotation policies and KMS bindings (consumed by
blackcat-crypto).
This repository is intentionally data-only: JSON/YAML manifests are loaded by blackcat-crypto,
blackcat-crypto-js, and other ecosystem components so slot naming stays consistent and audited.
blackcat-crypto-manifests/
├── README.md
├── docs/
│ └── ROADMAP.md
└── contexts/
└── core.json
Point your runtime config at a manifest file (recommended):
{
"crypto": {
"manifest": "../blackcat-crypto-manifests/contexts/core.json"
}
}blackcat-crypto loads the manifest via CryptoConfig and registers defined slots + rotation
policies in CryptoManager. CLI commands can also accept --manifest=path explicitly.
Validate manifests:
bin/manifest-lint [contexts-dir]Each manifest contains:
{
"slots": {
"core.crypto.default": {"type": "aead", "key": "crypto_key", "length": 32},
"core.hmac.csrf": {"type": "hmac", "key": "csrf_key", "length": 64}
},
"rotation": {
"core.crypto.default": {"maxAgeSeconds": 2592000, "maxWraps": 5}
}
}Add new slots/contexts here and reference the updated manifest from other repos. No duplication.
This repository is an official component of the Blackcat Covered System. It is licensed under BFNL-1.0, and repository separation inside BLACKCAT_MESH_NEXUS exists for maintenance, safety, auditability, delivery, and architectural clarity. It does not by itself create a separate unavoidable founder-fee or steward/development-fee event for the same ordinary covered deployment.
Canonical licensing bundle: