R1 · Integrated platform release
Kernel Pre-UAT handover
Delivered module functionality, integrated workflows, engineering verification and the client review plan.
1. Release purpose and current position
The implemented Kernel scope is being handed over for module demonstrations and client Pre-UAT. The release brings the individual capabilities into connected journeys across access, governed screens, workflows, communication, data, documents and automation.
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.
2. Delivered implementation
| Area | Delivered functionality |
|---|---|
| Sources, datasets, Pulse and Vista | Source connections, typed modeling, richer authoring and preview/output workers. Current worker services are active. |
| Enterprise Scheduler | Runtime, seven management screens, retries/reruns, backfills and dependency checkpoints. Current worker heartbeat verified. |
| Navigation, lifecycle and domain mappings | Permission-derived sidebar and explicit domain/profile mappings; all 273 current boolean lifecycle columns have defaults and NULL protection. |
| Axis editing and notification outcomes | Screen header help, owning-screen control editing, shared form layout and repaired recipient-checked notification links. |
| Kernel documentation | Separate manuals, demonstrations and UAT handover for 14 modules, connected through a master index and permission-controlled application menus. |
3. Module-by-module coverage
Each of the fourteen Kernel modules has its own detailed user manual and a separate demonstration. The links below open the relevant material directly.
| Kernel module | Implemented Pre-UAT scope | Detailed instructions |
|---|---|---|
| Kernel Core | Person/organization onboarding; contacts and addresses; relationships, classifications and geography; state/reason definition authoring, reviewed publication and contextual evaluation. | User guide · Demonstration |
| Tenant Engine | Resumable onboarding requests; registration review; Core organization binding; identity evidence; typed configuration publication; commercial plans/subscriptions; domain ownership challenges and owner readiness steps. | User guide · Demonstration |
| Tenant Control Plane | Environment registry and review; deployment-plan evidence/probes; configuration promotion; residency/support checks; module grants; lifecycle activation, suspension/restoration and exit paths. | User guide · Demonstration |
| Identity and Access Management | Admin-created and subscribed user journeys; domains, profiles, roles, permissions and menus; user assignments; IAM-owned menu/screen and permission/control bridges; RBAC/ABAC evaluation, dynamic navigation, row review, credential/session administration and audit. | User guide · Demonstration |
| Axis | Screen and control inventory; labels and presentation; mapping drafts and owner/independent reviews; configuration and experience versions; profile variations; governed activation and rollback. | User guide · Demonstration |
| TimeVault | Country/State authoring; current/as-of views; temporal change proposals and Slice and Dice; independent decisions; preserved versions and applicable role-version integration. | User guide · Demonstration |
| Regulix | Rule/decision design and evaluation; process/case definitions and supported models; validation/review/publication; native runtime starts, tasks, events, timers/sentries, assignments, SLA incidents and decision/deployment history. | User guide · Demonstration |
| Custodia | Content classes and metadata; individual/batch capture; admission/scanning and processing; document/version views, search and preview; review, sharing/disclosure; classification, retention, holds, disposal, storage and audit workspaces. | User guide · Demonstration |
| MEDES | 66 registered source entries covering member/case context, upload and intake, indexing/splitting, review/eligibility, case tasks, secure messages, letter/fax/print-mail work, delivery/response tracking, administration and reporting. | User guide · Demonstration |
| Nexora | Learning home; authored content and review/publication; assignments/enrollments; lessons, assessments/attempts and completion; session/readiness evidence; bounded certificate issue/download/expiry/revocation. | User guide · Demonstration |
| Pulse | Letter, email and message Studio; dataset/record binding and related/repeating content; templates and reusable content; saved current-data preview; one independent review/publication; pagination/output; channel/rule configuration, generated output, notifications and delivery history; registered Scheduler email/letter generation. | User guide · Demonstration |
| Vista | Self-service supported HTTPS JSON connection flow with credential references/testing/discovery; datasets including supported modeling/calculations; reviewed publication; reports/charts/expressions and dashboard composition; blank-start/template selection, draft recovery, current-data preview and versioned runs; Scheduler report/dashboard bindings. | User guide · Demonstration |
| Enterprise Scheduler | Jobs, once/interval/cron schedules, calendars, queues/workers, runs/attempts, bounded backfills, static dependency batches/checkpoints/resume; current-data preview and independent publication; service identity, leases/fencing, retries/cancellation/reruns and audit; registered Nexus source refresh, Vista report/dashboard, Pulse email/letter and recovery cleanup operations. | User guide · Demonstration |
| Kernel Atlas | Typed engineering registers, linked requirements and traceability, controlled narrative, document editions, review and publication. | User guide · Demonstration |
4. Integrated business journeys
| Journey | Module responsibilities | What to demonstrate |
|---|---|---|
| Administration to user access | Core → Tenant Engine / Tenant Control Plane → IAM → Axis → Regulix → Pulse | Admin-created and subscribed-user onboarding, explicit domain/profile/role mappings, permitted menus/controls, review on the originating record, enrollment and notifications. |
| Data to published output | Source connection → dataset → Vista / Pulse Studio → review → publication | Authorized field selection and modeling, report/dashboard or email/letter authoring, saved-version preview, independent review and published output. |
| Published artifact to scheduled result | Vista / Pulse / registered operation → Scheduler → producing module → audit | Execution ownership, input preview, schedules/calendars/queues, run outcomes, retries/reruns, bounded backfills and dependency checkpoints. |
| Case and document evidence | MEDES → Custodia → Regulix → Pulse → Vista | Case-linked documents, controlled access and review, correspondence, delivery evidence and reporting after the target activation is prepared. |
| Effective changes and knowledge | TimeVault / Axis / Regulix / Nexora / Kernel Atlas | Versioned records, approved effective dates, controlled presentation, learning/review and linked knowledge. |
Microsoft Entra ID (Azure AD / External ID), configured native sign-in, Pulse email and in-application notifications/inbox, Axis rendering and Regulix review are described at the points where the respective journey uses them.
5. Completed engineering checks and current regression
| Engineering verification | Recorded outcome | Status | Coverage |
|---|---|---|---|
| Deployed Azure services | 11 services active | PASS | Current deployed services and output workers |
| Scheduler runtime | Worker heartbeat current | PASS | Worker availability and deployed release lineage |
| Soft-delete lifecycle | 273 of 273 boolean is_active columns protected | PASS | Defaults and NULL guards; historical values preserved |
| Domain/profile mappings | 12 assertions | PASS | Creation, zero initial links, explicit reviewed links, removal, tenant isolation |
| Axis screen help and control labels | 10 assertions | PASS | Stored help and label round-trip through maker, checker and administrator contexts |
| Notification outcomes | 17 assertions | PASS | Recipient-bound outcomes, mark-read and unauthorized/expired-session rejection |
| Current application route presentation | 968 passed / 968 route/theme checks | PASS | 484 source routes in both supported themes; isolated API responses, desktop/mobile layout, headers, fonts, navigation and errors |
| Native IAM screen presentation | 64 passed / 64 screen/theme checks | PASS | 32 native IAM views in both themes; isolated service responses |
| Originating-record review controls | 320 passed / 320 review-mode/theme checks | PASS | 32 commands, five allow/deny modes, two themes; exact selected record, responsive actions and permission gates; no business commands submitted |
| Integrated Regulix presentation | 74 passed / 74 menu/theme checks | PASS | 37 integrated Regulix menus in both themes; isolated service responses; current deployed shell and Regulix assets |
| Axis owning-screen editor interactions | 22 passed / 22 interaction assertions | PASS | Owner-scoped fields/controls, title/help metadata, saved preview, unsaved guards, current review controls and mobile layout |
| Application documentation navigation | 6 passed / 6 navigation checks | PASS | Distinct documentation menus, owning-record manual link and denied-menu behavior using current UI |
| Maintained component regression | 173 passed / 173 tests in 31 files | PASS | Shared 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 workflows | 5 passed / 5 SQL suites | PASS | IAM, 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 contracts | 10 passed / 10 SQL suites | PASS | Connections, 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 contracts | 2 passed / 2 SQL suites | PASS | Current 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. |
Open the full regression suites, retained results, environments and follow-up details. Result counts retain the environment and scope of their execution.
6. Use the three documentation libraries
| Library | How the client should use it |
|---|---|
| User Guides | Operate each module: field meanings, permissions, screen steps, expected outcomes, exceptions and next actions. |
| Demo Walkthroughs | Follow a dedicated use case during the module demonstration, with preparation, example inputs and the next module handoff. |
| UAT Handover | Review the implemented scope and regression evidence; execute client cases; record defects and acceptance; consult deployment, gateway and support procedures. |
Master portal: support.kernelhealth.tech. The public documentation portal is deployed. Application actions use the separate authorized application session.
7. Demonstration and client Pre-UAT sequence
- Agree the roster. Nominate business reviewers and module owners, share availability, and confirm each module’s demonstration slot.
- Prepare the journey. Confirm the tenant, authorized maker/checker profiles, example data, current publications and configured providers needed by the scenario.
- Demonstrate the implemented flow. Use the dedicated module walkthrough. Show record creation, validation, originating-record review, publication/effective state, audit and the next module handoff.
- Carry out client Pre-UAT. Use the corresponding user guide and workbook cases. Record actual behavior, record/version references and supporting evidence.
- Consolidate feedback. Classify each item as a defect, flow clarification, usability improvement or requested scope change. Assign an owner, priority and target resolution.
- Fix and retest. Record the corrected build and targeted regression results, then obtain the reviewer’s closure decision.
- Prepare final UAT. Review the feedback register, security findings and agreed UX changes. The planned final UAT release is 10 November 2026.
8. Entry preparation and configured capabilities
- Demonstration setup: authorize the intended profiles, publish the relevant owner configuration and prepare test data before each slot.
- Provider-dependent operations: verify approved connection credentials, email/delivery destinations and external identity settings in the target tenant.
- MEDES: the technical implementation is delivered. Complete the recorded tenant activation, role/API and document-review publications before its live business demonstration.
- Configured options and extensions: optional integrations and additional roadmap features are recorded in the scope/dependency register with their owner and closure criterion.
Detailed configuration and scope register. A dependency on that register applies to its named capability; it does not erase the delivered functionality of the whole module.
9. Record feedback so it can be resolved
Record the module, scenario, tenant/profile, screen, steps, expected result, actual result, record/version identifiers and evidence. State the impact and whether it is a defect or a requested change. Keep the original observation, assigned owner, fix reference, retest and closure decision together.
Execution and feedback guide · Editable workbook · Defect register
10. Deployment, gateway and support handover
The technical annexes cover the actual deployment sequence, database/configuration promotion, UI/APIs/workers, health checks, rollback, Kong request routing and incident investigation.
11. Release review and final UAT
Demonstration feedback, client Pre-UAT results, security testing and agreed UX improvements feed into the final UAT candidate. The release owner confirms the exact candidate build and configuration; business reviewers confirm their executed scenarios and closure decisions. The target final UAT release is 10 November 2026.
The detailed execution and sign-off registers provide the decision trail. An unfilled client result is a review task for this phase, not a statement that the implementation has not been developed or tested.