Kernel ยท Pre-UAT release

Delivered implementation and verification

AreaDelivered functionality
Sources, datasets, Pulse and VistaSource connections, typed modeling, richer authoring and preview/output workers. Current worker services are active.
Enterprise SchedulerRuntime, seven management screens, retries/reruns, backfills and dependency checkpoints. Current worker heartbeat verified.
Navigation, lifecycle and domain mappingsPermission-derived sidebar and explicit domain/profile mappings; all 273 current boolean lifecycle columns have defaults and NULL protection.
Axis editing and notification outcomesScreen header help, owning-screen control editing, shared form layout and repaired recipient-checked notification links.
Kernel documentationSeparate manuals, demonstrations and UAT handover for 14 modules, connected through a master index and permission-controlled application menus.

Engineering verification

Engineering verificationRecorded outcomeStatusCoverage
Deployed Azure services11 services activePASSCurrent deployed services and output workers
Scheduler runtimeWorker heartbeat currentPASSWorker availability and deployed release lineage
Soft-delete lifecycle273 of 273 boolean is_active columns protectedPASSDefaults and NULL guards; historical values preserved
Domain/profile mappings12 assertionsPASSCreation, zero initial links, explicit reviewed links, removal, tenant isolation
Axis screen help and control labels10 assertionsPASSStored help and label round-trip through maker, checker and administrator contexts
Notification outcomes17 assertionsPASSRecipient-bound outcomes, mark-read and unauthorized/expired-session rejection
Current application route presentation968 passed / 968 route/theme checksPASS484 source routes in both supported themes; isolated API responses, desktop/mobile layout, headers, fonts, navigation and errors
Native IAM screen presentation64 passed / 64 screen/theme checksPASS32 native IAM views in both themes; isolated service responses
Originating-record review controls320 passed / 320 review-mode/theme checksPASS32 commands, five allow/deny modes, two themes; exact selected record, responsive actions and permission gates; no business commands submitted
Integrated Regulix presentation74 passed / 74 menu/theme checksPASS37 integrated Regulix menus in both themes; isolated service responses; current deployed shell and Regulix assets
Axis owning-screen editor interactions22 passed / 22 interaction assertionsPASSOwner-scoped fields/controls, title/help metadata, saved preview, unsaved guards, current review controls and mobile layout
Application documentation navigation6 passed / 6 navigation checksPASSDistinct documentation menus, owning-record manual link and denied-menu behavior using current UI
Maintained component regression173 passed / 173 tests in 31 filesPASSShared lifecycle, application navigation and record page; current Scheduler, source/dataset, report/dashboard and preview components. Per-test source fixtures were aligned with current routing and resource loading.
Native module workflows5 passed / 5 SQL suitesPASSIAM, TimeVault, Custodia, Nexora and Regulix: permissions/context, independent review, exact-version checks, replay, lifecycle and notification queue handoffs. Fresh production database clone; transaction-local test context; fixture writes rolled back; no external delivery.
Current Studio data/output contracts10 passed / 10 SQL suitesPASSConnections, dataset modeling/review, report/dashboard previews, Pulse previews/bindings/generation rechecks, working copies, analytical layout and source review. Fresh production database clone; transaction-local test context; fixture writes rolled back; no external delivery.
Scheduler storage, recovery and dependency contracts2 passed / 2 SQL suitesPASSCurrent database clone: durable storage lifecycle, retries, fencing, crash recovery, soft retirement, tenant-context rejection, immutable evidence, dependency ordering, invalid edges/cycles, version pins and execution bounds. Fixtures satisfy current foreign keys; all writes rolled back; no external operation executed.

Client Pre-UAT phase

How to read the status: implementation delivery, engineering regression and client acceptance are separate milestones. The engineering results below describe work already tested. The editable client case results begin Awaiting client validation because this handover starts the client Pre-UAT phase.

Security testing and user-experience refinements continue during Pre-UAT. The final UAT decision will include closure or explicit acceptance of the relevant findings and the agreed review outcomes.

The public documentation is deployed at support.kernelhealth.tech.

Read the complete Pre-UAT handover