Kernel documentation

Kernel · detailed operating flows

Completed journeys, traceability and integration readiness

The documentation contains 205 module journeys across fourteen Kernel modules, four cross-module journeys and one separately identified supporting Asset Operations journey. Manuals and demonstrations have distinct navigation and instructions.

39 additional procedures address the recorded detail gaps. The complete edition has 1131 ordered actions and 768 boundary, permission and recovery checks. A current illustration supplies screen context; the step callout table explains what to locate and which actual record result to inspect.

All 210 worked journeysFlow closure registerPreparation matrixEditable UAT workbook

New dedicated procedures

ModuleWorked procedureManualDemo
Identity and Access ManagementCopy menu access from one or more rolesRead procedurePresent walkthrough
Identity and Access ManagementBulk changes with mixed results and interrupted processingRead procedurePresent walkthrough
Identity and Access ManagementUser Access Hierarchy investigation and drilldownRead procedurePresent walkthrough
Identity and Access ManagementPersonal-information contact preferences and enrollment selectionRead procedurePresent walkthrough
PulseBrowser push opt-in, profile binding and unsubscribeRead procedurePresent walkthrough
PulseAuthor and review the correspondence catalogue before generationRead procedurePresent walkthrough
PulseSuppressed, future and expired generation policiesRead procedurePresent walkthrough
PulseChannel setup and provider-readiness boundariesRead procedurePresent walkthrough
PulsePulse generation queue recovery versus Enterprise Scheduler recoveryRead procedurePresent walkthrough
AxisProfile/locale-specific experience and restrictive overridesRead procedurePresent walkthrough
AxisRollback and the distinction between publication and activationRead procedurePresent walkthrough
CustodiaNested collection moves and inherited collection holdsRead procedurePresent walkthrough
CustodiaTyped internal and external document relationshipsRead procedurePresent walkthrough
CustodiaPrivate page notes independently of redactionRead procedurePresent walkthrough
CustodiaEncrypted supporting-copy creation and integrity verificationRead procedurePresent walkthrough
CustodiaPersisted storage investigations and scheduled reconciliationRead procedurePresent walkthrough
CustodiaMulti-file/ZIP intake and format-specific partial recoveryRead procedurePresent walkthrough
MEDESAdministration, status meanings and owner settingsRead procedurePresent walkthrough
MEDESFax-cover fields and exact reviewed transmission packetRead procedurePresent walkthrough
NexoraDiscussion creation, replies and moderationRead procedurePresent walkthrough
NexoraPolicy authoring/attestation and competency/readiness modelingRead procedurePresent walkthrough
NexoraPolicy authoring/attestation and competency/readiness modelingRead procedurePresent walkthrough
NexoraGoverned evidence-package request, approval, download and revocationRead procedurePresent walkthrough
NexoraLearning administration, FAQ and announcementsRead procedurePresent walkthrough
NexoraLearning administration, FAQ and announcementsRead procedurePresent walkthrough
NexoraLearner saved content, ratings, notes and intelligence viewsRead procedurePresent walkthrough
RegulixTimer wait, due-time advancement and repeated pollingRead procedurePresent walkthrough
RegulixClaim/delegate/release and per-stage task eligibilityRead procedurePresent walkthrough
RegulixCurrent-context and decision/event-driven CMMN sentriesRead procedurePresent walkthrough
RegulixIncident investigation and closureRead procedurePresent walkthrough
RegulixLoop and manually activated multi-instance process workRead procedurePresent walkthrough
RegulixLoop and manually activated multi-instance process workRead procedurePresent walkthrough
RegulixSimulation/process suites and terminal instance archiveRead procedurePresent walkthrough
RegulixSimulation/process suites and terminal instance archiveRead procedurePresent walkthrough
Tenant EngineSeparate parent-relationship and branding change walkthroughsRead procedurePresent walkthrough
Tenant EngineSeparate parent-relationship and branding change walkthroughsRead procedurePresent walkthrough
Tenant EngineCustodia supporting evidence through tenant identity reviewRead procedurePresent walkthrough
Kernel CoreGeneric active/inactive lifecycle with explicit false retainedRead procedurePresent walkthrough
Supporting Asset OperationsSupporting Asset Operations: request, decide, allocate and acknowledgeRead procedurePresent walkthrough

