Weave Compliance
Compliance interfaces and prototype implementations for local audit, reporting, ethics and governance.
Implementation status
Several types retain Production in their names, but the shipped defaults are scaffolding. Audit storage is in memory; report integrity/signatures, regulatory submission and governance-control labels include placeholders. default_framework() does not establish regulatory compliance. Its GDPR path primarily checks the consent label; several SOX/retention/bias validations are no-ops or fixed results. Read the specific module limitations below before integrating.
At a glance
| Field | Value |
|---|---|
| Crate/package | weave-compliance |
| Version | 0.1.1 |
| Source | libs/weave-compliance |
What developers should learn here
Compliance interfaces and prototype implementations for local audit, reporting, ethics and governance. Read the focused guides for current APIs and implementation limits.
Page map
Audit trail surface and exports.
Ethics framework hooks.
Membership and write-policy controls.
Regulatory framework adapters.
Documentation generators and compliance artifacts.
Declared types, traits, functions, and source provenance.
Source modules
audit— libs/weave-compliance/src/lib.rscompliance— libs/weave-compliance/src/lib.rsdocs— libs/weave-compliance/src/lib.rsethics— libs/weave-compliance/src/lib.rsgovernance— libs/weave-compliance/src/lib.rsprelude— libs/weave-compliance/src/lib.rsregulatory— libs/weave-compliance/src/lib.rs
