This repository defines a reference operational layer for managing threshold-protected secrets.
It specifies procedures, artifacts, and accountability boundaries without implementing cryptography, storage, or automation.
The purpose of this project is to:
- define auditable lifecycle procedures for threshold secrets
- establish normative operational artifacts
- separate cryptographic mechanisms from responsibility and governance
- prevent ambiguity in high-risk secret handling
This repository is specification-first and implementation-agnostic.
This project covers:
- secret lifecycle definition
- rotation, recovery, and revocation procedures
- custody accountability
- formal artifact specifications
It does not provide code, services, or runtime components.
This repository defines operational procedures around threshold secrets (manifests, rotation, recovery, and audit artifacts).
It assumes interoperability with the sealed shamir v1.0.0 reference
implementation, treating the cryptographic primitive as stable and
contractually defined.
This specification may evolve, but changes are expected to be additive and explicitly versioned.
This project does not:
- implement cryptographic algorithms
- store or transport secret material
- manage access control or authentication
- automate operational decisions
- replace KMS, HSM, or key management platforms
docs/ Procedural specifications formats/ Normative artifact definitions
The following documents are normative:
docs/lifecycle.mddocs/rotation.mddocs/recovery.mddocs/revocation.mddocs/threat-model.mdformats/secret-manifest.mdformats/rotation-record.mdformats/custody-log.md
This project prioritizes:
- explicit state transitions
- documented failure over silent success
- accountability over convenience
- auditability over automation
- governance over tooling
This repository is intended for:
- security architects
- compliance and audit teams
- organizations managing high-impact secrets
- engineers designing threshold-based systems