refactor: rename alknet-secret to alknet-vault
Rename the crate from alknet-secret to alknet-vault to better reflect its purpose as a local key vault (seed management, key derivation, encryption) rather than a network service. Symbol renames: - SecretService → VaultService - SecretServiceHandle → VaultServiceHandle - SecretServiceActor → VaultServiceActor - SecretServiceError → VaultServiceError - SecretProtocol → VaultProtocol - SecretMessage → VaultMessage - ServiceLocked → VaultLocked - alknet_secret → alknet_vault (crate name) Update ADR-008 with vault access pattern: the vault is a capability source, not a service endpoint. The CLI injects derived/decrypted material into operation contexts — handlers never hold vault references.
This commit is contained in:
@@ -20,7 +20,7 @@ Every architectural decision is classified as one of:
|
||||
|
||||
**One-way door** — Reversing this decision requires rewriting significant code across multiple crates or permanently closes a capability door. Examples:
|
||||
- BiStream as a concrete quinn type (closes WASM door permanently)
|
||||
- alknet-secret pulled into alknet-core as a dependency (loses standalone property permanently)
|
||||
- alknet-vault pulled into alknet-core as a dependency (loses standalone property permanently)
|
||||
- ProtocolHandler signature changes (every handler must be rewritten)
|
||||
|
||||
**Two-way door** — Reversing this decision is cheap or additive. Examples:
|
||||
|
||||
Reference in New Issue
Block a user