Skip to main content
IronKernel Platform

Crew: Governance & Compliance

Encryption, signed evidence storage, and compliance packet exports are implemented with redaction controls.

Problem

Encryption, signed evidence storage, and compliance packet exports are implemented with redaction controls.

Capability

PII encryption at rest (AES-256-GCM).

How it works

  1. 1 Encryption, signed evidence storage, and compliance packet exports are implemented with redaction controls.
  2. 2 Regulatory-rule execution and exception handling now enforce audit-ready decision capture.

Operational outcomes

  • Encryption, signed evidence storage, and compliance packet exports are implemented with redaction controls.
  • Regulatory-rule execution and exception handling now enforce audit-ready decision capture.

Integration boundaries

  • Identity & Lifecycle
  • Readiness & Eligibility

Proof model

Feature-level proof

  • Governance & Compliance scope is defined in product module catalog.

    verified

    docs/products/crew/product.md · Module Catalog > Governance & Compliance

  • Crew readiness and eligibility signals are implemented for assignment-gating workflows.

    verified

    docs/products/crew/product.md · Module Catalog > Readiness & Eligibility

    Code: backend/services/crew/internal/readiness

    Contract: proto/crew/v1

  • Crew readiness and eligibility decisions are implemented in dedicated service modules.

    verified

    docs/products/crew/product.md · Module Catalog > Readiness & Eligibility

    Code: backend/services/crew/internal/readiness

    Contract: proto/crew/v1

Solution routes that reuse this feature

Open these solution and feature-map routes to test this behavior in end-to-end buyer workflows (2).