Nairobi · Audit report
Land, finance, fleet and employment — corrected and re-certified
FCTE · Cross-Domain Revalidation
Published audit report · Read the scope with the result
Public audit view. Release-level findings, evidence categories and outcomes are shown here. Internal identifiers, physical mappings, exact thresholds, calibration parameters, repair mechanics and orchestration remain controlled.
Audit summary
Correction pass at a glance
Public release outcome after the cross-domain revalidation pass.
Public findings
What changed
The audit reports the semantic defect class and verified release outcome. Exact probabilities, coefficients, formulas, selection rules and object-level repair steps remain controlled.
| Domain | Finding category | Public finding | Outcome |
|---|---|---|---|
| Land | Geographic valuation realism | Context was not reflected consistently | Corrected · revalidated |
| Finance | Payment-state realism | A certification-relevant state was underrepresented | Corrected · revalidated |
| Fleet | Longitudinal vehicle chronology | A monotonicity edge case remained | Corrected · revalidated |
| Employment | Statutory wage and role diversity | Historical policy floor and role mix required refresh | Corrected · revalidated |
| Insurance | Claims availability | A release-availability issue surfaced during revalidation | Resolved · rechecked |
Assurance
Why this matters
Cross-domain realism depends on more than passing isolated checks. A correction is only closed when the affected release is revalidated and the result remains consistent with surrounding domains.
Source: Nairobi release audit and certification evidence. Public reporting preserves issue category, scope and outcome while internal methods remains controlled.