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.
New dedicated procedures
| Module | Worked procedure | Manual | Demo |
|---|---|---|---|
| Identity and Access Management | Copy menu access from one or more roles | Read procedure | Present walkthrough |
| Identity and Access Management | Bulk changes with mixed results and interrupted processing | Read procedure | Present walkthrough |
| Identity and Access Management | User Access Hierarchy investigation and drilldown | Read procedure | Present walkthrough |
| Identity and Access Management | Personal-information contact preferences and enrollment selection | Read procedure | Present walkthrough |
| Pulse | Browser push opt-in, profile binding and unsubscribe | Read procedure | Present walkthrough |
| Pulse | Author and review the correspondence catalogue before generation | Read procedure | Present walkthrough |
| Pulse | Suppressed, future and expired generation policies | Read procedure | Present walkthrough |
| Pulse | Channel setup and provider-readiness boundaries | Read procedure | Present walkthrough |
| Pulse | Pulse generation queue recovery versus Enterprise Scheduler recovery | Read procedure | Present walkthrough |
| Axis | Profile/locale-specific experience and restrictive overrides | Read procedure | Present walkthrough |
| Axis | Rollback and the distinction between publication and activation | Read procedure | Present walkthrough |
| Custodia | Nested collection moves and inherited collection holds | Read procedure | Present walkthrough |
| Custodia | Typed internal and external document relationships | Read procedure | Present walkthrough |
| Custodia | Private page notes independently of redaction | Read procedure | Present walkthrough |
| Custodia | Encrypted supporting-copy creation and integrity verification | Read procedure | Present walkthrough |
| Custodia | Persisted storage investigations and scheduled reconciliation | Read procedure | Present walkthrough |
| Custodia | Multi-file/ZIP intake and format-specific partial recovery | Read procedure | Present walkthrough |
| MEDES | Administration, status meanings and owner settings | Read procedure | Present walkthrough |
| MEDES | Fax-cover fields and exact reviewed transmission packet | Read procedure | Present walkthrough |
| Nexora | Discussion creation, replies and moderation | Read procedure | Present walkthrough |
| Nexora | Policy authoring/attestation and competency/readiness modeling | Read procedure | Present walkthrough |
| Nexora | Policy authoring/attestation and competency/readiness modeling | Read procedure | Present walkthrough |
| Nexora | Governed evidence-package request, approval, download and revocation | Read procedure | Present walkthrough |
| Nexora | Learning administration, FAQ and announcements | Read procedure | Present walkthrough |
| Nexora | Learning administration, FAQ and announcements | Read procedure | Present walkthrough |
| Nexora | Learner saved content, ratings, notes and intelligence views | Read procedure | Present walkthrough |
| Regulix | Timer wait, due-time advancement and repeated polling | Read procedure | Present walkthrough |
| Regulix | Claim/delegate/release and per-stage task eligibility | Read procedure | Present walkthrough |
| Regulix | Current-context and decision/event-driven CMMN sentries | Read procedure | Present walkthrough |
| Regulix | Incident investigation and closure | Read procedure | Present walkthrough |
| Regulix | Loop and manually activated multi-instance process work | Read procedure | Present walkthrough |
| Regulix | Loop and manually activated multi-instance process work | Read procedure | Present walkthrough |
| Regulix | Simulation/process suites and terminal instance archive | Read procedure | Present walkthrough |
| Regulix | Simulation/process suites and terminal instance archive | Read procedure | Present walkthrough |
| Tenant Engine | Separate parent-relationship and branding change walkthroughs | Read procedure | Present walkthrough |
| Tenant Engine | Separate parent-relationship and branding change walkthroughs | Read procedure | Present walkthrough |
| Tenant Engine | Custodia supporting evidence through tenant identity review | Read procedure | Present walkthrough |
| Kernel Core | Generic active/inactive lifecycle with explicit false retained | Read procedure | Present walkthrough |
| Supporting Asset Operations | Supporting Asset Operations: request, decide, allocate and acknowledge | Read procedure | Present walkthrough |
Use requirements and results together
- Open the requirement and its linked worked case. The previous case identifiers are preserved alongside the worked IDs.
- Prepare the selected profile, synthetic records and exact versions using the chapter and preparation register.
- Run the main path and the applicable denied/recovery checks. Record the observed state, returned identity and evidence in the workbook.
- Classify a missing provider/environment prerequisite, a defect and a change request separately. Retest the agreed correction on the same owning business flow.
- Keep client acceptance distinct from source review, retained engineering execution and illustrative browser captures.
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
| Integration | Delivered / readiness boundary | Prepare | Inspect actual evidence |
|---|---|---|---|
| Pulse email / letter / message generation | Implemented and covered by retained source/template/generation checks | Published catalogue/template pins, current dataset binding and recipient access | Retain generated output identity; dispatch and recipient receipt are subsequent outcomes. |
| In-app inbox / notifications | Implemented notification and authenticated outcome contracts | Current subject/profile and authorized originating record | Check actual inbox item, read state and outcome link with the recipient profile. |
| Browser Web Push | Implemented opt-in, assignment binding and unsubscribe contract | Supported browser, allowed permission, active subscription and configured push key | Provider acceptance is not proof of device display; expired endpoints are disabled. |
| Email / fax / other external transport | Use only a configured, authorized provider binding | Approved destination, transport configuration and controlled delivery test | Do not describe generated files or a local accepted command as delivered correspondence. |
| Azure external identity SSO | Integrated identity/session route | Tenant application registration, permitted identity and valid sign-in | Verify authorized selection and the resulting application session; no password is included in the package. |
| Regulix runtime timers and native work | Implemented native models, timers, tasks and checkpoint contracts | Approved exact model, eligible task worker and timer service | Timer advancement is owned by the engine; it is separate from a scheduled Pulse/Vista job. |
| Enterprise Scheduler | Runtime and seven management areas delivered separately | Current worker heartbeat, permitted operation/profile, published producer and queue/calendar readiness | Run/retry/rerun/backfill and dependent checkpoint outcomes have separate identities; uncertain effects require reconciliation. |
| Custodia scan / extraction / storage | Governed intake, scan and worker contracts available | Configured scanner/extractor/storage policy and admitted exact document version | Quarantine, malware decision, extraction, encrypted copy and archive are separate observable states. |
| Custodia scheduled reconciliation | Dedicated read-only scan/investigation contract | Authorized scan scope and the dedicated worker health | An observation or note authorizes no deletion/repair; it is not an arbitrary Scheduler job. |
| Nexora AI mentor | Provider not selected in the current authoring contract | Approved AI provider and explicit configuration before enabling | The help/learning functions remain separate; do not present generated mentoring as delivered. |
| Nexora SCORM hosting | Isolated HTTPS content host not selected | Approved package hosting, isolation and supported launch contract | Ordinary authored lessons and secure linked media remain available; package import/launch is not assumed. |
| Nexora live meeting provisioning | Automatic meeting provider not selected | Use the supported session record and an approved externally prepared meeting link | Session registration and attendance do not prove automatic meeting creation. |
| Recipient consent / channel fallback | Do not infer authorization from a local generation policy | Use the actual approved consent, suppression and routing provider contracts | A preferred contact or generated artifact is not blanket consent or automatic cross-channel fallback. |
| MEDES target use | Installed capabilities documented; target activation remains an environment prerequisite | Authorized case scope and active owner integrations | Demonstrate case/evidence/correspondence using prepared target records; do not substitute a fixture result for target acceptance. |
| Asset Operations | Separate supporting application; excluded from the fourteen Kernel module count | Its own authorized application entry and request/stock/actions | Use 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