Reusable Crowsi components with independent trust roles. Product registration, CLI composition and installed native helpers belong to vPremises environment operations.
- crowsi-certificate-manager: existing crate identity and publication declaration retained.
- crowsi-control-contracts: existing crate identity and publication declaration retained.
- crowsi-enforcement-point: existing crate identity and publication declaration retained.
- crowsi-independent-verifier: existing crate identity and publication declaration retained.
- crowsi-key-provider: existing crate identity and publication declaration retained.
- crowsi-local-control-bridge: existing crate identity and publication declaration retained.
- crowsi-pa-pep-transport: existing crate identity and publication declaration retained.
- crowsi-policy-administrator: existing crate identity and publication declaration retained.
- crowsi-policy-engine: existing crate identity and publication declaration retained.
- crowsi-rescue-console: existing crate identity and publication declaration retained.
cargo +1.97 test --locked --workspace --all-targets --all-features
cargo +1.97 test --locked --workspace --doc --all-featuresEach crate README and examples describe its public API. Tests and examples use synthetic state; they do not install an authority, service or maintenance timer. Authority, broker, enforcement, independent verification and recovery retain separate roles. Existing wire/schema identifiers and publish=false declarations are unchanged. Repository relocation does not imply a new registry release. Original repository/revision provenance is retained in source-consolidation.json; current LICENSE/NOTICE files remain with their owned source.
OSS responsibility and source completion defines the supported package boundary and required acceptance. It does not declare unexecuted source, distribution or production checks complete.
Dependency updates: repository policy. Registry releases: version tags and GitHub OIDC.