Use requirements and results together

  1. Open the requirement and its linked worked case. The previous case identifiers are preserved alongside the worked IDs.
  2. Prepare the selected profile, synthetic records and exact versions using the chapter and preparation register.
  3. Run the main path and the applicable denied/recovery checks. Record the observed state, returned identity and evidence in the workbook.
  4. Classify a missing provider/environment prerequisite, a defect and a change request separately. Retest the agreed correction on the same owning business flow.
  5. Keep client acceptance distinct from source review, retained engineering execution and illustrative browser captures.
129 requirements with case links186 Custodia baseline requirementsSupplied request reconciliationPer-case assertion/source mapping

The wider Custodia baseline register provides operating context for all 186 retained requirements. Mapping a requirement to a chapter is not a claim that every infrastructure, provider, performance or security measure has been newly executed. Use the requirement-specific qualification and actual result evidence.

Integration and provider readiness

IntegrationDelivered / readiness boundaryPrepareInspect actual evidence
Pulse email / letter / message generationImplemented and covered by retained source/template/generation checksPublished catalogue/template pins, current dataset binding and recipient accessRetain generated output identity; dispatch and recipient receipt are subsequent outcomes.
In-app inbox / notificationsImplemented notification and authenticated outcome contractsCurrent subject/profile and authorized originating recordCheck actual inbox item, read state and outcome link with the recipient profile.
Browser Web PushImplemented opt-in, assignment binding and unsubscribe contractSupported browser, allowed permission, active subscription and configured push keyProvider acceptance is not proof of device display; expired endpoints are disabled.
Email / fax / other external transportUse only a configured, authorized provider bindingApproved destination, transport configuration and controlled delivery testDo not describe generated files or a local accepted command as delivered correspondence.
Azure external identity SSOIntegrated identity/session routeTenant application registration, permitted identity and valid sign-inVerify authorized selection and the resulting application session; no password is included in the package.
Regulix runtime timers and native workImplemented native models, timers, tasks and checkpoint contractsApproved exact model, eligible task worker and timer serviceTimer advancement is owned by the engine; it is separate from a scheduled Pulse/Vista job.
Enterprise SchedulerRuntime and seven management areas delivered separatelyCurrent worker heartbeat, permitted operation/profile, published producer and queue/calendar readinessRun/retry/rerun/backfill and dependent checkpoint outcomes have separate identities; uncertain effects require reconciliation.
Custodia scan / extraction / storageGoverned intake, scan and worker contracts availableConfigured scanner/extractor/storage policy and admitted exact document versionQuarantine, malware decision, extraction, encrypted copy and archive are separate observable states.
Custodia scheduled reconciliationDedicated read-only scan/investigation contractAuthorized scan scope and the dedicated worker healthAn observation or note authorizes no deletion/repair; it is not an arbitrary Scheduler job.
Nexora AI mentorProvider not selected in the current authoring contractApproved AI provider and explicit configuration before enablingThe help/learning functions remain separate; do not present generated mentoring as delivered.
Nexora SCORM hostingIsolated HTTPS content host not selectedApproved package hosting, isolation and supported launch contractOrdinary authored lessons and secure linked media remain available; package import/launch is not assumed.
Nexora live meeting provisioningAutomatic meeting provider not selectedUse the supported session record and an approved externally prepared meeting linkSession registration and attendance do not prove automatic meeting creation.
Recipient consent / channel fallbackDo not infer authorization from a local generation policyUse the actual approved consent, suppression and routing provider contractsA preferred contact or generated artifact is not blanket consent or automatic cross-channel fallback.
MEDES target useInstalled capabilities documented; target activation remains an environment prerequisiteAuthorized case scope and active owner integrationsDemonstrate case/evidence/correspondence using prepared target records; do not substitute a fixture result for target acceptance.
Asset OperationsSeparate supporting application; excluded from the fourteen Kernel module countIts own authorized application entry and request/stock/actionsUse the supporting walkthrough only when that application is in the agreed demonstration scope.

Download the readiness matrix. Application implementation already recorded as delivered remains delivered. These documentation additions do not reopen that implementation queue. The user elected to continue without their production-browser acceptance; this package does not claim that excluded run.

Supporting Asset Operations

Asset Operations has its own application entry, stock and request lifecycle. It is not a fifteenth Kernel module and is not Nexora learning content. Its dedicated request → decision → allocation → acknowledgment procedure appears as a clearly labeled supporting annex in both cross-module editions.

Supporting operating procedure · Supporting demonstration · UAT handover