Capability state register

The full operating model, stated honestly

Every capability has an explicit state: CURRENT, FOUNDATION, or VISION. Trade features remain optional and applicability-gated.

A connected operating model for the evidence between a record and a decision.

Capability-state register

Current capability positions

Every capability is published with one explicit state: CURRENT, FOUNDATION, or VISION.

CONTROL

Documents, SOPs, specifications, HACCP/PCP controls, and decision owners define expected behavior.

  • Controlled documents and specificationsCURRENT

    Versioned content, owners, approvals, and expiry signals for SOPs, forms, and standards.

    Evidence-backed foundation for expected controls.

  • HACCP/PCP structures and linksFOUNDATION

    Structured hazardous-analysis logic and preventive-control links are represented in a connected model.

    Critical limits and validation context are modeled.

OPERATE

Daily forms, inspections, production, receiving, sanitation, and evidence capture record what happened.

  • Operational record and form workflowCURRENT

    Daily production, receiving, sanitation, and pre-op evidence tied to responsible roles and scopes.

    Designed as the factual history of what happened.

  • Deterministic scheduling and missing-record detectionFOUNDATION

    Expected checks and recurring record generation establish what should exist before review.

  • Supplier onboarding, COA, and shipment dossierFOUNDATION

    Trade plane content remains optional and applicability-gated for the core operating system.

DETECT

Limits, missing records, deviations, NCRs, and complaints are surfaced immediately for review.

  • Exception and limit detectionCURRENT

    Automated and rule-based detection where possible for excursions and required-record gaps.

    Exception states remain decision candidates until reviewed.

INVESTIGATE

Root-cause work links summary review, 5 Why, fishbone, and 8D evidence.

  • Investigation methods and incident analysisVISION

    5 Why, fishbone, and 8D surfaces are planned as part of a connected incident-response flow.

ACT

Corrective action, hold, disposition, change control, and verification are assigned and tracked.

  • CAPA, hold, and disposition workflowsFOUNDATION

    Corrective and preventive actions move through owners, due dates, and evidence requirements.

    Closure depends on verification outcomes.

TRACE

Supplier, lot, batch, shipment, and recall context stays linked back to exceptions and actions.

  • Supplier, lot, batch, and shipment traceabilityCURRENT

    Recall-ready links between suppliers, lots, transformations, and outbound shipments.

ASSURE

Training, calibration, maintenance, sanitation, and competency checks evidence control effectiveness.

  • Training, calibration, and maintenance assuranceFOUNDATION

    Competency, maintenance, and EMP readiness records provide operational confidence.

    Competency and training are explicit accountability artifacts.

  • Import/export and CARM readinessVISION

    Connected customs and cross-border controls when the Trade domain applies.

PROVE

Audit binders, evidence packages, reports, and management review close the operational loop.

  • Report and audit-package generationVISION

    Reviewable report snapshots and management-review context for evidence-first operations.