Operate
User Guides
Detailed operating procedures, fields, review decisions, troubleshooting and platform handoffs.
One index · three distinct libraries
Choose the document for your task: learn how to operate, present a demonstration, or prepare and record UAT.
Operate
Detailed operating procedures, fields, review decisions, troubleshooting and platform handoffs.
Demonstrate
Dedicated module demonstrations with preparation, screen steps, expected outcomes, evidence and next steps.
Accept
Release scope, regression results, test cases, deployment pipeline, Kong, dependencies, defects and sign-off.
Each module has a separate operating guide and demonstration. UAT links take you to the acceptance pack.
14 Kernel modules
| Module | Coverage | User guide | Demonstration | UAT |
|---|---|---|---|---|
| Axis | Govern the relationship between screens, UI components, permission references, labels, experience versions and generation deliveries. Axis controls reviewed screen configuration; IAM remains the authority for actual user access. | Read guide | Open demo | Acceptance pack |
| Custodia | Document capture, processing, metadata, versions, sharing, retention, governed export, archive and recovery. | Read guide | Open demo | Acceptance pack |
| Enterprise Scheduler | Job definitions, execution ownership, schedules, calendars, queues, retries, reruns, backfills, batches, checkpoints and audit. | Read guide | Open demo | Acceptance pack |
| Identity and Access Management | Full account, access administration, configuration, RBAC/ABAC, governance and audit procedures. | Read guide | Open demo | Acceptance pack |
| Kernel Atlas | Maintain governed project knowledge, relationships, traceability and controlled publications. Confirm the available workspace and permissions with your administrator before following these procedures. | Read guide | Open demo | Acceptance pack |
| Kernel Core | Maintain the shared people, organizations, contact, address, geography, relationship, state and reason records used by the platform. A party record represents a person or organization; creating a party does not create a sign-in account. | Read guide | Open demo | Acceptance pack |
| MEDES | Member/case context, evidence intake, independent review, case work, correspondence, delivery tracking and reports. | Read guide | Open demo | Acceptance pack |
| Nexora | Discover and complete learning, maintain governed content, manage assignments and campaigns, and inspect competency, credential and audit evidence. | Read guide | Open demo | Acceptance pack |
| Pulse | Source and dataset binding, email and letter design, review, publication, output, channels and delivery recovery. | Read guide | Open demo | Acceptance pack |
| Regulix | Design and govern BPMN processes, CMMN cases and decision rules; run approved definitions; complete assigned work; and inspect decisions, deployment, timers and SLA incidents. | Read guide | Open demo | Acceptance pack |
| Tenant Control Plane | Govern environment registration, deployment bindings, configuration promotion, residency/support policy, module entitlements, lifecycle activation and exit closure. Follow the dependency order rather than treating each control-plane form as independent setup. | Read guide | Open demo | Acceptance pack |
| Tenant Engine | Establish and govern a tenant’s identity, organization binding, configuration, commercial evidence, domains and published tenant truth. Tenant setup progresses through distinct owner checks; a saved or registered tenant is not necessarily active. | Read guide | Open demo | Acceptance pack |
| TimeVault | Manage effective-dated versions of controlled master data and inspect the review/history that made a version effective. Country and State provide the principal user journeys; reviewed role-definition preservation is an IAM integration. | Read guide | Open demo | Acceptance pack |
| Vista | Connections, sources, reviewed datasets, report and dashboard authoring, current-data preview, publication and scheduled output. | Read guide | Open demo | Acceptance pack |
Follow ownership and record references across Core, Tenant Engine, TCP, IAM, Axis, TimeVault, Regulix, Pulse, Vista, Scheduler, Custodia, MEDES, Nexora and Kernel Atlas.
| Module | Change | What is covered |
|---|---|---|
| IAM | Explicit domain/profile mapping | Approved domain creation starts with zero profile links; pending mappings do not grant eligibility. |
| Axis | Governed screen authoring | Create Screen, source/field definitions, access mapping, draft, preview and originating-record review. |
| IAM / Axis | Reviews on the owning record | Review pending master, mapping, screen and control changes in their originating workspace. |
| IAM | Named Super Administrator | Explicit scoped same-person review with administrator evidence; ordinary profiles retain independence checks. |
| Axis | Screen and control metadata | Screen title/help and control label/help/format maintained through governed presentation changes. |
| Axis | Owning screen controls | Controls list owning screens first; details and controls share context, refresh and Back behavior. |
| Pulse / IAM | Notification outcome links | Published notification OPEN contract restored; recipient/context checks retained. |
| MEDES | Activation qualification | Installed technical package; role grants, enabled APIs and review-route activation remain pending. |
| Kernel | Documentation hub | Master index, separate manuals/demos/UAT, linked modules, current supplement and offline downloads. |