Skip to main content
IronKernel Platform

Crew: Credential Management

Credential lifecycle with expiry, verification, and audit metadata supports role-based credential health.

Problem

Credential state drift causes late compliance surprises and manual audit effort.

Capability

Credential states (PENDING/VERIFIED/EXPIRED/REJECTED).

How it works

  1. 1 Track credential state and verification lifecycle.
  2. 2 Monitor expiry and exception conditions.
  3. 3 Propagate credential impact to readiness workflows.

Operational outcomes

  • Faster intervention on expiring or invalid credentials.
  • Improved audit evidence continuity.

Integration boundaries

  • Identity & Lifecycle
  • Readiness & Eligibility

Proof model

Feature-level proof

  • Credential Management scope is defined in product module catalog.

    verified

    docs/products/crew/product.md · Module Catalog > Credential Management

  • 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).